I need to disable PIE security on my Moto E LTE to be able to run some of my apps like Reaper, Network Spoofer, and possibly some IDEs. I've tried the flashable fixes on XDA and none has worked. I am running on CM13 with root and TWRP.
Anyone have an idea?
Related
There are threads here and there but I couldn't find anything who has gotten encryption working on a custom ROM, except on a thread that someone did it with Jedi X Rom. Anyways, I have tried the following ROMs + TWRP to encrypt with no luck:
jfltevzw_JellyBeans_B7
S4_Echoev29.1_S5PORT_VZW_090814
S4_Echoev29_VZW_100814
Danvdh-CM11-09-18-2014-M9-stable
Danvdh-GPE-5-12242014
EclipseTW-S4-v4.0.2-KitKatNC5
HyperdriveRLS20KKS4Final
All of the above ROMS, after I enable encryption, green Android comes up, reboot and then back to Android like nothing happened. I tried disabling superuser, safe mode... Closest to success was JellyBeans where it encrypted successfully but then asked password for Storage which the password did not work.
Anyone has gotten encryption working on their custom ROM? If you did, what recovery/ROM/build combination? Anything special you had to do to get it working?
I disabled SU, ran the encryption then re-rooted. I was running stock NC5 so not really "custom," but it worked.
ammjr71 said:
I disabled SU, ran the encryption then re-rooted. I was running stock NC5 so not really "custom," but it worked.
Click to expand...
Click to collapse
Oh so many questions...
Which stock NC5 you were running - Can you point me to the file?
How did you install to your S4? Odin/recovery?
Which recovery do you have TWRP/CWM?
Why didn't you just enable SU after encryption instead of re-rooting?
Lastly, was using a PIN enabled available for encryption for this ROM or did you have to use a password instead?
Sorry for all the questions, but I see light at the end of the tunnel. I was going to go back to stock so that I can enable encryption. (My company policy requires 'Google Apps Device Policy')
Thanks!
ammjr71 - which stock NC5 ROM did you use?
Anyone else out there to successfully encrypt a rooted ROM?
OK, I think I see the light at the end of the tunnel for encryption on a custom ROM.
This method seems to work for most of the custom ROMs:
In SuperSU, uncheck 'enable superuser' and then in application manager, Turn off SuperSU. Make sure SuperSU is in turned off page. After that, reboot and encrypt should work... Also, I noticed for encryption to work, security software version under about phone should not be blank. It should be something like MDF v1.0 Release 3.. Lastly, try a password with 6 characters and one number; not a simple 4 digit PIN.
Does anyone have any idea why the xt1039, moti g 4g cannot detect the sim card after i downloaded cyanogenmld 12, aka pergine onto to ir? What am i doing wrong?? Or is it a. Cm12 bug?
Hi, I have almost the same problem. After installing LP 5.1.1 (all LP for Samsung Vibrant) I lose root access. When I flash superSU for root access then I lose mobile services.
Same problem on d605, can't load modem firmware.
My Marshmallow device is rooted and Greenify is running in Root mode. When I check the enable Aggressive Doze mode option it checks but it unchecks itself when I go back an access the menu again. I don't know why. Can anyone help me fix this ?
I'm also having this issue with Sultan's CM13 for the OnePlus One.
I check "Aggressive Doze", leave settings, then re-enter to find that it has been unchecked. Even after a reboot, this still happens.
bhatt095 said:
My Marshmallow device is rooted and Greenify is running in Root mode. When I check the enable Aggressive Doze mode option it checks but it unchecks itself when I go back an access the menu again. I don't know why. Can anyone help me fix this ?
Click to expand...
Click to collapse
Is it enabled in Device Administrator? Do you have the latest Supersu?
Try uninstalling and reinstalling.
tnsmani said:
Is it enabled in Device Administrator? Do you have the latest Supersu?
Try uninstalling and reinstalling.
Click to expand...
Click to collapse
Yes. I've the latest SuperSU . I tried uninstalling and reinstalling the 2.8 beta 1 and beta 2. Still it doesn't work. Btw I'm using Unofficial CM 13 on Moto G 1st gen XT1033..
I followed the instructions here to sim-unlock my Verizon XT1528 and am now using it on Consumer Cellular. I have disabled most of the built-in verizon and moto apps, however it seems that the OTA updater has already downloaded a system update, as it keeps repeatedly prompting me to install the update.
Will installing the update cause any issues with my current service? Will it need to be re-unlocked? Or will it continue working the way it is after the update has been installed? Or will the "other improvements" make it useless to me.
The current software version is 23.11.17.survia_verizon.verizon.en.US.vzw, build # LPI23.29-17, android version 5.1 (screenshot)
The new software version it wants to install is 23.16.5.en.US. (and it really wants to install it!).
Part of the reason I'm concerned is that according to the page on their website, "This update brings Android™ 5.1 Lollipop to your phone along with other improvements", however the phone already has 5.1 on it.
To be clear, I am talking about the verizon XT1528 Moto E 2nd Generation with the locked bootloader--it is not possible to root it or install another ROM.
Lastly, if updating will lock me out of using Consumer Cellular on it, is there any way to remove the update and/or prevent the prompt from showing up again.
@StanSt
For what it worth this is what mine is running. I'm on AT&T though. I don't know if that would make any difference or not.
Worked Fine
I updated my wife's xt1528. GSM still works.
crazyjim_68 said:
I updated my wife's xt1528. GSM still works.
Click to expand...
Click to collapse
Note that the original post was inquiring about a previous update.
There is an update in the past couple of days or so (late April - early May 2016) that brings it up to 23.201.2 etc etc , build LPIS 23.29-17.5.-2
Moto says changes are "Includes the updates of Android security patches until April 1st 2016."
GSM still works after this latest May update.
Hey there fellow XDA forum members, I am currently running stock 6.0 Marshmallow on my Moto E XT1527 Surnia (Telus) and have that squid build of TWRP and it runs fine. Now here's where I run into issues... I've tried twice now to flash the SuperSU Update zip but when I boot into recovery TWRP doesn't ask me if I want to install SuperSU, and not sure but I didn't check the box for "keep read only" and just swiped right; does that matter? Anyhow; back to my OP, is there a way to get SuperSU Update to stick? Cause after flashing the zip as aforementioned, and reboot system, it just hangs at the white warning bootloader unlocked screen...why?? And I heard about systemless root for 6.0 but honestly don't know where to begin, and thought there would've been a tutuorial or a guide but have yet to find one, any help is greatly appreciated, thanks!
I posted this recently.. [XT1527] Install Systemless Root on Marshmallow
It was on page 2
I used that method and i have the same phone as you.
It's still working good for me but you may want to toggle namespace separation on or off
if some app's give you issues.
If you have Busybox installed then make sure it's using a recent newer version that is fixed for this issue too.