Related
I have a Nook Color. Somehow (and I really can't recall how), I can no longer get to the B&N side of my Nook. Even with the micro-SD out, I still go directly into CYANOGEN. To make matters worse, every single app I try to get from the market will not download. Once I 'Accept & download', the app starts to download then I get an Error overlay screen: "name-of-software" could not be downloaded due to an error.
So I have a V--E--R--Y generic tablet that can't do much. Please help.
Thanx in advance...................................
How did you go about installing CM7? Did you install it to the internal storage?
Please help!!! Noobie messed up NC (big time)
That's part of the problem. I did not consciously install to internal memory, I wanted it to boot from the SD card.
That's what I did...
That's what I did once. I unwittingly installed it onto the internal memory. It also happened to be really buggy. I restored it to stock using Clockworkmod Recovery. Did you use the installer for the SD card?
On a 16GB microSD, I used Win32DiskImager to write 1gb_clockwork-3.2.0.1-eyeballer to a newly-formatted SD card.
I put the ZIP file for: gapps-gb-20110828-signedgapps-gb-20110828-signed, and gapps-gb-20110828-newtalk-signed.
I tried the home-power key combo. It asks me if I'm sure that I want to restore to the factory. I say "Yes" but when the Nook starts up, I'm still in cyanogen mod.
Should I (re-)format the MicroSD, write 1gb_clockwork-3.2.0.1-eyeballer (or another version) then move recovery-clockwork-3.2.0.1-encore?
Aside from not being able to get back to B&N-supplied software, I can't do anything with the NC as an Android tablet.
OP, do you intend to install CM7 into the internal memory?
All I'm trying to accomplish is to get back to the factory NC settings. Once I can get there, I'll decide.
How to hard reset and Factory Default Nook Color - http://goo.gl/pSFui
Power down your NC. Wait approximately 10 seconds or so-- just give it a bit of a break between shut down and factory reset.
Press and hold power button and your "N" home button almost simultaneously-- press Power first and then the N.
Hold these until your screen flashes the "Touch the future of reading" message; hold for a second or two afterward, then release. You will then get a prompt asking if you want to reset your nook to factory. Press the home button to continue. It will ask you to confirm. Press the home key again. Your nook will deregister, reset, and when it reboots, you will see "Kate" in her tutorial video, as if you'd never registered it in the first place.
(Obviously your account info will still be valid-- simply register with your email/pw combo instead of creating a new account.)
Hope this helps- if so please click thanks
Sent from my MB860 using XDA App
I did this (more than once - grrrrrrrrrrrrr!). I never see the "touch the future....." message. Instead, I get a cyanogen mod 7 screen with the message "Booting into Recovery". Then I get a sickly yellow-greenish screen that asks (twice) if I want to teset. I confirm both times then it "wipes" the data. It then boots into a cyanogen mod 7 screen (and the skateboarding 'droid) and I go through the registration process.
Now, when I select a Google app, the downloading (Google Maps) seems to be taking forever, but at least I'm not getting the error I got before.
Also, I do not see the progress of the download that I'm used to seeing on my phone. All I see is "movement" under the "Downloading..." message. How long do I leave it before I abort the download?
Your micro sd card is removed right?
Sent from my MB860 using XDA App
mike11050 said:
On a 16GB microSD, I used Win32DiskImager to write 1gb_clockwork-3.2.0.1-eyeballer to a newly-formatted SD card.
I put the ZIP file for: gapps-gb-20110828-signedgapps-gb-20110828-signed, and gapps-gb-20110828-newtalk-signed.
I tried the home-power key combo. It asks me if I'm sure that I want to restore to the factory. I say "Yes" but when the Nook starts up, I'm still in cyanogen mod.
Should I (re-)format the MicroSD, write 1gb_clockwork-3.2.0.1-eyeballer (or another version) then move recovery-clockwork-3.2.0.1-encore?
Aside from not being able to get back to B&N-supplied software, I can't do anything with the NC as an Android tablet.
Click to expand...
Click to collapse
Eyeballer is a clockwork recovery bootable SD image which is used to install stuff (e.g. CM7) to internal memory.
http://forum.xda-developers.com/showthread.php?t=1030227
VeryGreen (size agnostic thread) is the SD image which creates a full OS on the SD card itself leaving the internal memory alone.
http://forum.xda-developers.com/showthread.php?t=1000957
You have used the Eyeballer method and have therefore done an internal install. You must also have installed a CM7 zip not just the gapps zip as they are just google apps and not an actual ROM.
You have 2 ways forward.
The simplest is if you want to end up with internal CM7 and are not interested in running the B & N ROM. Start again by creating the Eyeballer SD card using win32diskImager. Make sure you use a real USB SD adapter and not a card slot on a laptop. Put onto the card the CM7 ROM zip. I recommend the one from the KANG MiRaGe thread in the development forum. It is the most up to date and stable version available at the moment. Also put on one gapps zip (20110828). Now put the card in Nook, Power up and when in recovery then use the menus to format system, data and cache. Do NOT format boot. Then flash the CM7 ROM zip, then the gapps zip. Power down and prepare a clean SD card either by reformatting the eyeballer card with something like the HP USB card utility or a partition manager in the PC like miniTools. You could also use a different SD card if you want to keep the eyeballer one for future use. Put the card back in, power up and you should now be in a stable CM7 environment where you can set up wifi, register with the Google market and download apps.
The second way if you really want to return to stock on the internal and run CM7 of the SD card then use the eyeballer method but instead of flashing CM7 and gapps you now use a return to stock zip. Make sure you still format the partitions as before.
http://forum.xda-developers.com/showthread.php?t=914690
Once you have it back to stock and upgraded to whatever stock you want then follow the VeryGreen method from the link above. Once the SD card has put CM7 on itself, do not worry that there is only a 114MB space if you ever put the card back in the PC. That is normal; it is just the boot partition that the PC sees. The rest of the card can be seen if you USB connect the Nook to the PC.
Yes it is. Also, even though I'm not getting an error, no apps are loading.
You absolutely rock!!!!!!!!!!!!!!
I'm back at the NC "baseline". I tried to go back to a 1.2 (which is what it came with) using "update-nc-stock-1.2-signed". Once I re-booted, it kept returning to the NOOK COLOR screen. Then I used a 1.0.1 from your last post. It came back fine with 2 exceptions. 1) I now have a message that I need to install a SD card. When I do, my (Windows Explorer) "Computer" screen only recognizes the SD card and not the Nook. These are piddly little issues, but if I can get them fixed, great! (Right now, I cannot upgrade the NC or move any books or load any apps.
Thanks again!!!!!!!!!!!!!!!
mike11050 said:
That's part of the problem. I did not consciously install to internal memory, I wanted it to boot from the SD card.
Click to expand...
Click to collapse
I had this same problem. Since I am a new member, and can't post links, I'm going to try to help.
Install Clockwork Recovery to an SD card. Yes, the same way you did when installing clockwork to the SD the first time.
There are some threads on other fourms (google is your friend) that have links to Update files that allow you to update while keeping clockwork recovery, and some that will remove clockwork recovery. If you can remove the SD card and boot into the Stock Nook OS, then don't worry about installing 1.0.0 or 1.0.1 like some of the forms say. Just place the .ZIP file of the hacked update (usually 1.3 or 1.4 I think) into the root folder of the SD card, then Install it on your NC just like installing CM7 onto the internal memory. Your nook should start working again. It restored mine to full functionality. I can now pay 3 Dollars for angry birds, but at least its not as terribly slow and laggy as it was with CM7.
mike11050 said:
You absolutely rock!!!!!!!!!!!!!!
When I do, my (Windows Explorer) "Computer" screen only recognizes the SD card and not the Nook. These are piddly little issues, but if I can get them fixed, great! (Right now, I cannot upgrade the NC or move any books or load any apps.
Thanks again!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
I had the same issue last weekend, somehow my internal memory had become unrecognizable to anything, and the local Barnes and Noble store had a SD card that repartitioned the internal memory, and I was back in business. And as an added bonus I now have the 4 GB app/BN partition and the 1 GB mostly useless partition.
mike11050 said:
On a 16GB microSD, I used Win32DiskImager to write 1gb_clockwork-3.2.0.1-eyeballer to a newly-formatted SD card. ...
Click to expand...
Click to collapse
The instructions I see when googling around where I see that image mentioned are instructions for installing onto the Nook Color internal memory.
In the simplest case, making an n2a card is much less complicated than that ~ all you need is on the PC, write the size agnostic image, then drop in the CM7 build you want to use, then put the card in the Nook and it creates itself. There are upsides and downsides to different n2a methods, but that one seems to be the easiest ~ I've done it successfully several times, and I'm certainly nothing like an expert when it comes to these Android systems.
A recovery card image will make a bootable recovery card ... and while that might not have been what you needed to get what you want, its what you need to get the nook back to stock.
You might want to go to
http://forum.xda-developers.com/showpost.php?p=22809801&postcount=148
... to get a version of the 1.4.1 upgrade that your recovery card can install. You'll probably have to wipe all sorts of partitions, which means you'll have to sign in with the B&N store again and you'll get to download you B&N apps again, but that's pretty straightforward.
This OP in this thread:
http://forum.xda-developers.com/showpost.php?p=10623716&postcount=1
... says that it will be necessary to format ("wipe") the /data and /system partitions, but it doesn't seem like you'll lose anything you want to keep. After all, you've either overwritten or completely tangled up your stock B&N info.
That post above has 1.4.1. There should be a signed 1.4.2 lying around somewhere, but if not, once its back to stock, you can update to 1.4.2 the normal way, download the B&N update file, drop it in the root of the Nook, make sure its at least 30% charged, and let it go to sleep, which will run the update file.
I've worked ever so hard trying to configure and get the aesthetics of my cm7 rom up and running and apps in my testing might have triangulated and caused this error, I don't know.
Whenever I try to install a rom, boot into recovery, do a backup-- basically my clockwork is broken. Not broken, it still tries. It just pops this up on the screen:
Populating /dev using udev: done
Initializing random number generator....done
modprobe: chdir (2.6.32.9): No such file or directory
Starting network...
Detected Standard B&N nook layout, emmc first
It appears the SD card is already properly formatted
Skipping format
Mounting /dev/mmcblk1p1 as /boot
Looking for the install images....
Initial Install files not found
Please download it from nook.linuxhacker.ru
and put on first partition of this SD card
the name should start with updatei-cm and end with .zip
Click to expand...
Click to collapse
I'm using a recently nightly build of CM7.
I really love how I have it set-up, but if I don't have anyway to ever back it up my results are effortless.
How can I fix this situation without removal of the system. anyone, please?
First of all, have you done a nandroid backup in CWM? If so you can definitely recover.
Second it looks like your boot file is corrupted, always sending you to recover rather than a normal boot. What boot setup are you using?
echoedge said:
I've worked ever so hard trying to configure and get the aesthetics of my cm7 rom up and running and apps in my testing might have triangulated and caused this error, I don't know.
Whenever I try to install a rom, boot into recovery, do a backup-- basically my clockwork is broken. Not broken, it still tries. It just pops this up on the screen:
I'm using a recently nightly build of CM7.
I really love how I have it set-up, but if I don't have anyway to ever back it up my results are effortless.
How can I fix this situation without removal of the system. anyone, please?
Click to expand...
Click to collapse
You have installed your ROM to SD. There is no CWM recovery on SD installs. You cannot do a nandroid backup with the SD recovery.
See my post here for an explanation of the difference between emmc installs and SD installs:
http://forum.xda-developers.com/showthread.php?p=25354258
However, there is a way to back it up. Keep reading further down in my post.
thank you.
but how do i get access to uAltRam and uAltImg.
Multi SD Mount APP isn't working.
R/W permission difficulties in root explorer..
Using the 4202012 nightly build..
please help,
this shouldn't be too hard, don't let it drive me crazy
echoedge said:
thank you.
but how do i get access to uAltRam and uAltImg.
Multi SD Mount APP isn't working.
R/W permission difficulties in root explorer..
Using the 4202012 nightly build..
please help,
this shouldn't be too hard, don't let it drive me crazy
Click to expand...
Click to collapse
Take the card out and put in your PC. It will see the boot partition and you can copy the files there.
leapinlar said:
Take the card out and put in your PC. It will see the boot partition and you can copy the files there.
Click to expand...
Click to collapse
Hmm.. somehow I got it doing that. I of course tried that before and only the two partitions were loading. This time I was messing with it and clicking the multi sd mount widget and somehow the boot drive came up and I transferred the files on there.
So now I can do a nandroid backup as usual? Or sense it's an (Alt) instead of a recovery thing must it be different?
I'll try some things in the mean time..
Okay, so I have to boot into recovery and choose alternative and do it manually.
Can't do it with Rom Manager/Rom Tool Kit. Tried and it did the same error as in the OP.
Off to try now.
This is really strange though.
I've been messing with Nooks for a while and always used rom manager and the recovery console just fine.. but i've always ever done dual sd boots.This is my first time really doing a single one.
I'm in the boot menu (encore u-boot menu by j4mm3r), 1.2 port + extras.
It's been at
'Booting. One Moment'..." for at least a minute. Assuming it's frozen itself..
edit: Yeah, the Alt files didn't work.. I reset and pressed the N button, went to alternate and SD card. Nothing.
Reset it and it works as usual, but still no ability to backup..
echoedge said:
Okay, so I have to boot into recovery and choose alternative and do it manually.
Can't do it with Rom Manager/Rom Tool Kit. Tried and it did the same error as in the OP.
Off to try now.
This is really strange though.
I've been messing with Nooks for a while and always used rom manager and the recovery console just fine.. but i've always ever done dual sd boots.This is my first time really doing a single one.
I'm in the boot menu (encore u-boot menu by j4mm3r), 1.2 port + extras.
It's been at
'Booting. One Moment'..." for at least a minute. Assuming it's frozen itself..
Click to expand...
Click to collapse
Do not use ROM Manager with the verygreen SD installation. It does not work. Use the boot menu to boot into the alternate. Hold the n key while booting. Choose sd, alt.
Edit: you said two partitions showed up. Did you physically take the card out and insert into a card reader in your PC? It should see just one drive. Make sure those two files are there or it will hang when you choose it in the boot menu. I suspect you put the files on emmc boot since you used that strange program to do it.
Sent from my Nook Color running ICS and Tapatalk
No,
it's something with the multi mount sd app widget.
I hook mini usb to usb.
then hit the widget.
and JUST the boot partition comes up.
It says something about disk F: is not formatted correctly as well.
Just plugging it in without the multi mount app the outward sd card partition and the nook color come up, just those two.
And can't believe I didn't think to take the mini SD out and use an adapter. I'll try it again with that.
You're right I did mess something up with my EMMC.
Before I had it on a stock nook.
Now it goes to the cyanomod thing.
I took the miniSD card out, plugged it in for power and it turned on.
Went to that, had a bunch of force closed issues nothing worked, dry and empty, etc.
Any suggestions?
I'm gonna check out the miniSD card partitions now and try to get something going with that.
echoedge said:
You're right I did mess something up with my EMMC.
Before I had it on a stock nook.
Now it goes to the cyanomod thing.
I took the miniSD card out, plugged it in for power and it turned on.
Went to that, had a bunch of force closed issues nothing worked, dry and empty, etc.
Any suggestions?
I'm gonna check out the miniSD card partitions now and try to get something going with that.
Click to expand...
Click to collapse
There are many threads here that will tell you how to restore stock to emmc. Search for them.
But to get the SD working, do what I said. And I would suggest getting rid of that mount program so you don't mess it up again.
Edit: The problem with those mount programs is, if you mount the wrong partition, windows can only read fat partitions and will ask you to format. System and data are ext4 which windows cannot read.
Sent from my Nook Color running ICS and Tapatalk
Thanks a bunch.
In ubuntu once the sd card is inserted all 4 partititions automatically came up so I was able to copy and paste the Alt images.
Am backing up right now
And yeah getting the emmc back to stop np.
One thing i'm confused about.. you're saying one cannot update rom's if booting from an SD card?
also, i assume all in eed to do to make a back-up on my hard drive or usb (so its not just inclusive to the minisd), i can just root browser into mnt/sdcard/clockworkmod/backup and and create a zip of the 2012.5.5.etc.etc.etc. made folder and trnasfer it onto external device? If needed all I would need to do is a transfer back?
echoedge said:
One thing i'm confused about.. you're saying one cannot update rom's if booting from an SD card?
Click to expand...
Click to collapse
Yes you can update the ROM. Just not with CWM. You place the update-...zip in the boot partition of the SD and then using the boot menu (hold n during boot) select SD and recovery. The script in the boot partition will install the ROM for you. You need to read the first post in the agnostic image thread. It tells you all this.
On the second question, you can do it that way, but the files are already compressed there so just copy the folder to your PC to archive them.
is it okay to just boot into alternative (power + vol up/down) instead of going through the manual booting with the 'N' on start-up?
echoedge said:
is it okay to just boot into alternative (power + vol up/down) instead of going through the manual booting with the 'N' on start-up?
Click to expand...
Click to collapse
Yes. I didn't know you could do it that way. See, you taught me something. LOL. As long as you are getting into the 3.0.2.8 CWM recovery it's OK.
Sent from my NookColor using Tapatalk
This was my way of rooting. Is this the best way of doing things these days? It's here for reference because if someone new comes here it's easy to get lost (which rooter to use etc):
0) Backup using noogie from http://code.google.com/p/nst-recovery/downloads/list (whole root partition - should be ~2gb)
1) CWM boot loader:
http://forum.xda-developers.com/showthread.php?t=1360994
2) Format:
http://forum.xda-developers.com/showthread.php?t=1475613
3) Root it with MinimalTouch:
http://forum.xda-developers.com/showthread.php?t=1346748
(skipping sign-in: top left screen touch, top right corner screen touch, bottom right, bottom left... then get youtube via the apps button in the centre bottom then swipe to the right)
I guessed MinimalTouch is a little better than TouchNooter because it allows us to choose USB only adb for better security. I wondered if this is the preferred way now...
If market isn't working then you can install some by adb install, including fdroid, a small alternative FOSS repository. (appbrain apk too?)
4) Then think about multitouch for pinch to zoom. Might as well use the intergrated USB host mode since it's disabled by default it shouldn't fry anything
http://forum.xda-developers.com/showthread.php?t=1570637
Let me know if I missed anything or got something wrong. Need to disable over the air updates too still?
How to boot noogie from the SD Card?
I have been trying to boot from the SD card but I can't seem to get it to work.
All that is needed is to write the noogie.img file to the SD card, put it into the Nook, and just turn the Nook on right?
Any info would be very appreciated. God Bless ya jago25_98.
I'll let someone else do a better job, but...
1. Acquire SD card, and reader.
2. Write noogie.img (win33diskimager) to the sd card and do the backup thingy. If you did it right, the file should be about 1.9gb in size (an image of the nook's internal storage)
3. Get another SD card (or use the same one) and write the CWM recovery tool (win32diskimager) to the sd card.
4. Place the root zips onto the SD card (anywhere is fine). Do not extract them.
5. Place the SD card in your nook and turn it on. You should get the clockwork boot screen.
6. (Check the CWM post for detailed info) Follow the rooting instructions for the rooting method of your choice.
7. For TouchNooter, wait 24 hours. For MinimalTouch, start playing with your new tablet!
Sorry if these steps are wrong or hard to follow, this is just what I've learned by hanging out here long enough. (someone correct me)
I installed with Nooter. Is it safe to reinstall with another method, like noogie? I want to get multitouch to work but dont know how it works for nooter without cwm.
How to force Nook to boot to noogie.img on SDcard?
brendan10211 said:
I'll let someone else do a better job, but...
1. Acquire SD card, and reader.
2. Write noogie.img (win33diskimager) to the sd card and do the backup thingy. If you did it right, the file should be about 1.9gb in size (an image of the nook's internal storage)
3. Get another SD card (or use the same one) and write the CWM recovery tool (win32diskimager) to the sd card.
4. Place the root zips onto the SD card (anywhere is fine). Do not extract them.
5. Place the SD card in your nook and turn it on. You should get the clockwork boot screen.
6. (Check the CWM post for detailed info) Follow the rooting instructions for the rooting method of your choice.
7. For TouchNooter, wait 24 hours. For MinimalTouch, start playing with your new tablet!
Sorry if these steps are wrong or hard to follow, this is just what I've learned by hanging out here long enough. (someone correct me)
Click to expand...
Click to collapse
Thank you for the step by step! That will come in handy! but how to I get the Nook to boot from the SD card when trying to use the noogie.img? I am trying to make a back up (I am on the 1.1.2 firmware version)
I have tried just puting the card in the Nook with the noogie.img written to the card. Then turning it on. But it doesn't boot to the card. I know this because it asks me if I want to format the card so it can be used for storage. And I can cancel that and go to the library and see all my books on the internal storage.
I would really love to turn this into a much more capable tablet by rooting it. But I am at quite an empass with the "booting to noogie.img" issue.
I had the same problem with noogie when I wrote the image with roadkil's, then I wrote it with winimage and I could have the rooted forever screen and I could create my backup image.
I explained it there:
http://forum.xda-developers.com/showthread.php?p=26262575#post26262575
albertorrent said:
I had the same problem with noogie when I wrote the image with roadkil's, then I wrote it with winimage and I could have the rooted forever screen and I could create my backup image.
I explained it there:
http://forum.xda-developers.com/showthread.php?p=26262575#post26262575
Click to expand...
Click to collapse
Thank you, the way its written could very well be my problem. But the only thing is, I only use Linux computers. So a Windows image writing program won't work.
I followed this tutorial for writing the image to the SD card in the terminal: http://forum.xda-developers.com/showthread.php?t=1142983
It uses an entirely Terminal / Command Line way of writing the image to the SD card for both Mac, and Linux. So I'm not sure what the difference is between that and the Winimage program. But at this point I am at a empass, because I can not boot from the noogie.img to be able to do a full back up.
Are there any other Linux users here that may have a solution?
the trick is that you have to write to the root of the SD card... not the first partition.
also, there are better ways to do this now after noogie. I recently blanked mine to experiment with minimal touch. with that you get a cwm recovery onto sdcard. I didn't even boot to bold power button plus 2 lower buttons either side of the screen to get it to boot. I keep that on a separate card now. with it you can Android backup but you need more than 2gb for that. minimal touch root is more what I'm familiar with than the touchnooter. boogie I did ages ago and cant remember the details now
Yikes! Last night I was moving some files via adb wireless into the root directory of my nst (bad move for a newbie).
Now my nook will not power back on or anything. I've taken the battery out and plugged it back in. Nothing.
The screen is stuck on "Your NOOK has turned off completely" message.
No matter how long I hold the power button, nothing happens.
Have I bricked my device?:crying:
centralpark said:
Have I bricked my device?
Click to expand...
Click to collapse
Well, yes, but it's not a big deal. It's fixable.
You need something on an SD card, Noogie, Clockwork Recovery, one of the Nooters.
I'd use Noogie on an SD card and copy your backup to the internal SD card.
You do have a backup?
Renate NST said:
Well, yes, but it's not a big deal. It's fixable.
You need something on an SD card, Noogie, Clockwork Recovery, one of the Nooters.
I'd use Noogie on an SD card and copy your backup to the internal SD card.
You do have a backup?
Click to expand...
Click to collapse
I know that I did a backup last November, but I can't remember what it would be called.
Is it an image file?
Renate NST said:
Well, yes, but it's not a big deal. It's fixable.
You need something on an SD card, Noogie, Clockwork Recovery, one of the Nooters.
I'd use Noogie on an SD card and copy your backup to the internal SD card.
You do have a backup?
Click to expand...
Click to collapse
I found a file called "SalsichaNooter.img" and wrote it to my sd card via winimage32.
Am I on the right path?
If so,what should I do with it?
That's to say, you don't have a full backup?
The important thing is to always make sure you have a copy of the stuff on the mmcblk0p2 (/rom) partition.
That has all the stuff that is unique to your Nook.
There is also a backup copy on mmcblk0p3 under rombackup.zip
There's a lot of ways to get out of this situation.
I mentioned the Nooters for completeness.
I've never used one and I don't know a lot about them.
My preference would be for putting Noogie on an SD card,
looking at the internal SD card boot partition over USB and copying what's broken from the software update for 1.1.2
Renate NST said:
That's to say, you don't have a full backup?
The important thing is to always make sure you have a copy of the stuff on the mmcblk0p2 (/rom) partition.
That has all the stuff that is unique to your Nook.
There is also a backup copy on mmcblk0p3 under rombackup.zip
There's a lot of ways to get out of this situation.
I mentioned the Nooters for completeness.
I've never used one and I don't know a lot about them.
My preference would be for putting Noogie on an SD card,
looking at the internal SD card boot partition over USB and copying what's broken from the software update for 1.1.2
Click to expand...
Click to collapse
I just found my backup!!! It's called "nook_touch_backup.img" and is about 1.82 GB.
If my Nook won't power up at all, is it possible to restore this image to the internal memory?
Also, when I plug in my Nook via USB nothing shows up in my device manager.
centralpark said:
If my Nook won't power up at all, is it possible to restore this image to the internal memory?
Click to expand...
Click to collapse
Yes, if it is your backup.
Put Noogie on an SD card, use Win32DiskImager to copy the image to the internal memory.
Renate NST said:
Yes, if it is your backup.
Put Noogie on an SD card, use Win32DiskImager to copy the image to the internal memory.
Click to expand...
Click to collapse
My Nook will not turn on even after putting Noogie on my external SD card and then placing it back in my Nook.
Also, my Nook no longer shows up in my device manager :crying:
centralpark said:
Also, my Nook no longer shows up in my device manager
Click to expand...
Click to collapse
Well, the Nook is a composite USB device.
It shows up under "Android Phone" or whatever.
It also shows up under USB Mass Storage devices.
It should get a drive letter.
If it doesn't, go to Disk Management and futz and give it one.
Then use Win32DiskImager to write your backup to it.
Renate NST said:
Well, the Nook is a composite USB device.
It shows up under "Android Phone" or whatever.
It also shows up under USB Mass Storage devices.
It should get a drive letter.
If it doesn't, go to Disk Management and futz and give it one.
Then use Win32DiskImager to write your backup to it.
Click to expand...
Click to collapse
For some reason, my nook will not show up in "Device Manager" or "Disk Management" on any computer that I have.
It is stuck on the "turned off completely" screen.
No matter what I try, even though the green led light comes on when I plug it in via usb cable, it simply won't power up. The screen won't flicker...nothing.
I presume that you've tried all sorts of long pushes on the power button, 30 seconds?
You may be in that state where it needs the battery disconnect and reconnected.
Some have had luck with waiting until it discharges itself dead-dead.
OTOH, some got in this situation from doing that.
Renate NST said:
I presume that you've tried all sorts of long pushes on the power button, 30 seconds?
You may be in that state where it needs the battery disconnect and reconnected.
Some have had luck with waiting until it discharges itself dead-dead.
OTOH, some got in this situation from doing that.
Click to expand...
Click to collapse
I've tried multiple long pushes of power button etc.
Should the screen go totally blank when it's dead-dead?
I think somehow I deleted important files from the root directory last night using adb.
Removing the battery for 20 minutes made no difference.
Thanks so much for all your help.
Are you trying to get to "Rooted Forever" with noogie?
Renate NST said:
Are you trying to get to "Rooted Forever" with noogie?
Click to expand...
Click to collapse
I'm trying to get anything to work
Neither flashing noogie or clockworkmod to my external sdcard via win32diskimager caused my nook to come back to life.
I do know that my battery is good since last night it had over 90%.
No matter what I've tried, nothing causes my nook to show up in my device manager.
I only briefly see a message about "OMAP 3630" failed to install drivers.
The OMAP 3630 popups when it tries to boot off the USB.
That means that something that you have has a good mlo and u-boot.bin in the boot partition.
Whatever is after that is broken.
I would guess that your SD card is not written correctly.
It's a VFAT, look what's on there.
Is it the first (and only presumably) partition?
Is it marked active and bootable?
Progress
Renate NST said:
The OMAP 3630 popups when it tries to boot off the USB.
That means that something that you have has a good mlo and u-boot.bin in the boot partition.
Whatever is after that is broken.
I would guess that your SD card is not written correctly.
It's a VFAT, look what's on there.
Is it the first (and only presumably) partition?
Is it marked active and bootable?
Click to expand...
Click to collapse
Hip hip hurray!! Finally, I got sd_2gb_clockwork-rc2.zip to create a bootable sdcard.
I was then able to boot into cwm.
However, my card did not have enough space to put my noot_touch_backup file onto the card.
Also, the internal nook drive still is not showing up on my windows computers.
My card has about 1.74 gb left of free space.
Do you have any ideas on where to go from here?
Oh my goodness!!
I used win32diskimager to restore my nook_touch_backup file to my sdcard...then i rebooted and my old system is back up and running!!
I have no idea why, but I'm scared to turn my nook off again.
ok , i was have the same problem "kinda" , well follow my instruction hope it works with u
connect ur nook with ur computer for 15 mints .... or more .... between that there's a screen will show to u that ur nook cant power on ..... also ....tell me what led show to u "green or orange"
try and replay me
best regards
---------- Post added at 01:10 AM ---------- Previous post was at 01:07 AM ----------
centralpark said:
Hip hip hurray!! Finally, I got sd_2gb_clockwork-rc2.zip to create a bootable sdcard.
I was then able to boot into cwm.
However, my card did not have enough space to put my noot_touch_backup file onto the card.
Also, the internal nook drive still is not showing up on my windows computers.
My card has about 1.74 gb left of free space.
Do you have any ideas on where to go from here?
Oh my goodness!!
I used win32diskimager to restore my nook_touch_backup file to my sdcard...then i rebooted and my old system is back up and running!!
I have no idea why, but I'm scared to turn my nook off again.
Click to expand...
Click to collapse
good to hear .... but i was have the same problem "kinda" .... anyway
congratulations
Thank You
Renate NST said:
The OMAP 3630 popups when it tries to boot off the USB.
That means that something that you have has a good mlo and u-boot.bin in the boot partition.
Whatever is after that is broken.
I would guess that your SD card is not written correctly.
It's a VFAT, look what's on there.
Is it the first (and only presumably) partition?
Is it marked active and bootable?
Click to expand...
Click to collapse
Thank you for taking the time to point me in the right direction today! I truly appreciate it!! :victory:
Hi, so I've tried everything I can think of to restore my Nook to the stock 1.4.1 but nothing has worked and I've given up before I break anything else...
This all started when I was trying to install the CM7.2/CM9 dual boot from SD card - I burned the image to the SD card and booted but the device just hanged at a black screen (for a lot longer than it should have) after the CM "loading" startup screen.. I tried removing the SD card after holding the power button to turn it off but it then refused to boot to the EMMC stock OS... Somehow (I've only ever used SD card CM ROM's) an old CWM install (v.3.0.2 or something) was installed on the internal memory that booted when I tried to launch a factory reset (Power + N + vol+).
I then followed an older guide to restore to stock by formatting the /system and /data and installing a .zip from sd card (the nookcolor_1_4_1_signed.zip) but it failed with a (bad) error....
Now I don't know what to do. The device now hangs at "Read Forever" and the internal CWM is gone, as well as everything else I'm assuming... It will boot into CWM if it's installed on an SD card, but without that it will just reboot into Read Forever when I try to turn it off...
An aside, but now that I've checked with external CWM again, it appears there is now a "/system1, /system2, /data1, and /data2" file on the EMMC...
TL;DR: How do I restore Nook Color to stock 1.4.1 from CWM installed on an external SD card without flagging a "(bad)" error with the install?
Thank you for any help and I hope I haven't bricked this device... Hopefully this is just a case of ignorance on my part
EDIT: I've tried re-downloading the 1.4.1 and even a 1.2 signed ROM with out success. I haven't rooted the device, but I do not know how the internal CWM got there, as well as the fact that the external SD dual boot didn't work.. I'm using a new SanDisk Ultra 16GB SDHC Class 10 card if it makes a difference..
Could not having rooted the Nook be the only cause?
I had successfully dual booted the CM7.2 and CM9 for months until my old 16GB card broke... This was the new card I bought last week and it's been nothing but problems, exacerbated by myself, probably :/
I
cekren said:
Hi, so I've tried everything I can think of to restore my Nook to the stock 1.4.1 but nothing has worked and I've given up before I break anything else...
This all started when I was trying to install the CM7.2/CM9 dual boot from SD card - I burned the image to the SD card and booted but the device just hanged at a black screen (for a lot longer than it should have) after the CM "loading" startup screen.. I tried removing the SD card after holding the power button to turn it off but it then refused to boot to the EMMC stock OS... Somehow (I've only ever used SD card CM ROM's) an old CWM install (v.3.0.2 or something) was installed on the internal memory that booted when I tried to launch a factory reset (Power + N + vol+).
I then followed an older guide to restore to stock by formatting the /system and /data and installing a .zip from sd card (the nookcolor_1_4_1_signed.zip) but it failed with a (bad) error....
Now I don't know what to do. The device now hangs at "Read Forever" and the internal CWM is gone, as well as everything else I'm assuming... It will boot into CWM if it's installed on an SD card, but without that it will just reboot into Read Forever when I try to turn it off...
An aside, but now that I've checked with external CWM again, it appears there is now a "/system1, /system2, /data1, and /data2" file on the EMMC...
TL;DR: How do I restore Nook Color to stock 1.4.1 from CWM installed on an external SD card without flagging a "(bad)" error with the install?
Thank you for any help and I hope I haven't bricked this device... Hopefully this is just a case of ignorance on my part
EDIT: I've tried re-downloading the 1.4.1 and even a 1.2 signed ROM with out success. I haven't rooted the device, but I do not know how the internal CWM got there, as well as the fact that the external SD dual boot didn't work.. I'm using a new SanDisk Ultra 16GB SDHC Class 10 card if it makes a difference..
Could not having rooted the Nook be the only cause?
I had successfully dual booted the CM7.2 and CM9 for months until my old 16GB card broke... This was the new card I bought last week and it's been nothing but problems, exacerbated by myself, probably :/
Click to expand...
Click to collapse
Easy solution. Go to my tips thread linked in my signature and make a bootable CWM card per item A10. Then flash my format 567 zip. Then go to item A15 and download my 1.4.3 stock ROM and flash that. Boot up, register and you are golden.
If you want to put a ROM on SD go to my updated SD instruction thread also in my signature.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
I
Easy solution. Go to my tips thread linked in my signature and make a bootable CWM card per item A10. Then flash my format 567 zip. Then go to item A15 and download my 1.4.3 stock ROM and flash that. Boot up, register and you are golden.
If you want to put a ROM on SD go to my updated SD instruction thread also in my signature.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
Thanks! I'll try that right when I get home..
EDIT - Awesome - It works! The dual boot card also works!
EDIT 2 - so... booting from the SD card still doesn't work... It just hangs at the Cyanogen7 boot video looping over and over (left to go to the store, got back and it was still looping)... holding power button down just resets the device while the SD card is in, doesn't actually shut down for more than 4 seconds or so....
Should I post this as a new thread? I'll try searching for anybody else having this problem in the mean time...
cekren said:
Thanks! I'll try that right when I get home..
EDIT - Awesome - It works! The dual boot card also works!
EDIT 2 - so... booting from the SD card still doesn't work... It just hangs at the Cyanogen7 boot video looping over and over (left to go to the store, got back and it was still looping)... holding power button down just resets the device while the SD card is in, doesn't actually shut down for more than 4 seconds or so....
Should I post this as a new thread? I'll try searching for anybody else having this problem in the mean time...
Click to expand...
Click to collapse
Are you using Racks' dual boot SD? If so, how recent is it? You might want to go to his special CWM and clear dalvik cache and try rebooting again.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
Are you using Racks' dual boot SD? If so, how recent is it? You might want to go to his special CWM and clear dalvik cache and try rebooting again.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
Yeah, I used the Dual Boot image I downloaded a couple days ago from Techerrata (I used the one at the top of the list that had the most downloads, connection I'm on is blocking Techerrata so I can't get the exact name ATM) with burned with Win32DiskImager, popped in the card and turned on but it just hangs. I'll try clearing the dalvik cache with his CWM image and see if it fixes anything..
EDIT - Ok, I tried clearing the cache, but it gives me the following error:
E:unkown volume path [/data]
I checked the Mounts and Storage Menu, and it looks like I still have "/system1, /system2, /data1, and /data2" directories, did the 567 format.zip not take care of whatever file structure or partition these were kept on in the EMMC?
cekren said:
Yeah, I used the Dual Boot image I downloaded a couple days ago from Techerrata (I used the one at the top of the list that had the most downloads, connection I'm on is blocking Techerrata so I can't get the exact name ATM) with burned with Win32DiskImager, popped in the card and turned on but it just hangs. I'll try clearing the dalvik cache with his CWM image and see if it fixes anything..
EDIT - Ok, I tried clearing the cache, but it gives me the following error:
E:unkown volume path [/data]
I checked the Mounts and Storage Menu, and it looks like I still have "/system1, /system2, /data1, and /data2" directories, did the 567 format.zip not take care of whatever file structure or partition these were kept on in the EMMC?
Click to expand...
Click to collapse
The format 567 zip was for clearing the partitions on internal memory (emmc). Those partitions you are looking at are on the SD card (system1, etc).
You might just try clearing cache with his cwm rather than dalvik cache. You also might get a better response posting your dual boot question on the dual boot thread. I don't know a lot about the dual boot.
leapinlar said:
The format 567 zip was for clearing the partitions on internal memory (emmc). Those partitions you are looking at are on the SD card (system1, etc).
You might just try clearing cache with his cwm rather than dalvik cache. You also might get a better response posting your dual boot question on the dual boot thread. I don't know a lot about the dual boot.
Click to expand...
Click to collapse
Sounds good, I'll try that. Thanks again for all the help, though!
One thing to note... the initial boot does take a while and sits on a black screen while the cache image and formatted. Racks has put that into the dual boots with loop mounting so each bootable system will have its own cache space and avoid overwriting cache data from nother ROM.
DizzyDen said:
One thing to note... the initial boot does take a while and sits on a black screen while the cache image and formatted. Racks has put that into the dual boots with loop mounting so each bootable system will have its own cache space and avoid overwriting cache data from nother ROM.
Click to expand...
Click to collapse
Good to know, but should it really take more than 90 minutes to initially boot? I let it boot up to CM7 on a freshly burned Class 10 card and left for the store, when I got back it was still at the boot video, watched it for another 5 minutes and it still didn't do anything... I don't really know what the problem is, could it be the card?
I have seen it take up to10 minutes, but 90 is definately excessive... I would suspect the card being the issue... class 10 cards are not good for running any operating system from. While they have exceptional sustained read/write speeds... they (generally) have poor random small read/write speeds, and this is the types of files used by an operating system.
DizzyDen said:
I have seen it take up to10 minutes, but 90 is definately excessive... I would suspect the card being the issue... class 10 cards are not good for running any operating system from. While they have exceptional sustained read/write speeds... they (generally) have poor random small read/write speeds, and this is the types of files used by an operating system.
Click to expand...
Click to collapse
Oh.. ok, well good to know! I'll pick up a different card today and see if that will work.
I got the Mirage 7.2 to work, by writing the "generic_sd.img" to the card, the coping the .zip download to the boot partition (renaming it to "update-cm7-mirage.zip" so the generic loader would see it)...
I inserted the card, booted, and Tux showed up and it ran through partitioning the card, expanding the mirage zip, and shutting down. However, when I turned it back on, it showed the Cyanogen mod bootloader, and I selected "SD Normal" but Tux showed up again and it went through trying to partition again (which it said was not needed, so it skipped) and finding an update- / .zip file (which it deleted when it expanded it before), same with the SD recovery boot option... Should I just try a new card?
EDIT - So, I was sick of messing with SD card booting, and realized I really don't care if I have the stock OS on it anymore since my warranty is about to run out anyway, I just rooted it an installed Mirage 7.2 and it works! Thanks for the help with the SD Card problems, though!