Database Info

modified: Installing & Run application on sdcard

WARNING: Proceed at your own risk, this may damage your phone and/or make it unstable. This is for advanced users only and should only be attempted by those who understand the risks of the following changes
Original post: http://www.androidin.net/thread-1099-1-1.html
AS usual, this is for those WITH ROOT ONLY
Preparation:
1. Installed JF RC30 V1.2 (only if you are using JF RC30 1.2 , this is not compatible with RC8)
2. Make a NANDROID backup (you may get everything back to normal if the phone screw up)
3. A MICRO-SD card with 2 partitions divided : (1) a fat-32 partition, (2) a ext2, you need a linux/mac to format the sdcard with ext2 partition
* the fat 32 will be mounted as sdcard and the ext2 will be mounted as /sd for application data, make your own decision for the size*
4. insert the sdcard with 2 partition on the phone
5. set the phone to aeroplane mode for safe
Procedure:
1. adb pull /system/etc/mountd.conf /*somewhere you may want to back it up*
2. rm -f /system/etc/mountd.conf
3. using the modified mountd.conf, adb push /*the path of modified mount.conf */mount.conf /system/etc/mountd.conf
4. adb pull /system/init.rc /*somewhere you may want to back it up*
5. rm -f /system/init.rc
6. using the modified init.rc, adb push /*the path of modified init.rc*/init.rc /system/init.rc
7. reboot
8. busybox cp -a /data/app /sd/
9. rm -r /data/app
10. ln -s /sd/app /data/app
11. reboot
Now, the phone will install and run everyone on /sd, still mounting /sdcard as usual. It is possible that to mount or unmount /sdcard by usb without everything screwed up. Beware that your sdcard will be used as part of system, removing the sdcard may freeze the phone. If the phone get freeze because of removing the sdcard, plug the sdcard again and soft reset.
It is also possible that copy the application data to another card. If you want to change the sdcard, switch the phone off, mounting the sdcard to computer directory, copy the /sd partition to another sdcard with ext2 partition
Back to normal:
1. rm -f /system/etc/mountd.conf
2. adb push /*the backup of mountd.conf* /system/etc/mountd.conf
3. rm -f /system/init.rc
4. adb push /*the backup of init.rc* /system/init.rc
5. busybox cp -a /sd/ /data/app
6. rm -r /sd/
Change of mountd.conf:
changing /dev/block/mmcblk0 to /dev/block/mmcblk0p1
change of init.rc:
adding
insmod /system/modules/2.6.25-01843-gfea26b0/kernel/fs/ext2/ext2.ko
mknod /dev/mmcblk0p2 b 179 2 1000
mount ext2 /dev/mmcblk0p2 /sd noatime nodiratime

Any chance of this being simplified into the actual commands necessary for this!?
I'm a semi-noob at *nix stuff... I can format my SD card into 2 partitions, but I'm lost at step 4... What do we need to edit??

Changed step 4...just adb pull the mount.conf for editing..open the file in text editor..find "mmcblk0" and change it "mmcblk0p1" ..save the .conf...del the original one..push the new one to the original directory..

Yay. Now hopefully we can get this in an update.zip to flash

Yeah, I'm putting off doing this until someone makes an update.zip which I definitely know how to apply and get rid of if I screw anything up

REPLACES the internal memory...?
So the internal memory isnt used?
kinda the same trick as the browser cache and market cache, just a bit more complex as its an entire filesystem your moving, which wouldnt let the sys see the internal, mem, please correct me if im reading it wrong, Im not a total noob at linux but no guru dev either...
bhang

The internal memory is still used, just not for /data/app
19.rm -r /data/app
20.ln -s /sd/app /data/app
Click to expand...
Click to collapse
It should probably be /sdcard/app. In any case, this is a fairly complex mod that is not suited for Linux newbies. I would advise against folks considering this mod unless they understand and can test each step before attempting.

I agree and added a warning to the first post

Ummm yea, so what happens when you mount your sdcard for storage? I expect the phone goes crazy?
This tutorial, if you could call it that,(no offense) is really badly written and this process seems too risky for what you gain considering that if we are patient google will come out with this themselves.
Stericson

Stericson said:
Ummm yea, so what happens when you mount your sdcard for storage? I expect the phone goes crazy?
This tutorial, if you could call it that,(no offense) is really badly written and this process seems too risky for what you gain considering that if we are patient google will come out with this themselves.
Stericson
Click to expand...
Click to collapse
The procedure calls for two partitions on the microsd, one FAT32, other EXT. Theoretically it should work with mounting for mass storage. However, I agree that it's a rather sloppy hack.
There is talk about a similar strategy being officially implemented by the Android team. Instead of two partitions, it would be loopback mounted to a file in the FAT32. That would also provide some encryption security. See here. It's just talk though. Won't be a reality for at least a few months.

Well talk is certainly better than nothing...thanks for the info....
Stericson

I post a method withtout compiling the ramdisk.img but that do not force mounting the sd ext2 drive under rootfs but still workable...probably when i back to work I can compile 1 to flash

Am I the only one that thinks there are a few things that are getting 'lost in translation' here?
I'm not getting /sd mounted properly upon reboot...there's no way I'm going to continue attempting this till I see a better (no offense) tutorial or do a little more research on the command lines.
I would really shy away from this if you're an average user or don't know what mountd and init.rc files are used for....this could flat out wreck your phone.

TheDudeOfLife said:
Am I the only one that thinks there are a few things that are getting 'lost in translation' here?
I'm not getting /sd mounted properly upon reboot...there's no way I'm going to continue attempting this till I see a better (no offense) tutorial or do a little more research on the command lines.
I would really shy away from this if you're an average user or don't know what mountd and init.rc files are used for....this could flat out wreck your phone.
Click to expand...
Click to collapse
/sd is /sdcard (mount point for the micro sd card's partition)

I'm getting stuck right here:
8. busybox cp -a /data/app /sd/
9. rm -r /data/app
10. ln -s /sd/app /data/app
11. reboot
It's saying read only system blah blah, even though I have indeed mounted it is rw

pershoot said:
/sd is /sdcard (mount point for the micro sd card's partition)
Click to expand...
Click to collapse
No....no it is not.
/sd is a mount of the ext2 partition used for the 'copy' of /data/app (one of the things i disagreed with is picking /sd as a mount point for the second partition.)
/sdcard is the fat32 mount point...used as usual for mounting files.

IzzeLing said:
I'm getting stuck right here:
8. busybox cp -a /data/app /sd/
9. rm -r /data/app
10. ln -s /sd/app /data/app
11. reboot
It's saying read only system blah blah, even though I have indeed mounted it is rw
Click to expand...
Click to collapse
Type mount in adb shell and see if /sd is even mounted. I wasn't seeing it in my list. I don't think his mount command in the init.rc is correct, but I'm too busy with holiday stuff.
Don't rm -r /data/app if you have not 100% verified the copy works.

This line looks mangled (need flags in the args):
Edit: nevermind, looks like it should work in the init.rc

TheDudeOfLife said:
No....no it is not.
/sd is a mount of the ext2 partition used for the 'copy' of /data/app (one of the things i disagreed with is picking /sd as a mount point for the second partition.)
/sdcard is the fat32 mount point...used as usual for mounting files.
Click to expand...
Click to collapse
ahh yea. i just re-glanced over the instructions.
cool.

TheDudeOfLife said:
Type mount in adb shell and see if /sd is even mounted. I wasn't seeing it in my list. I don't think his mount command in the init.rc is correct, but I'm too busy with holiday stuff.
Don't rm -r /data/app if you have not 100% verified the copy works.
Click to expand...
Click to collapse
Yeah, don't see it. Hm.

How to swap SD cards w/ Apps2SD

All props go to Jonnythan who gave the steps in another post. Mods may want to sticky this....
1. As always: Nandroid backup
2. reboot phone
3. adb shell into the phone
4. mkdir /sdcard/backup/
mkdir /sdcard/backup/app
mkdir /sdcard/backup/app-private
cp -r /data/app/* /sdcard/backup/app/
cp -r /data/app-private/* /sdcard/backup/app-private/
5. copy sd card to pc
6. Shut off phone and remove old sdcard and insert new sdcard
7. Start in recovery mode and partition new sdcard (fat32, ext2, swap)
8. Enable usb mode, copy data from old sdcard to newly partitioned sdcard
9. reboot and ignore force closings
10. Plug in USB and enable USB mode
From PC ADB shell into phone and type the following (enter after each line):
rm -r /data/app/*
rm -r /data/app-private/*
[chances are those directories are empty already, but you never know]
cp -r /sdcard/backup/app/* /data/app/
cp -r /sdcard/backup/app-private/* /data/app-private
reboot recovery
11. Restore most recent nandroid
12. reboot and enjoy
All thanks again to Jonnythan

Tweaks:
Between 5 and 6, shut off phone. Then start step 7 by specifying to start into recovery mode to partition the card. Then specify that you need to plug in the usb and adb shell for step 10. End step 10 by typing in "reboot recovery" which will reboot you right into the recovery partition.
Thanks for writing it up! Now I don't have to

Ok, I must be doing something wrong here... Does this require a custom ROM or anything? Im on the sprint Hero, stock ROM and I do have root. Everytime I get to step 4, at the cp -r /data/app/* /sdcard/backup/app/ command i get an error. It cant find the directory. Also, if i check the folder properties through Astro or linda file manager, it says 0 files, 0 folders, and also shows that it is not taking up any space. Just as a test to see if I was somehow blocked, I made a nandroid backup and deleted the /data folder, and upon reboot nothing had changed. Still have all of my apps on the phone...

I think the stock ROM doesn't include the cp command.

jonnythan said:
I think the stock ROM doesn't include the cp command.
Click to expand...
Click to collapse
Wait, when i get my sd card I have to do all this? I can't just reformat using the utility and drag and drop everything back into the sd card?

runsoverfrogs said:
Wait, when i get my sd card I have to do all this? I can't just reformat using the utility and drag and drop everything back into the sd card?
Click to expand...
Click to collapse
Not if you're using AppsToSD.
If you're not using A2SD then just make a backup of the old card, unmount it, put the new one in, and copy everything back. If you are using A2SD, the process is more complex.

Cp = Copy. Works on any rom. Like he said since you're on the stock rom, I doubt you're using Apps2SD so no you don't have to do all this.

If only people would actually read the thread title....
"How to swap SD cards w/ Apps2SD."
Don't have Apps2SD? Then this isn't the thread for you.

Exactly what I was thinking.

jonnythan said:
If only people would actually read the thread title....
"How to swap SD cards w/ Apps2SD."
Don't have Apps2SD? Then this isn't the thread for you.
Click to expand...
Click to collapse
I'm using the modaco 1.1, i should've mentioned that. Doesnt that come with Apps2SD built in?

Only if you partitioned your sd card before you flashed.

After step 6, how do you boot into recovery mode to partition the new card if you dont have the recovery image on the new card? Did I miss a step where I added the recovery image to the new card?

chalan30 said:
After step 6, how do you boot into recovery mode to partition the new card if you dont have the recovery image on the new card? Did I miss a step where I added the recovery image to the new card?
Click to expand...
Click to collapse
The recovery partition is installed on the phone itself, not the card.

thanks I dont know why the first time I tried i didn't get back into the recovery screen but the second time I booted into it just fine... oh well thanks for all your hard work!!!

Partitioning links
To partition the new card, you might want to include links to sdparted and this page for people who want to do it manually.

I have a question about how to make the swap. I have moved /data/dalvik-cache/ to my sd card and freed up about 25 meg of space on internal memory. Is there anything I need to do in addition to your instructions or would it be better to just do a wipe and start from scratch. I am using MoCaDo 1.2 Rom using apps2sd and ext3 partition. I have a 16 gig card coming. By moving the cache I now have 143 meg of internal memory with about 65 apps installed counting some of the stock apps. I have removed several of those as well. 34 apps from the market or handmark.

esoteric1311 said:
All props go to Jonnythan who gave the steps in another post. Mods may want to sticky this....
1. As always: Nandroid backup
2. reboot phone
3. adb shell into the phone
4. mkdir /sdcard/backup/
mkdir /sdcard/backup/app
mkdir /sdcard/backup/app-private
cp -r /data/app/* /sdcard/backup/app/
cp -r /data/app-private/* /sdcard/backup/app-private/
5. copy sd card to pc
6. Shut off phone and remove old sdcard and insert new sdcard
7. Start in recovery mode and partition new sdcard (fat32, ext2, swap)
8. Enable usb mode, copy data from old sdcard to newly partitioned sdcard
9. reboot and ignore force closings
10. Plug in USB and enable USB mode
From PC ADB shell into phone and type the following (enter after each line):
rm -r /data/app/*
rm -r /data/app-private/*
[chances are those directories are empty already, but you never know]
cp -r /sdcard/backup/app/* /data/app/
cp -r /sdcard/backup/app-private/* /data/app-private
reboot recovery
11. Restore most recent nandroid
12. reboot and enjoy
All thanks again to Jonnythan
Click to expand...
Click to collapse
I see some possible problems with this method... what happens if you're copying the sdcard onto a windows machine to backup? You'll lose symlinks, uid, and the like.
Also, what if /app and /app-private don't get put back onto the new sdcard? You'll end up with symlinks that point to nothing.
How 'bout this method? (just a little tweak).
Boot into recover (adb shell reboot recovery)
when recovery comes up, go to the shell (adb shell)
Then, issue these commands (this assumes your ext partition is ext3, and that you're using Amon-Ra's recovery so you have BusyBox 1.13.2 or later):
mkdir /sdcard/extback
mount -o ro -t ext3 /dev/block/mmcblk0p2 /system/sd
cp -a /system/sd/. /sdcard/extback/
Now, back up the sdcard to a linux machine... keeping uid's and everything the same.
Turn the phone off, swap the cards, reboot into recovery (manually), format, partition, and convert ext2->ext3 the sdcard, put all the stuff back onto the card... and in the shell (within recovery
mount -o rw -t ext3 /dev/block/mmcblk0p2 /system/sd
cp -a /sdcard/extback/. /system/sd/
reboot
Now, it should all come up with the same attributes, no force close, and everything...
Basically, this method would swap sd cards outside of the normal OS (in recovery), but would keep all the attributes, symlinks, and uids the same for the main OS.
I think if you're using a windows box to backup the card, then we may want to look into making a tarball of the ext partition. I'm not sure if Amon-Ra's recovery supports this or not.

jmanley69 said:
I see some possible problems with this method... what happens if you're copying the sdcard onto a windows machine to backup? You'll lose symlinks, uid, and the like.
Also, what if /app and /app-private don't get put back onto the new sdcard? You'll end up with symlinks that point to nothing.
How 'bout this method? (just a little tweak).
Boot into recover (adb shell reboot recovery)
when recovery comes up, go to the shell (adb shell)
Then, issue these commands (this assumes your ext partition is ext3, and that you're using Amon-Ra's recovery so you have BusyBox 1.13.2 or later):
mkdir /sdcard/extback
mount -o ro -t ext3 /dev/block/mmcblk0p2 /system/sd
cp -a /system/sd/. /sdcard/extback/
Now, back up the sdcard to a linux machine... keeping uid's and everything the same.
Turn the phone off, swap the cards, reboot into recovery (manually), format, partition, and convert ext2->ext3 the sdcard, put all the stuff back onto the card... and in the shell (within recovery
mount -o rw -t ext3 /dev/block/mmcblk0p2 /system/sd
cp -a /sdcard/extback/. /system/sd/
reboot
Now, it should all come up with the same attributes, no force close, and everything...
Basically, this method would swap sd cards outside of the normal OS (in recovery), but would keep all the attributes, symlinks, and uids the same for the main OS.
I think if you're using a windows box to backup the card, then we may want to look into making a tarball of the ext partition. I'm not sure if Amon-Ra's recovery supports this or not.
Click to expand...
Click to collapse
Now I'm confused don't take much.
I tried reading the ext2 partition using ubuntu and loading it temp on my windows 7 PC. It would not let me open that partition so I could not copy anything to it.
I guess the easiest way is to just wipe the phone back to factory, booting to recovery with the new card in and create the fat32-ext2-swap partition, re-flash the MoDaCo or any Rom that uses Apps2Sd and install all my apps again. I am assuming this would work as well.

jmanley69 said:
I see some possible problems with this method... what happens if you're copying the sdcard onto a windows machine to backup? You'll lose symlinks, uid, and the like.
Also, what if /app and /app-private don't get put back onto the new sdcard? You'll end up with symlinks that point to nothing.
How 'bout this method? (just a little tweak).
Boot into recover (adb shell reboot recovery)
when recovery comes up, go to the shell (adb shell)
Then, issue these commands (this assumes your ext partition is ext3, and that you're using Amon-Ra's recovery so you have BusyBox 1.13.2 or later):
mkdir /sdcard/extback
mount -o ro -t ext3 /dev/block/mmcblk0p2 /system/sd
cp -a /system/sd/. /sdcard/extback/
Now, back up the sdcard to a linux machine... keeping uid's and everything the same.
Turn the phone off, swap the cards, reboot into recovery (manually), format, partition, and convert ext2->ext3 the sdcard, put all the stuff back onto the card... and in the shell (within recovery
mount -o rw -t ext3 /dev/block/mmcblk0p2 /system/sd
cp -a /sdcard/extback/. /system/sd/
reboot
Now, it should all come up with the same attributes, no force close, and everything...
Basically, this method would swap sd cards outside of the normal OS (in recovery), but would keep all the attributes, symlinks, and uids the same for the main OS.
I think if you're using a windows box to backup the card, then we may want to look into making a tarball of the ext partition. I'm not sure if Amon-Ra's recovery supports this or not.
Click to expand...
Click to collapse
Well, for one thing your method requires a linux machine
But what would you even have symlinks on the SD card for? Symlinks, uids, and attributes on SD card files simply aren't an issue at all for most people.
And truthfully if you are already doing that kind of stuff, you don't need this guide.

jonnythan said:
Well, for one thing your method requires a linux machine
But what would you even have symlinks on the SD card for? Symlinks, uids, and attributes on SD card files simply aren't an issue at all for most people.
And truthfully if you are already doing that kind of stuff, you don't need this guide.
Click to expand...
Click to collapse
As far as Linux... get VMWare player for free and download ubuntu and you're set real fast. Also if you notice what I said about doing a tar instead id using Linux.
As far as symlinks. You're right there "shouldn't" be any... but if you're backing up something why not do it right just in case? We have no idea what future versions of apps2ad sill do. It may happen that a file MUST reside on internal memory and therefore you'd need a symlink.
As far as the rest...
Actualy... each app gets its own user id and mismatches in those can cause problems with some apps. And each file in Linux gets attributes to tell the OS who is allowed ti read/write/execute it. If those get messed up it can cause problems.
So... we have a responsibility aa educators to give the best instructions possible. And not give instructions that ultimately would result in a backup that is missing vital information and would lead to a complete reload to fix the problems.
There are many reasons why Google decided to restrict apps to internal memory and we will never know all of them... this may very well be one of the problems they saw happening.

Clone an SD card (including EXT3) to another?

Like ghosting a HDD to another, I wanted to know if there's an app that can do this?
I think my 8GB LG branded MicroSD is failing as Windows keeps reporting that the drive needs to be scanned when I mount it via USB from my Desire so I'd like to just get a new Sandisk 8GB card and clone the old to new one to avoid having to go through restoring backups and so on.
If anyone has any ideas that would be grand!

check winimage.
That app can make image and recover it to drives!
Doesnt matter if disk is bigger than previous ( NB! may need to resize to get total space if its bigger, cannot remember)
I've always used it for vmware ESXi embedded sticks, made a million of them and the app works!
also linux routers.
Hope this helps.
vmware ESXi runs linux so it supports EXT!

No need for a program, copy data from fat partitions vis pc and use this ( from cyanogen wiki page) Used it three times now and no problems
Upgrading SD / Moving data to new SD
If you are using RA recovery, this is all done for you by making a BART backup. The following is if you're wanting to do it from the command line.
1. First, backup your ext partition on to your fat32 partition. Note, you will need enough free space to hold all of your apps.
* In Terminal Emulator or recovery console:
mount -a [enter]
tar cvf /sdcard/ext.tar /system/sd [enter]
Note that you must have root access for Terminal Emulator. If you get "permission denied" after entering the above command, then try entering the command "su". "sudo" will not work. After entering "su" try the above command again.
* Or, Using ADB shell from your PC:
adb shell
mount -a [enter]
tar cvf /sdcard/ext.tar /system/sd [enter]
2. Next, mount your SD card and download/backup everything on your fat32 partition. Make sure to get the ext.tar file that you just created in the previous step.
3. Change cards/repartion, or do whatever it is you planned to do here. For instructions on creating new partitions see the installation instructions above.
4. If you're not already, reboot into your recovery. Restore your backup files to your fat32 partition. Don't boot into CM yet!
5. Either go to console or ADB shell and type:
*
mount -a [enter]
*
tar xvf /sdcard/ext.tar [enter]
6. Double check that your directories are moved with:
ls /system/sd [enter]
7. Now you can reboot into CM!
8. Run fix permissions to fix any corrupted permissions.
9. Enjoy your new card!

If you have Amon Ra's recovery on your android phone you can do a bart backup with your old sd card, partition the new sd card as required, copy the bart backup to new sd card and then do a bart restore. It is what i did when i upgraded from my 2gb to 8gb, worked a treat.

Since I created this thread a few great things have happened, EXT4 support in unrevoked permanent flashed AmonRA recovery being the main one so now I am sorted thanks!

I use Gparted just copy paste

[Q] Nexus S stop on boot after ICS flash, please help!!

Got a very strange issue with my I9020T
after flashing DrewGaren ICS Beta2 from Koush Alpha11 with ROM Manager my phone stop on boot, no boot animation, just Google logo on black screen, also no access via adb or fastboot at this time.
Can easy enter to bootloader (volume up+ power) and have fastboot access
can reflash recovery (have tried different version of CWM).
Can enter in CWM recovery (now have V5.0.2.0) and have adb access, but seems no superuser access
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # su
su
/sbin/sh: su: not found
~ #
have tried to reflash different roms (have plenty on SDcard) but same issue, flashing seems to be ok, but hang on reboot
Have tried to flash I9020XXJK1- GRH78 via Odin, again flash is ok (it is replacing CWM recovery with stock (but i can reflash CWM recovery vwith fastboot) BUT again stop on boot (Google logo)
have also nand backup (created few month ago) if trying to restore from CWM getting following
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
Error while restoring /data!
Show Log from advanced CWM menu show some issues like
tar: can't make dir data/misc/vpn/profiles: Read-only file system
tar: can't remove old file data/misc/systemkeys/AppsOnSd.sks: Read-only file system
AppsOnSd.sksError while restoring /data!
mtd: successfully wrote block at 0
I: Set boot command '''
any idea?

Have you tried wiping data/cache/dalvik-cache?
BTW, where did you get your CWM? AFAIK, the latest version for Nexus S is 5.0.2.0

sure i did full wipe several times
sorry - my CWM is 5.0.2.0
some strange log issues on data wipe
Formatting /cache
Formatting /sd-ext
Formatting /sdcard/.adndroid_secure...
I: Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete
mtd: successfully wrote block at 0
I: set boot command ""

Hmm... If I were in your situation, I would try to downgrade or use another recovery, may be this one is a good start.
I'd also try flashing the latest OTA package from this thread.

same issue with new CWM
also unable to copy Stock ROM(Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader) to SD card.
from CWM enter to mount and storage
than
mount sd card
mount USB
can see SDCARD on my PC and even can copy ROM to /sdcard/ BUT
if try to install ZIP (can select copied zip) getting
Finding update package
Opening update package
e: can\t open /sdcard/blablabla.zip
(bad)
Installation aborted
after recovery rebout can not find newly copied rom in /sdcard/
It looks like some partition is read only and not flashed properly

It looks like file system problem but dont know how to fix
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
353255F7992E00EC recovery
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Unknown error: 0
C:\Program Files (x86)\Android\android-sdk\platform-tools>

Have you cosidered reflashing ICS? The problem may be the rom you installed?

arielgb2 said:
Have you cosidered reflashing ICS? The problem may be the rom you installed?
Click to expand...
Click to collapse
Before i have used Koush alfa11, but same issue with any ROM (have tried few ICS and GB available on my SD Card). Even flashed Stock Rom with with Odin
results are same - rom flashed (i can see changes on bootloader and baseband version from bootloader menu)
but after reboot - same
Google logo with lock at the bottom, after few sec brightness increased and key backlighted... and nothing

Did you remember to wipe the /system partition when going from GB to ICS?
Greetz

frutelaken said:
Did you remember to wipe the /system partition when going from GB to ICS?
Greetz
Click to expand...
Click to collapse
always wipe data/cache/dalvik/

Yes, good, but if you go from GB to ICS, you need to format the /system partition too.
Can be done in 'mounts and storage'.
Greetz

frutelaken said:
Yes, good, but if you go from GB to ICS, you need to format the /system partition too.
Can be done in 'mounts and storage'.
Greetz
Click to expand...
Click to collapse
you dont have to format anything. a simple wipe data/factory reset works just fine.

You should.
I had got stuck at the Google bootscreen trying to do it without a /system format. After I formatted it the ROM booted nicely.
I just verified and all the ICS installation nodes advise to format system, too. Since he's encountering this issue it wouldn't hurt him to try and do the full monty
Greetz

frutelaken said:
You should.
I had got stuck at the Google bootscreen trying to do it without a /system format. After I formatted it the ROM booted nicely.
I just verified and all the ICS installation nodes advise to format system, too. Since he's encountering this issue it wouldn't hurt him to try and do the full monty
Greetz
Click to expand...
Click to collapse
did try everything, can change bootloaders, can flash stock with odin, can restore previously saved backup (with error on data recovery, but i think it should start anyway). BUT always stopped on on reboot at google logo.
Also can mount USB from recovery menu and copy any files from SD card to PC, but any file copied from pc to SD card dissapear after reboot.
It looks like some system file mounting problem

Same boat!
oxothuk_uae said:
It looks like some system file mounting problem
Click to expand...
Click to collapse
FWIW, I seem to be in the same boat today!
NS4G -
I had been successfully bouncing between Koush's rlasalle15 port and AOSP, with no issues. Today got stuck in boot screen.
Tried recovery from CWM 5.0.2.0, no luck, as it doesn't see the SD card.
Tried wipe data/factory, I get this error:
e:format_volume:make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata
and an error formatting /sdcard/.android_secure!
so, data wipe completes, but something is going on here.
---------- Post added at 08:43 PM ---------- Previous post was at 07:50 PM ----------
So, mine is resolved, although I dont know why.
I connected the NS4g via USB and sat at recovery.
I went into ADB into ADB Shell to see what was up/
There was my /sdcard directory, but it was empty.
OK so the issue is somehow its shot, so I'll just create the clockworkmod folders and then push in my last revoery directory, since I moved a copy to my PC.
Halfway through the push, I get a protocol error, the USB on the PC starts singing (installed uninstall bonks) my screen go blank on the phone.
I do a battery pull and .......
Everything is fine! I get back into my last image on a normal boot, and can see my SD card fine.
WHat is strange is the files I copied during the ADB push are not there, so something is still funky in the file system, but so far, I am back up!
here is what I did:
C:\Users\xxxxxx>adb shell
~ # cd /sdcard
cd /sdcard
/sdcard # mkdir clockworkmod
mkdir clockworkmod
/sdcard # cd clockworkmod
cd clockworkmod
/sdcard/clockworkmod # mkdir recovery
mkdir recovery
/sdcard/clockworkmod # cd recovery
cd recovery
/sdcard/clockworkmod/recovery # mkdir bl
mkdir bl
/sdcard/clockworkmod/recovery # push "C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl"
C:\Users\xxxxxx>adb push "C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl" /sdcard/clockworkmod/recovery/bl
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/system.ext4.tar -> /sdcard/clockworkmod/recovery/bl/system.ext4.tar
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/recovery.img -> /sdcard/clockworkmod/recovery/bl/recovery.img
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/nandroid.md5 -> /sdcard/clockworkmod/recovery/bl/nandroid.md5
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/data.ext4.tar -> /sdcard/clockworkmod/recovery/bl/data.ext4.tar
protocol failure

schreibman said:
FWIW, I seem to be in the same boat today!
NS4G -
I had been successfully bouncing between Koush's rlasalle15 port and AOSP, with no issues. Today got stuck in boot screen.
Tried recovery from CWM 5.0.2.0, no luck, as it doesn't see the SD card.
Tried wipe data/factory, I get this error:
e:format_volume:make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata
and an error formatting /sdcard/.android_secure!
so, data wipe completes, but something is going on here.
---------- Post added at 08:43 PM ---------- Previous post was at 07:50 PM ----------
So, mine is resolved, although I dont know why.
I connected the NS4g via USB and sat at recovery.
I went into ADB into ADB Shell to see what was up/
There was my /sdcard directory, but it was empty.
OK so the issue is somehow its shot, so I'll just create the clockworkmod folders and then push in my last revoery directory, since I moved a copy to my PC.
Halfway through the push, I get a protocol error, the USB on the PC starts singing (installed uninstall bonks) my screen go blank on the phone.
I do a battery pull and .......
Everything is fine! I get back into my last image on a normal boot, and can see my SD card fine.
WHat is strange is the files I copied during the ADB push are not there, so something is still funky in the file system, but so far, I am back up!
here is what I did:
C:\Users\xxxxxx>adb shell
~ # cd /sdcard
cd /sdcard
/sdcard # mkdir clockworkmod
mkdir clockworkmod
/sdcard # cd clockworkmod
cd clockworkmod
/sdcard/clockworkmod # mkdir recovery
mkdir recovery
/sdcard/clockworkmod # cd recovery
cd recovery
/sdcard/clockworkmod/recovery # mkdir bl
mkdir bl
/sdcard/clockworkmod/recovery # push "C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl"
C:\Users\xxxxxx>adb push "C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl" /sdcard/clockworkmod/recovery/bl
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/system.ext4.tar -> /sdcard/clockworkmod/recovery/bl/system.ext4.tar
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/recovery.img -> /sdcard/clockworkmod/recovery/bl/recovery.img
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/nandroid.md5 -> /sdcard/clockworkmod/recovery/bl/nandroid.md5
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/data.ext4.tar -> /sdcard/clockworkmod/recovery/bl/data.ext4.tar
protocol failure
Click to expand...
Click to collapse
but path for my recovery was
....clockworkmod\backup\2011-11-20.15.12.14\
should i create same backup dir?

oxothuk_uae said:
but path for my recovery was
....clockworkmod\backup\2011-11-20.15.12.14\
should i create same backup dir?
Click to expand...
Click to collapse
So, understand mine didn't even 'work', so sure, try it and see. My orig back up was a date like your one as well, I just changed it to make it shorter.
Remember it bombed on my on the PUSH, then everything started to work.
SOMETHING is STILL no 'right', as it is hit or miss if I can even get back into CWM (as of now, no I can't), and 1/2 the time I get stuck booting.....
SO, I'm not completly clean, I'd love to know the ADB commands to do a complete reformat of everything on my NS4g SD card, as I think this has something to do with either the new ICS change to MTP .vs. USB mass storage, or maybe the difference between the koush port and the AOSP port. but I think I got some issues still to iron out.

schreibman said:
So, understand mine didn't even 'work', so sure, try it and see. My orig back up was a date like your one as well, I just changed it to make it shorter.
Remember it bombed on my on the PUSH, then everything started to work.
SOMETHING is STILL no 'right', as it is hit or miss if I can even get back into CWM (as of now, no I can't), and 1/2 the time I get stuck booting.....
SO, I'm not completly clean, I'd love to know the ADB commands to do a complete reformat of everything on my NS4g SD card, as I think this has something to do with either the new ICS change to MTP .vs. USB mass storage, or maybe the difference between the koush port and the AOSP port. but I think I got some issues still to iron out.
Click to expand...
Click to collapse
i have same empty /sdcard on adb shell
but can not push
seems problem can be fixed with full reformat or re-partintion memory
anyway push return this
push
/sbin/sh: push: not found

oxothuk_uae said:
i have same empty /sdcard on adb shell
but can not push
seems problem can be fixed with full reformat or re-partintion memory
anyway push return this
push
/sbin/sh: push: not found
Click to expand...
Click to collapse
Just for grins, try this:
Battery pull.
Insert battery
Hold volume down and power on.
if no luck try
adb shell
cd /sdcard
mkdir /foo
and see if it sees the sdcard

schreibman said:
Just for grins, try this:
Battery pull.
Insert battery
Hold volume down and power on.
if no luck try
adb shell
cd /sdcard
mkdir /foo
and see if it sees the sdcard
Click to expand...
Click to collapse
again
I CAN BOOT into recovery
can adb but any file copied to any dir DISAPPEAR after reboot
Mount comand return
Code:
mount -w
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nodev,noatime,nodiratime)
/dev/block/platform/s3c-sdhci.0/by-name/userdata on /data type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/platform/s3c-sdhci.0/by-name/system on /system type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/platform/s3c-sdhci.0/by-name/media on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
~ #

[Q] help unbrick b70+ tf101

i have a major and awkward problem , my tf101 is bricked after installing Clemsyn-Blades3.2OCver22a but the weirdest thing is my micro sd card does not show up, only the internal storage. so because of that i cant infect nothing into cmw via micro sd
also .. cold boot freezes

Have you tried reformatting your card in a computer for FAT32?
Also, is your B7O SBKv1 or SBKv2? If it is SBKv1 you can use NVFlash if you need to.

i tried nvflash does not work so im guessing im sbv2.
i formatted micro sd(fat 32)
still only internal memory shows up in cwm .
dnt boot, stuck on asus symbol, tried wiping data and cold booting still , dnt work.
tried everything to my knowledge

kingx00 said:
i tried nvflash does not work so im guessing im sbv2.
i formatted micro sd(fat 32)
still only internal memory shows up in cwm .
dnt boot, stuck on asus symbol, tried wiping data and cold booting still , dnt work.
tried everything to my knowledge
Click to expand...
Click to collapse
Have you tried a different SD card?

kokopopz said:
Have you tried a different SD card?
Click to expand...
Click to collapse
i tried another sd card, but with no unveil it still does not work.
idk if this helps but im using clockwork mod v5.5.04

kingx00 said:
i tried another sd card, but with no unveil it still does not work.
idk if this helps but im using clockwork mod v5.5.04
Click to expand...
Click to collapse
I would check the CWM 5.5.0.4 thread to see if others have the same issue.

kingx00 said:
i tried another sd card, but with no unveil it still does not work.
idk if this helps but im using clockwork mod v5.5.04
Click to expand...
Click to collapse
frederuco said:
I would check the CWM 5.5.0.4 thread to see if others have the same issue.
Click to expand...
Click to collapse
Yeah take a look here
http://forum.xda-developers.com/showthread.php?t=1530337

have you tried to mount manually your sdcard? wich version of cwm you have? the CWM 5.5.0.4 only shows internal sd, but you can manually mount microsd
You will needn adb ready to use in your computer.
adb shell will give you a shell where:
enter sdcard
Code:
cd /sdcard
create a folder to mount your microsd
Code:
mkdir microsd
mount your microsd
Code:
mount /dev/block/mmcblk1p1 /sdcard/microsd
and now navigate trough sdcard to that folder
EDIT: i just had the same problem and i fixed like that,

shaola said:
have you tried to mount manually your sdcard? wich version of cwm you have? the CWM 5.5.0.4 only shows internal sd, but you can manually mount microsd
You will needn adb ready to use in your computer.
adb shell will give you a shell where:
enter sdcard
Code:
cd /sdcard
create a folder to mount your microsd
Code:
mkdir microsd
mount your microsd
Code:
mount /dev/block/mmcblk1p1 /sdcard/microsd
and now navigate trough sdcard to that folder
EDIT: i just had the same problem and i fixed like that,
Click to expand...
Click to collapse
ill give it a try

shaola said:
have you tried to mount manually your sdcard? wich version of cwm you have? the CWM 5.5.0.4 only shows internal sd, but you can manually mount microsd
You will needn adb ready to use in your computer.
adb shell will give you a shell where:
enter sdcard
Code:
cd /sdcard
create a folder to mount your microsd
Code:
mkdir microsd
mount your microsd
Code:
mount /dev/block/mmcblk1p1 /sdcard/microsd
and now navigate trough sdcard to that folder
EDIT: i just had the same problem and i fixed like that,
Click to expand...
Click to collapse
now i have a microsd folder among internal folders
when i chose to open it keeps saying files not found . i already put stock rom on the microsd

kingx00 said:
now i have a microsd folder among internal folders
when i chose to open it keeps saying files not found . i already put stock rom on the microsd
Click to expand...
Click to collapse
ok, that's probably because /sdcard is a symobolinc link to /media/data, it did happen to me also
so go to root directory and delete sdcard with rm (of course you will have to unmount everything mounted over there is there is something)
now create a folder named /sdcard and mount your microsd over sdcard

shaola said:
ok, that's probably because /sdcard is a symobolinc link to /media/data, it did happen to me also
so go to root directory and delete sdcard with rm (of course you will have to unmount everything mounted over there is there is something)
now create a folder named /sdcard and mount your microsd over sdcard
Click to expand...
Click to collapse
my adb shell skills are lacking can you please tell me how i do this
thanks in advance

kingx00 said:
my adb shell skills are lacking can you please tell me how i do this
thanks in advance
Click to expand...
Click to collapse
Code:
rm sdcard
mkdir sdcard
mount /dev/mmcblk0p7 sdcard
cd sdcard
mkdir microsd
mount /dev/mmcblk1p1 microsd

shaola said:
Code:
rm sdcard
mkdir sdcard
mount /dev/mmcblk0p7 sdcard
cd sdcard
mkdir microsd
mount /dev/mmcblk1p1 microsd
Click to expand...
Click to collapse
tried it several times and still not able to get nothing into the microsd, i can see the file but when clicked still cant adb push the stock rom

kingx00 said:
tried it several times and still not able to get nothing into the microsd, i can see the file but when clicked still cant adb push the stock rom
Click to expand...
Click to collapse
adb push? what are you talking about? i think you are messing diferent things here

shaola said:
adb push? what are you talking about? i think you are messing diferent things here
Click to expand...
Click to collapse
i did what you told me, but still unable to enter the microsd, cwm keeps informing me no files are found. ive tried the code you given me . it created the microsd file , and i unmounted and mounted it back, and still nothing appears inside the file

kingx00 said:
i did what you told me, but still unable to enter the microsd, cwm keeps informing me no files are found. ive tried the code you given me . it created the microsd file , and i unmounted and mounted it back, and still nothing appears inside the file
Click to expand...
Click to collapse
Take the microSD card out of your TF. Use USB adaptor or what ever and transfer all files you need to it.
Put it back in the TF and do what shaola stated about mounting your sd card. See if that work.
I just think there's a mis communication of what he's trying to tell you and what you're actually doing.

shaola said:
have you tried to mount manually your sdcard? wich version of cwm you have? the CWM 5.5.0.4 only shows internal sd, but you can manually mount microsd
You will needn adb ready to use in your computer.
adb shell will give you a shell where:
enter sdcard
Code:
cd /sdcard
create a folder to mount your microsd
Code:
mkdir microsd
mount your microsd
Code:
mount /dev/block/mmcblk1p1 /sdcard/microsd
and now navigate trough sdcard to that folder
EDIT: i just had the same problem and i fixed like that,
Click to expand...
Click to collapse
big thx this has worked for me
i'm happy that my transformer is not bricked

So I have the issue where my CWM version is boot looping. I know how to fix it by flashing the CWM roach fix but my SD card directory is not visible either. I unfortunately can not get my transformer driver to install. The driver that is provided from the asus website isn't working. That and the driver should be showing "APX" i believe and it's showing "Transformer".
Basically, I guess I'm asking could this be caused due to me using windows xp? If i use windows 7 would I be able to get the driver installed? Would linux be a work around as well? Can anyone any thought of the situation that or maybe a work around?

I am stuck in the same boat as the original poster. The problem I have is that Win7 pro x64 will not recognize my b70 tf101 in cwm recovery. when i am in device manager it is listed in "other devices" and the device name shows up as "transformer"
any way you could link me the proper driver ?