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.
Related
Hey folks,
TF101 running 8.6.5.13 (pure rooted), trying to update to .18 using daoist's post here: http://forum.xda-developers.com/showthread.php?t=1334673
CWM keeps telling me it's having a problem with gmail.apk - I had installed the ICS version and (like a moron) failed to keep a copy of the 3.x apk.
Amongst others, I've tried using the .apk posted here: http://forum.xda-developers.com/showthread.php?t=1091566 and failed - it seems a tad old.
I am copying the .apk to the /system/app folder and setting permissions to read on owner/group/all and write on owner, and then installing it - "Application Not Installed" every time, and I've tried a few versions.
Can anyone (a) tell me where I'm going wrong (b) point me at the version of gmail.apk that I need or (c) give me an alternative route to get to 8.6.5.19 (yes, I know I said .18 at the top, ultimately trying to get to .19 but have to go to .18 first apparently)?
Any help greatly appreciated! (Even a pointer to where the install log files live to figure out why it's not installing might help!)
Cheers
PatMan
when you push it to system/app that is installing it you dont have to hit install from there jsut replace the new one with the old one reboot and clear gmail data and cache
mrevankyle said:
when you push it to system/app that is installing it you dont have to hit install from there jsut replace the new one with the old one reboot and clear gmail data and cache
Click to expand...
Click to collapse
Thanks - but did I mention that I had also "uninstalled" the ICS version by going to Applications -> Manage? Just by-the-by, you know! So I have no way (that I know of) to actually fire up the app - no shortcut, it's not in my app drawer, got no widget running.
I'm REALLY making this difficult for myself
Try this version, it's the backup I made before I pushed ICS Gmail app
http://dl.dropbox.com/u/16959871/Gmail.apk
baseballfanz said:
Try this version, it's the backup I made before I pushed ICS Gmail app
http://dl.dropbox.com/u/16959871/Gmail.apk
Click to expand...
Click to collapse
Thanks, but same result when I apply the .18 zip - "assert failed: apply_patch_check("/system/app/Gmail.apk", "<hex string>", "<different hex string>") E:Error (Status 7)". Those hex strings are what? MD5 checksums?
Strangely I have Gmail back now, so I'm better off that I was before - still getting that assert failed error when trying to apply the zip via CWM though...
I know you shouldn't have to do anything after pushing it to system/app but try clinking on it to install (worth a try).
Permission is rw,rw,r
baseballfanz said:
I know you shouldn't have to do anything after pushing it to system/app but try clinking on it to install (worth a try).
Permission is rw,rw,r
Click to expand...
Click to collapse
Nope, still the same - will attempt an unroot tomorrow, for now am going to relax and play some HL2.
Thanks tho, srsly
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.
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
Hello, all!
I'm wondering, how do you cancel an OTA update once it has started? I mean after it has downloaded, and you have chosen to install it.
Here's my problem: Everyone talks about how running an OTA update unroots your phone. No problem, I can just re-root it. What no one talks about (at least I didn't run across it before doing this) is installing OTA updates when you have TWRP installed...
So, my phone downloaded the update, and it asked me to install it. I accepted, it restarted, and TWRP came up. From there, nothing happened. I tried restarting it, and it booted up just fine. After about a minute of being up, the "Phone is shutting down" (or something along those lines) message pops up, and it reboots again.
I'm wondering, how do I go about cancelling the update? I've read online I need to download the update manually and run it through TWRP, but until I learn how to do that (and spend a few hours downloading it on this freaking slow internet connection), I would like to be able to use my phone.
Another alternative that I don't know whether is possible, can I somehow use TWRP to browse to where the OTA update was downloaded to, and install it through there? If so, what would the procedure be for doing so?
Thanks!
ElectroPulse
ElectroPulse said:
Another alternative that I don't know whether is possible, can I somehow use TWRP to browse to where the OTA update was downloaded to, and install it through there? If so, what would the procedure be for doing so?
Click to expand...
Click to collapse
Boot into TWRP, click install, click(Up A Level) until you are at "/" and look in the cache folder for the update zip.
It should be in there.
meekrawb said:
Boot into TWRP, click install, click(Up A Level) until you are at "/" and look in the cache folder for the update zip.
It should be in there.
Click to expand...
Click to collapse
Thanks for the reply!
Is it the "Blur_Version21.23.4.peregrine_retus.retus.en.US.zip" file? If so, that didn't work... Unfortunately it failed.
Here's what it said just before failing:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/cache/..."
Error flashing zip '/cache/..."
Updating partition details...
Any ideas?
Thanks!
ElectroPulse
ElectroPulse said:
Thanks for the reply!
Is it the "Blur_Version21.23.4.peregrine_retus.retus.en.US.zip" file? If so, that didn't work... Unfortunately it failed.
Here's what it said just before failing:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/cache/..."
Error flashing zip '/cache/..."
Updating partition details...
Any ideas?
Click to expand...
Click to collapse
You must have stickmount installed. Uninstall it and try again.
Note: If you changed or deleted anything in /system partition the install will keep failing. You'd have to fastboot flash the system img's from the 4.4.3 firmware.
meekrawb said:
You must have stickmount installed. Uninstall it and try again.
Note: If you changed or deleted anything in /system partition the install will keep failing. You'd have to fastboot flash the system img's from the 4.4.3 firmware.
Click to expand...
Click to collapse
Thank you for the reply.
Nope, Stickmount is not installed. Not sure what other apps there are that could cause this.
Not sure whether I've changed anything in /system... I don't believe I have, but an app I installed very much could have.
I'll look up this "fastboot flash" you are referring to.
Anyway, for now I am good. I copied the .zip OTA downloaded file to another location, hit the "clear dalvik and cache," rebooted, and I'm back to a working 4.4.3.
Problem solved until I decide to try to get 4.4.4 installed! (which I may never end up doing... Now that Cyanogenmod is officially out for Peregrine, I'm probably going to flash it with that when it gets stable enough (i.e. no RAM issues)).
[This was already posted, I just moved it to the Shield Q&A.]
As many of you may know, Nvidia has recalled their Shield Tablets. I'll be getting a replacement soon. I'll be rooting it as soon as possible when I get it, but first I have a few questions.
First of all, I rooted my tablet using a guide at IBTimes (that used info from XDA forums) installing CWM recovery.
After rooting I installed Link2SD, pretty much the reason I rooted, to save up some space on my internal memory. Everything was going fine, until I received the recall notice. I moved all my app files back to the internal memory, deleted Link2SD, ran a full unroot on SuperSU, (after a while of hanging on the "Please Wait" screen the app just crashed, it wouldn't load up and Root Checker said I had no root access after rebooting.
I don't know whether this was supposed to happen or whether it should have gone more smoothly, please give me an answer to this and tell me if it affected my system in any way) and fastboot flashed the stock recovery.img.
However when I tried to install the update, I got a red triangle error. After checking the log I got an error saying "Package expects build fingerprint of ... or ..., this device has ...."
I can't remember what the fingerprints were, but the first one was something that began with "nvidia/", had a bunch of numbers in the middle followed by an underscore, then it ended with "/release-keys".
However the device's current build fingerprint was exactly the same as the first, except that it cut off halfway through, right after the numbers and the underscore.
I tried resetting my cache, I tried a wipe of the user data. The only way to fix this for me was to re-install a bunch of stock images - recovery.img, boot.img, system.img, etc.
I don't want to wipe my data next time. So I ask for this in my answer:
- An explanation of what the error means
- How this error is caused
- A way to fix this error without wiping my device
- How to prevent this error
- If what happened to SuperSU in my case is normal and if it affected my device in some way
- And, if possible, a way to install the update successfully without getting this error and without having to unroot or remove CWM, and details on how to do this method and any risks.
Thanks in advance. An answer soon would be appreciated.
Quick answer:
- You don't need to restore to full stock before updating to the latest OTA. This is what I did, running a rooted stock system with TWRP recovery:
-- Go to Settings > About tablet > System updates and continue to click Check Now until the update has been found. I had to click like 4 or 5 times before it was found. It'll download automatically to your device (not your SD card), but I forget where that download location is... XD
-- once you've found your downloaded OTA.zip, copy it to a location you can easily find from your custom recovery.
-- reboot into custom recovery, flash OTA.zip, reflash superSU.zip, wipe cache NOT DATA, reboot
-- wait until device boots up, wait until the Optimizing blah blah process is done.
-- enjoy!
Additional thoughts:
- I've tried the Link2SD app, but I think it messes with my system in a way I don't like; personally I'd rather delete the apps I never use via custom recovery (see THIS THREAD on how to debloat your tablet for yourself!
- I think your error happened when you flashed stock recovery on top of the custom one. To prevent this next time, simply wait for either a flashable zip in THIS OTHER THREAD, or you can check to see if nVidia released any OTA3.1 recovery images if you want that full-stock experience.
Hope this helps!