Related
Recently when I put APK's on my SD Card and try to install them I receive the 'Application not Installed' error. When this happens with market apps it's easy enough to unmount the SD and remount after the install. However if the APK is on the SD how can I do this?
Is there a fix for this? Also if it helps I'm running the Wildpuzzle ROM and the APK I'm trying to install at the moment is Angry Birds (getjar).
Have you try settings > application and check Unknown application.
Sent from my HTC Wildfire using XDA App
CoaBalboa said:
Have you try settings > application and check Unknown application.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Yeah, the application installer shows up, I just receive the error message a few seconds of the scrolling grey progress-style/working bar.
Do you have a USB Cable? Try using "DroidExplorer", an awesome PC client that can directly install apps. Or, try using a File Browser like Root Explorer or Super Manager.
Do you, by chance, have an App2SD Patch? Because I have always found them buggy!
Try to "undo" everything you did up to before it stopped working. Also try formatting your cache partition and/or erasing dalvik cache. Did you do any flashing without making a NANDROID backup first?
Also try "SuperOneClick", there is an option to "Enable Non-Market Apps" for rooted phones.
Second-last resort? Factory reset. Last resort...? Backup all your apps/settings and reflash
jonusc said:
Do you have a USB Cable? Try using "DroidExplorer", an awesome PC client that can directly install apps. Or, try using a File Browser like Root Explorer or Super Manager.
Do you, by chance, have an App2SD Patch? Because I have always found them buggy!
Try to "undo" everything you did up to before it stopped working. Also try formatting your cache partition and/or erasing dalvik cache. Did you do any flashing without making a NANDROID backup first?
Also try "SuperOneClick", there is an option to "Enable Non-Market Apps" for rooted phones.
Second-last resort? Factory reset. Last resort...? Backup all your apps/settings and reflash
Click to expand...
Click to collapse
Thanks for this. I'm trying Droidexplorer, explorers on the device wont install the apk as it returns the same error.
How long should the installation take. It's been running 15 mins so far, the internal storage has decreased a little but the installing window (on pc) is still up?
I am assuming you have a rooted phone with unrEVOked3 right? Would you happen to have some kind of App2SD patch installed....? Because I always found them unstable.... what firmware are you using? I am loyal to Sunaabh v1.1 (Froyo) Custom Firmware as it is well supported
Hmmm I've encountered that installing loop before. But only when trying to install an APK that wouldn't normally work, such as an older version of the Market or Flash 10.1. It just means it's waiting for ADB server to do something but ADB has obviously crashed. It should not take more than 30 seconds for an APK to install via DroidExplorer. Just unplug your phone and close DroidExplorer.
Does this happen with all APK's? How many have you tried?
Only thing I can think of is that you did something to damage your package.xml data and/or permissions are corrupted.
Did you try formatting your cache partition in Clockworkmod? Please try this, it will not destroy any data. But it will trigger a long reboot - it will appear frozen at the bootup splash screen but just let it go while it rebuilds the cache.
Also try "Clear Data" under Applications > Manage > Market.
Have you flashed anything in clockworkmod? If you can provide more details of exactly what you've done to your phone that might help, but I really doubt it.... I think the only option is to restore from a Nandroid Backup or Reflash Sorry... but these things do happen and we always learn the hard way lol....
You can use the official HTC Sync software to backup your phone numbers and SMS and stuff I believe, and if you want to backup your installed apps you can use Titanium Backup or many other Backup apps on the Market, Free or Paid.
Make into a zip file and flash via recovery
Sent from my HTC Wildfire using XDA App
Thanks for everyones help, I now have it sorted!
I started an installation through Droid explorer and then cancelled it when the apk was on the phone.
Then I unmounted my SD
Then I used root explorer to browse to the apk on the phones internal memory
It installed with no worries and I remounted the SD!
WillKennerley said:
Thanks for everyones help, I now have it sorted!
I started an installation through Droid explorer and then cancelled it when the apk was on the phone.
Then I unmounted my SD
Then I used root explorer to browse to the apk on the phones internal memory
It installed with no worries and I remounted the SD!
Click to expand...
Click to collapse
Haha, how very odd! Regardless, good to hear you got it sorted
EDIT: If it happens again, maybe you could try to format the SD card. Might be possessed with some bad stuff in the .android_secure folder or something.
When trying to update Titanium Backup through Play Store it fails telling me that theres no more space left. However 9 GB of internal and 3 GB of external SD card are still free. Other applications (even bigger ones) install fine. I cleared Dalvik cache but without success.
What causes this error and how to solve it?
Is your device GS3? 9GB of internal?
Is it important how did i send this?
Try to remove current TB & then install the newer version
Is it important how did i send this?
I uninstalled TB and now I can't install it again with the same error.
I still have 9 GB free on phone and 3 GB on microSD.
nolf5xpwm said:
When trying to update Titanium Backup through Play Store it fails telling me that theres no more space left. However 9 GB of internal and 3 GB of external SD card are still free. Other applications (even bigger ones) install fine. I cleared Dalvik cache but without success.
What causes this error and how to solve it?
Click to expand...
Click to collapse
I had the same kinda problem, I had 6 gig of internal storage left and it was gone. It was a room back up that took all the 6 gig. Don't know why tho....
Sent from my GT-I9300 using Tapatalk 2
I experience the same. Hmm.
i had this problem yesterday when updated my firmware, most of my apps had to be reinstall. there is one app, UCCW, i had to reinstall through google play and it keeps telling me i have insufficient memory.
To fix this i had to uninstall, use root explorer find the folder of the app and deleted it if it still there and reinstall. viola it works.
ph3nom said:
i had this problem yesterday when updated my firmware, most of my apps had to be reinstall. there is one app, UCCW, i had to reinstall through google play and it keeps telling me i have insufficient memory.
To fix this i had to uninstall, use root explorer find the folder of the app and deleted it if it still there and reinstall. viola it works.
Click to expand...
Click to collapse
I think i have posted a fix a lot of times for the same problem..see if this works for you.. open root explorer..it works only if you are rooted.. open data.. then open apps.. then try to find if there is any odex file related to titanium backup. It mite be named titanium keramidas.odex or something like that.. delete it.. then install titanium again..
Using Root Explorer, go to /data/app and delete the file named Titanium.odex
Now everything should work normally..
Sent from my MB525 using Tapatalk 2
Had same problem and did pretty much same as chillz said above, I store backups on pc so I just moved mine from phone to pc.
sent from my SGS3 Using XDA app
Deleted the odex file and everythings fine.
Thank you very much
ive deleted everything i can find relating to tianium backup . still no joy . a search in root explorer finds nothing
dazzzdelux said:
ive deleted everything i can find relating to tianium backup . still no joy . a search in root explorer finds nothing
Click to expand...
Click to collapse
I got this problem when I used lucky patcher to patch the previous Titanium backup app and uninstalled it but xxx.odex still file left(may be name "com.keramidas.TitaniumBackup-1.odex" . Use Root explorer then go to /data/app and find that file then delete it,I think you should install Titanium Backup again.
zamth2001 said:
I got this problem when I used lucky patcher to patch the previous Titanium backup app and uninstalled it but xxx.odex still file left(may be name "com.keramidas.TitaniumBackup-1.odex" . Use Root explorer then go to /data/app and find that file then delete it,I think you should install Titanium Backup again.
Click to expand...
Click to collapse
awsome sorted mate , cheers
I can't use titanium backup anymore, everytime i run the app i get this:
Code:
Error
Sorry, I could not acquire root privileges. This application will *NOT* work!
Please verify that your ROM is rooted and includes Busybox, and try again
This attempt was made using the "/system/xbin/su" command
I'im running HWMOD's rooted firmware, with superuser "installed and updated", and also busybox "installed and updated". there's nothing wrong, but somehow i can't run titanium backup anymore somehow.
what can be the problem be please, i've googled it and i got no solutions whatsoever!
run the app root checker.
Also from someone who has been there, i dont think titanium works with our unit. Our unit has sd1 and sd2 and sd3. Titanium will backup to sd1, which is internal memory, you can see where this is going. I did a titanium backup, then full wipe, and lost everything because it was not backed up onto sd2...
nightanole said:
run the app root checker.
Also from someone who has been there, i dont think titanium works with our unit. Our unit has sd1 and sd2 and sd3. Titanium will backup to sd1, which is internal memory, you can see where this is going. I did a titanium backup, then full wipe, and lost everything because it was not backed up onto sd2...
Click to expand...
Click to collapse
I don't have to run ROOT CHECKER because i have already other root apps and they function flawlessly (SD maid, quick boot, Busybox installer...) but i run the ROOT CHECKER anyway and it says i do have root privileges.
i forgot to mention that i already used Titanium B to backup apps and data, everything was stored on the external sd card. i could also restore. after all this app is for all android devices.
hamdimo said:
I can't use titanium backup anymore, everytime i run the app i get this:
Code:
Error
Sorry, I could not acquire root privileges. This application will *NOT* work!
Please verify that your ROM is rooted and includes Busybox, and try again
This attempt was made using the "/system/xbin/su" command
I'im running HWMOD's rooted firmware, with superuser "installed and updated", and also busybox "installed and updated". there's nothing wrong, but somehow i can't run titanium backup anymore somehow.
what can be the problem be please, i've googled it and i got no solutions whatsoever!
Click to expand...
Click to collapse
Hi
Also running HWMOD's rooted firmware and Titanium Backup works perfectly well or me. I also have an
Advent Vega and I was able to transfer my SD card from it to the Media pad and restore apps from my Titanium
Backup on it to the Media pad.
Stransky
Sent from my VegaCream RC2 using xda premium
Stransky said:
Hi
Also running HWMOD's rooted firmware and Titanium Backup works perfectly well or me. I also have an
Advent Vega and I was able to transfer my SD card from it to the Media pad and restore apps from my Titanium
Backup on it to the Media pad.
Stransky
Sent from my VegaCream RC2 using xda premium
Click to expand...
Click to collapse
that's what makes the app perfect, BACKUP and RESTORE between different android devices.
have you updated superuser? this seems to have been the cause. Titanium Backup was working fine before I updated superuser and error message is the same as yours. currently i'm using MyBackups.
you can check HWMOD's thread for details as somone also has him about this already.
{SOLVED}
ferdz33 said:
have you updated superuser? this seems to have been the cause. Titanium Backup was working fine before I updated superuser and error message is the same as yours. currently i'm using MyBackups.
you can check HWMOD's thread for details as somone also has him about this already.
Click to expand...
Click to collapse
I solved it, the problem is that titaniumbackup is using the "/system/bin/su" command but the SU binaries are actualy installed in "/system/xbin/"
what i did is going to BUSYBOX and from there switching the install location to "/system/xbin/"
i tried "mybackups" but i prefer TB
hamdimo said:
I solved it, the problem is that titaniumbackup is using the "/system/bin/su" command but the SU binaried are actualy installed in "/system/xbin/"
what i did is going to BUSYBOX and from there switching the install location to "/system/xbin/"
i tried "mybackups" but i prefer TB
Click to expand...
Click to collapse
thanks hamdimo! will try your solution when I get home later.
btw, HWMOD just released HWMOD kernel 3.0.42 + custom updates and this issue was also addressed.
ferdz33 said:
thanks hamdimo! will try your solution when I get home later.
btw, HWMOD just released HWMOD kernel 3.0.42 + custom updates and this issue was also addressed.
Click to expand...
Click to collapse
I fear that my hack could led to believe that searching for the "su" binary only in predefined positions is a good thing ...
I still believe applications should gather the correct informations from the PATH environment variable, as good ol' *NIX does.
But as you said it's kind of addressed, let's hope the hack will have a story
These problems arise only if one updates the "Superuser" application past the 3.0.7 (with "su" binary 3.0.3.2).
That one version is the latest one working as expected.
And yes I am a bit sceptical about my own choice of including 3.1.3 instead of the 3.0.7 in my latest update.
The "su" binary executable alone has grown from a mere 22Kb to 380Kb and "apk" has doubled it's size too (1.5Mb).
Related to these changes in "Superuser" several applications does not work any more for many users and upgrades are needed.
The process of getting "root" privileges for any application has turned tremendously slow. From almost immediate to 2/3 secs. each time.
this solution worked for me
Since superuser is working and granting root permissions to other apps (except TB). Using root explorer, I tried renaming the original su file from /system/bin/su and replacing it (copy-paste) with the su file from /system/xbin
Reloaded TB and it worked =)
Actually i have no problem in my 1st install for titanium backup. but soe how i uninstall accidentally. when i reinstall, it prompt memory not enough but i hve abt 3.5 gb left. my fone is rooted S3. can anybody help. tks in advanced...
Hi,
I re-flashed my phone yesterday to the official 4.1.2 ROM (Spain), this was on Paranoid Android before, did a full wipe etc. All seems okay, rooted it, but the external SD card is read only, all files are marked as R, suspect this is also why titanium backup hangs restoring my apps. Never had any problems like this before and I can't find anything to fix this, it's driving me mad. Can anyone suggest a fix,
Thanks,
I managed to fix this with root explorer by re-mounting as r/w. titanium backup still hangs though
re-install TiBu.
Sent from the little guy
gastonw said:
re-install TiBu.
Sent from the little guy
Click to expand...
Click to collapse
not only TiBu hangs, Waze navigation cannot access SD card. no re-install helps, I've repartitioned SD, reformated, reflashed phone,
SD is not working the way it should
Hi, mines okay now following using root explorer. I installed and older version of TiBu from their website and it worked fine, this it was v 5.7 or something. Also I raised a support call and they suggested changing the app processing mode, haven't tried this as the older version worked so I'm going to stick with it.
Same problem here.
Apparently it is only in adb shell and only if I am not root. Apps and Terminal app can access without problems.
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
I have the same problem. Initially, I thought that the sdcards were not mounted (for su root) but that wasn't the issue.
TB will currently backup VIRTUAL items (e.g. Accounts, WiFi access points) which have the TB logo next to it. It seems to fail for all other items.
gale2000 said:
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
Click to expand...
Click to collapse
Same problem here. According to this post:
http://forum.xda-developers.com/showthread.php?t=2391363&page=7
the small app called sdfix could solve the problem. I haven't tried yet.
cr2069 said:
Same problem here. According to this post: http://forum.xda-developers.com/showthread.php?t=2391363&page=7 the small app called sdfix could solve the problem. I haven't tried yet.
Click to expand...
Click to collapse
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Anybody have luck with Helium?
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
iammudd said:
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Click to expand...
Click to collapse
Too bad, seems to be TB's problem. Waiting for any progress...The main reason I want rooting is to use TB, but it's not working...
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/ascend-mate2/orig-development/2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
iammudd said:
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
Click to expand...
Click to collapse
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
foltz61 said:
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Yes, fastboot boot TWRP_MT2-L03_RECOVERY.img allowed me to try it out first. If it had failed, then hopefully I would still have had the stock recovery. (After playing around with TWRP a bit, I DID eventually flash it.)
foltz61 said:
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
iammudd said:
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
Click to expand...
Click to collapse
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
Click to expand...
Click to collapse
Same problem and this also fixed it for me thanks
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
Click to expand...
Click to collapse
This workaround has been made obsolete. See next post:
I didn't know what the drawbacks are to using this folder so I was initially reluctant but I've given up and went down this path as well. However, I've reduced some permissions and here's what appears to be working for me:
Use ES Explorer to create the new folder and change its permissions to rwx for group and others. (I didn't need to change owners for any of the folders.)
Use ES Explorer to TEMPORARILY add read-only permission to /data for OTHERS.
Change TiBu backup folder location by manually navigating to the new folder.
Once the new folder has been selected, I restore /data to its original permissions. (The read permission was only needed temporarily for TiBu to find the new folder.)
Copying the files back to my PC, I can see that the zip files for the apks appear to have "reasonable" apk sizes (i.e. not zero-length as before).
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
kemonine96 said:
In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Click to expand...
Click to collapse
Thanks, this appears to have done the trick. It was very baffling when TiBu would work for some tasks but not others. Glad you stumbled onto this thread.
And another follow up for those using Helium or looking for an "adb backup" based solution
This device does not appear to include the full adb backup stack. From some limited testing tonight the pop-up prompt when running "adb backup' or using Helium Backup does not produce prompt on the device so it just fails. This is a known problem on some devices and it's too bad Huawei decided this wasn't a necessary inclusion.
kemonine96 said:
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
Click to expand...
Click to collapse
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
nrfitchett4 said:
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
Click to expand...
Click to collapse
Were you able to get adb backup to work at all? I never was able to get it to work.
I solved my titanium backup issues by going into SuperSU, then settings for SuperSU, and unchecked the mount namespace seperation box, then reboot
kemonine96 said:
Were you able to get adb backup to work at all? I never was able to get it to work.
Click to expand...
Click to collapse
It worked just fine for me. Used it to backup kids unrooted phones. That's been a couple years though.