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.
Related
Hi all,
Love my HTC Desire so much i bought a Witstech A81E Android 2.2 Tablet. Which is pretty buggy to say the least though on the whole works well.
The one thing that is driving me crazy is a number of apps dont install with the logcat error:
"packagename.apk requires unavailable shared library com.google.android.maps"
Now from what i have read apparently this device does not come with Google Maps API so my question is how do i add it?
Can it be done? Do i need to modify a ROM to do it? can i push it via adb or apk?
A little help would be greatly appreciated.
It would need to have google apps installed to be able to access the libraries. Best bet is to find out if it has been rooted yet and try to install the proprietary applications they can't ship the device with.
appreciate the help mate. i've rooted the device though where can i find google maps api?
the unit already has google maps 5.0 installed but apparently doesnt have the API's.
Any idea what im looking for? will it be an APK or just some files i need to put in a system folder?
i think im over my head
additionally i have searched for any com.google.android.maps related data on my desire and have found the following:
/system/framework/com.google.android.maps.jar
/system/etc/permissions/com.google.android.maps.xml
/etc/permissions/com.google.android.maps.xml
/data/dalvik-cache/[email protected]@[email protected]
could it be as easy as copying this over to my tablet?
Ill try it out tonight.
If the application is installed correctly it should work because the api is stored in the data. Is the application on the tablet installed to the /system/ or /data/ partition. It might be looking for the data in /system/
not sure what you mean about where the application resides? you mean the app i am trying to install? The app i am trying to install is Tasker.
i have been doing some googling and saw someone else have the same problem and he managed to fix it:
When trying to install some apps, I would see this error message in logcat:
requires unavailable shared library com.google.android.maps
I had the Google Maps app installed and working, but that didn’t fix the issue. It turns out, I had to add two other files and restart the phone. I found those files in the google zip from Cyanogenmod. It took a little fiddling, but I was able to use these instructions to remount /system in write mode. First step was to take the following two files from the google apps zip (gapps-hdpi-20101114-signed.zip) and put them onto my sd card.
/system/etc/permissions/com.google.android.maps.xml
/system/framework/com.google.android.maps.jar
Then to load them onto the phone, I opened the terminal emulator and ran:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp /mnt/sdcard/com.google.android.maps.xml /system/etc/permissions/
cp /mnt/sdcard/com.google.android.maps.jar /system/framework/
Then after I rebooted the phone, I was able to install apps that depend on Google Maps. I can now check bus and train times, and do all kinds of other cool stuff with maps!
Click to expand...
Click to collapse
i simply used root explorer to copy it across though still not working. surely someone smarter than me can tell me what i am doing wrong.
is copying with root explorer essentially the same as above?
damn i could have sworn someone here would have been switched on enough to help me on this
oh well back to random googling for me.
Well did you try using terminal emulator? And do what he did? B/c that looks like a remount to system to me easy as pie just do what he did you can find the files with root explorer or do it on your pc doesnt really matter. You can Not achieve what he did just using root explorer you need terminal emulator!
Sage said:
damn i could have sworn someone here would have been switched on enough to help me on this
oh well back to random googling for me.
Click to expand...
Click to collapse
I don't know how much it will help (or if its 100 percent true) but I was just told recently that moving a file via root explorer is the same as pushing it via adb.
sent from gv1.5 on g2
^correct
Sent from Enrique Iglesias.
now i am confused. can i use root explorer or not? i used root explorer and then reset the correct permissions on the files though its still not working.
I take it i can get a terminal emulator that runs on the device itself yeah?
Ill try that next.
If that fails i am going to try my first attempt at cooking a ROM
Appreciate all the help!
no more love for Sage?
i dont know why its so hard..
I did try to cook the original ROM though unyaffs couldnt extract the img.
looks like i might have to boot up a Virtual nix box.. damn this is so much harder than it should be.
I've been running cm7 nightlies and now stable 7.0 for some time now. I have the new radio, ladios' kernel, and the sdcard read fix flashed.
I installed super manager and successfully deleted some of the stock cm7 media off my phone last week. Today, I came across the new GPS.conf files and wanted to try them.
Super manager couldn't switch the system to r/w despite saying "ok"
When I try to delete or write in the system with EStrongs file explorer, ghost commander, or android mate, they all give strange errors. The deleted files disappear but reappear after reboot. If I try to paste a file in system/etc I only get an error.
Superuser is successfully allowing permissions. I have the latest busybox. I have r/w enabled in each file manager.
I even tried an adb push test which first said "system is r/o only". The next try was "successful" but didn't do anything.
I'm still new with adb so I probably did something wrong. I typed in that r/w command, mount now shows: /dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
I can't figure out what changed and what I need to do to get r/w permissions. My only theory is that i had uninstalled and reinstalled super manager earlier and that somehow messed with my permissions.
You cannot permanently modify the system partition while the phone is booted into Android. The only way is to use adb while the phone is in recovery mode. Any changes you make while the phone is booted will be lost after a reboot.
Go check on those media files you thought you deleted. I bet you'll find they are still there.
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
You don't need to sign them on the aria
Sent from my Liberty using XDA App
jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Click to expand...
Click to collapse
Those programs will work on some phones but not the Aria.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
It really is as simple as adding or removing a few files from the zip file if you want to modify it.
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,.
Most of the files in my TiBU folder will copy. All the properties files, and ~half of the .gz files. Most of these are game backups for progress purposes.
Dragging and dropping using Windows explorer doesn't work (nothing will happen at all)
Using ES File Explorer from the phone doesn't work.
adb from the PC doesn't work (command line has entries saying something about permissions on the failed files)
Help? I'm aware I could try backing up to cloud, but that's a workaround vs actually solving the problem. Plus it takes a while.
deusfaux said:
Most of the files in my TiBU folder will copy. All the properties files, and ~half of the .gz files. Most of these are game backups for progress purposes.
Dragging and dropping using Windows explorer doesn't work (nothing will happen at all)
Using ES File Explorer from the phone doesn't work.
adb from the PC doesn't work (command line has entries saying something about permissions on the failed files)
Help? I'm aware I could try backing up to cloud, but that's a workaround vs actually solving the problem. Plus it takes a while.
Click to expand...
Click to collapse
I think TIBU needs a big update....I have same issue but my biggest problem is I can´t uninstall any system apps (there a some I don´t need) when I tap the uninstall button always same thing...."Cannot find the .apk file .....no problem whith my personally apk´s..?
Somebody same issue?
I ran into the same issue and solved (?) it by rebooting into recovery and doing an adb pull from there. It doesn't work from within Android like you said but once you're in the recovery partition things are different.
I think this not a problem with TiBu (or maybe it just needs an update like shivasrage said), because I can't copy my Nandroids to my PC either. I had to do a adb pull from recovery as well in that case. In fact, now that I remember, yesterday I tried to copy some backups I did in ES Explorer and some of them failed.
Android 4.3 is secure but that's messing with our old habits and making things more difficult.
Yeah but I had this problem before updating to 4.3
deusfaux said:
Yeah but I had this problem before updating to 4.3
Click to expand...
Click to collapse
Oh, that's weird. I never had this problem before 4.3.
I just went through this exact same problem with my TWRP backup files yesterday (Except in that case it was an issue with the latest 2.6 version of TWRP, not the Android OS). For Titanium Backup, I am going to have to go back today and count the files that I copied over to my PC using Windows Explorer and compare it to an adb pull under Recovery. There are so many files as part of the backup that I would never have noticed a couple of missing ones like I did on TWRP.
EDIT: Just checked and 427 files were copied over doing it each way with a full Titanium Backup (Windows Explorer or an adb pull), so it works fine for me. I am on Android version 4.2.2.
I solved the problem by installing BusyBox from Play Store (Normal install). Then, opened a command window (you can also do it using Terminal Emulator) from within my platform-tools folder in C and typed:
adb shell
su (grant permission in the phone)
busybox chown -R 1023.1023 /data/media/*
Click to expand...
Click to collapse
Now I can safely copy all files by drag-n-drop or adb pull from within android.
Cheers
Can someone walk me through solving this? I'm wanting to do a factory reset immediately, but I can't before copying over these Titanium Backup'd apps.
Why is this even happening?
ABD, ES File Explorer, everything is giving me a permission error. The latter said EACCES (Permission denied) Refused by system.
edit: nevermind. I narrowed down the offending files, and forced new backups by deleting the old ones and re-doing them. Something about the way TiBu wrote a handful of the backups was not allowing anything to copy the files.
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'