Hi,
My original post was this: http://forum.xda-developers.com/general/xda-assist/question-to-install-apk-manually-t3183357. I was advised to put it here.
In linux we can extract a .DEB file and manually put each of its contents in its relative system directory, then it works just fine after a reboot (or logout-login process). Is there a way to do the same for the .APK files?
Thanks in advance,
Multimann2
It seems that if you have system restricted phone it's impossible for an user without any connections and experience to install system software
Related
I usually download my apks in my computer and send them to my phone so I could archive them or send them to friends easily. The problem is, their file names are very long and hard to read in the phone. If I rename the apk files, would it affect installation-wise, ie it will install as another 'version' of that app. So let say if i installed a renamed apk and update it with another version of the same app, would it interfere?
Hello all,
I have written a script to push as file to my TB and it works kind of...I just want to know why it is not functioning as it should.
Here is what I am attempting to do.
Since my HTC weather does not have my city listed and my weather is always way off, I hacked the HTC weather database to add my city. And it works great.
So I wanted to create a weather_update.zip to install using CWM to do all of this for me if I changed roms and to allow others to use it as well.
the file goes into the /data/data/com.htc.provider.weather/files directory.
My script mounts data, pushes the file, changes the appropriate permissions, then unmounts.
It works as intended because I can see the file using adb prior to reboot.
However, after a reboot, the file is overwritten by the original. I can even delete the file completely, reboot and it is rebuilt. So my modified file does not stick.
BUT, if I use root explorer and copy the file to the correct directory and change permissions, my modified file works even after a reboot.
I don't understand why it works one way but not another.
Is there a step I am missing in the updater-script?
Any help would be appreciated....
Thanks,
Scott
UPEngineer said:
Hello all,
I have written a script to push as file to my TB and it works kind of...I just want to know why it is not functioning as it should.
Here is what I am attempting to do.
Since my HTC weather does not have my city listed and my weather is always way off, I hacked the HTC weather database to add my city. And it works great.
So I wanted to create a weather_update.zip to install using CWM to do all of this for me if I changed roms and to allow others to use it as well.
the file goes into the /data/data/com.htc.provider.weather/files directory.
My script mounts data, pushes the file, changes the appropriate permissions, then unmounts.
It works as intended because I can see the file using adb prior to reboot.
However, after a reboot, the file is overwritten by the original. I can even delete the file completely, reboot and it is rebuilt. So my modified file does not stick.
BUT, if I use root explorer and copy the file to the correct directory and change permissions, my modified file works even after a reboot.
I don't understand why it works one way but not another.
Is there a step I am missing in the updater-script?
Any help would be appreciated....
Thanks,
Scott
Click to expand...
Click to collapse
I could be way off base here but wouldn't you have to recursively delete the original to keep it from rebuilding?
dbu said:
I could be way off base here but wouldn't you have to recursively delete the original to keep it from rebuilding?
Click to expand...
Click to collapse
LOL, what I was thinking too, but it doesn't seem to work, unless I am doing it wrong.
If I replace the file and reboot, the original rebuilds.
If I delete the file completely and reboot, the original rebuilds.
If I replace the file using root explorer after phone has booted and then reboot, my modified file sticks.
That is what I can't figure out. Why it sticks after OS has loaded but rebuilds if the same file is placed before reboot.
And I can't figure out where the file is being rebuilt from.
Uggggg.
Hi guys,
I'm currently trying to manipulate the file /data/system/packages.xml in order to make Android start one of my apps with another user id. However, this doesn't work because it seems that Android recreates the file completely when shutting down the system which means the old user id is being written back into the file.
Without rebooting, changing the file's contents (or even deleting it completely) doesn't do anything either, it seems that the contents are being loaded into the memory on boot.
What I need are your ideas on how I can make my app run as another user (or edit the file permanently) I need this because I want to access another app's non-exported service.
Thanks in advance!
edit: Even if I try editing the file and then shutting down the system unexpectedly (One X, holding down power for like 10 seconds without using the software shutdown), the file is being restored after reboot. When I check the file in CWM after a normal shutdown, it's also back to normal. So I guess Android rebuilds it on shutdown AND on boot.. or something?
edit2: I just tried the following: Rebooting into CWM, editing /data/system/packages.xml from there, checking file contents (worked), rebooting system - file contents restored. I'm starting to think that this isn't the file I have to edit. But which one is it?
edit3: Tried editing /data/system/packages.list instead, didn't work either. The file is also being restored to the original state.
- Android 4.1.1, CM10, German
did u managed anything?got same issue
Hi,
So the situations is like this:
Just got a new LG Nexus 4, NFC enabled, GREAT!!!!
But then I start using it, and the NFC sound (everytime the phone reads a nfc-tag it makes an sound) annoys me beyond belief.
So I start looking around, it seems there's no solution, except recompiling the app.
So I learn how to compile an app (noob here), using this guide: http://forum.xda-developers.com/showthread.php?t=1860115
I'm up to the point where my apk is decompiled, and I have modified the sound files, located in my decompiled files folder respectively at res/raw/start.ogg & res/raw/end.ogg.
I modded the files using audacity, lowering the volume to zero, used them to replace the original .ogg files. The file size is a bit smaller as the original ones (1Kb difference).
Next I use the recompile command: apktool b decompiled_apk_folder_with_modified_files modded_apk_file.apk
So now I have the new nfc apk file, called NfcNci.apk, with which I replace the original file in /system/app.
Next up I reboot my phone into recovery, wipe all cache and dalvik cache, and reboot again.
First thing that pops up on my screen is a force-close message, saying that the nfc-service force closed.
Anyone who can tell me what I did wrong? Or how I can fix this?
Attached are: my decompiled-files-folder (compressed to zip)
the original NfcNci.apk file
my modded NfcNci.apk file which causes the FC's.
Any help will be greatly appreciated!!!!
S.
Looks like you're still on 4.2
The latest NfcNci.apk has some more files.
And your apk is missing the META-INF folder.
I guess that this is the problem.
But you should use "adb logcat" to ensure we're on the right track.
Micky
1 thing i would recomend is not using the actual apk you just built. instead, open your new apk with a file manager such as 7zip and remove your newly compiled files out of it, then put them into the original apk from your rom using 7zip as well! thus keeping the apk's original signature
try to copy the least amount of files from one to another, so to be safe only pull out your new .ogg files, then put them into your original apk! hope this helps
ldrifta said:
1 thing i would recomend is not using the actual apk you just built. instead, open your new apk with a file manager such as 7zip and remove your newly compiled files out of it, then put them into the original apk from your rom using 7zip as well! thus keeping the apk's original signature
try to copy the least amount of files from one to another, so to be safe only pull out your new .ogg files, then put them into your original apk! hope this helps
Click to expand...
Click to collapse
Hi, I tried this, installed 7zip, and double clicked the original apk, I opende the res/raw/ directory, and only copied the files I was using: start.ogg & end.ogg. Then I close 7zip, and send the file to my phone. But as soon as I it them to /system/apps on my phone, and reboot to recovery, wiping the dalvik cache. I get FC's on reboot (NFC-service has FC'd).
Any reasons for this?
Thanks for the help, both of you!
BTW: I'm on Android 4.3 JB
Hello xda-developers,
I'm trying to figure out the proper way to transfer app data from an Android image disk. I'm very new to this, so I hope I'm not missing something basic.
Situation. I have a .img disk image file obtained from a .vmdk file via a virtualbox conversion , the latter being created by an Android emulator. I'm trying to recover some app data and transfer that to a new, working, .img disk. The emulator works on Android 4.4.2, if that matters.
What I did. I extracted apks and copied app data folders (com.<devname>.<appname>) from/to the /data/data directory. I did that using a file manager (ES file explorer) or via the cp command, as I found in many tutorials and guides. Others suggested to copy those folders to /Android/data instead, so I did try that as well. These procedures were ineffective, because they both messed up with folders and files permissions. Although cp -ar retains folders/files permissions and ownership, that was of no use after the import into the working image. Those operations were performed on Ubuntu 18.04.
The problem (and a workaround). When the apks are installed, a new uid (in the 10000 group) is generated for them. These values are unknown when I import the data folders, hence they are destroyed at phone boot. A log in /data/system/uiderrors.txt confirms this. The only way I could make it work was to install the apk from scratch, open the app so that the new data folders are created with a proper uid, replace those folders with old ones and manually change ownership and permissions accordingly (for every apk). This turned out to be effective but it's a very tedious and error-prone process.
What am I doing wrong? How do ADB push, pull and backup commands manage folders permissions/ownership and app uids? Could they be useful in my situation? If so, how can I use them on a .img file?
Thank you.