Related
When i download and install an App from the Android Market where the Apk installation file is temporary placed? Which path?
tnx in advance
the apk's are stored at /data/app and /data/app-private after you installed the app and will be removed if you uninstall it.
Tnx for the answer mopodo, but if i hard reset the device, can i will use theese files to reinstall them?
i'm sorry for my bad english...
sidvizioso said:
Tnx for the answer mopodo, but if i hard reset the device, can i will use theese files to reinstall them?
i'm sorry for my bad english...
Click to expand...
Click to collapse
No, you can make a backup to your SD card with apps like MyBackup or Backup For Root Users.
So which is the temp path of the downloaded apk from market?
i want to grab them...
Pinesal said:
No, you can make a backup to your SD card with apps like MyBackup or Backup For Root Users.
Click to expand...
Click to collapse
of course you can.
you just have to copy them to your sdcard or pc an install them again, with «adb install something.apk» or «Astro File Manager» (or a similar file managerapp)
a hard reset will delete everything on «/data»
If you have root copy the contents of both folders to your SD card.
mkdir /sdcard/apps
cp /data/app/* /sdcard/apps
cp /data/app-private/* /sdcard/apps
Then after you wipe (I've never heard anyone call it a 'hard reset' before) you can use an app like Astore or ApkInstaller to reinstall them.
If you don't have root then not only will you not be able to read app-private, but your ROM wont have busybox so you wont be able to bash in those commands. In that case use an app like Astro or AppManager to copy non-private apks to the sdcard, but for private apps you'll have to redownload them (without being charged of course.)
Pinesal said:
No, you can make a backup to your SD card with apps like MyBackup or Backup For Root Users.
Click to expand...
Click to collapse
Only if they're non-private (reside in /app, private being /app-private).
He's probably coming from WinMo. We called a factory reset/wipe a hard reset.
mopodo said:
the apk's are stored at /data/app and /data/app-private after you installed the app and will be removed if you uninstall it.
Click to expand...
Click to collapse
Slightly off topic lol But i see you said Private does that mean you could manually back up Private apps you buy off market by just copying them /w root access?
When I run the following from an adb shell, with or without SU root:
cp /data/app/* <my location on sd>
I always get:
cp: permission denied
In fact, no matter how or where I cp from or to, and no matter what I am trying to copy, even if I leave all arguments blank, I still get "cp: permission denied" -- I have busybox installed in /system/xbin from /data/local and as far as I can tell it installed ok. Phone is a rooted Sprint hero 1.56.651.2 running stock ROM.
I have also tried to 'adb pull /data/app' and it always find 0 files. None of this is a big deal for me, however, as I am just trying to backup a bunch of apks for free apps in case versions change too much. Mostly just curious...
Any ideas?
EDIT: Both Astro and AppManager handled the (non-private) apk backups fine -- so I have no real need for the cp method to work, but I am still wondering why it will not -- is it the adb shell? must I use a terminal emulator from on the phone instead? something else? Anyways, if I really want to pursue it, perhaps I should take it to a busybox thread at this point...
EDIT2: It appears as if the 'cp' command as I was running it wasn't getting passed through busybox (not sure why). From what I can piece together reading other threads, it seems that if you have installed busybox on top of a ROM that doesn't already have it (like stock, after rooting and recovery setup) than you must prefix commands with 'busybox' when entered, as in 'busybox cp /data/app/* <my location>' and it does work for me that way. Still cannot seem to copy /data/app-private which I thought having root access would allow -- I guess I just don't understand nearly enough about busybox implementation, linux permissions, and, well, linux in general.
You could try an app manager and back 'em up from there.
Just try the following command.
busybox cp /data/app/* /sdcard/<your backup loc>
askwhy said:
When I run the following from an adb shell, with or without SU root:
cp /data/app/* <my location on sd>
I always get:
cp: permission denied
In fact, no matter how or where I cp from or to, and no matter what I am trying to copy, even if I leave all arguments blank, I still get "cp: permission denied" -- I have busybox installed in /system/xbin from /data/local and as far as I can tell it installed ok. Phone is a rooted Sprint hero 1.56.651.2 running stock ROM.
I have also tried to 'adb pull /data/app' and it always find 0 files. None of this is a big deal for me, however, as I am just trying to backup a bunch of apks for free apps in case versions change too much. Mostly just curious...
Any ideas?
EDIT: Both Astro and AppManager handled the (non-private) apk backups fine -- so I have no real need for the cp method to work, but I am still wondering why it will not -- is it the adb shell? must I use a terminal emulator from on the phone instead? something else? Anyways, if I really want to pursue it, perhaps I should take it to a busybox thread at this point...
EDIT2: It appears as if the 'cp' command as I was running it wasn't getting passed through busybox (not sure why). From what I can piece together reading other threads, it seems that if you have installed busybox on top of a ROM that doesn't already have it (like stock, after rooting and recovery setup) than you must prefix commands with 'busybox' when entered, as in 'busybox cp /data/app/* <my location>' and it does work for me that way. Still cannot seem to copy /data/app-private which I thought having root access would allow -- I guess I just don't understand nearly enough about busybox implementation, linux permissions, and, well, linux in general.
Click to expand...
Click to collapse
Well in windows
'adb pull' is used if that helps
So I just rooted a Glacier out of the box using VISIONary and gfree. Did everything exactly as was supposed to: temprooted, ran gfree, permrooted with "Set system r/w after root" checked, flashed engineering bootloader. Still running stock ROM.
Whenever I try to use adb remount, it fails saying "Operation not permitted." I want to use adb push to write to the file system, but I can't do that without the remount command.
I've tried using terminal emulator to copy a file from the sd card and failed:
Code:
$ su
# cd /sdcard
# cp -f hosts /system/etc
cp: cannot create '/system/etc/hosts':File exists
I've also tried outright deleting a file and failed:
Code:
# cd /system/etc
# rm hosts
rm failed for hosts, Read-only file system
I'm stupefied.
jdkoren said:
So I just rooted a Glacier out of the box using VISIONary and gfree. Did everything exactly as was supposed to: temprooted, ran gfree, permrooted with "Set system r/w after root" checked, flashed engineering bootloader. Still running stock ROM.
Whenever I try to use adb remount, it fails saying "Operation not permitted." I want to use adb push to write to the file system, but I can't do that without the remount command.
I've tried using terminal emulator to copy a file from the sd card and failed:
Code:
$ su
# cd /sdcard
# cp -f hosts /system/etc
cp: cannot create '/system/etc/hosts':File exists
I've also tried outright deleting a file and failed:
Code:
# cd /system/etc
# rm hosts
rm failed for hosts, Read-only file system
I'm stupefied.
Click to expand...
Click to collapse
To be sure you could download a root explorer and see if you can mount R/W
Sent from my HTC Glacier using XDA Premium App
Is there a free application that does this?
Unfortunately, I won't have access to it for the next few days (someone else's phone, and he's going out of town).
the stock rom doesn't except the remount command.
I believe that astro has the remount ability in it. You might want to consider flashing a custom rom though, even if its one of the stock based ones.
option94 said:
the stock rom doesn't accept the remount command.
I believe that astro has the remount ability in it. You might want to consider flashing a custom rom though, even if its one of the stock based ones.
Click to expand...
Click to collapse
I see, thanks very much for the explanation. Is that also why the terminal commands didn't work? Does the stock ROM not allow r/w permissions even if you have superuser permission?
Since it's not my phone, I didn't flash a ROM, only ClockworkMod recovery 3.0.0.6. Next time I see him I'll ask whether he wants to do any firmware changes or not.
jdkoren said:
I see, thanks very much for the explanation. Is that also why the terminal commands didn't work? Does the stock ROM not allow r/w permissions even if you have superuser permission?
Since it's not my phone, I didn't flash a ROM, only ClockworkMod recovery 3.0.0.6. Next time I see him I'll ask whether he wants to do any firmware changes or not.
Click to expand...
Click to collapse
That's correct... I think. all I know is that the stock Rom doesn't usually play well with root lol so yes flash a custom rom
Sent from my HTC Glacier using XDA Premium App
You can make the stock rom rw, but its a pain and I dont really remember the command. Its something like
Code:
mount -o,rw remount /dev/block/mmcblk0p25 /system
That may br right, but if not it wont do any damage. just give you a syntax error.
option94 said:
You can make the stock rom rw, but its a pain and I dont really remember the command. Its something like
Code:
mount -o,rw remount /dev/block/mmcblk0p25 /system
That may b right, but if not it wont do any damage. just give you a syntax error.
Click to expand...
Click to collapse
Ah yes, I remember using that once before. I've since forgotten it since I never use it with my own phone. Alrighty, I'll mark this as answered.
hi, developers!
it's so urgent if anyone knows how to do this please instruct me, infinitive thanks here in the first place!
i need to pull the directory of /data out to my PC，i'm rooted and able to use adb for this only,
first i use the command line
---------------------------------
adb pull /data(enter)
---------------------------------
The result is
---------------------------------
0 files pulled ,0 files skipped..
---------------------------------
then i tried the following command line
---------------------------------
adb shell(enter)
su(enter)
cd data(enter)
cd data(enter)
ll(enter)
---------------------------------
ok，it's not empty! everything I need is here,and ACCESSIBLE...for sure!
then i exited the adb shell mode and pulled again, but pulled nothing...
alright i went back to adb shell mode with su and tried
---------------------------------
chmod 777 /data(enter *no sign to show if this worked)
---------------------------------
then do the same pulling thing but again, didn't make any sense.
i also tried "cp" the files in /data i need, but only to find they're copied to local storage rather than my PC.
NOW COMES THE QUESTION:
is there any way i can directly gain privilege to pull files from /data,
or is there another way to backup /data to PC?
THE SITUATION IS
i've got a boot up problem, just can't pass through the bootanimation, before I reflash the pad, i'll need to retrieve crucial agenda notes and memo lest they're wiped.
but the recovery backup function failed to back up userdata...(/data)
Just a hunch, but can you (using adb shell and SU) cp /data to /mnt/external_sd, then pull it from there or use a card reader?
stuck
p_025 said:
Just a hunch, but can you (using adb shell and SU) cp /data to /mnt/external_sd, then pull it from there or use a card reader?
Click to expand...
Click to collapse
thank you pal! i've tried such thing as you remind me of but totally, /data is omitted! while i use "cp", for another thing, while i was trying to "cp" another folder to extern sd, it read read-only file system. so it goes all the way back to the PERMISSION thing, or i need to gain privilege to modify the property of /data so that i can pull what i need out of this nightmare...and should modify /external sd also if using "cp".
kept waiting, please help:crying:..any constructive instructions shall be greatly appreciated!!
yours truly cordially!!
can u actually use adb without access to the os??
what rom and BL were u on?
seems strange u need permissions for /data - have u tried mounting it?
from memory data resides at mmcblk0p8 u might be able to dd that 2 ur ext SD or Google to search dev forum
I'm know dev just throwing stuff o.to.tje
mix...
Sent from my GT-I9300 using Tapatalk 2
I tried today to upgrade from 4.1.2 to 4.2.2 but it failed about 30% of the way through the upgrade and ended with the Droid on his back with a red x.
Its rooted but got stock recovery.
I did the same upgrade for my Nexus 4 to 4.2.2 from 4.2.1 and that upgraded fine.
What's causing the upgrade to fail?
Any help would be much appreciated.
Thanks
Jon
Sent from my Nexus 7 using XDA Premium HD app
look for the error message in /cache/recovery/recovery.log
If you comb thru the bigger threads on the 4.2.2 update....every imaginable problem and solutions are in there.
Sent from my cell phone telephone....
This is part of the log that shows the failure.
Any help would be much appreciated.
Thanks
Verifying current system...
failed to stat "/system/xbin/bttest": No such file or directory
file "/system/xbin/bttest" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/xbin/bttest", "07168ec97de36a7cca8b6867ad66937c6c6c1f4d", "2bb363a3f434d165d1167d915c2ba44967e22071")
assert failed: apply_patch_check("/system/xbin/bttest", "07168ec97de36a7cca8b6867ad66937c6c6c1f4d", "2bb363a3f434d165d1167d915c2ba44967e22071")
E:Error in /cache/da55f917feee.signed-nakasi-JDQ39-from-JZO54K.da55f917.zip
Sent from my Nexus 7 using XDA Premium HD app
OK jonchill I will try to help out.
But only because you inadvertently disclosed a new OTA download (JZO54K->JDQ39) for nakasi.
Here's the deal:
The OTA process performs checksums on hundreds of individual files (and even partitions e.g. boot partition) before it begins any work. 100% of checksums must pass before anything gets changed by the OTA.
It's a safety feature meant to protect people from applying the wrong files to their tablets/phones. More importantly, the reason that it is done is because the OTA does not contain "replacement" files - it only has small binary "patch" files which can be used only in conjunction with the original file to create the intended replacement file. This is how OTAs can be so much smaller than a full ROM - the files already present are "patched" to create their replacements.
But the bottom line is that if *you* removed or altered any single file which is a target of the OTA patching process, these pre-installation checks will fail. (Even worse, it stops immediately - it is possible that you have more than one file involved in this. Because of this stop-on-first-fail behavior, you don't know yet whether or not there are more to come.)
When I say *you* I mean you personally plus any root-using apps which you installed and ran on your tablet. Could have been an app.
OK, now for the good news. I downloaded the OTA - thanks for providing the file name - and looked at the installer script; that installer script for JZO54K-> JDQ39 is shown here on pastebin. The file which your OTA is complaining about is "bttest" - and as it turns out, this check occurs on line 1040 - it is the third from last file checked. The only thing which comes after that is a check of
/system/xbin/dexdump
and
the boot partition ( EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX )
Now I don't have any idea what might have caused "bttest" to disappear from your ROM. On the off-chance that "dexdump" got deleted too, attached is a zip of those two files from the JZO54K distro.
This is not a flashable zip - it's just the two files. It's your responsibility to get them into /system/xbin/
Note their ownership info:
Code:
-rwxr-xr-x 1 root 2000 5448 Oct 2 14:49 /system/xbin/bttest
-rwxr-xr-x 1 root 2000 59828 Oct 2 14:49 /system/xbin/dexdump
If you restore them to /system/xbin/ make sure you
Code:
chown 0.2000 /system/xbin/bttest /system/xbin/dexdump
chmod 755 /system/xbin/bttest /system/xbin/dexdump
I verified their SHA1 checksums (note these are the 2nd string of digits in the failing assert_check).
2bb363a3f434d165d1167d915c2ba44967e22071 bttest
e5e4d35038ed3e32a15194275806d90e64e003c6 dexdump
good luck.
I've downloaded the files and tried transferring them across to XBIN but it fails saying the folder isn't writable, I've tried changing the permissions on the folder but it errors saying can't set permissions.
What am I doing wrong?
Thanks
The /system partition is typically mounted "ro" - Read Only.
Root-aware file browsers typically have a toggle in their (root-related) menu to remount /system in rw mode, but you can easily do it yourself from the command line. (using a terminal emulator or adb). You just need to be root to do this. (Or you can just do everything in the custom recovery, in which case the /system mount point will be in "rw" mode by default)
C:\foo> adb shell
$ su
# mount -o remount,rw /system
(copy files into place, do chmods , etc)
# mount -o remount,ro /system
Just tried a you suggested and it doesn't seem to want to put the system into RW. I've also tried changing the permissions through the file manager I've got installed and get the same result.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Read-only file system
255|[email protected]:/ #
Thanks
jonchill said:
Just tried a you suggested and it doesn't seem to want to put the system into RW. I've also tried changing the permissions through the file manager I've got installed and get the same result.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Read-only file system
255|[email protected]:/ #
Thanks
Click to expand...
Click to collapse
Well, that's odd. I'm not really sure why that is happening. You could fool around with the mount command a little bit or just avoid all this nonsense and do what you need via adb in the custom recovery.
If your bootloader is unlocked, but you don't want to *flash* a custom recovery (I see you said you have stock recovery), you can nevertheless temporarily *boot* one, and just that temporarily booted custom recovery as in:
- put device in bootloader mode
C:\fubar> fastboot boot name-of-custom-recovery-image.img
(wait until it is booted)
C:\fubar> adb shell
# mount /system
# cp /sdcard/wherever/bttest /system/xbin/bttest
# cp /sdcard/wherever/dexdump /system/xbin/bttest
# chown 0.2000 /system/xbin/bttest /system/xbin/dexdump
# chmod 755 /system/xbin/bttest /system/xbin/dexdump
# sync
# umount /system
reboot
I don't know how you originally rooted, but generally the adb connection from either custom recovery (TWRP/CWM) needs an additional USB driver (yes, even though you "already have ADB working with the normal OS"). I suppose most lazy folks use either a toolkit or the XDA Universal Naked driver for this. (No support will be given by me on driver installs - I need to draw the line someplace.)
good luck
Tried booting to a temp custom recovery (TWRP) and followed your instructions but still getting the Read-Only file system. At this stage would it be better to take a backup and re-flash a full image?
C:\NRT\data>adb shell
~ # ←[6n
~ # ←[6nmount /system
mount /system
~ # ←[6ncp /sdcard/bttest /system/xbin/bttest
cp /sdcard/bttest /system/xbin/bttest
cp: can't create '/system/xbin/bttest': I/O error
~ # ←[6ncp /sdcard/dexdump /system/xbin/dexdump
cp /sdcard/dexdump /system/xbin/dexdump
cp: can't create '/system/xbin/dexdump': Read-only file system
Thanks
Well that is bizarre.
Some boot kernel/ramdisk configurations use a "errors=remount-ro" mount option with ext4 filesystem that automatically prevents a "rw" mount if corruption was detected in the ext4 filesystem meta-data.
Although when the mount of /system succeeds in 4.2.2 stock I don't see that - this is what you get:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
I also don't see that option in use with TWRP 2.4.1.0 either:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/mmcblk0p3 /system ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
It's just a hypothesis - but perhaps somehow your /system partition got damaged?
I am reluctant to continue giving advice since your device is behaving non-nominally. (I never used JZO54K, so I can't say for sure.)
It is possible that doing a dirty overflash of factory 4.2.2 (of only the boot partition & system partition) via fastboot would succeed, but I would feel a lot more comfortable about doing that in the sequence JOP40C->JOP40D->JDQ39 where you are converting a 4.2.x ROM to a later version. In your case though, coming from a 4.1.x ROM (JZO54K), that seems like there could be downstream problems.
The conservative route would be to take as many backups as you feel are appropriate, e.g. Nandroid + TiBu or Carbon, reinstall the full factory 4.2.2 stock (including bootloader!), re-root, and then restore your market apps & data (TiBu or Carbon). Note that because we have no idea what the changes/bug fixes were in the 4.18 bootloader update, you probably want to make sure you install the 4.18 bootloader first (and make sure to reboot to it!) before doing any of the subsequent steps (partition erasures & formatting, in particular).
I wouldn't do anything at all, though until I had succeeded making a full Nandroid backup and making sure I had a copy of it off of the tablet. Do your Nandroid backups succeed?
bftb0 said:
Well that is bizarre.
Some boot kernel/ramdisk configurations use a "errors=remount-ro" mount option with ext4 filesystem that automatically prevents a "rw" mount if corruption was detected in the ext4 filesystem meta-data.
Although when the mount of /system succeeds in 4.2.2 stock I don't see that - this is what you get:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
I also don't see that option in use with TWRP 2.4.1.0 either:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/mmcblk0p3 /system ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
It's just a hypothesis - but perhaps somehow your /system partition got damaged?
I am reluctant to continue giving advice since your device is behaving non-nominally. (I never used JZO54K, so I can't say for sure.)
It is possible that doing a dirty overflash of factory 4.2.2 (of only the boot partition & system partition) via fastboot would succeed, but I would feel a lot more comfortable about doing that in the sequence JOP40C->JOP40D->JDQ39 where you are converting a 4.2.x ROM to a later version. In your case though, coming from a 4.1.x ROM (JZO54K), that seems like there could be downstream problems.
The conservative route would be to take as many backups as you feel are appropriate, e.g. Nandroid + TiBu or Carbon, reinstall the full factory 4.2.2 stock (including bootloader!), re-root, and then restore your market apps & data (TiBu or Carbon). Note that because we have no idea what the changes/bug fixes were in the 4.18 bootloader update, you probably want to make sure you install the 4.18 bootloader first (and make sure to reboot to it!) before doing any of the subsequent steps (partition erasures & formatting, in particular).
I wouldn't do anything at all, though until I had succeeded making a full Nandroid backup and making sure I had a copy of it off of the tablet. Do your Nandroid backups succeed?
Click to expand...
Click to collapse
Thanks for all your help, as this is going to be quite a bit more complex than first thought I'm going to leave the above until I come back from holiday.
Thanks again.
You can always tell when there's a technical guru around... they use wonderful phrases like "...since your device is behaving non-nominally...".
bftb0, your posts, as ever, continue to be hugely informative and a delight to read...
----------
Hi, jonchill... (when you return from your holiday)...
Here's what I would try...
When I'm poking around in /system (usually for something more prosaic, like changing the BOOTANIMATION.ZIP), I use X-Plore File Manager (http://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en).
It's a ROOT capable DUAL pane file manager... so you should be able to copy the files directly into /SYSTEM/XBIN (setting one pane as your SOURCE, the other as your DESTINATION TARGET).
Once copied there, LONG PRESS on the respective files just copied, select PERMISSIONs from the context menu that appears, and set accordingly.
But first, you will have to go into CONFIGURATION>ROOT ACCESS and set X-Plore File Manager to SUPERUSER+MOUNT WRITABLE...
I have both these files (bttest and dexdump) in my xbin folder... and permissions for both are 755.
See my screenshots appended to this post.
Hope this helps...
Rgrds,
Ged.
-----------
PS. where did you get the OTA updater ZIP nakasi-JDQ39-from-JZO54K.da55f917.zip from? I've Googled around for it, but can't find it anywhere. Would be nice to have it in my collection.
GedBlake said:
You can always tell when there's a technical guru around... they use wonderful phrases like "...since your device is behaving non-nominally...".
bftb0, your posts, as ever, continue to be hugely informative and a delight to read...
----------
Hi, jonchill... (when you return from your holiday)...
Here's what I would try...
When I'm poking around in /system (usually for something more prosaic, like changing the BOOTANIMATION.ZIP), I use X-Plore File Manager (http://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en).
It's a ROOT capable DUAL pane file manager... so you should be able to copy the files directly into /SYSTEM/XBIN (setting one pane as your SOURCE, the other as your DESTINATION TARGET).
Once copied there, LONG PRESS on the respective files just copied, select PERMISSIONs from the context menu that appears, and set accordingly.
But first, you will have to go into CONFIGURATION>ROOT ACCESS and set X-Plore File Manager to SUPERUSER+MOUNT WRITABLE...
I have both these files (bttest and dexdump) in my xbin folder... and permissions for both are 755.
See my screenshots appended to this post.
Hope this helps...
Rgrds,
Ged.
-----------
PS. where did you get the OTA updater ZIP nakasi-JDQ39-from-JZO54K.da55f917.zip from? I've Googled around for it, but can't find it anywhere. Would be nice to have it in my collection.
Click to expand...
Click to collapse
Ged
The OTA was what I received automatically.
I've already got XPlore and have tried what you suggested but get Can't write to file /system/xbin/bttest can't move temp file to /system/xbin/bttest.
Thanks
So, before I do a firmware update (In this case 4.2.2 to 4.3 OTA) I do a Titanium backup and a TWRP backup and copy both sets of backup files to my PC; it obviously makes no sense to only have backups on the device you are backing up. I upgraded to TWRP 2.6.0.0, did a full backup, and as usual I went to copy my backup files over to my Windows 7 computer using Windows Explorer and I can only get a couple of the files to move over. No warning, no error, no nuttin. This has always worked before......Did something change, and if so, how do I fix it?
I see from another post that TWRP changed the permissions of the backup files in the latest version of the program, and in my case the location as well. The workaround is to a) change the permissions on all those backup files, which I could see the nightmare problems that could cause later on when doing a restore and/or the security issues or b) doing an adb pull.
SOLVED.
The adb pull did the trick. All files were transferred over to my PC.
I had several issues getting adb to work:
1) I had an old version of the SDK installed on my PC which was causing a devices not recognized problem or something similar.
2) I didn't notice the message about verifying the RSA on my phone, which once verified, fixed the phone "offline" problem.
3) The screen lock on my phone was coming on after its timeout and locking me out from seeing the phone.
reverted to twrp 2.5.0.0
Same problem here with Google Nexus i9250 / twrp 2.6.0.0 / win7 64bit. Tried to copy backup of (BOOT/SYSTEM/DATA) via MTP or ftp from Nexus to PC. Only the first two files (boot.emmc.win/-md5) were copied. After downgrading to twrp 2.5.0.0 everthing was fine.
I had the same problem. It is caused by strange suid permissions set by TWRP. Solved it using chmod 0664 /data/media/0/TWRP/... (as root)
I was not able to adb pull before changing the files' permissions.
More details here:
http://forum.xda-developers.com/showpost.php?p=44120545&postcount=14
(Google found that HTC One thread first, so I didn't search any further)
Type this in Terminal Emulator:
su
busybox chown - R 1023.1023 /data/media/*
That should solve all permissions problems.
I had no trouble at all by doing the following:
Access the sdcard from /data/media/0
Copy data.ext4.win and system.ext4.win to a temporary location.
(The "Set UID" and "Set GID" permissions were automatically removed. If not, you can change them from here.)
Copy the files to PC using MTP.
The remaining backup files from the TWRP directory can be copied normally.
Done
Note: You can instead just change the permissions on these two files inside the TWRP directory, but I did the temporary location copy just to be safe.
Mercado_Negro said:
Type this in Terminal Emulator:
su
busybox chown - R 1013.1023 /data/media/*
That should solve all permissions problems.
Click to expand...
Click to collapse
coming up with chown: unknown user -
is that a space between 1023 and /data?
daryllh said:
coming up with chown: unknown user -
is that a space between 1023 and /data?
Click to expand...
Click to collapse
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Mercado_Negro said:
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Click to expand...
Click to collapse
After I did this command, my pc can't detect the back up
handols said:
After I did this command, my pc can't detect the back up
Click to expand...
Click to collapse
Did you plug/unplug your device after running this command? There shouldn't be any problems. Furthermore, now you should be able to copy your TWRP and TiBu backups successfully to your computer. It's a pretty straight forward process.
Im on twrp 2.5.0.0 with Android 4.3. I cant copy the BACKUP folder directly to my PC with the default windows explorer because the backup isnt stored in /sdcard/TWRP. How can I fix this? I used to be able to do this without adb push/pull...
Mercado_Negro said:
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Click to expand...
Click to collapse
Thanks for this. I'm able to backup TWRP folder to PC now :highfive:
Since my original post 3 months ago I updated all my programs to 4.3 friendly versions as each was released (superuser 1.0.2.1, Windows drivers, TWRP 2.6.3.0, etc.) and now I don't need to do adb pulls any more and I can just copy and paste files from my phone to my pc and all files are copied over without missing any of them. Now I see the updated programs are already starting to show up for Android 4.4; here we go again.
Now see 0 / legacy emulated
Mercado_Negro said:
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Click to expand...
Click to collapse
Hi just wondering, Is there a way to cancel this command (just add a +R maybe) I did it on my phone and I think it may be the cause that I have a Legacy emulated 0 path problem Ive searched around and cant seem to find a solution. Thanks
NightCrawler504 said:
Hi just wondering, Is there a way to cancel this command (just add a +R maybe) I did it on my phone and I think it may be the cause that I have a Legacy emulated 0 path problem Ive searched around and cant seem to find a solution. Thanks
Click to expand...
Click to collapse
What's the problem? That's a valid path.
Legacy emulated 0
Mercado_Negro said:
What's the problem? That's a valid path.
Click to expand...
Click to collapse
I have an external sd (sdcard1) = /storage/sdcard1 so gr8 but then I have emulated (??) Storage/emulated/legacy and Storage/emulated/0 and sdcard0 storage/sdcard0 they were complety different folders been reading around seems to be a problem with cm when I go from 4.2 and over my phone is a e970 att, cant delete the emulated folder... already erased all my data previously, any help will do,I'm almost sure it had nothing to do with the chown command but had to give a try.
NightCrawler504 said:
I have an external sd (sdcard1) = /storage/sdcard1 so gr8 but then I have emulated (??) Storage/emulated/legacy and Storage/emulated/0 and sdcard0 storage/sdcard0 they were complety different folders been reading around seems to be a problem with cm when I go from 4.2 and over my phone is a e970 att, cant delete the emulated folder... already erased all my data previously, any help will do,I'm almost sure it had nothing to do with the chown command but had to give a try.
Click to expand...
Click to collapse
No, it doesn't have anything to do with this command since it's just a way to set different permissions.