Related
I am not very good at making good step by step instructions but Lots of others are.
Here are the steps that I used.
Unlock bootloader via normal means
Flash chainfire boot img from here
Flash Twrp
Boot into Twrp and click mount and mount /system/
ADB Push supersu Zip file to /system/
Twrp install SuperSu.zip
Reboot
Profit
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Hi
Evo_Shift said:
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Click to expand...
Click to collapse
Wish I tried that first, turned off encryption now, although could re-encrypt.
Yes this should work. TWRP doesn't support decryption, which means any files copied to the phones user storage that we might want to install by TWRP (such as SuperSU), can't be seen by TWRP, as it can't decrypt the user data, so it can't be installed from recovery.
However, the system partition isn't encrypted, so pushing a file to the system, will allow TWRP to read it and install SuperSU. Of course you can't do things like full back ups as there probably isn't enough space on the system file system, so you need the user storage area for that, so you would need that decrypted for larger files so that TWRP can gain access.
Regards
Phil
Don't forget adb sideload for installing zips without using internal storage
Use Oem Unlock?
fastboot oem unlock
Yes
How does this affect using Android Pay?
Rado_vr6 said:
How does this affect using Android Pay?
Click to expand...
Click to collapse
Same as other rooted/unlocked devices it doesn't work.
So you can root while keeping encryption enabled? I need encryption for work, but root is a MUST have. Would like to verify before I order. Thanks.
I was under the impression that flashing the chainfire boot img disables encryption?
Did you fastboot into TWRP (no flashing/installing needed) Code = fastboot boot twrp-2.8.7.0-bullhead.img and then adb push supersu?
I've done what the op had and I have root with encryption.
Sent from my Nexus 5X using XDA Free mobile app
I also want to agree. I just tried to unlock tethering without full root, but ran into issues. So to fix my issues, I just decided to follow the ops steps and root the phone. After adding the image, I was unable to push supersu due to adb not working in twrp. However, I rebooted the phone and saw the encryption password on boot. Once the os was loaded, I went into settings -> security and noticed the phone was set to encrypted. Looking through the program list, supersu installer was in the list and worked perfectly. Thanks op.
Sent from my Nexus 5X using XDA Free mobile app
How long does the device take to boot up? I've been sitting at the boot animation for a while now.
You can have root access through SuperSU with encryption enabled. I have it running just fine with encryption enabled. What you do have to have turned off is dm-verity. With dm-verity enabled, modification to the system partition are "not allowed".
And Chainfire's modified boot image has 3 main modifications:
1. A modified sepolicy with SELinux provisioning for SuperSU
2. dm-verity turned off
3. forceencrypt for data partition disabled. Basically disabled forced default encryption, but you can still encrypt.
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Camp As A Champ said:
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Click to expand...
Click to collapse
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
dbrohrer said:
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
Click to expand...
Click to collapse
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Camp As A Champ said:
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Click to expand...
Click to collapse
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
This worked for me too - I tried to:
>adb push supersu.zip /system/
... Then in TWRP install -> select /system/supersu.zip
But this failed for some reason... However, this worked:
>adb sideload supersu.zip
Then reboot, and restore Thanks a lot! Didn't want to give up encryption either...
dbrohrer said:
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
Click to expand...
Click to collapse
Will I be able to do this through TWRP or should I just use ADB to flash the image files? Sorry for all the questions, this is my first nexus phone and I'm getting used to all the new methods
Nevermind, got everything to work, thanks for the help though
Hey guys! I've having some trouble getting my device set up with root and encryption, while ending with a locked bootloader. I hope I can find some help.
Here is the procedure I tried:
Unlocked the bootloader
Did a full restore to MHC19I through fastboot
Flashed this boot.img
( This is so I can encrypt the user data partition after getting into Android, and it also allows a system-root without getting a boot loop )
Flashed the twrp-3.0.0-1-angler.img recovery
Locked the bootloader
Booted into TWRP without ever going into Android yet
Sideloaded BETA-SuperSU-v2.68-20160228150503.zip
Booted into Android and setup with my Google account, I used a fingerprint and set a PIN, and selected "PIN required on startup"
Update all the stock apps, with some reboots in between
Then encrypted the phone through security settings
Now here is where I'm having trouble.
When I boot into TWRP after having encrypted the user data partition, it asks for my password, as it should, but it won't take my PIN. It tells me "Password failed, please try again" and "Failed to decrypt data." Is the password prompt not asking for the PIN I set? Does TWRP only support decryption with a password, or something? Can I not use a fingerprint to lock the device? What am I missing here?
Is there perhaps another procedure to getting Android setup with TWRP, root, and user data encryption while ending with a locked bootloader?
Thank you in advance for all your help!
You need a modified Twrp for this new Base. Just have a look around
Gorgtech said:
You need a modified Twrp for this new Base. Just have a look around
Click to expand...
Click to collapse
Is the "twrp-3.0.0-1-angler.img" image here not the new modified TWRP for MHC19I?
edit: According to this post, I'm using the correct version of TWRP.
Yes, this one should fit. I had the same problem before.
mylios101 said:
Hey guys! I've having some trouble getting my device set up with root and encryption, while ending with a locked bootloader. I hope I can find some help.
Here is the procedure I tried:
Unlocked the bootloader
Did a full restore to MHC19I through fastboot
Flashed this boot.img
( This is so I can encrypt the user data partition after getting into Android, and it also allows a system-root without getting a boot loop )
Flashed the twrp-3.0.0-1-angler.img recovery
Locked the bootloader
Booted into TWRP without ever going into Android yet
Sideloaded BETA-SuperSU-v2.68-20160228150503.zip
Booted into Android and setup with my Google account, I used a fingerprint and set a PIN, and selected "PIN required on startup"
Update all the stock apps, with some reboots in between
Then encrypted the phone through security settings
Now here is where I'm having trouble.
When I boot into TWRP after having encrypted the user data partition, it asks for my password, as it should, but it won't take my PIN. It tells me "Password failed, please try again" and "Failed to decrypt data." Is the password prompt not asking for the PIN I set? Does TWRP only support decryption with a password, or something? Can I not use a fingerprint to lock the device? What am I missing here?
Is there perhaps another procedure to getting Android setup with TWRP, root, and user data encryption while ending with a locked bootloader?
Thank you in advance for all your help!
Click to expand...
Click to collapse
First: Why did you re-lock the bootloader? You cant flash any twrp updates or update with factory images.
Second: You should have just flashed supersu in twrp before any booting?
When clean installing I personally follow these:
fastboot flash bootloader
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-02.50.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot format userdata
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash recovery twrp
fastboot reboot-recovery
While in twrp I:
adb push supersu to /sdcard/
then flash supersu in recovery
then wipe dalvik/cache in twrp
finally let the phone boot and set up normally. Leaving bootloader unlocked
Gorgtech said:
Yes, this one should fit. I had the same problem before.
Click to expand...
Click to collapse
You've had the same issue before that I'm having now? What was your fix?
I've flashed system, boot and vendor before. Also updated the bootloader and the radio and was asked for a password which I could not get rid off. I had to sideload supersu and also flash a modified Twrp after. Now I can access the recovery like I was used to. It's the latest Base which causes trouble.
thepoetlives89 said:
First: Why did you re-lock the bootloader? You cant flash any twrp updates or update with factory images.
Second: You should have just flashed supersu in twrp before any booting?
Click to expand...
Click to collapse
I lock the bootloader for obvious security reasons, but it leads to the user data partition being wiped, which prevents the partition from encrypting on initial Android setup.
I do flash Supersu through TWRP before my first boot to Android, otherwise TWRP gets wiped out.
I'll give your procedure a try! Thank you.
mylios101 said:
I lock the bootloader for obvious security reasons, but it leads to the user data partition being wiped, which prevents the partition from encrypting on initial Android setup.
I do flash Supersu through TWRP before my first boot to Android, otherwise TWRP gets wiped out.
I'll give your procedure a try! Thank you.
Click to expand...
Click to collapse
As far as i know with 6.0.1 with the stock boot.img it automatically encrypts on first boot, even with an unlocked bootloader.
thepoetlives89 said:
As far as i know with 6.0.1 with the stock boot.img it automatically encrypts on first boot, even with an unlocked bootloader.
Click to expand...
Click to collapse
No, I believe the problem is that it does not automatically encrypt on first boot when I lock the bootloader. My work around was using a modded boot.img so I can encrypt post-setup through the security settings menu, but I can't decrypt with TWRP. Without the boot.img and a locked bootloader, it sits in a bootloop and never encrypts. through the security settings option.
I have to confirm this, but it looks like the only way to get the device encrypted, rooted, and TWRP accessible is to not use the modded boot.img and leave the bootloader unlocked, which I'd rather not. Regardless, I'll give it a try and report back.
mylios101 said:
No, I believe the problem is that it does not automatically encrypt on first boot when I lock the bootloader. My work around was using a modded boot.img so I can encrypt post-setup through the security settings menu, but I can't decrypt with TWRP. Without the boot.img and a locked bootloader, it sits in a bootloop and never encrypts. through the security settings option.
I have to confirm this, but it looks like the only way to get the device encrypted, rooted, and TWRP accessible is to not use the modded boot.img and leave the bootloader unlocked, which I'd rather not. Regardless, I'll give it a try and report back.
Click to expand...
Click to collapse
I was able to encrypt with the modified boot.img that supersu makes when you flash it over the one that comes with the factory image. Bootloader unlocked.
Gorgtech said:
I've flashed system, boot and vendor before. Also updated the bootloader and the radio and was asked for a password which I could not get rid off. I had to sideload supersu and also flash a modified Twrp after. Now I can access the recovery like I was used to. It's the latest Base which causes trouble.
Click to expand...
Click to collapse
How did you sideload supersu? I have the same problem as you
Fastboot format userdata in terminal.
kunal_07 said:
How did you sideload supersu? I have the same problem as you
Click to expand...
Click to collapse
I'm using the "adb sideload" function under "advanced" in TWRP. Another user suggested doing an "adb push" and then using the regular TWRP install instead. I'm going to try that and see what happens.
edit: sideloading vs pushing supersu made no difference. Android is still not encrypting the user data partition on first boot.
edit 2: After some testing, it looks like flashing the latest beta of Supersu is what is preventing Android from encrypting, which is obviously a problem. Without flashing Supersu, TWRP doesn't persist and I can't get root access.
I was able to root using RC SuperSU 2.69 using chainfire auto root
Easy solve.
1. Create 4 digit screen lock pin code when booted in rom settings>security
2. Use flashify to flash newest twrp
3. Boot into new twrp and use new pin code to decrypt data
When flashing new version of TWRP it automatically encrypt the data with "default_password" but if you try to use that as your password it will not work. If you create a pin, then use that pen to decrypt the password it will work. Then if you go back into your booted up rom and change the password to none TWRP will not ask you for a password.
Can't remember steps 1. And 2. Might be switched
i just updated to the mch19i build via fastboot (since i'm rooted and can't take an ota apparently - has anyone made twrp-able zips for those updates yet?) and am having this same problem. what's different about this build that we need a different twrp for?
asj0422 said:
i just updated to the mch19i build via fastboot (since i'm rooted and can't take an ota apparently - has anyone made twrp-able zips for those updates yet?) and am having this same problem. what's different about this build that we need a different twrp for?
Click to expand...
Click to collapse
Well for one thing twrp 3.0.0.1 allows for vendor images to be flashed to the vendor partition. The previous ones you can't. That's why I updated with flashify. Two seconds of easiness. Just set a 4 digit lock screen pin before because twrp encrypts with unknown password upon first boot that's why you assign it one.
The only way for otas is to side load or fast boot flash.
Or. Run a custom ROM and get flashable zips for updates, these work great with all these Google update releases
Hi everyone, I hate to bring back an old post but I am new to XDA today so I'm getting used to it.
Well, I'm a first time ROM user, PureNexus + ElementalX kernal (amazing). But I had a question regarding this encryption and TWRP. I know older versions of TWRP had issues with entering the encryption password, I want to encrypt mine but I want to be sure that this issue has been fixed. I can't find anything online regarding it either. Can anyone help me out?
Device: Nexus 6P
ROM: PureNexus 7.1.2_r24
Kernal: ElementalX 5.03
TWRP: 3.1.1
Any information would be helpful! Before I encrypt! Just don't wanna do it then be stuck.
Ayeeebroham said:
Hi everyone, I hate to bring back an old post but I am new to XDA today so I'm getting used to it.
Well, I'm a first time ROM user, PureNexus + ElementalX kernal (amazing). But I had a question regarding this encryption and TWRP. I know older versions of TWRP had issues with entering the encryption password, I want to encrypt mine but I want to be sure that this issue has been fixed. I can't find anything online regarding it either. Can anyone help me out?
Device: Nexus 6P
ROM: PureNexus 7.1.2_r24
Kernal: ElementalX 5.03
TWRP: 3.1.1
Any information would be helpful! Before I encrypt! Just don't wanna do it then be stuck.
Click to expand...
Click to collapse
Not sure what you are asking. If you've set a PIN, use it when promoted by TWRP.
I have installed TWRP for android N, however when I run it I need to enter a password to decrypt my data. I know this can be a problem resulting from not booting after unlocking, however I did. Also the default password 'default_password' did not work. I was wondering if there are any ways around this that do not involve wiping my phone.
Thanks
stants225 said:
I have installed TWRP for android N, however when I run it I need to enter a password to decrypt my data. I know this can be a problem resulting from not booting after unlocking, however I did. Also the default password 'default_password' did not work. I was wondering if there are any ways around this that do not involve wiping my phone.
Thanks
Click to expand...
Click to collapse
adb twrp-3.0.2-2-angler.img. Sounds like you are on an older version of TWRP.
BTW" with this version, you do not need to decrypt.
Currently adb twrp-3.0.2-2-angler.img. Sounds like you are on an older version of TWRP.
Click to expand...
Click to collapse
The version I'm using is twrp-3.0.2-3-angler, so it seems to be p to date, and apparently there are bugs for twrp 3.0.2-2 for android N.
I tried to root H918 T-Mobile, and ended up with just an unlocked bootloader, and no TWRP install.
I'd like to re-lock the bootloader, but I can't find any instructions. Any unroot instructions I've seen, include using TWRP.
Thanks!
Same here, before i ended up bootloader unlocked. Well decided to relock the bootloader
Just fastboot oem locked
jay661972 said:
Same here, before i ended up bootloader unlocked. Well decided to relock the bootloader
Just fastboot oem locked
Click to expand...
Click to collapse
OK. Tried this....and now I get:
Your device is corrupt
It cannot be trusted
and will not boot
Please help!
jeffeil said:
OK. Tried this....and now I get:
Your device is corrupt
It cannot be trusted
and will not boot
Please help!
Click to expand...
Click to collapse
have to wipe the whole phone you must have a custom boot.img
the t-mob version is unlocked via lgs website right
Try this method. As far as I know everything is back to stock at least it acts like it is.
https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
Old thread but i found it while trying to restore my US996 back to factory. The kdz method works then you just run the fastboot command to relock the bootloader. Amazing it was that easy to relock the bootloader....
I flashed the 10s update to h918 and very stupidly forgot to flash root so I'm stuck on unrootable 10s. I want to lock my bootloader so can at least have Android Pay working, if i lock it can it be unlocked again or do i have to wait for a root method for the new 10s software?
nymikey said:
I flashed the 10s update to h918 and very stupidly forgot to flash root so I'm stuck on unrootable 10s. I want to lock my bootloader so can at least have Android Pay working, if i lock it can it be unlocked again or do i have to wait for a root method for the new 10s software?
Click to expand...
Click to collapse
I think you can unlock /relock as many times as you want. Root take place after unlocking but you can't do that anymore.
I rooted my v20 f800l a few months ago using dirty Santa method. Everything was going fine until I decided to reset my phone via twrp. I selected system, internal memory, cache and ended up without an os with only access to twrp. I had a nandroid backup but twrp couldnt read or detect the nandroid backup files. With nothing else left to do i flashed it with a kdz file version 10e using lgup software. Now I have my phone running fresh os very smoothly but the bootloader is locked and root/twrp is not there anymore. Now I plan on rooting it again as I'm still on 10e version but I'm not sure if there is a bootloader lock/relock limit, I've already unlocked bootloader once and locked it once, can I do it again? Or is there a limit to it? Please help
lamepsycho said:
I rooted my v20 f800l a few months ago using dirty Santa method. Everything was going fine until I decided to reset my phone via twrp. I selected system, internal memory, cache and ended up without an os with only access to twrp. I had a nandroid backup but twrp couldnt read or detect the nandroid backup files. With nothing else left to do i flashed it with a kdz file version 10e using lgup software. Now I have my phone running fresh os very smoothly but the bootloader is locked and root/twrp is not there anymore. Now I plan on rooting it again as I'm still on 10e version but I'm not sure if there is a bootloader lock/relock limit, I've already unlocked bootloader once and locked it once, can I do it again? Or is there a limit to it? Please help
Click to expand...
Click to collapse
Don't believe there's any limit so go ahead
Sent from my LG-H910 using XDA Labs
A few days ago I updated my phone via TWRP, the process taken always worked:
1. Install firmware
2. Install decrypt.zip
3. Install Magisk
But this time, it didn't. After rebooting the phone, forced encryption started and after it was done, I found out that Magisk wasn't installed, on top of that, TWRP was replaced with the original recovery. Is there any way to re-root the phone?
Note: I have updated the phone in this manner a few times and nothing like this ever happened also, I tried reinstalling TWRP via fastboot, sins the bootloader is already unlocked, but got write errors, because of the forced encryption more than likely.
Are you sure you used the correct decrypt zip file ?
Tianhe said:
Are you sure you used the correct decrypt zip file ?
Click to expand...
Click to collapse
Yep, have used it in the past so i am sure it was the correct one.
User483901 said:
Yep, have used it in the past so i am sure it was the correct one.
Click to expand...
Click to collapse
There are different decrypt zips for Oreo & Pie. Also, there may be variations for different firmwares within the same version itself. Same goes for TWRP.
Tianhe said:
There are different decrypt zips for Oreo & Pie. Also, there may be variations for different firmwares within the same version itself. Same goes for TWRP.
Click to expand...
Click to collapse
Oh, didn't know that. But regardless, what does it matter what was used, I mean TWRP is no longer on the device so talking about which decrypt was used doesn't matter cuz it can't be used until TWRP is reinstalled which i think is impossible, cuz of the forced encryption, unless you know of a way.
User483901 said:
Oh, didn't know that. But regardless, what does it matter what was used, I mean TWRP is no longer on the device so talking about which decrypt was used doesn't matter cuz it can't be used until TWRP is reinstalled which i think is impossible, cuz of the forced encryption, unless you know of a way.
Click to expand...
Click to collapse
Encryption doesnt affect TWRP, the only drawback is that you cannot mount internal storage. However, if the TWRP version supports FDE natively then even that is possible. So encrypted devices can have TWRP recovery, you just need unlocked BL etc.
XDA
How to flash TWRP recovery in max Pro M1 without PC please help
@secreattecheme said:
How to flash TWRP recovery in max Pro M1 without PC please help
Click to expand...
Click to collapse
Is your phone bootloader unlocked?
I have never heard someone losing twrp by updating firmware. Perhaps you might have updated the rom which contained the stock recovery and hence replaced twrp. You can flash twrp again using fastboot. Remember that in order to remove encryption (since your phone has already encrypted the data) you'll have to format data from twrp and you'll lose all your data, even internal storage and twrp backups.
About decrypt.zip, there is a sequence of flashing it. It didn't always work for me though.
farhanshaikh671 said:
I have never heard someone losing twrp by updating firmware. Perhaps you might have updated the rom which contained the stock recovery and hence replaced twrp. You can flash twrp again using fastboot. Remember that in order to remove encryption (since your phone has already encrypted the data) you'll have to format data from twrp and you'll lose all your data, even internal storage and twrp backups.
About decrypt.zip, there is a sequence of flashing it. It didn't always work for me though.
Click to expand...
Click to collapse
No, I updated it by going to the Asus website and downloading the firmware update, have done the same with the Pie update and the one before it, edited the image file, so it can be flashed using TWRP and then did the steps in the OP.
Also, as said before i can't flash TWRP sins i get write errors in fastboot.