Related
Now I realise I am likely to be subjected to a torrent of mockery for this, but feel I should post it in the spirit of a public service announcement.
I needed to do a factory reset of my Galaxy S today (Froyo JPO via Odin - nice), and as a clever and forward thinking IT literate person thought it would be a good idea to back up my apps (if only to save my Angry Birds progress).
So I downloaded Titanium Backup from the Market, and used it to backup all my apps & and services with "useful data".
I then proceeded to do a factory reset using the handy code *2767*3855# (due to the minor snag of forgetting my Mobile Tracker password, and being unable to use the reset option in Settings)
arning 1 - This performs a reset as soon as you hit # - no "are you sure" or similar. Use with caution.
Once that had completed, all was good (messaging app was working again which was the reason for the reset), and I proceeded to reinstall Titanium Backup from the Market, and went to restore all my apps.
FAIL
Warning 2 - Titanium Backup saves it's backups on the internal SD card on a Galaxy S. This gets wiped by a Factory Reset, therefore saying Syonara to all your carefully backed up data. Whoops.
Now I will readily admit this is my own daft fault for not checking the backup location, and copying the data to my external SD card, but then "Experience is simply the name we give to our mistakes"
Here's hoping this prevents at least one other person making the same foolish mistake.
James.
Hangon, I'm 99% sure the internal doesn't get formatted using factory reset.. Well at least on my device (Aussy GT-I9000)
internal sd
stevles said:
Hangon, I'm 99% sure the internal doesn't get formatted using factory reset.. Well at least on my device (Aussy GT-I9000)
Click to expand...
Click to collapse
Today I did a Factory reset thiking I will los the data but the data is there. This confirm the 1% to complete de 100%.
Carlos
Data should still be there fella in 'sd' just move it into 'external_sd' same happened to me.
You should have really read the documentation before using the app
That being said, I have my backups stored on Dropbox so at least if anything happens I can restore it from the cloud.
Trust me guys - the TitaniumBackup folder on the internal SD was empty after the factory reset & reinstall.
That said - it's possible it was the reinstall that blanked it, although that would be even more daft.
Having not checked it during the process, I can't comment for sure when it went bye-bye.
It never happened to me. What about other files on your Internal SD? Did they get wiped out too or just the contents TitaniumBackup folder?
No idea, anyone experienced d1verjim's case? All I can think of is bug of TB that makes it "Delete all Backups".
---
"Experience is simply the name we give to our mistakes", but I think it's not your mistake this time, so hold on the 'experience' first! Gotta find the cause for that. TB is well-known for its stability.
I've been having this problem on and off for a while, mostly I believed it was related to something getting corrupted when I restored my apps to a new Rom with Titanium Backup.
I am happy to say, that after scouring the web for days, and trying a lot of wrong information, I finally figured out how to fix this.
It's real easy. All you need to do is remove any *.apk files located in the /cache directory on your phone (did not even need to remount- though I did it as root just in case).
I never did figure out why only some apps will have this problem or how the problem first comes about, but I have successfully done this twice and have since been able to install/update files that had this error before.
Update (3/3/11): OK - After scouring the Internet for over a month I finally figured it out. My info above was only part right. The problem is specifically with ROMs/Kernels that move the dalvik-cache to the /cache directory (HTC puts it in the /data dir).
In any case, when it's in /data, it is using app space, and therefore you usually run out of app space and know about it. However, because this is in /cache, you don't really know what you are using. As you load up on apps, your dalvik-cache grows, and since these apps need the .dex files in the cache, even if you clear your cache, it will just get re-created.
the /cache dir is also where the apps are temporarily stored while downloading from the market. So....
1. If you are getting immediate download fails, that means that your cache is so full that you don't even have space for the temp file.
2. If you get "Invalid Package" that likely means that there was not enough cache left to install the .dex files (the download is also taking up some of this space).
Unfortunately, the only way to fix this is to either remove some of your apps, or move your cache to your SD card.
HOWEVER, I found this great app on the market called Link2SD, that allows you to only move select apps to the SD card, and you can also move the dalvik-cache files associated with these apps.
see this thread for specifics: http://forum.xda-developers.com/showpost.php?p=10711328&postcount=1
it lets you select which apps to move. You will need to create a new partition on your card, though.
So far results have been great and I can finally update the 30+ apps that have been stuck for me for the last 2 months.
almost forgot, if you adb shell or use terminal emulator, you can type "df" to see how much space is left on all your mounts.
My phone has been doing the same thing with the whole package file is invalid bs. I tried to follow your instructions on going to the /cache folder. When I went to the folder, it was empty, so I wasn't able to remove any .apk files. So now what? How do I fix this?
If you use a File Managemet app like ASTRO, it will show the folder as empty because you need root access to see the dir. However, if you use Terminal Emulator or adb shell (as root) you will see that there are indeed other directories, and probably these orphaned .apk files.
Hi,
I'm also having the same issue with invalid package. I cleared the /cahch direcotry and still have the issue -- Is there something else i can try before wiping and starting over?
thanks
Rudey
It could also be caused by the .android_secure folder on your SD card. Clearing this folder and letting the market restore them solves issues a lot ofthe time.
As always use TiBackup or something to backup all your apps first too to be safe.
As the OP, I can tell you that I have, in fact, been unable to fix this problem.
Initially the suggestion I posted above worked, however a couple of days later is was no longer working again.
I have tried every trick on the web, including:
1. Removing SD card.
2. Deleting the above mentioned folder
3. clearing market cache
4. Clearing all caches in recovery
5. logging out and back in to google talk.
The only thing that fixes it is a complete factory reset.
I currently have a combination of 3 errors:
1. No download at all.
2. Download unsuccessful
3. Invalid Package
some apps will still update, but what is really weird is that I am even getting invalid package on new apps (so its not a corrupt app already installed on the phone).
One last thought. Once I am unable to update an app, even if I remove it, I can no longer restore the backup using Titanium.
oughta try reformating your SD card and let the phone reformat it too.
sgt. slaughter said:
oughta try reformating your SD card and let the phone reformat it too.
Click to expand...
Click to collapse
don't see why this is different than un-mounting the SD which should do the same thing and has been tried.
sw99 said:
don't see why this is different than un-mounting the SD which should do the same thing and has been tried.
Click to expand...
Click to collapse
na actually reformating it will fully wipe everything on the SD and having the phone do it is best always as its always better to format with the device your using the disk on the most in general.
Found the problem, updated in OP.
sw99 said:
I've been having this problem on and off for a while, mostly I believed it was related to something getting corrupted when I restored my apps to a new Rom with Titanium Backup.
I am happy to say, that after scouring the web for days, and trying a lot of wrong information, I finally figured out how to fix this.
It's real easy. All you need to do is remove any *.apk files located in the /cache directory on your phone (did not even need to remount- though I did it as root just in case).
I never did figure out why only some apps will have this problem or how the problem first comes about, but I have successfully done this twice and have since been able to install/update files that had this error before.
Update (3/3/11): OK - After scouring the Internet for over a month I finally figured it out. My info above was only part right. The problem is specifically with ROMs/Kernels that move the dalvik-cache to the /cache directory (HTC puts it in the /data dir).
In any case, when it's in /data, it is using app space, and therefore you usually run out of app space and know about it. However, because this is in /cache, you don't really know what you are using. As you load up on apps, your dalvik-cache grows, and since these apps need the .dex files in the cache, even if you clear your cache, it will just get re-created.
the /cache dir is also where the apps are temporarily stored while downloading from the market. So....
1. If you are getting immediate download fails, that means that your cache is so full that you don't even have space for the temp file.
2. If you get "Invalid Package" that likely means that there was not enough cache left to install the .dex files (the download is also taking up some of this space).
Unfortunately, the only way to fix this is to either remove some of your apps, or move your cache to your SD card.
HOWEVER, I found this great app on the market called Link2SD, that allows you to only move select apps to the SD card, and you can also move the dalvik-cache files associated with these apps.
see this thread for specifics: http://forum.xda-developers.com/showpost.php?p=10711328&postcount=1
it lets you select which apps to move. You will need to create a new partition on your card, though.
So far results have been great and I can finally update the 30+ apps that have been stuck for me for the last 2 months.
almost forgot, if you adb shell or use terminal emulator, you can type "df" to see how much space is left on all your mounts.
Click to expand...
Click to collapse
Didnt solve my issue.. I had reformatted my phone and SD card and reinstalled my apps. It was working fine again but now its back to some apps update fine.. some get DOWNLOAD UNSUCCESSFUL and some get PACKAGE FILE INVALID.. any ideas.. Im on sprint lovers rom (latest)
It appears th LINK 2 SD needs a second partition that I dont have nor use with SPRINT LOVERS ROM and 2.2 .... am I missing something??
To the OP,
The program you linked to seems to be a variation of dark tremor's a2sd method (http://forum.xda-developers.com/showthread.php?t=715116). His lets you move data, cache, and/or dc to the ext partition, but doesn't (at least I don't believe it does) give you granular control over which apps remain in the standard location.
In my own use, I chose to move all user installed apps to sd, but dc remained on the internal memory (albeit, not in /data, but in the /cache partition). I figured this way, even if the sd card is missing, the phone will still boot. I won't have access to anything I installed, but whatever the rom came with will still be accessible.
Follow the instructions on that thread and create the second partition. You won't need more than 500mb. apps2sd or link2sd is the only way you can fix this problem unless you want to remove some of your apps.
Sent from my PC36100 using XDA App
gpz1100 said:
To the OP,
The program you linked to seems to be a variation of dark tremor's a2sd method (http://forum.xda-developers.com/showthread.php?t=715116). His lets you move data, cache, and/or dc to the ext partition, but doesn't (at least I don't believe it does) give you granular control over which apps remain in the standard location.
In my own use, I chose to move all user installed apps to sd, but dc remained on the internal memory (albeit, not in /data, but in the /cache partition). I figured this way, even if the sd card is missing, the phone will still boot. I won't have access to anything I installed, but whatever the rom came with will still be accessible.
Click to expand...
Click to collapse
Yes that's true, and I eventually went the app2sd route. However, I was trying to avoid that because of the slow speed of my sd card.
Sent from my PC36100 using XDA App
sw99 said:
Yes that's true, and I eventually went the app2sd route. However, I was trying to avoid that because of the slow speed of my sd card.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm not sure which app2sd method you're referring to, but keep the following in mind. I discovered this after my backup images failed to restore properly.
In the past, i'd be backing up boot, system, and data partitions. Obviously with dt's a2sd, I need to include the ext partition now. No problem. BUT, when restoring, i'd run into issues where my apps were present, but all settings were lost. After much confusion and head scratching, I tried wiping cache and dc AFTER the restore, but before the initial boot. The restore was a success now!
Apparently, with a2sd on the ext3, some remnants of cache or dc remain when backing up, even if cache is not selected. As part of any good restore, first thing is to always wipe, so now we end up with a hodge podge of files in the cache which I think causes the OS to revert all the settings back to default.
Just something to keep in mind.
i wanted to go back how my dhd was.. lots of problem.. i havent fix my radio problem yet and now this invaled package thing *face palm*
My phone is HTC G7, and I use data2sd to get 1.5G rom space, now there is still about 1.2G left, but I also met the "invalid package file" problem. I can't find any *.apk in /cache, (root, with "ls -a"). But if I uninstall some apps, I could install or update other apps successfully. I could not use Link2sd for I already have data2sd and I guess it's not a problem of insufficient space, because I still have enough rom space.
Do you have any new solutions?
supericexu said:
My phone is HTC G7, and I use data2sd to get 1.5G rom space, now there is still about 1.2G left, but I also met the "invalid package file" problem. I can't find any *.apk in /cache, (root, with "ls -a"). But if I uninstall some apps, I could install or update other apps successfully. I could not use Link2sd for I already have data2sd and I guess it's not a problem of insufficient space, because I still have enough rom space.
Do you have any new solutions?
Click to expand...
Click to collapse
The problem is not the apps, its the /cache running out of space. I suspect that the app you are using cannot move the dalvik-cache files (and is really just a shortcut to android's app2sd - which is not the same as darktremor or link2sd).
in terminal us df -k to see how much space you have on each mount to confirm that there is little space in cache.
If you really have that much space in your apps mount, then I would suggest moving the dalvik-cache back to its original location (search for instructions, as the only way I know how to do it is by installing darktremor's app2sd). If you are still having problems, you really are limited to either partitioning your SD card and using apps2sd or link2sd or removing apps.
hope this helps.
I have been having this issue for a couple of months now - with a bit of a twist. After wiping my dalvik-cache, my apps began to sucsessfully update - except for Google apps.
I have no idea why just those apps, but going into settings/Applications/Manage applications, and selecting each app, then clearing that apps cache, allowed those apps to sucessfully update also.
I am thankful I did not have to resort to the above fix.
Any solution if not rooted?
I've just started to get this error when trying to update the Google+ app. The error is only happening with Google+, every other app I update/install works fine.
I haven't rooted my device, and I'm hoping there's a way to fix the issue without rooting?
Device: Nexus One
Rom: Stock Android
Version: 2.3.4
Although I couldn't see anything in the cache directories, I checked in /system/app and couldn't find any package that looked like it would be Google+.
I have a rather urgent issue, in which a factory reset wiped my sdcard. First of all, is that normal? This is my first device with no external microsd, and my first time using TWRP. Before, I had been using various versions of Amon-Ra or CWM, and when I factory reset they never wiped the sd card. Next, whether it was normal or not, I need a way to recover my data. I had around 8 gigs in sdcard before it got wiped.
To give you more background info on what was going on, I had a rooted 4.1.2 16GB Nexus, and I decided that I wanted to try PA. I made a nandroid backup of course, and then proceeded to flash the rom. I followed the instructions on the PA thread, first doing a factory reset followed up by the actual flashing, then a wipe of cache/davlik. After I tried the rom out for a few minutes, I noticed that there weren't any redeeming features to make it worth the time-consuming switch from stock to PA, transferring all my data and setting up my settings once more.
I rebooted back into recovery and factory reset again, and then I went to restore and saw that there were no backups. Suspicious, I went to the install menu, and found my entire sdcard folder had been wiped out. What happened?
Edit: I'm currently still on the recovery, afraid to do anything in case I lose my data forever.
Was your boot loader already unlocked or did you unlock it right before you flashed the ROM?
littleemp said:
Was your boot loader already unlocked or did you unlock it right before you flashed the ROM?
Click to expand...
Click to collapse
Thanks for the reply, especially on Christmas, but I got around the issue myself. It had been unlocked for 2 months now.
I noticed that every time I booted into recovery, it would make a "0" folder and move the contents of my sdcard into that "0" folder. Then the 0 folder would go inside another 0 folder, and so on and so forth. It was a really strange issue because I was unable to restore my backup; TWRP could not find my /sdcard/TWRP/backup folder, because it did not exist! It was in sdcard/0/0/TWRP/backup. I used the built in file manager in TWRP, and moved the contents back into the proper folder. I could then restore, and now I'm feeling relieved.
However, two issues remain; the 0 folders are still there, and storage transfer speeds seem very slow.
Edit: I got rid of the 0 folders by moving my folders out of them and then deleting the 0 folders, but the size of my files seem to have been inflated. What took up 6 gigs before is now taking up 8.8gb. Lol wut? Also, when I hook it up to a computer it tells me that 12GB has been filled. So many discrepancies.
androidwkim said:
Edit: I got rid of the 0 folders by moving my folders out of them and then deleting the 0 folders, but the size of my files seem to have been inflated. What took up 6 gigs before is now taking up 8.8gb. Lol wut? Also, when I hook it up to a computer it tells me that 12GB has been filled. So many discrepancies.
Click to expand...
Click to collapse
I am having the same problem. I think everybody has that problem, because it's caused by jelly bean 4.2 and its new emulated storage.
The only way I have found to get arround it was to copy all files on the computer from the sdcard, then formating the sdcard in recouvery and moving everything back.
Only problem I am having right now is that I can't for the love of it copy my files. Stupid MTP filesystem is really buggy and extremly slow. I constantly crashes or gives me multiple erros. The one I am having at the moment is something about a parameter error.
Very annoying the stupid filesystem under 4.2.
Btw. I can't get the adb pull command to work either. When I tell it to copy system/storage/emulated/legacy (I believe thats where the sdcard is actually loccated, right?!) it doesn't copy a single file.
If anybody could help me I would be very greatfull.
xaboren said:
I am having the same problem. I think everybody has that problem, because it's caused by jelly bean 4.2 and its new emulated storage.
The only way I have found to get arround it was to copy all files on the computer from the sdcard, then formating the sdcard in recouvery and moving everything back.
Only problem I am having right now is that I can't for the love of it copy my files. Stupid MTP filesystem is really buggy and extremly slow. I constantly crashes or gives me multiple erros. The one I am having at the moment is something about a parameter error.
Very annoying the stupid filesystem under 4.2.
Btw. I can't get the adb pull command to work either. When I tell it to copy system/storage/emulated/legacy (I believe thats where the sdcard is actually loccated, right?!) it doesn't copy a single file.
If anybody could help me I would be very greatfull.
Click to expand...
Click to collapse
I had the same fear, emotion and discovery a week ago when trying a new Rom thanks multi users feature .
You may try to switch from MTP mode to MSC in system setting to increase the speed.
Take care of the different tools because as example JROMFlasher will format the SD card for better cleaning. (I had backup!)
I think I read that the Factory Reset from the settings menu WILL erase everything.
Formatting with ClockworkMod, saves your sdcard files.
I also recommend unlocking asap just for laughs. Even if you don't plan on rooting or Modding... unlocking will ensure your files won't be deleted if you decide to or something happens that requires it
Sent from my Nexus 7 using XDA Premium HD app
Hi there,
i'm having some trouble with my S4, i9505.
I installed Resurrection Remix last weekend, and it hasn't been stable ever since. (cm-Resurrection_Remix_LP_v5.3.2-20150127)
In the beginning it would hold out for a few hours, but it started to reboot more and more frequently.
Finally, it would start to reboot, even whil rebooting into the recovery. Very annoying, and very hard to do anything.
I managed to restore to a nandroid backup from October 2014, but there's another problem.
I had installed that rom early in October It's Cyanogenmod 11.x.... Not sure exactly which version. I used the installer provided by cyanogenmod.org. That one has served me well for a long time, but lately I was having memory issues. I couldn't install new apps and even updating no longer works. I have >4GB free on my external SD, but installing apps to SD didn;t work. Moving apps to SD to make space was no go either. I kept getting "insufficient space" The operating system showed less than half the space on the internal memory was used. Lots of space left, but no space for apps apparently. ES file explorer doesn't think there's much space left on the internal SD. a few 100 MB max.
That's what tirgered moving to RR, but clearly that did'nt work well. I did a factory wipe from the recovery and cleared the cache.
What struck me is that the factory wipe isn't very thorough. Lots of data from apps was still accessible when Resurrection Remix was still behaving.
I tried to install cm-12-20150420-OPTIMIZED-FINAL-jflte.zip, but the installation quickly aborted saying it couldn't mount /system.
I managed to put my nandroid on the SD card and restored to the old situation, but the memory problems are still there.
In short, any idea what could be causing this behaviour?
and is there a way to do a complete and absolute wipe, so that any errors that may have accumulated over time will be erased?
I get the feeling that some link or redirection is wrong and the installs that I do get botched just a little bit.
Cheers,
Everything you are using is old and highly outdated.
1. Flash the latest TWRP from here:
http://teamw.in/devices/samsunggalaxys4internationalqualcomm.html
2.
Download the rom from my signature.
3.
Flash away and it will work fine.
Cool. Thanks. Will try that!
M
Hmmm. Didn't fix it.
OK. So I did that. ... As my phone thinks it's full, I had to do the install using terminal emulator.
Once that was done, it was smooth sailing.
Just started up again. But I only can get a few of the apps I used to have. I'm getting "device memory full" again.
I did the wipe function from twrp. Including wipe of Dalvik cache.
The "storage" item in settings says I have 397 mb available of 9.13gb, but visually the free space looks about 4 times larger than the .75 or so gb of data used by apps, etc.
Any ideas?
Menno
Mainow said:
OK. So I did that. ... As my phone thinks it's full, I had to do the install using terminal emulator.
Once that was done, it was smooth sailing.
Just started up again. But I only can get a few of the apps I used to have. I'm getting "device memory full" again.
I did the wipe function from twrp. Including wipe of Dalvik cache.
The "storage" item in settings says I have 397 mb available of 9.13gb, but visually the free space looks about 4 times larger than the .75 or so gb of data used by apps, etc.
Any ideas?
Menno
Click to expand...
Click to collapse
The memory full mesages is displayed when your internal storage is full. TWRP never wipes your internal storage. Delete the files manually or in TWRP select advanced wipe and select /data partiton.
Lennyz1988 said:
The memory full mesages is displayed when your internal storage is full. TWRP never wipes your internal storage. Delete the files manually or in TWRP select advanced wipe and select /data partiton.
Click to expand...
Click to collapse
Wow! thanks.
I went into TWRP and used the file manager.
Browsed around a bit and found a folder in /Data which belongs to Clockworkmod. The Cyanogenmod filemanager doesn't get there.
It basically had copies of all the nandroid backups I had made. with Clockworkmod. Not cool. I had made the backups to SD card, so apparently CWM forgot to delete these, or so.
Anyway, I deleted those folders and I'm back in business.
Cheers!
Issues after OtA
So..... just posting on my original thread. Hope someone is seeing this.
Last clean update went well... Apart from a few minor issues the wifi and bluetooth stability.
But since mid August my phone was nagging me about a new update being available. So I went for it finaly. Did OTA update 2 days ago.
Did not go well.
Gmail broken, Google Play crashing and bad wif stability.
Read around a bit on this forum.. Decided to do a clean install. MUCh better! :victory:
But... 2 issues remain...
1. my wifi doesn't seem to want to connect when I want it to. I always had issues with the wifi not connecting when the wifi strenght was not perfect, but since the August update, I can be standing right next to the AP and it's not connecting. My AP shows up right on top, and it just says saved. When I tap it and press connect, nothing happens. It does randomly connect every once in a while, for a couple of minutes... It works perfectly, great bandwitdh... and then nothing. It's not my AP. I'm posting from my laptop which has great connectivity. I put in the neighbour's wifi. Same thing.
2. How do I get rid of the Google search bar on top of the screen. Can't find it in the settings.
Oh. and when I switched over to cM12, I seem to have lost root access. How to get it bacK?
Cheers,
Menno
So I downloaded an update for Vemon Rom and went to flash it, I could remember the password I made for TWRP so I restarted my phone and ignored it, But the data on the phone got corrupted, I serarch online to see how to fix it and I saw Formating the userdata helps. So I did but now the phone is back to stock. I made a TWRP backup about a week before the update and now I can't find it no matter where I look, My SD card is merged with the phone memory, not sure if this info helped or am I boned and have to start completely fresh again?
Ragnell said:
So I downloaded an update for Vemon Rom and went to flash it, I could remember the password I made for TWRP so I restarted my phone and ignored it, But the data on the phone got corrupted, I serarch online to see how to fix it and I saw Formating the userdata helps. So I did but now the phone is back to stock. I made a TWRP backup about a week before the update and now I can't find it no matter where I look, My SD card is merged with the phone memory, not sure if this info helped or am I boned and have to start completely fresh again?
Click to expand...
Click to collapse
I'm not up to date on SD-Card merged. But formatting userdata wipes internal storage, so it's possible your sd-card got wiped on the process as well.
andybones said:
I'm not up to date on SD-Card merged. But formatting userdata wipes internal storage, so it's possible your sd-card got wiped on the process as well.
Click to expand...
Click to collapse
Well I tried looking for the backup before I did the Userdata wipe, also I'm sure it doesnt do internal storage, just system/data/cache its like a factory reset
Ragnell said:
Well I tried looking for the backup before I did the Userdata wipe, also I'm sure it doesnt do internal storage, just system/data/cache its like a factory reset
Click to expand...
Click to collapse
Sorry, Yea was thinking of something else.
Anyway nandroid are held in internal or sd-card foldwr: TWRP/BACKKUPS/serial#/name_of_nandroid
I'm sure you know this, however.
Sorry I couldn't be of any help.
andybones said:
Sorry, Yea was thinking of something else.
Anyway nandroid are held in internal or sd-card foldwr: TWRP/BACKKUPS/serial#/name_of_nandroid
I'm sure you know this, however.
Sorry I couldn't be of any help.
Click to expand...
Click to collapse
Rather gotten any helpful reply than none, thanks anyways bud
Formatting userdata is formatting the internal storage. If you had the Micro SD card added as adoptable storage, then your internal storage and Micro SD card can't be separated - what you do to one affects the other. So unless I'm misunderstanding something, all your storage got formatted.
Wiping doesn't erase your internal storage, but wiping alone wouldn't have solved your problem.