SM-N900T won't encrypt after rooting...

D

digittante

Member
Aug 6, 2009
48
6
0
twitter.com
Oct 17, 2013 at 3:26 AM
Escalating to it's own thread after a lot of trial/error in others:

I can't get native Android device-level encryption to work on an SM-N900T after rooting:

  • Tried CF-Auto-Root - root successful (KNOX Warranty tripped), but won't encrypt
  • Tried Root de la Vega - root successful (KNOX Warranty remained tripped), but won't encrypt
  • Tried Xposed Framework + Wanam Xposed to reset "System" to 'Official', successful, but won't encrypt
  • Tried TriangleAway just to verify that Counter, Binary, and System reported as intended (0, official, official respectively), but won't encrypt

Multiple attempts at device-level encryption, thorough and 'fast' cause immediate reboot. I'm using password, not PIN, as required, and also testing via manually initiating encryption as well as letting ExchangeSecurityPolicy enforce it. The only way I can get device-level encryption seems to be by restoring to stock (tested multiple times).

Perhaps there's some other env bit encryption requires/checks in order to run?

Any ideas welcome.

Thanks.
 
  • Like
Reactions: Shi9k
S

sebkinne

Member
Oct 3, 2010
26
2
0
Oct 17, 2013 at 7:24 AM
I can absolutely confirm this issue. Same thing happened here. Unroot and you are set. The issue is if you root again, it will stop booting - I found out the hard way. Sucks but hey.

As encryption for me is important, I will have to wait with re-rooting the device to remove bloatware.. too bad!

Also, TWRP which usually supports encryption also does not work with this version of Samsungs encryption.
 
E

Esteef

Senior Member
Sep 12, 2010
177
57
0
Oct 17, 2013 at 8:46 PM
digittante said:
Escalating to it's own thread after a lot of trial/error in others:

I can't get native Android device-level encryption to work on an SM-N900T after rooting:

  • Tried CF-Auto-Root - root successful (KNOX Warranty tripped), but won't encrypt
  • Tried Root de la Vega - root successful (KNOX Warranty remained tripped), but won't encrypt
  • Tried Xposed Framework + Wanam Xposed to reset "System" to 'Official', successful, but won't encrypt
  • Tried TriangleAway just to verify that Counter, Binary, and System reported as intended (0, official, official respectively), but won't encrypt

Multiple attempts at device-level encryption, thorough and 'fast' cause immediate reboot. I'm using password, not PIN, as required, and also testing via manually initiating encryption as well as letting ExchangeSecurityPolicy enforce it. The only way I can get device-level encryption seems to be by restoring to stock (tested multiple times).

Perhaps there's some other env bit encryption requires/checks in order to run?

Any ideas welcome.

Thanks.
Click to expand...
How did you reset knox to 0 using Wanam Xposed? I see no option to reset "System" to "Official"...
 
yousefarman89

yousefarman89

Senior Member
Jan 29, 2012
134
7
0
Chicago
Nov 3, 2013 at 7:30 PM
webdave said:
Having the same issue...
Click to expand...
After weeks of trying different things.I Finally figured it out!! (Verizon Variant, but should work with T-Mobile Galaxy Note 3 just fine, see website)

First- Encrypt your device, before rooting
Second- Use the Kingoapp Root method, not Root De La Vega. When i used Root De La Vega, it would not work, and I would get the same error as everyone else. http://www.kingoapp.com/# is the link to the kingo root method. Its a One-Click method that took 10 minutes from start to finish. I just downloaded Multi-Window Manager to test the root, and it worked like a charm.
 
webdave

webdave

Senior Member
Mar 27, 2011
127
14
0
South Bend
www.digitaljargon.com
Nov 3, 2013 at 7:35 PM
yousefarman89 said:
After weeks of trying different things.I Finally figured it out!! (Verizon Variant, but should work with T-Mobile Galaxy Note 3 just fine, see website)

First- Encrypt your device, before rooting
Second- Use the Kingoapp Root method, not Root De La Vega. When i used Root De La Vega, it would not work, and I would get the same error as everyone else. http://www.kingoapp.com/# is the link to the kingo root method. Its a One-Click method that took 10 minutes from start to finish. I just downloaded Multi-Window Manager to test the root, and it worked like a charm.
Click to expand...
That won't work for some of us because it will trip Knox. That is the advantage of Root De La Vega right now.
 
chris19000

chris19000

Senior Member
Apr 26, 2011
50
12
0
Calgary
Dec 23, 2013 at 3:36 AM
greffel said:
Can confirm this too, not possible to root and then Encrypt. Really would like this to work.

My phone is a SM-N9005
Click to expand...
Can also confirm not limited to the Note 3. Same thing for the Note 2 updated to 4.3 as well, SGH-I317m variant. Rooted with an odin flashed root injected stock rom.

---------- Post added at 08:36 PM ---------- Previous post was at 08:26 PM ----------
yousefarman89 said:
After weeks of trying different things.I Finally figured it out!! (Verizon Variant, but should work with T-Mobile Galaxy Note 3 just fine, see website)

First- Encrypt your device, before rooting
Second- Use the Kingoapp Root method, not Root De La Vega. When i used Root De La Vega, it would not work, and I would get the same error as everyone else. http://www.kingoapp.com/# is the link to the kingo root method. Its a One-Click method that took 10 minutes from start to finish. I just downloaded Multi-Window Manager to test the root, and it worked like a charm.
Click to expand...
Regarding the kingoapp root method - did anyone else read this thread? Written in the xperia forums but some telling info regarding the dev. http://forum.xda-developers.com/showthread.php?t=2460745&page=8 Might work but could be a heavy cost.
 
A

alphahere

Senior Member
Nov 6, 2010
657
176
63
Sep 28, 2014 at 8:15 PM
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
 
Last edited:
  • Like
Reactions: dramaqueenz
S

spyngamerman

Senior Member
Oct 11, 2008
177
23
0
Oct 5, 2014 at 12:49 AM
alphahere said:
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
Click to expand...
does this apply to all samsung rooted but bootlocked devices like say verizon galaxy s5?
 
A

alphahere

Senior Member
Nov 6, 2010
657
176
63
Oct 7, 2014 at 4:30 AM
spyngamerman said:
does this apply to all samsung rooted but bootlocked devices like say verizon galaxy s5?
Click to expand...
Just tried with a Verizon Note 3 with locked bootloader after running

pkill -KILL daemonsu

No problem encrypting data partition at all. So should work with S5.

Rebooting restores root function. The above command only temporarily disables root.

Good luck.
 
Last edited:
D

dramaqueenz

New member
Oct 10, 2014
2
0
0
Oct 10, 2014 at 9:31 PM
It worked!

OMG alphahere. Thanks so much, this finally worked on my Note 3 (N9005) with X-Note Rom 4.4.2 after hours and days of searching and failing...

Well, as a newbie I had to try several times. Turns out that I didn't read your post that carefully. It seems that the term "running adb shell as ROOT", so typing "su" that you have # instead of $ in cmd, is a small but important detail to disable SuperSU-Root temporarily in order to let encryption run without getting stuck in malfunctioning Enter-Password-Screen and ergo factory reset with Stock-ODIN from the start :)

THANK YOU, You're the best!!! <3
 
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone