Database Users

[Q] Can't get root to restore

I have Voodoo OTA Rootkeeper installed & had done a temp unroot, so I could access Amazon prime content, but now I can't get it to restore the root. Any ideas what I'm doing wrong? And it does say "root su restored" after I push the "restore root" button, but even after 2 device restarts, I'm still unrooted. NEED to get on the regular market!

Could it be because it update the os to 6.2? I don't recall what it was before & it never ASKED me to update it, but idk

LoriH7 said:
Could it be because it updated the OS to 6.2? I don't recall what it was before & it never ASKED me to update it, but I don't know.
Click to expand...
Click to collapse
I doubt it, it's working fine for me and many others on 6.2.

If you used it to unroot before 6.2, then when 6.2 silently upgraded, it would have undone the rooting and killed your OTA rooting.
6.2 didn't ask anyone. if you had wifi connected, it would download without messages. and at some point it would have rebooted, like for me. Or others said once they turned it off it went ahead and did it.
super one click will reroot it in less than a minute and you should be good until next time they do this.

Thelgow said:
If you used it to unroot before 6.2, then when 6.2 silently upgraded, it would have undone the rooting and killed your OTA rooting.
6.2 didn't ask anyone. if you had wifi connected, it would download without messages. and at some point it would have rebooted, like for me. Or others said once they turned it off it went ahead and did it.
super one click will reroot it in less than a minute and you should be good until next time they do this.
Click to expand...
Click to collapse
Thanks! I'd bet that's what happened. It's almost always connected to wifi & I've had it rooted for a couple of weeks. Thanks. Back to super one click....

Ok, so I rerooted, but all of my google services are broken still. Reinstalled the apks, but it refuses to install the googleframework.apk. It's on there, asks me about permissions & then says it won't install. I'm clearly missing a step or something.

wierd issue
When I try to reroot my KF after the 6.2 update it roots the device then attempts to reboot into root... and that is when it fails... it just sits on the kindle fire screen flashing like it is rebooting I let it sit for a few minutes and never fineness, however if I hold down the power it will shutdown and I can start it back up but only half way rooted ... and never finished installing superuser or busybody... any ideas?

Not sure about those issues. Different people reported different problems.
Seems not everyone used the same methods. for me googleframework and market worked perfectly fine afterwards, i didnt need to do anything else.

Once my KF updated to 6.2, I could not restore root through OTA Rootkeeper either. Connected it to my computer, ran SuperOneClick, root was restored and backed up my root once again. I think I needed to reset once to ensure that all of my sideloaded apks still worked.

Well I got it figured out I just did a factory reset and reapplied root and now it is working thanks guys
Sent from my Kindle Fire using xda premium

[Q] Encrypting a Galaxy Note 3

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.

Rooting Issue

Ive got a weird issue that I cant seem to get around and I wanted to see if anyone else has had this problem.
I got a replacement phone from Verizon last week. It came preinstalled with JB and since we have Towelroot now, I let it take the OTA update.
I rooted with Towelroot and when I went to install SuperSU, it tells me Knox is active and asks me to disable and I say yes. At that point, the phone just sits there and grinds on disabling Knox. Ive let it sit an hour and it still just sits there grinding on Knox. Its never finished disabling Knox the first time and Ive flashed the phone back to factory and re-rooted 4 times now, Everytime its the same.
If I reboot after that and re-run SuperSU, it gives me the Knox warning again and when I say Okay, it immediately says Knox is disabled.
Check root and it shows Im rooted and behaves as such.
Then the problems start. I start getting stuff FCing all over the place. Ive tried to do a Fix Permissions from within BusyBox and that didnt seem to help at all. I unrooted and the problems went away. I rooted again and they came back and then I got stuck on the SuperSU Binary Needs To Be Updated loop where every time I update, it fails and closes SuperSU.
Has anyone had this issue and if so, did you figure out a way around it?

I had Same errors installing Chainfire's SuperSu Pro
But all is working good now.
it Gives root to what ever I grant access to, so no complaints here.
I Have seen other posts with same issue so I am sure CF is aware and working on the issue.
Also, I have not had any FC's since rooting and installing SuperSu

Thanks for the reply.. I think the FCs are due to Knox not being disabled properly but Im not sure.
Did Knox disable okay for you?

Can I use "Factory data reset" on MK2 rooted phone?

I'm running MK2 rooted and recently my phone stopped charging. I've tried everything to get it to work, I'm fairly certain it's a hardware failure. I know I can probably replace the connector myself, but I prefer warranty. I've backed up everything (via cloud) and now I want to restore to factory settings. I can't use ODIN because the problem also prevents me from connecting to a computer.
Is it safe to perform the phone's "Factory data reset". Will have restore to factory setup?
Thanks.

dwestall said:
I'm running MK2 rooted and recently my phone stopped charging. I've tried everything to get it to work, I'm fairly certain it's a hardware failure. I know I can probably replace the connector myself, but I prefer warranty. I've backed up everything (via cloud) and now I want to restore to factory settings. I can't use ODIN because the problem also prevents me from connecting to a computer.
Is it safe to perform the phone's "Factory data reset". Will have restore to factory setup?
Thanks.
Click to expand...
Click to collapse
It should work just fine. Keep in mind the root binary is installed to system though so you might get custom flag for that.

I don't think factory reset works on rooted phones that have been encrypted.

Tronicus said:
I don't think factory reset works on rooted phones that have been encrypted.
Click to expand...
Click to collapse
My phone is not encrypted, but thanks for the tip.
DeadlySin9 said:
It should work just fine. Keep in mind the root binary is installed to system though so you might get custom flag for that.
Click to expand...
Click to collapse
I'm only rooted and haven't installed a custom recovery or custom rom. If I factory reset, can at&t tell my phone was once rooted?

dwestall said:
My phone is not encrypted, but thanks for the tip.
I'm only rooted and haven't installed a custom recovery or custom rom. If I factory reset, can at&t tell my phone was once rooted?
Click to expand...
Click to collapse
Yes, the su binary will stay there and trip the custom flag. If you want to remove that, either download and flags the ODIN package for your system or use SuperSU to unroot.
Sent from my SGH-I337 running GPE

DeadlySin9 said:
Yes, the su binary will stay there and trip the custom flag. If you want to remove that, either download and flags the ODIN package for your system or use SuperSU to unroot.
Click to expand...
Click to collapse
Can't use ODIN, the USB port doesn't work. So, I un-rooted in SuperSU, restarted the phone, then performed the Factory Data Reset. Everything is now reset, the phone still doesn't charge, the USB port still doesn't work. However, now when I turn on the phone I get the "Custom" lock icon. Not sure what I did wrong. I guess I'll have to repair it myself now?

dwestall said:
Can't use ODIN, the USB port doesn't work. So, I un-rooted in SuperSU, restarted the phone, then performed the Factory Data Reset. Everything is now reset, the phone still doesn't charge, the USB port still doesn't work. However, now when I turn on the phone I get the "Custom" lock icon. Not sure what I did wrong. I guess I'll have to repair it myself now?
Click to expand...
Click to collapse
You might of still had busybox, or if you had frozen system apps or something. I'd say see if you can use towelroot real quick, install a busybox app, remove it, and then unroot again. You also need to remove safestrap if you ever had that. Before doing that, restart your phone a few times though, as sometimes it won't change immediately or will say custom after a fresh install.

DeadlySin9 said:
You might of still had busybox, or if you had frozen system apps or something. I'd say see if you can use towelroot real quick, install a busybox app, remove it, and then unroot again. You also need to remove safestrap if you ever had that. Before doing that, restart your phone a few times though, as sometimes it won't change immediately or will say custom after a fresh install.
Click to expand...
Click to collapse
I never installed Safestrap, but I did freeze a number of system apps using Titanium Backup and I never unfroze them before I did the unroot and factory reset. I also had Xposed framework and Wanam Xposed module still installed, which I now understand can cause issues.
What would you suggest I do to get rid of the "custom" lock? I've restarted the phone 6-7 times and the lock is still there. Would running Towelroot still work with my situation? Is there anything else I need to do before I unroot again, like unfreeze apps or revert the Wanam Xposed settings?
Thanks for you help.

Note 4 reboots randomly only when rooted and it happens mostly when it's idle

I have the Note 4 (SM-N910H), I've had mine rooted for 2 weeks and it kept randomly rebooting twice or so every 1-2 days, now I've removed the root and everything seems to be working fine with no reboots for 1 week. Most (I even think all of them) of the random reboots happened while the phone was idle (screen off).
I've rooted using the CF-Auto-Root via odin.
Anyone knows why the root was causing random reboots for me? I've tried with knox disabled and enabled and with both options I get the same reboots while the phone is idle, also I would like to mention that I don't have an SD card in my phone. I tried everything, Tried a recovery reset, tried a soft reset... It only happens when I root it.
Thanks.

Sometimes xposed module can be a culprit.
Sent from my SM-N910G using xda premium

It keeps rebooting mine so if i unroot it will solve the issue?

dr.ketan said:
Sometimes xposed module can be a culprit.
Sent from my SM-N910G using xda premium
Click to expand...
Click to collapse
Xposed sucks on a stock odex roms. I suggest you flash a new rom or deodex your stock rom.

the note4 i have atm was never rooted (efuse intact), but it also reboots randomly every few days, sometimes every few hours!
so i would say root is NOT the general cause!!
maybe, or perhaps root makes it worse, but it cant be the only reason!!

TML1504 said:
the note4 i have atm was never rooted (efuse intact), but it also reboots randomly every few days, sometimes every few hours!
so i would say root is NOT the general cause!!
maybe, or perhaps root makes it worse, but it cant be the only reason!!
Click to expand...
Click to collapse
In my case it's the issue, I've had mine un-rooted for 3 weeks now with no any random reboot, I rooted it yesterday using CF auto root just to test and it rebooted today while it was idle. I've never used any Xposed modules. It's also on stock rom and stock recovery.

menko2 said:
It keeps rebooting mine so if i unroot it will solve the issue?
Click to expand...
Click to collapse
I think it's worth a try to unroot and see if the problem is solved for you.

Thank you.
Do you know how to unroot?
The biggest problem is how to pass my apps and data without Titanium that needs root access..

menko2 said:
Thank you.
Do you know how to unroot?
The biggest problem is how to pass my apps and data without Titanium that needs root access..
Click to expand...
Click to collapse
Just flash the latest stock ROM from sam mobile (http://www.sammobile.com/firmwares/) for your exact model number and CSC using odin, no data or apps will be lost and root will be automatically removed after the process.

You can install "Phone INFO ★Samsung★" from play store to know what your exact model number and CSC, you can also type all the fields you get after you open it (except for your IMEI) and write them down here to me so I can give you a link of the stock ROM from sam mobile so you just download and flash via odin.

After rooting open SuperSu and choose never for the question to also disable Knox. Until now I didn't have any unexpected reboot.

Planet X said:
After rooting open SuperSu and choose never for the question to also disable Knox. Until now I didn't have any unexpected reboot.
Click to expand...
Click to collapse
I mentioned in my original post that I tried with both, knox disabled and enabled but with both options I had the same random reboots, no matter what I do, the same problem for me as long as I am rooted. Did you have random reboots before while you are rooted and now you fixed it somehow?