Related
I've either made a hugely stupid error and turned on encryption and nobody will detail me why this is a bad idea.....
Or nobody who looks at my post in huge threads seems to want to answer this question:
I enabled encryption in my Galaxy Nexus settings. I am rooted on a custom ROM. I want to update/flash a new ROM.
Will things be different? Can I update like normal? or am I going to need to wipe/reset everything in order to flash an update?
XFreeRollerX said:
I've either made a hugely stupid error and turned on encryption and nobody will detail me why this is a bad idea.....
Or nobody who looks at my post in huge threads seems to want to answer this question:
I enabled encryption in my Galaxy Nexus settings. I am rooted on a custom ROM. I want to update/flash a new ROM.
Will things be different? Can I update like normal? or am I going to need to wipe/reset everything in order to flash an update?
Click to expand...
Click to collapse
Neither Clockwork Mod or even the stock recovery can access the storage on the device after it's encrypted. The fact that the stock recovery can't is exceptionally poor form on Google's behalf.
You can't even perform a factory reset. The only way to unencrypt the device is to flash it via fastboot.
I posted some details in this thread - http://forum.xda-developers.com/showthread.php?t=1392037
MrPendulum said:
Neither Clockwork Mod or even the stock recovery can access the storage on the device after it's encrypted. The fact that the stock recovery can't is exceptionally poor form on Google's behalf.
You can't even perform a factory reset. The only way to unencrypt the device is to flash it via fastboot.
I posted some details in this thread - http://forum.xda-developers.com/showthread.php?t=1392037
Click to expand...
Click to collapse
Thank you very much! Reading up on that was really a learning experience on this mess lol
Can I flash a ROM via Fastboot using a zip? Im not sure about that... any1 know?
XFreeRollerX said:
Thank you very much! Reading up on that was really a learning experience on this mess lol
Can I flash a ROM via Fastboot using a zip? Im not sure about that... any1 know?
Click to expand...
Click to collapse
Had the exact same problem and found out this solution the hard way. You can't do a factory reset to remove the encryption because the bootloader is different when you root.
The only way is to fastboot as mentioned above. You need to use the files provided for going back to stock. You should find them on here. Good luck.
I found this out the hard way as well, but I think this is the great benefit of encryption. If someone were to get a hold of your phone there would be no way for them to access anything without having or breaking the passcode. For serial rom flashers this kinda sucks but if you really care about your data and are willing to stick with either stock or stock rooted then this means you actually have a phone that's truly secure.
Sent from my Galaxy Nexus using Tapatalk
You'd have to be extremely paranoid about your data to want to encrypt your phone. I couldn't care less, nothing of importance is on my phone anyway
EddyOS said:
You'd have to be extremely paranoid about your data to want to encrypt your phone. I couldn't care less, nothing of importance is on my phone anyway
Click to expand...
Click to collapse
I run my business on Google Apps and my data would be sensitive. Not everyone uses there phones just for personal stuff.
I don't use it for that either! I delete SMSs after they've been read, email is downloaded to my PC once Outlook is opened and bar Facebook/Twitter and a small selection of other apps there's nothing personal on my phone
Funnily enough I use it as a phone more than anything
EddyOS said:
I don't use it for that either! I delete SMSs after they've been read, email is downloaded to my PC once Outlook is opened and bar Facebook/Twitter and a small selection of other apps there's nothing personal on my phone
Funnily enough I use it as a phone more than anything
Click to expand...
Click to collapse
Wow, I couldn't operate that way, I use my phone for everything, even my laptop and tablet are a bit useless now Each to their own I suppose
Im having some trouble going back to stock image to factory reset the phone
I flashed stock bootloader, stock radio images and booted into the OS and did factory reset, doesn't seem to work...help? I can't get this encryption off
XFreeRollerX said:
Im having some trouble going back to stock image to factory reset the phone
I flashed stock bootloader, stock radio images and booted into the OS and did factory reset, doesn't seem to work...help? I can't get this encryption off
Click to expand...
Click to collapse
Factory reset won't work. You need to completely wipe the phone by loading the stock img from Google that came on the phone. It is the only way it will work. You can find out how to do that on here, sorry I don't have the link on hand though so just search a bit. Feel free to PM as I had the exact same issue.
EDIT - try this toolkit to go back to the stock rom. You loose everything but it should remove encryption.
http://forum.xda-developers.com/showthread.php?t=1392310
I don't know why Google don't give the option to decrypt from the Google Apps dashboard. So annoying! Good luck, hope you get sorted.
Thanks for posting that - in the end the g-nex toolkit ended up bringing the phone back to stock and rooted the device again and I've now successfully factory reset the device and am back to running a custom ROM with root and no encryption
Thanks for the help
XFreeRollerX said:
Thanks for posting that - in the end the g-nex toolkit ended up bringing the phone back to stock and rooted the device again and I've now successfully factory reset the device and am back to running a custom ROM with root and no encryption
Thanks for the help
Click to expand...
Click to collapse
Yaaaaey glad you got sorted. Encryption from GApps at the moment is woeful. I am sure they are working on it.
jd1001 said:
Yaaaaey glad you got sorted. Encryption from GApps at the moment is woeful. I am sure they are working on it.
Click to expand...
Click to collapse
Hopefully they are as if you want a real secure device, its pretty pitiful to bypass if in the wrong hands.
Does this only apply if you've rooted your device and flashed a different ROM? If you have an unrooted phone and turn on encryption, will you have the same issues (i.e. unable to do a factory reset)? Is this only a problem with the Nexus or would any Android phone have this problem?
I ask because the company I work for is talking about forcing users to encrypt their phones if they want ActiveSync enabled. But they also want to be able to run a wipe on the phone if necessary. It would seem to me that encrypting the phone may prevent that as an option.
HuskerWebhead said:
Does this only apply if you've rooted your device and flashed a different ROM? If you have an unrooted phone and turn on encryption, will you have the same issues (i.e. unable to do a factory reset)? Is this only a problem with the Nexus or would any Android phone have this problem?
I ask because the company I work for is talking about forcing users to encrypt their phones if they want ActiveSync enabled. But they also want to be able to run a wipe on the phone if necessary. It would seem to me that encrypting the phone may prevent that as an option.
Click to expand...
Click to collapse
Touchdown.
It's a little pricy at $20 but well worth it in IMHO.
A remote wipe will only kill off touchdown and optionally SDcard storage.
Matridom said:
Touchdown.
It's a little pricy at $20 but well worth it in IMHO.
A remote wipe will only kill off touchdown and optionally SDcard storage.
Click to expand...
Click to collapse
Yeah, they are already looking at using Touchdown for devices that don't support encryption natively, but those that do (support encryption natively) they just want to enable the devices' own encryption.
So I'm still not sure if with encryption turned on, will it prevent a phone from being remotely wiped?
XFreeRollerX said:
Hopefully they are as if you want a real secure device, its pretty pitiful to bypass if in the wrong hands.
Click to expand...
Click to collapse
When you bypass it by flashing a new system over it you wipe all data that was ever on the phone. Ok your phone could be stolen, but no-one will ever know what CP you were hiding with that encryption. I'm very happy with the fact that there is a save backdoor... imagine forgetting your password for some reason or filling out the wrong password on setup... when that happend this thread would have been a "bricked my phone by forgetting the password. Who wants some nice spareparts for his phone" Q&A
Sent from my Galaxy Nexus using XDA
HuskerWebhead said:
Yeah, they are already looking at using Touchdown for devices that don't support encryption natively, but those that do (support encryption natively) they just want to enable the devices' own encryption.
So I'm still not sure if with encryption turned on, will it prevent a phone from being remotely wiped?
Click to expand...
Click to collapse
Just don't tell them you are using touchdown. I've tested the remote wipe in Android, it can kill the whole phone. The only way to keep your personal info safe is to use touchdown
Sent from my Galaxy Nexus
Matridom said:
Just don't tell them you are using touchdown. I've tested the remote wipe in Android, it can kill the whole phone. The only way to keep your personal info safe is to use touchdown
Click to expand...
Click to collapse
I think you're misunderstanding my intentions. I'm not looking for a way to bypass the encryption requirement they may be introducing. I'm just trying to understand if it will cause a problem for the remote wipe functionality if the phone is lost or stolen. If it will, I'll have to let them know so they can decide what is more important: encryption or remote wipe capabilities.
If a remote wipe functions regardless of encryption being enabled, then it's a moot point.
Hi all,
I'm currently not encrypted and prefer to keep it that way, I don't like entering passwords everytime I go to TWRP and I prefer the old school android system where encryption was a choice, not a mandatory decision made for you.
So when I install a ROM I run a few commands prior to installation to avoid forced encryption, unless it has an option within aroma to disable force encryption which most don't
Thanks to @j to the 4n for help with this, legend
Anyway if you'd like to install a ROM like lineage or aosp or resurrection remix etc and remain not encrypted? Keep reading.
*Note: if you're encrypted prior to doing this then stop, this is for people who've chosen to disable force encryption already but would like to retain it after installing aosp / lineage ROMs.
However if you'd like to remove encryption you'll need to format data via TWRP, not a wipe! Format.
Make sure you back up prior to doing this as it will format data, best to have the ROM on your SD card too so you don't end up with no OS.
If you've done the above or you already have a ROM installed without encryption, then you should be good to go.
------------------------------------------------------------------------------------------------
Just before youre about to install a ROM, let's say resurrection remix ( tested )
Make sure your phone is in TWRP and you're connected to your PC then just before you're about to click install, open up a command prompt on your PC then from ADB shell send the following commands to the device from your PC..
For Magisk:
echo "KEEPFORCEENCRYPT=false" >> /cache/.magisk
If the rom uses SuperSU, send the following commands.
echo "KEEPFORCEENCRYPT=false" >> /data/.supersu
echo "KEEPFORCEENCRYPT=false" >> /cache/.supersu
Then install your rom as normal.
Obviously for ROMs like viper your don't need to do this as there is an option within aroma, but for the likes of RR or lineage this will mean your phone will not encrypt on boot.
Should work for all ROMs but I've not tested this on all of them so if it goes wrong then it's not on me, this worked perfectly for me on RR coming from viper whilst not encrypted.
*Note: if you're not sure what root method your ROM uses then simply send all three commands and you should be good to go.
By using these you're not going to find yourself in TWRP being asked for a password you don't have as your device has been encrypted, I've lost data myself this way and it's extremely annoying.
:good:
If I can ask if anyone tries this and it works, would you mind replying with what it worked on so I can update the OP.
Cheers.
PS: if you're not sure what this is or have any questions, please ask away
Anyway to do this from the device for when your not near a PC?
JohnFawkes said:
Anyway to do this from the device for when your not near a PC?
Click to expand...
Click to collapse
Yes i believe it is, would need to write up a script which is ran prior to installing the rom, i've not got around to doing it yet.
Strictly speaking this should be an option with all roms, it's not exactly a lot of work is it?
Deleted
Works pretty well on Stock ROM.
Just RUU'd, and before rebooting went into download mode, flashed Recovery, flashed SuperSU, used this Command. and boom.
Multirom works.
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Dlind said:
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Click to expand...
Click to collapse
Yea it's used on the OnePlus 5 too. I wrote this prior to knowing of its existence and because the likes of lineage and other ROMs just assume you know, no warning.
Losing data is not fun.
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
dladz said:
Yea it's used on the OnePlus 5 too. I wrote this prior to knowing of its existence and because the likes of lineage and other ROMs just assume you know, no warning.
Losing data is not fun.
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah it pisses me off. But at least with this handy zip you can flash it anyway and have some mental relief that you stay decrypted.
Dlind said:
I used to have a one plus 3 and for some time before everyone used forced decryption the good ol friends from kali net hunter made a forced decryption zip, I will put a link down below, but listen when I say this, every time you flash a new boot .Img, or rom on the htc 10 you need to flash this if you want to stay decrypted. Its ok if you flash multiple times.
The file you want is, "no verity force encrypt".
I've used it on almost every aosp and stock based rom I've flashed also used on many custom kernels to, it still stayed decrypted.
https://build.nethunter.com/android-tools/
Click to expand...
Click to collapse
i've flashed the v 5.1 got greeted by a "Encrypting" Wait while your phone is being encrypted. Time remaining 01:50 Screen.
Guess that does not work on PureFusion OS ROM / HTC 10
Edit: Okay... this does NOT work when swapping Internal with Secondaries ROM in Multirom, but for a new install it does...
Haldi4803 said:
i've flashed the v 5.1 got greeted by a "Encrypting" Wait while your phone is being encrypted. Time remaining 01:50 Screen.
Guess that does not work on PureFusion OS ROM / HTC 10
Edit: Okay... this does NOT work when swapping Internal with Secondaries ROM in Multirom, but for a new install it does...
Click to expand...
Click to collapse
Sorry I hadn't tested with all ROMs, not even sure Pure Fusion was even available when I had my HTC 10.
Stick to the script, it's quick, easy and works, you can try a zip but unless someone has gone before you you're potentially walking into a bad time.
Jep.... the zip doesn't seem to work no matter what. Not even on Stock ROM. Prolly not compatible with HTC10.
These 2 Command lines though do work perfectly fine on PureFusion OS... simply install ROM, install SU, enter 2 lines. Done.
Haldi4803 said:
Jep.... the zip doesn't seem to work no matter what. Not even on Stock ROM. Prolly not compatible with HTC10.
These 2 Command lines though do work perfectly fine on PureFusion OS... simply install ROM, install SU, enter 2 lines. Done.
Click to expand...
Click to collapse
That's absolutely fine. Because this thread isn't about the zip..I have nothing to do with that, so in regards to the zip you flash it at your own risk.
Deleted
Though i do agree with him that having a .zip and not needing a Computer every time would be pretty usefull.
Does anyone know how to create TWRP flashable zips that includes only this 2 commands?
Hello I tied this for RR rom but I got this message in the cmd, am i doing something wrong?
edit i found my fault I had to adb shell
I know it's been about a year, since somebody posted, but: if anbyone else like me stumbles across this thread, have a look at: https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
It gives you even more information how to enable or disable encryption or dm-verity while usinf magisk.
Btw. you can use the terminal in twrp also, see link.
Can I use the built-in twrp terminal for echo-ing rather than using adb shell ?
Subh4sh said:
Can I use the built-in twrp terminal for echo-ing rather than using adb shell ?
Click to expand...
Click to collapse
Ofcourse,cause echo command is available everywhere.just make sure you install the magisk/supersu first before running the command
hi,
If I format /data, then the encryption is gone and LOS can be installed where backup with TWRP work?
I have U11, but i think it is the same...
Okay so after getting tired of safetynet and other issues Google has put on us I'm wanting to switch to magiskSU but Everytime I tried I bootloop and have to clean flash my rom. This is what I'm doing
1. Flashed unSU in twrp
2.flashed stock boot.img
3. Flashed the magisk.zip
4.got an error saying it failed to install magisk.zip
But whenever I try to reboot to system (I've tried reinstalling SuperSU and without reinstalling as well) I got a bootloop Everytime can someone instruct me or tell me what I'm doing wrong?
WeUseLord- said:
Okay so after getting tired of safetynet and other issues Google has put on us I'm wanting to switch to magiskSU but Everytime I tried I bootloop and have to clean flash my rom. This is what I'm doing
1. Flashed unSU in twrp
2.flashed stock boot.img
3. Flashed the magisk.zip
4.got an error saying it failed to install magisk.zip
But whenever I try to reboot to system (I've tried reinstalling SuperSU and without reinstalling as well) I got a bootloop Everytime can someone instruct me or tell me what I'm doing wrong?
Click to expand...
Click to collapse
What carrier/rom/update/etc?
WeUseLord- said:
Okay so after getting tired of safetynet and other issues Google has put on us I'm wanting to switch to magiskSU but Everytime I tried I bootloop and have to clean flash my rom. This is what I'm doing
1. Flashed unSU in twrp
2.flashed stock boot.img
3. Flashed the magisk.zip
4.got an error saying it failed to install magisk.zip
But whenever I try to reboot to system (I've tried reinstalling SuperSU and without reinstalling as well) I got a bootloop Everytime can someone instruct me or tell me what I'm doing wrong?
Click to expand...
Click to collapse
In Short. Currently for our device to have magisk, you need to use the boot image that @joemossjr and @Uzephi developed with Magisk support. Then install the magisk app. No zip install.
Refer to Joe's thread for the boot image at this link
https://forum.xda-developers.com/z2-force/how-to/how-to-root-moto-z2-force-t-mobile-t3672933
I would have went into detail and used a short link, but my head is currently throbbing so this is easier lol.
Edit: then realized your replied a minute before I Uzephi haha.
Uzephi said:
What carrier/rom/update/etc?
Click to expand...
Click to collapse
Spring stock rom on the original August update
Sent from my Moto Z (2) Force using XDA Labs
Acoustichayes said:
In Short. Currently for our device to have magisk, you need to use the boot image that @joemossjr and @Uzephi developed with Magisk support. Then install the magisk app. No zip install.
Refer to Joe's thread for the boot image at this link
https://forum.xda-developers.com/z2-force/how-to/how-to-root-moto-z2-force-t-mobile-t3672933
I would have went into detail and used a short link, but my head is currently throbbing so this is easier lol.
Click to expand...
Click to collapse
I know but when I tried that method and just installing the boot.img through twrp it failed and gave me a boot loop as well
Sent from my Moto Z (2) Force using XDA Labs
WeUseLord- said:
Spring stock rom on the original August update
Click to expand...
Click to collapse
I would suggest updating to November. I have a rooted magisk image, but you need to flash the decryption zip to get it to boot. If you update to November, I am going to release a flash-all type zip sometime today (after I fiddle with getting 4.4.107 upstream done) and working on a Google Pixel 2 skinned ROM for us here shortly with oem bloat completely removed
WeUseLord- said:
I know but when I tried that method and just installing the boot.img through twrp it failed and gave me a boot loop as well
Sent from my Moto Z (2) Force using XDA Labs
Click to expand...
Click to collapse
Have to ask this general base question of course lol. are you trying to dirty flash or did you do a full clean install?
But in general, what Uzephi said, as this is his project. I'll let him go ahead and take over. Goodluck
WeUseLord- said:
I know but when I tried that method and just installing the boot.img through twrp it failed and gave me a boot loop as well
Click to expand...
Click to collapse
You using stock kernel? To get crypto changes in 4.4.101-103 added, it breaks encryption on our phones and will cause a boot loop due to Motorola's dirty code. Hopefully when Oreo ROM drops (since Google is kinda telling oems to stay upstreamed) it will fix those issues in our stock ROMs.
Uzephi said:
I would suggest updating to November. I have a rooted magisk image, but you need to flash the decryption zip to get it to boot. If you update to November, I am going to release a flash-all type zip sometime today (after I fiddle with getting 4.4.107 upstream done) and working on a Google Pixel 2 skinned ROM for us here shortly with oem bloat completely removed
Click to expand...
Click to collapse
That's nice I think I'm gonna stick with SuperSU for now this phone is confusing
But one thing I must ask will we have a customisable rom like CM or something like that soon?
Sent from my Moto Z (2) Force using XDA Labs
WeUseLord- said:
That's nice I think I'm gonna stick with SuperSU for now this phone is confusing
But one thing I must ask will we have a customisable rom like CM or something like that soon?
Click to expand...
Click to collapse
Hard to say. Those of us that have tried hard bricked the device. Not readable via USB and wouldn't boot anything after the flash.
WeUseLord- said:
That's nice I think I'm gonna stick with SuperSU for now this phone is confusing
But one thing I must ask will we have a customisable rom like CM or something like that soon?
Sent from my Moto Z (2) Force using XDA Labs
Click to expand...
Click to collapse
To build off what Uzephi said. It's not that rom's wont be capable. It's just working with new things that are being implemented and changed until something starts going right. The jump to Nougat changed a lot of things with security and the switch to Oreo is changing even more that Google is wanting to push for android that inadvertently also affect security and compatibility.
This is speculation, but since they introduced Kotlin, I feel like they are trying to alter everything over the long run to become more streamline and compatible around it. Especially given they can control the progress of the script language to help them better. Which will really show true or false come mid next year.
We are lucky that Motorola sticks to a super close to stock experience because it's one less issue to deal with when playing with the new code and functions to try to get things to work. I'm really optimistic on this stuff because I like doing things that people think can't be done. So I believe that there will for sure be more customization and capabilities as we figure things out. Just takes time and effort. We worked for months and months on the S8 where people said impossible, and ended up getting it. So i have faith on this.
Acoustichayes said:
To build off what Uzephi said. It's not that rom's wont be capable. It's just working with new things that are being implemented and changed until something starts going right. The jump to Nougat changed a lot of things with security and the switch to Oreo is changing even more that Google is wanting to push for android that inadvertently also affect security and compatibility.
This is speculation, but since they introduced Kotlin, I feel like they are trying to alter everything over the long run to become more streamline and compatible around it. Especially given they can control the progress of the script language to help them better. Which will really show true or false come mid next year.
We are lucky that Motorola sticks to a super close to stock experience because it's one less issue to deal with when playing with the new code and functions to try to get things to work. I'm really optimistic on this stuff because I like doing things that people think can't be done. So I believe that there will for sure be more customization and capabilities as we figure things out. Just takes time and effort. We worked for months and months on the S8 where people said impossible, and ended up getting it. So i have faith on this.
Click to expand...
Click to collapse
Motorola already admitted the Z series will not be a part of Project treble meaning we need to try different vendor files to see if builds work. Sadly the ones used for the Z1 and wahoo mixed together cause the phone to go haywire and brick itself.
Uzephi said:
Motorola already admitted the Z series will not be a part of Project treble meaning we need to try different vendor files to see if builds work. Sadly the ones used for the Z1 and wahoo mixed together cause the phone to go haywire and brick itself.
Click to expand...
Click to collapse
And I understand that this means lack of simplicity in developing custom rom's. But it doesn't mean incapability. From what I understand as well, that treble can be implemented at a later date even though it will not be included with the initial Oreo update. You are working on a pixel rom conversion if I am correct right? Because I might have an idea...
But treble is still def exciting to think about being able to have one rom work on many different phones without modification. I honestly haven't divulged too far into it, but what are the odds of tearing apart the code and possible making support for it ourselves? I'm all for ridiculously long spans of working towards absurd goals hah
Acoustichayes said:
And I understand that this means lack of simplicity in developing custom rom's. But it doesn't mean incapability. From what I understand as well, that treble can be implemented at a later date even though it will not be included with the initial Oreo update. You are working on a pixel rom conversion if I am correct right? Because I might have an idea...
But treble is still def exciting to think about being able to have one rom work on many different phones without modification. I honestly haven't divulged too far into it, but what are the odds of tearing apart the code and possible making support for it ourselves? I'm all for ridiculously long spans of working towards absurd goals hah
Click to expand...
Click to collapse
Unless Motorola can repartition the phone, Treble won't come out, it needs a vendor partition. I can say at least on my Sprint phone the OEM block is about 1.5 GB when there is only about 200 MB of data on it, so they can splice that to save user data. Only other way is to repartition /system or /userdata for the space needed for the new partition.
Yes, I am doing a pixel conversion ROM. Tried just booting the pixel /system and it didn't work. I am taking assets from the Tamien and putting them into our November update using SuperR.
Uzephi said:
Unless Motorola can repartition the phone, Treble won't come out, it needs a vendor partition. I can say at least on my Sprint phone the OEM block is about 1.5 GB when there is only about 200 MB of data on it, so they can splice that to save user data. Only other way is to repartition /system or /userdata for the space needed for the new partition.
Yes, I am doing a pixel conversion ROM. Tried just booting the pixel /system and it didn't work. I am taking assets from the Tamien and putting them into our November update using SuperR.
Click to expand...
Click to collapse
I know there are few devs out there working on making it work on non treble phones. Repartitioning and adding a vendor partiion wouldn't be the issue with making it work. Rather trying to get the vendor source for drivers to add to it, and if they need to be reworked to add support. I've been off for a few months with health issues so I'm still getting back into things with oreo, but that seems to be the biggest issue at the moment that I could find.
When my health is back to 100 percent within a couple weeks I will dive into work with you and aid in any way possible for this. To me, trying to get driver source and make it work sounds fun. but we are far off topic now for this post so I'll leave this here haha.
New to the Moto Z2 play, moved to this from a Z2 force on Verizon after the shattershield started peeling. Anyway, there seems to be a lot of conflicting information here, and i'm struggling to actually nail down the process for root. My bootloader is already unlocked, however between several different versions of TWRP, Retus based phones vs Albus, ability to unroot and update if the system is modified, rooting with or without disabling encryption, countless different variants with different procedures, etc. i'm a little overwhelmed. Can anyone point me in the right direction of rooting my device (hopefully) WITHOUT losing all my data?
StATicxTW0T said:
New to the Moto Z2 play, moved to this from a Z2 force on Verizon after the shattershield started peeling. Anyway, there seems to be a lot of conflicting information here, and i'm struggling to actually nail down the process for root. My bootloader is already unlocked, however between several different versions of TWRP, Retus based phones vs Albus, ability to unroot and update if the system is modified, rooting with or without disabling encryption, countless different variants with different procedures, etc. i'm a little overwhelmed. Can anyone point me in the right direction of rooting my device (hopefully) WITHOUT losing all my data?
Click to expand...
Click to collapse
I'm about to buy the unlocked Moto Z2 Play from the Moto site (64GB variant... not sure of the model number) but have you checked out these threads?...
https://forum.xda-developers.com/showpost.php?p=75098899&postcount=40
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615/page3
allstar21369 said:
I'm about to buy the unlocked Moto Z2 Play from the Moto site (64GB variant... not sure of the model number) but have you checked out these threads?...
https://forum.xda-developers.com/showpost.php?p=75098899&postcount=40
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615/page3
Click to expand...
Click to collapse
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
I have a rooted XT1710-01, also. If you are going to install Xposed and Gravity Box, I recommend not updating Magisk, above v14. After v15 and now v16, I have had issues with Automate It app and Tasker rules not working, until I uninstalled Xposed.
Downgrading Magisk versions requires flashing your stock ROM and basically starting over.
Motorola has not posted firmware for this model.
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
So glad to see someone have it working and with a clear guide. I'm going to buy the phone this week.
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
I just wanted to let everyone know that the guide posted in that post worked for me perfectly. I had an XT1710-01 that I had unlocked the bootloader before but stopped there. Then I finally wanted to root it, and ran into everything the OP ran into - just so many different guides and versions of TWRP/Magisk not working with the Z2 Play, it was hard to nail down the exact versions of everything I needed and make sure I didn't flash an incompatible version or something. I found that same guide a few days ago as well but never did it until today, and can confirm it works. I already had my bootloader unlocked and just did the rooting portion and all my data was saved (but I wasn't too worried about my data honestly, it's all backed up anyway).
And a special thanks to OP for coming back and posting his solution. Nothing is more frustrating than searching for a problem online, finding a hit on your exact problem in a thread that was posted years ago, and then no solution is ever posted in that thread. So good job. :good:
Johmama said:
I just wanted to let everyone know that the guide posted in that post worked for me perfectly. I had an XT1710-01 that I had unlocked the bootloader before but stopped there. Then I finally wanted to root it, and ran into everything the OP ran into - just so many different guides and versions of TWRP/Magisk not working with the Z2 Play, it was hard to nail down the exact versions of everything I needed and make sure I didn't flash an incompatible version or something. I found that same guide a few days ago as well but never did it until today, and can confirm it works. I already had my bootloader unlocked and just did the rooting portion and all my data was saved (but I wasn't too worried about my data honestly, it's all backed up anyway).
And a special thanks to OP for coming back and posting his solution. Nothing is more frustrating than searching for a problem online, finding a hit on your exact problem in a thread that was posted years ago, and then no solution is ever posted in that thread. So good job. :good:
Click to expand...
Click to collapse
I just received my Z2 Play, unlocked the bootloader, and am about to flash the custom TWRP (albus_twrp.img) posted in the guide linked above... but the guide never says to "flash" TWRP, it just says to "boot" with TWRP and also "Enter your FBE password: it must work! (turn off screen and turn it back on if not responsive)"...
I'm not 100% sure what to do here. Should I boot TWRP first, do a full backup and then flash TWRP? I don't want to wipe it.
And what is this FBE (File-Based Encryption) password? I've never set one and don't want everything encrypted.
allstar21369 said:
I just received my Z2 Play, unlocked the bootloader, and am about to flash the custom TWRP (albus_twrp.img) posted in the guide linked above... but the guide never says to "flash" TWRP, it just says to "boot" with TWRP and also "Enter your FBE password: it must work! (turn off screen and turn it back on if not responsive)"...
I'm not 100% sure what to do here. Should I boot TWRP first, do a full backup and then flash TWRP? I don't want to wipe it.
And what is this FBE (File-Based Encryption) password? I've never set one and don't want everything encrypted.
Click to expand...
Click to collapse
I didn't flash TWRP on my phone. I think I tried it once and it failed for some reason, so I just followed the guide of booting into TWRP, backing up my phone, and pulling the backup. Should be okay for what I need, in case of a failure I will have a backup somewhere and can recover the device. But yes, I'd at least boot into TWRP, then backup your device like in that guide so you have a backup. Flashing it is up to you, I've always flashed a custom recovery but on this phone I'm keeping the original recovery so I can get an OTA. On my Nexus devices I don't care about OTA because I just flash ROMs all the time so it's no big deal.
The FBE password as far as I can tell is the 4 or 5 digit PIN number you are asked to input upon a fresh wipe of your device to set as a password. I have my phone set up to use my fingerprint to unlock the phone, and if that fails it will ask for my PIN, which is the same as the FBE of mine. I used that same number in TWRP when it asks for a password to unencrypt the data and it worked. As far as turning off encryption, I'm not sure if there's a way to do that. There could be, but to turn it off, it wipes your data as a security measure.
Johmama said:
so I just followed the guide of booting into TWRP, backing up my phone, and pulling the backup. Should be okay for what I need, in case of a failure I will have a backup somewhere and can recover the device. But yes, I'd at least boot into TWRP, then backup your device like in that guide so you have a backup.
Click to expand...
Click to collapse
Yeah, I can't backup my ROM most likely because I don't have an FBE password. When I go to backup my ROM in TWRP it fails.
Johmama said:
The FBE password as far as I can tell is the 4 or 5 digit PIN number you are asked to input upon a fresh wipe of your device to set as a password. I have my phone set up to use my fingerprint to unlock the phone, and if that fails it will ask for my PIN, which is the same as the FBE of mine. I used that same number in TWRP when it asks for a password to unencrypt the data and it worked.
Click to expand...
Click to collapse
I tried entering my unlock code and the pin I created but neither worked for my FBE password. I don't ever remember being asked to enter a password when setting up my device. I suppose this means I'll have to wipe data and then setup an FBE password.
allstar21369 said:
I tried entering my unlock code and the pin I created but neither worked for my FBE password. I don't ever remember being asked to enter a password when setting up my device. I suppose this means I'll have to wipe data and then setup an FBE password.
Click to expand...
Click to collapse
If it helps at all, the first time I tried it also didn't work for me and I did end up wiping my phone for other reasons before I came back and tried that guide again and it worked. I thought I set up the PIN they're talking about the first time around but I did have troubles in TWRP before the first wipe of my data. I would just boot up the phone regularly, plug it in to your computer, and try to grab any files you need and wipe it. I know that isn't the answer you're looking for, but it's all I can give I guess. Once you reset, hopefully they'll prompt you to make a PIN during the setup process and that should be the FBE password. Then follow the guide. I hope you get it man.
Oh, and to a note to you and everyone reading this, I booted to TWRP 3.2.1-0-albus and Magisk-v14.0. Dunno if it's just rumors or not but I heard the newer versions of Magisk might not work with the Z2 Play past version 14. Dunno if that's true but v14.0 worked for me.
Johmama said:
If it helps at all, the first time I tried it also didn't work for me and I did end up wiping my phone for other reasons before I came back and tried that guide again and it worked. I thought I set up the PIN they're talking about the first time around but I did have troubles in TWRP before the first wipe of my data. I would just boot up the phone regularly, plug it in to your computer, and try to grab any files you need and wipe it. I know that isn't the answer you're looking for, but it's all I can give I guess. Once you reset, hopefully they'll prompt you to make a PIN during the setup process and that should be the FBE password. Then follow the guide. I hope you get it man.
Oh, and to a note to you and everyone reading this, I booted to TWRP 3.2.1-0-albus and Magisk-v14.0. Dunno if it's just rumors or not but I heard the newer versions of Magisk might not work with the Z2 Play past version 14. Dunno if that's true but v14.0 worked for me.
Click to expand...
Click to collapse
Okay. I just wiped and re-set up everything and still no FBE password was asked for OR works when I go into TWRP. I'm using TWRP 3.1.1-0... I suppose I'll try it all again using TWRP 3.2.1-0-albus after deleting data.
*Edit: I did exactly what I just said I was doing booted TWRP 3.2.1-0-albus instead of 3.1.1-0 and when I it booted up and asked me for a decryption password I entered the pin I set up previously and it has been stuck at the "Mount, Trying Decryption" screen for a long time... but it's not frozen. It says "Updating partition details... ...done
Unable to mount storage
Full SELinux support is present.
Data successfully decrypted, new block device: '/dev
/block/dm-0'
Updating partition details...
...done"
And the progress bar/thing at the bottom is still animated like it's working... no forward or back buttons or anything and turning off/on the screen hasn't done anything... not really sure what to do here... I don't want to unplug it and brick my phone or force it off...
*Edit 2:
I now have it all sorted out.
TWRP never finished trying to decrypt data so I long pressed the power button and eventually went here -> https://forum.xda-developers.com/z2-play/development/twrp-moto-z2-play-t3729531 , downloaded "twrp_albus_3.1.2_r18_64.img" and in adb used the command:
fastboot boot twrp_albus_3.1.2_r18_64.img
This TWRP looks a bit different than all of the others but it let me boot up and use my recently created PIN code to actually decrypt my data and make a full backup. After that I just installed Magisk (the latest one, 16.4) as indicated in this guide -> https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792 and everything is fine. I never even flashed TWRP, just booted it.
Just curious what you guys have done about getting OTA updates since you've rooted and installed Magisk.
Have @allstar21369 or @pizza_pablo had the chance to figure out the update process?
I'm currently trying to navigate the Magisk uninstall --> OTA update process and could use some insight if either of you guys have any to share.
joefuf said:
Just curious what you guys have done about getting OTA updates since you've rooted and installed Magisk.
Have @allstar21369 or @pizza_pablo had the chance to figure out the update process?
I'm currently trying to navigate the Magisk uninstall --> OTA update process and could use some insight if either of you guys have any to share.
Click to expand...
Click to collapse
I didn't want updates, especially the oreo "upgrade".
pizza_pablo said:
I didn't want updates, especially the oreo "upgrade".
Click to expand...
Click to collapse
Hmm, didn't even think about just sticking on what works... Did Oreo give people some issues?
Since this was Day 1 with the new phone, I was just trying to get up to speed and probably sit on one version until I had compatibility issues with something, but everything just works.
joefuf said:
Hmm, didn't even think about just sticking on what works... Did Oreo give people some issues?
Since this was Day 1 with the new phone, I was just trying to get up to speed and probably sit on one version until I had compatibility issues with something, but everything just works.
Click to expand...
Click to collapse
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Double - double \_0_/
pizza_pablo said:
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Click to expand...
Click to collapse
I feel exactly the same way. No benefits for me. I don't want the bright white interface and I would never use the "Picture in Picture" (or floating video) feature (and if I did want that there are a couple apps for Nougat that do it).
But If I do decide I want it and give upgrading a shot I'll definitely post it here.
pizza_pablo said:
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Click to expand...
Click to collapse
Yeah, very understandable. It really is superfluous to the general experience.
allstar21369 said:
I feel exactly the same way. No benefits for me. I don't want the bright white interface and I would never use the "Picture in Picture" (or floating video) feature (and if I did want that there are a couple apps for Nougat that do it).
But If I do decide I want it and give upgrading a shot I'll definitely post it here.
Click to expand...
Click to collapse
Thank you sir! Keep me posted. I'm posting everywhere right now to learn the new methods so I know if there ever comes a time. This is my first phone since my Motorola Droid 4. Back then it was one click root, install and run Safestrap apk to get custom recovery, boot into custom recovery and flash zips to your heart's content. I'm sure this will be as "simple" once I learn, but it's pretty daunting in prospect.
I am grateful and I bought this because next tk Samsung s22 yktra this phone is definitely #2 in my opinion, which is saying a lot.
However the root process is tedious because I am not around a computer I am just lazy to get ito do flashing etc.
My question is, why do. We not have a a real recovery and ability to back up and restore various roms we or flash zips senselessly.
So my question is (since I just bought this) do you guys rhibj we will have to dastboir flash everything or at least much harder then with cwmod or twrp recovery. Is it not possible to have a recovery like those on t his phone?
Is there a better phone in the us that is unlockaable but has the quality like this phone and screen or the Samsung s22 yktra phone?
Thanks
Without a PC you can't run fastboot commands to unlock bootloader and root it. Twrp isn't available for stock a12, let alone the upcoming release of a13
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
I don't think that you will find too many phones from the primary companies (Google, Samsung, etc) nowadays that will have TWRP builds. As time progresses, the technology (and what is available) progresses as well.
jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
This is the most recent news about Android 12 compatibility for TWRP:
TWRP 3.6.2 Released
TWRP 3.6.2 is out now for most currently supported devices.
twrp.me
We are continuing work on Android 12. There is no ETA currently. You can follow our status on Zulip
Click to expand...
Click to collapse
Disclaimer: I am not advocating signing up for "Zulip", and I won't be doing so myself. When/if TWRP for Android 12 becomes available, I'll hear about it whether I sign up on there or not. It's also likely Android 13 will be stable by then.
Supposedly, the Official TWRP App (not itself updated since 2020) will notify when there's a new version - but I don't know if that applies to when there's no current version of TWRP Recovery already installed.
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
96carboard said:
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
Click to expand...
Click to collapse
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have
Pixel devices do not have a recovery partition; recovery lives in /boot with the kernel, as well as whatever patches you've applied. Currently, TWRP and Magisk cannot coincide for whatever reason. You can patch a boot image with TWRP, and it'll work AFAIK....but if you try to patch it with Magisk too, you'll get a boot loop.
Because we have full fastboot access, there's not really any need for TWRP. You can dump and backup partition contents using fastboot, but it's tedious.
jgrimberg1979 said:
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have.
Click to expand...
Click to collapse
ADP, Nexus, and Pixel devices have NEVER needed a recovery to function fully. This goes right back to the first Android phone in 2008. So nothing really has changed in this respect. Its mostly the "other" brands that need a recovery to work around various restrictions.
Backups can be taken from within the main OS, and restored similarly, and this is actually much preferred since the backup can be stored to a remote location such as a self-hosted Nextcloud server. You can look into seedvault (integrated solution) and neobackup (root solution).
Since Android 11 you cannot have TWRP and Magisk installed at the same time or it will lead to a bootloop. However, you can fastboot boot TWRP (without installing it) and have Magisk installed without getting into a bootloop. At least this is the way it was on Android 11 with the Pixel 2 XL.
Haven't used TWRP in a long time and don't miss it at all, to be honest.