Related
Hi there XDA people.
Normally content to lurk I thought I'd share how I fixed my upgrade issues and updated to the ww version of Jelly Bean ASUS sent out this morning.
I checked for a firmware update first thing this morning (as I've been obsessively doing regularly since the US update was released on the 22nd). To my joy I got that cheeky green arrow in the notifications window so left it to do it's thing. Had a shower, triggered it to update and went to get dressed. Whilst I was out of the room the upgrade failed and the tablet rebooted. My daughter was in the room so I have no idea what happened, my stupid fault for leaving it in the room with her, stupid me.
Long story short, I could no longer find the update via the firmware checker in settings. I tried a number of combinations of cold restarts and stopping various apps along with wiping their cache/data. These usually brought up the check for updates button but none would allow me to redownload the update. Sometimes I got a message saying "update available - check notifications", other times it didn't pick up the update and occasionally I just got a greyed out button. I'm sure this is ringing bells for some of you.
I reasoned that it had downloaded but for some reason something was stopping me download the update again. So using TotalCommander I searched around root directories for the "dlpkgfile" mentioned here - http://forum.xda-developers.com/showthread.php?p=30516010 . Found it (I think in the Cache folder of "File System Root", but this has all changed since the upgrade) and renamed the dlpkgfile to dlpkgfile.bak.
I then temp unrooted with voodoo, cold booted for good luck and then checked for firmware updates. Lo and behold it kicked in straight away, downloaded and updated without a hitch.
Hope this helps some of the folk who have had similar issues getting the firmware update to kick in again after initial issues.
Sent from my ASUS Transformer Pad TF300T using xda premium
gurningchimp said:
Hi there XDA people.
Normally content to lurk I thought I'd share how I fixed my upgrade issues and updated to the ww version of Jelly Bean ASUS sent out this morning.
I checked for a firmware update first thing this morning (as I've been obsessively doing regularly since the US update was released on the 22nd). To my joy I got that cheeky green arrow in the notifications window so left it to do it's thing. Had a shower, triggered it to update and went to get dressed. Whilst I was out of the room the upgrade failed and the tablet rebooted. My daughter was in the room so I have no idea what happened, my stupid fault for leaving it in the room with her, stupid me.
Long story short, I could no longer find the update via the firmware checker in settings. I tried a number of combinations of cold restarts and stopping various apps along with wiping their cache/data. These usually brought up the check for updates button but none would allow me to redownload the update. Sometimes I got a message saying "update available - check notifications", other times it didn't pick up the update and occasionally I just got a greyed out button. I'm sure this is ringing bells for some of you.
I reasoned that it had downloaded but for some reason something was stopping me download the update again. So using TotalCommander I searched around root directories for the "dlpkgfile" mentioned here - http://forum.xda-developers.com/showthread.php?p=30516010 . Found it (I think in the Cache folder of "File System Root", but this has all changed since the upgrade) and renamed the dlpkgfile to dlpkgfile.bak.
I then temp unrooted with voodoo, cold booted for good luck and then checked for firmware updates. Lo and behold it kicked in straight away, downloaded and updated without a hitch.
Hope this helps some of the folk who have had similar issues getting the firmware update to kick in again after initial issues.
Sent from my ASUS Transformer Pad TF300T using xda premium
Click to expand...
Click to collapse
I have the same problem but i can't find the dlpkgfile file. Searched with root explorer in the cache folder and rest of system root but nothing... Also tried temp. unroot with cold boot... :crying:
thanks, the whole morning and afternoon this was driving me crazy... but now its dl again :good:
Finally got it running.
- cleared cache and data of cmclient with titanium backup.
- cleared cache and data of dmclient with titanium backup.
- Temp. unroot in Voodoo (without this update check failed).
- update button available again, hit it and voila a green download arrow.
Update worked fine for me. I Just wiped my data as well
Sent from my R800i using xda app-developers app
bazzio said:
Finally got it running.
- cleared cache and data of cmclient with titanium backup.
- cleared cache and data of dmclient with titanium backup.
- Temp. unroot in Voodoo (without this update check failed).
- update button available again, hit it and voila a green download arrow.
Click to expand...
Click to collapse
I followed these instructions as I couldnt find the dlpkgfile either, unrooted with voodoo, cleared cache on the cm and dm client, it started downloading again, but to my disappointment it failed again during the restart. Had the logo of android on its back with a red triangle. I had to hold in power button to reboot.
What could be causing the update to fail? I havent disabled any system applications or messed with the build.prop file! :crying:
What I did was is this:
-Go to the the Apps section under settings
-Pick the "All" tab
-Then search for CMClient and DMClient and clear both data and cache of both of them
-Check for an update and Viola, green arrow shows up
I'm not sure if it works with root since mine is still unrooted so I don't have titanium backup installed yet.
Ulric099 said:
What I did was is this:
-Go to the the Apps section under settings
-Pick the "All" tab
-Then search for CMClient and DMClient and clear both data and cache of both of them
-Check for an update and Viola, green arrow shows up
I'm not sure if it works with root since mine is still unrooted so I don't have titanium backup installed yet.
Click to expand...
Click to collapse
Tried this, and it let me download and install the update again, but it failed again
mcall_r said:
I followed these instructions as I couldnt find the dlpkgfile either, unrooted with voodoo, cleared cache on the cm and dm client, it started downloading again, but to my disappointment it failed again during the restart. Had the logo of android on its back with a red triangle. I had to hold in power button to reboot.
What could be causing the update to fail? I havent disabled any system applications or messed with the build.prop file! :crying:
Click to expand...
Click to collapse
Im in the same boat as you, I did the same steps but it fails with the red triangle... I even did a factory reset and still doesnt update, could it be becuase of the root?
Have tried everything (dm delete, cm delete, temp unroot, atp tweak uninstall, cold boot, regular boot, etc) after the download failed at 99% and still either can't find or get immediate download failed. No JB love here
Sent from my SGH-I747M using XDA Premium HD app
Could anyone upload EmailWidket.apk from the WW version?
Found one but it says the check sum is not correct when trying to update...
During my update I also got the red triangle, so after a bit of investigation /cache/recovery/last_log pointed me to checksum error of Keyboard.apk. Restored it, fixed CM and DMClient but now it just says no update found. Any other suggestions?
Hello,
I just noticed 1 hour ago I have 4.3 OTA update for my Nexus 10. However the update has been failed, due to vfxsound mod as far as I understand. I deactivated this app but I cant see OTA update again if I check the system updates manually it states that your system is current(4.2.2). What can I do to have this system update notification again?
My configuration:
rooted (supersu)
CWM recovery
Thank you.
Same here!
mbt28 said:
Hello,
I just noticed 1 hour ago I have 4.3 OTA update for my Nexus 10. However the update has been failed, due to vfxsound mod as far as I understand. I deactivated this app but I cant see OTA update again if I check the system updates manually it states that your system is current(4.2.2). What can I do to have this system update notification again?
My configuration:
rooted (supersu)
CWM recovery
Thank you.
Click to expand...
Click to collapse
I can't update to 4.3 because of the same reason.
In my case, I installed both vfx and vhifi.
I deactivated and turned both of them into safe mode and tried to flash the update with stock recovery.
However, I still got "assert failed: apply_patch_check system/vendor/etc/audio_effects.conf"
There is a way to get the OTA update back, but I repeatedly failed, and ended up with error.
Someone please help us!
This happens because those files have been modified and are no longer the originals. Extract the files it is having issues with from the 4.2.2 factory image, replace them and try again, or just flash system.img from the factory 4.2.2 image and run the OTA again.
Edit: Also, to get the OTA notification again, go to Settings>Apps>All and force stop "Google Services Framework" then "Clear Data". Immediately return to the "About" screen and check for a system update. If any popups come up regarding allowing location services, choose "No" or otherwise don't allow it.
While the system update downloads, remove your google account, and re-add it to avoid any issues with sync, etc. on your google account. Keep in mind if you use 2-factor authentication via google, you'll need to add a new application password for your tablet.
I succesfully upgraded the system. As you said I replaced these file with the original ones. Now It works fine. The only problem is mx player doesnt work. I think they will update it soon.
plastikowl said:
This happens because those files have been modified and are no longer the originals. Extract the files it is having issues with from the 4.2.2 factory image, replace them and try again, or just flash system.img from the factory 4.2.2 image and run the OTA again.
Edit: Also, to get the OTA notification again, go to Settings>Apps>All and force stop "Google Services Framework" then "Clear Data". Immediately return to the "About" screen and check for a system update. If any popups come up regarding allowing location services, choose "No" or otherwise don't allow it.
While the system update downloads, remove your google account, and re-add it to avoid any issues with sync, etc. on your google account. Keep in mind if you use w-factor authentication via google, you'll need to add a new application password for your tablet.
Click to expand...
Click to collapse
Thanks for your guide , my problem is same as above problem with little difference , when I click on OTA update my phone restart and go to CWM recovery and say "it is not safe package , do you want to install ?" I click yes but nothing happened . I also try to get OTA notification back as same as your instruction but nothing happened . please help me . thanks
sabx13 said:
Thanks for your guide , my problem is same as above problem with little difference , when I click on OTA update my phone restart and go to CWM recovery and say "it is not safe package , do you want to install ?" I click yes but nothing happened . I also try to get OTA notification back as same as your instruction but nothing happened . please help me . thanks
Click to expand...
Click to collapse
Did you mean, "phone"? I can only speak for how this behaves on the Nexus 10. Also, if you enable location services (sometimes it tries when the google services framework starts back up) and you allow it, the OTA doesn't seem to show up (at least not for me, perhaps it's region-based?).
I had to redo mine several times while I replaced system files that had been modified, so I know it works if it's done the way I described. 60% of the time, it worked every time.
Also, try removing your custom recovery. I don't know how this affects things for the OTA but it's a factor I didn't have to contend with.
I'm pretty sure he meant tablet. I'm having the exact same problem on my N10.
plastikowl said:
Did you mean, "phone"? I can only speak for how this behaves on the Nexus 10. Also, if you enable location services (sometimes it tries when the google services framework starts back up) and you allow it, the OTA doesn't seem to show up (at least not for me, perhaps it's region-based?).
I had to redo mine several times while I replaced system files that had been modified, so I know it works if it's done the way I described. 60% of the time, it worked every time.
Also, try removing your custom recovery. I don't know how this affects things for the OTA but it's a factor I didn't have to contend with.
Click to expand...
Click to collapse
I sideloaded 4.4 and found enough drawbacks that I restored 4.3. Now, any suggestions on how I can get rid of the OTA notification that finally showed up -- and keep it from coming back?
Update: It's been 3 days now, and no update nags!
tjupille said:
I sideloaded 4.4 and found enough drawbacks that I restored 4.3. Now, any suggestions on how I can get rid of the OTA notification that finally showed up -- and keep it from coming back?
Click to expand...
Click to collapse
AFAIK, there is no way aside from installing a custom ROM that wouldn't even try to receive it. POSSIBLY by rooting and deleting a file in your system area, but I can't remember specifics.
I'm curious; what drawbacks did you find, exactly?
I'm curious; what drawbacks did you find, exactly?
Click to expand...
Click to collapse
1. No Flash.
2. My bluetooth mouse refused to pair.
3. My preferred browser (Maxthon) FCs when opening a URL
4. No battery percentage
5. Stickmount launches, but won't actually mount anything
Except for the Stickmount problem, none of these, individually, is a show-stopper (no Flash comes close), but in the aggregate, I'm happier with 4.3.
FWIW, 2 & 3 seem to be hardware-specific. The mouse will pair with 4.4 on a 2012 N7 (but the response is so jerky as to make it useless) and Maxthon does run on the N7.
tjupille said:
I sideloaded 4.4 and found enough drawbacks that I restored 4.3. Now, any suggestions on how I can get rid of the OTA notification that finally showed up -- and keep it from coming back?
Click to expand...
Click to collapse
After reading many of the posts re: 4.4, I decided I wasn't going to install the OTA whenever it did come. Well it came yesterday and I wondered the same thing. I posted a similar question in another thread but didn't get any response. So I ended up just removing the zip file from the cache folder to see what would happen. I copied it to my sd card so I'd have it just in case and then just deleted it from cache. I tried a few things to see if it would automatically download the file again, but so far it hasn't. System Update in Settings still says, "Android 4.4 System Update, downloaded & verified - 219.9MB, Restart & Install." But hitting the install button doesn't do anything. It just says "Rebooting" but it doesn't actually reboot, so I hit Cancel Install. Been working with the device all day and haven't received any additional notifications for the OTA.
A whole bunch of suggestions in the Nexus 7 Forum:
http://forum.xda-developers.com/showthread.php?t=1998378
I went ahead and ran the install, knowing it would fail with TWRP (which it did) and then renamed otacerts.zip (in the system/etc/security directory) to otacerts.bak. Check for updates shows system up to date. Hopefully, it'll stay that way.
1. No Flash.
2. My bluetooth mouse refused to pair.
3. My preferred browser to (Maxthon) FCs when opening a URL
4. No battery percentage
5. Stickmount launches, but won't actually mount anything
Except for the Stickmount problem, none of these, individually, is a show-stopper (no Flash comes close), but in the aggregate, I'm happier with 4.3.
FWIW, 2 & 3 seem to be hardware-specific. The mouse will pair with 4.4 on a 2012 N7 (but the response is so jerky as to make it useless) and Maxthon does run on the N7.
Sent from my Nexus 5 using XDA Premium 4 mobile app
sharksfan7 said:
After reading many of the posts re: 4.4, I decided I wasn't going to install the OTA whenever it did come. Well it came yesterday and I wondered the same thing. I posted a similar question in another thread but didn't get any response. So I ended up just removing the zip file from the cache folder to see what would happen. I copied it to my sd card so I'd have it just in case and then just deleted it from cache. I tried a few things to see if it would automatically download the file again, but so far it hasn't. System Update in Settings still says, "Android 4.4 System Update, downloaded & verified - 219.9MB, Restart & Install." But hitting the install button doesn't do anything. It just says "Rebooting" but it doesn't actually reboot, so I hit Cancel Install. Been working with the device all day and haven't received any additional notifications for the OTA.
Click to expand...
Click to collapse
Is your device rooted?
coppercents said:
Is your device rooted?
Click to expand...
Click to collapse
Yes.
Try notification Helper
Gesendet von meinem GT-N7100 mit Tapatalk
Are there any ways in solving this problem without rooting?
hey guys i have a big problem ota just shows to my device two days a go and automatically start to download then after i check it said couldn't download retry but the retry button does not work
how can i do? my device is not rooted and have an original os
Sent from my Nexus 4
Try wiping data and trying it again.
You could try sideloading the update. This thread has tons of information:
http://forum.xda-developers.com/showthread.php?t=2145848
I'm getting the OTA update to Android 5.1, it downloads, asks me to restart, then fails with an error screen and the robot lying on its back. The phone then reboots itself into the 5.0.1 firmware.
The phone is rooted, is anyone else getting the same issue. Are there any logs I can look at to find out why?
Thansk
i have troubles as well. i unrooted, installed stock recovery (via n4 toolkit) and tryed to install. it takes longer then before but i stell get an error. SuperSU is gone in my app drawer.. any other help?
PS: i am on stock rom 5.0.1
i tryed to use sideload ADB update. it says: "/system/bin/app_process32" has unexpected contents. Error in sideload/package.zip. Status 7
any tipps?
I used the excellent Wug Nexus Toolkit http://www.wugfresh.com/nrt/
Through there I unrooted. Then applied the new update.
rowdybeans said:
I'm getting the OTA update to Android 5.1, it downloads, asks me to restart, then fails with an error screen and the robot lying on its back. The phone then reboots itself into the 5.0.1 firmware.
The phone is rooted, is anyone else getting the same issue. Are there any logs I can look at to find out why?
Thansk[/Q
I tray everything but don't work, it tell me , cache file fail.
Click to expand...
Click to collapse
In my case, this did the trick: aaronhastings.me/updating-to-android-5-1-0-on-rooted-nexus-5
I hope it will help you, too.
Regards.