Related
Hi as title says I want to know how to transfer files propelry while booted into android kernel.
For example when you plug in your phone vai USB and use as card reader I can easily transfer files to and from but the problem is that when I unplug and go to view these files on phone the file system hasn't updated and I cant locate them on card.
Ive tried the unmount feature aswell as a hot reboot but nothing. Only way I can seem to do it is to power off and then boot back into android.
Is there any easier way or procedure that I need to follow?
TheATHEiST said:
Hi as title says I want to know how to transfer files propelry while booted into android kernel.
For example when you plug in your phone vai USB and use as card reader I can easily transfer files to and from but the problem is that when I unplug and go to view these files on phone the file system hasn't updated and I cant locate them on card.
Ive tried the unmount feature aswell as a hot reboot but nothing. Only way I can seem to do it is to power off and then boot back into android.
Is there any easier way or procedure that I need to follow?
Click to expand...
Click to collapse
best bet is to load the files in winmo then boot into android
Dude that wasnt my question, obviously I can do that, thats not the point.
My question was the best way to transfer files while booted into android, if it possible then obviously booting into windows and back to android every time you want to move/access files isnt the "best" way and its inconvient.
I appreciate your reply but your answer was irelivant unless its the ONLY way which I doubt (well hope)
Does anybody have a solution?
As of now, the only good way to transfer files is indeed through WinMo (or with a MicroSD USB reader, with phone powered off or in WinMo). Most Android builds support USB Mass Storage, but I haven't heard of one that handles it perfectly (which isn't too surprising, considering Android runs -sort of- from the SD card).
So in short, no there is no other way at this moment that I know of.
Edit: There is a way: through WiFi! There are some applications available on the market that turn your phone into an FTP-server, I use Websharing (Lite) for this. They don't need an unmounted SD card, so they'll probably solve your problem.
StephanV said:
Edit: There is a way: through WiFi! There are some applications available on the market that turn your phone into an FTP-server, I use Websharing (Lite) for this. They don't need an unmounted SD card, so they'll probably solve your problem.
Click to expand...
Click to collapse
Yeah I was thinking more of teh same route, Ive been using drop box for the moment but FTP server would be much better.
I was hoping there would be a solution to been able to access teh files that have been sent via mass storage mode but this could be just as good.
thnx for suggestion.
This is not a quickfix, but I was frustrated with the same problem last night when I was trying to locate the files that I just transferred to the phone. I noticed that unmounting, and remounting doesn't refresh the folders in the system. But I managed to find the transferred files after unmounting the sd card, and then browsing to the root sd card path instead of the mounted partition.
So, instead of mnt/sdcard/ you should look for the files in /sdcard after unmounting the card. See if that works, at least it worked for me last night.
Use droid explorer
This question may have been answered before but I just cant find it here.
I tried rooting my vibrant with the classic method described here.
http://forum.xda-developers.com/showthread.php?t=723479&highlight=issues+rooting+vibrant
It didn’t work and I got the following message:
E: can’t open /sd card/update.zip
(no such file or directory)
Installation aborted
I copied the update.zip file in DCIM of internal memory card and was still getting the same message.
I copied the update.zip file into my sd card and still got the same message.
I followed the steps exactly as they have been described in the rooting thread.
I haven't tried the one click root method yet.
Would anyone know what seems to be the problem.
Thanks.
You have to replace the update.zip file and flash it with recovery.
Sent from my SGH-T959 using Tapatalk
Are you saying I have to replace with a new update.zip file and repeat the method again?
I was doing it in recovery mode.
Use the one click method. You can find all the info on unlockr.com in the--how to -- (they have a nice video) If it doesn't work then you will need to flash back the T959UVJFD stock through Odin. Look in the bible or search in this website.
Why is your update.zip in DCIM? Download that one from the forum post, rename it to update.zip, and copy it to the root directory of your sd card.
Yea replace the update.zip with a modified one that gives you root access. Its should be on the bible(stickie post) and Recovery mode is correct.
Sent from my SGH-T959 using Tapatalk
Sdobron said:
Why is your update.zip in DCIM? Download that one from the forum post, rename it to update.zip, and copy it to the root directory of your sd card.
Click to expand...
Click to collapse
Can you explain what is the root directory of internal sd card where I need to place the update.zip file?
Yea replace the update.zip with a modified one that gives you root access. Its should be on the bible(stickie post) and Recovery mode is correct.
Click to expand...
Click to collapse
Now my computer isn't recognizing the phone when I mount the sd card. It tries to install drivers for the phone and can not.
Ok, by root directory they just mean the internal 16gb memory.
Ok look, download update.zip. Rename it to "update" without the quotation marks. If you are running windows 7 you dont have to add ".zip" windows knows it is a .zip file, so again just name it update and windows and your phone will automatically know it is update.zip. maybe the problem is you are naming it "update.zip" and your phone is reading it as "update.zip.zip"
Anyways, I don't know why your drivers don't work, but once you get your computer to recognize your phone. Mount your phone to your computer.
Then go to your internal memory, the 16gb one, not the external sd card.
Now, DON'T GO INTO any folders, the root is just the internal memory, again don't go into any folders. Place the "update" file into the internal memory, don't place it into any folder.
Reboot your phone into recovery mode, and then reinstall packages.
good luck.
SamsungVibrant said:
Ok, by root directory they just mean the internal 16gb memory.
Ok look, download update.zip. Rename it to "update" without the quotation marks. If you are running windows 7 you dont have to add ".zip" windows knows it is a .zip file, so again just name it update and windows and your phone will automatically know it is update.zip. maybe the problem is you are naming it "update.zip" and your phone is reading it as "update.zip.zip"
Anyways, I don't know why your drivers don't work, but once you get your computer to recognize your phone. Mount your phone to your computer.
Then go to your internal memory, the 16gb one, not the external sd card.
Now, DON'T GO INTO any folders, the root is just the internal memory, again don't go into any folders. Place the "update" file into the internal memory, don't place it into any folder.
Reboot your phone into recovery mode, and then reinstall packages.
good luck.
Click to expand...
Click to collapse
Nevermind. But thanks alot for your response and help. After looking around to find some alternative ways to root..I finally was able to root my vibrant using the method described
HERE
In the end, rooting was as easy as installing a simple app.
Now im going to do some research on ROMs and hopefully flash before doing titanium backup.
sLiKK said:
Nevermind. But thanks alot for your response and help. After looking around to find some alternative ways to root..I finally was able to root my vibrant using the method described
HERE
In the end, rooting was as easy as installing a simple app.
Now im going to do some research on ROMs and hopefully flash before doing titanium backup.
Click to expand...
Click to collapse
Ok, make sure you do lots of research. Read the bible, every last word of it.
Don't ever try to downgrade from 2.2 to 2.1 without having the proper 2.1 kernal, becareful with lagfix such as voodoo, and learn odin.
good luck
I have run into another issue. I can not mount my phone to computer.
With USB Debugging off... I dont even get a notification in the slide down menu asking me to either mount/unmount.
With USB Debugging on... I do get the option in slidedown menu to mount my phone. At the same time the computer shows a pop up message asking me to install driver software for Samsung_Android. In the meantime , I press mount sd card which by the way is still not recognized by the computer.
I dont have the driver for samsung_android to install on the computer.
Does anyone know a potential fix for this situation.
Thanks.
ok i'm using taboonay 2.0 with Thor's 3.0 kernel. I can see all the files on my SD card through root explorer and if i take the card out and hook it up to my pc. My question is why when i plug my iconia into my PC i can see the card, but can't see any files on it? Wasn't 3.2 supposed to fix this or it something on my end? haven't tried to reformat it cause it isn't a big issue to me just trying to figure out why.
i have sorta similar issue. I can access sdcard in root explorer or other apps, but if i pop it out it get interesting. I can still browse the sdcard contents in any file explorer even though i am holding it in my hand. Also i have not been able to access the sdcard from the latest clockwork recovery. The only directory there is LOST. So i take it to the pc and same thing, only the LOST directory, pop it back in the tablet, fire it up, browse to /sdcard directory, all the files i have downloaded are right there still along with that LOST directory......
So i cant flash anything now. Tried reflashing CWR from the Acer Recovery Installer, no progress. Tried formatting sdcard on pc using the tool in the sticky, same thing, cannot access sdcard in CWR.
Help.
**update: so here's what i found, apparently there is a directory called sdcard on my tab that is actually local system memory. It has all my downloaded files in it. I mounted the tablet with USB to my pc and moved one of the files to the sdcard(which is empty by the way, everything is going to the local ram for some reason) and rebooted into recovery and then it showed up in CWR!
So all this time my tablet has been syncing my google music beta music for offline use, around 10 gigs of it, and it dumped it all on the local memory so now im almost out of ram.....with an empty sdcard.....great
I believed you guys are having this same problem...please see this thread about directory naming structure...etc
http://forum.xda-developers.com/showthread.php?t=1242477
Hi,
Just Got the 7.7 3g - so far so good. Screen is as good as they say
The extra resolution defn. helps with web browsing.
Not finding any lag really.
7.7 is just about the limit for my two handed use but i would say the original 7" was a wee bit easier to handle but something with time should become more intuitive.
Just a few issues - external sd card is somewhat limited. Might be deliberate by Samsung but does not make sense.
Normal user apps cant access to the external sdcard. Using connect bot, i checked permissions and it seems that it is mounted by the os with system permissions, where as the internal sdcard is mounted as sd_rw.
This can't be correct? The only way to copy stuff to it is to use the samsung system file explorer as it has system permissions So copy to internal first then to external - this sounds like a bug?
I have not rooted this yet - might then chown to sd_rw get rid of this ?? There is a lot of entries in the vold.fstab to make sense of. Not a hacker so just looking around. A bit too early to start soft-bricking
But I take these don't have protected bootloaders so thats why we can root ?
Video playback is v.good but I am not able to throw on a bluray m2ts file (obviously with the sd card issue) and play smoothly. I found Dice player can handle m2ts by renaming it to a ts file. It then can use hardware decoding. Still drops frames but still watchable to a certain degree. For all other files mx player is still best. I have lossy transcoded some "native" blurays clips and seems that it handle high profile h264 1080p at high bitrates very well. Hoping, formatting sd card ext3/ext4 will improve things.
On the whole very impressive device - plus more ics goodies to come soon hopefully.
I've noticed some issues with the external SD card as well. Only the stock file manager can copy files from the internal storage to the external storage. I was able to transfer files to the ext. SD via Dooblou's Wifi Explorer, though. Although that would crap out a few times.
I'm hoping that we see some new ROMs with a different file system at any rate. The 4GB limit is so 1998.
Fix for external sd write issue
I've already posted a fix for this in our original thread?
davp said:
There is a fix for the write to external storage in this thread:
Samsung Galaxy Tab Plus->Galaxy Tab Plus General->unable to write files to external sd card
post #7
Requires root to apply fix.
There is a new permission that older file managers aren't asking for yet. The stock file manager knows to ask for it.
Fix worked for my P6810 wifi.
Click to expand...
Click to collapse
thaloneus said:
I can't post a link to the original post on another forum that worked for me so I will quote it:
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart your tablet.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Click to expand...
Click to collapse
Rooted and then applied this change.
Can write to ext sdcard !!!!
Cheers
Will apply as soon as i get tad, should be getting it today, cant wait
Sent from my GT-P1000 using XDA App
I think you have to format the sd card in the tab. I been able to transfer files no problem. Maybe its due to the mtp for the internal sd.
Sent from my GT-P6800 using xda premium
will6316 said:
I think you have to format the sd card in the tab. I been able to transfer files no problem. Maybe its due to the mtp for the internal sd.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Using downloaded apps or the stock File Manager app? Because I formatted the SD card in the Tab and nothing else can write to it. Now, I can drag and drop stuff from my computer via MTP, but that's not the same issue.
Ok, I'm trying to add the permission and it doesn't seem to save after a reboot. I'm rooted and made sure to mount that directory as R/W. After I edit platform.xml and reboot it simply reverts. Can anyone offer a more granular description to this n00b?
Thanks.
Edit: Nevermind. I edited the file on my computer and copied it over the original and am good to go.
burhanistan said:
Ok, I'm trying to add the permission and it doesn't seem to save after a reboot. I'm rooted and made sure to mount that directory as R/W. After I edit platform.xml and reboot it simply reverts. Can anyone offer a more granular description to this n00b?
Thanks.
Edit: Nevermind. I edited the file on my computer and copied it over the original and am good to go.
Click to expand...
Click to collapse
Thanks Burhanistan. I had this problem too and did what you did to get around it. Now I can read/write to the external SD with any file explorer.
Hello,
I can access the external SD with no problem, only issue is Titanium backup showing 440Mb capacity on the external SD (32Gb card).
Anyone with the same issue? Any fix?
Thanks.
No problem for me
davp said:
I've already posted a fix for this in our original thread?
Click to expand...
Click to collapse
Things must have changed as i got my P6800 recently did the upgrade from samsung and tried to copy to external sd and no problem for me. I never tried to do it pre upgrade but maybe the upgrade fixed that. Re i can copy and paste to device from my pc when its connected - to both device and sd. I can also copy using the the stock file manager from device to sd card.
No Issues here also
I recieved the tap a week ago. Now my 32GB Sandisk SD is here.
The Tap did at the first startup and using the described 12 MB Android update via internet conn.
Until now there is no issue between writing from/to SD over PC/MTP, copying between internal and external SD. Used preinstalled Filemanager and ES File Ex.
I tried it unrooted and rooted but not before the Android update.
davp said:
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart your tablet.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Click to expand...
Click to collapse
Some people are reporting the above procedure is no more needed, however, with several apps (like Titanium backup, and a SAMBA explorer), writing to the sdcard (extstorage/.../sdcard) is still impossible (GT6800 updated to latest samsung firmware).
I have used this procedure and can state that Titanium backup works now with the SD card.
Thanks to many reading within the XDA forum, I have found this simpler procedure :
- download / install the "Root Browser Lite" app from the android market
- add write access to group and other to the following directory: /system, /system/etc, /system/etc/permissions (with root browser Lite, press on the directory name during 3 seconds to get a contextual menu allowing to change the permissions)
- add write access to group and other to the file platform.xml in /system/etc/permissions
- use the editor of "Root Browser Lite" to modify the file platform.xml as described above (you should have two <group gid= ...> lines within the WRITE_EXTERNAL_STORAGE xml block.)
- save the file. Verify that a .bak file has been created and that the date of platform.xml changed.
- remove the write access.
- Turn off the GTAB, then turn it ON.
NB: Titanium backup still reports a erronous free size on the SD card (401MB), but backups on the sdcard work.
can't save the xlm doc
davp said:
I've already posted a fix for this in our original thread?
Click to expand...
Click to collapse
Hi, I edit the file but when I try to save it I fail because it says original saved as .....xlm.bak, but I can't find that file and the one I find is unchanged, any ideas?
There is an automated installer for the fix here:
http://forum.xda-developers.com/showthread.php?p=21670802
Is for the plus but worked fine for me
Sent from my SCH-I815 using Tapatalk
damm, must forget something, just followed exacty all the steps
still no writing on sd card
the automatic installer failed also
IS there a way to go into the (forgive the incorrect term) "registry" or similar, and have Android re-interpret/understand that instead of looking in "/sdcard"... it should instead look/point programs to "/mnt/sdcard/extstorages/sdcard"...
i heard that it might be called something like a "simlink" or "symbolic link"... maybe this could resolve the application installation issue to the sdcard as well as backups, transfers, etc... right now, not only do i run out of space too fast, can't install apps to the sd card, but as well, if i should run a hard reset... all my data erases! (yes, the internal "SD card" is erased in a hard reset)...
so, for all practical senses, when it says it will erase data, unless you KNOW you have copied ALL you user data to your "Real" SD Card, you will kill your data without even knowing it when you do a hard reset, even if you "thought" you were protected because "I saved my info to the SD card!"
(and yes, this was my experience today, so it's a fact.)
backup programs won't point to the sd card, (app manager, titanium, app list backup, etc)...
so unless you actively move files individually to the card (and know where to look)...
Bottom line... is there a hack/workaround on this that's not just "open up for file transfers" or is someone working on a ROM that might kill the partitioning and allow the /sdcard to actually point to a real external card?
Edited: Nevermind...
acess-rights-hell
hi forum
i would like to use the EzyKernel v1 - 23/02/2012 as in post http://forum.xda-developers.com/showthread.php?t=1513413&highlight=ezykernel
one of the prerequisites is a stock ZSKL firmware.
on the tab is/was XXKL4 AUT/CH
i successfully flashed the ZSKL2 - but that's where the nightmare started: i could not write to sdcard, busybox/superuser don't work properly, as i can't get root via su - which means to me, that there are messed up accessrights also in other places, not just the SD. the funny thing is, that i finally got the overclocking EzyKernel working, but not busybox + superuser.
does that sound familiar to anyone ?
i would really appreciate any ideas about this.
thank you
with best regards from switzerland
roland
could you please explain what "make sure you have mounted the file system r/w" means. And sorry for my noob question, but does this fix allow to install apps on the external sd card or I'm missing something.
After having formatted my internal sdcard, I'm unable to flash any rom. I've installed cwm revorery and would like to push a rom to the sdcard in order to be able to flash it, because right now theres nothing on my card (its totally formatted without any system on it).
When i try to push a file via toolkit to the internal sdcard there appears the following error message:
- exec ' /system/bin/sh' failed: No such file or directory (2) -
Can anybody help me out with this issue?
It looks like the error is saying it is missing a file in /system/bin/, which makes sense since internal storage is completely wiped.
Just start a command prompt in Windows and change directory to where adb.exe is in the android sdk. Then copy the ROM you want to install into the same directory as adb. Use the command "adb push blahblahblah.zip" to push the ROM from your PC to the internal storage. Obviously replacing blahblahblah.zip with whatever the ROM filename is.
Toolkit's can be handy, but before you use one you need to know how to unlock your phone and copy files to/from your device without a toolkit. So that way when problems arise you know what probably went wrong and how to fix it.
Probably not really helpful, but I was able to push files to /sdcard when I wiped all options and formatted Data with TWRP.
Same problem here
Please help us. I accidentally did the same. Now I can't copy file to the device. CWM is still functioning but there is nothing left to flash.
kimezra said:
Please help us. I accidentally did the same. Now I can't copy file to the device. CWM is still functioning but there is nothing left to flash.
Click to expand...
Click to collapse
Just flash TWRP recovery via Fastboot then mount the SD card as USB storage. Once you have done this you can copy a new Rom over and flash it.
Thanks for your quick reply!
EniGmA1987 said:
It looks like the error is saying it is missing a file in /system/bin/, which makes sense since internal storage is completely wiped.
Just start a command prompt and change directory to where adb.exe is in the android sdk. Then copy the ROM you want to install into the same directory as adb. Use the command "adb push blahblachblah.zip" to push the ROM from your PC to the internal storage. Obviously replacing blahblahblah.zip with whatever the ROM filename is.
Toolkit's can be handy, but before you use one you need tokn ow how to unlock your phone and copy files to/from your device without a toolkit. So that way when problems arise you know what probably went wrong and how to fix it.
Click to expand...
Click to collapse
You're right! I've learned that by wasting hours..
How do I change directory to where adb.exe is? what is android sdk? I'd be very happy if you could explain me some of the steps to achieve that or lead me to a tutorial where I can learn it.
Thanks again!
dr9722 said:
Just flash TWRP recovery via Fastboot then mount the SD card as USB storage. Once you have done this you can copy a new Rom over and flash it.
Click to expand...
Click to collapse
Thanks a lot for your reply!!
Would you mind telling me how to flash twrp recovery via fastboot?
Thx in advance!
http://forum.xda-developers.com/showpost.php?p=37019359&postcount=10
Also:
Once you are in a ROM again, download GooManager and look on Google for the easy steps to flashing TeamWinRecoveryProject.
Thank you so much EniGmA1987!! This is awesome!
It finally worked out for me! BIG THANKS!
Your welcome
Was it easy enough even without the use of a toolkit?
Your tutorial is very clear and easy to understand. I followed all the steps, but still couldn't find the pushed ROM on my SD card (after having waited for about 5 minutes). So I mounted all you can with cwm and used the toolkit - and it worked! Probably it was the directory that was set right after having followed your tutorial. Thanks again!!