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
Hey guys! I just got a One X from AT&T bought on eBay, although I live in Europe.
I managed to unlock the bootloader by changing the CID to 1111111 etc. (how many 1's?) and it worked fine.
I then ran installed ClockworkMod Touch Recovery for the HTC One X through terminal and it was a success.
I rebooted by holding down the power and volume down, and attempted to boot into recovery. I got a white screen with the HTC logo, and red text underneath saying something like "do not use this without HTCs permission" or something of the sort. The phone then turned off.
NOW I'm trying to boot again into the bootloader (I think that's what it's called, but by turning it off and holding the volume down and power key) and it just doesn't work. I've tried a million times, with different variations of holding down the keys. What happens is the light on the touch keys at the bottom flashes a bunch of times, then it boots normally. Everything works on the phone otherwise.
I tried to do it via fastboot/terminal by issuing the command ./fastboot-mac reboot-bootloader but it just says "waiting for device..." even though it's connected.
Anyone had this problem and found a solution?
Recovery
Clockwork recovery is not supported on the evita. Download goo manager and you should be able TWRP from that. And then you can reboot into TWRP.
I think you flashed CWM for the international (Tegra3 quad core) One X. Install TWRP as previous poster recommended.
There is no version of CWM Touch Recovery that is supported for the AT&T One X. You flashed the international version. Fortunately, you can flash TWRP right over it inside Goo Manager.
Be thankful you didn't flash it inside ROM Manager or you could have bricked your phone. I've seen people do it in the past.
ansedve season
Thanks guys, and glad I didn't brick the phone!
I installed Goo Manager and installed OpenRecovery Script, and managed to attempt to go into recovery, but again got the white HTC screen and something about "development purposes only" in red text.
I think I'm really lost on this one, any help would be great, like a link to a tutorial?
in fastboot run this command "fastboot erase cache", then boot into recovery.
DvineLord said:
in fastboot run this command "fastboot erase cache", then boot into recovery.
Click to expand...
Click to collapse
Don't be too concerned with the blah blah in red writing about development version etc. on the boot screen - you get that boot screen when you unlock the bootloader.
mollysue said:
Thanks guys, and glad I didn't brick the phone!
I installed Goo Manager and installed OpenRecovery Script, and managed to attempt to go into recovery, but again got the white HTC screen and something about "development purposes only" in red text.
I think I'm really lost on this one, any help would be great, like a link to a tutorial?
Click to expand...
Click to collapse
What did you do in recovery? Did you flash anything? Does the phone not boot up now?
Thanks guys for all your help. I guess know I technically know what to do to fix things, thanks to you. The only problem that after probably over 100 failed attempts I cannot boot into recovery. I tried all variations of holding the power and volume down button while restarting, rebooting, turning on/off or up/down sideways but it just boots normally every time.
This means I can't use fastboot etc. I guess unlocking the bootloader and voiding the warranty was for nothing
If you know another way to reboot into bootloader other than the hardware buttons method let me know!
Believe it or not, I think you are just performing the button presses incorrectly, if you can't access the bootloader. Bootloader is probably still intact, otherwise the phone would not be working at all.
1) In Settings>Power, make sure "fast boot" is not checked.
2) Then power the phone off fully, but holding the power button until the power menu comes up, and select "Power off". Wait a minute for the phone to power off completely.
3) Hold down the volume down rocker. DO NOT release it until I tell you to later.
4) Press the power button for 3 seconds, then release. DO NOT release the volume down rocker.
5) Once the white bootloader screen shows up, release the volume down rocker.
Alternately, you can do this:
a) With the phone powered on, hold the power button until the capacitive buttons flash (about 5 seconds).
b) The moment the screen goes black, hold down the volume down rocker, (again, DO NOT release it until the bootloader screen comes up) but release the power button.
The timing for this method is a little trickier, if you press the volume down rocker too late, it will boot normally (or safe mode), and too soon, and it just reduces the ringer volume and the phone stays on. But as long as you press and hold volume down the moment the screen goes black, it will work.
---------- Post added at 10:13 AM ---------- Previous post was at 10:11 AM ----------
But also, I would still not recommend trying to boot into recovery until you have installed the TWRP recovery as mentioned previously on this thread, if you have not done so already. There is no CWM Touch Recovery for this phone, so I'm pretty certain you installed in improper recovery on the phone, and recovery will not function at all.
Alternatively, you can go into Goo Manager and select the "Reboot Recovery" option, which should get you into TWRP
Or from command prompt "adb reboot bootloader" so long as you open your prompt from your adb application folder.
Or alternatively skip the middle man: "adb reboot recovery"
I really think your problem lies with your button pressing -- follow instructions on the previous post and you should be home free.
Well I actually eventually managed it! I think the volume button was a bit stuck because it still takes a few tries to boot into bootloader, but eventually I managed it and am in the TWRP menu right now!
I did a little victory dance when it happened. Thanks again!
My phone is stuck at the boot logo, and won't fully boot. The boot with the volume down button pressed doesn't work, or even the volume up thing, in order to enter fastboot I need to let it boot up to the logo then run the
Code:
adb reboot-bootloader
command. when i try the
Code:
adb reboot recovery
command, it boots to the oneplus logo, then reboots normally, and I am back to where I was. I cannot flash a new image, because my bootloader is locked, and in order to unlock it, the phone needs to boot up. Is there a way to unlock the bootloader without a full boot? Can I flash without an unlocked bootloader? Is it bricked? please, any feedback would be appreciated.
Beast_Boy said:
My phone is stuck at the boot logo, and won't fully boot. The boot with the volume down button pressed doesn't work, or even the volume up thing, in order to enter fastboot I need to let it boot up to the logo then run the
Code:
adb reboot-bootloader
command. when i try the
Code:
adb reboot recovery
command, it boots to the oneplus logo, then reboots normally, and I am back to where I was. I cannot flash a new image, because my bootloader is locked, and in order to unlock it, the phone needs to boot up. Is there a way to unlock the bootloader without a full boot? Can I flash without an unlocked bootloader? Is it bricked? please, any feedback would be appreciated.
Click to expand...
Click to collapse
So you can't boot into fastboot with the power + volume up button combo after shutting the phone down (hold power)? No you can't unlock bootloader without successfully booting into fastboot. No you can't flash without unlocking the bootloader.
Heisenberg said:
So you can't boot into fastboot with the power + volume up button combo after shutting the phone down (hold power)? No you can't unlock bootloader without successfully booting into fastboot. No you can't flash without unlocking the bootloader.
Click to expand...
Click to collapse
i can only turn the phone on in the normal mode. does this mean it's bricked? do I have to send it in?
Beast_Boy said:
i can only turn the phone on in the normal mode. does this mean it's bricked? do I have to send it in?
Click to expand...
Click to collapse
I would think it's bricked, it's virtually impossible to brick this device. So it'll turn on when the power button is pressed, but it won't actually boot, right? Nothing at all happens when using the fastboot button combo? A little background info would be good, what lead to this situation?
Heisenberg said:
I would think it's bricked, it's virtually impossible to brick this device. So it'll turn on when the power button is pressed, but it won't actually boot, right? Nothing at all happens when using the fastboot button combo? A little background info would be good, what lead to this situation?
Click to expand...
Click to collapse
The button combos do nothing, not even boot the device normally.
So, what happened is this: I was trying to root my phone, I plugged it into a windows 8.1 machine, and I was following a tutorial by C4Etech. It was working fine, until I unlocked the bootloader, after the it was unlocked, my machine could no longer recognize my device. I uninstalled and reinstalled countless drivers multiple times in an attempt make my machine recognize my device, rebooted my phone, my computer., the adb server, and anyhting else I could. Nothing worked. Angry and frustrated, I plugged it into my Linux Mint machine, and it recognized perfectly! because I am a noob, and have never done anything like this before, I began to panic when I saw that my phone wouldn't reboot like they did in the tutorials right after they unlocked the bootloader, so I skipped that part, and continued with the flashing. after flashing, my phone would no longer boot, so I thought I messed up with the unlocking portion because my phone wouldn't reboot after the "fastboot oem unlock" ( because I am a noob, I thought that the unlock was temporary, and that my many reboots of the phone managed to undo it.). thinking the unlock was the culprit to my broken phone, and thought adb must be glitched since it doesn't reboot after "fastboot oem unlock" like it did in the tutorials, like a genius, i typed in "fastboot oem lock" rebooted into fastmode, then typed in "fastboot oem unlock". I was filled with joy when I saw my phone reboot like it did in the tutorials, but my joy began to fade, as the phone was still booting after several minutes. And thats when I died inside, and began posting on many online forums, because google couldn't find anything that matched my situation.
the button combos stopped working after the flash.
Beast_Boy said:
The button combos do nothing, not even boot the device normally.
So, what happened is this: I was trying to root my phone, I plugged it into a windows 8.1 machine, and I was following a tutorial by C4Etech. It was working fine, until I unlocked the bootloader, after the it was unlocked, my machine could no longer recognize my device. I uninstalled and reinstalled countless drivers multiple times in an attempt make my machine recognize my device, rebooted my phone, my computer., the adb server, and anyhting else I could. Nothing worked. Angry and frustrated, I plugged it into my Linux Mint machine, and it recognized perfectly! because I am a noob, and have never done anything like this before, I began to panic when I saw that my phone wouldn't reboot like they did in the tutorials right after they unlocked the bootloader, so I skipped that part, and continued with the flashing. after flashing, my phone would no longer boot, so I thought I messed up with the unlocking portion because my phone wouldn't reboot after the "fastboot oem unlock" ( because I am a noob, I thought that the unlock was temporary, and that my many reboots of the phone managed to undo it.). thinking the unlock was the culprit to my broken phone, and thought adb must be glitched since it doesn't reboot after "fastboot oem unlock" like it did in the tutorials, like a genius, i typed in "fastboot oem lock" rebooted into fastmode, then typed in "fastboot oem unlock". I was filled with joy when I saw my phone reboot like it did in the tutorials, but my joy began to fade, as the phone was still booting after several minutes. And thats when I died inside, and began posting on many online forums, because google couldn't find anything that matched my situation.
the button combos stopped working after the flash.
Click to expand...
Click to collapse
Have you seen this?
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Might be worth a try.
Hi I'm hoping someone can help or at least point me in the right direction if i've missed a thread, i'm on Windows 7 64bit.
I appear to be stuck in a boot loop on my original Shield Tablet, stuck on nvidia screen when i try to go into recovery mode i get the "dead android" picture.
I have tried to unlock the bootloader and i get FAILED <remote: <>, device shows up under fastboot devices command, device shows up as Android Bootloader Interface in Device Manager.
I've searched the forums and seen this problem but everyone else seems to be able to unlock easily, this is the same but no replies https://forum.xda-developers.com/shield-tablet/help/nvidia-shield-unlock-bootloader-failed-t3178865.
Any help anyone can give me would be appreciated. Thanks in advance.
Check the recovery images section for your device here: https://developer.nvidia.com/shield-open-source
Instructions to unlock the bootloader:
Unlocking the Bootloader
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
Click to expand...
Click to collapse
You need to already have adb set up and the Shield connected to the PC to do this. If you don't have USB debugging enabled, this may not be possible, but you should still be able to get into recovery by booting the tablet with Vol- and power button (hold volume - and then just press the power button, don't hold both at the same time).
Yes I've tried that (I know the steps of unlocking the bootloader) that's when i get the FAILED error. When I try to enter recovery I get the "dead" Android picture.
Ok Guys So I Shouldn't Have Done This But I Used Fastboot To Flash Recovery And I think I Did It Wrong. It Said "ok" And Finished And I Rebooted Phone It Resetted And Then Stuck On The Orange State Bootloader Message. I Do The Recovery Mode And Goes Black And Nothing Is Responsive For a While, Sometimes Longer Than Others. This Happens If I Start Phone Normal Or Try Fastboot Or Download.
Because Of My Mistake I Cannot Connect To Pc Software And Im Not Sure Of What I Can Do. I Feel Like Im Not Going To Like The Answer For This But I Got To Take The Blame For This.
Btw i Have A Samsung galaxy Note 20 Ultra Sm-N986u
I think your phone is hard bricked
so you can't get fastboot using volume up+power or via adb?
rescue from manufacturer site pos or just device not being recognised?
It isn't hard bricked it's just way of Samsung trying to make life of simple people more difficult, people who paid for Samsung phones lots of money.
To sort that screen issues what you can surely do is,
Simply press volup + voldown buttons at the same time, no matter if you're on that orange screen or whatever just press those those two buttons at the same time and keep pressing them while you connect your phone to pc. you will boot into download mode. Then flash stock firmware for your phone. After stock of flashed Reboot and start your phone, go to developer options see if oem unlock option is there if it is then oem unlock it if it is not then go back to settings manually change date to year ago, then go to updates disable auto update, connect to WiFi, and press on update several times untill window shows up saying no updates, then go to developer options you should see oem unlock, unlock it.
Then boot into download mode and make sure you have working copy of recovery.
And make sure you follow instructions of whoever recovery you installed on how to boot into recovery. I have S20 plus and too had troubles with it, and the only working recovery for my phone is twrp customised. To boot into it after flashing recovery from odin auto reboot disabled I pressed voldown and power, USB cable connected, then after screen goes off I changed from voldown to volup while kept pressing power button and cable connected. Orange screen with warning showed up for 5 sec I kept pressing and it bottled to twrp and then I was able to install custom rom beyond rom and while installing in aroma I was able ti choose option to remove orange screen.
That's it.
I ran into the same error. I mistakenly loaded twrp's recovery into userdata instead of ap section. The phone was stuck at the orange screen and nothing was happening whatever i pressed. I waited till the battery to dry out and with 0% battery, i directly connected to pc and was able to get into download mode. Then i flashed stock and everything is now back to normal.
Carl Johnson (Cj) said:
I think your phone is hard bricked
Click to expand...
Click to collapse
Absolutely not