Database Users

[Q] Bricked!?!?!

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?

[Q] Custom ROM, stuck at boot animation...

I wanted to run a custom ROM on my A500 (first attempt at installing custom ROM), but i'm now stuck at the boot animation.
I downgraded my A500 to 3.0.1, rooted, installed clockwork mod, upgraded cwm to 1.5. So far so good.
Then i downloaded thor rom v12, copied it to the external sd card (by putting it on USB thumb drive, transfer to tablet, copy to external SD using file explorer - something tells me I'm going to need to pick up an sd card reader for my computer)
Rebooted into recovery, wiped everything (had nothing of value installed yet), and then chose to install zip file, chose thor_rom_v12.zip on external SD card, it started installing - looked like it succeeded.
Reboot tablet, and i've been staring at the boot animation (electric blue pulsating android with spinning gears on it) for about 45 minutes.
How should I proceed from here? Any idea what I did wrong?
Thanks

Hold the power button down and see if you can force it to shut down. I dont think itll turn off but its worth a try. You could also try the hard reset button (pin hole on the side of the tab) if the reset works than you should be able to boot back into recovery. If not than youll just have to wait till the battery dies.
Once you eventually get it turned off than try booting into recovery and do a full wipe and reflash the rom. I have a feeling the file you downloaded is corrupted though. if this is so than your tab probally wont boot up again.
At this point id redownload the thor or another rom and than try flashing that. You'd have to get an sd reader since you won't be able to transfer the files through your iconia again. If you can manage to get a clean download on your micro sd somehow than i'd skip straight to this step and start redownloading the rom right now.
BTW these are just the things i would try from knowing what I do about android. I haven't had any issues with my tab yet so I havent looked for solutions for this it, but ive dealt with other boot looped and soft bricked devices.
I'm sure if you do a search you'll find something.

SD Card Issues

So, the other day I was excited to see the TWRP update to 2.0. I've enjoyed the TWRP 1.x line for quite a while so I figured, why not? Then the troubles started. As that post of mine says, I cleared up the initial SD issues (not able to mount in recovery) with the "fastboot oem enableqxdm 0" command. I reverted it to TWRP 1.1.1. It still boot loops (both the recovery or system) quite often, requiring another enableqxdm and reflash the recovery. Each time I reboot, I have to cross as many fingers I can find the house and hope it gets through to the system. I had to go through 12 hours at work without my trusty phone to occupy my down time. Talk about grueling! Then I get home, turn it on so I could do some more fastboot magic, but missed the volume-down in time. It boots right into the ROM that time (not the 14 times I tried at work!.
Now, when it does successfully boot into the ROM (jaredthegreat's ICS Alpha 2.3) the notification bar is forever saying "Preparing SD Card." It ran all night and still wasn't done "checking" for errors. I have another 1GB SD card I tried, just to make sure it wasn't my normal one, and it does the same thing. I have formatted it (with Panasonic's SDFormatter) a few times, and still no luck.
I don't quite understand how flashing a ROM (even if it goes bad) would overwrite the phone's own settings (like enableqxdm) or cause this sporadic boot looping. I have been reluctant to flash another ROM, but I think it's the only thing I haven't tried.
Does anyone have any other insight into the how/why, or something else to try to get the SD card to work in the system, past this "preparing" stage?

So as to confuse myself even more, I have found that I can get past my boot-loop problem by just plugging in a USB cord. Whether it's my AC charger or my computer, for whatever reason, it needs a cord plugged in to get past the white initial EVO boot logo.
Now to work on the SD issue. I have read that deleting the fsck_msdos bin from the phone "fixes" it, but I haven't gotten my Windows adb to recognize my phone when it has any ICS ROM yet. Is it an HTC Sync/Driver issue or Android issue?

Sounds like you need to go with the ics-deck-pa8 ROM

Fixed bootloop, back in bootloop. Crap.

How it started: I use a NC with mirage 7.2 flashed to the emmc in my car. It runs Torque to display engine data, and is switched in and out of sleep with the ignition. Two days ago I started the car and got the low-battery "exclamation point" icon thing, so I figured the charging cable must have come loose*. I took it all out and left it charging overnight, but when I went to boot it in the morning it was stuck in a cyanoboot loop. I couldn't power the device down or enter emmc recovery. When I completely unplug the NC I can't do anything, the screen remains black no matter what I press, except it flashes white every 5 seconds or so. If I manage to plug it on, get to the cyanoboot loading screen and unplug it while holding the power button down at the right time, I can sometimes get it to power off completely.
What I have done so far: Tried various recovery SD methods, none of which worked. Wiped cache/data/system, factory reset, tried loading 7.2 again over the top of whatever is left in there, lol. Basically after it first happened I probably made a big mess of the file system in a desperate attempt for some kind of stability. I tried this recovery SD: http://forum.xda-developers.com/showthread.php?p=25354258#post25354258 ; section A10, and managed to get into CWR. I've never felt such joy in my life.
What finally worked: I repaired the 2nd partition with the help of this thread: http://forum.xda-developers.com/showthread.php?t=1759558 . I did not repair or format any other partitions though. After repairing the partition, I did a factory reset and flashed mirage 7.2 and gapps back onto the emmc. Before I rebooted, I swapped a clean SD in but it still went back into the bootloop..BUT...when I put my recovery SD back in it booted into 7.2! I set everything up and was happy to have it running again. Battery level was at 88%.
What made it stop working: I was testing to make sure the NC would enter sleep mode when disconnected from power, so I unplugged it. Everything went black, no "sleeping" screen, just a hard shut-down. I powered it back on and I'm now back in a cyanomod boot loop.
So...any ideas? If there's a way to completely wipe and reinstall everything I'm OK with that. I've never used ADB before but I'll give it a shot if someone can lead me in the right direction. Thanks in advance.
*I'm using a 2amp USB car charger with a modified data-looped cable for a/c style charging in the car. I know the supplied nook cables are prone to going bad, and this may have happened with the vibration of the car and all. Not sure.

Little update: I can sometimes get into TWRP by selecting the "normal emmc" boot from the cyanoboot screen. I don't understand how that's possible, as I flashed that on my original install of 7.2 months ago. Guess I need to figure out how to completely wipe and re-flash everything.

SPLEclipse said:
Little update: I can sometimes get into TWRP by selecting the "normal emmc" boot from the cyanoboot screen. I don't understand how that's possible, as I flashed that on my original install of 7.2 months ago. Guess I need to figure out how to completely wipe and re-flash everything.
Click to expand...
Click to collapse
To completely wipe and reflash everything, do the other two zips that you said you did not do from my partition repair thread.
Sent from my Nook HD+ running CM10 on Hybrid SD

No luck with that. Here's exactly what I did, so tell me where I might be going wrong:
1) Burned an image of the 6.1.0.2 recovery onto SD, then put the (2) recovery zips and the (1) format zip as well as the mirage 7.2 and gapp zips onto the SD.
2) Booted into cyanoboot, it took a few tries to get out of the loop and into CWM. Note that I can't power on at all unless it's plugged in. As soon as I unplug the NC it turns of except the screen will flash every 5 seconds or so. Once I got into CWM, I installed both partition repair zips, starting with the 1-4-5-6-7-8, followed by the 2. Rebooted. There were no errors at all.
3) Again it took a few tries to get out of the bootloop and into CWM. Installed the format zip and rebooted again.
4) Installed Mirage 7.2 and gapps and restarted, but went straight back into bootloop. I know that the rom requires a clean formated SD card, so before rebooting after I installed the zips I took out the SD card, formatted with SDFormatter and reinserted in into the NC.
I'm beginning to think this is something hardware related. :crying:

Sounds like there might be some bad data in emmc, I had this problem before and fixed it by formatting everything , even emmc and wiping dalvik cache. Then boot off a SD card using the latest cwm.
Sent from my NookColor using xda app-developers app

SPLEclipse said:
No luck with that. Here's exactly what I did, so tell me where I might be going wrong:
1) Burned an image of the 6.1.0.2 recovery onto SD, then put the (2) recovery zips and the (1) format zip as well as the mirage 7.2 and gapp zips onto the SD.
2) Booted into cyanoboot, it took a few tries to get out of the loop and into CWM. Note that I can't power on at all unless it's plugged in. As soon as I unplug the NC it turns of except the screen will flash every 5 seconds or so. Once I got into CWM, I installed both partition repair zips, starting with the 1-4-5-6-7-8, followed by the 2. Rebooted. There were no errors at all.
3) Again it took a few tries to get out of the bootloop and into CWM. Installed the format zip and rebooted again.
4) Installed Mirage 7.2 and gapps and restarted, but went straight back into bootloop. I know that the rom requires a clean formated SD card, so before rebooting after I installed the zips I took out the SD card, formatted with SDFormatter and reinserted in into the NC.
I'm beginning to think this is something hardware related. :crying:
Click to expand...
Click to collapse
It is possible that your partition table is messed up. The only way to find out is to boot to recovery, connect your USB cable to the PC and run ADB. It is also possible to make a CM bootable SD and use terminal emulator to check it out.
Once you get ADB shell or terminal emulator working, type the following command:
fdisk -l /dev/block/mmcblk0
It should say 965 cylinders, 4 heads, 63 sectors.
If it does not, we need to do a manual repair.
You can also abandon emmc and just run off SD.
Sent from my Nook HD+ running CM10 on Hybrid SD

[Q] Nook CM-7 boot loops

I've read the other posts, and there are some similarities, but I still don't get a clear picture... So here goes...
I've had my Nook Color for about two years and created a SD card boot to CM7 that worked like a charm for these last two years, then...
the system a few days ago went into a boot mode automatically, and just looped. All I could do was turn it off by long press on the power button.
I removed the SD card and booted to the Nook operating system and all went fine.
Re-installed the SD card and started the boot process, it again went to continuous CM7 logo looping.
Tried recovery mode, which seemed to go well, although it shut itself down without completing the boot process.
I have tried every imaginable switch combination (volume, power, n), all to no avail. Depleted power, full power, power connected, etc. Nothing breaks the cycle.
Recent app installations were Netflix, a word document processor, a speaker amplification. Titanium backup was running sometime in the near past. Most apps were loaded to the SD card.
I would like to be able to save some documents on the SD card, but now what to do?
Reload a fresh copy of CM7?
Load a new triple boot of basic, CM7 and CM9?
Just jump to a altogether new CM10.1?
Any suggestions (remember the forum rules, now...).
Thanks a million.
Well, here's what I've done.
Burnt another SD card with CM10.1 - works like a charm but don't have any of my old files on the card -started all new.
Downloaded CWM on another card, booted to it, but got menu choices I wasn't sure about, so chose "SD boot". removed the CWM card, put in my old CM5.7 card, pressed the "N" (to start the reboot), and got the same old loop.
I guess I just don't know enough, and don't know where to go to get smarter.
And the rest of the story...
CM10.1 ran fine for two days, then this morning on power-on, I got a message of "Trebuchet" error - no matter what I did, the error message prevented starting any other program or a normal power off. So...on restart, got LOOPING AGAIN! CWMod doesn't help.
Back to Google and forums.

Problem solved! (But, other than getting a good installation, I don't remember exactly HOW!)