I have a 1st gen motoX that I rooted ages ago with slapmymoto/pwnmymoto. It's stock, never messed with the bootloader. Never changed the ROM, it's running stock android 4.4.
Got a new job and requires encryption. If I try to encrypt it, will I break my phone? Alternatively, will it even work to encrypt it?
I've searched and see some details for other phones, but couldn't find this in my situation. If it's been asked/answered, my apologies.
Thanks so much for the help!:good:
You should be fine. It only really encrypts /data, anyway.
Related
So I have been reading around and it seems Lollipop will not encrypt with a rooted system image for the Droid Turbo. It simply gives a blank screen and you have to restart the Phone. I have also seen that if you downgrade to 4.4.4, encrypt, upgrade to 5.1 then you will have rooted Lollipop on the Droid Turbo with encryption. If your an encryption nut like I am, or someone who needs encryption for work, this should be what your looking for. The first step is to go back to unrooted 4.4.4 Kit Kat, I used the steps in this guide.
http://www.theandroidsoul.com/verizon-droid-turbo-xt1254-back-to-stock-downgrade-and-unroot-to-get-stock-recovery-and-stock-system-back-81328/?PageSpeed=noscript.
It worked like a charm. as soon as the flash was complete I went to recovery and factory reset. No way around this part, make sure you back up. I then booted into my phone, set up my gmail account and put my phone into flight mode to kill any signals and updates. I then encrypted it. After that I followed the instructions on Computerfreek274's post and image.
http://forum.xda-developers.com/droid-turbo/development/computerfreek274turbolollipop-t3147455
Seemed to work perfectly, it picked everything up and recognized it as encrypted. Yay for end user security! Thanks to everyone who makes this possible!
So you can upgrade system files with an encrypted device? Just how much of the phone is encrypted?
Unless I miss my guess, it looks like the whole thing, except the bootloader, gets encrypted. But you can upgrade the image of an encrypted device.
So I loaded up TWRP and Despair Kernel yesterday and rooted my N6 yesterday. There's not much going on yet as far as I understand because Xposed still isn't ready for Marshmallow and the new OS has a lot of great features I don't feel like I really need root, unless for adblocking. Anyways, so I refreshed back to stock through Fastboot, however now Android Pay states it cannot verify the system as if I was still rooted, which I am not. Has anyone experienced this?
Is it possible that the system partition is still R/W? I looked for a way to wipe the device completely and start back up from scratch, meaning erasing partitions, recreating them, etc. but could not find any information on it. Any help would be great as I have a horrible memory and constantly forget my wallet, so Android pay would do a great deal of good as far as I am concerned. Thanks guys.
Nooblet said:
So I loaded up TWRP and Despair Kernel yesterday and rooted my N6 yesterday. There's not much going on yet as far as I understand because Xposed still isn't ready for Marshmallow and the new OS has a lot of great features I don't feel like I really need root, unless for adblocking. Anyways, so I refreshed back to stock through Fastboot, however now Android Pay states it cannot verify the system as if I was still rooted, which I am not. Has anyone experienced this?
Is it possible that the system partition is still R/W? I looked for a way to wipe the device completely and start back up from scratch, meaning erasing partitions, recreating them, etc. but could not find any information on it. Any help would be great as I have a horrible memory and constantly forget my wallet, so Android pay would do a great deal of good as far as I am concerned. Thanks guys.
Click to expand...
Click to collapse
fastboot a factory image, thats the only way.
simms22 said:
fastboot a factory image, thats the only way.
Click to expand...
Click to collapse
Already have done that, still not working. After looking at reviews it seems to be an on going problem.
Sent from my Nexus 6 using Tapatalk
So this is almost the best phone in existence, except for one thing. It cannot be encrypted using the normal procedure. Choosing the encryption option simply restarts the phone. I have tried unrooting my phone then encrypting, I had the same issue. This same issue happened with MoFo'ed images before we had bootloader unlock. We got around it by loading an unrooted image, setting it up enough to encrypt the phone, then reloading the rooted image with MoFo root. Does anyone know if this could work again? Does anyone know if their is a way to "side encrypt" the phone by connecting it to a computer? I am currently running CM 12.1 with the newest update. Thanks for the help!
I did a couple of searches and came up empty but I am wondering if any ROM developers are working with encryption and root?
When I had my Galaxy S5 (Tmobile) it was first encrypted. I recall then once I rooted it I was no longer able to encrypt the device. I think there may have been some workarounds but they were pretty cumbersome to say they even worked at all.
I'm wondering if any developers are working that angle and if so should my inquiry be presented to developer of said ROM?
I also realize that encrypted devices do tend to read a bit slower than those no encrypted but I think I can live with that.
Please advise.
Best,
Hiatt
cwhiatt said:
I did a couple of searches and came up empty but I am wondering if any ROM developers are working with encryption and root?
When I had my Galaxy S5 (Tmobile) it was first encrypted. I recall then once I rooted it I was no longer able to encrypt the device. I think there may have been some workarounds but they were pretty cumbersome to say they even worked at all.
I'm wondering if any developers are working that angle and if so should my inquiry be presented to developer of said ROM?
I also realize that encrypted devices do tend to read a bit slower than those no encrypted but I think I can live with that.
Please advise.
Best,
Hiatt
Click to expand...
Click to collapse
Hello Hiatt,
Thanks for using XDA Assist. What specific device do you currently have? There are so many devices here and each might deal with your question differently. I moved your other thread to off topic since it was referring to iPhones, but this one seems to have a more specific device in mind.
Thanks,
coal686
I presently have a Tmobile Galaxy S6 which is rooted and running Sick as Hell (version X).
From what I have read and heard it seems as though root and encryption together don't always play well together.
Also, it was the other post of mine that mentioned iPhones (the one about factory resets and eDiscovery).
cwhiatt said:
I presently have a Tmobile Galaxy S6 which is rooted and running Sick as Hell (version X).
From what I have read and heard it seems as though root and encryption together don't always play well together.
Also, it was the other post of mine that mentioned iPhones (the one about factory resets and eDiscovery).
Click to expand...
Click to collapse
Lol, that's what I said. The other post was more about the iPhone issue so I moved it to off-topic. Since you have a Galaxy S6, I'll move this thread there so people with that device can give you a more personalized answer.
I don't think that having root is an issue with encryption. I Had my S5 encrypted only problem was a ui crash when entering the boot password. That was specific to the rom I was using and simply had to enter password 1 or 2 characters at a time between errors.
But I do think there may be a problem with custom recovery and encryption.
My S5 was verizon, thus still locked bootloader and used safestrap to get to a custom recovery which wasn't always active.
I would talk to someone with a lot more knowledge then I about this further. But pretty sure just having root is not a problem the recovery is where you can have issues
cwhiatt said:
I did a couple of searches and came up empty but I am wondering if any ROM developers are working with encryption and root?
When I had my Galaxy S5 (Tmobile) it was first encrypted. I recall then once I rooted it I was no longer able to encrypt the device. I think there may have been some workarounds but they were pretty cumbersome to say they even worked at all.
I'm wondering if any developers are working that angle and if so should my inquiry be presented to developer of said ROM?
I also realize that encrypted devices do tend to read a bit slower than those no encrypted but I think I can live with that.
Please advise.
Best,
Hiatt
Click to expand...
Click to collapse
Hi there,
Root + Encryption can work together as long as no custom recovery involved, so if you get your root by exploit instead of installing custom recovery almost 99% chance you can have your phone encrypted while preserving the root privilege.
My case explained here : http://forum.xda-developers.com/galaxy-note-3/general/success-root-encryption-t3372958
I didn't have a problem with encryption and root. The only problem that I had was that my Galaxy S6 Edge needed to be encrypted before root. I could not encrypt my phone with the "stock" rooted kernel. Once I was encrypted, I could install TWRP and root via supersu systemless root.
Once I had root, I would use flashfire to back up and install because TWRP could not read the DATA partition since it was encrypted. For some reason, it seems once the phone has been decrypted, the data partition could be backed up with flashfire, and I would be able to restore a backup as well.
This is where I ran into issues. If you are flashing a custom rom that will require you to wipe data, your device will lose encryption. Because I can be somewhat of a crack flasher at times, and that I am too lazy to deal with having to re-encrypt and reinstall all my settings, I just opted to stick with an unencrypted phone.
Hopefully at some point, TWRP will be compatible with encryption so that lives will be easy for us crack flashers..until then, I will probably stick with an unencrypted device unless I just want to stick with a stock rom, or a custom rom that I can load up and not have to wipe data every time there is an update.
I am getting older, really older..
Everyday for a year or so, I did not download Lollipop when asked, because my phone was rooted. Someday, I planned to read up on how to update my rooted phone but never got around to it.
Today,I saw the update message and said WOW, a new version of Android, it sure took T-Mobile long enough. I thought, is my LG G4 rooted, and I thought NO, so there is no reason not to download and install this now. I downloaded and installed Lollipop (622MB).
Now my phone boots into TWRP (v2.8.0.1). I seem to have forgotten almost all of what I knew about rooting, updating and where to look for answers.
Hopefully, this phone can work again without my losing my CONTACTS.
So can somebody tell me what I need to do?
THANKS
I'm definitely getting older, I just realized/remembered that I have a G3 not a G4. Sorry.
So you made a backup of your data and now you are going to flash Lollipop from TWRP, right?
jobella said:
So you made a backup of your data and now you are going to flash Lollipop from TWRP, right?
Click to expand...
Click to collapse
Almost.
A couple of Command Line entries restored Kitkat.
http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
I backed up my G3 and then flashed Marshmallow from TWRP.
Everything good now.