I'm running TaintedTenzo2.1 with A2SD on my Eris.
I found a file named *.apk in /data/app-private and have no clue what it is. I cannot copy and paste to SDCARD with root explorer, nor can I pull it with ADB. Any ideas?
Code:
# cd data/app-private
cd data/app-private
# ls
ls
*.apk
# ls -l
ls -l
-rw-rw-rw- root root 1538413 2010-08-10 19:54 *.apk
#
Why don't you PM the dev and ask
Sent from my Eris using XDA App
Do you think it is a function of that particular ROM? I've seen it in the same place when I ran CELB2.8, too.
Hmm that is rather strange, still I'm pretty nooby, but maybe a dev really could point you in the right direction, at least tell you what it is or does.
Sent from my Eris using XDA App
Try renaming it to a regular name while keeping the .apk extension.. its not there on my taintedtenzo, but I've seen it before.. sometimes that seems to happen and show up in data/app and/or data/app-private when you download an app from the market and it doesn't finish installing correctly for some reason.. In your case it was a private app you tried to install from market. It is not a function. Rename it to anything.. just remove the star and don't add any spaces, keeping the .apk at the end, then try to install and it should pop up telling you what app you are installing.
Only thing is I'm not sure if private apps can he installed directly from a .apk, as they always have a .zip file in data/app.
Tainted Tenzo 2.1 v8 and/or Kaos Froyo v31
Related
1) How do I remove hard linked files on the X10 Android file system? I also need to identify them with the "ls" command, but it doesn't work the same as linux by listing the count in the ls listing of hard links to a specific file. The reason is, when I try to move a file in /system/app, it tells me it failed due to cross-device link - likely because the OS knows the link will fail if I move the file to my /sdcard directory. I want to remove the hard-link.
2) Is there a listing of all the options available to the commands in the /system/bin directory? It seems the ls command, for example, is a stripped down version of the ls that comes with linux.
Thanks.
what method are you using to move the files in system/app? you should be able to move them using root explorer, or copy out using dd if= of= statements then rm, the xperia system does not seem to like cp and mv commands
I'm using:
Code:
mv /system/app/Facebook.apk /sdcard/backup/system/app
...it fails. A dd works, because it just does a block copy and doesn't move the file. I'll try moving it with Root Explorer.
I'd prefer an actual command instead of using an app on the phone, as I've connected the phone to my PC with the USB cable and using adb.exe.
FYI, I tried Root Explorer, for some reason it can move the file just fine! My phone is rooted and I'm running the adb shell with super-user access.
use this:
busybox ls -l
busybox cp
busybox mv
Or even better, use "busybox --install /system/bin" and let it install all the symlinks for you
aln688 said:
I'm using:
Code:
mv /system/app/Facebook.apk /sdcard/backup/system/app
...it fails. A dd works, because it just does a block copy and doesn't move the file. I'll try moving it with Root Explorer.
I'd prefer an actual command instead of using an app on the phone, as I've connected the phone to my PC with the USB cable and using adb.exe.
FYI, I tried Root Explorer, for some reason it can move the file just fine! My phone is rooted and I'm running the adb shell with super-user access.
Click to expand...
Click to collapse
biktor_gj said:
use this:
busybox ls -l
busybox cp
busybox mv
Or even better, use "busybox --install /system/bin" and let it install all the symlinks for you
Click to expand...
Click to collapse
Thanks for the tip, you've just explained what busybox is. I always wondered why Titanium Backup wanted Busybox for it to run properly. I'll try these commands out.
UPDATE: Nice, I get VI as well! I was wanting that. I got fedup editing a file on the PC and pushing it back to the phone. Thanks.
I am really tearing my hair out over this one, and I cannot find a solution no matter what I do. I have searched everywhere I can think of and no one seems to have a solution.
Device & ROM: HTC Incredible S (vivo) with CM7.1 Nightlies (#139)
Problem: Busybox doesn't work. I tried using the Logging Checker app By TrevE but kept getting the error "ls: no such tool", which I thought was was odd. So I tried manually calling ls in terminal emulator and via adb shell, same error, so I assumed busybox was borked. I also noticed Titanium backup was using it's internal busybox, presumably because it couldn't get access to the system one either.
Attempts to fix:
First I tried re-installing busybox via Stericson's app from the market, it recognised I have the default CM7 one installed and updated it to the latest version. Still get the same problem.
I tried setting permissions to be avalible for everything on both busybox files (bin and xbin). Same error.
I tried manually deleting busybox via root explorer from bin and xbin and reinstalling, Stericsson's app now says I have multiple versions installed. Same error.
I tried wiping and reinstalling my ROM. Still same error.
This is really driving me crazy and I have run out of ideas. Can anyone help? I am not a "noob" I have been using android for a couple of years as well as dabbling in ROM & Kernel dev, I know how to use a search, one guy here mentions the same problem but never says if he got it fixed, and this guy says re-installing his ROM corrected it. Has anyone else seen this problem before?
There might be copy on your sdcard. You could delete that as well and try a "clean" install.
Also, check your path to make sure xbin and bin are included
As a last resort, or maybe the first step, you can install it manually.
Unzip the app and extract the busybox binary. If I recall correctly, they are in the assets folder as .png files. Pick a version.
mount the system as read-write
mount -o remount,rw /your/system/partition/here /system
you can type "mount" to see where /system is mounted
Push or copy the binary file to /system/xbin/buysbox
this is easier said then done since you don't have cp or mv!
ghetto copy should work - "cat /sdcard/busybox.png > /system/xbin/busybox
make it executable "chmod 755 /system/xbin/busybox"
let busybox do the heavy lifting "/system/xbin/busybox --install /system/xbin/"
remount the system as read only
busybox mount -o remount,ro /system
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Manual install worked, thanks man! Well, it worked in so far as I can use the tools from terminal emulator, but the logging app still gives me ls:no such tool. Titanium Backup can see the system busybox though which is good.
It might be using an aboslute path like /system/bin/ls to call ls. Maybe add a link? That is the hard part about manual install- you might have some toolbox links or other executables in other path directories.
sent from my cyanogen(mod) vision
I'm having the same problem. I have Busybox installed, but TrevE's Logging Checker says "ls: no such tool".
Did you find a solution for this problem?
Add a link? Try "busybox which ls" it's probably not pointing to busybox. You might have to add some absolute paths and other nonsense.
sent from my cyanogen(mod) vision
Thanks for the reply. "which busybox ls" replies:
# which busybox ls
/system/xbin/busybox
/system/xbin/ls
It looks like you have ls linked. Maybe the logger tool is looking for it in /system/bin? Have a look in there and see if there is a link or binary. It could be a toolbox link?
Lastly, check permissions- maybe it's not executable/accessible?
sent from my cyanogen(mod) vision
I've tried creating a symlink in /system/bin and it still doesn't work, so I sent TrevE a private message; I'll update this thread when he replies.
l0st.prophet said:
I am really tearing my hair out over this one, and I cannot find a solution no matter what I do. I have searched everywhere I can think of and no one seems to have a solution.
Device & ROM: HTC Incredible S (vivo) with CM7.1 Nightlies (#139)
Problem: Busybox doesn't work. I tried using the Logging Checker app By TrevE but kept getting the error "ls: no such tool", which I thought was was odd. So I tried manually calling ls in terminal emulator and via adb shell, same error, so I assumed busybox was borked. I also noticed Titanium backup was using it's internal busybox, presumably because it couldn't get access to the system one either.
Attempts to fix:
First I tried re-installing busybox via Stericson's app from the market, it recognised I have the default CM7 one installed and updated it to the latest version. Still get the same problem.
I tried setting permissions to be avalible for everything on both busybox files (bin and xbin). Same error.
I tried manually deleting busybox via root explorer from bin and xbin and reinstalling, Stericsson's app now says I have multiple versions installed. Same error.
I tried wiping and reinstalling my ROM. Still same error.
This is really driving me crazy and I have run out of ideas. Can anyone help? I am not a "noob" I have been using android for a couple of years as well as dabbling in ROM & Kernel dev, I know how to use a search, one guy here mentions the same problem but never says if he got it fixed, and this guy says re-installing his ROM corrected it. Has anyone else seen this problem before?
Click to expand...
Click to collapse
I don't have the correct answer as of right now, but I believe why both you and I are getting "ls: no such tool" when running Logging Checker app By TrevE is because ls is being called from toolbox and not busybox, if you where to adb shell into your phone and run /system/bin/toolbox ls you get the same error, also when I looked into the APK theres a file called "AtLeastHaveTheBallsToTellMeYouLOLedReadingThis.smali" and yes I did LOL when I read the file name but there are instances with toolbox ls being called.
I'll keep you posted if I figure it out.
Running "/system/bin/toolbox ls" from adb shell does give me the same "ls: no such tool" error.
I unzipped the APK and didn't find the funny file you mention, thou...
dserodio said:
Running "/system/bin/toolbox ls" from adb shell does give me the same "ls: no such tool" error.
I unzipped the APK and didn't find the funny file you mention, thou...
Click to expand...
Click to collapse
Unzipping just the APK alone won't let you see the file, it's a binary xml file to my knowledge, I had to use a tool called android-apktool, once you decode the APK its inside the folder called smali/com/treve/loggingtest/.
Finally figured it out, I had to copy the toolbox binary from an Android emulator and put it on my phone along with setting up the right permissions and group and now toolbox ls outputs. I checked Logging Checker and now I get a listing of files inside the app.
spellnight said:
Finally figured it out, I had to copy the toolbox binary from an Android emulator and put it on my phone along with setting up the right permissions and group and now toolbox ls outputs. I checked Logging Checker and now I get a listing of files inside the app.
Click to expand...
Click to collapse
Could you please provide specifics? I have all the SDK tools installed, but where is the "toolbox binary from an Android emulator" located? Did you run the Emulator and adb pull the toolbox you needed from it? Where did you put it on your phone to make it work, and what permissions and group are necessary? I would also like to use Logging Checker but I get the same error running evo-deck-1.3. While re-flashing may work, I'm worried it won't and then be stuck in the same place. Thanks.
Perhaps someone just happens to know if evo-deck-1.3 has Carrier IQ or not? I tried searching and couldn't find any specific mentions from the dev or users. Flipz actually preemptively pulled Carrier IQ from Fresh ROM 8 months ago when he didn't even know what it was, major kudos to him.
Same issue here: CM7.1 toolbox binary doesn't support "ls"
I have the same issue. Installed Logging Checker app By TrevE (thanks!) but get the "ls: no such tool" msg.
TrevE's app installs busybox (and its associated links) in /system/xbin, but for some reason his app appears to invoke "/system/bin/toolbox ls" which produces that message.
I can't find any other "ls" on the system other than the one in /system/xbin which is a link to /system/xbin/busybox.
Maybe I should just replace the toolbox binary with busybox after nandroiding?
I PMed TrevE but he has a lot going on right now.....
*update*: I did try remounting /system as rw and then # cd /system/bin; mv toolbox toolbox_save; cp /system/xbin/busybox . ; mv busybox toolbox
That changed the behaviour of the logging checker app; now it says "empty" instead of "ls: no such tool", but it also broke many commands that were linked to toolbox such as "vmstat". Also it didn't fix the registration problem with the app (says I haven't donated even though I've purchased the key app).
So I undid the changes (before I screwed anything else up) and rebooted.
At this point you might as well use the detector on Market by Voodoo or Lookout because troubleshooting this may well take longer than just using another detector. I do worry though that those who need removal will still be forced to TrevE's app but may find it not working after paying for the license key. Be careful though! I'm sure that malicious "detectors" will start popping up, which will be their own spyware at best and possibly extract the data from CIQ at worst.
V8 of TrevE's app and key fixed the problem for me
Thanks again to TrevE for creating this! I installed Version 8 and everything was fixed.
Hi,
I'm attempting to replace Email.apk on my miui rom. This is the method I am using:
Code:
adb push Email.apk /sdcard/
adb shell
su
rm /system/app/Email.apk
rm /system/app/Email.odex
mount -o rw,remount /dev/block/mmcblk0p9 /system
cp /sdcard/Email.apk /system/app
reboot
When the phone has rebooted, my changes do not take affect. To check, I pulled the /system/app/Email.apk back, and found it to be the original version.
Can anyone tell me what I'm doing wrong here?
Thanks,
Have figured this out...
adb appears to send some kind of cached version over. Renaming the file before transferring forced adb to use the correct file, and all is well.
jimhaddon said:
Have figured this out...
adb appears to send some kind of cached version over. Renaming the file before transferring forced adb to use the correct file, and all is well.
Click to expand...
Click to collapse
How? I like to know too, guide step by step....thanks
You mean renaming the original file first to any name then copy the moded file with the original name ?
If that what u mean , so I better to delete the original one first then but enstead my moded file . Is that right ?
Sent from my GT-I9100 using XDA App
Just use something like root explorer, no need for adb...
Joey2o11 said:
Just use something like root explorer, no need for adb...
Click to expand...
Click to collapse
I tried to use root explorer to change phone.apk, it didnt work.. i changed the file but it kept on crashing all the time ...
Sent from my GT-I9100 using XDA App
hielo_te said:
I tried to use root explorer to change phone.apk, it didnt work.. i changed the file but it kept on crashing all the time ...
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
You'll get lots of FCs until you reboot the phone then it should be fine.
I was gonna ask this as a question but then I just tried it and it all worked... So on my P509 using my rooted Android 2.2.2, "Mount /system (rw/ro)" app, Astro File manager, and Terminal Emulator. I placed a blank mp3 on my sd card and named it Startup.mp3. (Found a nice short one here: xamuel. com/blank-mp3s/) I made the /system file rewritable with the "Mount /system (rw/ro)" app. Then I typed only these code bits into Terminal Emulator:
To remove the old file:
su(enter)
mount -o rw,remount /system(enter)
rm -r /system/sounds/lgeSounds/Startup.mp3(enter)
Then cause I wanna copy a file from one place to another it's (you might need to change these 2 file chains based on what you learn from astro but it's most likely the same):
cp -r /mnt/sdcard/Startup.mp3 /system/sounds/lgeSounds/ (enter)
It worked fine. I'm kinda happy I figured out how to do this but I wanna make sure I didn't screw something up. I figure I can't be the only one annoyed by the t mobile noise at start up.
Next time just replace your mp3 file to system/sounds...poweron.mp3 is the name of the original file
Sent from my LG-P500 using xda premium
There are 2 files played when the phone is turned on. One is Poweron.mp3 and the other is Startup.mp3 and both are in a folder that is read only until you mount the drive as rewritable. So you can't just go in and delete it unless you have Root Explorer which has the ability to set the system file to rewritable...or do what I just said for free.
Exoplanetary said:
There are 2 files played when the phone is turned on. One is Poweron.mp3 and the other is Startup.mp3 and both are in a folder that is read only until you mount the drive as rewritable. So you can't just go in and delete it unless you have Root Explorer which has the ability to set the system file to rewritable...or do what I just said for free.
Click to expand...
Click to collapse
So you u think you have become a themer ..:banghead::banghead::banghead:
I've used blackbird rom b4 which is nothing more than a stocked rom. I took a mp3 file (mw3 mp3) placed it in the system/sounds folder, renamed that file to poweron.mp3 than changed permissions than booted, the mw3.mp3 file worked right along the call of duty boot animation. I only worried about one file not any others
Sent from my LG-P500 using xda premium
That's cool, JRhodes85. Yeah, I thought I had done something cooler that what I did cause I made the system folder rewritable with that app but somehow thought I had done it with all the coding cause after using it to make the folder rewritable it still didn't work with my file manager...only in terminal.
jazzzzzzz...? Why so serious? These are just phones, man.
Greetings! My apologies if I've posted in the inappropriate forum. The 3rd gen Fire 7" HD doesn't seem to have a home as yet.
I have rooted and had a working ES Explorer app. I noticed there was an upgrade to what I was using and figured I'd install it. That was a mistake. The newer version (which I was attempting to install directly from the Amazon store) didn't install properly because of the presence of the older. The older no longer worked so I removed (or thought I did) the app. My thought...let's reinstall my old one the way I did before, remove it properly, then try to reinstall the newer version.
I had used Android Injector to get the original on. I try it now and get the following error:
Command issued:C:\Program Files\Android Injector\adb.exe install C:\Installs\Kindle\ES_FIL~1.APK
pkg: /data/local/tmp/ES_FIL~1.APK
Failure [INSTALL_FAILED_ALREADY_EXISTS]
2330 KB/s (2833758 bytes in 1.187s)
I figure fair enough. I'll just use ADB shell and remove it. But there is nothing to remove!
[email protected]:/ # cd data/local/tmp
cd data/local/tmp
[email protected]:/data/local/tmp # ls -l
ls -l
-rwxr-xr-x shell shell 89968 2013-11-26 19:35 exploit
-rwxr-xr-x shell shell 188 2013-11-25 00:35 rootme.sh
-rw-rw-rw- shell shell 104564 2013-11-25 00:33 su
[email protected]:/data/local/tmp #
Any ideas on what I can do? It doesn't seem possible remove a file that doesn't seem to exist. I haven't done much to the system as yet. I've thought about restoring to factory defaults. However, my concern with that is that I've renamed /system/etc/security/otacerts.zip to /system/etc/security/otacerts.zip.old (effort to prevent OTA) and I've disabled the ads by renaming /system/app/dtcp_apk-release-signed_62320010.apk to /system/app/dtcp_apk-release-signed_62320010.apk.old --- if I try to restore to defaults, what are the chances I brick it due to those renamed files?
Or, I could rename them back if someone would be kind enough to offer me the exact command(s) to use in ADB shell so that I can get those files back to a state of being read/write instead of read only as they seem to be now? I'm comfortable with cmd line type stuff. I just don't have a 100% grasp on the exact syntax for some things -- this being one of them.
Any assistance much appreciated!
Files/Directories not hidden
It occurred to me as I thought about this today some more that maybe the file was hidden. So I check:
[email protected]:/data/local/tmp # ls -la
ls -la
-rwxr-xr-x shell shell 89968 2013-11-26 19:35 exploit
-rwxr-xr-x shell shell 188 2013-11-25 00:35 rootme.sh
-rw-rw-rw- shell shell 104564 2013-11-25 00:33 su
[email protected]:/data/local/tmp #
Ok...kills that idea. I don't understand why I'm being told a file exists that I can't see in any way.
DigitalVortex said:
It occurred to me as I thought about this today some more that maybe the file was hidden. So I check:
[email protected]:/data/local/tmp # ls -la
ls -la
-rwxr-xr-x shell shell 89968 2013-11-26 19:35 exploit
-rwxr-xr-x shell shell 188 2013-11-25 00:35 rootme.sh
-rw-rw-rw- shell shell 104564 2013-11-25 00:33 su
[email protected]:/data/local/tmp #
Ok...kills that idea. I don't understand why I'm being told a file exists that I can't see in any way.
Click to expand...
Click to collapse
My 2 cents. Did you check and see if it exists in the /data/app dir where it is installed to by default. check there or /system/app if you installed as root.
Sent from my KFTHWI using xda app-developers app
cdub50 said:
My 2 cents. Did you check and see if it exists in the /data/app dir where it is installed to by default. check there or /system/app if you installed as root.
Click to expand...
Click to collapse
Suggestion appreciated. I checked both places and nothing found that remotely resembles es explorer. I used the -la switch as well to make sure I wasn't missing anything as a hidden file.
I'm fairly stumped at this point and really don't mind setting it back to defaults. My only concern in doing that is making sure I don't brick it given the file renames I mentioned in the original post. I remain open to thoughts/ideas/opinions.
One other thing to try is open the amazon app store and check the cloud storage to see if you can restore the app from there.
Sent from my KFTHWI using xda app-developers app
I tried that in the early stages of recognizing the issue. And I'm wondering if my renaming the file to /system/etc/security/otacerts.zip.old is messing things up in that realm. The newer version of ES Explorer had failed to complete its install and showed on my screen with a little red '!" in the lower right of the icon. I tried to reinstall from the cloud and it wouldn't complete. I then proceeded to remove it from the cloud. The fun part after that is that the app's icon still shows on the Kindle with that "!" on it. I tried to go back into the app store to re-download. It tells me I can't and refers me back to my cloud storage.
Alright, thinking "out loud" here. I suppose if that file is causing this commotion, if I rename it back, there's the potential of everything returning to normal. To rename it back, I can only do that through the adb shell right now. The file perms are read only and if I try to chmod it, I can't because of the dir perms (I think). Would I want to do something like chmod -R 777 system/etc/security/otacerts.zip.old rename and then same command with 644 to set it back? Directories are usually 755 from my recollection. That's why I'm just a little confused on what my syntax should be to rename that file from the command line. I know once I have write privilege I can just mv system/etc/security/otacerts.zip.old system/etc/security/otacerts.zip.
DigitalVortex said:
I tried that in the early stages of recognizing the issue. And I'm wondering if my renaming the file to /system/etc/security/otacerts.zip.old is messing things up in that realm. The newer version of ES Explorer had failed to complete its install and showed on my screen with a little red '!" in the lower right of the icon. I tried to reinstall from the cloud and it wouldn't complete. I then proceeded to remove it from the cloud. The fun part after that is that the app's icon still shows on the Kindle with that "!" on it. I tried to go back into the app store to re-download. It tells me I can't and refers me back to my cloud storage.
Alright, thinking "out loud" here. I suppose if that file is causing this commotion, if I rename it back, there's the potential of everything returning to normal. To rename it back, I can only do that through the adb shell right now. The file perms are read only and if I try to chmod it, I can't because of the dir perms (I think). Would I want to do something like chmod -R 777 system/etc/security/otacerts.zip.old rename and then same command with 644 to set it back? Directories are usually 755 from my recollection. That's why I'm just a little confused on what my syntax should be to rename that file from the command line. I know once I have write privilege I can just mv system/etc/security/otacerts.zip.old system/etc/security/otacerts.zip.
Click to expand...
Click to collapse
I don't think the cert is your issue as I had restored from a backup using safestrap and I had not backed up a game I had downloaded so I restored it from the cloud and I had moved otacert to another directory. Why not just try a different file manager?
Sent from my KFTHWI using xda app-developers app
[RESOLVED] Help: remove file that "doesn't exist" (KFSOWI)
That was a good idea. Trying something else doesn't mean I need to keep that...just a means to an end. So I did. I used that and renamed items to original. Rebooted. The weird stuff still existed - the "!" on the ES Explorer. I was just about to go for the restore when I noticed SYNC at the top of the list. I had never thought to try that. I sync'd the device. The "!" disappeared. I could download ES Explorer 3 from the cloud and this time it installed.
Lesson learned.
DigitalVortex said:
That was a good idea. Trying something else doesn't mean I need to keep that...just a means to an end. So I did. I used that and renamed items to original. Rebooted. The weird stuff still existed - the "!" on the ES Explorer. I was just about to go for the restore when I noticed SYNC at the top of the list. I had never thought to try that. I sync'd the device. The "!" disappeared. I could download ES Explorer 3 from the cloud and this time it installed.
Lesson learned.
Click to expand...
Click to collapse
Glad it's all working. I highly recommend using safestrap to do a backup in case you ever mess up you can restore. I have tested backup and restore and both work with safestrap. I had installed a .zip via twrp and was wedged and did a restore and everything is back to normal.
Sent from my KFTHWI using xda app-developers app
cdub50 said:
I highly recommend using safestrap to do a backup in case you ever mess up you can restore. I have tested backup and restore and both work with safestrap.
Click to expand...
Click to collapse
You're successfully using safestrap on the 3rd Gen Kindle Fire HD 7 then? Just making sure because the more stuff I read in here, the more differences I find between mine and my kids' 2nd Gen HD 7's. I found another example tonight....I have Lookout on their Kindles and it won't run on mine. Anyway, thanks again for the help!
DigitalVortex said:
You're successfully using safestrap on the 3rd Gen Kindle Fire HD 7 then? Just making sure because the more stuff I read in here, the more differences I find between mine and my kids' 2nd Gen HD 7's. I found another example tonight....I have Lookout on their Kindles and it won't run on mine. Anyway, thanks again for the help!
Click to expand...
Click to collapse
Using SafeStrap on Kindle Fire 7" HDX (Thor). Just waiting on a ROM to flash so I get rid of Fire OS not a big fan and I would rather have the google app store amazon app store just doesnt have much selection IMO.