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

[alphahere]

New instructions.

This should work with all rooted samsung devices that are using supersu.

Install busybox and run the following commands from a command prompt (adb shell or a terminal app).

[email protected]:/ $ su
[email protected]:/# pkill -KILL daemonsu

You should be back at the "$" prompt. Don't type any other commands or reboot the device! Encrypt the device now.

Hopefully these instructions are better.

 

[spyngamerman]

thanks seems i must have missed something last time i tried seems to be working now see it starting to encrypt woot

Made my evening

 

[nastea]

Fantastic......Been trying to do this for a month and finally stumbled upon this post. So far AT&T S5 Active, being encrypted....Thanks!

 

[Nime Cloud]

This should work with all rooted samsung devices that are using supersu.

Install busybox and run the following commands from a command prompt (adb shell or a terminal app).

[email protected]:/ $ su
[email protected]:/# pkill -KILL daemonsu

You should be back at the "$" prompt. Don't type any other commands or reboot the device! Encrypt the device now.

Hopefully these instructions are better.

DO NOT reboot after these commands, just go to encryption and encrypt the phone.

 

[darkman088]

This should work with all rooted samsung devices that are using supersu.

Install busybox and run the following commands from a command prompt (adb shell or a terminal app).

[email protected]:/ $ su
[email protected]w:/# pkill -KILL daemonsu

You should be back at the "$" prompt. Don't type any other commands or reboot the device! Encrypt the device now.

Hopefully these instructions are better.

Hello,

can you please make these instructions more specific ? Shall the phone be started in Safe mode first ?
What is adb shell ? Launched from TWRP or from an app, installed within the Android OS ?
Yesterday I tried this:
1. I have installed the latest Busybox free version
2. I have installed a terminal app.
3. I tried to find a running daemonsu process using ps -l | grep daemonsu - nothing was displayed
4. I executed pkill -KILL daemonsu anyway. It really turned the prompt to $
5. I went to encrypt the phone - it showed a lock, after 2-3 minutes it rebooted and nothing was encrypted.
Could it be, that all the Custom ROMs which I tried, simply don't provide the module(s) for encryption (KNOX or
whatever) ? How can I check that ?
There is ONLY one ROM for Note 3, with which I could encrypt my device:

http://forum.xda-developers.com/showthread.php?t=3349306

but unfortunately, it doesn't provide any possibility to encrypt the SD card. Also, when I connect the phone
to my laptop, only the Internal storage is shown, not the SD card. I did NOT format it as internal storage. It's
just there and all the files can be seen from the phone, but not from the laptop. I was googling this like mad
and didn't find a similar case.

What am I doing wrong ? I'm really getting desperate, I am fighting more than a week with these problems
and still no solution on the horizon :-/ I tried virtually any Marshmallow ROM for Note 3 I could find.

 

[MasterBrush]

Are these instructions still working for Android 5.x or 6.x
I tried it with my rooted S5 running Android 5, but it doesnt work

UPDATE:
I managed to encrypt the device. It works when I put the device in safe mode and do the "pkill -KILL daemonsu"
But now the password I entered doesnt work. I tried to encrypt 2 times now, just to make sure I enter the right password, but the password I set before is not working after encryption.

This should work with all rooted samsung devices that are using supersu.

Install busybox and run the following commands from a command prompt (adb shell or a terminal app).

[email protected]:/ $ su
[email protected]:/# pkill -KILL daemonsu

You should be back at the "$" prompt. Don't type any other commands or reboot the device! Encrypt the device now.

Hopefully these instructions are better.

 

[darkman088]

Are these instructions still working for Android 5.x or 6.x
I tried it with my rooted S5 running Android 5, but it doesnt work

UPDATE:
I managed to encrypt the device. It works when I put the device in safe mode and do the "pkill -KILL daemonsu"
But now the password I entered doesnt work. I tried to encrypt 2 times now, just to make sure I enter the right password, but the password I set before is not working after encryption.

Hello,

it looks like you are one step ahead! How did you run pkill -KILL daemonsu in safe mode ? I have tried this, but my terminal app was disabled and I couldn't launch it, so I couldn't run the command

Regarding your question - did you try to wipe the phone with a factory reset ? This should get rid of all previous encryption keys. What is your custom recovery ? I had huge problems with TWRP 2.8.7.0 - it wasn't wiping the phone correctly and it was still asking for some unknown password - it was a REAL MESS !!
Then I was successful with the latest TWRP version. Hope this helps...

 

[MasterBrush]

Hello,

it looks like you are one step ahead! How did you run pkill -KILL daemonsu in safe mode ? I have tried this, but my terminal app was disabled and I couldn't launch it, so I couldn't run the command

Regarding your question - did you try to wipe the phone with a factory reset ? This should get rid of all previous encryption keys. What is your custom recovery ? I had huge problems with TWRP 2.8.7.0 - it wasn't wiping the phone correctly and it was still asking for some unknown password - it was a REAL MESS !!
Then I was successful with the latest TWRP version. Hope this helps...

In safe mode, I used adb shell to run the pkill command. Terminal app wouldnt run in safe mode.

Yes I tried also factory reset and right after reset to encrypt. Same issue, encryption sucessful, but entering password doesnt work.
I have stock recovery installed.

 

[darkman088]

In safe mode, I used adb shell to run the pkill command. Terminal app wouldnt run in safe mode.

Yes I tried also factory reset and right after reset to encrypt. Same issue, encryption sucessful, but entering password doesnt work.
I have stock recovery installed.

Can you please enlighten me on what adb shell is ? I think I can enter it from TWRP but then the OS is not running and when it starts, daemonsu will be active again.
Is it necessary to connect the phone to a computer to run adb shell ? Is there an app called adb shell that runs in safe mode ? I'm quite confused

 

[MasterBrush]

Can you please enlighten me on what adb shell is ? I think I can enter it from TWRP but then the OS is not running and when it starts, daemonsu will be active again.
Is it necessary to connect the phone to a computer to run adb shell ? Is there an app called adb shell that runs in safe mode ? I'm quite confused

adb shell: you need install adb shell on your computer and connect phone via usb.

 

[darkman088]

Fine, I can do that, but can you please provide a download link and a detailed procedure on how to do that ?
Do I need to enable USB debug mode ? Many thanks

---------- Post added at 03:19 PM ---------- Previous post was at 03:12 PM ----------

OK, I found it and I've downloaded it, it's a really small package:

http://adbshell.com/downloads

But when I launch adb.exe, it just gives me 1000 options, please kindly let me know
what syntax do I have to use and if I need USB debug mode. Many thanks in advance!

 

[darkman088]

adb shell: you need install adb shell on your computer and connect phone via usb.

OK, I've done that, but absolutely no effect. The phone still restarts after appx. 2 minutes without any error and encryption is not in place.

 

[darkman088]

In safe mode, I used adb shell to run the pkill command. Terminal app wouldnt run in safe mode.

Yes I tried also factory reset and right after reset to encrypt. Same issue, encryption sucessful, but entering password doesnt work.
I have stock recovery installed.

Dear MasterBrush,

what is your magic for this to be working ? Do I still need to install BusyBox ? Do I need to enable USB debug mode ? PLEASE HELP me, I'm really desperate with this...

P. S.: Tried also with busybox installed. The same effect - reboot after 2 minutes and no encryption

 

[Miguel angelor9]

It would be a correction of what?

This should work with all rooted samsung devices that are using supersu.

Install busybox and run the following commands from a command prompt (adb shell or a terminal app).

[email protected]:/ $ su
[email protected]:/# pkill -KILL daemonsu

You should be back at the "$" prompt. Don't type any other commands or reboot the device! Encrypt the device now.

Hopefully these instructions are better.

hello! I have custom rom cynogenmod you podria best esplicar this procedure? how to apply this line then command or as it is concerned, applied in terminal android more unsuccessful application! A doubt could reverse patcher error for android when using lucky patcher application! Making this process ...:good::goodne more question I am with busybox installed, a problem ?remembering what my device is galaxy s5 Korean base, sm-g900s.the image can be seen on CyanogenMod 13 Android 6.0 applied in su, enabled!

 

[baalpeteor]

WOW

YOU ARE GOOD. someone get this man a BEER!!

This should work with all rooted samsung devices that are using supersu.

Install busybox and run the following commands from a command prompt (adb shell or a terminal app).

[email protected]:/ $ su
[email protected]:/# pkill -KILL daemonsu

You should be back at the "$" prompt. Don't type any other commands or reboot the device! Encrypt the device now.

Hopefully these instructions are better.

 

[Ogt192]

I think I bricked my phone, help please!

Can anyone help me out with this? I might have bricked my phone.

I followed the instructions. I had recently rooted my phone and installed busy box. I used the terminal emulator from busy box.

I put in the commands and went to encrypt. The phone went through encryption, now it's trying to start and it's been stuck at the Samsung animation for over 12 hours. I tried turning it off and on a couple times. Still stuck.

I can get into the (vol down + home + power button) area. Is there a way to get it to start?

Can I factory reset it? Or fix the brick somehow?

Any help would be appreciated.