Related
How can this be fixed? I can still do the Vol Down + Power combination thing, but the phone will not load to my home screen via normal start up.
I have no idea how to fix this, seeing as it was caused by me applying a theme in Metamorph. I don't have SDK either...
I have a HTC Magic, 32B.
I'm trying to fastboot recover it right now, but even when my phone says FASTBOOT USB, the command prompt still says <Waiting for device>
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
First of all sorry for my english
I have bricked my inspire 4g eng s-off i was just trying to root my inspire 4g without unlocking bootloader noob i just know nothing about unlocking bootloader i used htc quick root software when the process start the software requested me an hboot image and unfortunatly i located to recovery image and phone turned off now when ever i try to turn it on it gives three vibrates vol down +pwr five vibrates please help m
volume up +voldown+pwr button five vibrates and a stable green led vol down +pwr three vibrates and red blinking led just pwr on button three vibrates red blinking led
If your bootloader wasn't unlocked, I don't see how you could have bricked it. Also, do you know if you had usb debug mode turned on? You couldn't have flashed an image with a locked bootloader and the scripts won't work either since the adb/fastboot utilities cannot talk to your phone if debug mode is off.
At any rate, pull out the battery for a few minutes, reseat the battery, connect the phone to your pc, hold down vol- and power and see if you can get to a bootloader screen. Even if it seems to boot but hangs at the green htc logo, you should still be able to issue adb commands and recover.
Once the phone boots, on your pc, open a command prompt and type the command "adb devices" without quotes to see if your phone is recognized. Let us know the status then.
turboyoshi said:
If your bootloader wasn't unlocked, I don't see how you could have bricked it. Also, do you know if you had usb debug mode turned on? You couldn't have flashed an image with a locked bootloader and the scripts won't work either since the adb/fastboot utilities cannot talk to your phone if debug mode is off.
At any rate, pull out the battery for a few minutes, reseat the battery, connect the phone to your pc, hold down vol- and power and see if you can get to a bootloader screen. Even if it seems to boot but hangs at the green htc logo, you should still be able to issue adb commands and recover.
Once the phone boots, on your pc, open a command prompt and type the command "adb devices" without quotes to see if your phone is recognized. Let us know the status then.
Click to expand...
Click to collapse
the bootloader was lock but eng s-off and there is is no adb no fastboot boot i have tried all methods putting battry out for 15 mints i have checked with another battery with no luck when ever i try to turn on my phone it give three vibrates and my pc recognize it as QUALCOMM DIAGNOSTIC 900e when i press vol down +pwr it gives three vibrates vol down +up+pwr five vibrates is there any way to flash the rom in qualcomm diagnostic mode and the usb debug was on last time kindly help me !!
Branded badmash said:
the bootloader was lock but eng s-off and there is is no adb no fastboot boot i have tried all methods putting battry out for 15 mints i have checked with another battery with no luck when ever i try to turn on my phone it give three vibrates and my pc recognize it as QUALCOMM DIAGNOSTIC 900e when i press vol down +pwr it gives three vibrates vol down +up+pwr five vibrates is there any way to flash the rom in qualcomm diagnostic mode and the usb debug was on last time kindly help me !!
Click to expand...
Click to collapse
Qualcomm mode is what happens when you hold volume down instead of up while booting. A common issue with the inspire is the volume rocker malfunctioning and becoming "stuck". Usually it is volume up that gets stuck. Either way you will have to probably repair the volume rocker by replacing it. With the age of the device though I don't think it's worth it to spend any money on repairs. It's almost 3 years old now. I know it seems concidental to happen at the same time your trying to unlock it but it can happen. If it is something that went wrong while you were trying to unlock it your pretty much in the same boat. If it only goes to Qualcomm mode there is nothing you can do.
Gizmoe said:
Qualcomm mode is what happens when you hold volume down instead of up while booting. A common issue with the inspire is the volume rocker malfunctioning and becoming "stuck". Usually it is volume up that gets stuck. Either way you will have to probably repair the volume rocker by replacing it. With the age of the device though I don't think it's worth it to spend any money on repairs. It's almost 3 years old now. I know it seems concidental to happen at the same time your trying to unlock it but it can happen. If it is something that went wrong while you were trying to unlock it your pretty much in the same boat. If it only goes to Qualcomm mode there is nothing you can do.
Click to expand...
Click to collapse
i have checked the volume rocker and replaceed it with no luck
Branded badmash said:
i have checked the volume rocker and replaceed it with no luck
Click to expand...
Click to collapse
Then something happened when you tried to unlock it. If you can't access the device via fastboot or adb then it is not fixable. Reflashing a boot img or hboot would be what you would want to do if you could gain access.
K got this HTC from a friend of me, was working before, had it rooted and fixed with custom rom
It was S-on on v1.27
k now gonna try to explain what's going wrong:
When i shut down the phone, put battery out, back in, connect to usb, i get the phone recognized by ADB (my HTC phone)
when i type adb reboot-bootloader, device responds and boots into fastboot mode
when i use vul up i get Fastboot usb on screen
from this point i can't get any further, device doesnt respond from any button action except for vol up.
Device is not recongized in windows now (windows 8 64bit) got the famous error 43
So in ADB everything is fine, but in fastboot nothing is working/responding
when i pull battery out, then put it back in, i can succesfully boot with volup en power, then i get everything running (custom rom from before) but it says safe mode
Any ideas what i can do to get this thing back on it's feet?
regards,
Robin
robin-sips said:
K got this HTC from a friend of me, was working before, had it rooted and fixed with custom rom
It was S-on on v1.27
k now gonna try to explain what's going wrong:
When i shut down the phone, put battery out, back in, connect to usb, i get the phone recognized by ADB (my HTC phone)
when i type adb reboot-bootloader, device responds and boots into fastboot mode
when i use vul up i get Fastboot usb on screen
from this point i can't get any further, device doesnt respond from any button action except for vol up.
Device is not recongized in windows now (windows 8 64bit) got the famous error 43
So in ADB everything is fine, but in fastboot nothing is working/responding
when i pull battery out, then put it back in, i can succesfully boot with volup en power, then i get everything running (custom rom from before) but it says safe mode
Any ideas what i can do to get this thing back on it's feet?
regards,
Robin
Click to expand...
Click to collapse
In bootloader(fastboot mode) no buttons will works except vol up,down and power..
If you want to flash a custom rom then
First goto bootloader
Now enter to recovery by using vol down and then power button to ok.
Place a Rom.zip in sdcard format cache/dalvik , all partition except sd and then flash rom..
ahsan64 said:
In bootloader(fastboot mode) no buttons will works except vol up,down and power..
If you want to flash a custom rom then
First goto bootloader
Now enter to recovery by using vol down and then power button to ok.
Place a Rom.zip in sdcard format cache/dalvik , all partition except sd and then flash rom..
Click to expand...
Click to collapse
problem was that none of the button's where responsive, i found the cause of this, volume buttons are damaged (the strip inside was broken)
So now i have a new problem much wurse i think
only power button works, so i did a complete reinstall with ruu, booted up fine, but always in safe mode for some strange reason,
Now after shutdown, i can't get the phone on anymore, only goes to Hboot, and there is nothing responsive, non eof the buttons work, can't use vol buttons because they are broken.
Adb is not responding either, only getting HTC Android USB device in my device list....
I think the phone is ready for trash? :S
robin-sips said:
problem was that none of the button's where responsive, i found the cause of this, volume buttons are damaged (the strip inside was broken)
So now i have a new problem much wurse i think
only power button works, so i did a complete reinstall with ruu, booted up fine, but always in safe mode for some strange reason,
Now after shutdown, i can't get the phone on anymore, only goes to Hboot, and there is nothing responsive, non eof the buttons work, can't use vol buttons because they are broken.
Adb is not responding either, only getting HTC Android USB device in my device list....
I think the phone is ready for trash? :S
Click to expand...
Click to collapse
in bootloader adb doesn't work only fastboot
so when you are in hboot screen try this command
fastboot reboot (in the hboot screen should say fastboot usb)
rzr86 said:
in bootloader adb doesn't work only fastboot
so when you are in hboot screen try this command
fastboot reboot (in the hboot screen should say fastboot usb)
Click to expand...
Click to collapse
can't get into adb anymore so i think the phone is dead unless we repair the volume buttons right?
robin-sips said:
can't get into adb anymore so i think the phone is dead unless we repair the volume buttons right?
Click to expand...
Click to collapse
since you are dealing with a hardware problem then yes
but try this
boot normally(even on safe mode)
connect it to pc and type
adb reboot bootloader
it will take you directly into fastboot mode
then type fastboot reboot
see how it goes and check volume button from there(to confirm the hardware issue)
otherwise repeat the procedure but instead of fastboot reboot run the ruu.exe again
Hi. someone if he can help me how to factory reset htc one s. When turn on phone i have only htc screen with red text "This build is for development purposes..." It's the same when i try hold power + volume down or volume up...can't load to fastboot or recovery mode, again i get red text. If anyone have a solution how to instal official or custom firmware (ROM). :crying: