Hi,
I'm on latest M version, latest TWRP, systemless root and Despair kernel 3.1.
When I first installed TWRP it couldn't decrypt partitions, so I had to install a kernel that disables force encrypt and factory reset the phone. So I ended up with un-encrypted partitions.
Now, TWRP supports decryption so I thought to encrypt the partitions. I went to Security -> Encrypt phone. This has been hanging on Android animation logo for 2.5hrs and no indication when it will finish.
Has anyone had a similar problem ?
What are my chances that it will complete gracefully and I wont need to factory reset the phone once again?
jodvova said:
Hi,
I'm on latest M version, latest TWRP, systemless root and Despair kernel 3.1.
When I first installed TWRP it couldn't decrypt partitions, so I had to install a kernel that disables force encrypt and factory reset the phone. So I ended up with un-encrypted partitions.
Now, TWRP supports decryption so I thought to encrypt the partitions. I went to Security -> Encrypt phone. This has been hanging on Android animation logo for 2.5hrs and no indication when it will finish.
Has anyone had a similar problem ?
What are my chances that it will complete gracefully and I wont need to factory reset the phone once again?
Click to expand...
Click to collapse
Chances are very low. I had the same issue and the only way I was able to fix it was to use the Google factory image and completely wipe the phone. Then boot it before flashing anything including TWRP. It encrypts in about a minute. Setup the phone, and then flash TWRP, modified root boot image if you want, and the corresponding SU zip.
Sent from my Nexus 6P using Tapatalk
Related
So I went ahead and started to root my Nexus 6P. I installed the systemless modified boot.img and TWRP, then I sideloaded the systemless SuperSU in TWRP. I am encrypted and TWRP can decrypt still, however when I try to boot the phone, I get the Decryption unsuccessful message and it wants me to reset the phone. I hit reset, it factory resets in TWRP, and it just comes to the same screen upon boot. Any ideas?
Just flashed the userdata.img and system.img parts of the factory image, upon boot I get a message saying there is an internal error in the device and to contact the manufacturer. I just flashed the stock bootloader, boot.img, radio, system, userdata and now it is just stuck on the boot animation. =(
Just used the flash-all.bat in the factory image and now it is working again. Not sure what caused the problem, I know others are using the systemless root method, so I have no idea.
gakio12 said:
Just used the flash-all.bat in the factory image and now it is working again. Not sure what caused the problem, I know others are using the systemless root method, so I have no idea.
Click to expand...
Click to collapse
Reflash vendor and it will fix error
Sent from my Nexus 6P using Tapatalk
So I was trying to flash the new N beta. I wanted to do it without wiping internal storage if possible so I went into the flash-all.bat and deleted "-w" so it wouldn't wipe. I wasn't sure if it would flash successfully without wiping but I figured it was worth a shot and if it didn't work I could always boot to TWRP, copy my data to my PC, then do a flash with a full wipe...
Well, after the flash completed and the phone booted up I'm getting the "Encryption Unsuccessful" error. Did it really attempt to encrypt my phone while flashing the beta? Why would it do that? Is there anything I can do at this point to avoid wiping my data? Losing my data isn't a huge deal, but I'd like to know why this happened...
I had the same after flashing Nougat factory in a similar way. However, I had hard-booted after about 15 mins into the first boot as I figured it was in a bootloop. However, I now suspect it was encrypting the phone while doing the first boot. If this was the case, thats a big usability flaw IMHO - it should notify what's going on, and tell the user to connect the charger. Anyways, looks like I'm going to have to restore from backup
if you used the stock boot image then that's why it encrypted you. Stock has forceencrypt. You need a modified boot image to remain decrypted. @Tigerstown has a thread with modified boot images for angler. Use that in place of stock boot image and decryption will remain. For now however you will have to format data. Soooooooo. Flash the modified boot image then format data and you will be decrypted again.
The topic should be SM-A300H can't encrypt. The other issue I solved.
So this is my issue: Encryption doesn't install correctly. I am using lollipop.
After choosing encrypt my device in settings/security it reboots, and shows the green android symbol, but nothing more happens. It shows the green android character for about 15 seconds, and then it boots as usual without encrypting the system.
I did a wipe with TWRP 3.0.2-1-ashyx because of the encryption problem, I wanted to try out with a fresh install and see if it was possible to encrypt the system but it did not make a difference.
I had rooted the device with Kingroot before the wipe, and kingroot was still installed even after doing the wipe which is odd. I tried uninstalling kingroot after the wipe as well but encrypt still didn't work, same problem.
So if there's a solution to this problem I would be grateful if you can help me.
Additional question: in case I cannot get encryption to work for some yet unknown reason, is there any 3rd party app I can try that will encrypt the entire system? I am not looking to encrypt single files, only full system encryption is good enough.
*deleted*
Flash the stock firmware then boot to recovery and factory reset.
You should then be able to encrypt.
Be forewarned that if you do encrypt you will no longer be able to mount data or storage in twrp.
hi guys,
please i have some questions i really need there answers:
1- (rooted phone) if i do a factory data reset will the root gone and the TWRP also ?
2- (rooted phone) is there a way to install an update if i got it ( like update security patches "monthly" ) on rooted phone without wipe data or loosing the root or TWRP?
3- (rooted phone) if i reinstall the factory image full,the root and TWRP will have gone or not ?
thanks a lot !
1. If you use systemless root a factory reset will remove it. If you use a root method that modifies the system partition a factory reset won't remove root. Factory resets will not remove TWRP.
2. Installing monthly security updates and keeping TWRP, root, and data can be done by manually installing the update using fastboot and doing the following:
-Systemless root method: flash everything EXCEPT the recovery, boot, and userdata images.
-System based root method: install everything EXCEPT the recovery and userdata images. You will have to reflash Superuser/SuperSU (whichever you prefer) in TWRP since flashing the system image will remove root. There's no way around this.
3. If you use fastboot to install everything included in a factory image you will lose root, data, and TWRP.
Face_Plant said:
1. If you use systemless root a factory reset will remove it. If you use a root method that modifies the system partition a factory reset won't remove root. Factory resets will not remove TWRP.
2. Installing monthly security updates and keeping TWRP, root, and data can be done by manually installing the update using fastboot and doing the following:
-Systemless root method: flash everything EXCEPT the recovery, boot, and userdata images.
-System based root method: install everything EXCEPT the recovery and userdata images. You will have to reflash Superuser/SuperSU (whichever you prefer) in TWRP since flashing the system image will remove root. There's no way around this.
3. If you use fastboot to install everything included in a factory image you will lose root, data, and TWRP.
Click to expand...
Click to collapse
Could you explain me what are the difference between systemless root method and system based root method, in order to get know what is it the method that I used
Chouiyekh said:
Could you explain me what are the difference between systemless root method and system based root method, in order to get know what is it the method that I used
Click to expand...
Click to collapse
If you are running Marshmallow or Nouget and used a version of SuperSU that is a year or less old it does system less root by default.
You can flash OTA updates on a rooted device with FlashFire without using a computer.
You can also flash an OTA image in TWRP and then simply flash root after, before you boot the phone. If the phone boots without root, out will wipe TWRP and leave you with stock recovery.
But honestly, from the questions being asked, you might not want to try this stuff until you understand it better. Losing root and TWRP is not a big deal. You can flash them again in about 1min and 30 seconds, so it's not worth worrying about.
Sent from my Nexus 6P using Tapatalk
Why would factory reset remove systemless root? I expect factory reset to only reset what you're supposed to have changed since factory image. That is /data.
Systemless must be in /data if it's not in /system, right? I don't really know much about systemless, because I don't use Android pay, Snapchat or play children's games haha.
But my guess is that if it's not touching system, then it must be in data, so wiping data would remove it. But I'm just guessing.
Sent from my Nexus 6P using Tapatalk
HikingMoose said:
You can also flash an OTA image in TWRP and then simply flash root after, before you boot the phone. If the phone boots without root, out will wipe TWRP and leave you with stock recovery.
But honestly, from the questions being asked, you might not want to try this stuff until you understand it better. Losing root and TWRP is not a big deal. You can flash them again in about 1min and 30 seconds, so it's not worth worrying about.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
thank you, i got it easily because i'm not a beginner i have some experience
HikingMoose said:
Systemless must be in /data if it's not in /system, right?
But my guess is that if it's not touching system, then it must be in data, so wiping data would remove it. But I'm just guessing.
Click to expand...
Click to collapse
You guessed right. Never thought of that, thought it was actually all done from boot partition.
Quoting Chainfire:
As the binaries should still be updatable, and we don't know the space we have available in the boot image itself, we're mounting a (writable) ext4 image with /su as mount point from /data, and modifying PATH accordingly. Interestingly, for reasons yet unknown to me, if the image is mounted r/o by init, later remounting it r/w causes a bunch of issues. So we're keeping it r/w (for root) for now.
Ok have a ZTE Axon 7 can't flash any thing because of it instantly encryption and I get recovery and then game over any one have a Cure for this......... thanks in advance.
You have to do a factory wipe, to remove encryption. Then when setting up the phone again when it prompts you to set a security pin or finger sprints skip that part.
chairmanmarv said:
You have to do a factory wipe, to remove encryption. Then when setting up the phone again when it prompts you to set a security pin or finger sprints skip that part.
Click to expand...
Click to collapse
Tried that and it didn't work.....it doesn't matter what I flash stock ROMs tell me my password is correct but memory is corrupt and need to be wiped and when I flash a custom ROM it doesn't boot just two flashes of the led and that's it.
Which TWRP recovery are you on?
What I mean by Factory reset is a full Factory wipe your whole internal is erased. It is like a clean slate new phone.
You should have all the necessary files for your flash on your sd card there is an option to select storage to flash from there.
So when I first swapped from Stock Nougat to AEX I was encrypted on 5/4 ROM my internal was locked by encryption and could only dirty flash roms. it was annoying so I factory wiped and flashed latest AEX from there and didn't set up security right away so no encryption.
I realised my TIBU back ups were all on internal so had to basically start from scratch oops lol.
It is a little outdated now with the official Oreo roms but user @Oki 's guide helped me a lot and has clear steps and guides to get you all rooted and sorted on custom roms.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
chairmanmarv said:
Which TWRP recovery are you on?
What I mean by Factory reset is a full Factory wipe your whole internal is erased. It is like a clean slate new phone.
You should have all the necessary files for your flash on your sd card there is an option to select storage to flash from there.
So when I first swapped from Stock Nougat to AEX I was encrypted on 5/4 ROM my internal was locked by encryption and could only dirty flash roms. it was annoying so I factory wiped and flashed latest AEX from there and didn't set up security right away so no encryption.
I realised my TIBU back ups were all on internal so had to basically start from scratch oops lol.
It is a little outdated now with the official Oreo roms but user @Oki 's guide helped me a lot and has clear steps and guides to get you all rooted and sorted on custom roms.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Click to expand...
Click to collapse
Just found out that the phone has bricked itself it would play any video or sound so did a hard reset now just getting a constant boot loop trying to get it in to EDL as we speak.....got EDL flashed stock ROM in miflasher now stuck on splash screen.......been on the splash screen for 10 minutes now.......
chairmanmarv said:
Which TWRP recovery are you on?
What I mean by Factory reset is a full Factory wipe your whole internal is erased. It is like a clean slate new phone.
You should have all the necessary files for your flash on your sd card there is an option to select storage to flash from there.
So when I first swapped from Stock Nougat to AEX I was encrypted on 5/4 ROM my internal was locked by encryption and could only dirty flash roms. it was annoying so I factory wiped and flashed latest AEX from there and didn't set up security right away so no encryption.
I realised my TIBU back ups were all on internal so had to basically start from scratch oops lol.
It is a little outdated now with the official Oreo roms but user @Oki 's guide helped me a lot and has clear steps and guides to get you all rooted and sorted on custom roms.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Click to expand...
Click to collapse
Ok now got the thing back was able to reunlock the bootloader and installed recovery flashed candy rom with one issue could not mount system so now just flashed Oreo stock rom so all good again....... thanks for the help
The stock ROM encrypts by default, and formatting data partition in twrp is the only way to remove it. But to prevent the encryption before it happens, you have a few options:
1. If you dont plan to root, flash @jcadduono's no verity opt encrypt zip (Google it)
2. Magisk and SuperSU can optionally disable encryption before it happens. Magisk Manager has a config option if you're installing from the app. You can use Aroma SuperSU config if SuperSU is your root method of choice.
Hope that helped!
I would like to note that AOSP/Lineage/CM-based ROMs dont encrypt by default. though Im sure it could be enabled if you wanted to. This seems to be unique to the stock ROMs, mainly because Google insists that phone OEMs should go for higher security by enabling encryption as the default.
AnonVendetta said:
The stock ROM encrypts by default, and formatting data partition in twrp is the only way to remove it. But to prevent the encryption before it happens, you have a few options:
1. If you dont plan to root, flash @jcadduono's no verity opt encrypt zip (Google it)
2. Magisk and SuperSU can optionally disable encryption before it happens. Magisk Manager has a config option if you're installing from the app. You can use Aroma SuperSU config if SuperSU is your root method of choice.
Hope that helped!
I would like to note that AOSP/Lineage/CM-based ROMs dont encrypt by default. though Im sure it could be enabled if you wanted to. This seems to be unique to the stock ROMs, mainly because Google insists that phone OEMs should go for higher security by enabling encryption as the default.
Click to expand...
Click to collapse
Yep this is the problem I am having now....... can't find much info about it.