Related
My nook color stays not much longer than 1min after loading all the apps & just after that it reboots. I've tried installing a fresh rom couple of times & wiping each & everything but just after installing all the apps again, it reboots. Have tried both by installing it manually & restoring through titanium backup as well, but same result. It works fine only when I remove my micro sd. I know that some apps doesn't works when installing in micro sd & that's why I've installed all my apps in internal memory. I never faced that issue when I was using Phiremod v6.3 build. Recently after moving into the latest nightly build, this issue occurred. Please tell me how can I resolve this issue? I've been trying to find the solution from so many days but couldn't able to find. Thanks
You could use ROM Manager to restore the last ROM if you did a backup or just reinstall it. I am a little confused about what you mean by loading all the apps. Apps are generally loaded as you use them, not at boot up. When you first boot up you can usually see the SD card icon at the bottom of the screen before it gets mounted. It is possible the card got corrupted. If you don't have anything on it but app backups and it works fine when the card is out you could try reformatting the card on your PC or with a camera that uses micro SDHC cards.
You also might have a misbehaving app loading on startup.
When I first boot the system, the sd card icon shows at the bottom of the screen & disappears after loading all the games from it. After that I can see all my apps & games in app drawer but after a min, it gets reboot. I only have games in sd card, not a single app & neither any app in my internal memory which loads at startup.
Well if the nook boots and runs just fine without the SD-card inserted, then we can be pretty certain that something on the card is messed up. Lot's of possibilities: Corrupted .apk file, partially corrupted file structure on the SD-card itself, Hell it could also be auto-update panicking because it's trying to update an app that has yet to load off the SD-card.
First thing I would try is formatting the SD-card within CM7.
Also try turning off auto-update
If that fails, connect the SD-card to your computer and scan it with windows to check for any file table corruption.
If that fails, it's hard times ahead for you. You'll have to go through the apps one-by-one to see which one is being the little bastard.
Good luck.
Thanx for The help. But all I have on my SD card is just game. Before installing anything on my internal memory, I restored my games backup 1st to my SD card through titanium backup. It was then working absolutely fine. After that I installed apps manually just to see which app is causung error. But all were installed without any problem, used for a while then I manually reboot. Since then I am getting this issue.
Hi,
Having a with a Nook where it will not complete boot of CM7 which is installed on an SD card. Instead it boots into the Nook Color software.
I hold down the power button till I see the green Cyanogenmod logo with the Loading text, which I think means it is booting from the SD card (I can get it to boot into CM recover), then the screen goes blank and something goes wrong and the boot process continous with the 'n' screen and eventually loads the Nook boot animation and ends with the Nook software loaded. The nook software seems to be running fine except I can't get the SD card to boot all the way.
I've tried 2 known good SD cards, which boot without problems on my second nook, so I know it is not the SD card. I suspect something got corrupted with the boot process files, so I have been trying to find a way to overwrite the existing files with a virgin copy.
1) Can't get ADB running, I suspect the ADB route is only possible if I have the nook booting in a rooted CM7 in the first place (if some one could confirm that would help)
2) I have tried the x8 boot fail reset as well as the erase and deregister option in the nook software with no change in the above behaviour.
3) My last hope is to do an update back to stock using the recovery mode of the SD card. I can copy an updater file to the small partition of the SD card that is visible on Windows. I found a 1.2 stock updater, but it is ~200MB which is too big to fit on the SD card. If someone could point me to a smaller updater or a sd image with CWM and >200MB space that would be very helpful. TY!
What exactly are you trying to do? If you are just trying to set up dual-boot of CM off of your SD card, you don't need to do anything to the stock B&N internal install. I've had good luck using the procedure in the [ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards thread.
Are you sure the initial CM install on your SD card went well? It's known to be very particular (see top of that thread) about what SD cards work. The first few times I tried, I didn't realize there were error when CM was initially extracted which led to similar failures. From what you've described, the SD setup is failing. Normally, you don't need to worry too much about what's on the internal emmc setup of the Nook Color.
bobstro said:
What exactly are you trying to do? If you are just trying to set up dual-boot of CM off of your SD card, you don't need to do anything to the stock B&N internal install. I've had good luck using the procedure in the [ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards thread.
Are you sure the initial CM install on your SD card went well? It's known to be very particular (see top of that thread) about what SD cards work. The first few times I tried, I didn't realize there were error when CM was initially extracted which led to similar failures. From what you've described, the SD setup is failing. Normally, you don't need to worry too much about what's on the internal emmc setup of the Nook Color.
Click to expand...
Click to collapse
Hi bobsto, some background. I've been using CM7 on a microSD for several weeks now. I dual boot between Nook SW and CM7 that way. I've been using the link you posted above to create the SD cards and so far I have not had to touch the eMMC files at all.
Then a friend messed around with the Nook I gave them with CM7 on an SD card. I don't what the friend did, but when I got the Nook back it would not boot into CM7. I pulled my SD card from my working Nook and it wouldn't work either. So I'm guessing someone screwed with the Nook internal files. So I am trying the factory restore of the Nook SW to see if that will fix the problem and allow me to load CM7 from the SD card again. Interestingly Nookie will boot from SD and CM7 won't. Still trying stuff to see what will fix the problem. Suggestions are welcome.
sfsilicon said:
Hi bobsto, some background. I've been using CM7 on a microSD for several weeks now. I dual boot between Nook SW and CM7 that way. I've been using the link you posted above to create the SD cards and so far I have not had to touch the eMMC files at all.
Then a friend messed around with the Nook I gave them with CM7 on an SD card. I don't what the friend did, but when I got the Nook back it would not boot into CM7. I pulled my SD card from my working Nook and it wouldn't work either. So I'm guessing someone screwed with the Nook internal files. So I am trying the factory restore of the Nook SW to see if that will fix the problem and allow me to load CM7 from the SD card again. Interestingly Nookie will boot from SD and CM7 won't. Still trying stuff to see what will fix the problem. Suggestions are welcome.
Click to expand...
Click to collapse
Gosh, I wish someone could figure this out.
I restored original stock after a full CM7 root and it went fine but I can NOT get a dual boot sd card to work.
It seems to install but when I reboot it shows CM7 screen briefly then always boots to Nook OS.
Tried many many different cards and image writers and CM7's and even a card from my other Nook which I know works.
It will not boot into the CM7 from the SDcard.
Any help?
grohval said:
Gosh, I wish someone could figure this out.
I restored original stock after a full CM7 root and it went fine but I can NOT get a dual boot sd card to work.
It seems to install but when I reboot it shows CM7 screen briefly then always boots to Nook OS.
Tried many many different cards and image writers and CM7's and even a card from my other Nook which I know works.
It will not boot into the CM7 from the SDcard.
Any help?
Click to expand...
Click to collapse
Try this for CM7 - http://forum.xda-developers.com/showthread.php?t=1022786
Nookie also works - http://forum.xda-developers.com/showthread.php?t=922324
Not sure what is going on, but it worked for me.
sfsilicon said:
Try this for CM7 - http://forum.xda-developers.com/showthread.php?t=1022786
Nookie also works - http://forum.xda-developers.com/showthread.php?t=922324
Not sure what is going on, but it worked for me.
Click to expand...
Click to collapse
Thanks, the first worked like a charm!
I made a 32gb CM7 sdcard.
Still wish I could have got the size-agnostic card to work, it bugs me when I can't figure stuff out.
grohval said:
Still wish I could have got the size-agnostic card to work, it bugs me when I can't figure stuff out.
Click to expand...
Click to collapse
I'm in the same boat, but after 1 day of research and trial and error I'm happy it works. Maybe someone smarter will see this and know the answer and solve my problem curiousity.
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.
[Q] Chronic "Unexpected Lack of Boot Partition on the SD card! Please Report"
Hi,
First let me say - YES, i have searched all of the forums here (and a number of other sites) and seem to have tried almost every option.
I have Chronic "Unexpected Lack of Boot Partition on the SD card! Please Report" problems. The farthest I get guaranteed is the cyanogenmod boot and menu (if I try and bring it up). I'm simply trying to get the SD card with cm7 to boot reliably and not eventually loose the boot partition.
Off and on since spring I was able to burn a CM7 image (verygreen's size agnostic, and one or two others I have since lost track of) to a SD card; have had it boot to cm7 and it work for awhile - but then eventual degraded into the no partition found error. the majority of the time it just doesn't work and results in that annoying purple black screen.
When it does work, it only works for awhile and then the boot partition can't be found; a few very small 3 of times - if I copied a new update it woke back up ad worked for a couple of reboots then lost the partition again.
Anybody got time to take pity on my melted brain and take a few guesses?
Clearly I'm not only missing something - but as things have gotten worse, am now missing more (if that is possible) as I'm going backwards to see why it no longer works at all.
At this point wrong has happened so often, I'm just lost on what even worked way back when I started.
I'm trying to backtrack to where it at least worked a little for a few days...but noob world is decaying into worse world.
I tried a couple of other, older processes and a multiboot menu one that seemed promising (plus could handle the new naming conventions for 7.2 CM7); but that one never even got past the missing boot partition.
I have tried approx 10 2gb SDCards, Sandisk, Kingston, Unknown; Class 4 and mixed.
I have tried 3 8GB SD Cards, Sandisk, class 4
I have tried 1 16gb SD Card, Sandisk, class 4
I have tried a Vivitar Micro SD Card Reader
I have tried the micro SD card Adapters in a laptop, and then in a sandisk USB adapter.
I even tried doing it all using the Nook color via a USB cable.
I even tried leaving the nook color off and connecting the USB cable to the PC to initiate a boot.
Using Windskimager
Using SD formatter
Have formatted Full erase and overwrite.
Tried leaving partition size alone
Tried partition resizing up to 250mb
Tried cm7 zip alone and with gapps
WinXP on 2 desktops and a laptop
It sounds like you have run the gamut of attempted resolutions.
That message is part of the verygreen partitioning script that runs every time the verygreen recovery is run. So, that means the normal boot kernel for CM7 is not loading.
The way the verygreen SD should operate is it starts with uImage and uRamdisk on the boot partition. Those are verygreen's recovery files. The first time it is booted, it looks at your emmc to be sure it is a nook. Then it looks at the SD to see if it has been partitioned yet. If it is not, it partitions it into those partitions necessary for installing ROMs. After partitioning, it looks for a zip to install. If it does not find one, it shuts down and the next time it boots it does the same thing until it finds the first ROM zip to install. If it finds one, it installs it. The first time it installs a ROM, it renames those uImage and uRamdisk verygreen files to uRecImg and uRecRam and they become the verygreen recovery files. And it installs new uImage and uRamdisk files from the zip to become your CM kernel and ramdisk. These are what normally will load in the future to start CM.
Now, with the disk partitioned and CM installed, ordinarily, after the cyanomod logo comes up, it boots by default to CM via the uImage and uRamdisk files. If you intercede with the boot menu and tell it to boot to SD recovery, it looks for uRecImg and uRecRam to load the verygreen recovery. If that is loaded, the verygreen script does all its checking again, it verifies that emmc is a nook, then tries to verify if the SD is partitioned. If it is, it looks for a new zip to install. If, in checking to see if it is partitioned, it cannot find partition 1, it gives that message that has been bugging you.
So I see two things that are happening to you.
First, it is booting to the verygreen recovery first instead of CM. That could be due to a recovery bootloop happening. Look at my tips thread linked in my signature to see an explanation as to what that is and how to possibly get out of it.
Second, after it boots to the verygreen recovery, it does its checking and cannot find partition 1 of the SD and gives you that message.
What I cannot understand is, if you have no partition 1 on your SD, how is it booting to the verygreen recovery?
What you have not told us is what you have on emmc. Stock? Does it boot properly without the SD installed? Or does it go to stock recovery?
After this happens to you again, take the card out and put it in the PC. Tell us what you see. What files are there? Maybe look at it with Mini-Tool Partition Manager and see what partitions it reports.
leapinlar said:
What you have not told us is what you have on emmc. Stock? Does it boot properly without the SD installed? Or does it go to stock recovery?
Click to expand...
Click to collapse
Ditto on that - especially as it boots happily to that error message time after time after the green cyanomod screen appears and I can also do the menu trick to get it to go into recovery.
Just as a clarifier: A number of times it tried to do the install (text flowing by) and at the end claims it can't find the boot partition - odd (unless I have less of an idea of what I am doing than I think) as isn't all that running from that partition? A fairly even number of times it doesn't even run the install and just errors out right up front.
Once in a great while it all works, and I'm good for a few days - but eventually upon rebooting to get it back to normal (either by menu choice or by pulling the sd card) - all I get is that lack of partition again.
leapinlar said:
What you have not told us is what you have on emmc. Stock? Does it boot properly without the SD installed? Or does it go to stock recovery?
Click to expand...
Click to collapse
Yes with the SD card out it boots to stock, although a few time what looked like the CWMod menu came up after I shut down and started up without the SD card installed. Maybe only 2 or 3 times out of WAY to many boots to stock so the kids could read their books while I went to work.
I have even tried resetting the nook to factory on the off chance I did something dumb while mucking about to cause that.
leapinlar said:
After this happens to you again, take the card out and put it in the PC. Tell us what you see. What files are there? Maybe look at it with Mini-Tool Partition Manager and see what partitions it reports.
Click to expand...
Click to collapse
Will do so later tonight and will read the notes in your signature as well.
I saw something go by about the boot partition having to start at the 63 block or something - I can't believe ALL my SDcard adapters / writers are bad, but could the nook reader be screwy? Anyway to do a real test? I've been using the Easeus Partition Manager, but will try the Mini-Tool Partition Manager.
Thanks for the step by step explanation of exactly what happens in the process so I can again get a handle on what it's all doing. That all makes sense to what it looks like it tries to do. Deeply appreciate the time!.
You know, I am beginning to suspect something is wrong with your card reader built into the nook. Some sort of intermittent thing like a pin not making a good connection to the card. Put an ordinary SD in it and see if your stock can consistently read it.
Is your unit still under warranty? You might want to explore seeing if you can get it replaced.
Your downloaded verygreen image might be corrupted. Have you tried re-downloading it?
Sent from my NookColor using xda app-developers app
leapinlar said:
You know, I am beginning to suspect something is wrong with your card reader built into the nook. Some sort of intermittent thing like a pin not making a good connection to the card. Put an ordinary SD in it and see if your stock can consistently read it.
Is your unit still under warranty? You might want to explore seeing if you can get it replaced.
Click to expand...
Click to collapse
I had thought of that too - at stock it seems to have no problems reading consistently; I've done surface tests using partition manager - but haven't located any real other options of hard testing like once done for hard drives.
Plus the fact that sometimes, it will work for days before it craps out.
j8048188 said:
Your downloaded verygreen image might be corrupted. Have you tried re-downloading it?
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
A number of times - I went through and wiped all my downloads for the latest try.
Okay So As I mentioned I went back and wiped everything I had downloaded and restarted (again).
Current status is it's working BUT:
suspiciously too easy this time, worked first shot
- (having said that, I've had looking stupid and asking suddenly means it all starts working - so if it's that I'm good with this)
I've only rebooted into CM7, not back to stock at any time
Have not removed the SD card
I've not had time to load up the apps I like, just the kids games
- (sometimes I think it's the more wanted, the less reliable)
Obviously because I haven't removed the SD card, i haven't been able to retry things enough to recreate the other problems of boots right, yet can't find the partition when it really counts.
Changes (listing stupid things too, just because):
-Went back to my sandisk class 4 16gb HC card
-changed USB adapter back to sandisk one, using a sandisk micro to SD adapter that specifically says sdhc (although I think that is really just marketing
-Formatted the SD in the Nook x2, and did not use SDformatter
-Looked at the partition on the card with MiniTool not Easeus partition manager
-There is a step in verygreen's where you pop the card out and reconnect to the PC BEFORE adding the cm zip, made sure to do that - but could swear I had done it before.
Full painful boring steps that SO far has gotten it past the first stage of creation (again the full test is when I boot into stock a few times, or remove the SDcard for anything, or load my really wanted apps on the android side):
--Also note my lack of class 4 Sandisk cards, I only had one after all. BUT I have had this all work to this point with the 16gb only to have it go south.--
Painful details is so I can catch what is really worthwhile different as even WHEN I get it to work, I'm going back to try all the other cards because it worked so oddly and failed so oddly and differently - but that's just me.
> The 2GBs are:
6 Sandisk SD, don't see any class Rating
2 no brand SD, don't see any class Rating
1 Kingston SD, don't see any class Rating
> The 8gb are SDHC "Adata" Class 4 SDHC
> The 16gb is a Sandisk Class 4 SDHC
Using the 16GB Sandisk Class 4
--------------------------------
> Nook booted to stock
Inserted SD Card
Unmounted
Formatted sucessfully
unmounted and removed
> Put in Red SD / SDHC Adapter
Put in Sandisk MicroMate SDHC to USB Adapter
Put in Front USB spot
> Mounted as E Drive
E Drive shows standard Nook Folders:
.amdroid_secure
B&N Downloads
LOST.DIR
My files
> MiniTool Partition Wizard
Surface test = all good.
>Write the image on your SD card
Used Win 32 Disk Imager
After done with writing, eject and then re-insert the uSD card into your computer.
Two Partitions - 118 and 14.72gb
>Copied to card:
update-cm-7.1.0-encore-signed.zip
Installed correctly
configured wireless
Rebooted = OK
Rebooted = OK
>Turned off
Removed SD Card
Put in Red SD / SDHC Adapter
Put in Sandisk MicroMate SDHC to USB Adapter
Put in Front USB spot
copied gapps
>Boot into Recovery
Gapps installed
> boot
all good
did all set ups like before
added apps (7 games for kids)
rebooted twice
started using
added one app I really like (newshog)
Listening for drumming... nothing so far (Dr. Who reference)
I'm going to go the weekend before rebooting to stock as I can do some adding, and rebooting to android.
Maybe backup the droid side this time around.
THEN the death tests on Monday
-thanks for listening_
p.s. - Yes, I still suspect the card reader somewhat as REMOVING may be where it breaks down.
However, once or twice when I had the Unexpected lack of boot partition error - I was able to bring it back by doing a CM7 update via recovery, despite it refusing to find the boot partiton immediately previously - of course that means the SDcard was removed and reinserted. Most time reinsertion = no help.
You do not need to remove the SD to test booting to emmc. Just press and hold the n button during the boot until the boot menu comes up. Then select emmc/normal and boot. It will boot to stock. The only problem with doing that is now your SD boot partition is 'sdcard'. But should work for testing stock.
leapinlar said:
You do not need to remove the SD to test booting to emmc. Just press and hold the n button during the boot until the boot menu comes up. Then select emmc/normal and boot. It will boot to stock. The only problem with doing that is now your SD boot partition is 'sdcard'. But should work for testing stock.
Click to expand...
Click to collapse
Yes, I know - but it's two separate tests to see which one caused the problem.
Turns out that neither was needed - it was easier to create; my son simply turned it off (not a reboot cycle as I had been doing which worked).
When it was turned on, it no longer boots - it goes straight to BSOD (actually deep purple).
Booting into recovery gets me:
Penguin Logo
rcS!
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
Error! Unexpected lack of boot partition on the SDCARD!
Please Report!
Poweroff when ready
Since I'm till held to the noob reposting limit of once every 5 minutes and the captha I can barely read - I'll post MiniTool result in about 5 minutes. I'll link a screen capture if i can here.
I tried to boot per menu to the EMMC stock; Clockworkmod Recovery v3.2.0.1 came up. I know I did emmc and what ever the second default is (which should be normal) - I'm pretty sure it was normal.
I offed it and did the same and confirmed it was the default; THIS time it came up Nook stock.
Is there some way I installed something to the stock NOOK and didn't remove it when I restored to factory? The other day I did the restore from that same clockworkmod screen NOT from the stock Nook environment.
I'm wondering if I somehow created my own monster way back when I first started this and was playing in the android environment.
I just edited what I wrote a few seconds ago. The reason it went to emmc recovery is because the recovery flag was not reset when that SD Recovery told you that error. Did you read my tips about recovery bootloops? When you exited 3.2.0.1, it cleared the flag and booted normally.
I still suspect hardware issues.
Just for Ha, Ha's I hooked the Nook via USB to the PC.
G Drive "Removable Disk G" (wants a disk to be inserted)
E Drive "MyNookColor" ( Lots of what I assume to be standard Nook folders.
See my edit above.
Attachement # 1 SD Card from Mycomputer:
Attachment # 2 MiniTool View of SD Card
Boot Partition
Properties using Minitool Partition Wizard (attached):
Used
Partition Info
File System Info
Surface Test of Boot Partition:
Perfect - so no picture.
This is SO aggravating - I almost would accept just knowing why rebooting wrecks something if I knew WHAT).
leapinlar said:
I just edited what I wrote a few seconds ago. The reason it went to emmc recovery is because the recovery flag was not reset when that SD Recovery told you that error. Did you read my tips about recovery bootloops? When you exited 3.2.0.1, it cleared the flag and booted normally.
I still suspect hardware issues.
Click to expand...
Click to collapse
Sorry, apparently not closely enough - got lots of time again.
....didn't expect that anyone would be watching, was busy posting pictures so I could go away and read and think...
Probably is hardware - wish I had some way to vigorously test that, I get that basic use in Nook Stock doesn't really prove everything is good.
Plus I bought refurbished and I have to go dig up the warranty, it was months ago, so not too hopeful and boxes long gone. Don't know how nice B&N is, free replacement charger and cord is one thing - whole another refurb unit is different if I can't show stock SD card reading is an issue, not sure how much they check, but I don't think they care about CM7 off a SDcard not working!
Everything looks perfect on that card. All the right files, partition sizes, etc. You have stock on emmc, CWM 3.2.0.1 on emmc recovery.
I still suspect hardware issues. Powering off makes card semi-unreadable. Can still boot to it but when checking for partition information on SD fails.
If you registered your nook, the serial number is all you need. Refurbished usually have a one year warranty. Mine did. Just tell them card reading is intermittent. Which it is. They are pretty generous. You still have stock on there.
Edit: Try just an ordinary SD and power off, reboot, and repeat many times and in between check card reading ability.
leapinlar said:
Everything looks perfect on that card. All the right files, partition sizes, etc. You have stock on emmc, CWM 3.2.0.1 on emmc recovery.
I still suspect hardware issues. Powering off makes card semi-unreadable. Can still boot to it but when checking for partition information on SD fails.
Click to expand...
Click to collapse
Yup, it's really the only thing that hasn't been able to be changed through all of this.
I've mostly gotten these results - I've managed to make it worse as I redid things and apparently got sloppy. But when going back to methodically following instructions I have what I had months ago. I had hoped buying other cards would make it at least act differently.
Thanks for all of the reviews and double checking, at least I now it's not something obvious (but wasn't obvious to me) that I missed along the way!
I'll have to call B&N and see how strict they are and if they take the "It just has trouble reading any SD card consecutively".
Now where was that review of the Nexxus 7.... and I wonder how all the tablet prices are going to drop especially for the Galaxy Tab. Buying is not as fun but I am completely beat with modding failures.
We are too fast with each other. Lol. See my edit above.
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!