Related
About a week or so I've been experiencing a new problem: the SD card becomes inaccessible and none of the applications installed on the SD able start (obviously). Soft resetting my HD solves the problem, but only temporarily for a few minutes. It really let me down a couple of times when I needed my SatNav app the most.
I'm using Laurentius26's v4 custom ROM. All I can think of is formatting an SD card. Any other thoughts?
Try some recovery software on your PC to get off as many files as possible then re-format. They can become corrupted over time. You might want to get another card though, as they only have a limited read/write cycle and sounds like yours could be slowly dying if it's been used a fair bit. If fairly new then if it was me I wouldn't trust it with my data and I'd buy a new one.
Hello guys....and girls if any
i'm a bit of a noob, managed to get Android working from SD but thinking of putting it on NAND. My question(s) to you guys:
IS IT WORTH IT?
is the battery life - any better or at least equal to winmo?, functionality wise, is it 100% working?
Is having 2 OSs more versatile, is it worth getting rid of winmo and its apps?
Awaiting replies from members that have Android NAND for a while and can give a full view
I apologize if this question has been asked before...i looked...couldn't see a thread like this.
Thanks
Only recently did I switch to android on my HD2. I used WinMo Stock Rom before, but I had a lot of problems with Windows, I wasn't happy about the general UI and the lack of "modern" applications.
So 2 or 3 weeks ago I decided to switch to Android NAND. Here are some of the points witch made me use NAND instead of SD.
1st: Space. I only have a 2 GB SD, so a SD Rom would've taken 'all' or most of my SD Card Space.
Installing it on the ROM saved me a lot of Bytes. ^^
2nd: No trouble with 2 OSs. As I thought that WinMo was useless anyway, I thought it to be stupid to still have it and let it consume space. I thought, NAND can't run worse as WinMo did for me, so why keeping it as fallback ROM. Also, I have an old phone (Sony C905) to fall back when flashing ROMs or if any problem would occur. (Just to mention it, I did not have any problems at all really)
These where my main points to use a NAND ROM (I am using this one here by gpc: http://forum.xda-developers.com/showthread.php?t=909096 )
After having used a NAND Rom for a couple of weeks now, I made the experience that these ROMs run very smoothly. Everything works for me, the sync between Google and Android is awesome. I followed the instructions of the cooks and did not have any problems with GPS, Bluetooth, Wifi, ... everything is working fine (exept stock tethering - but that can be easily achieved by 3rd-party apps). My Problem is, that I flash relatively often and I do not use any kind of backup so I have to reinstall all my apps. But the 200+ MB which the ROM leaves free from internal memory enable me to install a lot of apps and the market helps me to easily reinstall all of them after a flash.
Overall, Android Gingerbread is more stable (as to your question: I'd say it is working to 95%, and the 5% missing being non-essential, or can be achieved by 3rd-party-apps), has more functions, and drains less battery than WinMo6.5 - in my own personal oppinion... and it only took me half an hour to get my device from Win to Android. So I still do not see the point in leaving WinMo on the device and use up space of your SD Card.
But you should ask yourself, what do you need from WinMo, what do you need from WinMo what it can not do, and what can an Android-ROM do for you. And if you find for yourself that a NAND Android can do everything you need from your OS (or even more), than where is the point in still using an outdated OS?
I hope I could help.
PS: There are a lot of votings here on XDA and as far as my memory goes most of them voted for NAND-based roms... so I don't think that I am alone with my oppinion.
EDIT: BIG WARNING Thou': I should read all posts (especially sticky-ones) carefully to see, if you have the right Radio, and so on! a NAND-Rom _does_ have some kind of risk installing, and I don't want to be held responcible for bricking your phone. I am just telling you my personal experience as a User (I am neighter a developer nor have I ever flashed a phone in my life before), but I know, that there are some Users which did encounter problems. It's your decision in the end, I guess.
-felt like adding a disclaimer-
It depends if you still want winmo or not. Battery life is about the same as SD for me, overall performance is about the same as SD builds, but there are some bonuses with nand, like you can change sd cards, use recovery, couple other small things. If you don't use winmo anymore and don't want it, might as well put android to nand. You have to decide if losing winmo is worth it. Personally I use SD android because I have WP7 on NAND. I used NAND android for a while, and when I went back to SD android, I didn't really notice any difference. SD android is good enough for me and I think being able to have 2 OS's on my phone is much more important and is what makes the HD2 unique and special. If I just wanted android, I would have gotten a native android phone. When you put android on nand, it makes it just like any other android phone and there's nothing it can do that many other phones can't, but when dualbooting you're phone can do things that no other phone can do. And I use WP7 just as much as I use android now, so it's great having both OS's on the same phone.
I was pretty happy with WM+Sense on Stock T-Mobile HD2. And I'm expert-user of WM. But with so many apps for Android and so few NEW apps for WM - it is hard to resist. So I moved to Android SD-mode.
At that point I liked everything except battery life. And GPS Fix was slow. I tries few SD ROMs ... liked them all, not much difference for me. To fight battery drain I moved to NAND.
Speed-wise I do not see any difference between NAND and SD. My battery life is better with NAND. But then again ... may be ROMs get improved, may be I got more experience with how to manage things battery-wise. Got my slow GPS Fix resolved, but I'm sure it would work on SD-mode too.
I would almost all equivalent apps for Android to replace my favorite WM apps.
Bottom line is (for me).
1. Battery is still BETTER with WM. I have to charge every day with Android, with WM I could go 1.5 days, sometimes even 2. But then again ... Android is more into "cloud".
2. Booting into NAND directly is not much faster than WM+Android SD.
3. There is NO navigation with TTS+reliable map/poi source on Android which can be compared to properly skinned Primo 1.1 and that is my ONLY big complain.
4. Overall user experience with Android is better. For me at least. And it crashes much-much-much less than WM. Surprise !
Overall I'm happy with my WM->Android move and I'm not going back. But hey, I was happy on WM too
I have been running CM7.1 RC1 off of my SD card without for about three weeks now.
But today, my NC started freezing often. Sometimes it won't even finish loading the home screen. Additionally, when I make any changes (wallpaper, ADW settings, install apps), the changes/apps are not there after I reboot.
If there are any gurus out there who can help me out, I'd really appreciate it.
Well I would say your sd-card is getting a bit overwhelmed with all the stuff on it what size brand and class is it?
I have a Class 4 16GB Sandisk uSD.
Under storage settings:
SD is listed as Total Space: 13.31 GB, Free Space: 2.13 GB
Internal Storage Total: .93 GB, Available: 574 MB
Additional storage on /mnt/emmc Total: 1.00 GB, Free: 1.00 GB
I also tried deleting 4.55 GB in files is ES File Explorer. But when I restarted, they came back.
To recap: Freezing often; files I delete come back after restart and files I install disappear after restart.
I was getting problems like that after any force close happened -- any settings changes I made would just vanish after rebooting. I had reinstalled CM7 a couple of times and that always seemed to fix it, but something always would creep back again. I finally just installed CM7 to emmc and haven't had a problem since.
ponyboy82 said:
..... I finally just installed CM7 to emmc and haven't had a problem since.
Click to expand...
Click to collapse
Got to agree with this
ponyboy82 said:
I finally just installed CM7 to emmc and haven't had a problem since.
Click to expand...
Click to collapse
I was thinking about that, but since I've been having issues with the screen while plugged in, I wanted to ensure that I don't void the warranty on my NC in case I have to exchange it.
Edit: I also like having the multimedia storybooks to read with the kids.
I've seen enough anecdotes about SD installs suddenly going bad that I wonder if they're stable in the long run, but not enough to convince me that they're not. My SD install did go bad (more conventionally: force closes and lag), but I was already thinking about moving to eMMC, so I just took the plunge. If anything, I might set up a stock 1.2 SD card down the road.
thesourgin said:
I was thinking about that, but since I've been having issues with the screen while plugged in, I wanted to ensure that I don't void the warranty on my NC in case I have to exchange it.
Edit: I also like having the multimedia storybooks to read with the kids.
Click to expand...
Click to collapse
While it wouldn't help with dual-booting, you could also keep a microSD card around to revert it to stock if needed. I thought the latest nook app was supposed to support storybooks, but it gave me an "unsupported" error when trying to open an "enhanced" book, so I don't have much personal experience.
Taosaur said:
I've seen enough anecdotes about SD installs suddenly going bad that I wonder if they're stable in the long run, but not enough to convince me that they're not. My SD install did go bad (more conventionally: force closes and lag), but I was already thinking about moving to eMMC, so I just took the plunge. If anything, I might set up a stock 1.2 SD card down the road.
Click to expand...
Click to collapse
Yeah, it seems like this is an unspoken problem here. I'm not sure how prevalent it is, but when you do mention weird behavior when using an SD card, usually someone will suggest moving to emmc or say they had a similar issue when they were using an SD card as well.
Well, I went ahead and put Phiremod 6.3 on Emmc. No issues yet...
I had to buy a new SD card. The one I had CM7 on was completely locked up. I couldn't delete, save or even format it.
Thanks to everyone for the advice!
Use MiniTool Wizard or EASUS (or whatever) to format the uSD card
I'm currently having intermittent problems with random freezes. My nook freezes up and becomes unresponsive to input. I'm forced to manually shut down the nook by holding the power button for 4-5 seconds, and restart.
The last time the nook froze was when I tried to download the doubletwist player app from the market. After it froze, i restarted, and then the installation went on just fine.
I'm currently running CM 7.1 stable on a sandisk 32gb class 4 card using verygreen's method. I got the latest gapps (i think 0828), and the market is at version 3.3.11. I don't have much loaded on the nook just yet since it's still new to me, so it's strange that I'm having instability issues so early. I have also tried fixing permissions by using ROM Manager without much effect.
Also, on a side note, it seems like my nook does not update any accounts (gmail, imap email, facebook, etc) when my screen is off - is that normal? My wifi is always on and active, but the accounts don't update/sync until the screen is turned on.
Hmmm... so no one has experienced freezing issues for the Nook Color? My nook seems to freeze at least once a day - it ranges from downloading apps, playing games, all the way to typing an email...
Any insight would be greatly appreciated!
I rooted and had my Nook all for a day, but rooted it immediately.
Only thing I can think of:
1. Are you OCing?
2. Did you format data before installing the rom?
3. Did you flash a different kernel?
Sent from my SPH-D700 using XDA App
About the syncing issues, I don't know if the nook is setup to sync like that? It has wifi but I don't believe it is on all the time to save battery... in all honesty its all new to me, but we can learn together.
Sent from my SPH-D700 using XDA App
Well it does seem like it syncs some data now... for instance my yahoo mail, and my work's exchange mail. But it doesn't seem to be very frequent... i guess maybe that's just how it is?
It still does freeze on me though, but to answer your questions:
1. Are you OCing - Yes, I do have it OC'ed to 1200mhz
2. Did you format data before installing the rom? - I'm back onto MIrage's 7.2 RC, but i did not format the data beforehand... maybe that's it.
3. Did you flash a different kernel? - Yes, i flashed to the new kernel that fixes SOD.
It's all new to me too, but i'm beginning to think you get what you paid for in this instance.
switch81 said:
Well it does seem like it syncs some data now... for instance my yahoo mail, and my work's exchange mail. But it doesn't seem to be very frequent... i guess maybe that's just how it is?
It still does freeze on me though, but to answer your questions:
1. Are you OCing - Yes, I do have it OC'ed to 1200mhz
2. Did you format data before installing the rom? - I'm back onto MIrage's 7.2 RC, but i did not format the data beforehand... maybe that's it.
3. Did you flash a different kernel? - Yes, i flashed to the new kernel that fixes SOD.
It's all new to me too, but i'm beginning to think you get what you paid for in this instance.
Click to expand...
Click to collapse
1. OC to 1100. OC'ing to 1200 has no noticeable increase in performance, it overheats the device, and burns through battery like no tomorrow. I also suggest setting your minimum frequency to 1100. It sounds counter-intuitive, but the minimum frequency shows no real effect on battery. LeslieAnn (Harmonia dev) linked to a thread about the effects of overclocking on the battery (The OP was testing on the LG Optimus V to be precise). This person benchmarked and tested at different clocking speeds and found that if you set your CPU to it's highest stable clock speed (806 for the Optimus, 1100 for the Nook) it's actually better on battery life. So, my suggestion is set it to 1100/1100 min/max.
2. *facepalm* Tsk, tsk, tsk. I tried the Mirage port for the Nook and found it to be very buggy. The keyboard was always glitching, apps FC'd, etc. I'm not necessarily putting Mirage down, but it has quite a way to go before it's ready to be run on Nook. ATM I'm running Dalingrin & Fattire's CM9/ICS build (though it's only an early build, an RC maybe an alpha build at most at this point), it is amazing, aside from some bugs (you have to use a bootable microSD to utilize recovery) it's superb. If you feel a need to change ROMs, I'd go with either CM9/ICS: http://tinyurl.com/7ny5r5c Or one of the CM7 nightlies (they are fairly stable for nightlies and include plenty of goodies).
3. SOD... never had that. So I have no advice there, apparently you got it patched. I'm running Fattire's 2.6.32.9 kernel for ICS (comes standard with the ROM), no problems so far.
Edit: Clock to 1100/1100 on the interactive or interactiveX governor. Forgot to write that.
Edit #2: I'm a bit unattentive today (3.5 hours of sleep...). To address your email sync issue, I'd go into settings and see what your sync interval is (mine is set to every 15 minutes, screenshot here: http://tinyurl.com/cgkjnxe). If you have it set to something low like that and still have sync issues, it may be due to ROM bugs, or a plethora of other reasons (possibly WiFi speed?). If setting it to a lower sync interval helps, so be it, but if not, I'll look further into the problem. And by the way, check out that sexy ICS interface. This shall be my last edit.
worldindo1 - do you run CM9 off of your emmc? or a sdcard? I'm thinking about moving over to the emmc, and wondering what the benefits would be.
switch81 said:
worldindo1 - do you run CM9 off of your emmc? or a sdcard? I'm thinking about moving over to the emmc, and wondering what the benefits would be.
Click to expand...
Click to collapse
By default, the way Dal and Fattire have it set up, it automatically installs the boot to eMMC. Which means the loss of 5GB of storage space. But with another .9GB on internal, and up to 32GB of external, app and media storage should be no problem. So there is a con, but the pro is that you never have to worry about inserting SD to get into it.
Take heed to a few warnings:
1. Don't try to boot into recovery by using ROM manager or by Power+Home button. Use a CWR bootable. Otherwise, you corrupt your boot and have to restart.
2. GApps is still a bit buggy (unless you build straight off from their most current source) so it can/will FC on you.
3. Make sure you flash the proper version of GApps: http://db.tt/ujcVWK1U All other versions of GApps for ICS have nfc (Nook doesn't have nfc) which leaves you with a completely unusable device due to cont.force close of nfc service.
4. USB transfer DOES NOT WORK! D: If you want to put files on your SD, either use a phone or use a microSD adapter.
Note: Took down the link because something in the ZIP (not quite sure what) may have corrupted. Now I say this, but don't freak out if you already downloaded it. Whatever happened within the ZIP wont harm your Nook so don't worry about it.
The CM9 zip can either install to emmc or SD depending on which installation method you use.
Which you choose to do is entirely dependent on your usage of the device and whether the NC is a working tablet or an experimental device. Some are OK with current state of CM9 and put it on the emmc for convenience.
At the moment I chose to leave CM7 on the emmc for normal usage and swap in a CM9 SD card to play with the current state of play in its development.
On the subject of OC I have pretty much always run at 1200 On Demand with the default minumum. I do tweak the voltages down to the value originally suggested by Dalingrin. I have no overheating and battery life is great.
For freezing it maybe be worth upping the version or trying out the KANG MiRaGe which has all known fixes in.
bobtidey said:
The CM9 zip can either install to emmc or SD depending on which installation method you use.
Which you choose to do is entirely dependent on your usage of the device and whether the NC is a working tablet or an experimental device. Some are OK with current state of CM9 and put it on the emmc for convenience.
At the moment I chose to leave CM7 on the emmc for normal usage and swap in a CM9 SD card to play with the current state of play in its development.
On the subject of OC I have pretty much always run at 1200 On Demand with the default minumum. I do tweak the voltages down to the value originally suggested by Dalingrin. I have no overheating and battery life is great.
For freezing it maybe be worth upping the version or trying out the KANG MiRaGe which has all known fixes in.
Click to expand...
Click to collapse
I've found it to be more stable on eMMC. Installing via recovery menu by default put it on my eMMC. The loss of space doesn't bother me, even on other ROMs. There is actually a way to trick the device into thinking that eMMC is an SD card (basically the ability to install apps on "SD" without a mounted SD card, as well as media storage)
So I have not yet tried CM9, or putting the OS on the emmc... however I did switch over to LauncherPro recently.
I have to say... I've been having a lot less issues with LauncherPro... and not to mention, there is a HUGE performance difference. The scrolling of the home screens are so much smoother with LauncherPro than ADW. So I would recommend anyone to give that a shot!
Hi, I'm really sorry if this is considered cross posting, but I'm starting to get desperate here and really need help. I'm on a deadline and running out of time, I need to figure this out somehow and have been bashing away for almost 24 hours now.
My question is in this thread - and is the last post.
I am actively online and working on this. I'm starting to consider just reverting to stock from the recovery partition and then building everything from scratch, but if I can avoid that time vampire I would like to. Does anyone know what's going on, have some ideas, or anything?
Next step, I'm going to try the 1Gb 5Gb repartition that Dean originally developed. Though with my Nook broken already and my inability to restore it to a working state despite having a ton of perfectly fine Nan backups, I have doubts as to whether anything will change there.
I'll monitor both threads. Thanks in advance for any guidance/help.
Edit: Still plugging away, last steps mentioned above didn't work. Next steps: I'm reading Leaping Lar's partition fix thread and getting some ideas. am going to try:
Flash Partition > Boot to CWR
Format > Flash to CWR
Flash Dizzy Den's signed 4.1 zip > Boot to CWR
Flash my Registered Nan backup of Stock 4.1. > Boot to MMC, get a look around
I think I already did this, but left out the last step. Might work as it should restore my registration data instead of starting me from an unregistered account. If it seems worth trying at that stage, I will then flash my registered Nan of 1.4.2 and get a look at that.
Speculation: I just realized, I've been trying to restore a backup of a rooted 1.4.2 over an unregistered 1.4.1 - which is what I keep getting reverted to. I don't know if that matters, but my hope is if I flash my registered backup over what I'm reverted to, then build up to registered 1.4.2, that will help things... We'll see.
Failing all of this, I will try Leapin' Lar's partition repair.
I have finished reading the Partition thread I linked to above (where my original post is) and found that one other person reported my issue, almost to the T. His/Her user name is Blondie. Blondie seems to have quit without a fix, or if ever got a fix it was never posted. It was quite some time ago, but if any of those who helped him/her can remember if there was a fix would you let me know what it was?
Screw the original nook firmware. Go install CM7 Mirage ROM.
Rooting a stock nook is pointless. CM7 is better, faster, more efficient than stock and it comes rooted by default.
Now that your serial number is probably gone or corrupted in the /rom partition, you most likely cannot register your nook with the B&N servers, and that is probably why you can't install apps.
If you need a complete partition table wipe, follow this guide. http://forum.xda-developers.com/showthread.php?t=1759558
Next time you decide to mess around, be sure you backup your ROM and factory partition before doing anything.
sagirfahmid3 said:
Screw the original nook firmware. Go install CM7 Mirage ROM.
Rooting a stock nook is pointless. CM7 is better, faster, more efficient than stock and it comes rooted by default.
Now that your serial number is probably gone or corrupted in the /rom partition, you most likely cannot register your nook with the B&N servers, and that is probably why you can't install apps.
If you need a complete partition table wipe, follow this guide. http://forum.xda-developers.com/showthread.php?t=1759558
Next time you decide to mess around, be sure you backup your ROM and factory partition before doing anything.
Click to expand...
Click to collapse
I do have backups of everything. As I said above, they aren't wholly functional.
I never said I was completely unable to install apps, or that I couldn't register with B&N. I can register fine, and in some scenarios I can indeed download my apps just fine, just not if I try and restore a MN Nan backup. That is not because of a missing SN but because of a registration issue that can be caused by the MN process - otherwise I would not be able to download them at all in any scenario.
Also, if you know the MN process you know my factory partition is intact. Perhaps the partitioning messed with it a little, I'm not sure - but nowhere did I say I have yet tried to reset to stock from the factory partition, so we have no real way of knowing yet.
I understand that my OP is starting to get tl;dr because I don't want to double-post, but actually reading what has been done so far and reading the post at the original thread I linked to might be more useful in trying to give people advice. A little less snark would be useful too, I am not a n00b at this by a long shot and talking down to people tends to get hackles up instead of being productive - especially when you clearly haven't read their thread - as an example, if you had read it, you would have seen I already know about Leapin' Lar's partition fix and it's one of the next things I plan to try..
On the other hand, I may take your suggestion about installing CM7 Mirage. Honestly, I had my reasons for not doing that in the past, but those reasons are largely moot today. I will get a look at the thread. Thank you for the suggestion.
You're right, I apologize for not reading thoroughly. I had a derp moment.
No worries Sagirfahmid, I owe you an apology too. I'm sorry to have jumped on you, I am a little bit... stressed, and tired. Not that it's any great excuse. I need to take my own advice about talking to people. Sorry.
And fwiw, I believe you are right and the original partition did mess with the factory partitions, I've just been avoiding facing it. I really ought to get off the fence and run the repair and then follow Dean's guide to using fdisk on the emmc, but I'm getting OCD about trying every other thing first - even down to considering a flat reset to factory and rebuild from scratch. Stupid, I know.
Thing is, there is at least one other person out there who had this exact problem, and it didn't sound like her issue ended up being a corrupt partition as the partition repair didn't help her. Unless it was too corrupted. I know there were a lot of people running the same system as me, and it was very stable. Someone besides me and one other person has to know what this is and how to deal with it. That's what I'm hoping anyway. LOL
And seriously, thank you again for the reminder that there are other options out there that might better suit me now. The more I read the more I think if I can just reset the darned thing to a fully working state, I may well just do an SD CM10... or should I just stick with Mirage? Is there an advantage to Mirage over 10.2?
Yes definitely. It's faster--that's the most obvious advantage. (I disabled all the fancy animations and removed a lot of useless system apps like the phone, contacts, calendar, camera, and GPS app via adb).
Also, CM7 Mirage has USB host mode, so if you get a male microUSB to female standard USB port, it is very possible to use a keyboard or mouse, or a flashdrive or harddrive (if you get a powered hub). AFAIK, the max current it can supply without a powered hub is 100mA (enough for a flashdrive or keyboard/mouse that isn't too fancy--skip the ones with LEDs; each LED uses around 15mA).
Oh yeah, CM10 runs in phone UI (there's an extra bar on top taking up space).
In CM7, there's only 1 bar, so you have a bigger area on the screen. Of course, there is a patch to get CM10 into tablet mode, but I don't like all the hassle.
On CM7, you can overclock the CPU to 1.2GHz, but on CM10, it's limited to 1.1GHz AFAIK.
=====================================================
Right now, I'm hoping to get Debian ARM natively installed on the Nook Color. I've been making progress thanks to the devs and users here. Android is still required, but it will be on top (instead of the other way around, which is Android on top and Debian chrooted). SInce they'll be using the same kernel, I think I can get Debian to use the Nook Color's USB port to connect devices like printers or scanners (that would be so awesome...).
If you're interested in running full blown Debian on the NC, and assuming that you are able to fix yours, you can check out this thread: http://forum.xda-developers.com/showthread.php?t=2422518
Solved
Sorry for the double post. Need to separate this from the wall o text above. Problem is solved and since I never did find a spelled out definite answer while I was reading the last 2 days, I want to post it here where someone who might be looking in the future might easily find it.
To reiterate the problem concisely for those who don't have time for the diatribe above:
My device is a Green dot Nook Color:
* Running a stable Manual Nooter 5.08.20 over a Stock B&N 1.4.2 ROM, and using > This < method to block OTA Updates - basically use a SQLite Editor for Andriod to modify the fota mode in the nook's registry.
I recently started getting the Low Memory message asking me to please archive some of my apps to SD. Am about to go on a long trip abroad and I not only needed what apps I had but also need a couple more. Solution: Repartition the Data and Media partitions.
Full backups: have a whole slew of backed up NC B&N Update zips, Flashable updates created by several awesome people here, and step-by step Nan Backups of every single time I have re-rooted my device after a B&N Update - signed and registered stock configs, roots and final images, and finally a whole store of dated backups of my Tibu backups off of my SD card.
So, I repartition following steps exactly.
* At first reboot, CWR freezes on load. This makes me thing something went horribly wrong.
* Reboot again, everything seems to Format fine, reboot into Nook
* Unlike most people, my nook has reverted to an unregistered stock 1.4.1, no root.
* Flash my latest Nan-backup of my rooted NC, doesn't take properly and B&N is a mess because (duh) I didn't register it before flashing - But I shouldn't have needed to because all of those settings were in my Nan Backup. Okayyyy... weird.
* Flash back to a Registered stock NC nan backup of 1.4.2 since that was the last version I used. I was able to DL books and read them, and could DL apps - but my apps couldn't install at all and there were a couple of new B&N Apps that were stuck in a DL/Install loop too. Hm.
* Flash an earlier root Nan over that. Now my Nook can't download anything, I get an error message that it cannot execute. Lovely.
* Bash around in this fashion trying to make it work, occasionally trying different partition schemes in the process, while reading every thread I can find on the subject of what issues I'm having.
I begin to suspect that my partitions might be all messed up, especially considering the original freeze from CWR, but have no real way to check that and don't want to give up, so I post in the instruction thread and later here to see if anyone has any guidance or knows what this is.
A whole slew of people have endorsed this method and had no problems.
A few people had some problems, but only one user has reported exactly my problem off of the exact build I was running, no less. (1st link is that user's first post and 2nd is the page where her posts begin). However, that thread ended with no real answer - or so I thought.
At once point before the issue ended with no further response from the poster with the issues, Leapinlar (who had been assisting her, or at least trying to) tells her that if his Partition Repair didn't solve anything, then it likely wasn't the problem. If she cannot get her B&N Apps to DL & Install, then it's most likely the version of the B&N Stock that she is on and she needs to flash to the most recent - he even points her to a signed CWR Flashable one that he created for 1.4.3. She argues that can't be the issue - and I get that, because the apps installed and worked before in 1.4.1 right? So why all of a not now simply because she's back on 1.4.1 again?
I don't know why B&N would have made it so that you can't install any older apps on your device even though they installed on older ROM versions, forcing people to move up to 1.4.3, but it appears to me that this is exactly the case and Leapinlar is once again correct.
Took me a long time to internalize that and have it click. After running his Partition Repair with the same results as her, I left it on a registered 1.4.1 Stock, put the NC down and stepped away for a while to do other things. when I came back I was fixated on what Leapinlar said about flashing to a newer version of B&N Stock. So I did. And when that didn't really fix it I flashed up to the next ans last version, 1.4.3.
Hallelujah, problem solved!
For my own apps to download, I had to wait for a couple of new ones sent to Nooks from B&N for version 1.4.3 to download and install - and they were not able to do that on earlier versions. I propose that their inability to install was what was blocking my other apps. but it could be that the others were also made version specific once B&N stopped making NCs in favor of HD's and the Tablet, and released the final update.
Regardless, that is the final answer. If you are on MN and repartition, and then find when you boot you are taken to unregistered stock, and upon registering you can access your books but your apps will not install after downloading and you have a couple of new ones that seem stuck at dlownload and install, all you need to do is Update your NC to the final release, 1.4.3, and the re-root. I think you will need to re-root from scratch, unless maybe your last root backup was from 1.4.3 - which mine was not.
Next dilemma: Stick with root or start running a CM ROM from SD...
I'm a cheapskate, that's the truth. I am a geek, I want to do **** with my devices and I don't care if I end up bricking them so long as there are ways to recover. I also care about my privacy. I don't stick with the stock firmware because:
1. B&N wants you to REGISTER with your CREDIT CARD to be able to actually USE the Nook Color. Why the hell?
2. B&N possibly has BACK DOORS to your Nook Color. They might DRM lock apps or something. They can obviously force updates onto their users unless they root. They might also decide it's time to brick your tablet if they wanted, so you would go buy another one (yes, this is more of a conspiracy theory, but hey, if they can force updates, they surely can also do this).
3. B&N's custom Android is crippled unless you root. You can't use the 5GBs of space. Why the hell not?
etc etc...there are more reasons I don't stick with any stock firmware, be it for a tablet or phone.
(I use Debian on my computer most of the time now because Windows is a piece of crap. You can't do whatever you want on it, except game. Did I mention the useless startup services and apps you need, especially antivirus, for Windows to function without worries of getting a keylogger or some nasty virus? Valve has made Steam for Linux very usable, and I rarely use Windows for gaming now. Linux is tons faster, and I can do almost anything on it).
Have you ever used a T-Mobile smartphone? the apps that come installed are numerous! It makes me want to puke every time I use a stock Android phone from a phone company. I like and want my devices to only contain the apps I want. That means NO BACKDOORS, NO FISHY BACKGROUND PROCESSES, NO **** APPS, NO RESTRICTIONS.
======================================================
Backup the documents and whatever you have on your B&N firmware. Install CM7.2 Mirage onto INTERNAL SD card.
Stop being a wuss :silly: and start enjoying a better Android experience.
sagirfahmid3 said:
I'm a cheapskate, that's the truth. I am a geek, I want to do **** with my devices and I don't care if I end up bricking them so long as there are ways to recover. I also care about my privacy. I don't stick with the stock firmware because....
Click to expand...
Click to collapse
I completely understand! I have many of the same concerns and make workarounds and otherwise try to frustrate the usual 'Big Brother' tactic that are becoming so prevalent. I don't think you've gone into the realm of conspiracy theory at all, what you're talking about is a long term goal I think. Think of the marketing and capital profit possibilities of that kind of control over a still largely unregulated market - 'largely unregulated' because the technologies and the possibilities they allow are evolving so quickly.
I also am a 'computer geek', prefer control of my own devices and am very strict about personal security. So then why does B&N have my personal data? Largely because they had it far earlier than there was ever a blip on the tech radar of 'e-readers'. I'm also incredibly bookish and there haven't been a whole lot of B&N in my region, but I prefer their company as a book retailer, so I was a member that had begun ordering from them online as soon as they had a website to order from. So, it wasn't a huge loss for me to keep the stock and use it as intended. here are some things about this that do grate with me, yes, but they wouldn't have lost my data history anyway, so wth, I might as well get a really elegant e-reader interface from a company I mostly like and support. This is definitely not a situation that applies for everyone, I know.
I use windows on a secondary boot partition and funnily enough, largely for gaming. I also use it on a work laptop because I have to. I run Suse most of the time, myself.
As far as DRM, it' something we need to fight in the courts and through making our own backups for experimentation, and that's all I can really say.
When I bought my NC over two years ago, tablets were still pretty uncommon and e-ink readers all the rage. I splurged on this even though I was still using a flip phone because I felt it would serve multi needs well:
a) The need for an e-reader (I travel at least 1ce a year and I read a lot while traveling. Books are HEAVY! and I'm getting oilder...)
b) The desire for an e-reader that could read color and comics - so I could DL comics and fan creations and manga as well as books on the same device - and one that isn't an Apple (I dislike Apple as much as I dislike MS).
c) The desire to have a good interface in a size that is more readable than most phones on the market, to surf the web on or read the above during my long commutes.
d) The desire to have all of the above in one item that would also not tie me to a single seller - in other words I also wanted to run the Kindle App and Google books.
At the time, Kindle Fire had not been released and the next best machine (actually, tied as of the time I bought this nook) was an iPad. Other tablets out there were more expensive and glitchy and without that quality - some didn't even expect to ever update their android ROM. There was nothing on the market close to the NC in that price range - and I knew I could root it or otherwise replace the original ROM if I didn't like it, to do what I wanted, and essentially never brick it!
I chose MN over CM or Nightlies because I didn't have to mess with the factory partition at all or ever worry about replacing it, and it let me use my nook directly from system in a two-sided boot that had a tablet on one end and a Nook on the other. Very neat. I got the 3 yr warranty when I bought it because at that time they stated that you could return the NC within that time for a lower price on the next new thing. I plan to use that, so I wanted the original factory partition intact.
There are only two things today that would keep me from running a CM install or SD right now. The most important of those two is Battery Life.
The trip I'm about to go on is to India from the east coast of the US. We'll be gone about a month and my NC/Rooted or flashed tablet will be my ONLY mobile device. I need something stable, and that if I am not already familiar with it will be fairly intuitive, and most important - Good Battery Life. As far as I know, the CM ROMs for NC are energy hogs - is that still the case? We will have a lot of devices to try and keep charged, one plug adapter, and the NC will have a central role in our keeping in touch with family and friends. We we go for a day without a charge but with about 8 hours of use including wifi time on a MN root, I know I will still have enough charge the next day till we get to the next location where we can try and charge everything.
My other concern is more about running apps and what apps will work with the setup I'm planning - which I already know would work on my NC had I not hit the "Low Memory" wall and started all of this.
I am still interested in running CM, can you point me to info on these? For the second, I need to link to Canon Image Gateway wirelessly and also a Bloggie. I love that CM7 can run a USB interface! That's a huge advantage that I could use!
Even if I don't use it for this trip, I may change it when I get back to a CM7 sd boot to play with till I'm used to it. Also, I am rooting a NC for a Niece before I leave, and I think I'm going to change tactics and put CM on it instead.
As to smartphones... LOL. I still have a pay-as-you-go flip phone, wanna talk about being cheap and having security paranoia? XD Seriously, I spend a lot on my computers - which I prefer to build - and spent a lot on my tablet back when I bought it and when I replace it will consider carefully and spend on that again. =) Smartphones? I will get one eventually, it's a matter of time, but I'm holding out as long as I can. LOL
...I need something stable, and that if I am not already familiar with it will be fairly intuitive, and most important - Good Battery Life. As far as I know, the CM ROMs for NC are energy hogs - is that still the case?
Click to expand...
Click to collapse
Nah, CM ROMs have great battery life these days. I get 10 hours on my Nook Tablet (CM10, 4700mAH battery AFAIK); 8 hours on my Nook Color (CM7, 4000mAH battery. Obviously, it's going to have a slightly lower battery life). Also, keep in mind the li-ion battery is almost a year older than the Nook Tablet, so it has a decreased charge capacity. Li-ion's have a lifespan of 3 to 5 years--after than, you're gonna get crappy runtime on battery. Good news is li-ions are very recycle-able and non-toxic. I think most major electronics stores accept li-ions for free.
The only issue with stability is that, if you have wi-fi set to "always on" in CM7, sometimes you'll get a SOD (screen of death) after an extended period of sleep. Basically, your screen will fail to turn on--you must force power off and restart the NC. The guaranteed workaround is to set the wi-fi setting to "only when screen is on." You can safely overclock your CPU to 1GHz (+200MHz past stock 800MHz) guaranteed, and 1.2GHz almost guaranteed (I have mine at 1.2GHz, no freezes or crashes at all, and I run Debian chrooted in it currently, which takes a lot of power).
My other concern is more about running apps and what apps will work with the setup I'm planning - which I already know would work on my NC had I not hit the "Low Memory" wall and started all of this.
Click to expand...
Click to collapse
All CM builds can transfer apps' storage location to the external microSD if you wish. I have all my games and non-essential apps on my 32GB class 10 microSD, both on my NC and NT. Again, don't forget, the CM7 build for NC has USB host mode (so if you were really crazy, you could possibly plug in a 3TB+ mechanical harddrive, with a powered hub of course). Don't forget, the Nook Color also has bluetooth (which isn't there on B&N software). I have successfully transferred files between my netbook and my NC via bluetooth (but you have to be within 1 to 2 feet distance lol, unless you tear apart the NC and mod an antenna or something). You can also use an external bluetooth GPS receiver and bluetooth headset. Go look on the NC accessories thread if interested.
Even if I don't use it for this trip, I may change it when I get back to a CM7 sd boot to play with till I'm used to it. Also, I am rooting a NC for a Niece before I leave, and I think I'm going to change tactics and put CM on it instead.
Click to expand...
Click to collapse
Good idea. Install CM7 on your niece's NC (INTERNALLY :silly: ) and see how you like it. I guarantee you'll like it, and so will she. Since you messed with the partitions, I would suggest you visit the CM7.2 Mirage thread and post if the changes in partition sizes should make any problems with flashing.
Thank you for all this great info! I had read about the SOD issue, but I usually keep my wifi off when not using it, so I'm not too worried about that - it helps battery life some too. Interesting, I hadn't realized lion batts had that limited a lifespan. I haven't noticed a whole lot of change in my own NC's life, but to be honest I haven't looked either. I should.
Regardless, great to know CM is better at battery life.
sagirfahmid3 said:
I have all my games and non-essential apps on my 32GB class 10 microSD, both on my NC and NT.
Click to expand...
Click to collapse
Actually, that brings up the issue of class 2 vs class 10 cards and stability. There are a few threads that have benchmarked SD cards for running CM ROMS and have found the best and most stable - especially for large cards - is a 16 Gb Cl2 SanDisk... it looked by recent discussions that this is still the case, have you noticed this at all? My card is also Cl10, and as of now I think I would want to run CM off of an SD, at least until I'm used to it.
Turns out I didn't mess with my partitions after all. Gotta love computer systems! LOL Turns out the issue was version of stock I was running, and only that. I re-registered, updated to 4.3 stock and all is fine. You would think I would learn one day to read, step away and consider, instead of banging my head against a wall repeatedly. I should have figured it out much sooner, Leapinlar basically spelled it out for the other member who had this problem. And it completely explains the issues I had too. I may end up messing with them correctly again though.
I did not know the NC ended up having a blue tooth after all! I remember the speculation but the teardowns had only begun then and I never followed up on them. Now that IS interesting!
My Niece's on the other hand does have a corrupted partition, but from something she did to it. I think I will flash CM to the emmc, nice idea!