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.
hello.
I have rooted my phone for some time with chainfire super user.
I started facing blue screen problems and random restarts now. thought maybe there is some hardware faults. started SU app and have choosed full unroot and problem have disappeared for some time.
What have happened and why?
firmware 4.4.2.
Currently i updated software through kies (nj1 update).
so far so good. no bluescreen for now.
update.. still getting randoms reboots... what is causing them?
I also had random reboots after I rooted. Though I don't think the super user app caused it. It happened only after I installed viper4android.
I changed roms since then and no problem.
Maybe you installed an app that causes it. Only thing I can suggest is, either change roms, or reinstall stock rom and root again
Did you delete Knox-related apps from /system?
no. i didn't delete them... should I? there were nothing mentioned about file delete in rooting manual so i did nothing.
Should I delete every file that contains word knox or any concrete files?
After I updated phone by kies, rooted again, data format couple times + dalvik cache clear, problem seems to disappear. for half day so far so good, no reboot.
to change rom will be next thing i will do if reboots reappear
Knox can cause problems on rooted phones. That's partly why you don't find Knox in ROMs based off stock. So yes, you should remove the Knox apps in /system.
just remembered... when I launched SU app it asked me do i want to disable knox. i choose yes.
is it enough for removing knox or it is necessary run for example DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0.zip
p.s. sadly i can't install busybox. after i click install it shows "checking system" forever
Choosing yes was the right answer, but while SuperSU does disable Knox, I'm inclined to believe it's only so that SuperSU can properly function and install the su binary and doubt it's permanent. However, I never tested this, as I delete Knox apps regardless.
I've tried various root methods without success, last one worked BUT was unable to access the play store, "my files" section or the basic package installer, making it imposible to disable the knox security log for the notification issue and everytime I successfuly root it I can install busybox, supersu and root checker but beyond that I am unable to proceed further. When I restarted the phone it stays stuck in the att boot logo while vibrating from 2-3 times on a loop.
From that point on I have to wipe memory/cache and start all over again...
I Started up the phone without supersu but even that it has factory reset, there is lag from the phone.
anyone help?
I'll post device info
there's also a problem I found myself trying to fix the first problems after rooting it was a "dm-vareity verification" problem, son't know if I spelled correctly but that was basically what it said
Thanks In Advanced. :laugh:
Hey guys,
a few days ago i checked out apkupdater and out of curiousity i checked for updates on system apps and installed em with no problems.
After rebooting my phone today I've been wondering why my phone is rebooting after a few seconds in lock screen.
And I was sure these "updates" are the cause for the problem.
This also happens in safe mode by the way.
I don't even have enough time to open Apps.
I tried to reflash with home csc to keep my data and hopefully replacing the bad system apps.
When it booted it showed a notification that its installing updates and I had a bit more time to spend on lock screen but still not enough to uninstall which most likely meant it was installing these "updates".
I'm trying to find out if there is a way to prevent the phone from updating its system apps after a reflash.
The solution itself is simple.. Get rid of these updates.. or factory reset.. but I'd like to keep my data.
I've read about several boot looping problems over the past few days, myself included. I'm starting to wonder a lot of phones were infected affected by an update. just out of curiosity, are you able to mount your partitions? Some of my partitions were messed up, including /data and /sdcard
I fixed it with the command:
adb remove com.dsi.ant.server
It is necessary to enable developer mode and adb debugging. My phone was booting and briefly restarting, so the only way to do it is by being quick.
Enviado desde mi SM-G935F mediante Tapatalk
Hello all,
My gf's G5 Plus suddenly went into a bootloop while she was uninstalling some apps to make some space for our newborn daughter pictues.
The G5 Plus was never rooted or tampered with in any way. Now it just won't boot and loop through the animation.
I've cleared the cache partition to no avail. I don't want to do a factory reset as I think it will completely erase the internal memory, and Google Photo only did compressed pictures backups (I don't want to lose the originals!)
Do you have any hints? I've read about a "safe mode" but it seems it can only be triggered from a running phone (power menu). Is there anyway to mount the user partition through USB on a computer?
Thanks a lot for any hint!
etique57 said:
Hello all,
My gf's G5 Plus suddenly went into a bootloop while she was uninstalling some apps to make some space for our newborn daughter pictues.
The G5 Plus was never rooted or tampered with in any way. Now it just won't boot and loop through the animation.
I've cleared the cache partition to no avail. I don't want to do a factory reset as I think it will completely erase the internal memory, and Google Photo only did compressed pictures backups (I don't want to lose the originals!)
Do you have any hints? I've read about a "safe mode" but it seems it can only be triggered from a running phone (power menu). Is there anyway to mount the user partition through USB on a computer?
Thanks a lot for any hint!
Click to expand...
Click to collapse
If it was unlocked, you could've tried to temp boot a TWRP recovery image and through that, you would've been able to mount user partition and copied the files. But as you said it's completely stock, I doubt that'd be possible. Are you able to access the stock recovery? I checked my recovery and there's nothing that might help you access internal storage from stock recovery.
If only you had enabled debugging and at least one computer would've been authorized ADB access by the phone, you could try to unlock it and temp boot TWRP but I'm not sure it's gonna happen in your case as most of the people who don't mess with their phones even open Developer Options in the Settings let alone enable USB Debugging.
Hopefully someone with more knowledge into this will help you out but at the moment, I can't think of anything else.
Honestly, assuming the device is purely stock and the bootloader is locked, your next option is to perform a factory default.
You will OK to just use Google Photo backup... All photos that are above 16MP are compressed to 16MP size, and the camera in the Moto G5 Plus is only 12MP. Photos that are equal to or less than 16MP in size are stored as is, so basically all photos taken by this device are stored on Google Photo are uncompressed. - Source
That sucks, same happened to me so i went for a custom rom, i believe they are doing this on purpose for G6 sales
M1810 said:
That sucks, same happened to me so i went for a custom rom, i believe they are doing this on purpose for G6 sales
Click to expand...
Click to collapse
No, they are not... You can remove your tin foil hat anytime.
Same happened to me, twice. I was on LineageOS. I had to wipe the phone and start anew, which isn' t so bad. Google made the entire process so easy.
My device is not rooted, it is showing oem locked. How to perform these actions then? It results into remote error while executing those commands