cm 10 and cm 10.1 multiple problems - Barnes & Noble Nook Tablet

Hi,
I am using barnes and noble nook tablet, flashed custom recovery cwm based recovery v 6.0.1.9 and the latest nightly : cm-10.1-20130514-NIGHTLY-acclaim.zip, latest gapps: gapps-jb-20130301-signed.zip. I am having few problems, hope I can get some resolution here.
Firstly I am unable to hard rest my tablet, either erase all data in settings or wiping everything from recovery doesn't restore my tablet to the factory state. I have the same wallpaper, lock screen, google account and everything.
The applications I have uninstalled are also shown and I am unable to get rid of them
super user application is not working and crashes on starting the program and also during start up
every application or system process crashes on start up and keeps popping message indefinitely so that the only thing I can do with my tablet is just to press ok for the popup sparing some few second lapses
few error messages are like this:
unfortunately, the process android.process.acore has stopped
unfortunately superuser has stopped
unfortunately, the process com.google.process.gapps has stopped
unfortunately, Exchange services has stopped
unfortunately, Email has stopped
unfortunately, google partner setup has stopped
unfortunately, google play services has stopped
unfortunately, talk has stopped
etc etc, they keep on coming and make me do nothing, I have tried going to recovery and wiping everything including rom cache system factory cache dalvik data etc what all are available, and tried flashing cyanogenmod and gapps again and again, but neither the data is wiped nor are the problems resolved,
Any help is highly appreciated. Thanks in advance..

additional info
i have other problems like settings not getting saved, for example If i enable debugging in developer options, the movement I go back to previous settings and come again to developer options, the setting remains unchecked. Even the about of the tablet is showing older cyanogenmod status like10-20121209-unofficial-acclaim although I flashed it with 10.1 nightly
Please help me. Thank you.

I don't know what went wrong in your installation. It seems very messed up.
If it was me I'd strat from scratch again with the "repart.img" (mentioned in many places here) that restores your device to "fresh out of the box" condition.
It's possible you have messed up ny formatting wiping too much in your desire ti wipe it clean though and if that's the case the repart.img won't work.

asawi said:
I don't know what went wrong in your installation. It seems very messed up.
If it was me I'd strat from scratch again with the "repart.img" (mentioned in many places here) that restores your device to "fresh out of the box" condition.
It's possible you have messed up ny formatting wiping too much in your desire ti wipe it clean though and if that's the case the repart.img won't work.
Click to expand...
Click to collapse
Thanks for reply, dint get time to immediately test, but what happened is I get a green check mark after getting installing new software, after which i am supposed to remove sd card and nook restarts itself, the nook does restart but cyanoboot starts up and cyanogenmod starts up, i am not getting message clearing data. What wrong could i have done?? Thank in advance.

The worst part is even if i load a sd card image with bootable rom also (from succulent), i am getting same errors, everything is crashing, i cant get beyond the start screen...I couldn't understand one thing, if this is a problem with the rom or other formatting, why is sd card image not working and showing the same errors as internal image?? I get the same error messages as described in the first post of this thread even with the sd card image..Any help is highly appreciated..

rammbbs7 said:
The worst part is even if i load a sd card image with bootable rom also (from succulent), i am getting same errors, everything is crashing, i cant get beyond the start screen...I couldn't understand one thing, if this is a problem with the rom or other formatting, why is sd card image not working and showing the same errors as internal image?? I get the same error messages as described in the first post of this thread even with the sd card image..Any help is highly appreciated..
Click to expand...
Click to collapse
It might be that the NT still boots from emmc rather than off SD. Some NTs will only boot off SD from the power-off state and upon insertion of a powered USB cable. If/when the NT successfully boots off SD for the first time it should take you through a series of network and Google account setup screens, that's how you'd know you're running off SD. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more info/pointers on creating bootable SD cards.
Also, if you're going to re-install CM10 down the road, you might want to take a look at http://forum.xda-developers.com/showthread.php?t=2056626.

digixmax said:
It might be that the NT still boots from emmc rather than off SD. Some NTs will only boot off SD from the power-off state and upon insertion of a powered USB cable. If/when the NT successfully boots off SD for the first time it should take you through a series of network and Google account setup screens, that's how you'd know you're running off SD. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more info/pointers on creating bootable SD cards.
Also, if you're going to re-install CM10 down the road, you might want to take a look at http://forum.xda-developers.com/showthread.php?t=2056626.
Click to expand...
Click to collapse
I know clearly that the nook tablet is booting from the sd card, because its asking me to setup new google account etc, but as the keyboard app is crashing, i cant enter my wifi password to continue, also other error messages are also occurring preventing me from doing anything further. Also during start up I am seeing a different version of cyanoboot and recovery which is matching with my sd card's version, further proof that I am booting from my sd card. Could this be any hardware issue other than emmc or rom? Could this be an issue with the RAM or something else. Thanks for support.

Try Albert's way to turn back to stock again
Check out Albert's [Devs] post for making SD card reboot back to BN stock 4.2 and start over...Using the Nightly builds of CM 10 are very UN stable Roms..experimental..If you want clean stable then I recommend using pacman's Rom build or my Favorite build PA Android build I'm currently using now.

Lestwist50 said:
Using the Nightly builds of CM 10 are very UN stable Roms..experimental..If you want clean stable then I recommend using pacman's Rom build or my Favorite build PA Android build I'm currently using now.
Click to expand...
Click to collapse
Strongly disagree, since the current nightly build is in RC5 status, but whatever...
OP: What class of SD card are you booting from? Also, did you flash your touchscreen firmware by any chance?

class 4 sd card, i dont know if i flashed the touchscreen firmware or not, i dint specifically do something like that. I cant even use the repart.img as the its working in the beginning and i getting a green check mark but after booting that, its simply starting the preinstalled cyanogenmod instead of wiping the device. Any further help?? Thanks in advance. It would be nice if any can diagnose whats wrong, whether the hardware or the software. Thank you.

Did you try this? http://forum.xda-developers.com/showthread.php?t=1470910

Related

[Q] CM7 RC1 upgrade issues and questions

I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
kabell4 said:
I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
Click to expand...
Click to collapse
Regarding your nightly question, they are full ROMs...the difference between them is the code that was committed within the previous 24 hours. Of course that also means that, in theory, some of the nightlies could be 100% the same...anyway, the nightlies can be a beautiful thing or a disasterous thing...usually if there's an issue with a nightly it is quickly found by those who flash each nightly and it is brought up around 3.2 million times and it is typically fixed by the next nightly.
Partitioning usually does mean a wipe of data on the SD. Careful!
When I upgraded to a 32GB flash from the stock 2GB from my Aria, I backed up the entire contents and restored on the new one. Apparently there is volume information stored somewhere (not sure where) and the phone couldn't recognize the card and asked me to partition it.
Because I had a backup, I decided to do so, but instead of partitioning for the entire size of the chip, it partitioned only 2GB!
So I had to stick it into a reader and repartition it manually and then selectively restore music, etc back on the card.
After that it worked just fine. So short version: yes it does.
kabell4 said:
I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
Click to expand...
Click to collapse
You will need to creaate an sd-ext partition to fix the issue of installing (larger) apps with CM7.
The best way would be through ROM Manager.
wifi
Installed the RC2 and can't connect to a hidden SSID wifi network.
That is a known issue with the wifi driver on cm7 thus far. Not sure if it will be corrected though. Anyone else know if it is in the works?
"Do you mind if I turn up the AC?"
I believe if you flash to nightly 14 all will be good, not 100% sure though.
TheFurnace said:
That is a known issue with the wifi driver on cm7 thus far. Not sure if it will be corrected though. Anyone else know if it is in the works?
"Do you mind if I turn up the AC?"
Click to expand...
Click to collapse
As far as I know there are no plans to change it. But then again we weren't supposed to get fm radio working either...
Sent from my cm7 Aria using XDA App
Too true. Never know what is coming down the pipeline!
"Do you mind if I turn up the AC?"
stellarhopper said:
You will need to creaate an sd-ext partition to fix the issue of installing (larger) apps with CM7.
The best way would be through ROM Manager.
Click to expand...
Click to collapse
Great input from everyone. Thanks! Following up on the sd-card partitioning... I have a new 8g card and want to more to CM7. If I partition it, what happens when I restore the backed up app using My Backup Root? And, what is the best partition configuration, why, and what info get store in each section (ext)?
Thanks...
kabell4 said:
Great input from everyone. Thanks! Following up on the sd-card partitioning... I have a new 8g card and want to more to CM7. If I partition it, what happens when I restore the backed up app using My Backup Root? And, what is the best partition configuration, why, and what info get store in each section (ext)?
Thanks...
Click to expand...
Click to collapse
The easiest way to partition is using your ROM manager.
Just select the max size for SD-EXT (I think it would got to 512MB), and none for swap.
I'm not sure if this would have any effect on your backup - I myself started out from scratch and got my apps from the market even though I had made an Astro backup...
You will store all your stuff - music, pictures etc in the normal partition. The SD-EXT will be automatically handled by the phone.
Tried flashing Nightly 22 on my Aria from 17. I spent a lot of time customizing 17. Is there a way to keep all of the old home screens? Also, GPS lock isn't working for me. Using MyBackup Root for Apps, but it seems to duplicate the apps?
kabell4 said:
Tried flashing Nightly 22 on my Aria from 17. I spent a lot of time customizing 17. Is there a way to keep all of the old home screens? Also, GPS lock isn't working for me. Using MyBackup Root for Apps, but it seems to duplicate the apps?
Click to expand...
Click to collapse
You should be able to flash each new nightly without losing any of your settings/customizations/homescreens and apps.
While upgrading from ROM manager, just check the backup option, don't check wipe data and cache.
I can confirm this works transitioning from 14 to 22 because I just did it yesterday night
As for the GPS problem, thats a known issue - the workaround is to make a nandroid backup of your current cm7, then do a complete phone reset, then do a nandroid restore of cm6 or 6.1 (hope you have one), do another factory reset, and restore your cm7 from the backup you took in the 1st step
stellarhopper said:
You should be able to flash each new nightly without losing any of your settings/customizations/homescreens and apps.
While upgrading from ROM manager, just check the backup option, don't check wipe data and cache.
I can confirm this works transitioning from 14 to 22 because I just did it yesterday night
As for the GPS problem, thats a known issue - the workaround is to make a nandroid backup of your current cm7, then do a complete phone reset, then do a nandroid restore of cm6 or 6.1 (hope you have one), do another factory reset, and restore your cm7 from the backup you took in the 1st step
Click to expand...
Click to collapse
first of all, i would never suggest using rom manager for things such as that. historically it has only caused problems and has been more of an inconvenience than anything. second of all, when you boot into CWM and do it the right way, don't wipe data, it's suggested but not necessary that you wipe cache and dalvik, then flash the rom and you'll be good.
Thanks to both of you. Big help and not deleting the data did the trick. Looks like I'm good to go and GPS is working well again. Is there a way to ensure I don't have duplicate apps taking up space on the card and phone? I'm getting errors on moving some apps to the sd card.
kabell4 said:
Thanks to both of you. Big help and not deleting the data did the trick. Looks like I'm good to go and GPS is working well again. Is there a way to ensure I don't have duplicate apps taking up space on the card and phone? I'm getting errors on moving some apps to the sd card.
Click to expand...
Click to collapse
Not all apps can be moved to the FAT32 partition on the SD card. Widgets also, won't work properly if moved to the SD FAT32.
If you need more memory, look into (read up) partitioning your sd card with a ext3 partition and installing S2E or Dark Tremor a2sd (DT a2sd).
zervic said:
first of all, i would never suggest using rom manager for things such as that. historically it has only caused problems and has been more of an inconvenience than anything. second of all, when you boot into CWM and do it the right way, don't wipe data, it's suggested but not necessary that you wipe cache and dalvik, then flash the rom and you'll be good.
Click to expand...
Click to collapse
Oh, I had no idea about that, thanks for the info.
I've been using ROM manager without any problems so far, apart from one lately, that when I reboot to recovery, I always get an error screen - exclamation mark in triangle...but I just pull the battery and reboot into recovery manually and it starts whatever command I had given it (backup/new rom) automatically...

TNTLite 4.4 issues

Hi everyone,
First time poster but have been reading and browsing for a couple month now and have been able to find fixes for all the issues on my own. I have however had this one issue from the beginning and have not found any fixes or even the issue being mentioned (been using TnTLite the entire time, going up the versions from early 3's to now 4.4).
When my Gtab goes to sleep or even sits idle for a while my WiFi just stops working. The connection is still there and Gtab thinks it's connected but I can't access the net until I turn Wifi off and on and then it works until I let it sit or the screen shuts off. This is annoying at the least and I would love to fix it, even if I have to go to a different ROM (but I do like TnTLite above others).
Does anyone find version 4.4 more laggy than 4.2.5? Gtab is just not as responsive and I seem to have a Flash issue where net videos crash after working for 1-15min.
Also I have CWM 0.8 and when I try to flash with a MicroSD I keep going back into CWM. I changed SDCARD to SDCARD2 in the common file but still my card is not being read. Basically if I want to install the stock ROM and nothing else I can't cause it only boots into CWM and not the SD card. I do have the card formated in FAT32 at 2048. Am I missing something, do I need to uninstall CMW first somehow?
If you re-read the first post in the TnT Lite 4.4 thread, you'll see that you can toggle the CWM back to stock recovery with some built in commands.
Yeah, I saw that as one of the options but I want to be able to patch via the micro SD card and CWM seems to be interfering with that. I mean if I revert to stock with CWM I will still have CWM installed. I want the true original state but more than that I want the MicroSD card recovery to work.
Switching to stock recovery removes CWM and will allow you to use the MicroSD to install. All you have to do is put a file named "command" in the recovery folder on your MicroSD card with the following contents:
--update_package=SDCARD2:/update.zip
When you reboot into recovery it will find that command and execute the update.zip on your MicroSD card.
Thank you!
It was my suspicion that CWM is interfering but I also had recovered from the SD card a couple times even with CWM installed, at least I think so, but it is good to know. I'm also still having issues with net video crashing now and again. The screen goes white and I have to reboot. Started when I installed 4.4 and now that I reverted back to 4.2.5 it is much better but still I had it happen just now and it never did before 4.4. The upgrade to 4.4 also slowed the tablet down which did improve as I went back to 4.2.5.
Try going into CWM and wipe dalvik cache and also do fix permissions, usually cures most of those problems after going from one version to another.
What exactly am I loosing when I wipe delvik cache, do you know? And thanks for the suggestion, haven't tried that yet.
Vigilantys said:
What exactly am I loosing when I wipe delvik cache, do you know? And thanks for the suggestion, haven't tried that yet.
Click to expand...
Click to collapse
Here is a post that explains it
http://forum.xda-developers.com/showpost.php?p=3844295&postcount=5

[Q] Corrupted Internal Memory

Hello people. I have a 32 GB Wi-Fi only Tab, running seraphimserapis' CM9 preview kang.
I'll dive right into things here. Earlier today, I flashed the above ROM, everything went perfectly, booted up just fine, and got all my apps back up and running. I was using my tab fine for the entire day with no problems to speak of. Later in the day, I began transferring some misc. files (documents, music, etc) to my internal SD card via MTP USB transfer. After the transfer was complete, I unplugged my tab, and went on my merry way. The next time I booted up, everything began FCing on me, and nearly every app I tried to open immediately FCed. Thinking it was a temporary bug, I rebooted my tab, but the same problem persisted, multiple different processes fced upon boot, and almost all my apps would fc as soon as I opened them. After trying a few more times, I gave up, and booted back into CWM (which I can do perfectly fine), cleared cahce and delvik cache, and did a factory reset. This however,seemed to only augment the problem. Upon booting up (after doing that initial tab setup), trebuchet FCes (in a "FC loop", as it continually tries to open), and the tablet is completely unusable. I have tried wiping cache, reformatting and rebooting several times, each time with the same result
I am able to get into settings however, by plugging in the tab, and clicking USB debugging (for whatever reason, settings does not FC), and am able to connect to my internal memory via MTP. When the tab pops up in my computer, it says I have 25 GB out of 28 available GB, but when I click on the folder, it is completely empty. If i try to move files over to my tab, or even create a new folder, I get an error message saying "the device has stopped responding or has been removed". (Pictures below)
http://img141.imageshack.us/img141/9855/75464072.jpg
http://img190.imageshack.us/img190/3395/61277691.jpg
I do not believe this is a problem with the rom for two reasons. (1) no one else has had this problem (to my knowledge), and (2) it was working fine the whole day, until i did that file transfer (that being said, this is my own amateur opinion, which you may choose to completely disregard it in your diagnosis). I am 99% sure I didn't unplug the tab while files were still transferring, but I did not unmount the storage or eject it or anything fancy of that nature before I unplugged it.
My question is, is there any way I can somehow reformat the internal memory of my tab? Otherwise, is there some other possible fix you experts may possibly have? Or am I screwed?
I apologize in advance if you ask me to try something and I cant respond promptly. Its 3AM here and i need to wake up early tomorrow. Thank you in advance
Edit:
I am quite convinced there is some kind of internal memory corruption problem here, but I really am not an expert enough to know for certain. The tablet still boots up fine, but is completely unusable as trebuchet fc loops 90% of the time i reboot the tab. Obviously, the entire thing isnt trashed as it appears to boot and get into the system fine, but I it's still completely unusable from that point on.
I have tried formatting the /data and /cache partitions of the internal memory to no avail. I would try formatting /system, but from my understanding, thats only advisable if you are able to flash a new rom after formatting, but if i cannot write into my internal memory, then there's no way i can flash a new rom. Conveniently enough, I deleted the .zip file for the rom off my internal sd, and i cannot access my clockworkmod recovery from CWM (gives an error, I don't think that would have worked anyway) since the internal sd is (i believe) corrupted. I also tried mounting as USB from CWM, and that also gives an error...
I am clean out of ideas. I'm not sure if this is a completely unfixable problem, or if self repairing is well within the realm of possibility. If someone can shed some light on me that would REALLY be appreciated. Otherwise i might have to send it back to sammy (still under warranty), which i dont mind doing, but if they boot it to find an ICS rom, they probably wont be so keen to repair it...perhaps there's a way to brick it further so they can't tell?
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
.......HOW??
brennanyama said:
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
Click to expand...
Click to collapse
I'm hoping you see this reply as its been quite a while since you've had the issue. I'm working with a Galaxy S2 Skyrocket with the same intenal memory corruption/ files system corruption you were facing. I followed what you did regarding push a rom thru adb and that worked for me, but my question is, how did you get the roms to successfully write if you couldnt write to internal memory? My system is mounted as read only apparently and locked itself with whatever I had on there on August 28th. No matter how many times I format, erase, or wipe it, it returns to the same state as if its a deep lock on it.

[Q] Rooted long ago with CM7, failing, looking to start fresh

Evening all,
I previously rooted my Nook Tablet 16gb using an SDCard and I believe CM7. I stopped using the nook for awhile and when I brought it back out CM7 would constantly crash. I don't know if I should start with the guide on the Android Developers sub forum as I don't know if that's current.
Could someone please point me in the right direction for where to get started? Is the SD card method the best? What launcher should I choose? I'll continue searching the forums but any help is greatly appreciated.
Thanks!
Punkrulz24 said:
Evening all,
I previously rooted my Nook Tablet 16gb using an SDCard and I believe CM7. I stopped using the nook for awhile and when I brought it back out CM7 would constantly crash. I don't know if I should start with the guide on the Android Developers sub forum as I don't know if that's current.
Could someone please point me in the right direction for where to get started? Is the SD card method the best? What launcher should I choose? I'll continue searching the forums but any help is greatly appreciated.
Thanks!
Click to expand...
Click to collapse
CM10+ is your best bet. It's based on Jelly Bean. Pretty stable also. CM10 released a stable version on 12/31 and CM10.1 is almost to it's stable release (RC4 was just released.)
The succulent versions are my favorite. Go to http://iamafanof.wordpress.com/ and check out some of the posts. Find something you like. If you need help just let me know.
Punkrulz24 said:
...
Could someone please point me in the right direction for where to get started?
...
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
Thanks to the both of you. Data, in my own research I have found the Succulent versions of which you speak. So far I've been following this guide here, but I've run into a pretty big issue. The images that I'm trying to download are hosted on this goo.im site, and I'm having numerous problems trying to download from there. If I can get the download to work, it slows to a crawl then ultimately stops. Any browser I use fails with this.
I'm still searching, however do you know of any other mirrors I would be able to download the releases?
Also, the Nook was already previously rooted. Do I need to update CWM or the root to be able to use CM10? And if so, how?
Thanks!
I managed to download the files that were necessary and got it running. The only problem I'm having now is the sluggishness that is being caused by CM10.1. Waiting to see if this is fixed via a reboot, but it's even taking a little while just to open the book on the Nook. I don't know if this is due to having previous files on the nook or anything. I need to start looking into ways to completely restore the Nook to factory condition and work at it from there as well. Even after the reboot just bringing the Nook out of lock can take awhile.
Also it appears some report that this can be untethered... and some report that they always have to reboot with power plug to get it to load CM10.1. Has anyone been able to force the issue one way or the other? Any idea why some have success and some don't? As always I'll continue searching, but if you get to the answers before I do I would appreciate it.
Punkrulz24 said:
I managed to download the files that were necessary and got it running. The only problem I'm having now is the sluggishness that is being caused by CM10.1. Waiting to see if this is fixed via a reboot, but it's even taking a little while just to open the book on the Nook. I don't know if this is due to having previous files on the nook or anything. I need to start looking into ways to completely restore the Nook to factory condition and work at it from there as well. Even after the reboot just bringing the Nook out of lock can take awhile.
...
Click to expand...
Click to collapse
If you're running CM internally on EMMC I'd suggest you wipe /data (which will entail reloading your apps from Google Play) and /cache; if you're running CM off SD card you'd need to wipe the /data partition on the SD card (aka /data1 if you're using CWM version compiled by Succulent).
digixmax said:
If you're running CM internally on EMMC I'd suggest you wipe /data (which will entail reloading your apps from Google Play) and /cache; if you're running CM off SD card you'd need to wipe the /data partition on the SD card (aka /data1 if you're using CWM version compiled by Succulent).
Click to expand...
Click to collapse
Digi I believe it's off of the SDCard. When I boot the Nook w/o power or SDCard it loads Nook software + root. I went ahead and formatted the data partition as well as the system partition (for some reason in my partition manager it was listed as EXT3)... got everything squared away. The OS part of it seems to be running a bit better right now... Loading a book in the Nook app still takes forever but I'm beginning to think that's because it's Game of Thrones, and it merged 4 books into one so it's like 3500 pages. It takes between 45-60 seconds to load each time I go in.
Punkrulz24 said:
Digi I believe it's off of the SDCard. When I boot the Nook w/o power or SDCard it loads Nook software + root. I went ahead and formatted the data partition as well as the system partition (for some reason in my partition manager it was listed as EXT3)
...
Click to expand...
Click to collapse
/system's partition type is supposed to be ext3.
... got everything squared away. The OS part of it seems to be running a bit better right now...
...
Click to expand...
Click to collapse
You might want to take a look at this thread http://forum.xda-developers.com/showthread.php?t=1005633 which discusses comparative performance of different brands and classes of SDcard for the purpose of running ROM.
CM10.1 is a speed demon on my mom's NT. I've never ran on anything but emmc, however.
Sent from my DROID RAZR MAXX HD

[Q] CWM doesn't see sdcard to install ROM

I've basically spent my entire day off from work trying to root my Nook Tablet 8GB to get CM10.1 put on it, and I'm ready to yank my hair out. A while back I successfully got CM10 on an sdcard and have been running that from the sdcard while my warranty was still active (just in case). Now my warranty's run out, and CM10 had been running sluggish for a while, in spite of my cleaning off all unnecessary files regularly. So I figured I'd try an internal ROM install. After hunting around for some really good detailed instructions for noobs (because I totally am one), I found this post (http://forum.xda-developers.com/showthread.php?t=2037368) and decided that even though it looked inefficient to go from CM7 to CM10, it broke the steps down enough for me to follow along.
However, I'm now stuck with CWM not reading the sdcard once it's time to install CM7 and gapps from the zip files. I keep getting the message, "No files found." I've tried unmounting the sdcard (and mounting "sd-ext," just for kicks), and it says, "Error unmounting /sdcard." If I try choosing "format /sdcard," it says, "E:format_volume failed to unmount '/sdcard.'" I've tried popping it out and back in multiple times. I've tried formatting in SDFormatter over again (even did a full overwrite erase, which takes forever, b/c I got a message saying the device doesn't support flash erase). I've been using Minitool to ensure that the partition is always FAT32, primary, set to active. I've gone into the stock OS and used a workaround I found to ensure that it will install apps from unknown sources. I've tried doing the root again from the beginning (which is a pain in the butt because I only have 1 sdcard to use for both the root and the ROM, so I have to keep switching the files out). I have no idea what I could be doing wrong, but I fear that it's something really basic.
Does it matter that I'm leaving the partition labeled "boot" for the ROM install? Is there a better way to put the files on the sdcard besides just with a Windows drag and drop? Is there a way for me to reboot the Nook from within CWM to maybe force it to read the sdcard fresh (keeping in mind that the sdcard no longer has the CWM files on it by that point)? I've seen some info online about people having issues with this class of sdcard, but I really don't want to spend the money on a new one until I rule out the possibility of a stupid user error. I'm also loathe to give up and go back to running a ROM from the sdcard because I've already put over 8 hours into trying to make use of the full Nook memory... If anyone has suggestions, I'd greatly appreciate it. Please keep in mind that any instructions will need to be very, very basic, though.
CWM version 5.0.2.8
sdcard type: SanDisk 8GB Class 4
Files on the sdcard: cm-7-TEAM-B-BETA1-signed.zip and gapps-jb-20130301-signed.zip
MidnightFrost1701 said:
I've basically spent my entire day off from work trying to root my Nook Tablet 8GB to get CM10.1 put on it, and I'm ready to yank my hair out.
...
Click to expand...
Click to collapse
There is no point in flashing CM7 if you're aiming to immediately flash CM10 on top of it.
To flash CM10.x, I'd suggest you try the process outlined at http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1. See http://forum.xda-developers.com/showpost.php?p=42985699&postcount=117 if you'd like to use a more recent CM10.1 build.
...
Files on the sdcard: cm-7-TEAM-B-BETA1-signed.zip and gapps-jb-20130301-signed.zip
Click to expand...
Click to collapse
You'll need an older version of gapps to go with CM7, see http://goo.im/gapps.
digixmax said:
There is no point in flashing CM7 if you're aiming to immediately flash CM10 on top of it.
To flash CM10.x, I'd suggest you try the process outlined at http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1. See http://forum.xda-developers.com/showpost.php?p=42985699&postcount=117 if you'd like to use a more recent CM10.1 build.
You'll need an older version of gapps to go with CM7, see http://goo.im/gapps.
Click to expand...
Click to collapse
Thank you, I'll try that tonight after work! After having been through the steps in the original instructions so many times, I'm familiar enough with things like Minitool Partition Wizard that I can get by with slightly less noobish instructions now. So that's one silver lining... [crosses fingers]
It seems to have worked! The first time I tried to turn it on after the install, the screen went and stayed black after the initial Cyanoboot screen. So I forced a reboot, but it appears to be running just fine! Thanks for the help!

Categories

Resources