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
well i had trouble installing the trickroid v7 on my [S3] and it will say OS not installed.
then after many tries, of pulling the usb in and out and restarting several times to bootlocker
I cannot open to bootlocker anymore and the phone seems to died and not be able to charge.
WHEN I HOLD POWER button and volume down, all 3 soft touch keys lit up for 6~7 seconds, then the the black screen flashes a green line and off.
I cannot connect to the computer through usb either, for some reason.
i have the same problem.my phone worked fine, i unlocked bootloader, installed recovery and rooted. yesterday i put my phone on charging and today it was dead??? it flashes 7 times while holding vol down + power and then nothing happens.
EDIT:
i got it working!!! i connected it to pc, run adb command: adb reboot-bootloader and i got bootloader menu, after that i went into recovery and i did factory defaults and rebooted phone,now it's charging and everything is OK!
Bubach28 said:
i have the same problem.my phone worked fine, i unlocked bootloader, installed recovery and rooted. yesterday i put my phone on charging and today it was dead??? it flashes 7 times while holding vol down + power and then nothing happens.
EDIT:
i got it working!!! i connected it to pc, run adb command: adb reboot-bootloader and i got bootloader menu, after that i went into recovery and i did factory defaults and rebooted phone,now it's charging and everything is OK!
Click to expand...
Click to collapse
man.. i know i can fix it... but i cant connect to the damn pc. it unable to detect it... !!!
this is what i have done and got it working. connect phone to pc that has installed htc drivers, hold down volume down button + power, phone flashes 7 times and orange led is working now. after that go to adb, type adb devices and my phone serial number was shown. after that i did the adb reboot-bootloader and my phone was alive again.
p.s. i tried also with HTC One S All-In-One Toolkit V1.1,before i made it, to send command, but phone led only show orange light and again went off. u can give a try.... if that dont work, then i think phone is dead and ready for repair :/
Moto G not boot, it just gets in the bootloader screen warning
I'm having the exact same issue, just flashed the latest stable version of CM11 (with gapps obviously) from dhacker's thread in CWM.
Coming from 4.3 with the US version t-mobile moto g.
Stuck on the bootloader unlocked screen.
I thought for a while it was just that the first loadup takes awhile but has been 10 minutes now and am figuring something bad happened.
ignore all the italics, I'm an idiot
Edit: 25 minutes in, have tried connecting the phone to computer and running command prompts to it like I did to get into recovery, device not recognized under cmd "adb devices" or "fastboot devices" when connected to computer
Phone screen goes black for about 0.8 seconds when power button is held down and immediately pops back up into warning bootloader unlocked screen, trying to go into fastboot or anything like with volume down and power button achieves the exact same effect.
Any help would be greatly appreciated.
Edit2: If I hold the power button and down volume for 20 seconds (just ignore when the screen goes black and hold it for 20 seconds) it will boot into fastboot mode
Recovery seems to do nothing but the device is now recognized by the mototool all in one, I will report back if I figure out anything more useful, I am hoping the mototool will save me
Edit3: tried flashing stock recovery, my phone now says in pink "hab check failed for recovery", tried flashing CWM recovery, it seemed to work. I then clicked "fix boot logo" it worked. The phone is now showing the motorola logo but doesn't seem to be doing much else, I'll let it sit for a couple minutes.
Edit4: If none of this works at least you'll have an interesting read about how to further destroy your phone
Tried rebooting to recovery, the mototool thinks it did it but my phone stays stuck at the motorola logo. I then told it to check connection and it now thinks there is no longer a device connected. Tried turning the phone off again, went immediately back to the motorola screen. I seem to be in the same situation except the bootlogo is no longer that ugly text. Back into fastboot mode, lets see what else we can do.
I checked to see if it was recognized by command prompts now and it IS, if you go back under like you were unlocking the bootloader and open up a cmd prompt and type "fastboot devices" it's recognized in this fastboot mode. This has given me new optimism, I'm feeling hopeful that my device is not destroyed, hopeful and very hungry, I will report back in after getting food.
Edit5: I've realized that I have no idea where to go from here, while I can access command prompts I have no idea what commands to put in, I tried hitting "factory" under the fastboot in hopes that it would flash my factory recovery, no such luck, I'm back to the same situation, tried hitting BP tools next because I didn't know what it was and thought it would be helpful, no such luck, back to the same screen, my quickly inflated confidence is now waning, I do have hope that someone can fix this issue but I am thinking that someone is not me.
I hit the recovery button, I'm sure I had done this before but this time it worked, went to restore from sd card, and restored my backup I made right before all these issues, it recovered my device, I then restarted it and everything is good now.
Apparently I am an idiot, but that's okay because my phone is working again now, after only about an hour or something.
TO FIX YOUR ISSUE HOLD DOWN VOLUME AND POWER AT THE SAME TIME FOR 20 SECONDS, IGNORE WHEN THE SCREEN GOES BLACK, KEEP HOLDING FOR ALL 20 SECONDS, CHOOSE RECOVERY, THEN GO BACK TO YOUR BACKUP THAT YOU SAVED BEFORE FLASHING A NEW ROM, RESTART THE DEVICE AND NOW THE DAY IS SAVED
So here was my situation:
I was flashed the wrong piece of software (stupid me) and I was stuck in a boot loop. Unfortunately the volume down button on my HTC one S was not working so a simple boot into bootloader mode did not work!
Furthermore, I couldn't even get the phone OFF! Pressing the power button for minutes on end still ended up in the HTC constantly rebooting itself. (Worst thing ever!).
FIX:
Step 1: Power Off device
Although this may sound very easy to do, I could not get the device powered off via the power button(10-20 secs) so I had too do it the hard way.
Luckily, the One S being a sealed phone isn't actually hard to take apart. Its actually rather simple!
I used a video on youtube to disassemble then took out the battery for about 30 minutes. (Search "HTC ONE S fix" on Youtube and you'll find it. Sorry i can't post any links im a junior member!)
Step 2: Plug the USB cable into your PC
Put the battery in ( if you used the physical battery pull out of course)
With the device completely off plug the cable into the PC and run the command
Code:
adb devices
By doing this my device actually went straight to the recovery screen and the device was recognized on the computer.
Now the recovery screen i got wasnt very helpful as it continuously rebooted and eventually booted back to the white HTC screen.
HOWEVER, the fact that I could use ADB commands gave me hope.
Step 3: Reboot into bootloader using adb command
Code:
adb reboot bootloader
This is where I really saved myself i ran this command and got to the bootloader screen and I was able to actually work with that!
Step 4: Flash/ Restore Backup to your device and get it up and running!
Now there are a couple of ways you can choose to do this depending on your specific situation and resources available:
A) When in bootloader mode you can access the fastboot commands which will allow you to run any flashing commands that you need to rewrite whatever is corrupted (e.g boot.img)
B) If you have a working recovery simply select recovery and boot into recovery and flash either your nandroid backup or a new ROM as a whole
C) This is what i did, I ran a stock RUU which deteccted my phone and in 10 minutes my phone was up and running!!
Now I know this is a rather rare case, but I actually thought my phone was gone and the fact that I got it working really motivated me to put this out there so someone like me may be able to get their phone up and running again!
Forgive me this is probably my first real thread, Hopefully I continue to post how I fix some of the rarest occurrences I always seem to get myself into.
NO MORE BOOTLOOPS! Who says we need volume down buttons? LOL
Moto G XT1032 Black screen, can't reset
I was playing a game I've been playing for at least one week, when my screen suddenly went black. Pressing power wouldn't help. I had this happened once and did the "press power+vol down for 10 seconds" to reset the device, but now it didn't work. I've been looking around to see what to do, and nothing is working.
Pressing power for 120 seconds (as motorola's site suggests) didn't work.
I tried adb reboot but I got "device not found."
Code:
fastboot devices
showed it, though, so...
I tried
Code:
fastboot reboot
and I got "rebooting... finished." But nothing happened on the phone.
So I tried
Code:
fastboot reboot-bootloader
and now it's "waiting for device" and
Code:
fastboot devices
reports nothing.
When I press the power button for 10-15 seconds I get a vibration, but that's about it. If I press it along with vol down I get nothing, but windows reports it as an unknown device when the 10 seconds pass (as if it restarted).
Any help would be greatly appreciated as I don't have any backup device or anything u_u"
Bumping and updating:
After I used another cable I was able to get to fastboot (but only using the computer, the phone screen is still black). I tried fastboot -w and also reinstalling the gpe with this (http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522), then installed twrp.
Nothing worked, so now I'm wondering if the problem is my screen, and if so, how can I be sure?