Related
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
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?
Hi. I was on #xoom at freenode earlier and I got some help, but unfortunately no solution. (thank you Kas, EbonyGhost, Pyrator and the others)
I flashed the recovery here:
http://forum.xda-developers.com/showthread.php?t=1074979
I flashed... THE ZIP!!
The flash went well, then the device rebooted and showed "Starting RSD mode 3"
I have only 2 screens:
- with VolUp + power = dual core techno + "Starting RSD mode 3"
- with VolUp + power then immediately VolDown = only the dual core tech logo, no text
Either way: no adb, no fastboot. Tried other usb slots. Tried reinstalling moto drivers.
The xoom never gets recognised by windows. I don't have the dongdong sound when I plug it, in either mode.
I already tried this:
http://forum.xda-developers.com/showthread.php?t=973355
but I get < waiting for device > because it's not recognised by windows...
Any other idea?
Thanks
Regards
Note: I might be away for several days. I'll try everything you say, but maybe I won't be able to post my feedback until monday night (around GMT timezone)
I have this exact problem.
So, when you power up the device, you press 'vol-down' when you see the Motorola logo? Because that should put you into fastboot mode. Don't use the power+vol-up, only turn on device and press vol-down when you see the logo. I've been in the same situation, but was able to get fastboot working like this...
if you hold the volume down button and power on the device and get no fastboot then you may as well just send it to motorola. looks like this is becoming a problem and cannot be fixed.
mbroeders said:
So, when you power up the device, you press 'vol-down' when you see the Motorola logo? Because that should put you into fastboot mode. Don't use the power+vol-up, only turn on device and press vol-down when you see the logo. I've been in the same situation, but was able to get fastboot working like this...
Click to expand...
Click to collapse
This. Flashing the wrong partition should *not* mean that you can't get into fastboot any more.
I know that volume down should get me to fastboot but in fact it doesn't. Windows never makes dong dong when i plug the xoom... My drivers are ok because my nexus one gets recognized instantly and adb is working fine on the phone...
Any reason you don't use RSD to flash the wifi xoom sbf file? (I'm pretty sure someone said that was released not too long ago)
I didn't try yet, I can't find the SBF for the wifi xoom.
I tried the 3G SBF file it's not even working. I know it's not the right file for my device but since it's already bricked...
I have RSD Lite 4.9, latest moto drivers, updated using the moto tool.
When I load the sbf file in rsd lite, I can't see the device, and pushing start has no effect.
I did that when the device was showing "Starting RSD mode 3"
How can I get it back?! I tried on my windows laptop and also on a macbook, without any luck.
This is happened to me , and i flipped cuz i rendered my $600 Xoom to a paper weight , i rebooted (Volup+power then voldown) , i tried ADB and it didn't work... then i left my computer to do something, i returned to my PC and i was flipping through DOS command lines (up and down arrows) and click enter in one of the commands by mistake and it worked! the command was "fastboot erase cache"
i then typed the following to return to stock (you need the stock files)
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Thanks, but I don't have fastboot. It's always < waiting for device >
Topper Harley said:
Thanks, but I don't have fastboot. It's always < waiting for device >
Click to expand...
Click to collapse
You mentioned you tried the steps in http://forum.xda-developers.com/showthread.php?t=973355, but how did this section go:
"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."
ed. The other suggestion I heard floating around is to flash the CDMA Xoom's SBF -- yes, it won't get you all the way there, but it might restore things up to the point where you can get into fastboot and then flash the stock images.
I did try already to fastboot flash boot boot.img (stock), then reboot pushing vol up, vol down, both, using clicking or holding them... no luck
I also tried to flash the VZW SBF file but RSD Lite doesn't even see the device. I'm trying now to get some linux running and use sbf_flash instead because I was told that it's more efficient than the linux one.
No luck yet on that part either.
I was able to get my xoom restore with the following steps:
Hold Power + Vol up to start reboot
immdiately hold Power + Vol down (This will get you to the Fastboot menu)
enter the commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
You've now successfully flashed your Xoom back to stock. Now it's time to relock the device.
Type fastboot oem lock, wait for the menu, the press the volume-down button. Then press the volume up button. It'll take a minute or so, then reboot. You're now completely back to stock and ready for the update.
hoopsdavis said:
I was able to get my xoom restore with the following steps:
Hold Power + Vol up to start reboot
immdiately hold Power + Vol down (This will get you to the Fastboot menu)
Click to expand...
Click to collapse
It stops here. I can't get fastboot.
I tried waiting for the battery to die and tried every combination of vol up/down/power, hold/click/double click the buttons...
I'll let it cool off for one day without battery... maybe it'll wake up wanting to give me fastboot...
I'm losing hope...
Topper Harley said:
It stops here. I can't get fastboot.
I tried waiting for the battery to die and tried every combination of vol up/down/power, hold/click/double click the buttons...
I'll let it cool off for one day without battery... maybe it'll wake up wanting to give me fastboot...
I'm losing hope...
Click to expand...
Click to collapse
I'm in the same situation here... tried basically all the same steps. I'm lost too... can't connect with ADB, Fastboot or RSD... tried all kinds of key combos as well. "Starting RSD Mode 3"... its wearing me down!!
How can i change the topic title? I wanted to say "xoom bricked?" but I typed rooted by mistake
I'm in this exact situation, and I've tried everything suggested here. I spent some time in IRC talking to a few developers, and we tried pretty much everything to get fastboot to work. No luck, so I tried RSD like you said, and that didn't work, either. Eventually we gave up, and I got an RMA from Motorola via their website. I should receive the FedEx box tomorrow so I can return it to them.
If you want, I'll report back here when the whole process is over and tell you if they end up fixing it for free or not. It sounds like it'll probably be at least a week, though.
benso87: yes, tell me. I have time don't worry (away from home until may 28th)
Otherwise, I think mine is definitely a brick. I tried the last thing I didn't: boot linux and test sbf_flash: not working.
I'll try to send it to moto (the device is imported).
I'm kinda sad... not for the money, but for the bad command that completely destroys a device in seconds... and right, for the money aswell...
Small update: I got the box yesterday and sent it back, then got an email this morning saying Motorola received it. Hopefully the whole process will go this fast.
They gave me a tracking number and a site to check to see how things are going, so that's more info than I was expecting. They haven't asked any questions yet, so that's also good.
Hoping someone here may have some ideas. ..
Picked up a couple Global's the other day on eBay. Two of the three work great. Was able to get them unlocked, rooted, and band unlocked. They are working great on T-mobile! The issue I'm having is with the third one. When I enter the bootloader, I get nothing but a black backlit screen with no writing. When I attempt to use RSD Lite, I can't get it to recognize the phone at all.
So next I tried booting the phone normally, and then hooking it to the PC. RSD Lite does recognize it that way. When I begin the flash process, the phone attempts to reboot into flash mode, screen goes black, same backlit screen with no writing. I would like to point out that I am doing all this with a 5-wire factory cable, so none of the usual button combo mistakes, undercharged battery issues, etc. apply here. If you have on of these, you don't need a battery in the phone at all. With and without battery, with and without factory cable...hasn't mattered, no bootloader no matter what. The issue is that the bootloader acts as if it just isn't even on the phone. I know there are several ways to reload that consumer replacement to a droid 1, but I haven't found anything for a 2. The other thing limiting what I am able to do is that the phone is running .629, which means no root or CWM, so those couple tricks are out the window at this point also, and because of the bootloader issue I am unable to downgrade using RSD Lite or any of the bootable CD options that usually work for phone stuck on .629.
So at this point I'm figuring the phone is just stuck the way it is, but I thought I'd throw it out there and see if any of you guys had any similar experiences. Thanks
strabo231 said:
Hoping someone here may have some ideas. ..
Picked up a couple Global's the other day on eBay. Two of the three work great. Was able to get them unlocked, rooted, and band unlocked. They are working great on T-mobile! The issue I'm having is with the third one. When I enter the bootloader, I get nothing but a black backlit screen with no writing. When I attempt to use RSD Lite, I can't get it to recognize the phone at all.
So next I tried booting the phone normally, and then hooking it to the PC. RSD Lite does recognize it that way. When I begin the flash process, the phone attempts to reboot into flash mode, screen goes black, same backlit screen with no writing. I would like to point out that I am doing all this with a 5-wire factory cable, so none of the usual button combo mistakes, undercharged battery issues, etc. apply here. If you have on of these, you don't need a battery in the phone at all. With and without battery, with and without factory cable...hasn't mattered, no bootloader no matter what. The issue is that the bootloader acts as if it just isn't even on the phone. I know there are several ways to reload that consumer replacement to a droid 1, but I haven't found anything for a 2.
Click to expand...
Click to collapse
maybe bricked, could try manually installing update.zip from android recovery, if you can get to that
How to enter Android system recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the power button.
Once you see a warning sign with an android robot appear, press the Search button on your physical keyboard if you're running froyo/2.4.x firmware. For gingerbread/4.5.x firmware, press Volume Up and Down buttons.
and be sure you are using
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
The other thing limiting what I am able to do is that the phone is running .629, which means no root or CWM, so those couple tricks are out the window at this point also, and because of the bootloader issue I am unable to downgrade using RSD Lite or any of the bootable CD options that usually work for phone stuck on .629.
Click to expand...
Click to collapse
.629 has been rootable since 16 April 2012
just use ezSBF & Root 2.3.4/ 4.5.629
So at this point I'm figuring the phone is just stuck the way it is, but I thought I'd throw it out there and see if any of you guys had any similar experiences. Thanks
Click to expand...
Click to collapse
sd_shadow said:
maybe bricked, could try manually installing update.zip from android recovery, if you can get to that
How to enter Android system recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the power button.
Once you see a warning sign with an android robot appear, press the Search button on your physical keyboard if you're running froyo/2.4.x firmware. For gingerbread/4.5.x firmware, press Volume Up and Down buttons.
and be sure you are using
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
.629 has been rootable since 16 April 2012
just use ezSBF & Root 2.3.4/ 4.5.629
Click to expand...
Click to collapse
Ah Shadow! I was hoping you'd see this. Let me clarify a little bit.
1. I am able to get phone to boot into OS. I did try to install the update.zip already but I'm still having the same problem with the boot loader.
2. I know about the easy sbf, and tried that with this particular phone, but because of the problem with the boot loader when easy sbf or RSD Lite switch the phone, or attempt to switch into flash mode, the computer no longer recognizes the phone.
3. I did think about rooting the phone to try to open up a few other options to at least get around the problem. Since it's on .629 already though I'm limited to rooting using easy sbf as far as I've understood, but again since I'm having the issue with the boot loader that hasn't been an option I have been able to successfully use.
4. The power button on the phone isn't working, so I'm unable to use the key combo to access the boot loader; however, I have a factory cable...now I say factory cable not meaning the stock charging cable...but the 5-wire factory cable. Typically with Motorola phones using this cable you simply remove the battery, and then with no battery in the phone hold down both volume buttons and plug the factory cable in and it automatically reverts to the boot loader.
I know that there is a consumer replacement boot loader for the droid 1 to fix issues like this, but I haven't seen one for the two. The other issue is that the replacement is an sbf file which ill be unable to use, and didn't know if that was something that would exist as an update.zip that could be flashed through the stock recovery
don't need power button
with phone off, hold up arrow and connect usb cable
should boot directly to bootloader
sd_shadow said:
don't need power button
with phone off, hold up arrow and connect usb cable
should boot directly to bootloader
Click to expand...
Click to collapse
yeah we're on the same page there. When I do that, instead of getting the bootloader like I normally would, I'm just getting a blank black backlit screen, like the boot loader isn't there. Instead of getting bootlader D0.11 ect, It's just a blank screen. It doesn't matter which method I use to access it, both volume buttons and usb, up arrow and usb, whether there is a battery in the phone or not, I'm still getting the same result. If I boot the phone normally, and then try to let RSD switch it for me, it does it, and then I get the same black screen and the flash mode failure error. Like I said there is a consumer replacement bootloader for the 1 that I've been able to use to fix this problem in the past, but if one exists for the two I haven't been able to locate it. So at this point I have a working OS, a working stock recovery, and no boot loader
think there was a 608 bootloader file, can't remember where i saw it
but it didnt work on 629 anyways
you might be able to root with http://forum.xda-developers.com/showthread.php?p=37438602
Root Droid 2 on Gingerbread 2.3.4 [WINDOWS]
i havent got it to work, but it only takes a few mins to download and run
Sent from my XT862 using xda premium
sd_shadow said:
think there was a 608 bootloader file, can't remember where i saw it
but it didnt work on 629 anyways
you might be able to root with http://forum.xda-developers.com/showthread.php?p=37438602
Root Droid 2 on Gingerbread 2.3.4 [WINDOWS]
i havent got it to work, but it only takes a few mins to download and run
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
Yeah I tried that last night. I saw where you were having problems with it too. I had seen where a few months back there was someone else that was having this issue that you were trying to help walk them through, but the thread kinda died off, so I wasn't sure if there was ever a resolution to it. Ok well thanks for your time. I'll be sure to post an update for people coming behind me if I manage to get anywhere with it.
strabo231 said:
yeah we're on the same page there. When I do that, instead of getting the bootloader like I normally would, I'm just getting a blank black backlit screen, like the boot loader isn't there. Instead of getting bootlader D0.11 ect, It's just a blank screen. It doesn't matter which method I use to access it, both volume buttons and usb, up arrow and usb, whether there is a battery in the phone or not, I'm still getting the same result. If I boot the phone normally, and then try to let RSD switch it for me, it does it, and then I get the same black screen and the flash mode failure error. Like I said there is a consumer replacement bootloader for the 1 that I've been able to use to fix this problem in the past, but if one exists for the two I haven't been able to locate it. So at this point I have a working OS, a working stock recovery, and no boot loader
Click to expand...
Click to collapse
if you are still working on this a Bootloader Only
HS_S_signed_AP_BL_D11_cdma_droid2we_Consumer_replacer.zip
has been posted here http://sbf.droid-developers.org/cdma_droid2/list.php
If you're still looking to root, try Framaroot from here. It worked for me on .629. No idea about the bootloader however . Good luck though!
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