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
Hi,
my phone died yesterday because the battery was empty - so I charged it a little but the phone won't turn back on. The only thing I see are the touch buttons flashing when I hold the power button. And when I hold it long enough, the screen just flashes... When I tried to connect it my computer I got the ADB to work - I even managed to get to the recovery one time (i used the command adb reboot recovery for almost a hundred times before it came on). I wiped everything, reinstalled the rom (TrickDroid 4.0.0), but when I tried to reboot it nothing changed... it's still not working. Fastboot is not working.
Is there anything I can do about it?
Thanks.
Mmm, are you using CWM perhaps? If so, once you get the phone into fastboot - flash twrp.
Some suggestions you can try:
keep trying vol- + power untill you get into fastboot, it should work eventually.
Charge the phone a bit, unplug the usb cable, try and boot it <- This worked for me when my phone acted up like this, took a couple of tries though.
Have you tried spamming adb reboot bootloader ? That should also put you into fastboot eventually.
Once in fastboot, reflash the boot.img for the rom as well.
And once it works again, dont let the battery go flat, this seems like quite a common issue when the battery runs out.
Thanks for suggestions - I wrote a script that tired adb reboot bootloader every 20s .. and after like 400 runs it booted - I have no idea what this is about - but I should buy a new phone...
Tahnks again!
So as the title goes, I was helping my friend.
The phone first suddenly just crashed and went into safe mode and it wouldn't get out of safe mode. Even after rebooting it still doesn't get out of safe mode.
So I suggested to my friend that I help him reinstall his ROM and I was going to flash cm12 for him. So he rebooted the phone into fastboot mode and i did fastboot oem unlock
After fastboot oem unlock, the phone rebooted back into fastboot mode except this time the screen was blinking while the phone was plugged in. When the phone was not plugged in, the screen wouldn't blink but trying to restart it results in a black screen. So I suggested to my friend that the battery is probably low and he said the battery was low when we started. So I told him to plug in the phone to his charger and leave it to charge for a while. We met back after 30 mins and but this time it got even worse. I couldn't even detect the phone in fastboot mode. Previously it had "????? fastboot" when i ran the command fastboot devices but this time there was nothing. Also before we left the phone to charge for 30 mins, slightly after the "???? fastboot" fastboot devices wouldn't turn up anything but fastboot commands like fastboot reboot would work. I tried to install TWRP but it came up with a too many links error.
Now the phone doesn't even get detected by fastboot on windows and we're meeting up irl and im brining my laptop along to try to fix it. Does anybody have any idea about what went wrong?? Im kinda dumbfounded. I have unlocked the bootloader of the oneplus and install a custom rom on my own device but ive never encountered something like this... Any help would be great!
EDIT:
tl;dr - Nexus 5 went into fastboot mode and the screen started blinking after fastboot oem unlock was issued. Previously, it was stuck in safe mode and you couldn't get out of it even if you rebooted. Now it the screen stops blinking if you dont connect the usb cord but the moment you connect the device to an adapter or a computer, the fastboot mode screen just keeps blinking and blinking and the computer can't detect it either so you can't do anything. rebooting with volume up and power also just lands you back in fastboot mode with the blinking. weird ass problem and it looks like im the first. it does say state unlocked though so theres that
I had something similar happen. In my case I had forgotten you have to completely boot up android after doing the oem unlock (not just boot loader). I had to do the opposite, OEM lock bootloader, reboot all the way, then OEM unlock, (again) then reboot all the way. Then continue as before.
It worked for me
I flashed CM12 a few days ago on my rooted HTC sensation, with unlocked bootloader, S-OFF etc.
The install has not gone too well, and most of the programs started force closing, to the point where all the android can do is shut down, restart, or go into aircraft mode by holding the power button.
I can not send the phone an adb reboot-bootloader option, because the phone wont prompt me to authorize my PC for remote commands, and I cant get into the bootloader of the phone by powering on with volume down + power, because the volume down button is faulty.
Is there anything else I can do to recover the device and re flash, such as placing a file or script on the SD card for when it boots??
Thanks for any suggestions/help.
mi16chap1 said:
I flashed CM12 a few days ago on my rooted HTC sensation, with unlocked bootloader, S-OFF etc.
The install has not gone too well, and most of the programs started force closing, to the point where all the android can do is shut down, restart, or go into aircraft mode by holding the power button.
I can not send the phone an adb reboot-bootloader option, because the phone wont prompt me to authorize my PC for remote commands, and I cant get into the bootloader of the phone by powering on with volume down + power, because the volume down button is faulty.
Is there anything else I can do to recover the device and re flash, such as placing a file or script on the SD card for when it boots??
Thanks for any suggestions/help.
Click to expand...
Click to collapse
Have you tried turning the phone off, plugging it into the computer, turning the phone on, and keep on sending the adb reboot-bootloader command as the phone is booting up? I've heard that this works as the phone will eventually get it at one point while its booting up.
Hi, ive been having problems with my pixel 7, it seemed like no matter how i flashed it it still wouldnt work 100 percent properly. even if i used android flash tool. So today i flashed the disable-verity/verification flags and then booted into system and I turned off auto system updates and did adb reboot bootloader. It didnt reboot into the bootloader but instead shut off and showed the icon for a battery that wasnt charged. holding voldown and power did notheing immidiately so I unplugged the usb and held power and volume down. It went into the bootloader, however this time the readon was not vol down pressed but "bootonce-bootloader" instead. anyone ever see this or know what this means?
PochiRaccoon said:
Hi, ive been having problems with my pixel 7, it seemed like no matter how i flashed it it still wouldnt work 100 percent properly. even if i used android flash tool. So today i flashed the disable-verity/verification flags and then booted into system and I turned off auto system updates and did adb reboot bootloader. It didnt reboot into the bootloader but instead shut off and showed the icon for a battery that wasnt charged. holding voldown and power did notheing immidiately so I unplugged the usb and held power and volume down. It went into the bootloader, however this time the readon was not vol down pressed but "bootonce-bootloader" instead. anyone ever see this or know what this means?
Click to expand...
Click to collapse
Question: Is your Pixel Carrier Locked?
It's my first post leave some comments if you find it helpful...
I was using a Linux box with a BLU oem USB c charger.. wait till the battery percentage shows 0% or 1% hold the volume down button while pressing the power button just get to the bootloader and ..
Once your able to connect it using fastboot... Either use fastboot reboot recovery or select it from the boot menu..
Download the platform tools from Google.. also the latest OTA for your device.. extract the zip to a your Desktop then toss the compressed OTA... In that folder open terminal or cmd... Run adb sideload OTA.zip..
Reboot one more time to manually enter recovery WIPE DATA nd Factory Reset..
Reboot back to bootloader fastboot reboot sideload or reenter recovery>apply OTA from adb..
Adb devices should return device and sideload... Issues the command adb sideload OTA.zip one last time... Nd your back in business... My friend