Hi all,
Is there any Custom ROM running Android 11, with encryption working. I tried PE11 and Crdroid 7.4 and Arrow11.
All are going to boot loop, if encryption is initiated.
I'm looking for a ROM which can do encryption (for work purpose). It will be helpful, if someone can share working custom ROM tested.
Also is this some kernel issue or TWRP settings which is causing encryption to fail?
I would also love encryption. This is one of the persistent issues I have with custom ROMs and why I'm moving to a real Linux phone once they get a bit better.
Related
Having issues encrypting system now that phone is rooted it just reboots without enabling no matter if i try fast or normal version now that rooted.
I have recently got safestrap setup and i was wondering which rom is closest to stock but has system encryption working .
Thanks in advance not too many roms out sadly yet for this device and verizon atm
so may have to try them all and see which works trial and error but would like to save myself some time and/or if anyone knows a work around to make this work i would be much appreciated just want android system encryption working with rooted stock ideally so if i can fix that without needing a rom all the better
Hi, I have a sprint LS980, but it seems that ANY rom that I try that is not stock based, whether it's lollipop or marshmallow, CM12, CM13, Blisspop, CrDroid, Resurrection Remix, I can never seem to get encryption working, which is a big deal for me. Every time I start encryption with these roms, no progress bar is ever shown, all I get is the boot animation and the phone does nothing unless I hard reset. Obviously, when I hard reset the phone boots and works normally, but is not encrypted.
My question is, has ANYONE managed to get encryption working on a non-stock rom on a Sprint LG G2?
Worked for me on RR (12.1) and CM13 without a problem at all. Have a D802
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
dude...I just got the N6P and ran CM13 within hours. This is what I did...
unlocked the bootloader
downloaded the lastest (MTC19X) image off of https://developers.google.com/android/nexus/images and unpacked it into the C:\Program Files (x86)\Android\android-sdk\platform-tools folder
ran the flash-all.bat
fastbooted TWRP
installed CM13. (didn't wipe internal storage)
installed arm64 open Gapps pico
BAM!!!
right now running stock kernel. it's cool. I'm PrivacyGuard-ing the hell out of all my apps (turned off START AT BOOT and KEEP AWAKE for almost every downloaded app), though, so battery is OK
also using Kernel Adiutor but underclocking values for the CPUs doesn't seem to stick
So it likely worked for you since you had flashed the newest vendor.img first. Apparently there are compatibility issues with certain features that cause them not to work (such as WiFi) if you're using an older one.
chaoticyeshua said:
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
Click to expand...
Click to collapse
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
kaufikauf said:
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
Click to expand...
Click to collapse
Very much so. I appreciate it!
Has anyone encountered the constant popup of the Select Sim Card message? I'm using project fi and I am still unable to find a solution to this issue.
I just moved from Pure Nexus 7.1 to SuperXE 8.1. I think I forgot to flash vendor image but otherwise did full clean flash. ROM boots but when trying to connect to WiFi there is voice input but no keyboard. Haven't ever seen something like this before... Added vendor image and redid full/clean flash multiple times with same result. Unfortunately, activity on that ROM thread is a bit slow and I'm down without my phone so decided to ask for help here.
Adding $20 bounty for help fixing. Serious withdrawal mode without my phone. I have a backup phone but it is nearly unusable...
Solution here https://forum.xda-developers.com/showpost.php?p=76126862&postcount=263
Since you are coming from Nougat to Oreo i would suggest you first flash the full oreo factory image before flashing the oreo custom rom. Its not usually a must but solves a lot of minor problems
Hi, after attempting to enable encryption I get an infinite boot loop animation, and after I force a hard reset (keeping the power button pressed) the phone boots back to normal as if nothing happened. This means that encryption was not even started (otherwise it would be needed to format partition again if the process was interrupted).
What are my options here? On previous Android versions, whenever I came across a Rom that didn't support encryption, I would just flash a stock recovery image alongside the custom rom and try encrypting again, successfully. However, there are no Android 11 stock recovery images for this device (it got abandoned in Android 8.1 I believe), so this isn't an option anymore.
Unfortunately this ROM doesn't seem to have a dedicated thread here on XDA and people on their Telegram channel have not been able to provide guidance so far...
Any tips are appreciated!
ROM: PixelExperience Plus 11 (Android 11) version 2021.05.14
Device: Moto G5 Plus (potter, XT1685)
Recovery image: TWRP 3.5.2_9-0-potter
I have found no v11 or v10 roms which work with encryption (even when they say they do). I have not tried many v9; Your answer is to go back to stock 8.1 and everything will work again (but you'll be on v8):
[Oreo][Stock][Rom] TWRP Flashable Stock Builds
About this project This project provides repackaged Stock Oreo roms that can be flashed by TWRP. Modifications from stock are listed below. As we are now moving into the Oreo world, I've decided that now is a good time to make a few changes...
forum.xda-developers.com
edit: note that i'm on xt1687 (usa) model of potter
edit2: I just tried Arrow v10(official) and it encrypts (after a number of reboots; give it time)
bravo97 said:
edit2: I just tried Arrow v10(official) and it encrypts (after a number of reboots; give it time)
Click to expand...
Click to collapse
hi, in the case of PE+ 11, it just goes to reboot the first time and stays in loading android screen forever (waited a couple hours last time), so I think "giving it more time" wouldn't solve it.
Good to know there's some Rom compatible with encryption though, although it's android 10... I also got a hint that crDroid 11 may be compatible with encryption on potter.