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.
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.
I'm having the same problem How did you delete the fsck_msdos from the bin?
theinstagator said:
I'm having the same problem How did you delete the fsck_msdos from the bin?
Click to expand...
Click to collapse
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
I was having this same issue..it would typically take up to 5 minutes or more to "check for errors" after a boot.
To fix this I backed up my sdcard, reformatted, copied everything back, then reflashed. Everything was fine after that.
i have somewhat the same problem but in my case it sometimes say blank sdcard or damged sd card it read fine when plugged into an sd card reader any help
Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.
hmaxos said:
Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.
Click to expand...
Click to collapse
Well, after getting other errors such as "no enough space" from Platinum Backup (there was a space on SD Card), I had to go to Format the SD after copying everything. Then I copied back the important folder the SD. I also had to reinstall SwiftKey. Now everything is fine and no data loss.
SD card Checking for errors
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Well I will try to backup and format it.... If it works then good if not then I will have to root my LG P880 .
My Problem is "preparing external sd card checking for errors" now that error is not showing while following above steps but now when i click my memory card that is not opening and after opened my memory card my internal device memory also not opening .
baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
Simple fix, Difficult decision. Remove SD Card from slot then Factory reset phone. Once it comes too just go through all steps to setting up device then reinsert the SD Card into the slot. BOOM!
thank you very very much it worked for me
baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
thank you so much but it is read only please help
yeah...
supremeteam256 said:
Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.
Click to expand...
Click to collapse
i am having same issue i always changes roms please can you halp me..
still not working mine is lenovo K3 Note And my Phone is rooted. It is showing Preparing SD card checking for errors
Didn't work for me.
Hard reset don't work.
Delete the fsck.msdos but don't work.
The fsck.msdos file comes on every wipe back.
I think this is a cm issue.
On stock no problems with my external sd card on my HTC One M8.
I'm going crazy...
No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,
Anitha Sivakumar said:
No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,
Click to expand...
Click to collapse
ive deleted the fcsk file on bin
the notif "preparing sd card" was gone but another problem occured, i cant even open my storage, ext sd card and even internal card ive tried your solution, ive put my sd card on another device, i cant find any fcsk files that you mention i cant even delete any file from my card using another mobile :crying::crying::crying:
It worked.... Thanks bro..
:good:
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Bloody Brilliant. I have no idea why I could not find this solution two years ago. I have spent several hours searching for this solution, several times. In my case, I needed to remove the fsck.exfat file in the /system/bin folder.
My attention span is extremely short. I have been living with a 3 to 4-minute card scan for a 256GB microSD in my Samsung Note 3 for two and a half years. For all of the reboots I have done (which must be near a thousand, if that's not severely underestimated) I have had to deal with waiting to use my phone. I can't tell you how discouraging it has been to have such a powerful, useful device crippled by such a stupid flaw: that of checking the SD card that you rarely remove, for errors, every single time the phone is rebooted, even after graceful reboots called by the "proper" methods.
I can't tell you how many times I have rebooted my phone, only to forget the reason I rebooted it, because my phone took 4 minutes to reboot.
Productivity to the cubed-root.Pisses me off.
Someone who has more voice than me please get the Android People to change this. As of Nougat, this is still the default behavior. How can an organization be so stupid...? I have no doubt that just this flaw has sent many people to the Apple camps. Who the cuff in their right mind would want to deal with such a hassle?? Are they seriously unaware of the trend for people to actually believe that their devices, machines and technology ought to be doing things faster than previous generations?
(Please just take the following cynicism with a grain of salt. I just learned the above fix, something I really should have figured out a long time ago/kicking myself!!) :crying:
For the anally-inverted who might bring up the obvious argument that your phone will no longer be able to detect or fix corruption, all that needs to be done is the following:
1) move the fsck.exfat (or whatever the formatting) file to a different folder. In my case I moved it to the /data folder
2) use some delay scripting program that will symlink the fsck.exfat file to a tmpfs location say, 30 seconds after boot; or longer if needed. This intermediary step is necessary in order to create a temporary symlink, which will be nonexistent upon reboot.. If we didn't create a temporary symlink, the fsck.exfat command would be immediately available after each reboot (which we don't want) because symlinks are normally permanent. Therefore, this step will need to be run after every reboot (but again, time-delayed).
3) the last command is to create another symlink, linking the tmpfs fsck.exfat symlink created in the last step back to the /system/bin folder (or wherever it originally resided). So this is a symlink of another symlink. This step actually should only need to be done once, since this symlink should remain after reboot, even though it is initially broken upon reboot until the previous command recreates the intermediary symlink. It should become effective again when the previous step is run by the time-delayed scripting program.
Now your phone has the ability to check the card upon you calling the fsck.exfat routine through normal means, one of which can just be a simple unmount -> mount request from the Android system settings . Your card won't be needlessly fsck-checked to death every bloody time you reboot your phone.
(If you found this tutorial helpful and desire to quote or improve upon it, please cite/credit me for the inspiration! It came through much effort and learning!)
I have a problem and found this unanswered question in the internet:
Hello,
so I have a rather big problem here. My internal SD-card on my I9000 does not accept any changes(delete/write/move).
The funny thing is that I can actually copy files to my sd and delete files. I can even format it(from recovery mode, windows, menu) whatever I do seems to work till I reboot. After every reboot my system is back to the state before I changed anything.
I tried everyway I could think of. Changing permissins via adb shell, installing file system fixes via adb push(to my surprise it did allow me to copy files directly into /system as long as I did it while in recovery mode).
I even tried several different firmwares. No matter what I do it's the same, no changes are permanent. As soon as I reboot every change is gone.
This feels like working with oracle and forgetting to commit.
Is there a way to format the sd card via adb shell? Preferably a low level format(since the quick format doesn't seem to do anything). Or some sort of forced flush for the sd card? Some way to just clear my internal sd should do the trick.
Every solution I found on the internet didn't work.
What does work is the download mode, the recovery mode and adb.
I sure hope someone has an idea. It's rather unpleasent being unable to change anything on the internal sd.
My problem is exactly the one stated above, and I have tried pretty much everything I found in the internet, including running Ubuntu live cd and format/partition/etc, but the problem persists.
I need one of 3 possibilities:
1 - Someone tell me what is wrong and how to fix
2 - Since Internal SD is unchangeable, would like to know how to make /data and /sdcard to be mounted on external sd at boot time (probably some changes at firmware or kernel).
3 - Someone tell me that it is broken and cannot be repaired by software, must be hardware serviced.
Really thanks in advance
Same problem!
i do have the EXACT same Problem!!!! Any solution jet?
Got a similar problem with my Galaxy Tab... Anyone found a solution yet?
friend of mine has a htc and uses a program called superwipe
http://forum.xda-developers.com/showthread.php?t=834812
dont know if it will work on the galaxy s though, but coukd be worth a read through the notes and posts
Wow . I have a similar problem. Although EVEN more troublesome.
Inaddition to all this
I cannot even DELETE the alarms taht i set before having this problem. I cannot Install the apps as well.
Uninstalling the ones - and they reappear the next time I boot.
Need Serious HELP on this.
My phone is restricted to ONLY making calls and sms. Thats all.
I have the *EXACT* same issue here. Only with a Sprint Galaxy Tab. My reboot is fresh and gives me "nothing" every time I boot no matter how much I configure. I can't write anything to the internal SD card or make any new folders.
jrhsu529 said:
I have the *EXACT* same issue here. Only with a Sprint Galaxy Tab. My reboot is fresh and gives me "nothing" every time I boot no matter how much I configure. I can't write anything to the internal SD card or make any new folders.
Click to expand...
Click to collapse
I have a different problem. My internal sd seems slow. Anyway, I must feel lucky.
If you look at page 15 of the following datasheet, you will notice that the moviNAND can be set in a "write-protect" mode:
http://web3032.sh1.magic2008.cn.m1.magic2008.cn/uFile/3032/201144131545503.pdf
See if you can read the CSD register data on your phone, and mingle with it.
Good luck.
Any one fix this
Any one fix this I have the same problem
Yesterday I gave the soluction, but someone deleted my post.
EDIT!!
Sorry, I wrong topic!!!! Sorry!!!!
superandroid2011 said:
I have a problem and found this unanswered question in the internet:
Hello,
so I have a rather big problem here. My internal SD-card on my I9000 does not accept any changes(delete/write/move).
The funny thing is that I can actually copy files to my sd and delete files. I can even format it(from recovery mode, windows, menu) whatever I do seems to work till I reboot. After every reboot my system is back to the state before I changed anything.
I tried everyway I could think of. Changing permissins via adb shell, installing file system fixes via adb push(to my surprise it did allow me to copy files directly into /system as long as I did it while in recovery mode).
I even tried several different firmwares. No matter what I do it's the same, no changes are permanent. As soon as I reboot every change is gone.
This feels like working with oracle and forgetting to commit.
Is there a way to format the sd card via adb shell? Preferably a low level format(since the quick format doesn't seem to do anything). Or some sort of forced flush for the sd card? Some way to just clear my internal sd should do the trick.
Every solution I found on the internet didn't work.
What does work is the download mode, the recovery mode and adb.
I sure hope someone has an idea. It's rather unpleasent being unable to change anything on the internal sd.
My problem is exactly the one stated above, and I have tried pretty much everything I found in the internet, including running Ubuntu live cd and format/partition/etc, but the problem persists.
I need one of 3 possibilities:
1 - Someone tell me what is wrong and how to fix
2 - Since Internal SD is unchangeable, would like to know how to make /data and /sdcard to be mounted on external sd at boot time (probably some changes at firmware or kernel).
3 - Someone tell me that it is broken and cannot be repaired by software, must be hardware serviced.
Really thanks in advance
Click to expand...
Click to collapse
Looks like my problem as well
http://forum.xda-developers.com/showthread.php?t=2155644
To test quick go development->>launch tools->>bad behavior->>crash the system server.
Your device will reboot and you will have both in/ext sdcard (if its the same prob).
damgood said:
Looks like my problem as well
http://forum.xda-developers.com/showthread.php?t=2155644
To test quick go development->>launch tools->>bad behavior->>crash the system server.
Your device will reboot and you will have both in/ext sdcard (if its the same prob).
Click to expand...
Click to collapse
I have the same problem, cannot even use the phone as it FC any apps after boot. And no changes possible to the sdcard.
Have you found a solution yet?
DerBusisVoll said:
I have the same problem, cannot even use the phone as it FC any apps after boot. And no changes possible to the sdcard.
Have you found a solution yet?
Click to expand...
Click to collapse
Sorry - no - I had to start from scratch, my thougt was too many files on the ext card But I not sure and cannot recall - My phone is working good now. Only advice is to reinstall from scratch
I am also facing the same problem on my galaxy nexus after upgrading to KK using custom ROM. Any solution?
Does anybosy able to doanload the superwipe?
superandroid2011 said:
I have a problem and found this unanswered question in the internet:
Hello,
so I have a rather big problem here. My internal SD-card on my I9000 does not accept any changes(delete/write/move).
The funny thing is that I can actually copy files to my sd and delete files. I can even format it(from recovery mode, windows, menu) whatever I do seems to work till I reboot. After every reboot my system is back to the state before I changed anything.
I tried everyway I could think of. Changing permissins via adb shell, installing file system fixes via adb push(to my surprise it did allow me to copy files directly into /system as long as I did it while in recovery mode).
I even tried several different firmwares. No matter what I do it's the same, no changes are permanent. As soon as I reboot every change is gone.
This feels like working with oracle and forgetting to commit.
Is there a way to format the sd card via adb shell? Preferably a low level format(since the quick format doesn't seem to do anything). Or some sort of forced flush for the sd card? Some way to just clear my internal sd should do the trick.
Every solution I found on the internet didn't work.
What does work is the download mode, the recovery mode and adb.
I sure hope someone has an idea. It's rather unpleasent being unable to change anything on the internal sd.
My problem is exactly the one stated above, and I have tried pretty much everything I found in the internet, including running Ubuntu live cd and format/partition/etc, but the problem persists.
I need one of 3 possibilities:
1 - Someone tell me what is wrong and how to fix
2 - Since Internal SD is unchangeable, would like to know how to make /data and /sdcard to be mounted on external sd at boot time (probably some changes at firmware or kernel).
3 - Someone tell me that it is broken and cannot be repaired by software, must be hardware serviced.
Really thanks in advance
Click to expand...
Click to collapse
Galaxy Tab 2 running on blisspop rom
I have to reboot every time this happens. The error message in mx player shows cannot write to internal sd..
Es xplorer cannot delete any item. Terminal emulator shows mount as read only
Any way to fix this?
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!
Hi All,
I have just rooted my One.
I backed up the entire SD Card and I have copied some things back (DCIM, Downloads, My music (apart from my Play store offline files).
I cannot locate many of the images I took with the phone prior to root. I can also not for the life of me figure out why so much space is consumed on my memory considering what I have on the device.
Regardless, I didnt know if there was some secret hiding place that things go to hide.
I had many of these photo's in their own folders within the Gallery, these are also unavailable.
I have since backed up my photo's to DropBox, and they all appear in there, so I am looking to sync my PC with my dropbox tonight then copy the photo's I want back to the phone, but firstly I need to know these files arent still hiding on my "sd card" before I go and further duplicate them.
Is there anyone out there who has gone through the same thing and has some pointers as to what to look for as I find the file structure within ES File Manager quite confusing with SD and 0/ with emulated partition that seems to be a dupliucate of SD Card etc etc.
Sorry, very noob question, however I have been rooting phones for ages, my last being the HTC OneXL and everything seemed to make so much more sense on that phone.
Any advice would be greatly greatly appreciated.
Thanks for any help in advance.
Scott
Yes, the SD and 0/ folder is a duplication of your storage, so do not need that folder. You can delete any other stuff inside the media folder, though. If everything is already stored on your computer, how about you format the SD card and use adb to sideload a ROM? In other words, a clean, fresh install.