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] "Unfortunately, settings has stopped working" after factory reset

Hello folks,
The SGH-i337 is my first android device and I've had it only for a few days now. I rooted the phone using the "1 click root and debloat" files in the development section of this forum. Everything worked great after that. Today I installed an unofficial apk on my phone but I wasn't comfortable with it at all. So I did a factory reset (are you not supposed to do that?)
After the factory reset, the phone boots up and gives me the usual settings menu. At the end of the settings however, it lags for a few seconds before it says "Unfortunately, settings has stopped working". This brings me back to the "choose a device name" menu in settings. If I fill it out again and go through settings, it crashes again. I can't get into anything else on the phone since it keeps going through the initial setup.
I've tried booting into recovery mode and deleting the cache. I doubt that this clears it since the phone gives me an error and reboots. I tried selecting factory reset through the recovery mode but that also gave me the same issue (said error and rebooted).
After some searching I've found that flashing a stock rom with odin might be the best way to go. Is that correct or is there a better way? On the odin download page, it only lists the 9505 version for Galaxy S4. Could I use that for my SGH-i337?
I think the phone is still rooted because it says Samsung Custom before booting up. Thanks for the help!

Had same exact issue as well.
I booted in to download mode and flashed it with factory rom, then installed CWM.
This is what i used. http://forum.xda-developers.com/showthread.php?t=2297033

KGB7 said:
Had same exact issue as well.
I booted in to download mode and flashed it with factory rom, then installed CWM.
This is what i used. http://forum.xda-developers.com/showthread.php?t=2297033
Click to expand...
Click to collapse
Oh man, you're a life saver. I'm downloading the file and I'll give it a shot. So just to confirm, I put the phone into download mode and run Run_Me.bat and that should fix the issue?
Also for future reference, are you not supposed to do a factory reset after rooting your phone? Thanks!

Fixed it
The issue arose because the settings program was supposed to follow up with at&t locker setup. But since I had deleted the at&t files with the debloat tool, it kept crashing. So the solution was to reset the phone to stock firmware. I used Odin 3.07 to flash the factory ROM onto the phone and now everything is back to normal.
I guess this also answers my previous question, if I'd probably have the same problem again if I do a factory reset.

aleatoric said:
The issue arose because the settings program was supposed to follow up with at&t locker setup. But since I had deleted the at&t files with the debloat tool, it kept crashing. So the solution was to reset the phone to stock firmware. I used Odin 3.07 to flash the factory ROM onto the phone and now everything is back to normal.
I guess this also answers my previous question, if I'd probably have the same problem again if I do a factory reset.
Click to expand...
Click to collapse
Just dont use all in one tool as you did before. Just use the chooper rooting process in the link I provided.
Then manually remove the apps you dont with titanium backup.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[Q] Encrypting a Galaxy Note 3

I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks

tahnoonp said:
I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
Click to expand...
Click to collapse
I'm having the exact same issue. Encryption is requited to get my work email and I can't get it to go.

Finally got mine to encrypt
Took me a bunch of tries.. and finally once i opened a chat with samsung support it finally worked.. i was at 100% charge, plugged into the wall and if finally worked. not sure if thats a bug in its detection if your over the stated 80% or not... good luck.. i finally got it working though.. only did a fast encryption as it didn't work on previous tries either way... so i just chose one and tried it again.

tahnoonp said:
I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
Click to expand...
Click to collapse
I have the Google Policy Manager and Encryption is required for me too. I started at 81% and the first time I did it, it just rebooted. The second time I did it it worked like it was suppose to. Try it again right after it reboots and see if it works.

Make sure the phone is charged and keep trying over and over.
It will work eventually.

I gave up. I'm using touchdown now for work email which will allow me to skip full device encryption
Sent from my SM-N900V using Tapatalk

Same problem here, it will not encrypt
....help please

This is the answer I found doing a couple of root and unroot
1.If you encrypt the device and then root it you will net get past the passcode in the phone (black screen)
2. If you root the phone first and ten try to encrypt you will get the problems mentioned in this thread
..any tips how to get the phone rooted and then encrypted?

greffel said:
This is the answer I found doing a couple of root and unroot
1.If you encrypt the device and then root it you will net get past the passcode in the phone (black screen)
2. If you root the phone first and ten try to encrypt you will get the problems mentioned in this thread
..any tips how to get the phone rooted and then encrypted?
Click to expand...
Click to collapse
Bump. I'm looking for this answer too.

digittante said:
Bump. I'm looking for this answer too.
Click to expand...
Click to collapse
anyone at all? im stuck. Bump!

was having a similar problem on nexus 4 but safe mode helped there.
dind't help on my new n3. shouldn't have rooted before encrypting.
tried pressing encrypt about 10 times.
tried boot into recovery + wipe . also tried safe mode. also tried unroot + factory reset (pretty sure recovery + wipe /data is the same as reset user data from settings).
waiting for the firmware image to download - decided to try a firmware reflash

and then before flashing it I tried rebooting to recovery and powering off and encrypting and it worked. or maybe it was that random 12th time it worked because of an unrelated reason.
and after trying to root it again it just booted to a black screen after cf-root and enter encryption password screen.
*sigh*

My Work-Around
svyr said:
and then before flashing it I tried rebooting to recovery and powering off and encrypting and it worked. or maybe it was that random 12th time it worked because of an unrelated reason.
and after trying to root it again it just booted to a black screen after cf-root and enter encryption password screen.
*sigh*
Click to expand...
Click to collapse
I'm an AT&T customer, but I bought a T Mobile Note 3 off of Craigslist, unlocked it, rooted using Chainfire's ODIN thread, and then used the RegionFree Lock Away app. I was unable to encrypt just like you guys until I did the following. Flashed TWRP tar file from the TWRP site using ODIN. Rebooted into recovery and made an image, backup up everything, just in case. Rebooted and went in the SU Superuser application that Chainfire originally installed and uninstalled through the settings in the program. Once I rebooted I was able to encrypt the device (without fast method), I already had my SD Card encrypted. Once I encrypted the device I downloaded Kingo Root at the advice of DesignGears and used the one click root application from the Kingo Root site (google it.) After I did that, I now have full root access back, encryption, and never had to uninstall the region lock, so I didn't lose phone connectivity, applications, or anything else during the process. I recommend using TitaniumBackup and syncing via Google Drive or Dropbox before you start the process so you can restore your apps and data, once again, just in case.

encrypted ATT Note 3 not able to root
I was able to unroot my ATT Note 3 and then encrypted it. But Kingo Root failed to root the device. (I used it to root the phone once previously)
Now I stuck in a status with encrypted phone not able to root anymore.
Any suggestions please?
GHolbrook4 said:
I'm an AT&T customer, but I bought a T Mobile Note 3 off of Craigslist, unlocked it, rooted using Chainfire's ODIN thread, and then used the RegionFree Lock Away app. I was unable to encrypt just like you guys until I did the following. Flashed TWRP tar file from the TWRP site using ODIN. Rebooted into recovery and made an image, backup up everything, just in case. Rebooted and went in the SU Superuser application that Chainfire originally installed and uninstalled through the settings in the program. Once I rebooted I was able to encrypt the device (without fast method), I already had my SD Card encrypted. Once I encrypted the device I downloaded Kingo Root at the advice of DesignGears and used the one click root application from the Kingo Root site (google it.) After I did that, I now have full root access back, encryption, and never had to uninstall the region lock, so I didn't lose phone connectivity, applications, or anything else during the process. I recommend using TitaniumBackup and syncing via Google Drive or Dropbox before you start the process so you can restore your apps and data, once again, just in case.
Click to expand...
Click to collapse

I was able to get mine to encrypt after killing the bloat apps. All Google sync, amazon, and Verizon services. I can't say which one was killing it since it stopped pretty much every app or service that wasn't critical to the device.

Can anyone confirm that Encryption will never work once we root our phone ?

nlatifolia said:
Can anyone confirm that Encryption will never work once we root our phone ?
Click to expand...
Click to collapse
Same question here... Anyone was able to encrypt after being rooted???

Same question, rooted can't encrypt.

Just got a note 3 and this is an old thread. So wanted to update this question.
To encrypt device after root all that is needed to do is run the following command from terminal or adb shell as root. You must have the latest busybox installed.
pkill -KILL daemonsu
After running this command you should be back at the "$" prompt and out of root. Do not run su again.
Then encrypt your device. Encryption should work fine. Once rebooted you will have root again.
I had to repeat the above steps because I ran su again. Running su restarts daemonsu.
Good luck

Hi,
I was able to root and encrypt my sm-n900 note3 using the steps mentioned on this post:
http://forum.xda-developers.com/showthread.php?t=2791587
Just make sure that you have your backups ready case something goes wrong
I've installed the bloatwares after rooting and encrypt.

Help with Root and Recovery please!

Hello.
My Galaxy S4 was dying so T-Mobile just replaced it with an S5. It came with:
LMY47X.G900TUVS1FOJ4
I clicked on Software updates in About device and it did whatever updates, but the version stayed the same. Then I went to autoroot [dot] chainfire [dot] eu and downloaded the correct file to root. I unzipped the file and ran Odin 3.10.6 that came with it. I was able to root the device no problem.
What seemed like a problem afterward was that I couldn't find SuperSU in the Application list. I know the phone was rooted though because I could launch Titanium Backup to restore all my stuff from the S4. I went to the Play Store to download SuperSU. It kept complaining that I needed a new binary, but it would fail every time to update. I even tried downloading the latest SuperSU zip to install in the recovery mode, but that failed too. I really wasn't too worried about this.
While looking up how to root the S5, I saw some posts where people mentioned their root access stopped after 24 hours. I just experienced this when I launched Titanium Backup to begin uninstalling bloatware. I was informed that I didn't have root access anymore.
I figured I'd try to reflash the auto-root through Odin. According to Odin, everything passed, but looking at the device, it said it's already patched and the restore failed, so it aborted.
Now the device is stuck in an infinite reboot loop. I can access both the download and recovery modes, but that's it.
I'd really really like to not have to do a factory wipe as it was a pain to get everything copied over from the S4.
Can I flash it with something else?
Once I can get back in the device, how do I keep the device rooted? Do I have to flash TWRP or CWM?
The only root program I use is Titanium Backup and would really really like to keep using it to makr regular backups.
Thanks a lot.

Try booting into recovery and wiping the CACHES
If it still won't boot, grab a stock ROM from sammobile .com for your model S5 (G900T by the looks of the ROM name) and flash it with ODIN from download mode
That won't wipe your data or anything you've restored, as long as you don't reset
If it still won't boot, you might have to suck it up and factory reset after flashing stock
Was the TiBu backup you restored, rooted? Maybe restoring the backup restored an old version of SuperSU and broke the CF AR version
Might need to go down the TWRP and SuperSU from TWRP recovery route to get it rooted properly if CF AR isn't woprking 100%, which it doesn't for a fair few people

I tried clearing the cache, but that didn't work.
Is there a way to download the stock ROM without having to create an account on the download site?
The Titanium Backup I restored was rooted. Everything was totally fine, until I went back to TB and it suddenly told me I wasn't rooted anymore.
I did try TWRP after I made the original post. I think messed up the device, but I can get in now. I flashed the latest version and booted into Recovery Mode. I clicked on Fix Permissions and possibly one other thing. It let booted farther before the infinite bootloop. It'd show my lock screen and give me 1-2 seconds before rebooting. If I swiped quickly, I could see the home screen with most of my icons gone. Clicked on Apps shows most of the apps are gone. When I removed the SIM card, I stopped getting the infinite bootloop. Here are the list of important programs I have left:
Contacts (all cleared out), Gallery (all present), Messages (all present), My Files (shows files from previously installed programs that I can no longer access), Phone (works when I put the SIM card back in), Settings
Unfortunately, TB and the Play Store are both gone. I might be able to install stuff using adb or by copying files over. I haven't tried, but it doesn't look good. I tried reflashing the CF ROM. It didn't change anything. I suspect I may be looking at a factory reset at this point. I'm happy to try any other suggestions.
Thank you.

whynoteel said:
Is there a way to download the stock ROM without having to create an account on the download site?
Click to expand...
Click to collapse
Wut? lol, just make one, it's free...
XDA does not spoon feed

I created an account and downloaded the stock ROM. I flashed the device and got most of the programs to appear again though the Play Store was still missing. I decided to cut my losses and just do a factory reset. I rooted again and put everything back in place. Now I'm experiencing the problem where I lost root after a day or so of use. I'll start a new thread.
Thanks for your help.

Something wierd is going on.

i checked manually for upates, 15 minutes ago. It showed me that an system update is avaible.
Update installed, rebooted and here starts the wierd things.
-Phone boots up but the only thing im able to access is the ''edge'' bar where is the edge people and other fun features.
-Pressing volume button down will bring the boot menu with : reboot, shutdown etc..
-Tried to boot in safe mode. no luck, only the safe mode bar appears in the left.
-Wiping cache, no luck.
-Not rooted. Stock.
Only thing that i installed outside the play store is the samsung lab application wich is shared here in the forums because its not avaible for s6 edge+ for some reason in the samsung's app store.
I managed to boot in recovery mode and this text took my attention : mmb29k.g928fxxs3bqa9 (frimware codename?) 6.0.1 android version
Made factory reset, works now but lots of important data (pictures, music etc..) lost in that.
I made an google search with mmb29k.g928fxxs3bqa9 and found nothing.
(edit: In the download folder, there seems to be a file with the rom build number/number)

Yeah I had the same problem, posted about it in the general forum. I flashed another stock ROM ontop of it from Sammobile and it saved me from doing the factory reset.

Tondern said:
Yeah I had the same problem, posted about it in the general forum. I flashed another stock ROM ontop of it from Sammobile and it saved me from doing the factory reset.
Click to expand...
Click to collapse
After the factory reset its been running fine with the update. I alerdy emailed samsung about this.

justanpotato said:
After the factory reset its been running fine with the update. I alerdy emailed samsung about this.
Click to expand...
Click to collapse
they are still sharing it.

Someone who's phone updated correctly needs to make these guys a firmware they can flash back with Odin otherwise they won't be able to find anything that works. (no downgrades allowed)
Make sure you backup what you can. Export contacts, everything on Phone when you connect your computer can be copied in/out, if you didn't know. App data will have to be individually backed up.