Database Users

Encrypting after root?

Has anyone been able to encrypt the N3 after rooting? I can't get it to go and it is mandatory for my work email to be pushed to my phone.\
edit: I've now tried manually using the settings menu. Even after setting a "high security password" it just flashed the android encrypt icon, reboots and then goes right back into the system. I've tried doing "fast encryption" as well and that doesn't work either.
edit 2: If anyone is wondering I didn't get this to work, however, after some searching I was able to find that Touchdown does encryption and will enforce all policies within the touchdown app itself keeping it separate from the rest of the phone. So I'm able to get my work email, not have to encrypt my entire phone, and stay within policy compliance. I just wish touchdown integrated with the stock calendar.... can't win 'em all.

Flying_Hellfish said:
Has anyone been able to encrypt the N3 after rooting? I can't get it to go and it is mandatory for my work email to be pushed to my phone.\
edit: I've now tried manually using the settings menu. Even after setting a "high security password" it just flashed the android encrypt icon, reboots and then goes right back into the system. I've tried doing "fast encryption" as well and that doesn't work either.
edit 2: If anyone is wondering I didn't get this to work, however, after some searching I was able to find that Touchdown does encryption and will enforce all policies within the touchdown app itself keeping it separate from the rest of the phone. So I'm able to get my work email, not have to encrypt my entire phone, and stay within policy compliance. I just wish touchdown integrated with the stock calendar.... can't win 'em all.
Click to expand...
Click to collapse
I've noticed this as well. Can't encrypt device when System reports "Custom". Currently it seems the only path to device encryption is restoring un-rooted stock firmware. . . .

This is driving me nuts since I have to encrypt my device do to Coporate net.
encrypt first then root - Don't work
Root first then encrypt- Don't work
can anyone else confirm this ?

greffel said:
This is driving me nuts since I have to encrypt my device do to Coporate net.
encrypt first then root - Don't work
Root first then encrypt- Don't work
can anyone else confirm this ?
Click to expand...
Click to collapse
im not a dev but have read about this issue from S3 and up and the only positive thing i have seen is that it can be possible when TWRP can be installed it "can" support encryption. i dont think you will find a solution without recovery option.

greffel said:
This is driving me nuts since I have to encrypt my device do to Coporate net.
encrypt first then root - Don't work
Root first then encrypt- Don't work
can anyone else confirm this ?
Click to expand...
Click to collapse
Confirmed. I've tried repeatedly to root-then-encrypt. All attempts failed. As soon as I un-rooted and rebooted, I was able to encrypt.

digittante said:
Confirmed. I've tried repeatedly to root-then-encrypt. All attempts failed. As soon as I un-rooted and rebooted, I was able to encrypt.
Click to expand...
Click to collapse
After weeks of trying different things.I Finally figured it out!!
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.

[Q] Beating MobileIron on a Rooted S4 [MDL]

First my phone's details:
Rooted
Model: Samsung-SGH-I337 (AT&T)
Android Version: 4.2.2
Build: JDQ39.I337UCUAAMDL
Here's the situation...
I'm an IT guy (low on totem) and we're in the Pilot phase for Android using MobileIron. I have a rooted AT&T 32GB S4 and I'm trying to fool MobileIron into believing my phone is compliant. I have done lots of reading on this subject, and nothing has helped, to this point. I have access to the MobileIron server, so I can register, and de-register, my device as often as I want. I plan on reporting this back to the people who get paid more than I do to let them know how secure this is.
Here's what I've tried:
1. I have installed Xposed Framework, and installed RootCloak, but it has zero effect on MobileIron. I couldn't even get to the point in MobileIron setup where I could download our 'secure apps'. (I am aware that RootCloak moved to Cydia, but I read it wasn't as good)
2. I tried using 'Hide My Root' from Play, and that also had zero effect on MobileIron; I got no further than I did with RootCloak.
3. I tried using 'Hide Rooting Lite' from Play, and I was able to download our 'secure apps', and MI required that I create a password/pattern to unlock my phone. In my opinion, this got past the first level of authentication that MI requires, which is a step in the right direction. I have recently learned that MI also scans your list of installed APPs for any APP that requires root.
Do any of you think that changing the names of some of my apps (Titanium Backup, Root Explorer, etc.) would help fool MobileIron? What about trying to DualBoot ROMS? If the secondary ROM that I setup is not rooted, and I have MI installed on it, would it be able to detect root from my primary ROM?
Any help, or ideas that I have not thought of yet, that you geniuses can provide would be greatly appreciated!!

GatorRuss said:
First my phone's details:
Rooted
Model: Samsung-SGH-I337 (AT&T)
Android Version: 4.2.2
Build: JDQ39.I337UCUAAMDL
Here's the situation...
I'm an IT guy (low on totem) and we're in the Pilot phase for Android using MobileIron. I have a rooted AT&T 32GB S4 and I'm trying to fool MobileIron into believing my phone is compliant. I have done lots of reading on this subject, and nothing has helped, to this point. I have access to the MobileIron server, so I can register, and de-register, my device as often as I want. I plan on reporting this back to the people who get paid more than I do to let them know how secure this is.
Here's what I've tried:
1. I have installed Xposed Framework, and installed RootCloak, but it has zero effect on MobileIron. I couldn't even get to the point in MobileIron setup where I could download our 'secure apps'. (I am aware that RootCloak moved to Cydia, but I read it wasn't as good)
2. I tried using 'Hide My Root' from Play, and that also had zero effect on MobileIron; I got no further than I did with RootCloak.
3. I tried using 'Hide Rooting Lite' from Play, and I was able to download our 'secure apps', and MI required that I create a password/pattern to unlock my phone. In my opinion, this got past the first level of authentication that MI requires, which is a step in the right direction. I have recently learned that MI also scans your list of installed APPs for any APP that requires root.
Do any of you think that changing the names of some of my apps (Titanium Backup, Root Explorer, etc.) would help fool MobileIron? What about trying to DualBoot ROMS? If the secondary ROM that I setup is not rooted, and I have MI installed on it, would it be able to detect root from my primary ROM?
Any help, or ideas that I have not thought of yet, that you geniuses can provide would be greatly appreciated!!
Click to expand...
Click to collapse
Hi! Any luck with beating mobile iron?

MobileIron is kicking my ass. I have a Nexus 5 that's never been rooted and I can't get MI to install on this device. Is it because the bootloader is unlocked? I'm in IT as well, and our MobileIron administrators have NO IDEA what to do.

Broadscope said:
MobileIron is kicking my ass. I have a Nexus 5 that's never been rooted and I can't get MI to install on this device. Is it because the bootloader is unlocked? I'm in IT as well, and our MobileIron administrators have NO IDEA what to do.
Click to expand...
Click to collapse
I had a similar issue in my non-rooted M8. MI started working after I did a factory reset .

[Q] Can't Enable Unknown Sources

Hello: I have an AT&T I337 that until 2 days ago had stock ROM on it. I didn't like the fact that AT&T blocked my ability to 1) tether, and 2) sideload so after about 1 1/2 years I finally decided to root and flash a ROM that would allow me to do these things. I downgraded from NB1 to MK2, rooted with saferoot, installed safestrap, and installed Deadly Venom's v3.0.2 NC1 KitKat ROM. Since there are some outstanding instructions in the AT&T GS4 forum I was able to do all this relatively easily (and I'm pretty much a NOOB) and I'm really happy with the ROM so far. The Wi-Fi Hotspot capabilities seem to work well; the only problem is that I still can't sideload. The "Unknown sources" option under "Security" in settings is greyed out and unchecked (so are "Wait for debugger" and "Verify apps via USB," under "Developer options," but I don't think I need those items for anything). Does anyone else have this problem? Or more importantly, does anyone know how to enable "Unknown sources" so I can install apps from the Amazon Appstore, etc.? I thought for sure that rooting would be the solution, if not the custom ROM. I even tried using the AndroidCentral Sideload Wonder Machine v1.2 that someone mentioned would install apk's regardless of the phone's security settings -- it didn't. Any assistance would be greatly appreciated. Thanks...

It should be some "device administrator" app that is causing this.
Sent from my SGH-I337 running GPE using Tapatalk

You're right!
I just figured out that it was indeed my employer requiring device administrator privilege in order for me to sync my work email on my phone. I removed the email admin account and all my security restrictions cleared (along with my email account, unfortunately). Thanks for your advice, Case closed!

K
Sent from my GT-I9300 using XDA Premium 4 mobile app

Can't enable unknown sources
It's not for me it didin't work for my phone....anymore solution that you can give me?I searched alot of websites and i hope this one works,
Thanks

Android Pay not working.

I Haven't rooted my phone yet but it keeps telling me this when I open android pay, when I first got my phone I set my up my card but now it saying that phone is either rooted or bootloader unlocked which isn't the case.
On Vodafone UK, before this I used my OP3 with Magisk with Android Pay but I haven't used that since I've got my s8 so I'm not sure what the issue could be.
Any insight to this?
Besides the usual factory reset.

same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that

I'm having the same issue on a Galaxy S8 via Tmobile. I've never rooted it, have no clue if the bootloader is unlocked and I'm stock since I reset the phone the first time I got the error. Still getting the error and Android pay help chat was not useful.

Same issue here, on Voda UK. I used Package Disabler pro and thinking I might have disabled something I need.

So since I had OEM unlock enabled after disabling it, it passes and safetynet now.

I had no problems adding cards, but a few days later when I wanted to add more cards, I get the error. I can't remember what I did in between that would've caused this, but definitely not rooting! I turned developer option to off and still get the error.
My S7 is rooted and TWRPed and have no problems adding cards!!!!???

Very weird. Working just fine on my rooted s8+ with magisk.

I'm on T-Mobile with a S8 and Android Pay connected to my PayPal is getting card read error everywhere I try to use it.
Safety net says everything is ok too. Not sure what's going on. I have the newest update and not rooted.
Sent from my SM-G950U using Tapatalk

I installed different Samsung Pay Framework apk and now I want to revert back and downgrade to another version to make Spay work.. when I click uninstall updates it wont let me. (Gives message that App is needed by system administrator.. when I open sys admin nothing there. hidden app)
Any ideas or suggestions on how to downgrade Samsung Pay Framework?
Thank you in advance,
Joe

xeathpk said:
Very weird. Working just fine on my rooted s8+ with magisk.
Click to expand...
Click to collapse
Hi Can you let me know how you managed to root with Magisk and get Android pay etc to work?
My phone:
Model: SM-G955F
SW: G955FXXU1AQF7
I tried rooted and couldn't get it working, and now recovered to official ROM and still can't get it to work?!?

Dont you people know anythin?
All EU(exynos) S8 and other galaxies come with unlocked bootloaders. Thats causing the problem
Lock it

Hi all,
I already posted a question in the Official stock upgrade but it got lost in the other comments, so I'm trying my luck again.
I had an italian branded SM-G950F (OMN), I wanted to remove all the Vodafone stuff, so I installed a MULTI-CSC as per the official stock firmware upgrade thread, when I did it I had my Australian sim card in and I got a weird UK CSC (the multi CSC didn't have australia in it), after installing everything I noticed that Android Pay didn't work, so I did a factory reset with my italian sim card in and still Android Pay was complaining that my firmware was modified or rooted.
I decided to use an australian specific firmware so I downloaded an XSA firmware and did the procedure again.
At this stage Secure Folder and Samsung Pay work (the phone is NOT rooted, this update has been the only "mod" I have done) but Android Pay is still saying that my rom may be modified or rooted so it doesn't open.
It is pretty important for me because my back supports android pay but not samsung pay
The phone is not rooted, if I reboot the phone in download mode the warranty void bit is 0 (which is good).
If I use Root Checker Pro, under safety net tab, I get CTS profile match as FAIL, I was thinking this could cause Android Pay to fail.
any idea?

start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF

degsyh said:
same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that
Click to expand...
Click to collapse
Does rooting in UK\Europe void our warranty?

mariuscrist said:
start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF
Click to expand...
Click to collapse
Hi mariuscrist,
I'm not sure what app can be suspicious, I have reinstalled the apps I had before the firmware update and I could use android pay then. I'll see what it can be, probably it could be worth to do a factory reset and test android pay before anything else?

Question [Question] New phone 1, unable to communicate with Google servers

I received by nothing phone 1 via beta membership (I'm in the US) and for some reason it refuses to communicate with Google servers. Whether during initial setup, trying to add a Google account, or trying to access the Play Store I am always faced with the error: There was a problem communicating with Google servers. Please try again later. I also am unable to check for updates. I get the error message: Updates are temporarily unavailable. Try again later.
I've tried two different SIMs/carriers, and three different known working WiFi networks. I did notice my phone is running Spacewar-S1.1-220813-1608EEA which implies is it's running the European firmware. Could this be what is causing the issue? Do I need to cross flash? I checked downdetector and Google doesn't appear to be having server issues at the moment. Any help or suggestions are greatly appreciated. Thanks!

wwwryan said:
I received by nothing phone 1 via beta membership (I'm in the US) and for some reason it refuses to communicate with Google servers. Whether during initial setup, trying to add a Google account, or trying to access the Play Store I am always faced with the error: There was a problem communicating with Google servers. Please try again later. I also am unable to check for updates. I get the error message: Updates are temporarily unavailable. Try again later.
I've tried two different SIMs/carriers, and three different known working WiFi networks. I did notice my phone is running Spacewar-S1.1-220813-1608EEA which implies is it's running the European firmware. Could this be what is causing the issue? Do I need to cross flash? I checked downdetector and Google doesn't appear to be having server issues at the moment. Any help or suggestions are greatly appreciated. Thanks!
Click to expand...
Click to collapse
For some reason when the sim card is inserted, it cannot connect to Google Update servers.
These are the steps I took to get my beta version working:
1. Removed sim card, factory reset, and followed the startup instructions with wi-fi only !important!.
2. After start up is complete check for updates and you should be able to connect to Google Servers/play store and download/update.
3. Then, after updates, you can shut down and insert your sim, and turn on. You can still access the Google Play store as normal, but the OS updates are still buggy.
I still have to figure out how to update with a new release is out.

Who-Lep said:
For some reason when the sim card is inserted, it cannot connect to Google Update servers.
These are the steps I took to get my beta version working:
1. Removed sim card, factory reset, and followed the startup instructions with wi-fi only !important!.
2. After start up is complete check for updates and you should be able to connect to Google Servers/play store and download/update.
3. Then, after updates, you can shut down and insert your sim, and turn on. You can still access the Google Play store as normal, but the OS updates are still buggy.
I still have to figure out how to update with a new release is out.
Click to expand...
Click to collapse
Thank you for your reply. I did just manually update to 1.1.1 via sideload. If on device OTA updates are buggy that is not a big deal. I don't mind manually updating as this phone is mostly just a test/play device and not my daily driver.
I will attempt the steps you mentioned and setup with WiFi only with no SIM card installed and see if that helps. Thanks again!
Random side question: Are you running 1.1.x latest or 1.5.x? If 1.5.x, is it worth upgrading for Android 13 or is it more buggy? Thanks!

@Who-Lep thank you so much, that indeed fixed the issue. Once I factory reset and completed all setup without any SIM card inserted communicating with Google servers worked correctly. Much appreciated!

wwwryan said:
@Who-Lep thank you so much, that indeed fixed the issue. Once I factory reset and completed all setup without any SIM card inserted communicating with Google servers worked correctly. Much appreciated!
Click to expand...
Click to collapse
Awesome, no problem, glad it worked out!
I went straight through all the updates to the latest beta 1.5.1 Beta 2, so I can't really compare but, no major bugs on newest release, only had to reboot once because of UI glitch and hasn't happen again.