Related
Hey guys ive been lurking around for a while troubleshooting my builds, I have figured out that when I run my android build off of the sd card by itself everything runs well, but once i put in my 10GB of music everything starts to fall appart and i get sod after a minute or two in the lockscreen. I was wondering if creating a separate ext2 partition for android to boot from and keeping my data on the other partition would provide me with any more stability. BTW im using the stock 16 gig class 2 card that came with the phone
Where on the SD card is your music? Root or in the Android folder. I ask because I have a 2 year old 8GB class 4 SD card that came with my preloaded CGO8 navigation (ICO8, but for US) and have never formatted. I've loaded most of the Android builds and most I've had no problems, other than typical for the build.
SD cards are digital. Unlike analog hard disks data is not fragmented. Formatting does not serve a useful purpose for an SD card. Even deleting files (except protected) deleting is just as, if not more, effective.
Do some research, think independently to come up with your own conclusions, but these are mine.
Oh, by the way, this is not the right forum for your question....you should have done some research before posting.
i was not asking about formating i was asking about partitioning and if running android from an ext2 partition on the sd card would create more stability on the build
audscott said:
SD cards are digital. Unlike analog hard disks data is not fragmented.
Do some research, think independently to come up with your own conclusions, but these are mine.
Oh, by the way, this is not the right forum for your question....you should have done some research before posting.
Click to expand...
Click to collapse
Analog hard disks? No fragmentation on flash media? Wow, sounds like you need to do some research...
I also have the same issue where if I put Android along with my music on the 16gb card, it gets stuck at jumping to kernal on reboot.
im copying my music on the new sd now will report back if the problem persists, but i have a feeling that running off of an ext2 partition will provide us with better r/w speeds, similar to ubuntu running on an ntfs partition instead of ext4
Having music (anything else) on your SD card should not really affect Android. Most builds are in an 'Android' folder, so that is where the system looks for its information. This may slow things down a bit (just like an overloaded HDD) but generally there should not be much difference.
Creating and ext2 partition will not help. Of course, now that I have said that, I have an ext2 partition on my SD card that was left from using my rooted G1 with cyanogen mod and Apps2SD. By default, my android build on my HD2 automatically looked in that partition for apps (froyo does this).
So, I do not think it will change anything about freezing or 'jumping to kernal' but it does have its uses.
EDIT: And, since WinMo is actually booting android, I don't think containing your android stuff in an .ext2 partition would even work. Needs to be FAT32 for haret to see it. (this is my assumption, not necessarily a fact)
Isn't the rootfs.img file actually like a simulated ext2 filesystem? Doesn't this file emulate the device memory? I'm not exactly sure, maybe someone else can expand on this. I don't think there is any benefit to partitioning the card in the current state of the hd2's development. Maybe when we are able to flash nand, nand will be formatted to ext2.
polo735 said:
Isn't the rootfs.img file actually like a simulated ext2 filesystem? Doesn't this file emulate the device memory? I'm not exactly sure, maybe someone else can expand on this. I don't think there is any benefit to partitioning the card in the current state of the hd2's development. Maybe when we are able to flash nand, nand will be formatted to ext2.
Click to expand...
Click to collapse
Well, there is that and the system.ext2 and data.img. This is all the files in Android (basically).
But with these files, android knows where to look to find them, placing them in your own ext2 partition will hide them from android.
When we are able to flash to nand (and now) an ext2 partition will allow you to store apps on that partition, given you are able to move apps to SD, which is not currently possible in our builds.
I installed apps to my SD card on my G1 (on an ext2 partition), so when I used Froyo on my HD2, android was able to read from that partition and use my old apps. All that means is that I did not have to reinstall all my old apps, and save space in the data.img created by android.
audscott said:
Where on the SD card is your music? Root or in the Android folder. I ask because I have a 2 year old 8GB class 4 SD card that came with my preloaded CGO8 navigation (ICO8, but for US) and have never formatted. I've loaded most of the Android builds and most I've had no problems, other than typical for the build.
SD cards are digital. Unlike analog hard disks data is not fragmented. Formatting does not serve a useful purpose for an SD card. Even deleting files (except protected) deleting is just as, if not more, effective.
Do some research, think independently to come up with your own conclusions, but these are mine.
Oh, by the way, this is not the right forum for your question....you should have done some research before posting.
Click to expand...
Click to collapse
First of all, before you call someone out you might want to do some research of your own so you don't come across looking like a moron. Fragmentation happens regardless of the actual hardware, and most file systems are vulnerable (whether it be fat, ntfs, ext2, ext4, etc). And while deleting files and reformatting end in the same result, a quick reformat makes far fewer writes to the card by simply wiping the allocation table. Each file name must be modified individually if you delete them, adding unnecessary wear to the card. As for a hard drive being "analog", it stores its data the same way as a memory card - 0's and 1's - which is digital. Just a little refresher there.
Now, as for the question at hand, which is completely appropriate for this forum as it directly concerns the development and installation of android on our HD2's, the use of ext2 for the android files has been done successfully on other winmo devices in order to increase stability and speed in the system. In fact I have done this very thing on my Kaiser in the past. Whether its possible with our current HD2 setup is another matter, so I'll direct you to these links - do a little reading and play around with it, let us know what you find. I'll probably look at it myself this weekend as a stop-gap until a full NAND flash becomes available, which hopefully is sooner rather than later - I'll report back if I find something.
http://www.androidonhtc.com/wiki/Installing_Android
http://android-devs.org/forum/viewtopic.php?f=56&t=194&sid=69cc2d8c93262ff8c70de594d50e5874
In my own experience, I have a 4Gig class 10 and 16Gig class 2 (stock).
I use my 4Gig for Android test runs.
I use my 16Gig for my Android currently in use.
I have my Music in at the root /Music
Android is in the traditional /Android
Any pics I take I just move over /DCIM
I haven't experience any corruption. Before testing, I format the SD card on my computer with 64k or 32K blocks. I copy over my saved /Music and /DCIM and then load the new Android in /Android.
ALWAYS Eject the SD card. Keeping those rules and I haven't had issues.
Well I switched to my other 16gig class 2 and my problems went away, it seems the stock card was going bad but not using a 20yr old file system would be nice regardless
Sent from my HTC HD2 using XDA App
... oh, and about fragmentation, I'm not a software engineer (I'm electronics engineer), but I wouldn't get too worried about SD card fragmentation. It can happen, but not in the same way as a physical HD.
SD cards can do random access reads/writes much better than a physical hard drive. However, if you've formatted your blocks too small, the controller has to piece together two bits of info instead of one.
Example: 64k file written to 8k formatted SD, will have to piece together 8 blocks.
A 64k file written to 64k formatted SD is written all to one block.
The flip-side is if you have a bunch of small files (1k - 5k) and you're formatted at 64k, you've just wasted 63k of a 64k block writing a 1k file. It's inefficient.
willgill said:
Example: 64k file written to 8k formatted SD, will have to piece together 8 blocks.
A 64k file written to 64k formatted SD is written all to one block.
The flip-side is if you have a bunch of small files (1k - 5k) and you're formatted at 64k, you've just wasted 63k of a 64k block writing a 1k file. It's inefficient.
Click to expand...
Click to collapse
Considering the sizes of most music and picture files these days and the fact that all Android little files are inside one large file, I believe going with 64k blocks would be better. Even going with a larger block size than 64k might be a good idea. Too bad 64k is the limit.
Larger block sizes might be inefficient when dealing with system folders like C drive in windows or system folder in linux since they contain a huge number of small files. That is why windows default is 4k.
This is one of those things that I've always assumed would work, but I don't think I've seen anyone actually confirm it or talk about it yet. Before doing any of this I did a clean wipe of everything, just to avoid confusion on my part.
Step 1) I DD'ed the entire filesystem to an 8GB microSD that I have.
Step 2) Mounted p1 from SD (which is a copy of P1 from internal)
Step 3a) Pulled ramdisk
Step 3b) Extracted ramdisk
Step 3c) Changed all mmcblk0 refs to mmcblk1 in init.rc
Step 3d) Recompiled ramdisk
Step 3e) Pushed ramdisk back to p1 on SD
Step 4) Shut down Nook, reboot, confirm via mount command that all mounted volumes are mmcblk1
As I said, this is nothing revolutionary, but I figured it could be good for testing, especially if anyone wants to take a shot at a potentially dangerous mod like recovery or installing a fresh /system. Also, if I ever seriously messed up my internal memory, I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way.
Very interesting. Thanks for the effort. Might be worth saving the image in case someone actually DOES brick their nook.
I'm curious as to the specifics. Aren't there several filesystems on the device? What did you do to pull/extract/recompile the ramdisk?
APKs
Are you able to install apk files to the emulated rom/nand on SD card...
also are you able to mount an extra partion on the card....
Thanks
"I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way"
That will be great if we can push those files back to NAND
FYI, Holding just power + Nook buttons for about 15-20 sec will bring up the factury reset screen.
nook'r said:
Are you able to install apk files to the emulated rom/nand on SD card...
Click to expand...
Click to collapse
I haven't yet, but I don't see why not. Nothing especially different about it as opposed to the internal filesystem.
nook'r said:
also are you able to mount an extra partion on the card....
Click to expand...
Click to collapse
Right now I left vold alone, so it rather stupidly mounts p1, which contains all the critical stuff. I don't see any reason why vold couldn't be made to point to another seperate partition. (which is what I did with some other trials when using the internal ramdisk to boot to /system on the SD - left p1 as a "sdcard" partition)
nook'r said:
"I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way"
That will be great if we can push those files back to NAND
Click to expand...
Click to collapse
I've backed up my own partitions individually. I suppose if I zero'd empty space and gzipped I could probably find some way to write the entire partition table to somewhere.
Would this be useful to someone who would want to dual boot with Ubuntu or MeeGo?
Could this be used to "dual boot" the fully stock Nook in store and then from card when you want to be free?
Homer
Homer_S_xda said:
Could this be used to "dual boot" the fully stock Nook in store and then from card when you want to be free?
Homer
Click to expand...
Click to collapse
This can be used for whatever you want to use it for. I've been running this way for quite a while, and everything works just as it would if you're running from the internal. It's just like dual booting on your PC.
The first (that I saw) and best documentation for setting this up can be found at:
http://blog.fsck.com/
axe2 said:
This can be used for whatever you want to use it for. I've been running this way for quite a while, and everything works just as it would if you're running from the internal. It's just like dual booting on your PC.
The first (that I saw) and best documentation for setting this up can be found at:
http://blog.fsck.com/
Click to expand...
Click to collapse
This is intriguing.
I would love to run everything off a micro sd and then pop it out to put it back to stock.
Would a 1GB micro sd work ok for this?
Someone needs to come up with an automated way to do this. That would be awesome.
moovius said:
This is intriguing.
I would love to run everything off a micro sd and then pop it out to put it back to stock.
Would a 1GB micro sd work ok for this?
Someone needs to come up with an automated way to do this. That would be awesome.
Click to expand...
Click to collapse
1GB is going to be too small to hold the whole system, but 4GB should work.
It should be something that would be scriptable assuming that the required tools exist on the standard rom, but I don't know if the tools are on there.
You could probably get to 1 GB if you dumped all the recovery junk and made media and data tiny. I'm trying to think if there's anything earing up tons of space besides /system.
Of course, just because you can doesn't mean you should.
how about multiple partitions on a 16gb
clockworx said:
This is one of those things that I've always assumed would work, but I don't think I've seen anyone actually confirm it or talk about it yet. Before doing any of this I did a clean wipe of everything, just to avoid confusion on my part.
Step 1) I DD'ed the entire filesystem to an 8GB microSD that I have.
Step 2) Mounted p1 from SD (which is a copy of P1 from internal)
Step 3a) Pulled ramdisk
Step 3b) Extracted ramdisk
Step 3c) Changed all mmcblk0 refs to mmcblk1 in init.rc
Step 3d) Recompiled ramdisk
Step 3e) Pushed ramdisk back to p1 on SD
Step 4) Shut down Nook, reboot, confirm via mount command that all mounted volumes are mmcblk1
As I said, this is nothing revolutionary, but I figured it could be good for testing, especially if anyone wants to take a shot at a potentially dangerous mod like recovery or installing a fresh /system. Also, if I ever seriously messed up my internal memory, I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way.
Click to expand...
Click to collapse
Think someone could put together a noob guide for this? I'd like to try running a rooted version of Nook Color from SDCARD (partitioned?) on my stock Nook Color.
If possible? Please & Thanks...
Ok after many hours tonight I have managed to put together a couple .zip files that will install a modified vold.fstab on your Nook Color. (I am a total n00b at this)
The EMMC of the Nook Color has a partition for the ROM and a 5 GB partition that's mostly if not completely unused. Presently, there aren't any 3rd-party managers to move apps to that unused partition, so I modified the vold.fstab and am now able to use that partition for apps, files, etc.
NC.SWAP.VOLD.ZIP swaps the way the SD and EMMC directories are mounted. By swapping the mount points, and renaming EMMC to SDCARD, your apps, etc., will install to the internal storage, vs. installing to your SDCARD. Your physical SDcard is automatically mounted as "EMMC."
This also means that the music player still finds files, you can move files to "EMMC," and you can still eject the SDcard ("EMMC"), put it back in and it still shows up automatically. Now your NC won't freak out if you pull the card out without unmounting it - all of the apps are on the actual EMMC. You'd just find the SDcard under /mnt/emmc instead of /mnt/sdcard.
Because this ZIP file maps the change at an OS level, when you boot to recovery, your NC sees SD as the SDcard, so no issues occur. When you boot into your ROM, the mount points are swapped and you'll have access to the renamed "SDCARD" (5 GB) on your NC.
Use CWR 3.0.1.0 to install the .zip and check out the results with File Manager.
Thanks go out to Clark008, luciferii and Cali^Gal from #nookcolor, Loonacy and Raymondull from #Cyanogenmod, and EpicFail1236 from XDA.
Sorry if this is a bit crude, it's my first script ever. I would be happy to get any advice on how to make this better!
EDIT: I have been looking into renaming the emmc mount to say SD-External or better yet making it mount as /mnt/sdcard/sd-ext. it might be possible, ill be looking into it as soon as I can got laid up for a bit.
"Because this ZIP file maps the change at an OS level, when you boot to recovery, your NC sees SD as the SDcard, so no issues occur. When you boot into your ROM, the mount points are swapped and you'll have access to the renamed "SDCARD" (5 GB) on your NC."
/\/\ That clarifies a lot compared to the brief orig post. Will likely be flashing it this weekend.
BTW, if this expands and you need this 2nd post just have a mod give it to you. Thanks again!
BRILLIANT. Will be definitely testing this later today. Can't wait to run SD Tools on this
Sent from my NookColor using Tapatalk
it works! interesting how it'll work out as to unmounting, flashing roms. but with emmc being useless this is fantastic.
Thank you for the effort and time place in this mod
Yeah. The whole point of this was to utilize the 5GB internal emmc and not waste it. The next step is to mod the CWM to mount emmc as /sdcard so you can flash your zips from where you download them to (usually /mnt/sdcard/download), which in this case, goes to your emmc. But CWM will mount your external sdcard instead. For the time being, we can just put the zips we need to flash to the external sdcard, ie. /mnt/emmc.
I don't know if anyone noticed it yet, but if you usb mount after the swap, the transfer speed is kind of slow (~1.5mbps). I don't know if this is due to the emmc or that the read ahead cache needs to be tweaked.
We're open to make this even better. Feel free to comment and provide feedback.
This sounds like a step in the right direction, however, what I would like to see would be merging the emmc with the internal storage. What I mean is this; right now, when I go into "Storage", I see an "SD card" (8gb), "Internal Storage" (0.92gb), and "/mnt/emmc" (5gb). Why can't we combine the .93 Internal and the 5gb emmc together to make a 5.92gb Internal storage and eliminate the emmc from teh storage area? I'm sure there is a reason that I'm not aware of, but it seems that this would be the same as just about every other device. I am pretty sure the ROM is running from the emmc partition, so that has to have something to do with it, but I don't see a purpose for 3 storage places. I keep getting errors when I try to download apps and I don't even have very many installed. I have had to move most of them to the SD card to make room and some apps don't like to be installed on the SD card.
Another option would be to swap the emmc with the Internal storage. Then we'd be using the 5gb and the .92 gb would be sitting there doing nothing instead. Again, I'm sure there are reasons for this, I'm just asking to learn.
I agree.. ideally having the emmc mount be part of the system would be ideal.
Calla969 said:
This sounds like a step in the right direction, however, what I would like to see would be merging the emmc with the internal storage. What I mean is this; right now, when I go into "Storage", I see an "SD card" (8gb), "Internal Storage" (0.92gb), and "/mnt/emmc" (5gb). Why can't we combine the .93 Internal and the 5gb emmc together to make a 5.92gb Internal storage and eliminate the emmc from teh storage area? I'm sure there is a reason that I'm not aware of, but it seems that this would be the same as just about every other device. I am pretty sure the ROM is running from the emmc partition, so that has to have something to do with it, but I don't see a purpose for 3 storage places. I keep getting errors when I try to download apps and I don't even have very many installed. I have had to move most of them to the SD card to make room and some apps don't like to be installed on the SD card.
Another option would be to swap the emmc with the Internal storage. Then we'd be using the 5gb and the .92 gb would be sitting there doing nothing instead. Again, I'm sure there are reasons for this, I'm just asking to learn.
Click to expand...
Click to collapse
i have no idea TBH but thats far beyond my ability. really it would be nice to symlink emmc to the SD card or the other way around. the issue is that you cant symlink with fat partitions :-/
This is neet. I don't know enough to comment, but it looks valuble for some people.
I just use my stock emmc for music storage and let apps sit on SD w/ videos.
WobbleTheHutt said:
i have no idea TBH but thats far beyond my ability. really it would be nice to symlink emmc to the SD card or the other way around. the issue is that you cant symlink with fat partitions :-/
Click to expand...
Click to collapse
No, but you can symlink to them. Why not set vold.fstab to mount the partitions onto other names and make symlinks named /sdcard -> /othername? That way, the symlinks can do their jobs or rearranging the namespace to suit our needs.
The ramfs isn't FAT32, is it?
I'm an old cmdline type, tricks like this are used all the time to fool software with stubborn opinions about filenames.
Dennis
Jiggity Janx said:
If this works as effectively as it sounds like it will it's gonna rock! With the multiple wifi/bluetooth file transfer options I can say bye bye to the need for an sd card!
EDIT: I think this thread is eerily quiet because of the popular advice written up HERE. Specifically #5...
IMO, with a great write up on the best ways to work with this, all of the things it will affect (positive and negative), and the proper words of warning then the individuals that take it upon themselves to modify their devices are the only ones that can be held responsible if it doesn't work out as they had hoped. They also have to understand that when they work outside the boundaries of an accepted "standard" that they are somewhat desolate and will need to come back into the fold before they can/will be helped...
Just my .02...
Click to expand...
Click to collapse
This may be slightly off topic, but I cannot for the life of me figure out what that post is complaining/ talking about, I have had no trouble bouncing between HC, CM7 and stock.
All you have to do is flash to stock and then worst case you force the boot failure and the nook resets its self automatically
The last few posts on that message are myself and another person who have had not trouble with that now the OP hasn't responded so i'm not sure what to make up that post.
Is it real and an actual issue?
Or did the poster overreact to something?
Can some one please explain it to me if I am wrong about something in using a EMMC version of HC?
chisleu said:
This is neet. I don't know enough to comment, but it looks valuble for some people.
I just use my stock emmc for music storage and let apps sit on SD w/ videos.
Click to expand...
Click to collapse
Seems neet to me also. Always interested in using both emmc and sd space.
@ chisleau - I like the concept of putting all my music on emmc. Do you use an option in CM7 to install or move all your apps to your SD card?
thinking out loud (and not actually doing it) -- but we know that /data is /dev/block/mmcblk0p6 and and the "media" or "emmc" is located at /dev/block/mmcblk0p8 -- can't we just repartition and merge the two?
minotauri said:
thinking out loud (and not actually doing it) -- but we know that /data is /dev/block/mmcblk0p6 and and the "media" or "emmc" is located at /dev/block/mmcblk0p8 -- can't we just repartition and merge the two?
Click to expand...
Click to collapse
We can repartition but don't do it for this Reason -#5 http://forum.xda-developers.com/showpost.php?p=12494638&postcount=1
http://forum.xda-developers.com/showpost.php?p=12494666&postcount=2
ROMs that follow proper packaging - This emmc swap mod is one of them. So we're fine for those who are still hesitating.
Clark008 said:
ROMs that follow proper packaging - This emmc swap mod is one of them. So we're fine for those who are still hesitating.
Click to expand...
Click to collapse
Yep, I was hesitating, but between your post above and the "Thanks" from fattire to the OP, that is all the encouragement I need to take the plunge.
A few questions, tho, if someone can help me to understand this better....
I guess until I saw the OP, I did not realize that all apps in CM7 are installed to the SD card, as when I look at my installed apps in App Mgr, they don't show as being on the SD card. Is this some sort of CM7 voodoo or are my apps really on the internal memory?
Right now, with CM7, I am using the EMMC partition to store my music, under "My Files/Music". Power Amp can see this folder and it will play all my music just fine from within that directory on the internal partition, so if I install this update, what will that do to the 5Gb of internal storage I have now and the music on it?
Also, if I do install this update, what will happen to the apps and their associated data that I already have installed? Is this best done on a fresh build or will everything (apps/data and music) be A-OK after the Swap update is applied?
Just want to know what I am getting into by applying this update, as I have things pretty stable right now. If I could roll with apps on internal and music on SD, I would be more than fine with that, as long as I don't lose any of my apps/data/music in the process. If this is just mere partition re-naming/re-pointing, then I suspect my assets will remain intact?
Thanks to all who collaborated on this project!
why can't the entire internal partitions be imaged?
i use dd all the time to backup my sd card installs in case a test kernel or nightly goes poorly- or to burn a fresh install for multiple people. I just pop in the sd card into my laptop and burn the image back to the sd card.
if this was possible i'd have no issues with running off internal entirely if i could just burn the img. and get everything back as stock, including important device identifiers incase those were erased.
Need undo
This did what it's supposed to do but it seems to be causing a problem with the way I'm booting from sd. Is there a way to undo this?
Bump since I found this useful. +1 for CWM sdcard/emmc swap to enable SDcard-less flashing goodness from ROM Manager.
Hi,
I have a working rooted 8gb nook tablet. The tablet has stock recovery installed on it and I don't think I want to change it to cwm at this point, unless I absolutely have to. My question is -- can I use this method to backup my current ROM in case I do mess something up (like deleting build.prop file for instance)? The problem that I have is that the sd card ends up with only 50mb of free space after burning the image onto it and that is obviously not enough for the backup. I tried partitioning the card and creating an ext2 allocation (perhaps I need to use a different kind?) in addition to the tiny 50mb one, but cwm doesn't seem to recognize it and still tries to backup into the tiny space.
I would greatly appreciate any help.
Thank you.
Resize the partition of the SD card using a partition manager, or format the card and put these files on it (in root).
Forgot to mention in my original post that I did try resizing the 50mb partition to 1gb, but then the tablet just stopped booting at all. I had to take out the card and wait for a minute or two before it would start booting normally again.
I will try your files now. Thank you for quick response!
Nope, that did not work, unfortunately. It just booted normally, not from the sd card. But isn't the whole point of burning that image is to make the card into a 50mb one? I don't understand all the technicalities, but that seems reasonable, why else would they make it particularly 50mb large? And resizing the partition doesn't lead me anywhere either, as I mentioned above.
Maybe someone could point me in the right direction?
Right. So, the partition has to be checked as active if using MTP or flags should be on if using the other one. And the magical 50mb size allocation don't matter after all. Gotcha.
I am new at rooting, this is the first device I have tried to root. I followed the thread for a triple boot CM7 , CM9 and CM10 (also stock OS) from Malloneem. I decided to only flash CM7 and CM10 to NT 1.4.3. Everything worked great, except during the initial setup of both CM7 and CM10 it will not recognize my WiFi. I have tried twice, after first time I wiped NT and reformatted the sd card and started from scratch. same result both times.
I read through the replies and noticed that someone else had the same problem. the response said to wipe the cache and it should fix the dalvik. I wiped both the cache then tried and then wiped the dalvik and had the same results. With the CM10 it says "turning on wifi" and stays there.
I am a new member to xda so I cannot post a reply to the original thread.
Any help would be much appreciated.
If I cannot get this to work is there another method where you can use CM10 and stock OS? (something that is extreamly easy to follow)
Bears85 said:
I am new at rooting, this is the first device I have tried to root. I followed the thread for a triple boot CM7 , CM9 and CM10 (also stock OS) from Malloneem. I decided to only flash CM7 and CM10 to NT 1.4.3. Everything worked great, except during the initial setup of both CM7 and CM10 it will not recognize my WiFi. I have tried twice, after first time I wiped NT and reformatted the sd card and started from scratch. same result both times.
I read through the replies and noticed that someone else had the same problem. the response said to wipe the cache and it should fix the dalvik. I wiped both the cache then tried and then wiped the dalvik and had the same results. With the CM10 it says "turning on wifi" and stays there.
I am a new member to xda so I cannot post a reply to the original thread.
Any help would be much appreciated.
If I cannot get this to work is there another method where you can use CM10 and stock OS? (something that is extreamly easy to follow)
Click to expand...
Click to collapse
You can use this:
http://iamafanof.wordpress.com/2013...-1-jellybean-sdcard-img-for-nook-tablet-0110/
Write the image file to an SD card and you'll be good to go. You can use a repartitioning software to expand the partitions on your SD if you want. Use the instructions on the link I provided.
The SD card image will contain CM10.1 4.1.2. If you want to use a different ROM you can download the SDC version of any ROM ( has to be SDC!), place the zip on your SD card or internal storage. Boot into SDC recovery and installed the zip file. You'll need the GAPPS zip also (which has to be SDC also.)
Thank you for the help. My appologies for the redundant question but when I flash this ROM I will be able to bounce between CM10 and the stock B& N OS correct?
Bears85 said:
Thank you for the help. My appologies for the redundant question but when I flash this ROM I will be able to bounce between CM10 and the stock B& N OS correct?
Click to expand...
Click to collapse
Yes. Because CM 10 will be on your SD card. Stock will be on your internal. If your internal partitions or anything is messed up ( maybe the reason you can't boot stock) you can tell from CM.
datallboy said:
Yes. Because CM 10 will be on your SD card. Stock will be on your internal. If your internal partitions or anything is messed up ( maybe the reason you can't boot stock) you can tell from CM.
Click to expand...
Click to collapse
Thank you again. I have read throught the instructions on the link you provided and I am a little confused on the partitioning part. As I mentioned before this is my first time rooting anything. The instructions on the triple boot regarding the partitioning of the sdc were clear giving sizes for the newly created partitions etc., I didn't see that on this link (unless I missed it). Could you explain it so a newbie can understand it?
Thanks.
Bears85 said:
Thank you again. I have read throught the instructions on the link you provided and I am a little confused on the partitioning part. As I mentioned before this is my first time rooting anything. The instructions on the triple boot regarding the partitioning of the sdc were clear giving sizes for the newly created partitions etc., I didn't see that on this link (unless I missed it). Could you explain it so a newbie can understand it?
Thanks.
Click to expand...
Click to collapse
Well is there any reason why you would like triple boot? You need a fairly good size SD card if you want three systems. I just provided the simplest way to run cm on the nook. Write the image to your SD card and it will make it boot able. If you want to triple boot then setup your SD card partitions like you had before, but you only need to install the zips as alt boots.
Again, you probably don't need triple boot. Cm10+ has everything you'll need.
datallboy said:
Well is there any reason why you would like triple boot? You need a fairly good size SD card if you want three systems. I just provided the simplest way to run cm on the nook. Write the image to your SD card and it will make it boot able. If you want to triple boot then setup your SD card partitions like you had before, but you only need to install the zips as alt boots.
Again, you probably don't need triple boot. Cm10+ has everything you'll need.
Click to expand...
Click to collapse
No, I dont need the triple boot. Being a newbie I may have misread something (probably the case) but the link you gave me directed me to partition the sd card. it was this portion that was not clear to me. I was referencing the directions for partitioning on the triple boot thread as a comparison. The site you gave me said to partition the card but gave reference as to how big to make each partition. I don't need the triple boot.
My kid uses the NT to help read (read to me, etc...) I wanted something to get more of a tablet feel while keeping the stock system as well.
Thank you again. I appreciate the help. I will look at it again.
Bears85 said:
No, I dont need the triple boot. Being a newbie I may have misread something (probably the case) but the link you gave me directed me to partition the sd card. it was this portion that was not clear to me. I was referencing the directions for partitioning on the triple boot thread as a comparison. The site you gave me said to partition the card but gave reference as to how big to make each partition. I don't need the triple boot.
My kid uses the NT to help read (read to me, etc...) I wanted something to get more of a tablet feel while keeping the stock system as well.
Thank you again. I appreciate the help. I will look at it again.
Click to expand...
Click to collapse
On the iamafanof site you can scroll down there will be an SDC image. There is a difference between the image and the zips. All you need to do is download the SDC image, write it go your SD card using an file writer ( win32 disk writer will do) and your SD card will be ready to boot. Put it in your nook and and it will boot cyanoboot and should automatically do a SDC boot. It takes a little bit for the first boot to start ( usually 2 or 3 minutes)
Once you get your nook to boot cm I can tell you how to expand your SD partitions to hold more apps.
If you still have problems with WiFi it may be a different problem ( shouldn't happen).
If you need help or need a step by step guide I can find one or make one for you.
datallboy said:
...
If you need help or need a step by step guide I can find one or make one for you.
Click to expand...
Click to collapse
Just in time, "hot off the press" (almost) step-by-step guide: http://iamafanof.wordpress.com/2013...-2-jellybean-sdcard-img-for-nook-tablet-0416/.
For a more stable ROM build, use the CM10.0 image dated 12/31 in cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img.rar posted at http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/.
datallboy said:
On the iamafanof site you can scroll down there will be an SDC image. There is a difference between the image and the zips. All you need to do is download the SDC image, write it go your SD card using an file writer ( win32 disk writer will do) and your SD card will be ready to boot. Put it in your nook and and it will boot cyanoboot and should automatically do a SDC boot. It takes a little bit for the first boot to start ( usually 2 or 3 minutes)
Once you get your nook to boot cm I can tell you how to expand your SD partitions to hold more apps.
If you still have problems with WiFi it may be a different problem ( shouldn't happen).
If you need help or need a step by step guide I can find one or make one for you.
Click to expand...
Click to collapse
Thank you for your help. I worked and was simple. If you could explain the partitioning that would be great. If not, its working just the way I want it.
Thank you again!!
Bears85 said:
Thank you for your help. I worked and was simple. If you could explain the partitioning that would be great. If not, its working just the way I want it.
Thank you again!!
Click to expand...
Click to collapse
You have 4 partitions on your SD card: boot, system, data, sdcard. Your boot partition holds the files the boot CM. This is where recovery, mlo, uboot, etc is. System holds files essential for the ROM to work.
The only two you need to worry about are data and SD. Your data partitions holds apps. That is when you download an app the files in the apk file are put there. This would be like your internal storage for any phone or tablet. SD card is like an external SD card for your phone or tablet. Its where extra data files, photos, music etc go.
Depending on what size of SD card you have determines how big you can expand your data or SD partition.
Using a partitioning software ( like GParted) you can change the partitions and expand them to the side you want. I have a 16 GB SD card. So I expanded my data partition to 4 GB, and the rest went to SD card. Its okay to delete data or SD partition to expand it, but don't delete boot or system because you'll have to reformat the card and write the image file to the card again ( and ain't nobody got time for that.)
datallboy said:
You have 4 partitions on your SD card: boot, system, data, sdcard. Your boot partition holds the files the boot CM. This is where recovery, mlo, uboot, etc is. System holds files essential for the ROM to work.
The only two you need to worry about are data and SD. Your data partitions holds apps. That is when you download an app the files in the apk file are put there. This would be like your internal storage for any phone or tablet. SD card is like an external SD card for your phone or tablet. Its where extra data files, photos, music etc go.
Depending on what size of SD card you have determines how big you can expand your data or SD partition.
Using a partitioning software ( like GParted) you can change the partitions and expand them to the side you want. I have a 16 GB SD card. So I expanded my data partition to 4 GB, and the rest went to SD card. Its okay to delete data or SD partition to expand it, but don't delete boot or system because you'll have to reformat the card and write the image file to the card again ( and ain't nobody got time for that.)
Click to expand...
Click to collapse
This worked great!! thanks for all your help!!