background
i was rooted, then got the auto update, it broke my root
i have tried every mothod out there, even z4, oneclick
started with manual though
nothing, root apears to work fine, but afer the reboot, no root
tried a reset, same thing
any options for me? i actually like touchwiz so i didnt want to flash, but i can
is there a way to flash a non-rooted phone with odin that will root it?
thanks
oh i have flashed before, but it was the omnia i had prior to this
http://forum.xda-developers.com/showthread.php?t=803682
check this out, i used it last night and it does work.
finally got it
had to do the manual root until i got the # prompt
run su
delete su and busybox
reboot
then reroot
the system thought it was still rooted.
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'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:
I have the XT907 which was successfully rooted, so I presume(d). Last night I did nothing out of the ordinary. I plugged it in to charge, as it was almost dead. I woke up and took it off the charger, went out to smoke while coffee brewed, ran Clean Master app and it asked for SU permission (SuperSu). It didn't strike me as odd because I have it set so apps that update are required to ask for SU permission again. Only this time it wouldn't accept the permission I granted it. I tried again and it still wouldn't authorize (I was using the memory boost and I was trying to stop an app from auto starting when this happened). It told me to manually check the authorization in SuperSU. I did and it's listed there, all permissions granted. I ran RootCheck and it asked and was granted SU permission. I downloaded RootChecker just for a second opinion, and it too was granted SU permissions.
Before, during and after all of this, aside from the above mentioned Root checking app, I've downloaded one app onto my XT907: WiFi Password(Root). I needed the PW for my work's WiFi. It was denied SU permission. I've removed Clean Master from SuperSU, forced stopped Clean Master, rebooted Phone. Clean Master asks for permissions, is supposedly granted said permissions, but still won't accept them.
So two apps tell me I do NOT have Root on my phone, while two root checking apps say I DO have Root. I've not uninstalled or reinstalled anything or changed any settings as to get a further opinion on the matter. I rooted my device with KingRoot and uninstalled with SuperSU about a month or so ago. This is the first issue I've had. Any idea what gives? I'm a little stumped on this one.
It seems the issue is only with some apps. I've managed to fix the issue with Clean master by disabling SuperSU, re-enabling it then rebooting. Clean Master was granted permission and accepted it. So far I've not run into other issues. All root checking apps still say I have a proper root. If the issue continues, how about a reinstall of SuperSU? If I lost root, how would I regain it?
A while back I was able to achieve root on my ZTE 2050 (which also goes by about 20 other names.) I was continuously having issues with the phone locking up, I couldn't access the root files, as well as many other issues. I tried installing BusyBox to see if that helped. I was able to access the root files, but if I moved or deleted anything, the phone would begin to freeze up again. Every time it froze and I would restart it, I would lose cell service until I rebooted the phone between 4 - 6 times. Finally what I figured out is that the folder BusyBox was installing the applets in, /system/sbin, were fighting against Magisk and it's BusyBox. After deleting BusyBox and reinstalling it in /system/bin and applying the option to have it reinstalled upon every boot, I have no issues accessing and modifying the root system. Don't know if anyone else has had trouble with that, but if so I hope this helps. Now if I could only figure out why I lose stock recovery once the phone is rooted or could even install TWRP I'd be doing pretty good.