Related
I'm currently using a 2GB MicroSD card with an apps2SD partition (Ext2) and a storage partition (FAT32)
I have a 4GB card that I'd like to move everything to. I could surely partition it the same way I did my 2GB card, but then it would be a blank, partitioned card. What's a good way to get all my apps and such moved over, as I'm running windows (which won't read the Ext2 partition)
Would Norton Ghost do it?
no try Ext2IFS_1_11a
can't remember where it is: if it doesnt work DL linux and boot into it from disc (no need to install) and copy onto disc from there...
Use linux.
plug in uSD card, do NOT mount. If it automounts, UNMOUNT it. Check device name "tail dmesg".
If device name is for example, sdb, then copy contents to hard disk;
"dd if=/dev/sdb of=~/sdbackup" -- this will create a file in your home directory called "sdbackup".
pull card, insert new card. If it mounts, unmount it. Again check device path.
"dd if=~/sdbackup of=/dev/sdb"
Now pull card, the data on the new card mirrors the old card. Plug back in. Note: we pull and then reinsert to make sure that the kernel reloads the partition table. There are other ways of forcing this, but this is the easiest and most fool-proof.
You have unpartitioned free space at the end of the card.
Use a combination of "parted" and "resize2fs" to resize/move partitions, or just use gparted to handle these operations graphically.
jook11 said:
I'm currently using a 2GB MicroSD card with an apps2SD partition (Ext2) and a storage partition (FAT32)
I have a 4GB card that I'd like to move everything to. I could surely partition it the same way I did my 2GB card, but then it would be a blank, partitioned card. What's a good way to get all my apps and such moved over, as I'm running windows (which won't read the Ext2 partition)
Would Norton Ghost do it?
Click to expand...
Click to collapse
Thanks for your help.
lbcoder said:
Use linux.
plug in uSD card, do NOT mount. If it automounts, UNMOUNT it. Check device name "tail dmesg".
If device name is for example, sdb, then copy contents to hard disk;
"dd if=/dev/sdb of=~/sdbackup" -- this will create a file in your home directory called "sdbackup".
pull card, insert new card. If it mounts, unmount it. Again check device path.
"dd if=~/sdbackup of=/dev/sdb"
Now pull card, the data on the new card mirrors the old card. Plug back in. Note: we pull and then reinsert to make sure that the kernel reloads the partition table. There are other ways of forcing this, but this is the easiest and most fool-proof.
You have unpartitioned free space at the end of the card.
Use a combination of "parted" and "resize2fs" to resize/move partitions, or just use gparted to handle these operations graphically.
Click to expand...
Click to collapse
Are these directions explicit/comprehensive? Will I need to partition first? I don't know very much at all about linux, but I've got an ubuntu cd downloading. I've poked at it a little before - I can at least get a terminal and follow your directions, if this is all there is to it.
edit
I'm trying copying things manually in ubuntu's file.. explorer.. thingy. Then I'll partition the new memory stick with gparted and copy the files there.
This seems more natural to me, since I'm not familiar with command-line operations much anyway. Personally, I don't see why it won't work.
edit again:
I don't have permission to copy the folders "app" "app-private" or "dalvik-cache"
How can I do this?
edit edit again
google found me a "sudo nautilus" command which seems to open a file browser window with more permissions. I still can't actually copy the folders I mentioned before, but I recreated them in my backup location and I can copy the contents. Maybe this will take care of it.
update:
nope, that worked for "app" and some (but not all) of "dalvik-cache" but not "app-private"
How do I gain permission to copy it?
I'm willing to go back to the terminal, but I get an error on the tail command. There's nothing found, or somesuch. Sorry, I meant to copy the message exactly but I forgot before I rebooted the computer I was doing it with.
Can anybody help me out a little more with this?
The error I get right off the bat is "tail: cannot open 'dmesg' for reading: no such file or directory"
The only access to linux I have is an ubuntu live CD
Code:
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
[email protected]:~$ tail dmesg
tail:cannot open `dmesg' for reading: No such file or directory
[email protected]:~$ _
MontAlbert said:
no try Ext2IFS_1_11a
can't remember where it is: if it doesnt work DL linux and boot into it from disc (no need to install) and copy onto disc from there...
Click to expand...
Click to collapse
How do I make use of this? It sounds like it should make Ext2 partitions appear in Windows Explorer just like anything else...
I installed it, but the Ext2 partition still doesn't show when I plug in the SD card. Do I need to do something particular?
I have rebooted.
Can anyone please give me more information on this, please? I've been poking at it different ways and still can't get it to work. Who knows something I don't?
jook11 said:
Can anyone please give me more information on this, please? I've been poking at it different ways and still can't get it to work. Who knows something I don't?
Click to expand...
Click to collapse
Code:
dmesg | tail
All the information to do this has been stated in this thread by now.
Any way to transfer Froyo from one SD card to another?
I would like to move it to a larger card but on my mac only 2 partitions mount but would love to put it on different device
Can this be done with adb?
is there a tool?
For windows you can use Win32DiskImager. You just select the letter of the drive containing the sd card (must be on an sd reader, not nook itself).
For linux you can use the command dd. You just have to do:
dd if=/dev/sd"letter of mount point here" of=/home/User/Desktop/SD_Backup.img
(to check for the letter you can use gparted, it can be gotten from the synaptic package manager if running ubuntu)
As for Mac, i have no clue. That being said you can easily download an Ubuntu live cd and use that to back it up
MattJ951 said:
For windows you can use Win32DiskImager. You just select the letter of the drive containing the sd card (must be on an sd reader, not nook itself).
For linux you can use the command dd. You just have to do:
dd if=/dev/sd"letter of mount point here" of=/home/User/Desktop/SD_Backup.img
(to check for the letter you can use gparted, it can be gotten from the synaptic package manager if running ubuntu)
As for Mac, i have no clue. That being said you can easily download an Ubuntu live cd and use that to back it up
Click to expand...
Click to collapse
How do I know the mount points? Can I just make one. Img file that will expand to the 4partitions?
From 1.1 Nook Color with 1.1 ghz overclock
Load up gParted once in ubuntu, in the top right it will have an arrow pointing down that lets you switch physical Hardrives (or in our case an SD card). Unless you have multiple HDD that are 2GB or 4GB (whatever size your SD card is) it should be easy to be able to find which one is the SD card. It will be /dev/sdX where x is the letter its mounted under.
Once you get that letter open up a terminal and type
dd if=/dev/sdX of=/home/"You User Name Here, exclude quotes"/Desktop/Backup.img
again, where X is the mount letter
Once it's done it you will have all 4 partitions backed up into one img file, so once you wish to restore it you just type
dd if=/home/"You User Name Here, exclude quotes"/Desktop/Backup.img of=/dev/sdX
(and again, X being the mount letter)
If you just wanted to say backup your /system partition you would do
dd if=/dev/sdX2 of=/home/"You User Name Here, exclude quotes"/Desktop/Backup.img
no number = backs up entire card
1 = backs up boot
2 = backs up system
3 = backs up data
4 = backs up media (stuff that your nook see's as being on the sd card such as what you download from a browser)
Canadoc said:
How do I know the mount points? Can I just make one. Img file that will expand to the 4partitions?
From 1.1 Nook Color with 1.1 ghz overclock
Click to expand...
Click to collapse
Is there a way to make a working backup (that can be recopied to a different card) without switching out of Windows Vista 32 bit? The backups I made with Win32DiskImager or WinImage don't let the NookColor get any farther than the flashing 'android_' screen at start when I copy them to a different card.
Try packing your boot, system, data and sdcard partitions into a .img file then use winimage/win32 or dd to write the image to a new sd card. (Kinda like making your own custom ROM image.)
RileyGrant said:
Try packing your boot, system, data and sdcard partitions into a .img file then use winimage/win32 or dd to write the image to a new sd card. (Kinda like making your own custom ROM image.)
Click to expand...
Click to collapse
@ RileyGrant - Thanks for the quick reply. I haven't done much coding in years and the Nook is my first attempt at rooting/roms/etc (better to brick a $250 toy than a $500 one...). Anyway, I don't have any problems following instructions - can you point me to somewhere that would explain the above procedure in more detail?
Thanks!
ShadowKatcher said:
Is there a way to make a working backup (that can be recopied to a different card) without switching out of Windows Vista 32 bit? The backups I made with Win32DiskImager or WinImage don't let the NookColor get any farther than the flashing 'android_' screen at start when I copy them to a different card.
Click to expand...
Click to collapse
I have the same problem. I 'm trying to move froyo to a 16GB sdcard but it keeps getting stuck on the "Android_" text. Any advice?
You probably failed to reproduce system permissions while copying files.
An easy way of transfering a working OS from one SD to another would be to:
- Download my USB mass storage utility in dev forum
-Install it
- Mount each partition of your SD to your PC, one at a time.. And do the following for each of them:
- Make tar/zip files of partition content
- Then uncompress the files on each new partition of the new SD..
Don't forget to expand 4th partition for maximum SD capacity...
Sam
Sent from my HTC Desire using XDA App
Worked like a charm! Thanks Sam!
I am absolutely pulling my hair out here. I have 3 16GB sd cards - 2 16gb ridata class 6, and one patriot class 4.
No matter what I do, I cannot get any of them to work with Froyo. ONLY my 16gb cards fail - I have various other 4 and 8gb cards floating around that work 100% fine.
With this image, I can boot the first time, run the makepart.sh command (which gives a "too many cylinders on disk error), and reboot fine again. When I go to finish formatting the SD card partition using formatpart.sh, it completes the process but never reboots - it just gets stuck on the Android... text in the bottom corner of the screen.
http://forum.xda-developers.com/showthread.php?t=922324
With these images, both 6.6 and 5.9, I can boot initially just fine but the sd card is only seen as 884mb. When I expand the partition to take up the rest of the free space (about 14gb) using EASEUS partition manager, I can boot fine next time but get literally hundreds of force closes to the point where I can't do anything. I've tried everything - creating new partitions as both logical and primary, resizing existing partitions, formatting from terminal and windows 7 x64, etc, etc.
http://forum.xda-developers.com/showthread.php?t=883175
So I've had it. If someone can make me a flashable and bootable SD card image (preferably 6.6, but 5.9 works too) that simply works with the 16GB cards (so I can actually utilize the extra space) and includes the below I will paypal them $125.
-Google Apps
-Market
-Camera and Voice apps removed
-Dropbox added
-Mount/System added (if the app does not take up the full screen force close it once)
-Nook Reader
-Phone and TelephonyProvider removed
-SetupWizard renamed (Can't get it to work. Go into Setting>Accounts & sync to add gmail account after your wireless has been setup)
-Flash installed and updated
-Default Launcher removed
-Zeam added
-Button Savior
-Angry Birds
-Astro File Manager
-Gingerbread keyboard
I basically want a version of the customized Nookie, but with Angry birds, astro, and button savior instead of softkeys (I can't stand softkeys).
To clarify, it only has to work with 16GB cards to get the $125. If it can work with 4 and/or 8GB size cards too, I'll add another $50.
Thanks for looking.
$500 if someone can de-expand my snookie "wife" from 16GB to 2GB and isolate her to sit in her fixed emcc and cook me up some gingerbread. lol. and yes i have used the search function already.
Edit: I did my own research and came to this, I did not create it but I read that some people are using it on 16gb SD cards and it works perfectly. So I decided to put it here.
Updated 2/6 new version! Pandora, YouTube, MP3's all play now. Flash might work w/o choppiness now too(?) - let us know.
Installing Nookie Froyo custom Android 2.2 ROM to boot off of an SD card:
The first thing you're going to need is a micro-SD card:
*at least 2GB in size
*at least 4GB is recommended, in order to have several GB's of storage on the SD Card partition (what Android reads as actual SD card storage)
*Class 6 or 10 is preferred
*Class 4 may be fine, 2 will likely be slow
Be aware that some companies claim to be offering a higher-class card than they really are (as there's no independent third-party that monitors the Class specification). So researching the brand you're considering is recommended.
You'll also need an SD card reader
If you have an Android phone, you may also be able to use it by placing the SD in your phone, selecting Mount as USB Drive on your phone, and proceeding from there.
First, download the latest version of Nookie
Unzip the .gz file (Winrar, 7zip, etc. Should work for that) so that you have an .img file that you're working with.
If you're on a PC, you're going to want to get a program called Win32DiskImager.
If you're on a Mac or Linux machine, you'll want dd.
Connect the SD card to your computer.
For PC Users:
open Win32DiskImager, select (using the button with the dots) the image file for Nookie that you downloaded, then select the drive of your SD Card (be very careful you're choosing your SD Card drive and not another!), then choose Write Image. *After a few minutes, you're all done!
For Mac Users (instructions credit nookdevs.com)
Open a terminal window.
Find which drive the sd card is mapped to: type in the terminal this:
diskutil list
Be very careful to identify the SD card and not your hard disk. Be VERY careful.
Now unmount that drive typing this:
diskutil unmountDisk /dev/disk#
(My computer is was disk2 replace # with your number.)
The computer should say:*Unmount of all volumes on disk was successful
dd if=NameOfNookieFroYoImage of=/dev/disk# bs=1m
Again, replace # with the number of your card. Everything needed should copy right over to the card.
RUNNING NOOKIE:
Simply insert your Nookie Froyo SD card into your nook and power on. As long as your SD card is in your NOOKcolor when you power it on or reboot, it will boot into Nookie Froyo. Everything that would normally be on an Android phone or tablet's internal memory (plus what would normally be on an SD card) is all going to be on your SD (this is why we recommended a card of 4GB or more).
One of the first things you'll notice is that there aren't any Google apps installed. You'll need to do this yourself (I would have loved to include them, but there are legalities, yadda yadda...).
ADB Installation of Google Apps:
1. You'll need to have adb (Android Debug Bridge) installed on your computer. This link explains in relatively easy terms how to get this going . . .http://forum.xda-developers.com/showthread.php?t=502010
Basically, you'll want to install the Android SDK and become familiar with the location of the directory it was installed in.
If you want to make it easy, move the 'Tools' directory (inside the SDK directory) onto c:/ . . . (or whatever your main hard drive's letter is) then, to get there, you'll simply type cd c:/tools
2. Having installed the SDK for adb access to your nook, now download the google apps files, and unzip the file so that it extracts the folder called 'system' into the 'Tools' directory in the SDK folder you downloaded.
3. Now you'll open a command prompt in Windows (start menu>run>type 'cmd') and navigate to the correct folder (cd [folder directory's path]). On Mac, this would be done via Terminal.
4. Now, with your NOOKcolor connected to your computer's USB port, type the following (of course, hit enter after each line):
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb push [here, enter the path to your SDK tools folder]\system system/
adb reboot
5. Now your NC will reboot. When it boots, you'll have Market, Gmail, Google Maps, and many more Google apps.
* If you're getting a "device not found" error when running adb, first, reboot your Nook and your computer and see if it changes.
If that fails, download and unzip this file, open install.exe, and follow the on-screen prompts (this will install drivers so your computer will recognize the nook).
If that doesn't work, try opening the Super User app on your nook and then issuing the commands.
If that still doesn't work, refer to the steps in this thread, repeating if necessary.
One of the first things to do:
Before you start, one of the most important things to remember with the current version of nookie is to turn the screen off/on (do this each time you boot your nook). There's some serious touchscreen lag by default, and this is the very simple solution to make it go away. Nothing fancy, just put the screen to sleep for a sec, and when you turn it back on, it'll be plenty responsive.
Click to expand...
Click to collapse
Here is a comment a user posted regarding the 16gb SD cards
I bought a class 10 16GB from Wintek, a brand I've never heard of and not only was the card unbearably slow -- so massive lag a points, it ended up corrupting itself... Anyways, I put in a 16 GB class 4 Kingston I have and not only is it faster than the supposed class 10 -- rarely any lag, I've not had any problems.
Click to expand...
Click to collapse
Source: (all credit for creating the rom)
Android Central
Edit 2: Since you also wanted to delete any signs of cell phone options, use this theme.
http://forum.xda-developers.com/showthread.php?t=944278
Hope this helps
So... since someone did end up "fixing" your problem, although not directly in response to your thread, are they going to get a nice surprise?
Chirp....Chirp....Chirp....Chirp...
(Just Kiding)
"computerpro", have you looked to see if the FAT is FAT16 or FAT32? Pretty sure a 14G FAT16 isn't going to fly.
khaytsus said:
"computerpro", have you looked to see if the FAT is FAT16 or FAT32? Pretty sure a 14G FAT16 isn't going to fly.
Click to expand...
Click to collapse
It's Fat32. I'll try that solution posted above when I get home from class, but brian said he is working on an update that should work with all cards and it should be out today. What's weird is that I can even boot with a 10GB partition with 4gb unallocated space. IT's just once I get up in the 12-14gb partition size range when things start corrupting themselves. And again, what's weird is that this happens across different brand and class cards. They are not defective. I am convinced it has something to do with the too many cylinder error I get while running makepart.sh
We shall see!
I keep seeing SD card rooting questions. I'm providing a link to some guides that describe in gory detail how to get CM7 up and running on an SD card (for both MAC OSX and PC). These guides are built off of verygreen's size-agnostic SD card thread and he deserves any and all credit. All that I (DrAstro) and DrWho have done is expound on the easy-to-follow steps that he provides from the perspective of trying to teach someone who is only mildly computer literate.
http://clubnook.com/forum/showthread.php?953-Rooting-Instructions
If this helps, go to verygreen's SIZE AGNOSTIC card thread and give him thanks.
I've just copied and pasted directly from Clubnook in case people don't want to link over there. If this is useful for you, comment and I'll keep it updated. If not, just let it fall into the ether...
CM7 - SD Card - Mac Version
INSTALLING CM7 (CyanogenMod 7/Android 2.3) ONTO A MICROSD CARD FOR USE WITH NOOK COLOR
Thanks to DrAstro for the following instructions:
I used the instructions from verygreen (who deserves any and all credit):
http://forum.xda-developers.com/show....php?t=1000957
I did nothing other than follow exactly what he said to do and was up and running with full android market access in about 10 minutes (with a 5 minute nap in the middle!). It was literally that easy. I’ve just expanded, in gory detail, on the basic.
Basically, what you are doing here is taking a microSD card, making it so that the nook color can boot from it, putting a new OS on that card (CM7) and then adding the android market. At the end, you will be able to run a more tablet-like experience from your microSD card without doing anything to the internal software that BN put on there. Here are steps, with heavy borrowing from verygreen’s guide. Hopefully you will read and understand what you are doing, so that you can pick and choose which OS zip you want to use.
NOTE: These are mac specific instructions, as that’s what I used!
1) Downloaded the following files and put them on your desktop:
generic-sdcard-v1.2.1.img.gz
(http://nook.handhelds.ru/sdimage/gen...-v1.2.1.img.gz) - This file makes your SD card bootable. This is probably the “hardest” part of the process as you have to “burn” this image to the card, not just “drag and drop”
update-cm-7.1.0-RCO-encore-2.6.32-beta3.1.zip
(http://coachz.inetpro.org/~dalingrin...32-beta3.1.zip) – This is the latest beta version of CM7 that was available at the time I did this! There may be some instability, but they fixed the battery issues with this release so the tradeoff is worth it.
Or get the latest stable version update-cm-7.0.2-encore.zip
(http://tinyurl.com/3vyanhh)
gapps-gb-20110307-signed.zip
(http://wiki.cyanogenmod.com/index.ph...Latest_Version) – This was the latest google apps version that was available when I did this. It will give you access to the android market!
2) Get any microSD card that you don't mind trashing the data on. There a LOTS of options out there, but I would HIGHLY SUGGEST getting a SANDISK, CLASS 4, 8 GB or 16 GB card. It is by far the most likely card to work well for you.
Also get a reader for your microSD card. I got one that plugs into my USB port and lets me see my microSD card on my desktop.
3) The first step is to install the .img file to the microSD card. First, you need to double click it on your desktop and let mac osx unzip it for you. It should do this nicely and your resultant file will be:
generic-sdcard-v1.2.1.img (i.e. the .gz at the end will go away)
To install the .img onto the microsd card, put the micro sd card into your card reader. It should pop up on your desktop as a disk. Mine was called “no name”.
To write the image (called burning the .img file to), you need to do the following:
-Find which drive the sd card is mapped to. To do this on mac, you can use the terminal:
how to open the terminal:
a) Go up to the magnifying glass in the top right of your mac.
b) Click on it and search for the word “terminal”. The first thing it finds should be a little black box with the word Terminal.
c) Click on that and a window should open on your desktop. That window should say something like Terminal – bash – 80x24 in the top line and then have a bunch of words, maybe something about Last login: and finally a line that ends in a dollar sign $. Here’s where you will type in your commands.)
Inside of that terminal, after the dollar sign ($) first, type:
cd Desktop
That will take you to your desktop. If you now type
ls
This should show you a list of all the files and folders on your desktop. All the terminal does is let you work with files using text commands rather than a nice graphical interface (i.e. clicking on windows and stuff)
Now that you know a couple basics on “terminals” type this:
diskutil list
This lists all the spaces on your computer where things are stored. You need to unmount the microSD card that you just plugged in. This will allow you to erase the card and put what you want on it. You need to look at this list and figure out which drive# is your microSD card. To the far right, you will see the disk size. Your microSD card should be around that same size as what you bought (for example, I’m using an 8GB card and found the disk that was around 7.5 GB).
Once you know the right disk (mine was disk1, yours may be different) unmount that drive by typing this:
diskutil unmountDisk /dev/disk<#>
(to be explicit, my drive was disk1 so I typed: diskutil unmountDisk /dev/disk1)
It should say: Unmount of all volumes on disk<#> was successful
Next type:
dd if=generic-sdcard-v1.1.img of=/dev/disk1
Everything needed should copy right over to the card. It took my laptop 140 s.
Now unmount the microSD card, but NOT the same way as what you just did. How? Remember when you connected the microSD card and a folder popped up on your desktop? Right click on that and select “unmount”. Note, it might be the case that the folder was renamed “boot”. If that’s the case, that is the folder to unmount.
After the microSD card disappears from your desktop, remove your microSD card from the laptop and plug it back in. The folder named “boot” should pop up on your desktop. Now the easy part.
Drag and drop the file:
update-cm-7.1.0-RCO-encore-2.6.32-beta3.1.zip or update-cm-7.0.2-encore.zip
Into the “boot” folder. Now right click on the “boot” folder and unmount.
Take out the microSD card and put it into the nook color. Turn the nook color on and it will boot. A little penguin might pop up followed by lots of techie looking things flashing on your screen. That’s fine. Keep an eye open and when its done, the screen will go blank. It should turn itself off, but probably won’t reboot. You need to hold down the power button for around 8 seconds to turn it back on. It will reboot into CM7.
(note: This is updated from prior CM7 installations (i.e. these instructions are specific to installing the CM7 beta). If your unhappy with the performance of the beta, you can install a CM7 version that’s labeled as “stable”. The stable versions occasionally need to be turned off manually (i.e. by holding down the power button for 8 seconds)).
You’re almost there. You should have a homescreen with a few icons. Find the one labeled “settings”. Open this up, go to Wireless & networks, and connect to your wireless network. Now CM7 is ready to go online and you can turn off the nook color and install the Android Market.
You need to turn off the nook color. Take out the microSD card and connect it to your computer again. This time, two folders will pop up. One called “boot” and one called “sdcard” or something similar
This time, drag and drop:
gapps-gb-20110307-signed.zip
into the boot folder. Now comes the second hardest part, booting into recovery. The process depends on the version you are installing.
If you are installing the beta version I reference above then put the microSD card into the nook color and boot into CM7. Once you’re in CM7, hold the power button until a menu pops up and choose to “reboot”. Choose to reboot into “recovery” and you should be all set.
If you’re installing one of the “stable” versions, put the microSD card into the nook color and boot to Recovery Mode. In order to do this hold the nook N key and press and hold the power button for ~5-6 seconds. It may take a couple of tries. The screen may turn off a couple times. You may boot into CM7 a couple times. Eventually, with luck on your side, you will successfully boot into “recovery mode” and google apps will be installed. Once you manage to boot into recovery the screen will flash up lots of techie text, similar to when you started CM7. It should go blank when this is done. At this point you can turn it off by holding power for around 8 seconds. Turn it back on, follow the screen instructions and you should be good to go with an android tablet with the full android market, all running from your microSD card!
Setup Wizard stuck?
I actually got this working on the first try a couple weeks ago and it was fantastic!
I was able to play netflix and flash for the first time, and now my dad wants me to do his nook the same way. He has a 16GB sd card though, and the original instructions didn't work on >8gb cards. I can't just image his SD card to my SD card because I couldn't get my google account to de-register etc, so I started from scratch with my card and planned to image to his before configuring any user accounts.
I'm having repeated trouble with my retry attempt though
Basic CM7 install with the generic-sdcard-v1.2.1 and update-cm-7.1.0-RC0-encore-2.6.32-beta3.1 (the ones recommended as of today in the instructions)
I set up wireless access, shut down, and backed up my card at this point.
Copy the current 20110307 gapps to the boot partition, eject, put it back in the nook, boot into recover (I've gotten good at this), it installs, shut down. Back up my card again as I figure this is where I'll want to start the other card.
Back to the Nook, boot up, get past the CyanogenMod scateboard screen, and it goes to "Setup Wizard". This should be for setting up the Google Apps Marketplace account I think, except it's completely black except for grey bar across the top with "Setup Wizard" on it, and the bar across the bottom with menu/back/search/battery indicator etc (these do nothing).
I can press power button and get only two options: shut down the tablet or reboot the tablet. I can rotate the nook and the UI changes orientation. Nothing else does anything as far as I can tell.
Anyone else seen this problem? I've searched, and even tried to post to the dev thread, but I can't due to low post count.
Help! (and thanks in advance!)
*.gz img file not recognizable & not zipped
Hi. I rooted my Nook with Autonooter and love using it. YouTube and all work fine, but I would like to redo with CM7. I have all that I need, except I'm caught with the img file this time round. It has an extension .gz. Win32DiskImager does not recognize it. Some sites say that it needs to be unzipped, but it's not zipped. I hate being stuck before even beginning. I hope that you can explain why I'm having this trouble. TY!
The .gz file is just a compressed .img file.
There are a number of Windows apps that can de-comress the file, for example: 7-Zip
Martyn
Hi Martyn, Thanks again. Now, DiskImager is coming up with an error when I try to write. It says that there is not enough space on the disk. The unzipped img file shows to be 117megs, while my SD card is 16gigs. After I got the error, I chose to format the disk but have the same error. Do you mind to help again?
I saw this suggested: "I did a full format (not quick) and used WinImage to write the SD card instead. Works every time since then," by TL Jester here. I"m just curious why there always seems to be a roadblock.
sGooss said:
Hi Martyn, Thanks again. Now, DiskImager is coming up with an error when I try to write. It says that there is not enough space on the disk. The unzipped img file shows to be 117megs, while my SD card is 16gigs. After I got the error, I chose to format the disk but have the same error. Do you mind to help again?
Click to expand...
Click to collapse
I had this same problem, i discovered that it created a partition on the sd card... I had easeus partition master home edition, which i used to resixe the partition and you can see your full 16GB then.
sGooss said:
Hi Martyn, Thanks again. Now, DiskImager is coming up with an error when I try to write. It says that there is not enough space on the disk. The unzipped img file shows to be 117megs, while my SD card is 16gigs. After I got the error, I chose to format the disk but have the same error. Do you mind to help again?
Click to expand...
Click to collapse
I had an error message like this too. It turns out it was because I was trying to use the internal card reader in my laptop. I bought an external USB card reader, and it worked fine with the same card.
Originally Posted by sGooss View Post
Hi Martyn, Thanks again. Now, DiskImager is coming up with an error when I try to write. It says that there is not enough space on the disk. The unzipped img file shows to be 117megs, while my SD card is 16gigs. After I got the error, I chose to format the disk but have the same error. Do you mind to help again?
babyfine24 said:
I had this same problem, i discovered that it created a partition on the sd card... I had easeus partition master home edition, which i used to resixe the partition and you can see your full 16GB then.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ditto, same problem, same solution. When you write the image to the card it seems to create a default boot partition of 117mg. When I tried to put both the rom and gapps in the boot partition after writing the image, I got that message (but not every time). So I made the boot partition bigger before adding rom and gapps, using Easus. I increased it to 150mg or so, that was plenty.
One time image+rom+gapps barely fit in the boot partition, and while installing I got an error that said not enough space in disc. I redid it, making the partition bigger, and it worked. I think the installation process may temporarily use some of that boot partition space.
Hi,
This is my first android device, so am pretty much a newbie for android.
Have created this mod to mount external SD card partition as internal partition.
I took pointers from a lot of threads on xda forums to get this working, so I feel bound to share it.
Note: Have only tested it with Android 4.1.
(I'm not responsible for any Damage to your phone. Use at your own risk.)
Note: This will likely result in data loss. Backup!
Required :
1. Root Access
2. init.d support click here
3. Root Browser click here
4. SManager click here
5. An sd card (duh!) (with class 10 SD cards preferable)
6. Some way to partition your SD Card (like MiniTool Partition Manager)
Install instructions:
1. Create two ‘fat32’ partitions on SD card(EDIT: PS: both partitions should be Primary). Your first partition will be mounted as normal extSd card, and your second partition will be mounted as internal SD Card for your apps. (I partitioned my 64GB(10^9 bytes) sd card with ~16 GB 1st partition and ~42 GB 2nd partition)
2. Copy and paste “mountSd” to etc/init.d folder. (If you don’t have such a folder, means you lack init.d support. click here and follow instructions to enable it) This script creates another mount point called ‘sdcard2’ and mounts current internal sd card there. It also tries to mount second partition to ‘sdcard0’ location, but seems to fail some times (as fat32 is not natively supported linux partition it seems, but could be wrong), so step 3 is required.
3. Copy ‘mountSdFailSafe.txt’ to your phone’s ‘/data’ folder. Now with ‘SManager’, register this file as script with ‘su’ and ‘boot’ selected. (click and hold script -> in context menu click ‘Open As..’ -> ‘Script/Executable’ -> Is Script = true, select ‘su’ and ‘boot’ buttons)
4. Restart.
This should do it. Once restarted, second partition will be shown as internal memory.
Note:
You will lose all app data and other app related customizations. You may be able to restore it by simply copy pasting ‘Android’ folder from ‘/storage/sdcard2’ to ‘/storage/sdcard0’. This has not been tested by me but should work theoretically (as I started with a blank phone, and so did not need to back up my app data). Or you could use Titanium Backup.
Some Issues that occur due to this mod:
I have been using this mod since the past 2 weeks, and the phone is quite stable with this mod.
The only issue I have faced is that when connected to PC (Windows 8) through USB, ‘My Computer’ keeps crashing unless and until you disconnect the phone. Otherwise it seems to be working fine. To circumvent this issue I have been using Samba to share files between PC and my phone.
Please share how it works out for you guys.
Other Notes:
I tried to get this working with ext4 partition, which has a +ves that it will not require step ‘3’ of install instructions and supports file sizes >4GB, but there are loads of permission issues happening, which I could not solve.
(Thought of setting “set GID” bit and then finding and adding all users to root group but failed. Also tried to set owner group ‘sdcard_rw’ without much success. May be someone who knows linux better may know how to solve this, Could not find much help on the forums as it seems others are facing a similar problem see more)
Thanks to:
For basic idea (PS: do not use the given method exactly as you will end up in a boot loop. For some reason, ‘sdcard1’ mount point has to be mounted by system only and can’t be mounted any other way, it seems.)
http://forum.xda-developers.com/showthread.php?t=2180733
Edit:
Simplified installation if you do not care for easy accessibility to your orig internal memory:
Use this video tutorial by ashwin123:
The only exceptions are that, you need to partition your card,
and you have to use the file 'mountSdFailSafe.txt' instead of the file in the package mentioned by him.
Nice
Waiting for someone to test it n confirm it successfully works
Still here
N!geR -> E!ch0
NisJ said:
Hi,
This is my first android device, so am pretty much a newbie for android.
Have created this mod to mount external SD card partition as internal partition.
I took pointers from a lot of threads on xda forums to get this working, so I feel bound to share it.
Note: Have only tested it with Android 4.1.
(I'm not responsible for any Damage to your phone. Use at your own risk.)
Note: This will likely result in data loss. Backup!
Required :
1. Root Access
2. init.d support click here
3. Root Browser click here
4. SManager click here
5. An sd card (duh!) (with class 10 SD cards preferable)
6. Some way to partition your SD Card (like MiniTool Partition Manager)
Install instructions:
1. Create two ‘fat32’ partitions on SD card. Your first partition will be mounted as normal extSd card, and your second partition will be mounted as internal SD Card for your apps. (I partitioned my 64GB(10^9 bytes) sd card with ~16 GB 1st partition and ~42 GB 2nd partition)
2. Copy and paste “mountSd” to etc/init.d folder. (If you don’t have such a folder, means you lack init.d support. click here and follow instructions to enable it) This script creates another mount point called ‘sdcard2’ and mounts current internal sd card there. It also tries to mount second partition to ‘sdcard0’ location, but seems to fail some times (as fat32 is not natively supported linux partition it seems, but could be wrong), so step 3 is required.
3. Copy ‘mountSdFailSafe.txt’ to your phone’s ‘/data’ folder. Now with ‘SManager’, register this file as script with ‘su’ and ‘boot’ selected. (click and hold script -> in context menu click ‘Open As..’ -> ‘Script/Executable’ -> Is Script = true, select ‘su’ and ‘boot’ buttons)
4. Restart.
This should do it. Once restarted, second partition will be shown as internal memory.
Note:
You will lose all app data and other app related customizations. You may be able to restore it by simply copy pasting ‘Android’ folder from ‘/storage/sdcard2’ to ‘/storage/sdcard0’. This has not been tested by me but should work theoretically (as I started with a blank phone, and so did not need to back up my app data). Or you could use Titanium Backup.
Some Issues that occur due to this mod:
I have been using this mod since the past 2 weeks, and the phone is quite stable with this mod.
The only issue I have faced is that when connected to PC (Windows 8) through USB, ‘My Computer’ keeps crashing unless and until you disconnect the phone. Otherwise it seems to be working fine. To circumvent this issue I have been using Samba to share files between PC and my phone.
Please share how it works out for you guys.
Other Notes:
I tried to get this working with ext4 partition, which has a +ves that it will not require step ‘3’ of install instructions and supports file sizes >4GB, but there are loads of permission issues happening, which I could not solve.
(Thought of setting “set GID” bit and then finding and adding all users to root group but failed. Also tried to set owner group ‘sdcard_rw’ without much success. May be someone who knows linux better may know how to solve this, Could not find much help on the forums as it seems others are facing a similar problem see more)
Thanks to:
For basic idea (PS: do not use the given method exactly as you will end up in a boot loop. For some reason, ‘sdcard1’ mount point has to be mounted by system only and can’t be mounted any other way, it seems.)
http://forum.xda-developers.com/showthread.php?t=2180733
Click to expand...
Click to collapse
Am interested to try this but before I do, just wanted to check when you say data is lost, is it due to the lost of the original /data partition? Or just due to the sd card's partition?
What's the outcome when this is done, I mean do we have two data partitions one from the original phone's memory and another with the sdcard? And in the settings menu, will we get to choose to send apps over to sd? Thanks
grim_ripper said:
Am interested to try this but before I do, just wanted to check when you say data is lost, is it due to the lost of the original /data partition? Or just due to the sd card's partition?
What's the outcome when this is done, I mean do we have two data partitions one from the original phone's memory and another with the sdcard? And in the settings menu, will we get to choose to send apps over to sd? Thanks
Click to expand...
Click to collapse
Your application data will be lost in a way, as orig internal sd card will be mounted to 'sdcard2' mount point(newly created). All your app data will be installed to your memory card's second partition, which is now the new internal sdcard. To access your orig data, you will have to go to it through a file manager, and apps or media scanner will not be able to access this memory any more.
The scripts provided will not format your internal memory.
Still apk files, dalvik cache etc, will still take up your original internal memory's space.
Partitioning your sd card will probably format it as well unless you take special precaution (ie. through shrink volume).
Hope it makes sense...?
NisJ said:
Your application data will be lost in a way, as orig internal sd card will be mounted to 'sdcard2' mount point(newly created). All your app data will be installed to your memory card's second partition, which is now the new internal sdcard. To access your orig data, you will have to go to it through a file manager, and apps or media scanner will not be able to access this memory any more.
The scripts provided will not format your internal memory.
Still apk files, dalvik cache etc, will still take up your original internal memory's space.
Partitioning your sd card will probably format it as well unless you take special precaution (ie. through shrink volume).
Hope it makes sense...?
Click to expand...
Click to collapse
It makes sense, just am confused on how the system will still recognize the original storage when the sd card's storage is supposingly replacing it. Could you post a screen shot of your storage from settings?
grim_ripper said:
It makes sense, just am confused on how the system will still recognize the original storage when the sd card's storage is supposingly replacing it. Could you post a screen shot of your storage from settings?
Click to expand...
Click to collapse
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
NisJ said:
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
Click to expand...
Click to collapse
Can u do a tutorial video how to install this script bro?
Cuz the installation steps r bit complicated
Still here
N!geR -> E!ch0
NisJ said:
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
Click to expand...
Click to collapse
Phone keeps rebooting now, couldn't copy it to /etc/init.d
I think it has something to do with having data running in the background, now I don't know what to do with my phone
EDIT: Ok, manage to recover from the reboot state, had to deny root access to my file explorer. I think the reboot was caused when I set permission to write for /system. Anyway, everytime I keep trying to copy to /etc/init.d, I get a permission denied so am not sure what I should do now.
grim_ripper said:
Phone keeps rebooting now, couldn't copy it to /etc/init.d
I think it has something to do with having data running in the background, now I don't know what to do with my phone
EDIT: Ok, manage to recover from the reboot state, had to deny root access to my file explorer. I think the reboot was caused when I set permission to write for /system. Anyway, everytime I keep trying to copy to /etc/init.d, I get a permission denied so am not sure what I should do now.
Click to expand...
Click to collapse
When ever you copy something to init.d it will reboot, or does it go into boot loop?
To check if it worked correctly, see if new mount point storage/sdcard2 was created..
EDIT: If it worked correctly, then you could move to next step.
else you could also skip it, and goto the next step of SManager, but in that case you will lose access to your original internal storage as it wont be mounted to sdcard2.
E!ch0 said:
Can u do a tutorial video how to install this script bro?
Cuz the installation steps r bit complicated
Still here
N!geR -> E!ch0
Click to expand...
Click to collapse
Creating a video will take time at least til sat... prob more.
Will see if I can create a simplified install instructions once i reach home.
NisJ said:
When ever you copy something to init.d it will reboot, or does it go into boot loop?
To check if it worked correctly, see if new mount point storage/sdcard2 was created..
EDIT: If it worked correctly, then you could move to next step.
else you could also skip it, and goto the next step of SManager, but in that case you will lose access to your original internal storage as it wont be mounted to sdcard2.
Click to expand...
Click to collapse
What happens is that everytime I try to mount /system as writable, it reboots and hence I can't copy either files to their designated location
EDIT: Also, now everytime I reboot, there's a popup that says USB connectivity has stopped, and if I go under settings->storage, settings fc. I'm thinking this has something to do with two partitions on the sd card so I hope it all goes away when this works or I revert back to as it was.
EDIT 2: So I managed to get all the files to the appropriate place using terminal and managed to get the script to run at boot. Alas, the phone doesn't detect my sdcard at all now and still throws the USB connectivity error at boot. Once I removed the sdcard, everything works alright. Also, I figured the solution to the reboot (haven't tested it yet as I wanted to resolve my sdcard first):
http://forum.xda-developers.com/showthread.php?t=2317432
EDIT 3: Got the reboot solve, but the sdcard can't be read and I tried plugging it into my other phone, the first partition is only read. I can't get minitool to even find the 2nd partition. I am thinking I need to get a card reader to plug it into my laptop. Anyway, I went through your script and open the log file it used, says that there's an invalid argument for mount. Any idea?
Final Edit: Got it working! I had to re-partition my sdcard and made both partitions primary so maybe you might want to add that in OP as MiniTool by default selected the 2nd partition as logical
grim_ripper said:
What happens is that everytime I try to mount /system as writable, it reboots and hence I can't copy either files to their designated location
EDIT: Also, now everytime I reboot, there's a popup that says USB connectivity has stopped, and if I go under settings->storage, settings fc. I'm thinking this has something to do with two partitions on the sd card so I hope it all goes away when this works or I revert back to as it was.
EDIT 2: So I managed to get all the files to the appropriate place using terminal and managed to get the script to run at boot. Alas, the phone doesn't detect my sdcard at all now and still throws the USB connectivity error at boot. Once I removed the sdcard, everything works alright. Also, I figured the solution to the reboot (haven't tested it yet as I wanted to resolve my sdcard first):
http://forum.xda-developers.com/showthread.php?t=2317432
EDIT 3: Got the reboot solve, but the sdcard can't be read and I tried plugging it into my other phone, the first partition is only read. I can't get minitool to even find the 2nd partition. I am thinking I need to get a card reader to plug it into my laptop. Anyway, I went through your script and open the log file it used, says that there's an invalid argument for mount. Any idea?
Click to expand...
Click to collapse
Why are you trying to mount /system as rw?
for getting init.d support you just have to download the apk from mentioned thread and install it, and then fallow instruction in app.
you can mount root as rw with the foll command if you want, and that is exactly what is done in he scripts as well if you will check:
Code:
mount -o remount,rw /
also to check if partition is created on sd card, type the command:
Code:
blkid
and see if
Code:
/dev/block/vold/179:34
is listed
if not post the output and i'll see what i can do.
grim_ripper said:
Final Edit: Got it working! I had to re-partition my sdcard and made both partitions primary so maybe you might want to add that in OP as MiniTool by default selected the 2nd partition as logical
Click to expand...
Click to collapse
EDIT: Correct, you need both the partitions to be primary. got out of my mind when posting the tutorial.
NisJ said:
Why are you trying to mount /system as rw?
for getting init.d support you just have to download the apk from mentioned thread and install it, and then fallow instruction in app.
you can mount root as rw with the foll command if you want, and that is exactly what is done in he scripts as well if you will check:
Code:
mount -o remount,rw /
also to check if partition is created on sd card, type the command:
Code:
blkid
and see if
Code:
/dev/block/vold/179:34
is listed
if not post the output and i'll see what i can do.
EDIT: Correct, you need both the partitions to be primary. got out of my mind when posting the tutorial.
Click to expand...
Click to collapse
For whatever reason, my /etc folder is actually a link from /system/etc
Could you post a way to revert back? I think my apps are acting all funny now and just want to revert back to before. Thanks!
grim_ripper said:
Could you post a way to revert back? I think my apps are acting all funny now and just want to revert back to before. Thanks!
Click to expand...
Click to collapse
The apps are behaving funny because you have lost their data as I had warned in the original post.
To fix do either of the foll:
1. reinstall app, and start fresh.
or
2. restore from Titanium backup if you had created...
or
3. copy paste 'Android' folder from sdcard2 if it is created to 'sdcard0'
To remove and revert, just delete the files from int.d, and stop scheduling it in SManger.
Note: to un schedule it from smanager, you first have to remove memory card, un schedule and then put in your memory card (this is coz when phone boots up, it is in standard way, with 8gb internal but, after script is executed SManager looses its data too.
How complicated will it be to make this compatible with 4.2.2?
grim_ripper said:
How complicated will it be to make this compatible with 4.2.2?
Click to expand...
Click to collapse
Ideally should be possible, unless something has changed majorly, but I haven't tried it, as am waiting for OTA update. If it is not forth coming in 2-3 weeks, may be tempted to flash nordic rom and try.
NisJ said:
Ideally should be possible, unless something has changed majorly, but I haven't tried it, as am waiting for OTA update. If it is not forth coming in 2-3 weeks, may be tempted to flash nordic rom and try.
Click to expand...
Click to collapse
I did try but nothing happened, am guessing it has permission issues or something on those lines
grim_ripper said:
I did try but nothing happened, am guessing it has permission issues or something on those lines
Click to expand...
Click to collapse
Could you be more specific? Like system restarts etc...
Else in terminal try out what I Gave in post no 12 and give me what the output is for both the commands in the terminal.
Note: execute them with super user credentials.
Thanks
NisJ said:
Could you be more specific? Like system restarts etc...
Else in terminal try out what I Gave in post no 12 and give me what the output is for both the commands in the terminal.
Note: execute them with super user credentials.
Thanks
Click to expand...
Click to collapse
on the 4.2.2 update, it doesnt recognize the second partition even if it is formatted to primary and set to active. there r definitely some updates done in that field and plus i cant get the init.d rights on the phone as the test.log file is absent in the data folder..no matter what i do i just cant get it straight with the present procedure. please try it on 4.2 and there r more frequent updates on the nordiac then the local version. so i decided to flash it rather than waiting for ota update