So this morning i was checking the gallery on me NC that running phiremod nook V5.3. I went to that for V5.1, and low and behold i found all the pics and vids i had put on it when it was still stock 1.1.0.
Now in V5.1 that was not the case. Any idea why or how this happened, because i would have thought when you flash your device it would erase all old stock data.
Or is it because i never had to re-flash why I'm still seeing the files.
I think this could help solve some of the internal memory issues we are having.
That's to say, if you put 2G worth of stuff on your Nook then run phiremod nook V5.3 you can have an extra 2G of files that you would've used on an SD card.
Anybody with more insight on this Id be happy to hear from.
Did you not wipe anything when you went TO Phiremod?
xBryan said:
Did you not wipe anything when you went TO Phiremod?
Click to expand...
Click to collapse
Nope. Went from straight stock to V5.1 and then re-flashed with V5.3.
I thought i lost everything i had on it when i rooted it the 1st time, that seems not to be the case.
I literally just got home, haven't even unboxed the NC yet. With a rumored update coming in the next couple of weeks, should I wait to root/install CM7; or go for it right away?
If I'm going to have to wipe/reinstall in the next week or so, I'll probably just look at how the Nook is stock; but if I could update easily, or if it will take the devs a few weeks to work the new updates into the custom kernels, I'll just go ahead.
Thanks to everyone for all the hard work.
What did you buy it for? Did you buyfor the B&N functionatility? Stay stock.
Did you buy it for a tablet? Then install CM7.
The stock configuration is a book reader that can also function as a tablet.
CM7 is a tablet that you can install ereader software on.
lucifer316 said:
perhaps someone else can tell you if you need to root in order to use external roms on an sd card
Click to expand...
Click to collapse
The nook boots to the SD card first, so no you do not have to root to use the SD card versions.
I actually asked this same question 2 weeks ago. I ended up rooting (which as stated you don't have to do) and installing Cm7. I'll say that I couldn't be happier. Cm7 is stable and paired with dalingrins latest overclocked kernel, my nook is now super smooth and fast.
Sent from my NookColor using Tapatalk
Flash CM7, if you want to go back to stock after the update you can always go back.
I've been lurking on these forums a bit - trying to nerve myself up to install Jellybean. I'm a complete noob. (some Linux experience, curious about Android) Here's what I've picked up. (All measured relative to stock Froyo.) (And I like to fiddle, but I also love my Captivate-so I'm a bit nervous about this...)
Good stuff:
1. Jellybean is great, everything works. Helly Bean/Devil is probably a bit more stable than Cyanogenmod 10 right now. Phone, WIFI, Camera, Movie, Apps all work at the moment. ICS and Gingerbread were all appreciably laggy.
Iffy Stuff:
1. The GPS on anything but stock Froyo may behave a bit better, or not, as the Captivate GPS has hardware issues in addition to possible problems with stock Froyo.
Bad stuff
1. Encryption Unsuccessful: Jellybean is likely to share the 'Encryption Unsuccessful' bug with ICS on the Captivate. For some reason, ICS seems to handle SD access a bit differently than Froyo and this occasionally permanently borks the internal SD. It may occasionally bork an external SD, but that seems fixable so far. Someday, someone may figure out a fix, but don't count on it. For now, any Captive running ICS or later should expect to eventually lose the internal SD permanently.
2. IMEI: Something in the latest installs may result in replacement of my IMEI with a generic one. This will result in AT&T temporarily blocking my phone. This may be related to some custom roms and possibly some apps borking up the efs folder after something in the more recent Cyanogenmods sets the efs folder as R/W.
3. Bootloaders: If I bork up bootloader flashing, I can end up hard-bricked.
4. Sleep of death: Custom ROMs may aggravate a 'sleep of death' issue on older Captivates. Fortunately, I checked and my Captivate doesn't have this issue.
I'm wondering if the following sketch is workable and if I've left anything major out:
1. Backup phone thoroughly. Test backups.
2. Remove SIM card (or stay at home, AT&T simply doesn't pick up here anyways-)
3. Print out and follow one of the sensible guides for upgrading to Helly Bean/Devil Kernel. Use Heimdell - and - after the first time I flash new bootloaders - stop flashing new bootloaders. If I do hardbrick, I can most likely do a bit of soldering to do the unbrickable mod for recovery.
4. Disable access to internal storage and run from partitioned 64 GB external SD card chosen for fast R/W in small blocks (4k).
5. Check IMEI and fix access permissions to efs folder.
So, assuming that the above isn't completely idiotic...
1. How comparable (in terms of speed and stability) should I expect this setup to be? I'm particularly worried about running from a SD card. Most earlier recommendations have been to run from 16 GB SD cards, but I'd kind of like the extra storage. People who bork their internal SD cards seem to end up switching phones even after getting the external setup working and I'm wondering if external access is just unreasonably slow. Also, would 64 GB sizes result in ridiculous boot times or some sort of size limit?
2. Also, is Jellybean inherently laggy on a Captivate - or should it be comparable in responsiveness to Froyo?
3. If I do someday successfully bork my external SD card with an Encryption Unsuccessful message -what sort of information would be useful for me to provide?
4. I should expect a modest increase in setup time when flashing new roms (editing mounting information), but not that many other problems?
I would say you are over-thinking it.
Go here and follow the install instructions --> http://slimroms.nfye.eu/
No guts, no glory.
Sent from my SGH-I897 using xda app-developers app
Yeah I would agree that you're over thinking it. But there's nothing wrong with that. I remember being equally cautious and skeptical about flashing once, but luckily I had a knowledgeable friend to help me quite a bit.
You said you're on stock Froyo? Make sure you root, I don't think I saw that in any of your steps.
Honestly, if you follow the instructions to most ROMS you'll be fine. No need to worry so much. Especially once you do it once, you'll be MUCH more comfortable with flashing in the future. Maybe even watch a few youtube videos of people doing it! That always helps me. I'm more of a visual learner though.
But you're right, you do need to have a backup of your EFS folder, and taking your sim out would be best As far as performance vs froyo. Phenomenal. I've never had my cappy run this smooth, and you can thank project butter for that. Android lag is virtually gone
I was super nervous about rooting and going CM but it is the best decision you will ever make thats for sure. It has increased my phones speed enourmously and made it like a new phone, I would never run a phone on stock firware now lol. Why dont you just go with CM9 stabel release to start if you are nervous. My gf is still on CM9 and it is miles ahead of stock and essentially bug free
Slim ICS & Helly Bean
Yeah I would not go straight to Jelly Bean... try out ICS.
I have been using Slim ICS v4.2 as a daily driver for about a month now, no issues so far. Thank God, the Encryption Unsuccessful issue has not hit me yet. It seems to be random, so be careful. There are guides out there to get the phone running again, but those are for ICS. Not sure if they would work on JB.
Ice Cream Sandwich is much faster than stock 2.3.5 Gingerbread, don't know about 2.2 though. Though it does depend on what ROM you're using. I think the most popular ones are Slim, Team Nyx (ICSSGS?), CM9 and of course AOKP and MIUI (WeUI?). Jelly Bean ROMs include Helly Bean, Slim Bean, ParanoidAndroid, and CM10 nightlies (just off the top of my head, feel free to add to this guys).
I have not tried Jelly Bean yet as I am a bit apprehensive as well. I heard that Jelly Bean removes the datadata partition, and that screws things up going back to GB/ICS? Or maybe it screws up restoring Nandroids? Not sure. I mean, if I don't like Helly Bean, I want to comfortably be able to go back to Slim ICS. I think I will try a Jelly Bean ROM eventually but I may go back to ICS if it's slow/buggy/laggy. The developer of Helly Bean is DerTeufel, I know he's an amazing dev and more knowledgeable at this stuff than I will ever be, but I had a horrible experience using his Devil kernel with Slim ICS. Random reboots whenever I tried doing something "heavy" (like scrolling fast in browser). Semaphore kernel was better but it broke Maps and video playback. So I re-flashed the ROM and it's all good again.
And I like to fiddle, but I also love my Captivate-so I'm a bit nervous about this...
Click to expand...
Click to collapse
Yeah, same here, I just got it this year (2012) so I'll probably have it for a long time! Android has come so far though, it makes me jealous, and I want the latest Thank God this phone has gotten awesome support from developers, maybe we'll have Android 4.2 and - who knows? - a 5.0 ROM or two Maybe I should learn developing so I can make it myself.
__________________________________________
Edit:
run from partitioned 64 GB external SD card
Click to expand...
Click to collapse
Hmm, I thought Captivate only supports 32 GB? Maybe a custom ROM will support 64?
Just about any ROM in the development forum is going to be SO MUCH better than stock froyo.
I have enjoyed using slim ics and slim Bean. Both great roms..
Sent from my SGH-I897 using xda app-developers app
curiousgeo said:
So, assuming that the above isn't completely idiotic...
1. How comparable (in terms of speed and stability) should I expect this setup to be? I'm particularly worried about running from a SD card. Most earlier recommendations have been to run from 16 GB SD cards, but I'd kind of like the extra storage. People who bork their internal SD cards seem to end up switching phones even after getting the external setup working and I'm wondering if external access is just unreasonably slow. Also, would 64 GB sizes result in ridiculous boot times or some sort of size limit?
2. Also, is Jellybean inherently laggy on a Captivate - or should it be comparable in responsiveness to Froyo?
3. If I do someday successfully bork my external SD card with an Encryption Unsuccessful message -what sort of information would be useful for me to provide?
4. I should expect a modest increase in setup time when flashing new roms (editing mounting information), but not that many other problems?
Click to expand...
Click to collapse
I think the phone's internal memory is FINE. Just the internal SDcard is messed up. Since the system partition, and other OS files are in the internal memory, you should be fine with booting and speed. All that's messed up are the /data and /sdcard partitions.
Thanks to you all :good::good::good:- particularly the guy who mentioned that a 64 Gb card wouldn't work. (I'm not sure it wouldn't - since some threads sounded like they were able to get one working...but...realistically...I'm not close to filling up storage anyways.)
Rooting went smooth (One Click Root), backups are pretty smooth-still need to test them. (Titanium, Pro version, not because I need it...just the developer obviously put in a lot of work...) A 32 GB microSD card is on order - Sandisk ULT Class 10 - seems to have excellent noncontiguous read/write speeds. By the way, Amazon had much, much better prices than the local Best Buy.
Y'know, some people are pretty aggressive - that's great. Other people...read every thread on XDA regarding the encryption unsuccessful bug before rooting their phones. Yes. Sigh. It would have been more cost-effective to buy a new phone. I did learn a few things though.
I'm confused. For Captivates, I thought the OS was typically stored on the internal SD card? And the Encryption Unsuccessful Fixes I've seen amount to partitioning the external card, installing a rom on the external card, and modifying vold.fstab. Um...maybe I'll just install a file explorer and have a look. Need to pick a good one - want exploration and chmod. There doesn't seem to be an explicit guide to running Helly Bean from an external card, (unless my search foo fails me), so I'll need to figure something out.
Attached is a screenshot of several different folders in Root Browser. You can see all the different partitions.
The guy who made the guide for the Encryption Unsuccessful issue mentioned,
Your partitions for /data and /sdcard are no longer accessible.
Click to expand...
Click to collapse
So I guess that means everything else is fine? And I think you install the ROM from the external SD card, not on it.
Well I have been running helly bean with/Devil kernel and it is a bit laggy at frist, but it's all about getting the tweaks right in the devil configuration set-up. I would definitely suggest going through ICS, and not go straight to helly bean/ devil kernel. I would suggest doc's ICS V12, and get comfortable using that particular Rom with the icey glitch kernel before moving on to helly bean/ Devil kernel.
Sent from my SGH-I897 using xda premium
May i ask how did you tweak the Devil kernel and what are your settings? When I installed helly bean i found it lags quite a bit (even with lagfree governor), so i returned to cm9 (which is virtually lag free)
Sent from my SGH-I897 using xda app-developers app
I have been running MN 4-6-16a on NC software version 1.3 for over a year now. It's not totally stable (I get some freeze-ups occasionally & have to reboot) but it's workable. The other day, my wifi stopped working. Wifi goes off, and when I turn it on, it can't find my router, I get a black box that says 'unable to scan for networks', and it stops responding and the Nook asks me if I want to force close wifi. If I select 'wait' instead of force close, wifi shuts off.
Router works fine, other devices are connected. I have searched other threads, and it seems that some suggest installing CM7, though these suggestions are from a year ago.
Is there something more current I sould be running that would fix this problem. Suggestions would be greatly appreciated for this newbie.
http://forum.xda-developers.com/showthread.php?t=1941247
Nitrolady said:
I have been running MN 4-6-16a on NC software version 1.3 for over a year now. It's not totally stable (I get some freeze-ups occasionally & have to reboot) but it's workable. The other day, my wifi stopped working. Wifi goes off, and when I turn it on, it can't find my router, I get a black box that says 'unable to scan for networks', and it stops responding and the Nook asks me if I want to force close wifi. If I select 'wait' instead of force close, wifi shuts off.
Router works fine, other devices are connected. I have searched other threads, and it seems that some suggest installing CM7, though these suggestions are from a year ago.
Is there something more current I sould be running that would fix this problem. Suggestions would be greatly appreciated for this newbie.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1941247
The latest ROM for Nook Color is CM10 Jellybean 4.1.2 with a 3.08+ kernel. You can install it on a SD card and try it.If you like how it works you can install it internally. There are great tips threads you can utilize to help get you to the latest ROM. I use CM10 internally on my Nook Color. My other Nook Color has CM7.1 (gingerbread with 2.6.32 kernel). CM10 is running pretty smooth and just as fast as CM7.2.
hwong96 said:
http://forum.xda-developers.com/showthread.php?t=1941247
http://forum.xda-developers.com/showthread.php?t=1941247
The latest ROM for Nook Color is CM10 Jellybean 4.1.2 with a 3.08+ kernel. You can install it on a SD card and try it.If you like how it works you can install it internally. There are great tips threads you can utilize to help get you to the latest ROM. I use CM10 internally on my Nook Color. My other Nook Color has CM7.1 (gingerbread with 2.6.32 kernel). CM10 is running pretty smooth and just as fast as CM7.2.
Click to expand...
Click to collapse
Wow, that thread has 155 pages ... hard to get through all that .... I did read the first page, though
OK, so I should download CM10 latest nightly version & install ... I don't seem to have a way to back up my data or current ROM since I don't have an internet connection that works. Yes, I could install to SD, but I've read that there can weird problems with this? So I was going to jump right in to an internal install, but it looks like I will lose data for my apps. Is there any advantage to downloading CM7 instead of 10? I ask only because I found a good site with good (newbie) instructions on doing CM7, and the site I found for CM10 has some stuff that I don't completely understand.
Really, I don't have great aspirations for using my NC ... I just need wifi to work so I can access my apps, and that's the only reason I am looking at flashing a new ROM. Is this the only way to go to fix wifi?
Nitrolady said:
Wow, that thread has 155 pages ... hard to get through all that .... I did read the first page, though
OK, so I should download CM10 latest nightly version & install ... I don't seem to have a way to back up my data or current ROM since I don't have an internet connection that works. Yes, I could install to SD, but I've read that there can weird problems with this? So I was going to jump right in to an internal install, but it looks like I will lose data for my apps. Is there any advantage to downloading CM7 instead of 10? I ask only because I found a good site with good (newbie) instructions on doing CM7, and the site I found for CM10 has some stuff that I don't completely understand.
Really, I don't have great aspirations for using my NC ... I just need wifi to work so I can access my apps, and that's the only reason I am looking at flashing a new ROM. Is this the only way to go to fix wifi?
Click to expand...
Click to collapse
For SD card cm10 installation (use Sandisk class 4 or 6)
Here is LeapinLar's thread to get you started http://forum.xda-developers.com/showthread.php?t=1941858
Get the latest CM10 nightly here http://get.cm/?device=encore
Make sure to use Gapps 20121011.
Here are the steps involved to make a bootable sd card:
Unzip the ...Rev5.zip
Use program Win32diskimager.exe to write the above unzipped image to SD card
Copy latest Cm10 nightly to sdcard (do not unzip)
Copy gapps 20121011 to SD card (do not unzip)
Safely eject SD card from computer
Backup your Nook apps/data to separate SD card or computer. If you have Clockwork Mod Recovery installed do a nandroid backup on sd
Turn off Nook Color
Insert SD card you created above
Turn on Nook color
Watch the Cm10 splash screen come to life.
Have you tried rebooting your Nook color to see if it can attach to your router?
CM7 is dated on gingerbread and 2.6.32 kernel. CM10 is Jellybean on 3.08+ kernel.
If you prefer rooted stock firmware 1.4.3 check out this thread http://forum.xda-developers.com/showthread.php?t=1494901
Many thanks, hwong96! I followed the directions and got CM10 working on an sd and wifi works fine. I am going to take a look at upgrading the stock software and then rooting to see if I can get that working as well, as I prefer the B&N interface/look-and-feel. But in the meantime, at least I have a functioning tablet again. Thank you!
Nitrolady said:
Many thanks, hwong96! I followed the directions and got CM10 working on an sd and wifi works fine. I am going to take a look at upgrading the stock software and then rooting to see if I can get that working as well, as I prefer the B&N interface/look-and-feel. But in the meantime, at least I have a functioning tablet again. Thank you!
Click to expand...
Click to collapse
Your welcome. Another satisfied customer.
Check out item A15 in LeapinLar's thread for stock ROM install via CWM http://forum.xda-developers.com/showthread.php?p=25354258#post25354258
Hi,
Firstly ought to say thanks to verygreen et al. for the awesome cyanogen mod, have 10.1.3 up and running on a nook hd+ mand it's great.
I'm trying to get: h-t-t-p-s://play.google.com/store/apps/details?id=com.bskyb.skygotablet&hl=en_GB to work on the nook hd+ with cyanogenmod, they have some pretty extreme protection measures against rooted devices. I've read just about the whole 292 pages of the thread on Sky Go (The mobile version) to work out how I might go about getting it to work.
I've tried manually moving su, and OTA rootkeeper, and changing ro.tags to "release-keys" in build.prop, I'm just taking a backup now to try changing ro.secure to 1 in default.prop in initrd.gz. (I couldn't figure out another way to get hold of the boot image, am I missing something obvious?).
Basically wanted to know if I'm fighting a losing battle here - or if there some way to actually unroot cyanogenmod that I'm not aware of. Don't really want to have to go back to stock to get this working, but the tablet is for the Mrs and I think she'd really like Sky Go.....
I know in the previous version people had some success running with a stock kernel - does anyone know if it's possible to replace the Cyanogenmod kernel with the stock nook one?
Cheers