Related
I've heard about how it's pretty much impossible to brick the nook... Mine seems about as useful as a brick though. I was trying to set up a dual boot following these instructions. Basically, I had HC installed to the internal memory. backed it up, formatted system and data, then flashed update-nc-stock-1.2. CWM said that was successful. Then I rebooted with my CWM SD card out. Screen said "read forever" or whatever, then went blank. I waited for about 5 minutes, and pressed the power button. The screen went from an 'on' blank to an 'off' blank. Since then, I haven't been able to get it to turn on at all. Just an 'off' blank screen with no signs of life, even with charger cable connected. Tried it with CWM SD in and out. None of the buttons seem to do anything...
Thanks in advance!!
I'm pretty new to the Nook having just got it today, but I did some reading prior to attempting anything to see how easily I could back out if I had to.
Have you tried basically starting over (ie. Let go of the multi-boot dream for a bit and get back to basics)
You know, take a SD card, use diskimager to put the clockwork 3.0.2.8 image on it with the CM7 full ROM and boot to that, then format system, data and cache with clockwork and finally install the CM7 zip image (and gapps I guess) just to get going again.
If it all works, maybe take another run at whatever you are trying to do with the multi-boot stuff.
Thanks for the reply.
Sounds awesome; problem is I can't get the thing to do ANYTHING. boot period, into recovery or otherwise. I plug it in and it displays nothing - no 'wait 15 minutes and try again'. Just a black screen no matter what I do. I have an SD card with recovery on it, and i've tried making it do something with or without the SD card. No luck.
Good luck with your nook; I had really been enjoying mine.
So holding the power button for 10-15 seconds doesn't do anything?
Or when you plug in the power does it try to boot?
I mean in a complete worst case scenario you could grab yourself a T5 and open it up, disconnect the battery, and then reconnect it.
Then something is wrong with your Recovery SD card, as no matter what, hardware dictates that it reads the sd card first. The problem with what you did through dual boot methods is you resized partitions. So even if you do back out of all of this, you're going to be losing space unless you setup dual boot.
Recreate the CWM recovery card, either redownload the image and reburn it. Find a different one or something else, because it should load on startup.
Thanks for the help!
Reformatted SD again, then tried powering up with the power cord unplugged. Apparently it won't boot into recovery as long as the power cable is in, and whatever the boot was on EMMC was messed up. Happily running stock 1.2 now, next step, dual boot with HC!
Anyone know how I can delete this thread as it's pretty unnecessary?
The Device:
Nookcolor Refurb - came with stock 1.2 installed. Rooted with CM7 - initially had boot partition problems and went back and did the fix for it. (was using an old CWR, so had to redo that, too). Worked mostly fine for a few weeks. Had a little trouble installing the recent cm7 stable update. But after clearing and redo, no problems. Then I updated Adobe flash to 10.3 through the market. bad, bad, bad. (I've discovered). It has gone into a bootloop, but it doesn't even get in far enough to bring up CWR either internally or on a bootable SD card. It brings up "loading" - whether in CM7 or CWR - then shuts itself off. I have tried the 3 button salute and 8 interrupted boots, but neither works in any way. Is there something else I can do?
Also, a side note, the device will not charge to green light - even if charging overnight. At first I thought it was a battery issue, but after a day of combing the boards, I'm thinking bootloop from hell.
Help!!!!
Are you running CM 7 internally or from a card? If internally, try making a bootable CM 7 card and booting from that.
I am running it internally. The device will not boot from a card or internally. It doesn't get far enough into the boot before it loops for CWR to start up - either internally or off the sd card. I can get to the boot menu (hold down n when it starts up), but it doesn't boot off any of the options there, just goes to black screen.
What happens when you do the 8 failed boots?
Nothing really happens with 8 failed boots. I think it terminates the boot process before it gets far enough along for it to "count". Loading comes up, I count one thousand one....all the way to one thousand seven. Then it shuts off, often reboots itself. Same deal with CWR. Loading comes up, count to 7, shuts off. I can get to the boot menu in CM7, but I it doesn't respond when I request any type of boot from anywhere. Either hangs or restarts.
I'm trying ADB, but it won't stay connected. Flicks on right at the end of the loading process and then shuts down. It really sucks.
Shelly, shoot me a pm... i'll give ya my phone number and we'll work on getting it going.
Sorry if this is redundant, but in very basic troubleshooting have you tried charging your Nook? It probably is more complicated/serious than a low battery, but it wouldn't hurt to rule it out.
I finally did get it to charge to green light. Didn't make a difference. I can get it to hang sometimes when it's trying to get into CWR. And it will stay on the Boot Menu.
Just a side note, I have another NC that I've had since Jan. Autonootered, Manual Nootered, CM7ed, brought back from the dead many a times.
Dizzy Den - am shooting you a message shortly. Thanks.
Has this been solved? If yes how?
Could you find a solution to your problem?
I'm having the same issue now. Bought a Nook Color in November, Autonooted, flashed recovery from ROM Manager, flashed CM 7.1.0 internally from downloaded ZIP files via ROM Manager, was working just fine for a week, stable, fast, perfect. Overclocked to 1200 MHz after a few days which made the experience even nicer.
Then installed and started Google Maps which didn't work - the Nook turned off on launch of Google Maps app.
I had set Wifi to "stay on all the time" beforehand (which might have been bad because it creates Sleep of Death syndrome as i now know).
Now when i turn it on it shows "Loading" for 7 seconds and then the screen turns off. This is when booting CM, when booting the internal recovery (shows "loading recovery" for 7 seconds) and when booting from any SD card image (i've tried at least 10 different bootable SD card images, different cards and different card readers).
It recognizes and tries to boot off SD cards - i get different "Loading" screens depending on the image, honey-colored for a honeycomb image, with two skulls for a recovery, ... So that works.
The nook seems to be in some kind of "on" state because i need to hold the power button to turn it off before i can get it to boot again.
I can get to the boot menu as you could, but booting from there doesn't do anything at all. So the hardware seems to be OK because the boot menu itself works well and for more than 7 seconds.
I can charge it and it goes to a green light so it's no battery issue.
The nook does not show up on USB - well once it did for a second but that was it.
I even tried to let the battery run completely empty so internal registers can get reset - didn't change anything.
Help! Is it bricked now?
Going to a B&N store isn't an option btw - the next one is 6500 km from here.
(This is the first time i ever ask for help on a forum. I am running a ZTE Blade with CM7 just fine, and I've been stuck often enough but always found a solution myself...)
Gunnar
Have you guys tried this:
http://forum.xda-developers.com/showthread.php?t=1308304
Or completely restoring it to stock:
http://mrm3.net/nook-color-recover-any-bricked-device/
Tried, can't get far enough
Kingdruid, thanks, yes i've tried both of those links - sadly they don't help at all because i can't even boot SD card recovery images...
I tried various recovery images including the newest clockworkmod, but i am still stuck They all work for 7 seconds only.
So yes, a nook can actually be bricked it seems.
G.
tralulu said:
Kingdruid, thanks, yes i've tried both of those links - sadly they don't help at all because i can't even boot SD card recovery images...
I tried various recovery images including the newest clockworkmod, but i am still stuck They all work for 7 seconds only.
So yes, a nook can actually be bricked it seems.
G.
Click to expand...
Click to collapse
When you overclocked it, did you notice it getting hotter than usual? I wonder if it was due to the overclocking. All the users I see with unrecoverable nooks is after they overclocked.
No, i did not notice much heat. And it was working well in its overclocked state for a few days.
Do you think it's CPU is fried now?
tralulu said:
No, i did not notice much heat. And it was working well in its overclocked state for a few days.
Do you think it's CPU is fried now?
Click to expand...
Click to collapse
I own 4 of them so I would prefer the term "Unbrickable", but at this point I'm not really sure.
Try 8 failed boots and see if you can get into recovery to reset to factory.
cant get it working
so first noob post
i used this thread to root my nook color
http://forum.xda-developers.com/showthread.php?t=1000957
problem is i have followed the steps and re done it about 5 times and every time i turn on the nook it goes right to read forever and runs the stock OS
nook 1.2 brand new, and 8gig SD card
when i boot i hold the power button for the 5 seconds, am i missing something?
tntviper1 said:
so first noob post
i used this thread to root my nook color
http://forum.xda-developers.com/showthread.php?t=1000957
problem is i have followed the steps and re done it about 5 times and every time i turn on the nook it goes right to read forever and runs the stock OS
nook 1.2 brand new, and 8gig SD card
when i boot i hold the power button for the 5 seconds, am i missing something?
Click to expand...
Click to collapse
how did you write the image to the SD card? you can't just do the write button in winimage, you have to use the "convert virtual hard disk image to drive" or something... really should be mentioned in the n00b guides.
Sequence in winimage:
Disk->Use disk (whatever your sd card is)
Disk->Restore virtual hard disk image on physical drive (select the image you're trying to write)
Click ok on the warning and you should have a boot disk
"Write disk" is prominent but just copies the files to the disk, not resize or make it bootable.
Nope - no change
DizzyDen, nope, 8 failed boots does nothing. Just fails 8 times, no restore.
Not sure what the heck happened to my device. I was using it when it just froze up outta nowhere. I tried resetting it a couple times but it wouldnt get past the android screen. Hard Reset, nothing. So I tried going into APX mode, power+vol up(idk why) then, it wouldnt get past the 'Acer' screen after that. So I let it charge overnight now it doesn't show anything at all. The power button does light up, but thats it. what the heck just happened?
NOTE: I lent out my sdcard with the update.zip in it. would putting my sdcard back in fix the problem or is it bigger than that?
is this thread a possible solution to my problem? problems seem similiar
http://forum.xda-developers.com/showthread.php?t=1874345
can someone please help me find out what happened with this, I really dont wanna call Acer n send it in if I can fix the problem myself
500tab said:
Not sure what the heck happened to my device. I was using it when it just froze up outta nowhere. I tried resetting it a couple times but it wouldnt get past the android screen. Hard Reset, nothing. So I tried going into APX mode, power+vol up(idk why) then, it wouldnt get past the 'Acer' screen after that. So I let it charge overnight now it doesn't show anything at all. The power button does light up, but thats it. what the heck just happened?
NOTE: I lent out my sdcard with the update.zip in it. would putting my sdcard back in fix the problem or is it bigger than that?
is this thread a possible solution to my problem? problems seem similiar
http://forum.xda-developers.com/showthread.php?t=1874345
can someone please help me find out what happened with this, I really dont wanna call Acer n send it in if I can fix the problem myself
Click to expand...
Click to collapse
Eh, well, need to know the condition of the tab. Sounds like it is stuck in APX mode. (Black display, white PWR light). Is this the case?
Generally, you might be able to PWR down, by press and hold the pwr button for several seconds. Then try to boot it normally.
Oh, BTW, Pwr and Vol+ is not how to get it to APX. That usually gets the stock bootloader which really isn't much of anything unless you have an update.zip on your ext sd card.
Were you completely stock? (not rooted or custom rom)
MD
Yes that's the condition, black screen white pwr light. It is rooted, thats it. Running ICS 4.0. I wont be able to get my sd card until wednesday so if I need that update.zip file I'll have to wait a few more days. Its completely off right now, I tried powering on and off a few times and I got nothing just a blank screen. Im unsure, what to try next??
500tab said:
Yes that's the condition, black screen white pwr light. It is rooted, thats it. Running ICS 4.0. I wont be able to get my sd card until wednesday so if I need that update.zip file I'll have to wait a few more days. Its completely off right now, I tried powering on and off a few times and I got nothing just a blank screen. Im unsure, what to try next??
Click to expand...
Click to collapse
Yeah, you're going to need an SD card. And make sure the tab is charged.
In the meantime, you can try a couple things just to see it you can get a different response. However, understand this.
1. You can probably forget any personal data that's stored on it. Photos, downloads, music, etc. Just to prepare you.
2. You probably have a corrupted bootloader partition. How it happens, with a normally functioning tab, nobody really knows.
You can try doing a data wipe. Usually we would wait till you get an SD card, but I'm curious if you can get anything on the display. To do this, with the tablet off, Press and hold PWR, while at the same time, continiously cycle your rotation lock left and right, quickly until you see "erasing user data" or something similar on the display.
Another thing, manually put it into APX mode. This involves using a paper clip, and press and hold the "reset" button near the USB port, then press and hold PWR. Count to 4 and release PWR, and 1 second later release the paperclip. Then plug your tablet into the PC, and see if the PC loads the drivers for it. You should already have installed the Acer USB drivers. If not, get them from the Acer site.
Understand, your chances of getting it going again, are less than 50/50. But, we all will give it a shot.
MD
This is exactly the situation I'm in... Black screen, White power light...
I was in the middle of an app, when tablet rebooted, wouldn't boot back up..
I was able to get into CWM recovery... investigated, and found that /system wouldn't mount... So, I was prepared to re-flash, so I first went to do a nandroid backup of my data folder... I also had an old nandroid backup, so I decided to restore that... After I did that, I couldn't even get into recovery anymore...
I've tried setting my tablet into apx mode, and trying to flash, but they always seem to freeze at "uploading image" (both with afterota unbrick and blackthund3r's tool)
Now, blackthund3r's tool will actually get the acer logo to show up, with "Entering download mode...", so that leads me to think the tablet isn't completely shot? It just gets stuck during the upload image...
Tried the erasing data as suggested by MD, but no luck, just black screen...
What is the sdcard method that you are speaking of? Is there anything else I can try?
Thanks in advance
---------
Edit:
Tried placing update.zip on sdcard for flashing, tried turning on the tablet with volume down...No joy
Hopefully someone has some other ideas for me? Thanks again in advance.
---------
Edit 2:
After a day of searching, finally came across this post.
Fixed and saved my tablet... Whew!
I tried installed NC-MROM through recovery but when i selected anything with power it just went to a screen that was blank so I did it through ROM manager. NC rebooted and I used RM to install CWM again (it wasn't seeing it for some reason) and then tried to flash the gapps pack but every reboot it said it couldn't find the path to the file. So I tried downloading a new ROM through CWM but when I flashed it same thing. So I figured maybe it was the version of CWM so I flashed a different one, same thing. I think I tried it once more, picking 3.0.0 (it was whatever was the top one in the list). Tried rebooting into recovery to backup rom through RM, but now the phone is stuck on the green cyanogen screen saying loading with 3 dots. I've tried puttting unooter on a sd or even the B&N 1.42 image but i can't seem to get it to read the card. I tried getting to the device through ADB on my laptop but it isnt seeing it either. Did I turn it into a paper weight or is there any hope of getting it back working?
mumbles202 said:
Did I turn it into a paper weight or is there any hope of getting it back working?
Click to expand...
Click to collapse
No, not a paper weight, that is almost impossible. Go to my tips thread linked in my signature and look at items A8, A9, A10, A11, A12 and A15. One of those should help you get out of your problem.
Sent from my NookColor using Tapatalk
It will work somehow!
well, since it turned on, it will work. if it will not even turn on, there is almost no hope.
thejrcrafter2 said:
well, since it turned on, it will work. if it will not even turn on, there is almost no hope.
Click to expand...
Click to collapse
Not necessarily true about not turning on. If you wipe your boot partition and try to boot without a bootable SD in the slot, the unit will not turn on. To get it to turn on, insert a bootable SD in the slot and if the battery is charged, it should turn on.
But you are right about if it turns on, there is a very good chance it can be resurrected.
I have a TMobile/MetroPCS GS4 model SGH-M919N that got stuck in a boot loop last week. I was finally able to find working firmware last night and used Odin to flash. Once it got to PASS my phone automatically rebooted with the blue recovery boot text in the top left, but then it just went back into a boot loop. I tried all other firmwares and none of them got to 100% so now I don't know what else I can do.
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
alesu69 said:
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
Click to expand...
Click to collapse
Have you tried replacing the battery? I figured I would try that but I havent gotten around to it yet
Not yet, i have no spare battery. Looks like when i plug the charger my phone just vibrates, like it's rebooting, and it's not showing anything. I found a similar issue here: http://forum.xda-developers.com/showthread.php?t=2532447
Looks like one guy did solve his problem.
*need to mention that by dead I mean it shows the "Samsung Galaxy S4 GT-I9505" logo and also shows "RECOVERY BOOTING", even though I didn't enter in recovery mode. Looks like now it doesn't shows anymore "RECOVERY BOOTING", but still, it doesn't boot. I was able to flash firmwares via odin and kies, but still no luck.
LE: It start booting by.. magic, i got to samsung boot logo, but that's all, crashed again.
After flash with Odin, immediately boot into recovery, perform a factory wipe, and reboot.
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
alesu69 said:
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
Click to expand...
Click to collapse
How did you manage to get into recovery?
harary said:
How did you manage to get into recovery?
Click to expand...
Click to collapse
Yes, but if I leave my phone in recovery (stock or custom), it just either freezes, either reboots, even though i don't do anything, just let it idle.
I can't manage to boot into the ROM 'cause eventually it will reboot. I couldn't finish the setup wizard.
OK so I don't know if this helps, but I managed to at least get past the "blue recovery boot" part. When the phone vibrated I let go of the power while still holding home + vol up, and I managed to get to the android guy with a blue progress bar below him. My phone shut off as the progress bar got 80-90% but now I know it's not impossible to start recovery.
Well, nothing works. After flashing pit file, an 4.4.2 odin prerooted image from here, cf auto root and then twrp, it will still randomly reboot. I manage to get past the boot logo into setup wizard, but phone just freezes after a couple of minutes, can't finish the setup wizard. Also, if i idle in twrp it will reboot sooner or later, tested already.I left my phone idling in twrp just to recharge my battery.
At least i have no more "unable to mount /data" errors.
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Operation Ivy said:
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Click to expand...
Click to collapse
What do you mean with back and forth?
harary said:
What do you mean with back and forth?
Click to expand...
Click to collapse
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend who repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
alesu69 said:
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend which repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
Click to expand...
Click to collapse
I got several times into Recovery Mode now, flashed several ROMs. I had no issues with freezing, especially not in TWRP Recovery Mode. But sometimes if i am trying to go into Recovery Mode or i just want to start ROMs, the screen turns into yellow behind the Samsung logo. If i dont take out the battery this wents into a complete white, but nothing happens.
Yes please tell if you got some news..
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Joashrox said:
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Click to expand...
Click to collapse
But it is sure that the power button is working because i get this blue "recovery booting". Or am i wrong?
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
alesu69 said:
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
Click to expand...
Click to collapse
Replace power button to new one. I have the same problems with s3 and this works. Try it.
Sent from my GT-I9300 using XDA-Developers mobile app
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
alesu69 said:
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
Click to expand...
Click to collapse
If You can't charge phone... Yup, motherboard is died. If You plug the charger and see something this have to be button but if You plug charger and don't see anything this is motherboard.