I am using 2.6.32.32 - VFPv3_FP - Gtab/Zpad updated 03-07-2011 Kernel on Vegan 5.1
and I have found many threads on NTFS support for mounting like
http://forum.xda-developers.com/showthread.php?t=914822 and http://forum.xda-developers.com/show...5&postcount=27
but I have found nothing on NTFS writeable support; the newest kernel, which I am on, states:
-add NTFS (w./ write support (proceed with caution if writing!)),CIFS,FUSE,TUN (kernel modules; pull the desired module from lib-2632.29.tar.gz and place in to /system/lib/modules/2.6.32.31-cyanogenmod/ and use insmod to insert) and EXT4 (in-built)
so how do I go about making my NTFS drive writeable
I can mount and unmount it but it is readable only, even tried mounting it mount -o rw and it then will show up as r/w in root explorer but when I try to copy and past something onto the drive nothing copies so it is showing as being writeable but is not apparently writeable, I must be missing something.
Thanks
Hellow everybody.
Running android revolver 3 i connect my external usb hard drive, wich is formated in ext4, and is not mounted automatically, looking at dmesg i see that the system tries to mount it as ntfs drive so it fails, but i can manually mount it through a terminal emulator.
Does anybody know how can i correct this?
I have no experience in android systems. I thought i could add a line to the fstab identifying the disk by uuid but there is no fstab, there is vold.fstab but i don't underestand so well the syntax of that file.
is there in the other way something like udev rules or something like that in android?
Thanks
Did you ever find out how to use the vold.fstab correctly?
It might help me.
I'm trying to have a fixed mount point for some external usb disks on my mk808 (without much luck) and found my ext3 usb drive also doesn't mount automatically.
shaola said:
Hellow everybody.
Running android revolver 3 i connect my external usb hard drive, wich is formated in ext4, and is not mounted automatically, looking at dmesg i see that the system tries to mount it as ntfs drive so it fails, but i can manually mount it through a terminal emulator.
Does anybody know how can i correct this?
I have no experience in android systems. I thought i could add a line to the fstab identifying the disk by uuid but there is no fstab, there is vold.fstab but i don't underestand so well the syntax of that file.
is there in the other way something like udev rules or something like that in android?
Thanks
Click to expand...
Click to collapse
Can't mount SD card in recovery. See http://bit.ly/LgBTUN.
Tried fix permissions, mount sdcard in recovery says Error mounting /sdcard, other stuff too. Still no go.
Found forum posts with same problem in several HTC phones but don't think the fix works for TF101.
I'd like to put the Megatron ROM on my TF101 though I'd be happy just to get ASUS upgrades. They keep failing - I think from my Dvorak keyboard mod (see device config below).
Any ideas?
TF101. Stock, rooted rom with modded key mapping for Dvorak keyboard when docked. Android Version 3.2.1. Kernel 2.6.36.3 [email protected] #1, Build Number HTK75.US_epad.8.6.5.19-20111107.
Can you still boot Android or did you already wipe?
I also see ROM manager, which is usually bad news for the TF...
That's a rather old recovery, if you can get ADB access you can try my PERI tool to reflash a newer recovery that should mount properly, and then flash a ROM with that.
Good luck!
First, thanks for the help.
I tried your tool. Besides having entertaining comments, it just left me frustrated.
You can see some screenshots at https://docs.google.com/open?id=0B46V3MQdpAUOek1GRGlvS0FKTms
I'm wondering if the problem is that I can't mount / as RW. Perhaps I'm just not getting the right args to adb's mount command. I think I should be able to remount / RW as I can run "adb shell" and then "su" to get the "#" prompt.
I do think part of the problem is that /sdcard is not actually my sdcard. It is a symlink to /mnt/sdcard which is where the physical sdcard is mounted.
I tried to modify init.ventana.rc. I think that is the right file - I just found it by poking my head around. This is what I wanted to change:
Code:
on early-init
mount debugfs debugfs /sys/kernel/debug
export EXTERNAL_STORAGE /mnt/sdcard
mkdir /mnt/sdcard 0000 system system
# for backwards compatibility
symlink /mnt/sdcard /sdcard
But I can't mount / RW so I can't change it. I tried this:
Code:
$ adb root
adbd cannot run as root in production builds
$
I'm definitely rooted. I can su to root in ADB. I also have a SuperUser that seems to be working.
Update: I can mount / RW via ES File Explorer. I can then adb shell, su, and then update files in /. I pushed my updated init.ventana.rc but when I rebooted it reverted to the original.
I'm terribly frustrated.
Any ideas? I seem to have a totally useless CWM. I can't even put a file on /sdcard/update.zip because the sdcard isn't booted when I'm in recover.
Once I get / mounted RW, can I just copy a working CWM into some system directory?
I've spent half my day messing around with this thing. I'm very comfortable with the command line and would happily do a manual install if someone could tell me how to do that.
I tried the adb equivalent of:
Code:
run_program("/sbin/busybox", "dd", "if=/tmp/recoveryblob", "of=/dev/block/mmcblk0p4");
using the 5.5 recoveryblob but it didn't seem to do anything. If I just knew the magic commands, I'd be happy to do them.
Hi there.
I just released the beta version of my EasyFlasher tool.
Try using that, it'll flash Rogue Recovery for you which should successfully mount the sdcard.
You may need to use that (It's Nvflash based) It won't work on a Tf101G or Sl101 though. Give it a shot.
PERI didn't work because your ADB drivers don't work.
Thanks for your help. I finally got a working CWM by following this thread. I then flashed the CWMs you pointed to.
Problem solved.
Though I can always f-up my upgrade to CM9 and be back here for help in a few hours.
Too Funny
I just posted my thanks reply and then noticed that you two pointed me to the solution that I found.
I appreciate your help and timeliness (and your nvflash program too).
Neil
Got my TF101 BK70 SBK1 in same situation and this thread helped me a lot.
Just put my tf into apx mode (hold up + power for 7 seconds, screen stays black but device manager can see APX device connected, then use Universal Naked drivers to fix it.
After that, just open EasyFlasher and choose which recovery you want.
I also had the same problem, I didn't see this thread so I used this workaround:
if you have the keyboard dock you can mount an external usb drive as the sdcard (under the mount options) and do all the backups/flashing from there
Sent from my Transformer using xda app-developers app
There are two sd cards, the internal sd card which is the phone's built-in USB storage, and external sd card which is the removable sd card that is physically located at the back of the phone and is sealed by your phone's battery.
so technically speaking you should be choosing the "choose zip from external sd card" based on how you described storing your rom.
I'm not sure as to why your sdcard is unmounted, but you can remount it back using CWM. There should be a "mounts and storage" section in CWM menu, where you can remount the internal USB storage by selecting "mount /sdcard".
If you want to recover the data in your Android phone, just go to http://android-recovery.net/.
Need help with this can't mount /sd card /
Here is what I am getting (pics). This is on the Tf101 with CWM via 1 click root method
I am running stock 4.2.2, and I am trying to mount an ext4 formatted img file and chroot into it. However, no matter how and where I try to mount it (mount -o loop, losetup, ...), I get an error. Naturally, dedicated apps (Linux Installer, Linux Deploy) don't work either.
Has anybody managed to do this?
I have the latest TWRP, but I can't seem to mount the /data even after formatting it
Any ideas?
Okay, nevermind, a new kernel flash fixed this issue
It's crazy how often Samsung pumps out updates
Settings for MTP
I had to set my device to media transfer. I dont get the option to drop down from a menu and choose, I have to go into settings and bring up the different options. This is only happening to me on S8+(verizon)