Database Develop

[Q] Market downloads: where are the files?

I was just wondering... when you download an app from the market, the apk file is clearly saved somewhere... but where? I mean, sometimes the download is successful, but the installation fails. instead of downloading the file again, I'd like to launch the downloaded apk and re-install directly. Anybody has a clue?

/system/data
EDIT: Oh, nevermind, I didn't realize you meant when the install fails.

If not on root/data/app than try root/mnt/asec/ and they have many folders wich have inner files that name "pkg.apk" but apk icon say about that file was installed...You can copy in external drive and change on original name.
Regards

miro666 said:
If not on root/data/app than try root/mnt/asec/ and they have many folders wich have inner files that name "pkg.apk" but apk icon say about that file was installed...You can copy in external drive and change on original name.
Regards
Click to expand...
Click to collapse
Thanks!

ZioGTS said:
...when you download an app from the market, the apk file is clearly saved somewhere...
Click to expand...
Click to collapse
/cache
The size of this partition may be the root of your install failed problems. When I first flash JVR, I hit the marked like a madman and just hit download on all the apps I regularly downloaded. The /cache partition quickly filled up and half of my installs failed. To make matters worse, the half downloaded files stayed in /cache and I had to manually remove them to regain the space (although I assume they would have been cleaned up next boot).
If the app installs successfully the apk is deleted from /cache and you can then find it in the locations mentioned by miro666.

Transfer system files to external SD card?

My motherboard is toast, I bought a broken phone on ebay and switched out the motherboards but it isnt working. Phone works fine but wont recognize sim card or connect to network. Its just a camera/wifi device atm. So anyway..... I can still get the old motherboard to kinda work enough to play with it, the home buttons dont work or the power button and sometimes freezes up. Is there a way I can put the old motherboard in the phone and copy the system files to the external sd card or computer, then wipe the new motherboard and copy the files from the old mb to the new mb? I believe I have tried everything else but if anyone has any suggestions Im all ears
Thanks!

The easiest way would probably be to take the motherboard you're wanting to pull stuff from, hook it up (in the phone), and via USB in ADB do something like this:
adb pull / \backup
That would create a folder at the top level of your C: drive with all the contents of the phone on it. You could then move all of that to the new motherboard.
(That would probably be something like:
adb push \backup /
but I'm not 100% sure on that. You may have to do a more one-by-one procedure.)

when I try to push the backup I get this message....
failed to copy '\backup/acct/uid/0/task' to 'acct/uid/0/task' : Operation not permitted
Sooooo what did I do wrong??
Also I couldnt find where it saved the backup on my computer.
Ok, found the backup folder on my c: drive but what do I do with it now?

Bump cause I still havent figured this out Seems like I dont have the correct permissions in adb.

poprocksncoke said:
when I try to push the backup I get this message....
failed to copy '\backup/acct/uid/0/task' to 'acct/uid/0/task' : Operation not permitted
Sooooo what did I do wrong??
Also I couldnt find where it saved the backup on my computer.
Ok, found the backup folder on my c: drive but what do I do with it now?
Click to expand...
Click to collapse
If you typed in your backup like what you wrote above (\backup/acct/uid/0/task), it's likely that you're running into an error because you flipped your slashes midway through.
The backup folder needs to be in the platform-tools folder of the ADB installation, as that's where ADB pushes from.
Once you have that, reboot into recovery mode. This may not be 100% necessary, but I usually find that pushes work better from there as the file system is (usually) read-write.
Then, try this:
adb push \backup /
(You may have to switch the slash before the word backup so it reads /backup, I'm not 100% sure.)
If that doesn't work, drag an individual folder out of the backup folder to the main platform-tools folder and type:
adb push /acct \
You'll have to repeat that for each folder, but it should work.
If all that fails, you can try to make a CWM flashable zip file. I don't know exactly what the procedure is for doing this, but I would guess that the answer exists somewhere on this site.

jmtheiss said:
If you typed in your backup like what you wrote above (\backup/acct/uid/0/task), it's likely that you're running into an error because you flipped your slashes midway through.
The backup folder needs to be in the platform-tools folder of the ADB installation, as that's where ADB pushes from.
Once you have that, reboot into recovery mode. This may not be 100% necessary, but I usually find that pushes work better from there as the file system is (usually) read-write.
Then, try this:
adb push \backup /
(You may have to switch the slash before the word backup so it reads /backup, I'm not 100% sure.)
If that doesn't work, drag an individual folder out of the backup folder to the main platform-tools folder and type:
adb push /acct \
You'll have to repeat that for each folder, but it should work.
If all that fails, you can try to make a CWM flashable zip file. I don't know exactly what the procedure is for doing this, but I would guess that the answer exists somewhere on this site.
Click to expand...
Click to collapse
Actually what I typed was adb push \backup / then it gave me that error. It stored the backup folder on my c: drive, I will move it to the tools folder and see if that works. Going to go search on how to make a CWM flashable zip file now. Maybe i'll give that a shot too. Thanks for your help.

So If I am getting this correctly, I take the custom ROM I have flashed to my phone and then I can add my system files to to the system folder in the ROM I can then flash the ROM again and it will install all my files?

In theory, yes, that should work. All the CWM update file does is write the files inside of it to the folders that the updater-script file tells it to.
Again, this should work IN THEORY.

poprocksncoke said:
So If I am getting this correctly, I take the custom ROM I have flashed to my phone and then I can add my system files to to the system folder in the ROM I can then flash the ROM again and it will install all my files?
Click to expand...
Click to collapse
Ok, I tried this and put the .zip on my sdcard and ran it from recovery. Got an error that I didnt have enough space. Any suggestions?

Database errors and unable to to sync sdcard folder: [SOLVED]

Hi,
Well I am running a build of 4.2 attempted to go back to 4.1.2 and having not read the articles on the sdcard symlinks, had issues. So I went back to my 4.2 build.
I then proceeded to move files to the correct folder and now In some apps (Astro File Manager, Dropsync) I am getting errors. Astro says Error Code 14 database error and Dropsync says folder not writeable.
I am thinking it has to do with symlinks but not sure how to fix.
Thanks
Kevin
[Edit]
it was a permissions issue. Just had to run some commands to fix data/media. for reference
http://forum.xda-developers.com/showthread.php?t=2222297 sdcard Fix Permissions script

Changing boot animation on Android M Preview 3

I tried to change the boot animation, running M Preview 3, and despite the fact that the flash claims to have performed successfully, it did not. I'm trying to flash the Marvel boot from the Themes and Apps section, and I know the flashable file worked on 5.1.1. It didn't overwrite the bootanimation.zip in /system/media. At one point, I was able to manually move the file there myselfusing Root Explorer, but I did not realize that the /system partiton did not have enough space to hold the entire zip file, so it was a corrupted zip at that point, and now my boot animation is just "android" in gray lettering. I cleared up enough space to hold the entire zip file of the marvel boot, but now I cannot move the file there, ES File Explorer and Root Explorer simply say it failed to copy.
I just tried to use adb to push the zip file from my computer, but it fails because /system is a read-only file system. So, I tried to remount with a shell as read-write, after some initial issues with apparently /system/xbin/mount not working properly, it did remount as read-write when using /system/bin/mount. But, adb push still fails because /system is a read-only file system.
Code:
mount | grep system
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
But, as you can see, it's mounted as read-write.
I, also, just tried to move the file as root in an adb shell, with no luck. A bootanimation.zip shows up in /system/media, but apparently it is corrupt because I cannot open it with root explorer, or in Windows when I pull it. When I try to move the boot animation that I want, the shell reports that there is not sufficient space, which is true now. The bootanimation.zip takes up 40MB of the 55MB of free space in the /system partition. Any time I try to delete the zip, it is automatically recreated before I have a chance to move anything in it's place, even when I do:
Code:
rm /system/media/bootanimation.zip | mv /storage/emulated/0/Download/marvelboot/system/media/bootanimation.zip /system/media/bootanimation.zip
So, what am I missing? Is it even possible to change the boot animation on Android M? Am I doing something wrong, or not doing something I need to?

why flash it? its a boot animation.. extract it from the zip, then pkace the bootanimation.zip into /system/media/ then just reboot. thats all it takes.
edit.. i didnt read ypur whole post and realuze that yoh have other issues.

Yeah, I wish it was just as easy as flashing or moving the zip file to /system/media/... Normally it is, but with Android M there seems to be a problem?

cappiez said:
Yeah, I wish it was just as easy as flashing or moving the zip file to /system/media/... Normally it is, but with Android M there seems to be a problem?
Click to expand...
Click to collapse
no, no problem here. do you have full root? i mean do you have the ability to edit anything in /system/?

Everything seems fine according to root checker. And, if I make small changes to my build.prop (Just editing build.id), the changes stick after a reboot. Soooo.. Yes?

cappiez said:
Everything seems fine according to root checker. And, if I make small changes to my build.prop (Just editing build.id), the changes stick after a reboot. Soooo.. Yes?
Click to expand...
Click to collapse
so you fo have full root. i use root explorer to put animations into /system/meda/, havent had any issues. does that animation work on a n6?

It worked on 5.1.1. Since I moved to the M Preview 3 builds, it appears to have stopped working.

cappiez said:
It worked on 5.1.1. Since I moved to the M Preview 3 builds, it appears to have stopped working.
Click to expand...
Click to collapse
nope. im on m preview 3, and it works fine here.

Boot Animation issue in 6.0.1

I've updated my device today to 6.0.1 and rooted, however I can't seem to change the boot animation (yes, I have searched for answers and tried quite a few fixes).
Root Explorer tells me I have renamed the old file and copied the new file, however once I leave the directory and go back the old file is still there.
I have used the file explorer in TWRP and managed to delete the stock boot animation, but get a FAILED message when I try to copy the new file.
I used the terminal in TWRP and tried to copy the file manually, and receive a "No space left on device" message.
I've also tried mounting the /system as rw in adb. I can delete the bootanimation.zip file from there, and df -h shows 3mb free. Shouldn't the system partition have more space available than that?
Am I missing something, or has something changed with the new android versions?

Google has filled the system partition up to the brim. Also you can't remount system as rw while Android is running.
But the direction is right, go to TWRP, mount system, delete the old bootanimation. If the new one is not that much bigger then you could just copy it there, set permissions to rw-r--r--. But if the new animation is significantly bigger, you'll have to delete some bloatware first.

Thanks for that. The odd thing is, when I run DF in the terminal, it shows I have 20mb free. The boot animation file I am trying to copy is 6mb.
I'll keep poking around. If it doesn't work, it doesn't. It's not hugely important