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
Background Information:
Droid MAXX (XT1080)
Rooted
Write Protection - Off
Safestrap
Ok so I rooted my phone and turned write protection off and yesterday I couldn't get touchless control to train for the life of me so I decided to boot into safestrap this morning and I fixed permissions and then went to do a factory reset and selected format /system wihthout thinking about it...
Now all my phone does is turn on and stay at the blue Motorola logo...
So I tried to fastboot and rsdlite but neither will see the phone so I tried to adb devices -l and that won't see the phone either.
So any ideas on what I can do or did I hard brick my phone since write protection is off.
Thanks,
Ryan
G33kman said:
Background Information:
Droid MAXX (XT1080)
Rooted
Write Protection - Off
Safestrap
Ok so I rooted my phone and turned write protection off and yesterday I couldn't get touchless control to train for the life of me so I decided to boot into safestrap this morning and I fixed permissions and then went to do a factory reset and selected format /system wihthout thinking about it...
Now all my phone does is turn on and stay at the blue Motorola logo...
So I tried to fastboot and rsdlite but neither will see the phone so I tried to adb devices -l and that won't see the phone either.
So any ideas on what I can do or did I hard brick my phone since write protection is off.
Thanks,
Ryan
Click to expand...
Click to collapse
Adb won't work unless you're booted to the OS. You need to boot into your bootloader. With vol off press and hold vol down and pwr for about 5 sec then release. This will get you into bootloader where you can use fastboot, rsd, and such.
Sent from My Droid Ultra
Caseyk621 said:
Adb won't work unless you're booted to the OS. You need to boot into your bootloader. With vol off press and hold vol down and pwr for about 5 sec then release. This will get you into bootloader where you can use fastboot, rsd, and such.
Sent from My Droid Ultra
Click to expand...
Click to collapse
Yeah I tried booting into fastboot along with loading it into rsdlite but it didn't see the device since it wasn't really booting past the motorola logo. :/
If you are properly booting to the bootloader you should never see the moto logo.
Try this exactly (when the phone is stuck on the M):
1. Press Power and Vol - at the same time until the screen turns off
2. release power button once screen turns off, continue holding vol -
you should now be in the bootloader screen. Try it a couple of times if it doesnt work... I had this happen once or twice and it was a ***** to get the phone into the bootloader.
G33kman said:
Yeah I tried booting into fastboot along with loading it into rsdlite but it didn't see the device since it wasn't really booting past the motorola logo. :/
Click to expand...
Click to collapse
With all due respect, you must be doing something wrong or perhaps messing up some of the terminology. By following the steps I stated above it will boot your phone to the bootloader. It will say AP Fastboot mode at the top of the screen. And some other things. Then below that it will have your options in blue...normal power up, recovery, barcode...etc. Getting to that screen does not show the boot logo (in your case the Motorola logo) You also said you tried loading it into rsd. Well rsd won't work unless you're in fastboot mode ( the screen I mentioned above.)
Sent from My Droid Ultra
Yeah I have been in the AP Fastboot mode plenty of times before with this phone and it's not working this time I have tried numerous times this morning. With the Write protection - off I'm assuming when I formatted the /System /data /Cache partitions it messed everything up...
I submitted a claim (my phone was stolen) and will be getting a replacement tomorrow.
ap fastboot Flash Mode (s)
10.9B(*) (sha-61146a2, 2014-07-29 2:30:05)
eMMC Info: Size 8GB
Device is LOCKED, Status Code:0
Battery OK
Connect USB
Data Cable
Fastboot Reason: Sticky bit factory_fastboot
------------------------------------------------------------------------------------------------------------------
The Version Is 4.4.2 of the operating system
when i press the power button this happens, i can however hold the power button and both volume buttons to get into the operating system, by loading normally, I need to fix this issue so i can take another swing at trying to mod this razr-m xt907
the previous issue before i made it to this issue was
Fastboot Reason: fastboot failure this happens if you mess up and try to towel root from your phone as in download the file onto your phone and then run the file from your phone, so any user out there trying to root their phone, that is not the way to go. Also I Am Dubbing This The Screen of Black Death!
As per Rooting the Phone, I tried Using "motofail2go" I press enter the App communicates with the phone then the dameon Starts, after that nothing at all happens i let it sit for 15-20 minutes and nothing happens
please help me figure this out, my goal is to put cm on my phone, it is locked and unrooted at the moment, taking the above information walk me through it please, im on my knees begging.
I manage to solve it :good:
In summary:
What lead me to Error Mode:
I wanted to rollback to marshmallow, because i had updated to dual sim nougat (long story) so it was problematic (missing apps ecc.), i tried to install the rollback with "dd if of" before installing the marshmallow firmware with dload but something has gone wrong and the "recovery" and "recovery2" partitions were corrupted and "cust" and "version" as well but because of the update (no update in settings, NDR90M test-keys).
I rebooted in fastboot to patch things up, but the bootloader was locked because to rollback i reinstalled the single sim "oeminfo" partition, so i unlocked the bootloader, but the phone couldn't be factory resetted since it hadn't a working recovery, so the phone apparently refused to boot any other mode than "Error Mode" with the following message:
Error!
Func NO: 11(recovery image)
Error NO: 2(load failed!)
and it wasn't detected by any pc.
How it was solved:
After some googling i found out that let my phone discharge + a button combination could lead to booting into fastboot (https://forum.xda-developers.com/honor-9/help/help-hardbrick-func-11-recovery-image-t3656979), so i left my phone booted in Error Mode.
When it turned off i plugged it into the pc and left it charge a bit, and suprise, after some minute it booted up automatically in system (idk why), but it shutdown on the lockscreen, so i let it fully discharge again in Error Mode and i this time i plugged it into an outlet, and it booted successfully, but to boot into system i had to discharge it completely everytime.
I tried "adb reboot bootloader", "adb reboot recovery" and i tried to factory reset from settings but no luck.
Then i turned it off and i started to spam the **** out of my phone by trying every combination possible, and finally one seems to have lead me to fastboot after a lot of tries: i let it charge a bit while booted into the system (like 8%), then i turned it off, and i tried "Power + Vol+", "Plugged/Unplugged", "Power + Vol-" in random order and multiple times, and it worked, from what i remember it was: Turn off->Power + Vol+ (Error Mode) -> Plugged -> Power + Vol- (Fastboot)" but i'm not sure.
If the bootloader is unlocked and frp disabled it's a matter of hours and some "fastboot flash" before it will be fully functioning again, else i suggest to look in that topic and use dc unlocker as last resort.
let the phone drain the whole battery and then keep pressing volume down and connect it to pc,dont release the volume down till it opens to fastboot mode,if nothing happens in one try give it another shot,keep trying,it will work.thank you
I tried to downgrade from Android 11 to Android 10 a few months ago. Back then I had no knowledge about everything related to Bootloader Unlocking and other things.
I followed a tutorial. But my phone got bricked. So I followed an unbrick guide a few months later. I got it back to a state where I have basic Fastboot access.
But when I try to start the phone, is says Red State, Your device has failed verification. Incorrect Signature. Please download Image with correct signature or disable secure boot.
Now I don't have the Bootloader unlocked. I also can't do that with Fastboot. Results in the error that I am not permitted to do that. I also tried flashing TWRP but it says:
'download for partition 'recovery' is not allowed'.
Is there a way to get it working again? I would really need this phone again.
I have not made any backups. Also It says in Fastboot that my device is called: 0123456789ABCDEF. I dont think that is good because other phones I used fastboot on had a normal name.
J_029 said:
I tried to downgrade from Android 11 to Android 10 a few months ago. Back then I had no knowledge about everything related to Bootloader Unlocking and other things.
I followed a tutorial. But my phone got bricked. So I followed an unbrick guide a few months later. I got it back to a state where I have basic Fastboot access.
But when I try to start the phone, is says Red State, Your device has failed verification. Incorrect Signature. Please download Image with correct signature or disable secure boot.
Now I don't have the Bootloader unlocked. I also can't do that with Fastboot. Results in the error that I am not permitted to do that. I also tried flashing TWRP but it says:
'download for partition 'recovery' is not allowed'.
Is there a way to get it working again? I would really need this phone again.
I have not made any backups. Also It says in Fastboot that my device is called: 0123456789ABCDEF. I dont think that is good because other phones I used fastboot on had a normal name.
Click to expand...
Click to collapse
I'm dealing with that issue right now and my device won't even charge or turn on. Let me know if you find a fix. Did you try mtkclient already?
I have found a solution to fix red state. I also unlocked the bootloader afterwards and rooted the device.
The solution to fix red state is as following:
1. Go to: https://androidfilehost.com/?fid=2188818919693749336 and download the firmware (Its from FIH-Firmware.HikariCalyx.com Tutorial how to unlock bootloader)
2. Open SP Flash tool and load the firmware using the scatter file called MT6761_Android_scatter.txt
3. Select Format + Download and klick the download button
4. Now take your phone (Make sure to have it connected to a charger for over an hour bevore doing this, even tho the charging symbol might not show up) and hold down the volume buttons and while holding them, connect the phone to the pc using usb cable.
5. Wait for it to finish downloading.
6. When complete you should be able to start into fastboot. That can take up to one minute. Try putting the battery back in if it doesnt start after holding buttons over a minute.
7. When in fastboot, make sure the drivers are loaded. For this go into Device Manager. If there is an unknown device called Android, select update Driver > Search on my Computer > Select from a list. Then scroll down to TCL and then select Android ADB Interface. The device manager might tell you that it might not be the correct driver, but just continue.
8. Type into ADB and Fastboot window:
fastboot reboot recovery
9. When you see android laying on its back, hold power button and press volume up button (sometimes you have to press it 6 times), then the recovery menu should open up. Now select Wipe Data Factory reset. Select Yes and let it reset. After that start the phone again.
10. Your phone should start normal now. The startup can take up to 10 minutes. if it hasnt started after 30 minutes, repeat the procedure to reset it.
11. To get IMEI back, you have to unlock the bootloader and root the device. If you want to do that tell me. Its a bit complicated but i can tell you.
Make sure to follow the steps exactly
Thanks for the response, my device is a mt8163 and I have mtkclient if I can find the proper firmware what command would I use to flash the file