Database Users

Location of apps after app2sd?

With root explorer, i see that my apps are saved to something like '/system/sd/app,' but when I mount my G1, I can't find that folder. I can't even find the "system" folder. Anyone have any ideas?
Also, I pressed the "R/W" button on that folder in Root Explorer, but now I can't switch it back to R/O. It gives me an error saying, "Remount Failed: Device or resource busy."

what is it you want to do with the apps?

My gmail app is force closing, and I haven't found a way to reinstall it through market. I was going to try to replace the .apk.

I don't believe the gmail app is on the SD, it should be under /system/app/Gmail.apk
For the most part, the system apps install on the phone, the rest are on SD.

That still leads me to my first question, lol. I can't find the "system" folder after mounting my G1.

??
I don't know. I use the rooted file browser SUFBS and have never had a problem seeing the system folder.
Might have been associated with other changes you made to the system.
For me, if all else fails, I re-partition, wipe & re-flash.
Hopefully someone else can offer some better info.

I find it fine on my G1 via Root Explorer. It's just that I can't seem to locate it on my computer (i.e something like h:\system\app), after plugging my G1 in.
Sorry for any confusion.

You must be on a windows machine. You can not nativly see an ext partition under windows.
Look at the guides that tell you how to set up adb and adb push the application to the folder you want.

adobrakic said:
I find it fine on my G1 via Root Explorer. It's just that I can't seem to locate it on my computer (i.e something like h:\system\app), after plugging my G1 in.
Sorry for any confusion.
Click to expand...
Click to collapse
You can do these things right from recovery console, and probably terminal, I like recovery better though. place the file you want to use on the root of the SDcard. Since it is the Gmail.apk you want to replace you would go about it like this:
mount system
mount sdcard
cp /sdcard/Gmail.apk /system/app/Gmail.apk
reboot
thats pretty much it.

[Q] Inconsistancies accessing Device Storage from windows

I've just noticed this today and wondered if anyone else has see this?
There seems to be an inconsistancy between the tablet and the view of the Device Storage when connected to windows via micro usb port.
For instance. I connect the tablet to windows with micro usb cable and I view files under "Device Storage" which is the contents of the internal sdcard from /mnt/sdcard.
I also start up an adb shell and cd to the /mnt/sdcard directory. As expected, both show the same files. And if I create a file or folder in the windows exporer view, the file or folder shows up in the adb shell view as well.. great..
However, If I create a file or folder using the adb shell, it does not get reflected to the windows explorer view (until the tablet is rebooted). Likewise, if I create file in the explorer view and then delete it in adb shell, it stays around in the explorer view. Also, if I delete a file in the explorer view, it stays around in the adb shell view.
Anyone know what's going on here and why it doesn't stay in sync? Is the windows explorer view using some kind of cache view?
Thanks

Euclid's Brother said:
I've just noticed this today and wondered if anyone else has see this?
There seems to be an inconsistancy between the tablet and the view of the Device Storage when connected to windows via micro usb port.
For instance. I connect the tablet to windows with micro usb cable and I view files under "Device Storage" which is the contents of the internal sdcard from /mnt/sdcard.
I also start up an adb shell and cd to the /mnt/sdcard directory. As expected, both show the same files. And if I create a file or folder in the windows exporer view, the file or folder shows up in the adb shell view as well.. great..
However, If I create a file or folder using the adb shell, it does not get reflected to the windows explorer view (until the tablet is rebooted). Likewise, if I create file in the explorer view and then delete it in adb shell, it stays around in the explorer view. Also, if I delete a file in the explorer view, it stays around in the adb shell view.
Anyone know what's going on here and why it doesn't stay in sync? Is the windows explorer view using some kind of cache view?
Thanks
Click to expand...
Click to collapse
I have had 100% of the same thing happen on my A500. I often find that my files are in the wrong location and I still cannot get the external SD to read from the computer.
I have another problem concerning these issues maybe you could help with. I may have either flashed an update without the proper files to go before it; or I have have forgotton to wipe something. Nonetheless, my A500 wouldn't boot. When I did some research, I went to this site {http://forum.ppcgeeks.com/showthread.php?p=2127076#post2127076} because it seemed in my eyes to have pertinent information. I got the update.zip to install and my A500 booted again! However, I could not get to stop two because my insternal SD card was wiped somehow and when I get to the main screen, do the circular unlock, the launcer, and many other programs repeatedly force close, so much so that I cannot do ANYTHING. How would you approach this, and is there a way for me to get into CWM. I have a recent nandroid backup that what 100% functional, and I would hope the MD5 sums would still match....
Any help/advice is greatly appreciated!

ibrooks.. try the instruction in post#1 of thread http://forum.xda-developers.com/showthread.php?t=1132760
That will wipe the data, which I believe is causing all your force closes.
Once that is done, then you can root with gingerbreak.
After that, you can continue the instructions from that thread you referenced. But instead, I would suggest flashing the official 3.1 from http://forum.xda-developers.com/showthread.php?t=1159443
Edit: The official 3.1 is not pre-rooted, you'll need to do the 3.1 root app if you want root access back.

Euclid's Brother said:
ibrooks.. try the instruction in post#1 of thread http://forum.xda-developers.com/showthread.php?t=1132760
That will wipe the data, which I believe is causing all your force closes.
Once that is done, then you can root with gingerbreak.
After that, you can continue the instructions from that thread you referenced. But instead, I would suggest flashing the official 3.1 that's pre-rooted from http://forum.xda-developers.com/showthread.php?t=1159443
Click to expand...
Click to collapse
uh... it's not pre-root...it's stock and will need "iconiaroot" to root
http://forum.xda-developers.com/showpost.php?p=15456928&postcount=5

UnicornKaz said:
uh... it's not pre-root...it's stock and will need "iconiaroot" to root
http://forum.xda-developers.com/showpost.php?p=15456928&postcount=5
Click to expand...
Click to collapse
Thanks.. I guess I was thinking about the leaked version that was released with pre-root. i've updated my post.

I've had that problem happen when I was trying to downgrade from the leaked 3.1. I was getting frustrating trying to flash different ROMs and the about kept showing the same version over and over again. Finally I realised that the files were just being copied to the device storage instead of the SD card. Taking the card out and copying the files directly did the trick.
Sent from my A500 using XDA Premium App

Great! Nice to know that I'm not cRaZy! I was having quite a time last night trying to copy files back and forth from the tablet, only to have them not show up where I knew they were in Windows explorer when connected via usb,.

Cannot see twrp back up files. Please help.

I recently switched over to team win recovery from cwm. I do like the ui and functionality way better then cwm. The problem I'm having is that I cannot access my back up files from my PC via USB. When I use the file browser that is built into twrp I can see the back up files in the twrp folder. When I plug my tablet into my PC via USB and open the twrp folder it is empty. Also when I open the twrp folder in es file browser it is empty there too. I would like to store the back up on my PC rather then on my tablet. Am I missing something? I was having this same problem with titanium with backed up apps so I upgraded to the paid version and uploaded my back ups to Google drive. After that I looked in the titanium back up folder again on my PC and all the sudden the files were there when before they were not. Its very frustrating. Please help.
Sent from my Nexus 7 using Xparent Green Tapatalk 2

I had this same problem with TWRP when I started using it a couple of days ago. I'm not rooted, just unlocked and using fastboot to load the recovery image temporarily to do backups. And when I went looking for the backup files to move to my computer, I couldn't find them. It turns out to be a permissions issue, with TWRP creating the files/directories owned and visible only to root. Not a problem if backing up to a FAT formatted sdcard, but it is a problem with the Nexus 7 since it honors permissions and ownership of all files on the "sdcard".
Two fixes that I know of, though I have only used one so far:
1) After you do the backup, open up the psuedo terminal in TWRP and manually change the permissions or owner of the files recursively. Just set the starting directory in TWRP to "/sdcard/TWRP" and do "chown -R media_rw.media_rw BACKUPS" to change the owner, or do "chmod -R og+rw BACKUPS" to change the permissions. You really only have to do one of those, and I went with the owner change. I was then able to see the backup when connected to my computer, copy the files off, and then delete them to avoid taking up space on the tablet.
2) Although I haven't tried it yet, supposedly you can backup and restore directly to/from a USB thumb drive connected via OTG cable. This would be the easiest method for me, since I want backup and restore capability but without actually storing anything on the Nexus 7. I'm going to try it with a backup tomorrow, but I read about someone doing just that thing for the same reasons in a comment on reddit.
Hopefully that answers your question and gives you a way around it.

Just wanted to bump and let you know that the permissions issue seems to be properly resolved in the 2.2.1.5 version of TWRP. If you update then you shouldn't have to go through any crap to get at the backups.
Additionally, I tried doing a backup to a USB drive and it worked perfectly, so if you prefer that route it is definitely an option. Just make sure that you have the USB drive connected before you boot into TWRP, otherwise it doesn't notice the drive.

mtrs said:
I had this same problem with TWRP when I started using it a couple of days ago. I'm not rooted, just unlocked and using fastboot to load the recovery image temporarily to do backups. And when I went looking for the backup files to move to my computer, I couldn't find them. It turns out to be a permissions issue, with TWRP creating the files/directories owned and visible only to root. Not a problem if backing up to a FAT formatted sdcard, but it is a problem with the Nexus 7 since it honors permissions and ownership of all files on the "sdcard".
Two fixes that I know of, though I have only used one so far:
1) After you do the backup, open up the psuedo terminal in TWRP and manually change the permissions or owner of the files recursively. Just set the starting directory in TWRP to "/sdcard/TWRP" and do "chown -R media_rw.media_rw BACKUPS" to change the owner, or do "chmod -R og+rw BACKUPS" to change the permissions. You really only have to do one of those, and I went with the owner change. I was then able to see the backup when connected to my computer, copy the files off, and then delete them to avoid taking up space on the tablet.
2) Although I haven't tried it yet, supposedly you can backup and restore directly to/from a USB thumb drive connected via OTG cable. This would be the easiest method for me, since I want backup and restore capability but without actually storing anything on the Nexus 7. I'm going to try it with a backup tomorrow, but I read about someone doing just that thing for the same reasons in a comment on reddit.
Hopefully that answers your question and gives you a way around it.
Click to expand...
Click to collapse
Thank you for the tip. I went everywhere yesterday...
Best buy, radio shack, staples etc looking for an otg cable and had no luck. I'm going to order one online today. I will give the other techniques a try today though. I'm not familiar with pseudo terminal but I'm gonna dig in anyway. That's the best thing about these gadgets for me is hacking in and figuring out. Thanks again for your help!
mtrs said:
Just wanted to bump and let you know that the permissions issue seems to be properly resolved in the 2.2.1.5 version of TWRP. If you update then you shouldn't have to go through any crap to get at the backups.
Additionally, I tried doing a backup to a USB drive and it worked perfectly, so if you prefer that route it is definitely an option. Just make sure that you have the USB drive connected before you boot into TWRP, otherwise it doesn't notice the drive.
Click to expand...
Click to collapse
When I first started out with twrp I flashed 2.2.1.2 via adw. That was before I knew about the goo option in the play store. I've since upgraded to 2.2.1.5 and still having the same issue.
Sent from my Nexus 7 using Xparent Green Tapatalk 2

norcal61 said:
When I first started out with twrp I flashed 2.2.1.2 via adw. That was before I knew about the goo option in the play store. I've since upgraded to 2.2.1.5 and still having the same issue.
Click to expand...
Click to collapse
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.

mtrs said:
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
Click to expand...
Click to collapse
Cool, that totally makes sense. Can't believe I didn't try that all ready. I will definitely make a new back up with the latest version of twrp. I'm running the same ROM and kernel as the back up that I currently have stored. Gonna give it a shot right now and let you know how it works.
Sent from my Nexus 7 using Xparent Green Tapatalk 2

mtrs said:
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
Click to expand...
Click to collapse
No luck. That's weird. I deleted the folder SD/twrp/backups containing the back up, did another back up and still not visible on my PC or in es file browser.

norcal61 said:
No luck. That's weird. I deleted the folder SD/twrp/backups containing the back up, did another back up and still not visible on my PC or in es file browser.
Click to expand...
Click to collapse
Hmm, you may have to delete "/sdcard/TWRP" as well, and just let it recreate everything. I might have changed the permissions on it already on mine, which is why it worked for me just deleting BACKUPS. I'll double-check that when I get back home and make sure.

mtrs said:
Hmm, you may have to delete "/sdcard/TWRP" as well, and just let it recreate everything. I might have changed the permissions on it already on mine, which is why it worked for me just deleting BACKUPS. I'll double-check that when I get back home and make sure.
Click to expand...
Click to collapse
It worked! I deleted the twrp folder all together and it worked like a charm. I'm now able to see and move the backups to my PC. Thank you very much for your help. It is greatly appreciated!
Sent from my Nexus 7 using Xparent Green Tapatalk 2

Some path is :
/data/media/TWRP/BACKUPS/
You need copy to /sdcard/TWRP/BACKUPS and connect to pc will see it.

trungdtdev said:
Some path is :
/data/media/TWRP/BACKUPS/
You need copy to /sdcard/TWRP/BACKUPS and connect to pc will see it.
Click to expand...
Click to collapse
I had the same issue and tried searching for "TWRP" to locate every instance of that folder. Turns out that I had previous backups in:
/mnt/shell/emulated/TWRP/BACKUPS/
I am happy to report that I was able to delete several past and hidden backups and recovered over 9gb of space!

Transfer Nexus7 nandroid backup to my PC?

So I would like to transfer my nexus 7 nandroid backups to my PC. Since I only have an 8GB N7, I dont want to waste alot of space with nandroid backups. My question is, when connecting my N7 to my PC via USB cable, which folders do I need to transfer? The reason I'd like to do this is because I need to do a factory restore on my device, but after I get the factory restore done, I want to be able to reflash CWM and then use the files on my computer to restore my N7 (after transferring the files back to my N7 of course) Any help would be much appreciated!

Just cut the clockworkmod folder from the internal storage. Then if you Need to restore just drop it back
Sent from my HTC One X using xda app-developers app

I have had to do this as well. I keep my nandroid and TiBu files on my PC between ROM updates.

bagofcrap24 said:
Just cut the clockworkmod folder from the internal storage. Then if you Need to restore just drop it back
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sorry, but I never thought about this before. If I delete the CWM folder from my tablet, it will remain in my tablet folder on my PC? Then, if I need to do a restore, I can just connect to the PC and add it back to my tablet and restore? Is this correct?

No. Plug your tablet in
Open Nexus 7
Internal storage
Copy the folder clockworkmod to a place on your pc
Once complete delete it from internal storage
If you need to restore
Plug in
Open Nexus 7
Internal storage
Copy clockworkmod folder back from pc to internal storage
Sent from my Nexus 7

I realize this thread is a bit old, but I have been searching and I cant find the answer. My problem is simple. The clockworkmod folder simply does not show up on my PC. The directories that show are the ones for my apps etc, and I can't seem to dig deeper than that. On my Nexus 7 I can browse right to the backups, but I cannot access them from the PC. I have no clue why. I successfully rooted 4.2.2 yesterday and everything else I've done has worked fine, but I can only access the clockworkmod folder from the Nexus 7 itself or from the adb shell on the PC (but I have no idea if I can use the shell to move the backup file to the PC or not).
So in short, I have no idea what to do. I recognize that I am a noob here, but I have done my homework searching for this particular issue and I haven't been able to find anything resembling a solution.

Mjolniir said:
I realize this thread is a bit old, but I have been searching and I cant find the answer. My problem is simple. The clockworkmod folder simply does not show up on my PC. The directories that show are the ones for my apps etc, and I can't seem to dig deeper than that. On my Nexus 7 I can browse right to the backups, but I cannot access them from the PC. I have no clue why. I successfully rooted 4.2.2 yesterday and everything else I've done has worked fine, but I can only access the clockworkmod folder from the Nexus 7 itself or from the adb shell on the PC (but I have no idea if I can use the shell to move the backup file to the PC or not).
So in short, I have no idea what to do. I recognize that I am a noob here, but I have done my homework searching for this particular issue and I haven't been able to find anything resembling a solution.
Click to expand...
Click to collapse
The pathway for nandroid backup is not /storage/emulated/0 or /storage/sdcard0 or /sdcard
It's somewhere else, but I'm not sure exactly where. Download a root file manager like root explorer then search.
Sent from Nexus 7 3G using Tapatalk HD

stfudude said:
The pathway for nandroid backup is not /storage/emulated/0 or /storage/sdcard0 or /sdcard
It's somewhere else, but I'm not sure exactly where. Download a root file manager like root explorer then search.
Sent from Nexus 7 3G using Tapatalk HD
Click to expand...
Click to collapse
Thanks, I have been using the one that comes with ROM Toolbox. The path is data/media/clockworkmod but the problem is I can't access that from the PC. When I try to copy or move the backup file to a directory that I can reach from the PC, It fails. I just get a message saying copy failed or move failed and thats it. That happens with both ES file Explorer and the ROM Toolbox root file explorer. I can see the files just fine and they also appear to have read, write and execute permissions.
Perhaps I am doing something wrong as a user with these apps that I am not being allowed to copy or move these files.

Mjolniir said:
Thanks, I have been using the one that comes with ROM Toolbox. The path is data/media/clockworkmod but the problem is I can't access that from the PC. When I try to copy or move the backup file to a directory that I can reach from the PC, It fails. I just get a message saying copy failed or move failed and thats it. That happens with both ES file Explorer and the ROM Toolbox root file explorer. I can see the files just fine and they also appear to have read, write and execute permissions.
Perhaps I am doing something wrong as a user with these apps that I am not being allowed to copy or move these files.
Click to expand...
Click to collapse
OK, something occurred to me right after writing that reply. I have been trying to copy the whole folder containing the backup files instead of just copying the files themselves. So I went in one level deeper and selected all the individual backup files and was able to copy/paste them into a directory my PC can see and was able to copy them from there onto my PC hard drive. So problem solved I guess.

Difficult to transfer Nandroid to Win8 PC
I have spent the morning trying to find a certain way to transfer my TWRP folders/files to a Windows 8 PC, without luck:
If anyone knows of a simple way to do this please chip in.
Luckily I have an iMac which allows easy transfer from a Nexus device, so I was able to copy TWRP to the iMac and from there to a 32GB Flash drive, then carry that to the Win8 for copying. Not exactly what one would hope for in 2013.. but it works.
I looked at pulling TWRP using WUGfresh and a Nexus Toolkit and think myself lucky not to have ended up with a brick.
Any links to Howto for Windows 8 much appreciated
Mvh

Its as simple as
adb pull /data
Sent from my Galaxy Nexus

Pirateghost said:
Its as simple as
adb pull /data
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Can't get much simpler than that I guess
Thanks

So it's okay to just copy the backup itself to the computer desktop, then when I need it, transfer it back? I've been just going in to the CWM folder and copying the folder directly to my desktop. So if I need to I can just copy it back provided I put in the same folder?

nicholi2789 said:
So it's okay to just copy the backup itself to the computer desktop, then when I need it, transfer it back? I've been just going in to the CWM folder and copying the folder directly to my desktop. So if I need to I can just copy it back provided I put in the same folder?
Click to expand...
Click to collapse
of course....why would it NOT be ok?

Pirateghost said:
of course....why would it NOT be ok?
Click to expand...
Click to collapse
Well, I just wasn't sure if in the process of being transferred that windows might alter it somehow. I just transferred my Nandroid to my computer, deleted it off my phone, then transferred it back and booted into CWM. I went to restore just to see if it would show up and it did just fine.
I just wasn't 100% sure about it. It just seems too easy... lol. I have Nandroids of quite a few different Rom setups on my computer, I just never had to restore them yet. So hypothetically, if you had the storage space, you could take a Nandroid of every Rom setup you've had and be able to revert to them anytime?
I saw some video guides of people using Adb to transfer to their computers and wondered why they didn't just copy and paste it. I thought there must be a reason. I'm still relatively new to this (only been a few months since my first flash), so I'm still learning.
---------- Post added at 07:41 AM ---------- Previous post was at 07:02 AM ----------
Pirateghost said:
Its as simple as
adb pull /data
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
And what would the advantage of doing it through adb pull command instead of just simply copying it to the desktop? Is it safer or what? That's why I wonder if doing it this way is safe, when everyone else does adb commands...
Sent from my Galaxy S3 on Beans build 15 via tapatalk 2

nicholi2789 said:
Well, I just wasn't sure if in the process of being transferred that windows might alter it somehow. I just transferred my Nandroid to my computer, deleted it off my phone, then transferred it back and booted into CWM. I went to restore just to see if it would show up and it did just fine.
I just wasn't 100% sure about it. It just seems too easy... lol. I have Nandroids of quite a few different Rom setups on my computer, I just never had to restore them yet. So hypothetically, if you had the storage space, you could take a Nandroid of every Rom setup you've had and be able to revert to them anytime?
I saw some video guides of people using Adb to transfer to their computers and wondered why they didn't just copy and paste it. I thought there must be a reason. I'm still relatively new to this (only been a few months since my first flash), so I'm still learning.
---------- Post added at 07:41 AM ---------- Previous post was at 07:02 AM ----------
And what would the advantage of doing it through adb pull command instead of just simply copying it to the desktop? Is it safer or what? That's why I wonder if doing it this way is safe, when everyone else does adb commands...
Sent from my Galaxy S3 on Beans build 15 via tapatalk 2
Click to expand...
Click to collapse
If you are using cwm, the backups are not user accessible and do not show up under /sdcard, and the only way of accessing them is with ROM manager or with a root explorer... Which makes it hard to transfer back and forth from a computer. If you use adb you will be able to pull everything available under /data/media
Sent from my Nexus 7 using Tapatalk HD

That's weird... The backups show up on my computer.... I just plug in and open my phone through my computer, then I go to the CWM folder and drag and drop it to the desktop. Usually takes about ten minutes to transfer because my nandroids are huge (2.2 gb). That easy. I now have transferred it to the computer and then transferred it back to my ext SD card and used it to successfully restore. Did it yesterday.
That's weird. I wonder why it would show up on my computer and not everyone else's?

nicholi2789 said:
That's weird... The backups show up on my computer.... I just plug in and open my phone through my computer, then I go to the CWM folder and drag and drop it to the desktop. Usually takes about ten minutes to transfer because my nandroids are huge (2.2 gb). That easy. I now have transferred it to the computer and then transferred it back to my ext SD card and used it to successfully restore. Did it yesterday.
That's weird. I wonder why it would show up on my computer and not everyone else's?
Click to expand...
Click to collapse
Depends on what version you are on
Sent from my Galaxy Nexus

Pirateghost said:
Depends on what version you are on
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Well i guess on windows 7/Beams build 15 it's visible.... But even when I still had the stock Jellybean Rom I was able to transfer my backups no problem...
In any event, I should probably get more familiar with adb so i am able to transfer that way or restore if I get bricked somehow... Adb is just so complicated to me though. I've read countless threads and other how tos, but i'm still hesitant to try anything serious. It's friggen intimidating. I have the toolkit installed and the path all set up on my computer and everything, I just haven't done much with it yet.
Sent from my Galaxy S3 on Beans build 15 via tapatalk 2

not your version of windows OR ROM.
are you on 4.2.2 with latest CWM?

[Q] How to delete PUSHED files from "/sdcard/"

Hello, so I've done some light searching, but can't seem to find the answer to my question.
I've just finished installing a custom ROM to my Nexus 4, and in doing so, I pushed a few files to my phone via ADB
(ADB PUSH FILENAME.ZIP /SDCARD/FILENAME.ZIP) and am now wondering how to REMOVE these files that I no longer need.
When I am in recovery and select "install from zip" obviously, I am able to see the files, as that is how I installed them. However!
I can not view them via MTP (not that I've ever had much success with MTP) nor using ASTRO or File Manager.
Where are these files truly located and how can I delete them?
Ideally, I would like to learn how to view this directory, but would be happy enough just to know which ADB commands would list these files
and which commands will allow me to remove them one by one.
Thank you
*ISSUE RESOLVED*
After looking within CWM as to where sdcard contents were being sourced "/data/media"
I rebooted the phone, and attempted to locate this directory within File Manager with no luck....at which point, I realized that File Manager didn't have root privileges.
After giving root privileges to File Manager, I was able to navigate to /data/media and locate the pushed files and remove them.

If I were you I'd use adb shell and then the Linux remove command
That means:
Code:
adb shell
cd /sdcard/
rm - r FILENAME.zip
That's it, hope it works
Sent from my Nexus 4 running Android 4.3

Thank you for your reply! The only issue I have with that method, is not necessarily knowing the file names...
I would assume there are quite a few files within this directory, given that this isn't the first ROM I've installed.
I'd really like to be able to view the contents of the true location. Does anyone happen to know where it is on the Nexus 4 that CWM
is looking for the zip files? I would assume that this would tell where the files are located, and perhaps I could point an explorer to it.
What was puzzling was that searching the entire phone for "gapps" in ASTRO yielded no results.... as I am certain more than one of the zips I have pushed contain this within their file name.

losballatopg said:
Thank you for your reply! The only issue I have with that method, is not necessarily knowing the file names...
I would assume there are quite a few files within this directory, given that this isn't the first ROM I've installed.
I'd really like to be able to view the contents of the true location. Does anyone happen to know where it is on the Nexus 4 that CWM
is looking for the zip files? I would assume that this would tell where the files are located, and perhaps I could point an explorer to it.
What was puzzling was that searching the entire phone for "gapps" in ASTRO yielded no results.... as I am certain more than one of the zips I have pushed contain this within their file name.
Click to expand...
Click to collapse
adb shell
cd /sdacrd/
ls
then u see the names
or to delete all zips(i dont know if this will work, i only tried with del *.exe on Windows)
adb shell
cd /sdcard/
rm - r *.zip

use a file explorer, go into your sd card storage, find the files, long press and delete.

simms22 said:
use a file explorer, go into your sd card storage, find the files, long press and delete.
Click to expand...
Click to collapse
Yeah....so perhaps you didn't read either of my posts.....the files don't show up in any file explorer that I've tried. That was basically the main issue...

opssemnik said:
adb shell
cd /sdacrd/
ls
then u see the names
or to delete all zips(i dont know if this will work, i only tried with del *.exe on Windows)
adb shell
cd /sdcard/
rm - r *.zip
Click to expand...
Click to collapse
Once I have entered the /sdcard/ directory, running "ls" shows nothing..... :-/
I just don't know how this topic hasn't been discussed more often.....
What does everyone else do? Just keep filling that directory every time they push something and leaving it until the next wipe?

losballatopg said:
Yeah....so perhaps you didn't read either of my posts.....the files don't show up in any file explorer that I've tried. That was basically the main issue...
Click to expand...
Click to collapse
if you successfully pushed the files to /sdcard/, then thats where they should be, they cant be anywhere else. make sure that you arent looking in/sdcard/download/. what file explorer are you using btw? use a root file explorer(like root explorer), not a regular file explorer.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
losballatopg said:
Once I have entered the /sdcard/ directory, running "ls" shows nothing..... :-/
I just don't know how this topic hasn't been discussed more often.....
What does everyone else do? Just keep filling that directory every time they push something and leaving it until the next wipe?
Click to expand...
Click to collapse
because no one else has an issue with this. im guessing its the file explorer that you chosen to use or user error somewhere.

simms22 said:
if you successfully pushed the files to /sdcard/, then thats where they should be, they cant be anywhere else. make sure that you arent looking in/sdcard/download/. what file explorer are you using btw?
Click to expand...
Click to collapse
Yes, this would seem to be the logical answer wouldn't it? This isn't my first "Android Rodeo"...however, as Android and handsets have developed, directories are no longer always as they seem (or titled)
Luckily I was able to resolve my issues.....
After looking within CWM as to where sdcard contents were being sourced "/data/media"
I rebooted the phone, and attempted to locate this directory within File Manager with no luck....at which point, I realized that File Manager didn't have root privileges.
After giving root privileges to File Manager, I was able to navigate to /data/media and locate the pushed files and remove them.
Thank you for your efforts, and hopefully this helps someone else down the road who finds themselves in the same situation.

simms22 said:
if you successfully pushed the files to /sdcard/, then thats where they should be, they cant be anywhere else. make sure that you arent looking in/sdcard/download/. what file explorer are you using btw? use a root file explorer(like root explorer), not a regular file explorer.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
because no one else has an issue with this. im guessing its the file explorer that you chosen to use or user error somewhere.
Click to expand...
Click to collapse
I tried Solid Explorer, ASTRO File Manager, and the File Manager provided with CM 10.2
Were you to have simply informed me that files pushed to "/sdcard/" were located at "/data/media" my issue would have been resolved through the logic I ended up using.
Something tells me you prefer the blame game
Thanks anyway

losballatopg said:
I tried Solid Explorer, ASTRO File Manager, and the File Manager provided with CM 10.2
Were you to have simply informed me that files pushed to "/sdcard/" were located at "/data/media" my issue would have been resolved through the logic I ended up using.
Something tells me you prefer the blame game
Thanks anyway
Click to expand...
Click to collapse
first off, i dont use cwm, i use twrp recovery. all my files get pushed to wherever i push them, period.
if you look at my thanks at least, you can see that i dont prefer the blame game, but i do prefer helping people. and personally, that hurts my feelings, thanks

simms22 said:
first off, i dont use cwm, i use twrp recovery. all my files get pushed to wherever i push them, period.
if you look at my thanks at least, you can see that i dont prefer the blame game, but i do prefer helping people. and personally, that hurts my feelings, thanks
Click to expand...
Click to collapse
Well, then it seems that we have both learned something today. Glad we could be such a great!
No hard feelings

losballatopg said:
Well, then it seems that we have both learned something today. Glad we could be such a great!
No hard feelings
Click to expand...
Click to collapse
both learned something? im lost, what did i learn
oh nevermind. enjoy.

simms22 said:
both learned something? im lost, what did i learn
Click to expand...
Click to collapse
Well...you didn't seem to have prior knowledge of the fact that pushing to "/sdcard/" places files in the "/data/media" directory
(at least for when pushing within CWM Recovery on a Nexus 4, and from what I've read, all other recent versions of Android with no external SD)
Unless you're choosing to ignore this information...I'd call it something learned.

losballatopg said:
Well...you didn't seem to have prior knowledge of the fact that pushing to "/sdcard/" places files in the "/data/media" directory
(at least for when pushing within CWM Recovery on a Nexus 4, and from what I've read, all other recent versions of Android with no external SD)
Unless you're choosing to ignore this information...I'd call it something learned.
Click to expand...
Click to collapse
not while using twrp. but, point taken. i did learn something today, i learned of another reason why not to use cwm recovery

simms22 said:
not while using twrp. but, point taken. i did learn something today, i learned of another reason why not to use cwm recovery
Click to expand...
Click to collapse
I concur.

wow just read this thread and I must admit simms22 is quite helpful and even in some instances more helpful than he needs to be... LOL
now if pushing a file to /sdcard sends it to data/media then I truly agree as well CWM is a problem. I must admit though when using CWM I have never had that issue. Usually pushing a file to whatever folder I choose it normally goes there.
Also as a personal preference Root Explorer is a hell of a file manager..Jus Sayin'