I clicked on software update in about phone, and it showed me that update available.
I clicked on download.
As it started downloading I realized I do not have enough charge.
So I plugged in the phone.
The download stopped
So I restarted phone, went to Manage applications, and selected software updater. It had 208KB data which I deleted.
But again when I clicked on software update, it just said No update available.
How do I reset the software update to retry the download again??
Restart your phone again?
Sent from my GT-N7000 using Xparent Sky Blue Tapatalk 2
Already did that. No use.
I even wiped the Cache partition
I guess I will get it from Kies.
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?
I had a weird issue today. I tried to update a couple apps just because i checked in play store for updates. Nothing special. I hit the update all button and left the phone alone for a while.
When i got back, i got the message for every app which needed update, that there is not enough space available. I was shocked, since i knew i had a ton of memory left.
And after a check i found that i have around 7 gb free on the internal storage...
i tried to update the apps again one by one. but every app stops downloading at a certain percentage and its diffrent for every app which need an update.
if i stop the update process and redo it, the download will stop at the exact same position again. its the same percentage and also memory.
I already cleared cache and data of google play store. still nothing.
i wiped cache in stock recovery (no custom recovery installed, but rooted)
and still the same.
I also tried to uninstall one of this apps and reinstall it again, stops at the same point as before and now i cant even install it anymore....
what can i do?
Hi guys, I just got a tegra note 7. When I booted it up for the first time it said I had an update for 4.3 ota. I am at 4.2.2 currently. When I try to download it, it starts off fine. However, when it gets to 200 mb out of the 398, it says that it is downloaded, checking MD5. After that it says download failed. I've tried a factory reset, a regular reset. I've tried deleting the ota files and clearing the data and cache in the system updates app. Please help me figure out how to update this thing.
So I signed up for the ota preview, but then decided against installing it till a later build as a couple bugs I read about worry me.
I unenrolled, yet the notification still pops up, and its in system - updates.
I saw someone recommend wiping cache, so I booted in to recovery, and wiped, and its still there.
. I also tried deleted the catch of Google services.
Idea idea how to get rid of this? Ideally I'd like the new 6.0 ota that is coming and try that till the N OTA is more stable.
Had the same problem but in a different manner, when i decided to unenrolled the android beta page didnĀ“t gave me any device to do that, so what i did was, wiped my 6P, signed with a diferent user/email than mine, went to android beta page with that same user/email and the page then informes that 6P is on the N program, unenrolled, problem solved.