Database Users

Rooted Hero Fails adb remount, can't move files from SD

I rooted my hero last night and tried out a few different ROMs but eventually decided to revert to stock and make some manual changes. I used nandroid to restore to just after the root (1.56.651.2). I was able to remove some apps using adb, but the adb remount command fails (permission denied), and I'm unable to push a new bootscreen on to the phone. I also tried a Root File Manager and pre-kitchen as alternatives for the bootscreen, and neither one works. The Root Manager won't paste the files from SD into /system/media/ and pre-kitchen just reboots the phone.
Any suggestions?

Any chance this has something to do with downloading only up to SDK Platform 1.5? I'm at a total loss. I RUU'd my phone, did a clean root at startup using adb shell, and I still have the same problem. The adb remount command won't work, and I can't push anything into the system directory. For what it's worth, when I still had Root Manager installed I was able to toggle RO R/W in any directory with no problem, and I could move files around within the ROM... but I couldn't move anything into it from the SD. I'm new at this, so I have no idea what the problem might be. Anyone else had this problem or have any suggestions?

If anyone else runs into this problem, this solution worked for me:
adb shell
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system (Or any subdirectory you want to push to inside system)
# exit
adb push <local file> <device location>
Restore modified permissions when done.
Though I'm still not sure why this is necessary in place of adb remount.

I'm pretty sure the adb remount command will not work on the stock rom. You should be able to do it with just this command instead:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

dametzg said:
I'm pretty sure the adb remount command will not work on the stock rom. You should be able to do it with just this command instead:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Thanks... didn't realize stock wouldn't accept adb remount. If I use the above line from within shell, that doesn't help me push anything on to the phone though... so I needed to enable global permission and then do the push. Oddly enough I tried the same approach last night using Root Manager, and the transfer from SD still failed, even after I applied 777 to the dir I was trying to modify. The current solution may be kind of tedious, but at least it works.

you really shouldn't do 777 on your filesystem, ANY app can then write to your system, overwrite things, or install malicious code. Just remount manually and you should be able to push anything you want, just remember that w/ the stock rom you also don't get a full busybox either.

I'm not positive, but I would think after you remount, you should be able to "adb push" to /system. I suppose it might be specific to that shell, but I would think not.
You just may have to do it once each time you boot your phone.
Edit - err nevermind... you're having permission errors.... um... change adbd on the phone to run as root? not sure how off the top of my head...

A little guidance please (delete permissions, etc.)

(Sorry for not posting actual links - the system won't let me because I'm still a "new user.")
I already rooted my Sprint Hero using this (thread 583291) guide and can successfully tether using the WiFi Tether app. Yay!
Now I want to delete and/or replace the boot up sound (boot.mp3 located in /system/media/bootscreen) When I try to delete it right now (either through adb shell on my computer or from within a file manager app on the phone itself) I get permission denied or "read-only file system."
I see two threads regarding busybox, superuser, and adb remount. Thread 591303 which is dated 11/28/09 and is just for busybox and Thread 593952 which is dated 12/03/09.
I'm not sure which of these two I need to install. If it's the latter which includes ADB remount and superuser as well as busybox, then I'm not sure if I am supposed to unzip them before pushing them to my phone.
Could anyone point me in the right direction based on what I want to do (delete files on my phone - ANY file I want)?
Thanks in advance for any help you can offer.

All you should need to do is:
Code:
adb remount
rm /insert file path/file
So yours would be
Code:
rm /system/media/bootscreen/boot.mp3

Mr. Biggz said:
All you should need to do is:
Code:
adb remount
rm /insert file path/file
So yours would be
Code:
rm /system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
will rm work without busybox?

As long as you can shell into the phone it should work. The rm command is to be run inside the shell.
So it actually should be
Code:
adb remount
adb shell
rm /system/media/bootscreen/boot.mp3

You want to install the busybox remount and superuser Rom if you want to run stock.
Or manually install busybox, superuser whitelist and adb remount
Biggz - looks like they are on stock. No adb remount.

gbhil said:
Biggz - looks like they are on stock. No adb remount.
Click to expand...
Click to collapse
Unfortunate, custom is so much better.

If you are on stock, do this:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mv /system/media/bootscreen/boot.mp3 /system/media/bootscreen/boot.mp3.old
exit
[you can also do rm /system/media/bootscreen/boot.mp3 instead]

gbhil said:
You want to install the busybox remount and superuser Rom if you want to run stock.
Or manually install busybox, superuser whitelist and adb remount
Biggz - looks like they are on stock. No adb remount.
Click to expand...
Click to collapse
successfully removed (rm) the boot.mp3 in the shell - Thank you for that. I do want to replace it with a different one (I'll use the same file name since the .xml file still refers to it) so I'll need the cp command and I've noticed that it's missing in shell. I'm assuming I need to install busybox to get this functionality. I'm not really sure I want to install a complete new ROM and I don't mind manually installing busybox, adb remount, etc. What does installing "superuser whitelist" and "adb remount" allow me to do? I'm not sure what their potential uses are?

I installed busybox and have the cp command functionality now (see above post) but now when I try to copy anything to the /system/media/bootscreen folder I get "cp: cannot create '/system/media/bootscreen/boot.mp3': Permission denied"
I type "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" after getting into shell and typing "su" and getting the "#" prompt and it takes successfully (this is the only way I was able to actually "rm" the original boot.mp3 file to begin with.
See anything I'm doing wrong?

Nope, that is correct.
/system is normally mounted as read-only, so you can't add or delete anything. The mount command remounts it as read-write, so you can modify it as root.

armyturtle said:
<snip> I'm not really sure I want to install a complete new ROM and I don't mind manually installing busybox, adb remount, etc. What does installing "superuser whitelist" and "adb remount" allow me to do? I'm not sure what their potential uses are?
Click to expand...
Click to collapse
Superuser whitelist is an application that warns you and asks for you to provide permission whenever an app tries to use the su binary to run as another user. You want this, as without it there's no way to know if an application runs as root.
Adb remount is a service that allows you to toggle the +RW bit on the /system/ partition through the shell. IIRC the one one floating around also kills color terminfo so you don't get all the extra chars on a windows PC when using the ls command. Just a matter of convenience.

jonnythan said:
Nope, that is correct.
/system is normally mounted as read-only, so you can't add or delete anything. The mount command remounts it as read-write, so you can modify it as root.
Click to expand...
Click to collapse
I can't create/copy anything after getting into the shell and remounting as read-write. From CMD prompt I type:
adb shell
and get:
$
Then I type:
su
and get:
#
This is where I type:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Then trying to copy anything into the /system directory gives me:
Permission denied
It will let me DELETE anything I want from this folder (as confirmed by now deleting boot.gif just to check) but it won't let me cp (copy) anything to this folder. WHY?
What the heck?

try these commands for the boot mp3
Code:
cd/
cd /androidsdk/tools/
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
adb push directoryonpcwhereyourbootmp3is /system/media/bootscreen/
make sure that you rename the mp3 to boot.mp3 or it wont work anyways.
the other option (this is what I do) is find a bootscreen that you like (I use this one). open the zip file useing winrar or 7zip, navigate into the files where you see the boot.mp3 and drag in YOUR (now renamed) boot.mp3 close the window, put the zip file onto the root of your sd card, boot into recovery, choose flash from zip, flash the file and your good to go.

wtphoto said:
try these commands for the boot mp3
Code:
cd/
cd /androidsdk/tools/
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
adb push directoryonpcwhereyourbootmp3is /system/media/bootscreen/
make sure that you rename the mp3 to boot.mp3 or it wont work anyways.
the other option (this is what I do) is find a bootscreen that you like (I use this one). open the zip file useing winrar or 7zip, navigate into the files where you see the boot.mp3 and drag in YOUR (now renamed) boot.mp3 close the window, put the zip file onto the root of your sd card, boot into recovery, choose flash from zip, flash the file and your good to go.
Click to expand...
Click to collapse
tried this just now and still get "failed to copy 'C:\android-sdk-windows\tools\boot.mp3' to '/system/media/bootscreen/boot.mp3': Permission denied"
It's the /system folder... I can push to /data/local all day long, but anything in the /system folder is read only. How the hell can I change this?

/system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
if this is the code you are using then that could be your issue
the code line should look like this
Code:
adb push C:\android-sdk-windows\tools\boot.mp3 /system/media/bootscreen/
doing adb push C:\android-sdk-windows\tools\boot.mp3 /system/media/bootscreen/boot.mp3 says that you are trying to push the boot.mp3 to the directory bott.mp3 and there is no boot.mp3 directory the folder where you want the boot.mp3 is bootscreen. try the ubove code and see what happenes.

wtphoto said:
if this is the code you are using then that could be your issue
the code line should look like this
Code:
adb push C:\android-sdk-windows\tools\boot.mp3 /system/media/bootscreen/
doing adb push C:\android-sdk-windows\tools\boot.mp3 /system/media/bootscreen/boot.mp3 says that you are trying to push the boot.mp3 to the directory bott.mp3 and there is no boot.mp3 directory the folder where you want the boot.mp3 is bootscreen. try the ubove code and see what happenes.
Click to expand...
Click to collapse
Nope, was a typo on my part (here in the post, not when issuing the command). Still permission denied. I don't think it's actually mounting the /system folder as writable. Is there a way to check after issuing the remount command?
A quick command of "ls -l" at root prompt gives the following for the /system folder:
drwxr-xr-x root root 2009-09-21 06:30 system

after you run the remount command what does it say? does it say remount succeded?

After typing the remount command it simply repeats my command back at me and returns to the "#" prompt.

honestly at this point what I would try doing is do a back up then flash a custom rom like fresh 1.1 that has all the tools built into it. then go into the cmd prompt and cd to where sdk is then type adb remount and see what it says then adb shell and try to cp the file to that directory.
this is more a test than anything else.

wtphoto said:
honestly at this point what I would try doing is do a back up then flash a custom rom like fresh 1.1 that has all the tools built into it. then go into the cmd prompt and cd to where sdk is then type adb remount and see what it says then adb shell and try to cp the file to that directory.
this is more a test than anything else.
Click to expand...
Click to collapse
I'll try this - so you recommend trying fresh 1.1 then? I know it's just a test, but just in case I like the ROM and decide to stick with it, might as well try a really good one! I'll try this tomorrow - I'm beat! (Thanks again!)

Problems with adb push

I am running custom rom Rooted 2.1 v0.3.
Ever since flashing to the custom rom, when i try to push a file, such as:
adb push bootanimation.zip /system/media
I get the error:
Failed to copy.... Read-only file system.
I didn't have this error before flashing to the rom. Does this have something to do with superuser whitelist?
I have tired:
mount -oremount,rw /dev/block/mtdblock3 /system
and it didn't work and I tired:
adb remount
winch returned:
Operation not permitted.
This is ticking me off since I didn't have this problem until flashing the rom.
EDIT: Now if I try:
adb push bootanimation.zip /system/media,
I get:
Permission denied.
This is crazy.

I need help also. Rooting for first time and trying to get recovery.img on and keep getting read only errors. Tried remount to no avail. Help please

su
mount -o rw,remount /Dev/block/mtdblock3 /system
file system is case sensitive!
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
p.s.
make sure you have developer mode enabled "settings" and accept su permissions. Also have BusyBox

fKngFtd said:
su
mount -o rw,remount /Dev/block/mtdblock3 /system
file system is case sensitive!
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
p.s.
make sure you have developer mode enabled "settings" and accept su permissions. Also have BusyBox
Click to expand...
Click to collapse
...it's a lowercase d in dev.
mount -o rw,remount /dev/block/mtdblock3 /system

n2imagination said:
I need help also. Rooting for first time and trying to get recovery.img on and keep getting read only errors. Tried remount to no avail. Help please
Click to expand...
Click to collapse
I had the same problem. From what I could tell, I had the wrong ADB driver somehow. So I downloaded the drivers from the HTC website and went to device manager (Win7) and updated the driver software which fixed the problem. But I think i just lucked out when i stumbled onto that, I feel a blind retard with epilepsy trying to draw a circle on an etch-a-sketch when I'm doing things like rooting. But, it couldn't hurt to try it.

fKngFtd said:
su
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
Click to expand...
Click to collapse
adb install -l whatever.apk (from tools dir in sdk)

`mods said:
I am running custom rom Rooted 2.1 v0.3.
Ever since flashing to the custom rom, when i try to push a file, such as:
adb push bootanimation.zip /system/media
I get the error:
Failed to copy.... Read-only file system.
I didn't have this error before flashing to the rom. Does this have something to do with superuser whitelist?
I have tired:
mount -oremount,rw /dev/block/mtdblock3 /system
and it didn't work and I tired:
adb remount
winch returned:
Operation not permitted.
This is ticking me off since I didn't have this problem until flashing the rom.
EDIT: Now if I try:
adb push bootanimation.zip /system/media,
I get:
Permission denied.
This is crazy.
Click to expand...
Click to collapse
Did you ever get this fixed? I have the same problem!

I have the same problem also. I've been using SDK just fine for over a month or two, and now that I'm on V3, no worky. Somethings obviously going on. But what?!

LexusBrian400 said:
I have the same problem also. I've been using SDK just fine for over a month or two, and now that I'm on V3, no worky. Somethings obviously going on. But what?!
Click to expand...
Click to collapse
I think the proper permissions were not set for this ROM. Hopefully jcase can modify the file and re-upload the ROM =)
at least that's what I've gathered... someone PLEASE correct me if I'm wrong
edit: I looked at the script file and it seems like rw permissions are set properly???
jcase - any insight?

I personally get a bunch of "Out of memory" errors when trying to follow the recovery walk-through.

post baleeted

please help

Alright im already rooted and i flashed clockwork recovery image and I want it gone. I'm trying to go back to Amons recovery image. However when im in the command and I type in adb push recovery-ra-eris.img /sdcard I get no such file or directory error... but i have the file in the tools folder of my androidsdk... any thoughts

fenwaynomar45 said:
Alright im already rooted and i flashed clockwork recovery image and I want it gone. I'm trying to go back to Amons recovery image. However when im in the command and I type in adb push recovery-ra-eris.img /sdcard I get no such file or directory error... but i have the file in the tools folder of my androidsdk... any thoughts
Click to expand...
Click to collapse
Dumb question, but I gotta ask it...
Are you running with the tools folder in your path, so you can execute adb commands from anywhere in the shell? Or are you actually *in* the tools directory as you run the command?
Either way, maybe you should try specifying the full path of recovery-ra-eris.img (as in C:\path\to\recovery-ra-eris.img or /path/to/recovery-ra-eris.img).

I have the tools directory open as im doing the command... i didnt have this problem last time i did this... so idk whats wrong

corrosivefrost said:
Dumb question, but I gotta ask it...
Are you running with the tools folder in your path, so you can execute adb commands from anywhere in the shell? Or are you actually *in* the tools directory as you run the command?
Either way, maybe you should try specifying the full path of recovery-ra-eris.img (as in C:\path\to\recovery-ra-eris.img or /path/to/recovery-ra-eris.img).
Click to expand...
Click to collapse
And isn't the correct version Recovery-RA-eris-v1.6.2?

I downloaded it and thats the recovery image im using but it saves as recovery when i zip it

getting really frustrated because i think I lost all my previous nandroid backups and stuff so im going to say what im doing exactly to fix it and someone tell me what im doing wrong ha. I have debuggin on. I'm mounted. I downloaded the flash image and recovery image from the unlockr website. I put the files in the tools of my androidsdk... i type these commands.
cd\
cd c:\AndroidSDK\tools
adb devices
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
After i do the recovery-ra-eris.img i get an error

fenwaynomar45 said:
getting really frustrated because i think I lost all my previous nandroid backups and stuff so im going to say what im doing exactly to fix it and someone tell me what im doing wrong ha. I have debuggin on. I'm mounted. I downloaded the flash image and recovery image from the unlockr website. I put the files in the tools of my androidsdk... i type these commands.
cd\
cd c:\AndroidSDK\tools
adb devices
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
After i do the recovery-ra-eris.img i get an error
Click to expand...
Click to collapse
Here are the steps I have used over and over, so try this. And I used this link for the recovery, so maybe download this one and give these commands and recovery a shot.
Download Link: http://www.sendspace.com/file/jje5xr
Extract file contents to your \tools\ directory of your Android SDK
Open up a command prompt and go to your tools directory, and execute these commands: (MAKE SURE YOUR SDCARD IS NOT MOUNTED TO YOUR COMPUTER OR THESE COMMANDS WON'T WORK! MAKE SURE IT IS ON "CHARGE ONLY")
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img

Type dir recovery-ra-eris.img in your c:\AndroidSDK\tools directory. If it comes back with nothing, then you actually put the file somewhere else (don't worry, happens to me from time to time).
fenwaynomar45 said:
getting really frustrated because i think I lost all my previous nandroid backups and stuff so im going to say what im doing exactly to fix it and someone tell me what im doing wrong ha. I have debuggin on. I'm mounted. I downloaded the flash image and recovery image from the unlockr website. I put the files in the tools of my androidsdk... i type these commands.
cd\
cd c:\AndroidSDK\tools
adb devices
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
After i do the recovery-ra-eris.img i get an error
Click to expand...
Click to collapse

whats with everybody elses free version of rom manager not flashing the alternate recovery? im still a huge fan of ease of use personally. and its always worked im too scared to flash using it but i always flash the recovery when they update just to check it out.
and fyi renaming the recovery to something simple like recovery.img always makes things in the terminal easier as the gentleman above had mentioned

[Q] 1st update froyo

should i flash it. i dont have root

WOW! i cant believe no one has replied to you.
if you take a look at the first post with the topic
[ROM] Official AOSP 2.2 OTA
but you mentioned you dont have root. so try installing alogcat from the marketplace and capture the whole deal. then you can email directly from the app.

logcat isnt going to do much, it prefetches the files, need to pull the update.zip from adb

ok, so i havnt gotten the notice yet.
but need a bit of help prepping for when i do.
i have the android sdk installed on my desktop, and can create a virtual device etc...
but when i open the cmd prompt and try to run adb devices it says it is populating a list but i see no results or no file created.
so i tried just running adb logcat and it stops at waiting for device.
any pointers. im running win7x64 ultimate

well, i screwed it up. i removed the usb drivers and set it to debugging mode and got it working.
so i am able to run adb shell etc...
once i get the notice ill be ready to do an adb pull
adb shell
su
cd /cache/
ls
adb pull /cache/<package_name>.zip .

sepiid said:
well, i screwed it up. i removed the usb drivers and set it to debugging mode and got it working.
so i am able to run adb shell etc...
once i get the notice ill be ready to do an adb pull
adb shell
su
cd /cache/
ls
adb pull /cache/<package_name>.zip .
Click to expand...
Click to collapse
but how do you know the new radio and spl update name?

you should get that by running su then "cd /cache/ ; ls"
right now i have
download-1.apk
downloadfile.apk
recovery
lost+found
so after it is precached i run that "cd cache/ ; ls" i should have another file or two in there
that would be the file you run adb pull /cache/*.*

a tad bit of help, as a test i am trying to do
adb pull cache/downloadfile.apk d:\
but i get
remote object 'cache/downloadfile.apk' does not exist
i also tried adb pull /cache/downloadfile.apk d:\
and get the same.
edit:
tried doing a adb push
D:\android-sdk-windows\tools>adb push d:\test.txt /cache
failed to copy 'd:\test.txt' to '/cache/test.txt': Permission denied
so i dont have permission to put anything there, which means i likely dont have permission to pull from there
D:\android-sdk-windows\tools>adb pull /cache/downloadfile.apk d:\
remote object '/cache/downloadfile.apk' does not exist
so i opened another cmd prompt and and did an adb shell
su
and i am su
so while the other window was open and i was su i tried the same commands again and got the same results.
edit2:
D:\android-sdk-windows\tools>adb shell ls /cache
opendir failed, Permission denied
so it is definately a su/permissions issue.

Are you rooted? If not use Universal Androot.
*anticipation*

sepiid said:
a tad bit of help, as a test i am trying to do
adb pull cache/downloadfile.apk d:\
but i get
remote object 'cache/downloadfile.apk' does not exist
i also tried adb pull /cache/downloadfile.apk d:\
and get the same.
edit:
tried doing a adb push
D:\android-sdk-windows\tools>adb push d:\test.txt /cache
failed to copy 'd:\test.txt' to '/cache/test.txt': Permission denied
so i dont have permission to put anything there, which means i likely dont have permission to pull from there
D:\android-sdk-windows\tools>adb pull /cache/downloadfile.apk d:\
remote object '/cache/downloadfile.apk' does not exist
so i opened another cmd prompt and and did an adb shell
su
and i am su
so while the other window was open and i was su i tried the same commands again and got the same results.
edit2:
D:\android-sdk-windows\tools>adb shell ls /cache
opendir failed, Permission denied
so it is definately a su/permissions issue.
Click to expand...
Click to collapse
Here do this:
First if you have root, open up terminal or cmd prompt if you are on windows:
adb shell
su
mount -o rw,remount yaffs2 /cache
chmod 777 /cache
that will change the permissions allowing for read and write.
Now exit out of shell and just adb pull /cache/
That will pull everything out of the cache partition.

BAM!!! perfect!
i new it was permissions related. just couldnt figure out the "mount -o rw,remount yaffs2 /cache" part. might i ask you to break that down for me? at least the yaffs2 part.
thanks!
so once the update hits i am ready to grab the files.
callmeradical said:
Here do this:
First if you have root, open up terminal or cmd prompt if you are on windows:
adb shell
su
mount -o rw,remount yaffs2 /cache
chmod 777 /cache
that will change the permissions allowing for read and write.
Now exit out of shell and just adb pull /cache/
That will pull everything out of the cache partition.
Click to expand...
Click to collapse

So the YAFFS2 part of the code I put up there is designating the file system in which we are reading/writing.
YAFFS2 is the most popular and widely used format for flash memory.

please allow me.
yaffs2 is a filesystem type. /cache is of course the directory. -o is for option.
rw: read/write
remount: remount /cache again with new option.
sepiid said:
BAM!!! perfect!
i new it was permissions related. just couldnt figure out the "mount -o rw,remount yaffs2 /cache" part. might i ask you to break that down for me? at least the yaffs2 part.
thanks!
so once the update hits i am ready to grab the files.
Click to expand...
Click to collapse

Oh yeah and BTW, you can change the permissions back if you want after your done, otherwise I believe you can just reboot the phone and it fixes it, not entirely sure, I was trying to rewrite my default.prop to get adb remount to work with stock 1.6 rooted, but I am getting and access denied issue.

perfect was about to ask what the -o was but i tried mount --help and mount -h both resulted in nothing. then you reply sharpt71
thanks again all.
i am now ready to pull the update and upload once i get the update. hopefully soon!

Rather than the remounting and chmoding so you can adb pull.
You could probably get away with
Code:
su
cp /cache/<whatever> /sdcard
Then mount the SD card or put it in a card reader.

SilverSurfR said:
Rather than the remounting and chmoding so you can adb pull.
You could probably get away with
Code:
su
cp /cache/<whatever> /sdcard
Then mount the SD card or put it in a card reader.
Click to expand...
Click to collapse
You probably could I just know that this is a sure fire way to grab everything in cache directly to the machine, otherwise if you aren't next to a machine you could probably do a copy like you said.

My 2nd update failed, do you guys think the files are still in my cache?