Related
Can someone point me to a thread for setting up either or both of
Nookie Froyo or CM7 stable on a bootable microsd card. I wondered
about partitioning and which files systems were used on cards?
Do either come with CWR 3.0.2.x installed for targeting the card
instead of emmc? I have a sandisk 2gb card and a class 6 16gb card
available for targeting. Are the booted systems rooted? Can I image
the cards (via the windows image tool, or USB booted gparted image
tool) for backup or do I need to nandroid to the sdcard partition and
then copy the sdcard partition to windows for backup?
I still have to register the color nook, as the registration servers have
been down most of the day. Do I need to wait to boot the sd card
bootable until the device is registered?
thanks in advance
Followup got Nookie Froyo SD working
I searched both market and amazon app store and cannot find dolphin hd.
I find lots of add ons for HD but not the app.
rom manager says it installed CWR 3.0.1.0 but telling to reboot to recovery
doesn't work? Is it installing on the emmc instead of the sd card?
I'm confused about how rom manager would know the boot 'disk'
is SD not emmc and to manipulate SD not emmc? same for CWR?
thanks
more info -- RM did write CWR to emmc
how do I get CWR on the Nookie Froyo bootable?
how do I 'properly' shutdown Nookie Froyo (in the unix sense) so
it 'sync's and shuts down daemons, like unix 'shutdown -n' would?
Is there a rom manager & CWR that are SD card aware (knows
to write to proper sd card partition for what its doing)?
pointer to links if anyone knows?
CWR
this may help with CWR
http://forum.xda-developers.com/showthread.php?t=971197
Made a SD Bootable CWR ....
but I wonder if the software is setup to update EMMC or SD (Nookie Froyo)?
How would one know? I'm guessing since the recover system is ram based
that one takes out the SD card after booting, and inserts the card to be
targeted?
Thanks for the pointer.
Hello, I'm new to the Nook world. I'm Currently Trying to Root a Stock Nook v1.3.0.
Here's how the about screen looks (Minus User Info)
::Software Version::
1.3.0
::Model Number::
BNRV200
::Serial Number::
2014370085802011
I have a 2G SanDisk MicroSD Card.
I've followed the directions on this thread to the T.
http://forum.xda-developers.com/showthread.php?t=1054027&highlight=1+3
I have my SD Card setup with the Clockwork Image.
http://monster-rootpack.googlecode.com
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
So here's the issue.
I turn of my Nook, put in my Micro SD, plug in USB. But the nook boots straight into the Nook 1.3.0. No ClockworkMod Recovery.
I've tried using an 8G, 4G, and a couple of 2G's I have laying around. None of them work.
I'm using my phone as the SD connector, mounted in Clockwork. SD Only, nothing else (Can't do ADB, that's how I know its only the SD connected).
I just wanna get MIUI on my nook. Can somebody please help me, as I'd love to have this Nook Rooted.
Please feel free to PM me any info you have.
Just to make this point clear, you run the risk of damaging your cell phone by using it as a SD connector.
There is no need to root the factory firmware to install MIUI.
First download this bootable CWM image, HERE
If you are using windows, download Win32DiskImager, HERE
Use Win32DiskImager to flash the bootable CWM image to your SD card, this is where it can damage your phone if you don’t select the correct drive
Once the image has been flashed to the SD card, use windows explorer to copy the MIUI zip file onto the SD card.
With the Nook Color off, put that SD card into your NC, and turn it on
Now it should boot into recovery, and you can flash the MIUI zip to the device
Don't use your phone as your SD reader and make sure to run Win32 as admin.
Sent from space
koopakid08 said:
Don't use your phone as your SD reader and make sure to run Win32 as admin.
Sent from space
Click to expand...
Click to collapse
Thanks, I'm going to try and find my R4 Card Micro SD Adpator.
Sent from my MIUI.us Sensation 4G using Tapatalk
I am writing this n00b friendly howto for anybody who will encounter similar problem that I had, since I couldn't find much info how to solve it on this forum.
Recently I have flashed CM9 and later CM10 preview on my Galaxy S3 I9300 with 64 GB Sandisk SDXC card. The card was formatted in Samsung stock ROM, so naturally, it was formatted as exFAT. CM9 and CM10 reported it as "damaged SD card", but this was expected, since open source AOSP ROMs do not support exFAT. However, when restored to original stock ROM via CWM recovery, the stock ROM was showing "damaged SD card" error, too! Not sure why this has happened - the only info I found was someone mentioning that "CM9 is known to do this on exFAT cards" on this forum.
Connecting the card (via adapter and card reader) to computer didn't help - it showed as a RAW partition, Windows was asking to format it and even reported incorrect size. Trying about 7 different open source and commercial recovery tools did not help. However, if booted to recovery mode, CWM could see the card just perfectly!
So this is how to get the data back:
1. Boot to CWM recovery mode (power off the phone, then hold Volume Up-Home-Power buttons for 5 sec)
2. When in CWM recovery mode, connect phone via USB to computer. The phone should be recognized and drivers installed (if not already).
Note: I had problems with Windows recognizing the phone in recovery mode on some PCs (only 1 out of 3 worked, actually). To solve this, installed drivers from Samsung Galaxy S3 Toolkit (first step after toolkit installation) and problem gone: http://forum.xda-developers.com/showthread.php?t=1703488
3. Run adb command (from Android SDK platform tools) to ensure that the phone is visible to operating system - it should show serial number of the device and "recovery" next to it:
adb.exe devices
4. Browse the phone to find the location of sdcard (mine was /sdcard):
adb.exe shell
Note: when first time connected to phone via "adb.exe shell", running "ls" in /sdcard directory came out empty. Had to "exit" from shell and do "adb.exe shell" again.
5. Pull the files from your device using "adb.exe pull" command:
adb.exe pull /sdcard c:\temp
replace /sdcard with your sdcard directory on the phone (if different) and c:\temp with other folder on your PC, if you wish.
That's it! After files are copied, reboot to stock ROM and reformat the card. You can now copy all data back to it from your PC!
Now I'm trying to find a way to format the card to FAT32. Seems not so straightforward with 64GB cards!
Sincerely,
satanxda
Man! pity I didn't read this before I formatted my "damaged" card ... good to know there's solution for future
Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2
Yeah this needs to be listed in one of the stickies
Sent from my GT-I9300 using xda app-developers app
I had the same problem. From stock went to CM10, exFat got corrupted and then went back to Stock still external storage card showed as damaged.
I took the SD card out and put in adapter and then connected to PC. Then from command prompt ran chkdsk <Drive_Letter:> /f and it fixed the errors without me copying the files to PC.
Hope this helps.
And to format 64GB sd card from exFAT to FAT32, use guiformat tool or EaseUS partition master. I have formatted my card to FAT32 using EaseUS partition master.
Sent from my GT-I9300 using xda app-developers app
With this problem you can restore data in more easily way.
Insert your SDcard in CardReader, connect to PC, run Command line (cmd) and type:
chkdsk X: /f ,
where X is your card volume name. After operations is complete, you can use you card again and NO data had been lost.
Sorry for my bad english.
mahendra1020 said:
And to format 64GB sd card from exFAT to FAT32, use guiformat tool or EaseUS partition master. I have formatted my card to FAT32 using EaseUS partition master.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Tried it before posting this howto, but EaseUS didn't see the card at all. Windows disk manager in the meantime reported incorrect size (27 GB for a 64 GB card) and when formatted with guiformat I got a 27 GB partition. Could be a problem with card reader - will try another one as soon as I get my hands on one ;]
mahendra1020, magicm3n: in my case using chkdsk was not possible, since Windows showed the SD card as a disk with not formatted RAW partition (suggested to format it). To run chkdsk, partition type must be recognized.
And by the way, thanks everyone for comments and suggestions!
Sincerely,
satanxda
satanxda said:
Tried it before posting this howto, but EaseUS didn't see the card at all. Windows disk manager in the meantime reported incorrect size (27 GB for a 64 GB card) and when formatted with guiformat I got a 27 GB partition. Could be a problem with card reader - will try another one as soon as I get my hands on one ;]
mahendra1020, magicm3n: in my case using chkdsk was not possible, since Windows showed the SD card as a disk with not formatted RAW partition (suggested to format it). To run chkdsk, partition type must be recognized.
And by the way, thanks everyone for comments and suggestions!
Sincerely,
satanxda
Click to expand...
Click to collapse
Yeah even in my case windows showed sd card as not formatted but chkdsk still works.
Try /f instead of /r as arguments for chkdsk.
Are u formatting as fat or fat32? For me both the tool worked.
Sent from my GT-I9300 using xda app-developers app
mahendra1020 said:
Yeah even in my case windows showed sd card as not formatted but chkdsk still works.
Try /f instead of /r as arguments for chkdsk.
Are u formatting as fat or fat32? For me both the tool worked.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Probably you are right. Checkdisk button was disabled for me when right-clicking->Properties on the drive, but anyway Windows was reporting wrong size of the card, so I didn't want to risk forcing repairing and didn't invest too much time to that. But as I said, maybe it's the problem of my quite old SD card reader
By the way, successfully formatted from exFAT to FAT32 by using this Android tweak to mount the SD card as USB Mass Storage device on PC (so basically turning the phone itself into a card reader) and formatting in Windows with guiformat:
http://forum.xda-developers.com/showthread.php?t=1711009
http://www.ridgecrop.demon.co.uk/guiformat.htm
Sincerely,
satanxda
And did you get CM10 to read all of the 64 gigabytes?
For me CM cannot read the SD card over 32 gb.
Formatted my 64gb SDCard using EASEUS Partition Master to FAT32.
CM9 recognizes all the 59GB+, reads and writes on the card just fine. Didn't install CM10 yet, so don't know if that will work...
FWIW; the Chkdsk /f command did fix mine, and just as well, cause nothing I did (on multiple machines) could get the darn thing to mount in CWM.
yep, chkdsk does fix my 16g exFat card, and it works back just fine now. and before, i tried the CWM way twice, nothing i could pull up, os hints "remote object '/sdcard' not a file or directory"
I've had the same issue, and am really struggling to get anywhere at all with it...
I tried the method in the first post, but running ls on /extSdCard just gives an empty directory...
When I mount it in a reader in windows, it reports zero size and a 'please insert disc into Removable Disc (E: )' when I try and open it...
Even when I just threw my hands up and said 'ok phone, format it' it just says 'unmounting SD card' and then just backs into the normal screen.
At my wits end with this, I suspect the card might be fried, but want to get in if possible as it has my only stock backup!
Running the most recent CM9
kmfs said:
I tried the method in the first post, but running ls on /extSdCard just gives an empty directory...
Click to expand...
Click to collapse
What about /storage/extSdCard/ ?
Kangburra said:
What about /storage/extSdCard/ ?
Click to expand...
Click to collapse
hmm, well storage isn't part of the structure when is run ls after using 'adb.exe shell'
tried it anyway, get 'can't cd to /storage/extSdCard'
interestingly, when I try and get into just the 'sdcard', which I guess is just the internal storage?
I run 'cd sdcard' and the folder that I get into is /data/media
this is confusing, anybody any ideas?
mahendra1020 said:
I had the same problem. From stock went to CM10, exFat got corrupted and then went back to Stock still external storage card showed as damaged.
I took the SD card out and put in adapter and then connected to PC. Then from command prompt ran chkdsk <Drive_Letter:> /f and it fixed the errors without me copying the files to PC.
Hope this helps.
Click to expand...
Click to collapse
Please add this simple info to the OP!
P.S.
Windows 7 said the volume is in use and if I wanted to dismount it before it would allow to continue checking/fixing it. But at the end it worked perfectly!
Thank you very much! I had so much stuff on this card that I haven't backed up yet..phew
Thank you for this guide. Help me get all my data of my "Damaged" 64GB sdxc card
I have the same issue. Flashed CM10 M2 on my tmobile S3, got the error that SD card is damaged, restored stock image from backup, and I'm still getting the bad SD card error. I'm using CWM 6.0.1.2 and mounting the external SD failed. I don't see the contents when I connect through ADB. Mounting sdcard from CWM mounts /sdcard but that is the internal storage which is not what I want. I also tried connecting the card to my laptop running XP using a micro-SD card reader and running chkdsk but that reported the disk as a RAW partition. Any ideas on what else I can do to copy files off of the card?
The method mentioned in OP worked for me, using a macbook air with mountain lion and android sdk for adb installed.
After mounting the external sdcard in cwm and copying the files via adb I partitioned the sdcard (sandisk 64gb sdhx) with the inbuild harddiskmanager in mountain lion. You have to choose FAT (MS-DOS), it will choose fat32 automatically. After partitioning and formating the sdcard the card is recognized under cm10 and samsung firmwares.
OSX has no 32gb limit on fat32.
Hi there,
I made a thread here, I bricked my nook because I erased important files without making a backup before.
Someone here in the forums told me to ask for a "nand dump", what is that I'm not too sure but I guess that he meant that I would need the same files that I erased but from someone else and then I should erase some personal data to avoid B&N store account conflicts.
Anyways, I haven't found any dump neither any directions to put it on my nook glow. Does anyone know where could I get such a thing?
vdguzman said:
Hi there,
I made a thread here, I bricked my nook because I erased important files without making a backup before.
Someone here in the forums told me to ask for a "nand dump", what is that I'm not too sure but I guess that he meant that I would need the same files that I erased but from someone else and then I should erase some personal data to avoid B&N store account conflicts.
Anyways, I haven't found any dump neither any directions to put it on my nook glow. Does anyone know where could I get such a thing?
Click to expand...
Click to collapse
I'm stuck like you with a bricked glo-nook, and I haven't heard about that "nand dump".
Could you post again if you learn anything about it?
TIA
If you put noogie on an SD card and boot it it will serve the internal SD card (NAND) over USB.
There should be 7 visible partitions, only the first will get a drive letter in Windows.
Run Win32DiskImager and save that drive letter to a file.
Make sure that the saved result is about 1,9xx,xxx,xxx bytes.
Renate NST said:
If you put noogie on an SD card and boot it it will serve the internal SD card (NAND) over USB.
There should be 7 visible partitions, only the first will get a drive letter in Windows.
Run Win32DiskImager and save that drive letter to a file.
Make sure that the saved result is about 1,9xx,xxx,xxx bytes.
Click to expand...
Click to collapse
mmmm, in my case I just see a drive letter in W7 and it's the noogie sdcard. No other partitions, Win32DiskImager can't see other partitions either.
But under the portable devices in device administration I can see two devices: boot (drive F:, the noogie sdcard) and G: (can't access)
Thanks for the info.
It sounds like you mashed the partition table on internal SD card.
See this thread about CWR, ADB and fdisk: http://forum.xda-developers.com/showthread.php?t=1805936
Renate NST said:
If you put noogie on an SD card and boot it it will serve the internal SD card (NAND) over USB.
There should be 7 visible partitions, only the first will get a drive letter in Windows.
Run Win32DiskImager and save that drive letter to a file.
Make sure that the saved result is about 1,9xx,xxx,xxx bytes.
Click to expand...
Click to collapse
I don't think I quite understand. If I run Noogie on my SD card then it will boot normally? No matter if I did what I did (erased important files, that's why it's bricked)?
Noogie on an SD card will boot even with the internal SD card vaporized.
This will give you the "Root Forever" screen and serve (whatever exists of) your internal SD card over USB.
Clockwork Recovery on an SD card will boot even with the internal SD card vaporized.
It can perform lots of operation from a menu on the screen.
It can also provide ADB over USB which is helpful for cleaning up stuff.
Renate NST said:
Noogie on an SD card will boot even with the internal SD card vaporized.
This will give you the "Root Forever" screen and serve (whatever exists of) your internal SD card over USB.
Clockwork Recovery on an SD card will boot even with the internal SD card vaporized.
It can perform lots of operation from a menu on the screen.
It can also provide ADB over USB which is helpful for cleaning up stuff.
Click to expand...
Click to collapse
Alright I will try booting up with Noogie. Thanks for your answers, I just hope I can fix this device.
Thanks again.
vdguzman please keep me posted about any progress....I'm in the same situation.
BTW I've opened another thread here to keep track of everything
http://forum.xda-developers.com/showthread.php?p=29597949
thanks
Renate NST said:
Noogie on an SD card will boot even with the internal SD card vaporized.
This will give you the "Root Forever" screen and serve (whatever exists of) your internal SD card over USB.
Clockwork Recovery on an SD card will boot even with the internal SD card vaporized.
It can perform lots of operation from a menu on the screen.
It can also provide ADB over USB which is helpful for cleaning up stuff.
Click to expand...
Click to collapse
Noogie works, I tried to backup the image but I only did that AFTER my Nook had the problem so backing up with Noogie won't do it.
Glownooter WORKS but I don't know what to do to boot it normally. With Noogie I'm stuck on Rooted Forever and while Windows recognizes the nook, it's empty, completely empty.
I don't know what's ADB.
vdguzman said:
I don't know what's ADB.
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
http://forum.xda-developers.com/wiki/Android_Debug_Bridge
Renate NST said:
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
http://forum.xda-developers.com/wiki/Android_Debug_Bridge
Click to expand...
Click to collapse
Thanks for clearing that up
But what I'm trying to know is what kind of method will bring my Nook back to life, I'm no expert but I can manage if I'm told at least what will theoretically work.
I installed CM7 on a 16GB SD card for my Nook Color about a year ago and it has been working fine since then with no problems. I've been doing regular image backups of the SD card using Win32DiskImager. I recently had problems with an app update so decided to try and do an image restore of a recent backup. I get error messages from Win32DiskImager that there's not enough room on the SD card. I've tried reformatting/repartitioning the SD card using various tools (Windows format, Nook SD card format, EaseUS, SDFormatter, etc.) but haven't been able to get the full disk space back. The message I get from Win32DiskImager is: " Not enough space on disk: Size 30390270 sectors, available 30248960 sectors." This was the original SD card that had the CM image on it. Any ideas? Thanks!
zinger14 said:
I installed CM7 on a 16GB SD card for my Nook Color about a year ago and it has been working fine since then with no problems. I've been doing regular image backups of the SD card using Win32DiskImager. I recently had problems with an app update so decided to try and do an image restore of a recent backup. I get error messages from Win32DiskImager that there's not enough room on the SD card. I've tried reformatting/repartitioning the SD card using various tools (Windows format, Nook SD card format, EaseUS, SDFormatter, etc.) but haven't been able to get the full disk space back. The message I get from Win32DiskImager is: " Not enough space on disk: Size 30390270 sectors, available 30248960 sectors." This was the original SD card that had the CM image on it. Any ideas? Thanks!
Click to expand...
Click to collapse
Try burning the SD image file again and before rebooting, try doing the restore.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Try burning the SD image file again and before rebooting, try doing the restore.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks but I think I've figured out what the problem is. I have two 16gb sd cards but each is from a different vendor. Apparently each card has a slightly different storage capacity (~70M) so the image created from the card with the larger capacity won't fit on the sd card with the lower capacity. Does anyone know if there is a safe way to shrink the partition size on the sd card that currently has CM7 installed without losing the data? I could easily get by with 4gb instead of the current 16gb. I'd like to be able to use both sd cards using the same image.
Use minitools partition manager and shrink partition 4... as long as there's enough free space... nothing is lost.
DizzyDen said:
Use minitools partition manager and shrink partition 4... as long as there's enough free space... nothing is lost.
Click to expand...
Click to collapse
I was able to change the size of partition 4 but it just move it to unallocated space and kept the total memory of the sd card the same. Sounds like I would need to reformat the sd card to change the overall size.
I ended up using an imaging program called usbit. It has an option when restoring an image to truncate oversize images. It does warn that there is a chance of data loss when doing this but I tried it and it seemed to work without any problems. I was able to restore the images that I had created with Win32DiskImager with this tool. Another good feature with this tool is that it can also compresses the image files that are created with it.