Hello there,
I need help with this error on my DZ:
'unable to install application data on the device. Error: /mnt/sdcard/Tecarta/50.dat_temp (I/O error).'
The application I was trying to launch is the NKJV Bible software.
Thanks for your advice.
So is this a new SD card that you haven't used before now ?
steviewevie said:
So is this a new SD card that you haven't used before now ?
Click to expand...
Click to collapse
Correct, I only received it yesterday, and have spent hours formating and reformating to get rid of the "read only" error, and to copy the contents of the original 8GB that came with phone. But now have this problem.
Thanks.
Can you use it normally otherwise in the phone ? e.g. can you copy files to it within terminal emulator, or push files to it via adb etc ?
steviewevie said:
Can you use it normally otherwise in the phone ? e.g. can you copy files to it within terminal emulator, or push files to it via adb etc ?
Click to expand...
Click to collapse
I have not tried that. All I have used is the windows copy as well as making a .wrar file out of the 8gb contents, and then extracting the .wrar to the 32gb card.
Any suggestions?
YOSEFE said:
I have not tried that. All I have used is the windows copy as well as making a .wrar file out of the 8gb contents, and then extracting the .wrar to the 32gb card.
Any suggestions?
Click to expand...
Click to collapse
I would try to copy some files to it via Terminal Emulator, an "explorer" program or similar - so you can see if the phone just doesn't like the SD card, or whether it's only giving an error when installing an app.
steviewevie said:
I would try to copy some files to it via Terminal Emulator, an "explorer" program or similar - so you can see if the phone just doesn't like the SD card, or whether it's only giving an error when installing an app.
Click to expand...
Click to collapse
I have used the windows explorer to copy files, but what code can I used in terminal emulator to copy say, file "xyz" in the Androidsdk directory /tmp ?
YOSEFE said:
I have used the windows explorer to copy files, but what code can I used in terminal emulator to copy say, file "xyz" in the Androidsdk directory /tmp ?
Click to expand...
Click to collapse
The copy command is "cp", so try something like :
Code:
cp /tmp/xyz /sdcard
If it works ok it should just come back to the command prompt. Also you can do "ls /sdcard" to see everything there, e.g. see if it really did copy it to the SD card.
steviewevie said:
The copy command is "cp", so try something like :
Code:
cp /tmp/xyz /sdcard
If it works ok it should just come back to the command prompt. Also you can do "ls /sdcard" to see everything there, e.g. see if it really did copy it to the SD card.
Click to expand...
Click to collapse
Thanks. I will try it out.
EDIT: Solved. I had to follow advice from somewhere on the web. I had to put the card in a reader on my windows pc. Navigate to "Computer", then right-click drive "H" (that is what the msd card is on my pc), then click "Properties". After that, I selected "Tools", than clicked "Check now", and clicked "start". However, making sure that the first box (automatically fix file system errors) is checked. Leave "scan for and attempt..." unchecked.
Let the pc do its thing, and when it is done, that is it!
But hey, thanks steviewevie for being there and for being prompt to help me and others get our way around Android.
Probably I missed this question being answered somewhere, but I am tired of searching for it, so here it goes...
I decided not to root my device for now, and I am trying to get the most of it with stock limitations. Generally it is fine, but what bothers me most is the fact that i seem to be unable to write any files on phones internal memory. Is it so, that all / filesystem is inaccessible for write, or is there a dir where i could store some files i would like my phone to be able to access while sdcard is unmounted?
I may be wrong but thats the limitations of a "stock" phone,if you want access to the files you would have to root AFAI
That's exactly the impression I have, and I don't like the idea. I'm ex WM5/WM6 user, and I simply cannot understand why can't I have let's say /tmp/ dir just for myself...
banannq said:
That's exactly the impression I have, and I don't like the idea. I'm ex WM5/WM6 user, and I simply cannot understand why can't I have let's say /tmp/ dir just for myself...
Click to expand...
Click to collapse
Any reason for not rooting then? there are plenty stock roms/alternatives out there.
I grown tired of constantly tweaking my previous htc smartphone, decided to keep this one stock at least for now. I know rooting is an open door I will not want to close
and also I think there's no rooting method for gingerbread so far, is there?
As much as I know a downgrade is involved,I know what you mean about tinkering with the phone!It gets obsessive at times
You should have access to /data/local or at the very least /data/local/tmp
That's where fiels get pushed for rooting.
-Nipqer
The problem is I cannot even open /data directory
How are you trying to access the /data folder?
Cause if its some file manager app, some of them will only read sdcard.
-Nipqer
I'm used fre3vo to get temproot on my device (Z, Android 2.3.3),
and after that called:
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
i can write to /system, but after reboot or remount into readonly all my changes dissapearing. Should i need S-OFF on my device? Can i get S-OFF without rollback to v1.34 on temp rooted 2.42?
Yeah the emmc is write protected when you are s-on, so any changes to /system will dissappear on reboot.
Unfortunately you cannot get s-off without downgrading to 1.34.
-Nipqer
Nipqer said:
How are you trying to access the /data folder?
Cause if its some file manager app, some of them will only read sdcard.
-Nipqer
Click to expand...
Click to collapse
Normaly I use total commander for android, but tried also ES File explorer, Linda manager, andexplorer... all of them basicaly let me view / folders (with exception of /data, /root, /cache etc) so i think it is filesystem condition rather than file manager fault...
banannq said:
Normaly I use total commander for android, but tried also ES File explorer, Linda manager, andexplorer... all of them basicaly let me view / folders (with exception of /data, /root, /cache etc) so i think it is filesystem condition rather than file manager fault...
Click to expand...
Click to collapse
try root explorer. you can still view directories without root (the app will just tell you that it failed to request superuser access). I'm pretty sure everything under /data is r/w access by default. My phone is rooted so I can't verify whether or not you can write to that directory on stock (I'd assume you could as long as there's free space available) but I can definitely recall being able to look at all my directories on stock using root explorer.
sephiroth1439 said:
try root explorer. you can still view directories without root (the app will just tell you that it failed to request superuser access). I'm pretty sure everything under /data is r/w access by default. My phone is rooted so I can't verify whether or not you can write to that directory on stock (I'd assume you could as long as there's free space available) but I can definitely recall being able to look at all my directories on stock using root explorer.
Click to expand...
Click to collapse
I guess it doesn't matter what software i use android simply locks me out of internal phone memory. It sucks, because phone was advertised as having over 1GB of internal storage space (no mention about it being inaccessible), and i can't even store ringtones on my device (have to use sdcard, and suffer side effect of it being unmounted at times). What a shame... with all the greatness, android sucks at very simple things
banannq said:
I guess it doesn't matter what software i use android simply locks me out of internal phone memory. It sucks, because phone was advertised as having over 1GB of internal storage space (no mention about it being inaccessible), and i can't even store ringtones on my device (have to use sdcard, and suffer side effect of it being unmounted at times). What a shame... with all the greatness, android sucks at very simple things
Click to expand...
Click to collapse
Don't blame Android for your carrier locking down your device
Sent from my HTC Vision using XDA App
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
warlock257 said:
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
Click to expand...
Click to collapse
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
JoeSyr said:
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
Click to expand...
Click to collapse
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
warlock257 said:
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
Click to expand...
Click to collapse
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
JoeSyr said:
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
Click to expand...
Click to collapse
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
warlock257 said:
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
Click to expand...
Click to collapse
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
simms22 said:
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
Click to expand...
Click to collapse
Found the button, but didn't work
JoeSyr said:
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
Click to expand...
Click to collapse
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
warlock257 said:
Found the button, but didn't work
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
Click to expand...
Click to collapse
Well under normal circumstances, individual files on your sdcard should have permissions rw-rw-r--, and folders have rwxrwxr-x. (For reference, this is read as read, write, execute for Root, System, and Other, with dashes indicating that a permission is denied. So rwxrwxr-x means all permissions are granted to all three groups except for write to Other). This ties into larger aspects of the OS that basically exist to stop individual apps from reading or writing whatever they want without being included in groups.
The fact that you can't do something that shouldn't require elevated permissions, and you're getting that kind of error when you try to execute commands with higher permissions, suggests to me that your sdcard partition is using the wrong filesystem. Sort of sounds like a program tried to treat it like a real sdcard and formatted it to something else, in which case I have a hunch you're going to need to back up your data and do a full reset.
You might get a simpler solution if you ask in the thread for the toolkit you used. It's not something I have any experience with so good luck.
Out of curiosity, are you on Jellybean now? Jellybean changed the address for the sdcard partition, so if the toolkit wasn't updated to reflect this, it seems like the likely place things may have gone wrong.
---------- Post added at 07:04 PM ---------- Previous post was at 06:53 PM ----------
Actually if you want to check if it's using the right filesystem, run the command 'mount' from terminal. It'll give you a bunch of information, probably towards the bottom will be a line that mentions sdcard. Mine reads as
/dev/fuse /storage/sdcard0 fuse [more info about how it's currently mounted]
Yours -should- say that if you're on JB. If you're not, it should say something instead of /storage/sdcard0 (maybe /mnt/sdcard? I forget how it was on ICS). If it says something in place of fuse that may be the problem.
..I actually think mount used to say that the sdcard block was formatted as yaffs2, while everything else was formatted as ext4. Or maybe I just looked up that it was yaffs2 online, not from terminal on my phone? I wonder if this whole thing is the reason why some people seem bootloop-prone when flashing JB roms, if the changes have cut out access to important information about the filesystem, it may be triggering a really long error scan if their sdcard partition is large.
yes, backed up in ICS, and went to Jellybean.
doing a 'mount', I believe the line reads
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
The files that have the shield icon have permissions:
rw-rw-r--
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
JoeSyr said:
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
Click to expand...
Click to collapse
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
warlock257 said:
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
Click to expand...
Click to collapse
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
warlock257 said:
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
Click to expand...
Click to collapse
+1 This worked for me as well. Thanks for posting...:good:
Had the same problem. Deleting through the /media path worked.
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
+4 You Sir are a genius! Thanks given!
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Sorry to necro this thread almost 4 years later, but I had the exact same issue with deleting a folder on internal storage (Android Lollipop). Regardless if you're still here on XDA or not: thanks for this solution.
So.. Not really a I9250, but I guess my problem on i9100 is the same.
For some weird reason this just happened to WhatsApp directory.. But whatever.
After digging deeper and deeper in recovery, it seems like the folder wasn't own by media_rw group, but root
I just had to run
Code:
chown -R 1023:1023 <folder-path>
For some weird reason neither chown nor ls -l were correctly working when booted on normal system
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Click to expand...
Click to collapse
@Cilraaz, I have no idea if you're still on XDA but after at least a week of intense searching I found your advice which solved my problem! Thank you.
My problem was on i9500 (still) running stock Lollipop. I've been preparing to install a custom recovery, and did a TWRP (2.8.7.0) nandroid backup. Problem was I then couldn't find the TWRP backup folder. It would only show in TWRP's file manager. Root Browser didn't show it with SU privileges, nor ES File Browser and connecting it to the PC didn't help either. It's only after looking in /data/media/0 that I could find the TWRP folder.
Okay, so I updated my GSM Galaxy Nexus to the newest nightly of CyanogenMod and it ****ed things up royally, and I neglected to make a backup this time unfortuneatly.
I've tried flashing new ROMs ontop of it, but it doesn't fix the issue.
Right now my device boots, but shows a the home screen without any icons. I also have no navigation bar (app drawer/task manager/back button). Also, Trechbucket FC repeatedly. I can't find any of my files on the phone, even through adb, but when I go into settings and look under STORAGE and click photos, it shows me a gallery of all my photos.
Somehow my SD card is separated into /sdcard/0/ and /sdcard/legacy/ and my photos/downloads/everything is in legacy.
I've tried pulling using adp to grab all of my files, but it says the directory doesn't exist, (maybe I'm doing it wrong). I begun to try to pull the entire /sdcard/ and it did pull close to 2GB of audiobooks I had on there, but it was taking forever and I wanted to selectively pull photos/documents instead. I'm not even sure if I had let it continue if it'd have pulled my photos.
I type in adb pull /sdcard/DCIM /sdcard/ and it tells me that '/sdcard/DCIM' does not exist. I also tried /sdcard/DCIM/ and same thing.
Yet I can find it easily while in shell....
I think it's possible some of my files are hidden? I can use file explorer (by using Settings>Storage>audio>Explorer to see that all my files are under SDCARD/Legacy but I try to adb pull from that and it doesn't exist.
I'm really confused....
Any help either fixing my phone or pulling my data (which is on here) so I can erase/start clean?
I'd much appreciate your help.
Thanks.
A quick search in this forum of 'sdcard 4.2' will explain why this happens.
Anyway, fix is to use adb to pull /data/media (instead of /sdcard)
FriedSushi87 said:
Okay, so I updated my GSM Galaxy Nexus to the newest nightly of CyanogenMod and it ****ed things up royally, and I neglected to make a backup this time unfortuneatly.
I've tried flashing new ROMs ontop of it, but it doesn't fix the issue.
Right now my device boots, but shows a the home screen without any icons. I also have no navigation bar (app drawer/task manager/back button). Also, Trechbucket FC repeatedly. I can't find any of my files on the phone, even through adb, but when I go into settings and look under STORAGE and click photos, it shows me a gallery of all my photos.
Somehow my SD card is separated into /sdcard/0/ and /sdcard/legacy/ and my photos/downloads/everything is in legacy.
I've tried pulling using adp to grab all of my files, but it says the directory doesn't exist, (maybe I'm doing it wrong). I begun to try to pull the entire /sdcard/ and it did pull close to 2GB of audiobooks I had on there, but it was taking forever and I wanted to selectively pull photos/documents instead. I'm not even sure if I had let it continue if it'd have pulled my photos.
I type in adb pull /sdcard/DCIM /sdcard/ and it tells me that '/sdcard/DCIM' does not exist. I also tried /sdcard/DCIM/ and same thing.
Yet I can find it easily while in shell....
I think it's possible some of my files are hidden? I can use file explorer (by using Settings>Storage>audio>Explorer to see that all my files are under SDCARD/Legacy but I try to adb pull from that and it doesn't exist.
I'm really confused....
Any help either fixing my phone or pulling my data (which is on here) so I can erase/start clean?
I'd much appreciate your help.
Thanks.
Click to expand...
Click to collapse
i had this problem and thought I broke my SD card. But after a little exploring I found that Android 4.2 uses a new mounting point for SD card. My old SD card content was in /data/media, new sdcard content is in /data/media/0
I would recommend you either use adb or use terminal emulator to move your old files back to the new location. If you choose to use a file manager to do this, most likely it will be quite slow. I am assuming terminal emulator only does a low level dir path change while a file manager does an actual copy/move
Sent from my Galaxy Nexus using xda premium
DZYR said:
A quick search in this forum of 'sdcard 4.2' will explain why this happens.
Anyway, fix is to use adb to pull /data/media (instead of /sdcard)
Click to expand...
Click to collapse
Thanks so much. That did the job. Now I've just got a weird /0/ directory with everything in it.
coferjinelong said:
i had this problem and thought I broke my SD card. But after a little exploring I found that Android 4.2 uses a new mounting point for SD card. My old SD card content was in /data/media, new sdcard content is in /data/media/0
I would recommend you either use adb or use terminal emulator to move your old files back to the new location. If you choose to use a file manager to do this, most likely it will be quite slow. I am assuming terminal emulator only does a low level dir path change while a file manager does an actual copy/move
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I used ADB because I couldn't access terminal emulator because the phone had a botched update and wasn't working properly.
All's good now except for the fact that I've lost all my text messages..... and stuff...