Database Users

How I upgraded to WW version of Jelly Bean after a booched install stopped it.

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?

[Q] Nexus 4 4.3 update won't get past unlock screen without crashing

I had the update notification for 4.3 today and went to install it. Everything appeared fine. However, when the phone rebooted and showed my usual screen unlock, I swiped it in and then the phone crashes back to the X - so android is loading and I can see my wallpaper and the time and everything as usual, but screen unlock reboots the phone. The only other problem that I've noticed is that the forward camera doesn't work to use face recognition to get the screen to unlock - the screen is always showing as black when normally my face is there.
Any tips for a fix? I'd rather not wipe all my data as I'm on a slowish bandwidth connection for the next couple of weeks.

kabads said:
I had the update notification for 4.3 today and went to install it. Everything appeared fine. However, when the phone rebooted and showed my usual screen unlock, I swiped it in and then the phone crashes back to the X - so android is loading and I can see my wallpaper and the time and everything as usual, but screen unlock reboots the phone. The only other problem that I've noticed is that the forward camera doesn't work to use face recognition to get the screen to unlock - the screen is always showing as black when normally my face is there.
Any tips for a fix? I'd rather not wipe all my data as I'm on a slowish bandwidth connection for the next couple of weeks.
Click to expand...
Click to collapse
Do you have an unlocked bootloader?

abaaaabbbb63 said:
Do you have an unlocked bootloader?
Click to expand...
Click to collapse
Yes - why? Can I download the data somehow using adb? What difference does this make?

Got the same problem on my Nexus 4, updated via normal Ota, unlocked bootloader and rooted.
Any solutions apart from a complete factory reset?
Sent from my GT-P3110 using xda app-developers app

kabads said:
Yes - why? Can I download the data somehow using adb? What difference does this make?
Click to expand...
Click to collapse
Well, you could make a nandroid backup. That way, you will have your data saved. After that, install a stock rooted 4.3 ROM and only restore data from recovery.
Or, Adb could work too. It would backup your data to your PC, and you could restore after you reinstalled the ROM.
I don't really know why, but many updates to 4.3 failed. That's why a data wipe is always recommended.
I always use Titanium Backup. It's very simple and easy to use.

I've used Nandroid before - not sure why I didn't think of it - thanks.

kabads said:
Any tips for a fix? I'd rather not wipe all my data as I'm on a slowish bandwidth connection for the next couple of weeks.
Click to expand...
Click to collapse
I had this exact same problam and was able to fix it without losing data, settings or installed apps.
My Solution:
Download factory 4.3 image and extract system.img. You need to untar the gzipped file and then unzip the included zip file to get system.img
Flash only the system.img and reboot. (fastboot flash system system.img)
When the phone is rebooted, root will be gone, but all installed user apps, data and settings should be preserved.
Background:
After the 4.3 OTA, my phone would reach the lock screen and receive notifications. Sometimes a call would make it through and I would be able to answer, but most of the time calls went straight to voicemail. Callmaster might have contributed to this behavior.
However, if I attempted to enter a pattern on the lock screen, the phone would immediately reboot.
I was rooted using SuperSU prior to the OTA. My Nexus was also affected by the issue were attempting to access the 4.2.2 Security Settings resulted in an error. I never got around to fixing that issue, but suspected that the 4.3 and 4.2.2 problem were related.

solution that worked for me: keep failing pattern until prompted to type in google account details to login, it then worked for me after that, no longer rebooting when unlocking

The difference between "Official" and "Custom" device status was S-Health.

The difference between "Official" and "Custom" device status was S-Health.
I was freaking out over being unable to get my S5 to show as "Official" in its device status (wanted to update, but was told I couldn't) .Out of paranoia, I copied over all my Downloads to my SD card and removed it, deleted any root apps and even cleaned it up using SuperSU. And I rebooted a lot. After I finished, I still saw
Device Status: Custom
Then, I remembered the S-Health bug. Since i like S-Health, I had switched it over recently from being a System app to being a User one (because S-Health on a rooted device was, well, broken). So I re-rooted with SuperSU, then re-opened Android Tuner Free and moved S-Health back from being a User app to being a System one again.
Device Status: Official
I didn't even have to unroot, remove the SU app, or reboot it; I just checked back in Settings and it was "fixed."

Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P

verse187 said:
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
Click to expand...
Click to collapse
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...

primetechv2 said:
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
Click to expand...
Click to collapse
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.

KennyG123 said:
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
Click to expand...
Click to collapse
I never actually installed a custom recovery, though. I did eventually reinstall the fully stock firmware with Kies and then performed the upgrade, something I'm going to guess wouldn't be possible otherwise... But to be specific, I never had anything installed except got XPosed mods and a moved S Health to get it functioning again.
But I'm really sad that, for whatever reason, my device status kept flickering between Official and Custom, especially when it chose Custom after I disabled root.

I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?

BlackJou said:
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
Click to expand...
Click to collapse
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.

frcollier said:
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
Click to expand...
Click to collapse
It is on Dalvik though :/

well, I did it again.
rooted: Official status
Installed XPosed: Official
Removed S-Health: Official
Reinstalled old S-Health as a user app: Official
Shifted S-Health to System app: Official
Removed XPosed: Custom
Anybody know what permissions SHealth and HealthService (.apk, .odex) should be reinstated with, and in which folder they go, I'd be really happy. Especially if someone got back to me before I downloaded this 1.5GB system file to figure out if it says.

Apps optimized at every reboot

Since Lollipop 5.1, Android optimize the apps at every reboot (359 apps), it takes around 20 minutes each time. My phone is encrypted and it does that with or without SD card. Did anyone notice a similar behavior?
1) Tried to remove SD
2) Tried to clear Dalvik
No changes.

difto said:
Since Lollipop 5.1, Android optimize the apps at every reboot (359 apps), it takes around 20 minutes each time. My phone is encrypted and it does that with or without SD card. Did anyone notice a similar behavior?
1) Tried to remove SD
2) Tried to clear Dalvik
No changes.
Click to expand...
Click to collapse
On my phone a window shows up on a reboot that Android is optimizing apps, but it takes 3 sec. Your seems like you have just upgraded Android OS and it prepares apps for that. It could be that update didn't really go well. I have never encrypted my phone, so that could be something... If nothing helps, factory reset could work, but make sure that your sd card is decrypted before reset(if you have it encrypted too)

Same here, thought that xposed is the cause but it seems that other have this issue without root.
Sent from my D5833 using XDA Free mobile app

smardu said:
Same here, thought that xposed is the cause but it seems that other have this issue without root.
Sent from my D5833 using XDA Free mobile app
Click to expand...
Click to collapse
I did not have xposed when it began... I have root though

Charkatak said:
On my phone a window shows up on a reboot that Android is optimizing apps, but it takes 3 sec. Your seems like you have just upgraded Android OS and it prepares apps for that. It could be that update didn't really go well. I have never encrypted my phone, so that could be something... If nothing helps, factory reset could work, but make sure that your sd card is decrypted before reset(if you have it encrypted too)
Click to expand...
Click to collapse
The issue with encryption is that the recovery cannot access the data partition and so cannot fix file permissions which could be an explanation for the issue.
Though rarely it only optimize 1 app usually it's all of them...

Slightly different (and worse) here, phone encrypted and everytime I reboot it hangs, reboots itself and then optimizes each and every app.. rebooting has become an agony

I had root in 5.0.2 then went to 5.1.1 but had to use flashtool as the over the air update kept failing (because I had root? I undid root and still had the same problem).
So when 5.1.1 loaded I had the same issue you are having, and I found I couldn't get root so I flashed it again 5.1.1, still the apps optimising every boot.
So flashed it to 5.0.2 again, took root again. Rebooted and the apps still had to optimise again (far less apps though, like 170 compared to 350 on 5.1.1).
Do I flashed it back to 5.1.1 and now it seems to all work fine.
No idea what the issue was.
BTW I used the UK firmware for both versions.

Pyres said:
Slightly different (and worse) here, phone encrypted and everytime I reboot it hangs, reboots itself and then optimizes each and every app.. rebooting has become an agony
Click to expand...
Click to collapse
I already have this issue once. I don't reboot often, but I doesn't happen at each reboot...

Pyres said:
Slightly different (and worse) here, phone encrypted and everytime I reboot it hangs, reboots itself and then optimizes each and every app.. rebooting has become an agony
Click to expand...
Click to collapse
Actually this is the same as me, tries to boot ~2 min then reboot and optimize. I will try to reflash the zip pre-rooted.

I have had the same. I was on 5.0.2 with root. Updated to 5.1.1 with flashtool (as OTA no possible due to root). Had extensive battery drain and flashed back to 5.0.2 and then this boot problem. Only when I did a factory reset everything was fine again. I suppose clearing the cache/dalvik cache is not sufficient. Better to save all apps and data (Titanium backup for example), reset the phone and apply the update. Root with pre-rooted 5.1.1, then apply your backup ...
Brgds
omg

omg1010 said:
I have had the same. I was on 5.0.2 with root. Updated to 5.1.1 with flashtool (as OTA no possible due to root). Had extensive battery drain and flashed back to 5.0.2 and then this boot problem. Only when I did a factory reset everything was fine again. I suppose clearing the cache/dalvik cache is not sufficient. Better to save all apps and data (Titanium backup for example), reset the phone and apply the update. Root with pre-rooted 5.1.1, then apply your backup ...
Brgds
omg
Click to expand...
Click to collapse
That's what I did, solved the problem.

I've had this problem for quite a while. my phone is stock, unrooted. I have encryption enabled (required to get work email through Mobile Iron). I observe that this issue (double boot w/ optimize apps) starts after a software update. the only way I have resolved this is by wiping the phone completely and rebuilding my apps and customizations which is quite time-consuming. is there anyway to resolve this without wiping? And for the 1st time, the issue came up just last week but this time there was no software update that preceeded it. is this really just a fact of life when using Android with encryption enabled or is this just an Xperia-specific issue?

I have the same issue on my work issues Xperia Z3. 20 minutes per reboot. It's brutal. Not a good look for Android.

Can't access to notifications and quicksettings tiles.

Hello,
I flashed the latest img and vendor from Pure Nexus and i got a little problem, I cant see notifications though the vibration happens, and i can't draw the notifications menu either same about the quicktiles settings.
I also noticed that recent apps button doesn't do anything anymore, i rebooted in safe mode, still same issues, can you help me?

Sberdila said:
Hello,
I flashed the latest img and vendor from Pure Nexus and i got a little problem, I cant see notifications though the vibration happens, and i can't draw the notifications menu either same about the quicktiles settings.
I also noticed that recent apps button doesn't do anything anymore, i rebooted in safe mode, still same issues, can you help me?
Click to expand...
Click to collapse
Sounds to me like you didn't wipe properly when flashing the ROM. You need to wipe system, data, cache, dalvik cache before flashing, is that what you did?

Usually when you update the same rom it's better to dirty flash no? i cant wipe all my data everytime i want to update the rom, though i might go back to stock, i
what's the best way to backup apps within the phone, and should i go deodex or Oden

Sberdila said:
Usually when you update the same rom it's better to dirty flash no? i cant wipe all my data everytime i want to update the rom, though i might go back to stock, i
what's the best way to backup apps within the phone, and should i go deodex or Oden
Click to expand...
Click to collapse
My mistake, I didn't realise you were just updating the same ROM. Yes, usually you can just dirty flash, but the way something is implemented may have changed in the latest update, causing the issues you're having now. The solution is pretty simple though: backup your user apps with Titanium Backup, boot into TWRP and perform a full wipe (system, data, cache, dalvik cache), flash ROM + gapps, boot into ROM and set up your settings, restore your user apps with Titanium Backup.

Thanks a lot!

I had this same issue after the March security updates. Was given this and it fixed my issues completely! It manually runs the setup wizard. Not sure if it will fix it or not, but worth a shot.
http://forum.xda-developers.com/showpost.php?p=65767953&postcount=7