Database Info

titanium backup keeps crashing

currently on the newest stock rom and rooted, and i seem to be unable to run ti backup. it crashes immediately after launch. the only fix i've seen is to clear google play's cache/data and it didn't seem to work for me.
Sent from my Transformer TF101 using Tapatalk 2

Awhile back there was an issue which could be fixed by uninstalling then reinstalling the Pro key. Perhaps that will fix your issue.
Sent from my Transformer TF101 using Xparent Purple Tapatalk 2

thanks, but sadly, still crashing.
_________
i checked out the authors website. to inquiring minds, there was folder in my sd card called data/com.keramidas.TitaniumBackup which i deleted as per the website's instructions. that seems to have done the trick.
Sent from my Transformer TF101 using Tapatalk 2

Install "Busybox Installer" from Google play and try Titanium again...

jef_k said:
Install "Busybox Installer" from Google play and try Titanium again...
Click to expand...
Click to collapse
And if it says no root access while trying to install the newer version of busybox via the app, just try it again. I had the freezing problem while doing batch ops in addition to issues with gesturecontrol so i decided to update the busybox binary, failed the first time but when i tried it again the install went through.

Asus's Backup App won't open restore files?

I backed up my apps using Asus's App Backup Program.
But when I try to restore an app, it won't open file no matter what password I try to enter, which I never set a password to begin with.
I tested this issue by just backing up one app with no password set and then trying to restore and once again it won't open the file.
Thanks
Rob
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2!

Worked for me when i went from a 16 to 32.
I did set a password though

rlanza1054 said:
I backed up my apps using Asus's App Backup Program.
But when I try to restore an app, it won't open file no matter what password I try to enter, which I never set a password to begin with.
I tested this issue by just backing up one app with no password set and then trying to restore and once again it won't open the file.
Thanks
Rob
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2!
Click to expand...
Click to collapse
When I backed up an app (in order to use sparky root) I'm pretty sure I was forced to enter a password for the backup. Are you sure you were able to have no password?

TXKSSnapper said:
When I backed up an app (in order to use sparky root) I'm pretty sure I was forced to enter a password for the backup. Are you sure you were able to have no password?
Click to expand...
Click to collapse
I actually ran several tests, by just backing up one app for speed. I ran one test without entering for a password and another test using a simple 4 number password which is the minimum allowed.
The backup app would not open any of the backed up files?
Can you try testing it out for me? Just backup one file, with or without a password. Then try to restore it. See if it will open the file to start the restore process.
Thanks
Rob
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2!

your problem solved?

Jelly Bean firmware update failure thread

Starting from 30 firmware. It's a week old and it upgraded from 28 to 30 when I took it out of the box last week. It's rooted, but still locked.
I got a red triangle over the open stomach. It recovered to 30 and now won't recognize that an update is available.

Same here, my friend had a similar issue with his prime on Friday, ill try the same process on mine then get back.
Sent from my ASUS Transformer Pad TF700T using xda premium

posted this in the other thread already but i'm pretty sure you just need to go into DMClient / CMClient and clear data/cache and recheck.

Sorry for hitting multiple threads. I did have a tweaked build.prop. I just did a reset. I have to search for that cache folder.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jimbob_sf said:
Sorry for hitting multiple threads. I did have a tweaked build.prop. I just did a reset. I have to search for that cache folder.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
yeah it seems when an update fails, build prop changes or frozen apps are the reasons the majority of the people have their update failed. There should be a sticky at the top of XDA's tablet sections to revert any build prop changes and to unfreeze any apps before starting the update. I think some folks said if you wait a day or so it might work.. or clearing caches.. if i find the posts i'll put them in here

jyan_osu said:
yeah it seems when an update fails, build prop changes or frozen apps are the reasons the majority of the people have their update failed. There should be a sticky at the top of XDA's tablet sections to revert any build prop changes and to unfreeze any apps before starting the update. I think some folks said if you wait a day or so it might work.. or clearing caches.. if i find the posts i'll put them in here
Click to expand...
Click to collapse
yea. you need need the stock build prop when you update. and i would re-enable all the apps before update just to be safe. i don't remember seeing any confirmation as to whether or not that is necessary or for which apps it is necessary but you can just disable them again afterwards.

I renamed all 4 dmclient and cmclient files and now it won't show the system update option. Going to try some more stuff.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

fatpandas said:
posted this in the other thread already but i'm pretty sure you just need to go into DMClient / CMClient and clear data/cache and recheck.
Click to expand...
Click to collapse
Didn't work for me, neither did copying dlpkgfile to cache and creating a command file under /cache/recovery/ (what my friend did on his prime, it worked for him). I didn't get a new update when I checked with the Clients wiped and it stalled at red android when I did the cache method, ill try reflashing .30 later incase I did make any os changes I don't remember.
Sent from my XT894 using xda premium

I am stock rooted. I have not modified the build.prop and I have no frozen apps.
Here is the log of my failure from last_log (located in /cache/recvoery)...
Verifying Current System...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed" apply_patch_check("/system/build.prop","md5 hash","md5 hash")
E: Error in /cache/dlpkgfile
(Status 7)
Installation aborted

Did you guys check last_log in the cache folder...I think it's in a subfolder, can't remember. It should tell you exactly what failed
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

jimbob_sf said:
I renamed all 4 dmclient and cmclient files and now it won't show the system update option. Going to try some more stuff.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
renamed them? guessing you changed them sometime earlier to stop them? i just know they need to be there in stock condition to get the update.
moah909 said:
Didn't work for me, neither did copying dlpkgfile to cache and creating a command file under /cache/recovery/ (what my friend did on his prime, it worked for him). I didn't get a new update when I checked with the Clients wiped and it stalled at red android when I did the cache method, ill try reflashing .30 later incase I did make any os changes I don't remember.
Sent from my XT894 using xda premium
Click to expand...
Click to collapse
can't really comment on the manual method as i haven't tried it. if you're going to reflash, might as well just do a factory reset first (i think it's easier). someone else will probably pop in soon with some other ideas but from what i know, make sure you have stock buildprop, enable all apps, clear data/cache for CMClient and DMClient and recheck.
and for the dlpkgfile, then just make sure you have the proper version (US or WW)

If you already downloaded the update and it failed with the red triangle during update, is the file already on the infinity? If so how do I update it, because it is not showing an update now?

just wait for it to show up again.
next time grab the file from the cache folder before updating.

I'm in the same boat, (rooted TF700), installed the update but got the red triangle. Also after system reset I get no update available.

I forgot I had some frozen apps. Thawed them out, now I need it to show up again....Frustrating.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2 Beta-5

Could someone clarify the steps needed? I was rooted and the update failed so I did a factory reset and now no update shows I've cleared the data and cache from CM and DM client but no dice.
This drama is just reminding me why my phone and even my router run non OEM firmware and OS.

Anyone know what this means, why it has happened, and how I can remedy it?
I am rooted, locked and haven't frozen any apps.
What is Vibe_CN.apk? Sounds a bit like it tries to verify a CN (Chinese) version. The file exists, and from the icon, it appears to be @vibe Fun Center, and in my Titanium backup, it is listed as 3.2.1.1872 (38) (updated). There are no backups made of this, and when I press on it in TB, it gives me the option to Freeze (which I assume means that it isn't already frozen).
Anyone who can help me? I'm on the WW update (or at least should be )
Verifying current system...
file "/system/app/Vibe_CN.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/Vibe_CN.apk", "c36a7d96df630bfa6ab4e6a9484ac71f88d7c677", "297e177c2fd02d277792fe9b23b57c31ab67642c")
assert failed: apply_patch_check("/system/app/Vibe_CN.apk", "c36a7d96df630bfa6ab4e6a9484ac71f88d7c677", "297e177c2fd02d277792fe9b23b57c31ab67642c")
E:Error in /cache/dlpkgfile
Sent from my Asus Eee Pad Transformer Infinity TF700T

No files posted to the ASUS support site either

Same error here, any solutions? Rooted .30, failed upgrade, system reset didn't work and neither did facture reset, clear caches etc.

Well, i tried to restore the build.prop to stock and it sat on the spinning circle during the boot animation. Downloaded and installed the stock image (what I had anyway b/c not unlocked) to the SD card as EP201_768_SDUPDATE.zip, it installed it, but it still sits at the spinning circle. I'm thinking it may be hosed.
Anyone have the stock build.prop file (exactly as it appears in a text editor) they can paste here in the thread? Yes I can search, but if anyone has the adb push command to drop the file, that would be great too.

[Q] "Android is upgrading" on every boot [solved]

Every time I boot I get android is upgrading. I already tried cold booting but that doesn't seem to fix a problem. Is anybody else having this problem and were you able to resolve it?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

cromanorn said:
Every time I boot I get android is upgrading. I already tried cold booting but that doesn't seem to fix a problem. Is anybody else having this problem and were you able to resolve it?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Did you freeze any system apps like launcher, browser??

Nope. Other than being rooted I haven't modded anything
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

cromanorn said:
Nope. Other than being rooted I haven't modded anything
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Did you have Tibu backup software installed?

After thinking about it I did have one app frozen which I unfroze, rebooted and I still get the message. I'm rebooting again. Yes, I have titanium.
Sent from my DROID BIONIC using xda app-developers app

I uninstalled titanium and I do not get the message anymore.
Thanks
Sent from my DROID BIONIC using xda app-developers app

This happened to me once after installing/uninstalling apps
Sent from my Transformer Pad Infinity TF700T using Tapatalk 2

cromanorn said:
I uninstalled titanium and I do not get the message anymore.
Thanks
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
After uninstalling Titanium will not appeared that message.
Titanium reinstalling the message back or not?
What did you do? You ran out of titanium?

just find a way to solve this problem,
Use root explorer to go to system/framework
delete "com.google.widevine.software.drm.jar"
then you are good~

MarkAndroid said:
After uninstalling Titanium will not appeared that message.
Titanium reinstalling the message back or not?
What did you do? You ran out of titanium?
Click to expand...
Click to collapse
I could be mistaken, but if you use Titanium to make an "update.zip" in the root directory of your Internal storage, the system thinks you want to "upgrade" every time you boot. At least this is true if you boot into recovery. I've installed a backup this way before.

sls19061 said:
just find a way to solve this problem,
Use root explorer to go to system/framework
delete "com.google.widevine.software.drm.jar"
then you are good~
Click to expand...
Click to collapse
You shouldn't been doing that. This problem is often caused when gapps package is installed over an odexed stock ROM which includes com.google.widevine.software.drm.jar (and its correspondent .odex file). Now, taking into consideration that gapps includes the deodexed .jar, when it is installed you get the "Android is upgrading..." message on every boot.
If you want to do it properly, you should either stick to the stock .jar (as well as the .odex file), or if you prefer the one it is included in gapps package, you should then delete the .odex (/system/framework/com.google.widevine.software.drm.odex).

I tried to remove the two files (com.google.widevine.software.drm.jar and com.google.widevine.software.drm.odex), but it also continues to restart the procedure "upgrade android" at the start ...
What else should I take??

MarkAndroid said:
I tried to remove the two files (com.google.widevine.software.drm.jar and com.google.widevine.software.drm.odex), but it also continues to restart the procedure "upgrade android" at the start ...
What else should I take??
Click to expand...
Click to collapse
What's you setup?
Rooted? Stock? Unlocked with custom ROM?
Something seems to be wiping your Dalvik with each boot....
If you are rooted with Titanium Backup installed: Uninstall TiBu, reboot, reinstall TiBu and see if that fixed it.
If it didn't and you are on stock, I would re-flash the stock rom. Something got messed up in the system. It's probably easier to re-flash the stock firmware and root again than trying to find the culprit.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

MarkAndroid said:
I tried to remove the two files (com.google.widevine.software.drm.jar and com.google.widevine.software.drm.odex), but it also continues to restart the procedure "upgrade android" at the start ...
What else should I take??
Click to expand...
Click to collapse
Did it started to happen after installing gapps? If so, please check if your stock ROM also contains com.google.android.media.effects.jar (and .odex). The explanation is the same as before.

bgcngm said:
Did it started to happen after installing gapps? If so, please check if your stock ROM also contains com.google.android.media.effects.jar (and .odex). The explanation is the same as before.
Click to expand...
Click to collapse
I don't remember if this happened after installing gapps or after I OTA to 4.2.2 on my HTC one -- installed gapps pretty soon after OTA anyhow.
Tried to delete (/system/framework/com.google.widevine.software.drm.odex) but it re-appeared after reboot. There is also a com.google.android.media.effects.jar but no .odex.

I deleted both .jar and .odex and it's not show the number of apps to be upgrading but it show just android is upgrading.
bgcngm said:
You shouldn't been doing that. This problem is often caused when gapps package is installed over an odexed stock ROM which includes com.google.widevine.software.drm.jar (and its correspondent .odex file). Now, taking into consideration that gapps includes the deodexed .jar, when it is installed you get the "Android is upgrading..." message on every boot.
If you want to do it properly, you should either stick to the stock .jar (as well as the .odex file), or if you prefer the one it is included in gapps package, you should then delete the .odex (/system/framework/com.google.widevine.software.drm.odex).
Click to expand...
Click to collapse

bgcngm said:
You shouldn't been doing that. This problem is often caused when gapps package is installed over an odexed stock ROM which includes com.google.widevine.software.drm.jar (and its correspondent .odex file). Now, taking into consideration that gapps includes the deodexed .jar, when it is installed you get the "Android is upgrading..." message on every boot.
If you want to do it properly, you should either stick to the stock .jar (as well as the .odex file), or if you prefer the one it is included in gapps package, you should then delete the .odex (/system/framework/com.google.widevine.software.drm.odex).
Click to expand...
Click to collapse
Sir I only experience the "Android is Upgrading" every time i flash or install a zip file. Im using STOCK ROM, rooted, kernel with init.d support.
will your post be the solution to my query? or its on another topic?
TIA

If that is only after installing a .zip it is normal. It is because Dalvik cache is being created for the new app.

bgcngm said:
You shouldn't been doing that. This problem is often caused when gapps package is installed over an odexed stock ROM which includes com.google.widevine.software.drm.jar (and its correspondent .odex file). Now, taking into consideration that gapps includes the deodexed .jar, when it is installed you get the "Android is upgrading..." message on every boot.
If you want to do it properly, you should either stick to the stock .jar (as well as the .odex file), or if you prefer the one it is included in gapps package, you should then delete the .odex (/system/framework/com.google.widevine.software.drm.odex).
Click to expand...
Click to collapse
HI @bgcngm its me again lol
i have s-off my 802w upgrade 4.2.2 with your nandroid - run ROMCLEANER with success with your .txt now i have one last thing its this message of android is upgrading - i have deleted the file you mentionned but i still have the messag when rebooting
any idea of the problem ?
thnaks in advance

Also I can not remove it. I tried everything but the word "Androind is upgrading" remains. I ROM CROMI and Kernel Max

What can I do with stock, locked, but rooted JB?

I hope that xda community can help people like me, who prefer to stay with stock ROM for any reason, but was able to root the device. There are only a few things that I can think of right now is:
- [SAFE] Change gps.conf to improve GPS
- [SAFE] Change hosts to block ads
- [WARN] Delete bloatware
What else can I do to make this device better without having to unlock bootloader?
TIA

You can use Browser2RAM if I'm not mistaken
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

In short, you should be able to alter any file on the system that doesn't require a bootloader flash, like recovery or kernel I think.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

Titanium Backup. How about scripts to maintain your application? The xda app cache can grow quite large just as any app's cache can. Does it impact the app? Depending on the device it can be invisible or it can lag your device. Rooted, I have scripts running nightly that delete the cache files so I don't have to. And yes - the difference is readily apparent.
Sent from my SCH-I510 using xda app-developers app

funnel71 said:
In short, you should be able to alter any file on the system that doesn't require a bootloader flash, like recovery or kernel I think.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
so theoretically i can push the whole modded rom if i know which files to replace? maybe use adb to delete all then extract all? possible?

norman505 said:
so theoretically i can push the whole modded rom if i know which files to replace? maybe use adb to delete all then extract all? possible?
Click to expand...
Click to collapse
Doubtful on that because altering the wrong files while its running could render it unresponsive. I was thinking more like changing default props files for tweaking, hosts for ad removal, and adding busy box files. I guess my first answer was too broad, sorry.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

hi
Like i am also on Stock Rooted ROM with Locked boot loader..i followed the guide on TF700 forum about things that we can mod ..
also i have downloaded lot of apps from market that need root!.
MY LIST OF APPS:
Rom Toolbox Lite
Seeder (V useful app)
My backup Pro
AdAway
Andromizer
Pimp My Rom
Root Explorer
And many more...u cn try them...But be careful dnt try to mod anything that you dont know..u will end up in a boot loop.
Hope it helped u.
Sent from my ASUS Transformer Pad TF300T using xda premium

norman505 said:
I hope that xda community can help people like me, who prefer to stay with stock ROM for any reason, but was able to root the device. There are only a few things that I can think of right now is:
- [SAFE] Change gps.conf to improve GPS
- [SAFE] Change hosts to block ads
- [WARN] Delete bloatware
What else can I do to make this device better without having to unlock bootloader?
TIA
Click to expand...
Click to collapse
- [Safe] Read full logcat and /proc/last_kmsg (useful for developers, or users who wants to help developer know what went wrong or why a particular app crashed)
- [Safe] Cheat on games :angel:
- [RISKY] Change boot animation
- [RISKY] Disable apps that autostarts on boot.
- [RISKY] Tweak CPU Governor, I/O scheduler, SD card read cache, sysfs, Android internal memory manager & task killer, Dalvik heap size, WiFi and Tegra 3 parameters. I would recommend using Android Tuner app for tweaking.
Don't know about other people, but, I had bad experiences with Pimp My Rom (Beta).

Using motochopper method, I got mine Root but Unlock stock JB.
I just used System Tuner (free version of Android Tuner) to disable some apps at boot time and it works.
When I am abroad without Wifi, I use GPS Time to set the clock.
Titanium Backup Root to backup apps and system because for some reason the ASUS stock App Backup doesn't work right anymore
(for around 90 apps, always having 3,4 apps failed).