I recently tried booting using what turned out to be a bad SD card image. At the time it got as far as the ANDROID block letters on the edge of the screen. I took the SD card out but then realized I had no way to reboot it: the power button did nothing and I couldn't pull the battery like on my Droid. At first the only option I could see was to wait a day or two until the battery ran down. Now, I know nothing about adb except what I did to get the market added to froyo but I did remember that it ended with an adb reboot command. I tried that, my NC rebooted and all is good.
So I'm wondering what options exist when the device doesn't boot?
- adb reboot (may not respond and probably of little use if EMMC boot is bad)
- ???
Make a bootable sdcard with CWR on it. Then no matter what state the device is in if you put the bootable sdcard in the device and power on it will boot into CWR so you can do whatever is needed to get yourself back up and running again in short order
But what if the device is already on like in my case? Other than adb reboot (which may or may not work) there's no way to force a reboot, or is there?
FYI you can always turn the device off no matter what. Just hold the power key for about 10 - 15 secs and no matter what states you are sitting at it will force it to power down. Just like a comp when you hold the power key down for an extended amount of time it will in fact power off.
On another note depending on what recovery you have on the device if it does get stuck and you force it to power down like I just mention you can boot into ( CWR ) recovery mode and from in there there is a reboot option also. Again tho that would only work if you have CWR installed on the internal memory.
I did hold the power button down for fairly long time. Apparently it wasn't long enough.
I just have the rooted stock 2.1 internally. Don't know what, if any, recovery that gives me.
So much to learn, so little time...
lol.... I hear ya there. Been messing with Android phones for ages now but a new learning curve when it comes to the Nook with so many different options we have to choose from. BTW I have had it to where I had to hold the power key down for over 30secs to get it to power down just so you know. If you run into the issue again for sure just keep holding it and it will power down at some point.
Good to know. Thanks.
Related
Does not work for me anymore, and figures I find this out when I get a bootloop.
So yea basically I keep getting clear storage popping up, but after countless attempts and even holding home once I get passed clear storage it stays on the htc logo until I eventually release it and then it tries to boot the phone.
Of course the usb isn't enabled at that point too so I can't connect through adb. I don't know why it won't let me go into recovery but...
Pull Battery,
Volume down + End key
Home key
Your in Recovery
Unless I'm missing the point of this thread?
Correct me please.
Ah thanks.
Yea it suddenly started working again, but I swear home+power stopped working for like 20 tries or something.
Weird stuff but I'm all good
So.... Been playing with this for the last two days trying to root this phone.
I've rooted a few other phones, so I do have experience with the overall process, but I am unable to even boot this phone into Recovery. I have tried booting into recovery by holding down both volume buttons + power and from adb terminal "adb reboot recovery."
Neither method works. The phone will boot (or reboot from adb) and brings up the "at&t World Phone" screen and then nothing else appears. The first time I tried this it actually wouldn't boot up even after pulling the battery and trying to start normally, it still sat at the same screen. I let it sit all day today at the screen until the battery died. I was finally able to get it to boot up earlier.
If anyone can help, that'd be greatly appreciated. Let me know what info I need to add.
I usually just press and hold both volume buttons and power then release just the power button and keeping the volume buttons still pushed on the 2nd time the white at&t screen pops up... Works for me every time.
Sent from my SAMSUNG-SGH-I897 using XDA App
hold volume up+down and power key btw this is wrong section to post supposed to be in general
Oh sorry, didn't realize it was supposed to be posted in general.
I've tried the Volume Up/Down + Power and this does not work, as I stated originally.
I've also tried to do it from the adb shell, which also does not work.
Does anyone have any idea why I can't access recovery?
I"m having a similar issue. Holding volume up+down and power and releasing in any combination just boots the phone up. If I just hold volume up+down and power the phone alternates between the AT&T World Phone screen endless.
Yes u have to let go of the pwr button when the phone screen turns on
Sent from my SAMSUNG-SGH-I897 using XDA App
I've tried just about every combination of the Volume Up/Down + Power and no luck.
I've also tried the following ADB commands, with no luck, it just reboots the phone:
adb reboot recovery
adb reboot-boatloader
When I hold Volume Down + Power I get the a Yellow Triangle with a Android guy with a shove with the text "Downloading... Do not turn off Target!!!"
When I hold Volume Up + Power I get an Android guy with the following text: "POWER RESET or UNKNOWN UPLOAD MODE"
For kicks, I tried to to flash a rooted update.zip via the Volume Down + Power way with the Samsung update software, the same way I have done with the Samsung Moment. Wasn't sure if it'd work, but worth a try.
Any one else have any ideas or suggestions?
Phishie, do you have a final release version? Or anything special about the phone you have?
I just press the two volume buttons first (to make sure theyre pressed before you hit power), then press the power button, as soon as the screen turns on, I let go of everything and it works just fine, no need to have ridiculously complicated instructions.
The trick is to make sure both volume buttons are pressed BEFORE you hit power. Then release. Easy as pie
Also, if you guys are having too much trouble, just download the one click root/unroot. It will run, boot your phone into recovery, then all you have to do is scroll to install packages with volume key and hit power. Done.
Trust me, I am making sure I'm pretty the keys completely. I've literally tried it fifty times by now.
And I've also tried the One Click Root. This does not boot the phone into recovery either. It just sits at the AT&T World Phone screen forever and will actually get stuck here and will not boot up normal even by pulling the battery and powering it back up. It'll just get stuck at the for-mentioned screen. I have to connect it to adb and reboot it there to get it out of the loop it's stuck in.
that doesnt sound good. Maybe you need to try a factory reset? are you running stock rom and everything?
When I first got the phone I did a factory reset.
Yea, it's completely stock to my knowledge. But I have a different ROM than the final release version that everyone else has. This is a pre-production device.
same problem
I try all the combos as well, no luck, would the combos be different for 2e vs 3e recovery?
I try combo, it powers on, the same thing happens, the at-t comes up, goes for a second, then screen brightens, wait a bit and then the home row buttons light up, hangs there... doesnt matter which kernel or which rom I flash, same thing, adb and other stuff wont work as they need usb debugging enabled, which mine isn't.
Is there a way to mod the phone files and flash to enable usb debugging? Anyway to remap the buttons to 2 button vs 3 button?
Everyone post your methods for entering recovery please?
My NC will no longer turn on AT ALL -- doesn't even flash the screen -- after maybe about the 4th boot of the Froyo on eMMC install I put on there. It's not my hacking it, that would make no sense as it booted several times before just failing when I rebooted it with ADB after deleting the YouTube app. I think somewhere in there something connected to power just failed. But I suspect if I get it warranty replaced B&N will just blame my rooting it rather than finding the actual cause of the problem.
So I want to know if the extended warranty is just a "no questions asked" type, because that would be helpful in getting my device fixed!
If it won't turn on at the store, they can't check. However this isn't 100% ethical, as you did make major changes, which could be at the heart of this.
Can you boot from sd at all?
Sent from nookcolor
I'd say go for it, companies shouldn't get mad at us for doing what we want for the device that we bought.
...But this isn't really the best train of thought for this situation because you want to get another one or your money back xD
Had this same issue earlier. Have you tried booting without the sd card? Plug it into your computer, and see if it shows it as connected, hold down power and try it a few times.
Sent from my LogicPD Zoom2 using Tapatalk
Had this happen to me also. What I did was burn the ClockWorkMod to your SD card, also copy the factory boot.img and system.img file from the [ADV][DEV][STOCK IMAGE]Nook 1.01 stock dd images thread in development. Put it into your Nook, connect the USB cable to your computer and then hold the power button for about 20-30 seconds. It should flash to life, at least mine did. Once it comes up use the volume buttons to scroll down to the mount and storage option. use the "N" button to click it, then click on the mount /system option, then format /system option. then the same for mount /data, then format /data. Finally mount /sdcard, then on your computer using adb, use the adb shell command, and then use the 2 dd command from the thread mentioned above.
Rebbot after that and remove the sdcard, then do the power + N reset and the 9 reboot thing and you should be back at stock.
Hope that helps.
Turned out to be that whatever was broken installed on the eMMC had caused the device to be turned on, with the screen off, but entirely unresponsive to the buttons. I brought it into B&N and managed to get it to power on once with the battery nearly depleted. Then I recharged it, rebooted it and it went black and unresponsive again. They swapped it for me with about 10% battery left. So what will happen is: it will get to the depot with no battery left, they'll power it up, flash it, and it will go to some other deserving customer
When I tried to disable the voodoo lagfix my phone froze, after about 20 minutes i decided to pull the battery and now the phone freezes when trying to boot and even after plugging in the charger, it freezes on the battery load symbol. Unfortunately, the 3 button way to get to the recovery menu doesn't work. help me please??
I'm having the same problem - phone just hung on the kernel load screen (firebird 2) after trying to shut off lagfix - although I can get to a red recovery mode menu. Not that it's helping at this time. It would be nice if I could recover without a clean wipe of the phone.
Anyone have any ideas. I'll be scouring the threads...
You could try making a jig and flashing to stock http://forum.xda-developers.com/showthread.php?t=841512
how are you getting to the red recovery menu?
i have the same kernel and i'm running the firefly 1.5 rom
I can't boot into anything and the only solution i have so far is to make a jig or buy one and not have a phone for a little bit, which is going to suck..
I've tried the following combinations, just because I know people are going to ask.
1. take out battery, sim, etc.
2. leave out for about 15 seconds
3. plug in the battery, plug in usb and hold two volume buttons-> freezes while trying to load battery status
3.b same precedure as above except plug in usb first hold volume buttons then battery-> still frozen
3.c hold volume buttons, battery, then power button, let it cycle atleast 2 times and let go of power at att logo while holding the volume-> frozen at kernel loader
3.d same as above but with only one volume button at a time, both up and down-> no cigar
3.e all the precedures above while wildly pressing all the soft keys (home, search, yadda yadda) out of frustration -> thinking, gosh i'm screwed
did i miss out any secret other combinations or methods known to work?
I'd really like to do this without hardware, but making a jig kinda sounds like a fun project and i do have a soldering iron in storage somewhere...
xsamxoxo said:
how are you getting to the red recovery menu?
i have the same kernel and i'm running the firefly 1.5 rom
I can't boot into anything and the only solution i have so far is to make a jig or buy one and not have a phone for a little bit, which is going to suck..
I've tried the following combinations, just because I know people are going to ask.
1. take out battery, sim, etc.
2. leave out for about 15 seconds
3. plug in the battery, plug in usb and hold two volume buttons-> freezes while trying to load battery status
3.b same precedure as above except plug in usb first hold volume buttons then battery-> still frozen
3.c hold volume buttons, battery, then power button, let it cycle atleast 2 times and let go of power at att logo while holding the volume-> frozen at kernel loader
3.d same as above but with only one volume button at a time, both up and down-> no cigar
3.e all the precedures above while wildly pressing all the soft keys (home, search, yadda yadda) out of frustration -> thinking, gosh i'm screwed
did i miss out any secret other combinations or methods known to work?
Click to expand...
Click to collapse
I'm afraid not. This happened to someone I know and they told samsung the OTA update bricked it and AFAIK they fixed it for free. They never tried using a jig though, so if you don't want to wait to replace it or anything you could try a jig since it might work and the parts are pretty easy to get (and if you'd be replacing the phone, a jig is ALWAYS good to have anyway)
Just another note to throw in there, the computer recognizes the phone, but strangely my computer freezes while trying to read the media storage drives. I can't tell if the internal sd is mounted because of the ever-lasting wait but i'm almost positive its not.
Do adb commands work?
Sent from my SGH-I897 using XDA App
Thnikk said:
Do adb commands work?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
nope, it says "error device is offline"
You could try ... when the phone is booting and trying to catch it before it freezes is spam the heck out of the command adb reboot download then after hitting the enter button hit the up arrow and keep repeating until either the phone a) hopefully goes into download mode or b) freezes and throws the error.
Who knows.. might get lucky.
avgjoegeek said:
You could try ... when the phone is booting and trying to catch it before it freezes is spam the heck out of the command adb reboot download then after hitting the enter button hit the up arrow and keep repeating until either the phone a) hopefully goes into download mode or b) freezes and throws the error.
Who knows.. might get lucky.
Click to expand...
Click to collapse
it connects even though the phone is frozen. I'm heading over to "The Shack" pretty soon and just making a jig.
Thanks for all your help everyone.
Edit: Just confirming that with much dedication and a steady hand I finally have my captivate up and running with the help of the resistors. I also flashed the 3 button fix stock rom.
Well, I kept trying the least invasive methods first. Tried to reflash Firebird. Then went adb and such. In the end, it was pretty clear that it had hung at the lagfix correction, and I was dealing with a file system error. I was eventually able to get into download mode. The hardest discovery was finding that I had gotten the wrong drivers from samsung. The ones in the [stock rom] odin master clear page were what I should have been using. When I loaded those, the computer recognized that I had a phone and not a "serial gadget" and then I knew I was close. Odin finally saw the phone, and a couple tries at "light" re-stocking failed at file analysis, so I did the repartition (aha, file system error), and it shot through the whole process and I had my phone back and flashed to Serendipity in about 20 minutes.
But I would like to know about the red menu. That was unexpected (blue for standard, green for cwm).
No need for a jig. I had access to some phone functions, most importantly, download mode.
So I tried to safestrap cm10.1 onto my Droid 4. But, I was much more familiar with a previous version, not with the touch interface and stuff. I did what I thought I had to do: Create a partition, install the zip to it, reboot.
But, to my horror, when I rebooted, I was greeted with a black screen (backlit). I couldn't turn off the phone by holding down the power button either. I had this problem once with my Droid 3, and I 'solved' it by just taking the battery out. But I know things are much more 'locked-down' back there with the Droid 4, so I didn't want to do that.
After a little while, the thing just ran out of batteries. I was hoping to charge it up again. When I plugged it into a wall, I got the little battery icon, which I thought was definitely good news. But now I can't even turn it on, or get my computer to charge it!
UPDATE: I'm going to try using fastboot
Have you tried booting into fastboot and then flashing the stock firmware to the phone?
Also to reboot the phone when it freezes, you can hold the power button and volume down together for about 10 seconds.