Hi,
If I try to turn on android disk encryption I get a logcat saying unable to get the block device size.
I accidentally found that if I turn on selinux enforcing it starts but immediately after boot I get the infamous 'encryption unsuccessful'.
I tried shrinking the filesystem by a few MB but same outcome.
Anyone successfully managed to turn on encryption in cyanogenmod?
I tried doing it in the stock rom and it worked but TWRP/CWM can't mount the data (likely stock rom is using another encryption method?).
Thanks.
Looks like encryption is somewhat successful as I can decrypt the data in CWM (vdc cryptfs ...) and even more, with a stock kernel I get the enter password prompt (can't enter as I get a com.android.phone process has stopped all over again).
Looks like a kernel bug in CM.
Yes, it's definitely a kernel bug as I flashed the kernel from this image (http://forum.xda-developers.com/gal...pment/cm-11-port-galaxy-tab-pro-10-1-t2850042) and everything works as expected.
I'll try and extract the initrd from both kernels and see of any diffs.
I found a solution to fix "RECOVERY IS NOT SEANDROID ENFORCING" error and hanged on boot logo and having root.
I tried to root my s6 edge with chainfire auto root and that was a mistake because my device hanged on boot logo with a message saying "RECOVERY IS NOT SEANDROID ENFORCING". i have searched for 4 hours here and in other forums with no luck, all of them said i have to re-flash the stock firmware again. so here is what you have to do
download these files
1. Kernel https://mega .co.nz/#!Nc9AjRwI!EB5-e_qpV41yGr-ADd1V6Sr8E0HFiLF8h7tOTApvby Y ( remove the space )
2. TWRP 2.8.7.1 https://dl.twrp.me/zeroltetmo/twrp-2.8.7.1-zeroltetmo.img.tar
3. Odin 3.10.7 http://forum.xda-developers.com/attachment.php?attachmentid=3446301&d=1440131361
4. SuperSU https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
flash the kernel first.
then flash the recovery twrp
boot into twrp and push the superSU zip file to your internal memory using adb command.
install the superSU file and reboot then bingo.
if you still have the message on booting, you have to freeze the security logagent
Hello, I grabbed some Flyme 6 ROM for the Swift from AFH. Flashing in TWRP gives a message 'Failed to mount dev/block/bootdevice/by-name/userdata at data" but flash ends successfully. Booting up sticks at boot animation. What could be the problem?
Hi all,
- bootloader is unlocked
- I have latest OOS installed (9.09 I think?)
- twrp codeworx 3.3.1
- Magisk installed
- developer options enabled, adb enabled
And here's my issue:
- downloaded latest magisk as zip file
- selected reboot to recovery
- twrp asks me for password, I enter my NIP but says "Can,t decrypt data'"
- Provides no option to reboot to system...
- rebooted, goes again to twrp
- rebooted to other menu where you can select fastboot, recovery, system when selecting system it goes to recovery...
So right now I'm frigging STUCK going to recovery all the time.
What are my options out of this nightmare?
I'd think:
- flash stock recovery from fastboot?
- other?
Suggestions welcome guys, I'm at the office and can't try anything now but definitely need input before I screw up things even more
Thanks
liberteus said:
So right now I'm frigging STUCK going to recovery all the time.
What are my options out of this nightmare?
I'd think:
- flash stock recovery from fastboot?
- other?
Click to expand...
Click to collapse
So... Got home, booted via fastboot the PREVIOUS twrp recovery (i.e. NOT this one https://sourceforge.net/projects/ch...rkx-signed-forcedecrypt-dumpling.img/download) and it gave me the option to actually cancel the password and keep the system read only. At which point I was able to reboot to system, and that's it, fixed.
I'll flash the twrp version that got me out of my self digged hole now.
Here's the version I used: twrp-3.2.2-0-20180721-codeworkx-dumpling.img (2018)
I upgraded my 8 Pro to Android 11 (11.0.1.1 IN11BA) and was able to keep root using Magisk's feature "patch to inactive slot".
However, after two-three reboots on Android 11 (activating some Magisk modules, and installing some apps) the phone suddenly got stuck in a boot loop.
I figured it might be helpful for someone else to know how I recovered my phone without losing any data.
First, I needed to get access to the phone, so I entered fastboot mode by pressing volume button during boot.
Then I downloaded my firmware dump from XDA and patched the recovery.img using this tutorial:
https://forum.xda-developers.com/on...ecovery-oxygen-os-stock-recovery-adb-t4084487
My patched recovery image is linked in post #46 of that thread.
I fastboot flashed (since fastboot boot didn't work) the recovery image to my phone and rebooted to recovery.
Using the patched recovery image I was able to get root access to all partitions, including /data.
When investigating a boot loop on this phone I found the following path useful:
Code:
/mnt/vendor/op2/boot_log/
In that directory you will find logs from the last five or so boots, and at the end of the "android_boot.log" file I found this message:
Code:
StagingManager: Failed to install sessionId: 664232199 Error: APEX activation failed. Check logcat messages from apexd for more information.
I'm not familiar with "StagingManager" and "APEX sessions", but after digging through PackageInstallerService.java it seems this error is caused by some kind of app installation that is done during reboots (now I'm guessing).
Anyway, I didn't care much about the reason for the error, I just wanted my data back, so I deleted this file (containing the failed APEX session):
Code:
/data/system/install_sessions.xml
After deleting that file I was able to boot my system and access all my data again!
Nvm..
dladz said:
Don't need with the recovery is still intact so no need to touch it you'll cause more issues.
So you got the bootloop when you installed some magisk modules.
Click to expand...
Click to collapse
My boot loop was not caused by a magisk module. I did remove all magisk modules and even re-flashed stock boot.img, but that did not help.
adb wait-for-device didn't work since the boot loop occurred before adbd start (it seemed).
And, I absolutely didn't want to wipe my system from recovery.
nilezon said:
My boot loop was not caused by a magisk module. I did remove all magisk modules and even re-flashed stock boot.img, but that did not help.
adb wait-for-device didn't work since the boot loop occurred before adbd start (it seemed).
And, I absolutely didn't want to wipe my system from recovery.
Click to expand...
Click to collapse
No worries man I got the wrong end of the stick. Dw
I've Updated and it's stuck at bootloop . What I can do?
My mobile is the T-Mobile version that I have converted to Android 10 International.
this will help someone, for sure
nice work writing down your expirience
Just to be clear with what I said earlier.
If it fails after a magisk module installation then just boot to safe mode then reboot and all magisk modules will be deactivated.
According your post that's how it happened.
"However, after two-three reboots on Android 11 (activating some Magisk modules, and installing some apps) the phone suddenly got stuck in a boot loop"
1. Safe mode
2. Reboot
3. Remove last module and activate other modules.
Done
PS: I do a lot of module testing and this is my safety net so yes it 100% works.
You're method will help people for sure though
just so you know, you just saved my ass.
i expirienced the same problem
i did cleard data of google, google services, google framework and google play store
after that - google downloaded some kind of update and that's it
at android boot log there was same error
adb shell rm /data/system/install_sessions.xml using modded stock recovery rocks