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.
I have a problem with superuser that I can't understand.
So I bought this new Samsung Galaxy Note 3, and I rooted it by flashing my phone with Clockworkmod 6.0.4.5(1116) with Odin, and then installing UPDATE-SuperSU-v1.65.zip through the recovery window.
To be honest the process didn't go ideally smooth. Since I misunderstood how to proceed with the process, I had to reinstall Clockworkmod a few times.
After finishing from that, I started trying to use software that needs root access (like LuckyPatcher), and lucky patcher was hanging at the beginning black screen and not proceeding. And I tried many other programs, and they always don't proceed and stop.
So eventually I went to the Application Manager and select Superuser, and chose to "Uninstall updates", and only then, all those Superuser prompt messages started popping up asking me to grant LuckyPatcher and all other software that tried to access root... and since I chose to Uninstall updates, the phone restarted.
Of course, after the phone restarts, we're back at square 1, but the programs, to whom I granted root access get root access for some time...
I tried updating Superuser from the market, but when the program starts, it says "The Superuser binary (su) must be updated.", and I have a option called "Recovery Install", when I choose it, the phone keeps showing a message saying "Installing Superuser..." and it never finishes. Yesterday I left it and went to sleep, and eventually it gave an error message. I would say that Superuser update itself requires root access which it couldn't get... but that's as far as I know. I tried the "Uninstall updates" trick but it never worked.
Also I have to say I tried to install Superuser versions 1.51, 1.60, 1.65, 1.80 through recovery with a zip file, and it didn't fix it. And I installed CrashROM from here:
http://forum.xda-developers.com/showthread.php?t=2535355
and it didn't help either.
What do you think? How can I repair that and have normal Superuser permission asked normally? Please advise.
Thank you.
Any help, please?
Problem solved
The solution was to specifically install SuperSU from the market and not superuser. That fixed it.
After i tried
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
on lollipop on vodafone uk, i got this error message on boot, i press ok and after reboot i got no root
Then i install superuser through twrp that i previously had and keep getting this error message on boot.
The thing is i cant get past it, its covering the whole screen no operating system ui just that in a white box and a press ok, which doesnt work until after 2 minutes.
EDIT: its just constantly saying programs has stopped responding in a loop and cant get into android system. How do i fix this, i tried fixing permission in recovery but that didnt work.
So what i can do without losing all my work on my phone.
I hope you made a backup before flashing root files
Boot into recovery, clear CACHES, reboot - see how you get on with that
If you flashed CF Auto Root, there was no need to flash SuperSU, as it comes part of CF Auto root, someone else just did that and ended up in a boot loop, had to wipe the phone and flash a stock ROM
Thats the thing i didnt, i watched a video saying it wouldnt delete your files rooting and decided not to backup.
I was stuck on samsung logo half the time and other times stick with "unfortunately MTP application has stopped." in a big white box blocking me getting into android.
I tried fix permission, clear cache and delvin cache and nothing worked.
I just system wiped and got in but lost all my work.
Fortunately Google backed up most of my photos and videos and contacts but no sms messages.
Now i gotta get all my apps back on my device and get it back to how it was and hopefully i did not mess any important texts.
Note to self: Always backup.
EDIT: i just had gaaps not working and giving server error, after trying out ways to fix that i tried all the normal stop app and clear cache, and then did fix permission in twrp, and after doing "also fix SELinux contexts" it messed me over and got me back to that white box.
so another note to self not to use "Fix SELinux contexts" as that messed up my system after getting 30 apps back installed.
I’m by no means an expert, but I’ve always been tech savvy or at least been able to research and follow directions for things I’d like to do on my devices. I flashed my rom using Odin to fix the bootloop, but I still need a way to successfully move the app to system apps without getting stuck in a bootloop. Here is what I have done or attempted so far:
1. I have a Galaxy Tab 4. I recently rooted this device using Kingo Root.
2. After I rooted the device I confirmed I had root access and everything seemed ok. I have used this app before to root other devices with no problem. I wanted to root this device so I could move Fake GPS Location Spoofer to the system apps folder and make it a system app.
3. I used lucky patcher to move the app to the system apps folder. However when it went to reboot my device, my device became stuck in a bootloop. After trying to repair the os, I successfully used Odin to flash my rom (android 5.1.1) and fix the problem.
4. After attempting to move the app with other file folder systems with root access, I still can’t move this app without it resulting in a bootloop.
What am I missing or doing wrong? Any suggestions, solutions, or insight would be welcome. If you need additional information or detail, just let me know. Thanks!
Update: After some more testing I believe that the rooting with Kingo Root is the problem and not the attempts at moving the app to system app. I flashed the 5.1.1 Rom with Odin then proceeded to to reroot the device with KIngo Root. Once I did that and it showed as successful. I restarted my device and I got the bootloop problem. I've tried rooting the device SM-T330NU using the method in the general section of the samsung tab 4 forum but was not able to boot into recovery and got a different bootloop problem that would go black and then blink repeatedly. I made sure to use the download for the 8.0 so I'm not sure what is going wrong.
Suggestions?
Update 2: I managed to finally root my device with the CF method. I am still not sure why the other methods I used didn't work.
So I rooted my phone following information on this site/a video guide from youtube (I dunno if I'm able to post links but I can PM if you need to see what it had me do etc) so I did a fresh root with TWRP, RMM bypass, no-verify encryption, magisk. All worked great the phone was rooted etc, I then stupidly removed google play services to try get an early date APK which caused issues so I thought a wipe with TWRP would fix the issue but the startup wizard wouldn't work, so I then removed startup wizard via TWRP got back into the phone and put the new version of play services on, yet still had issues so I got the default firmware for my model at samsmobile and put it on via odin - all worked great phone booted fine etc but some apps said a boot was detected, so I made sure to go into developer options and make sure the OEM was locked, did a wipe via the default options when holding power>bixy>up however some apps still say the phone is rooted.. I checked with a rootchecker and I pass the safety and it says no boot detected. So I dunno what the problem is? The only thing I did see was when I did the wipe this came up
"remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (no such file or diectory)
e:[libfs_mgr] is_dt_compatible(): firmware info was not valid: '/proc/device-tree/firmware/android/compatible: no such file or directory"
Really dunno what to do from here.
bump
mrberta said:
So I rooted my phone following information on this site/a video guide from youtube (I dunno if I'm able to post links but I can PM if you need to see what it had me do etc) so I did a fresh root with TWRP, RMM bypass, no-verify encryption, magisk. All worked great the phone was rooted etc, I then stupidly removed google play services to try get an early date APK which caused issues so I thought a wipe with TWRP would fix the issue but the startup wizard wouldn't work, so I then removed startup wizard via TWRP got back into the phone and put the new version of play services on, yet still had issues so I got the default firmware for my model at samsmobile and put it on via odin - all worked great phone booted fine etc but some apps said a boot was detected, so I made sure to go into developer options and make sure the OEM was locked, did a wipe via the default options when holding power>bixy>up however some apps still say the phone is rooted.. I checked with a rootchecker and I pass the safety and it says no boot detected. So I dunno what the problem is? The only thing I did see was when I did the wipe this came up
"remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (no such file or diectory)
e:[libfs_mgr] is_dt_compatible(): firmware info was not valid: '/proc/device-tree/firmware/android/compatible: no such file or directory"
Really dunno what to do from here.
Click to expand...
Click to collapse
BUMPITY BUMP BUMP, plz help my fwiend!