SELinux is a security mechanism which stops unauthorized access of processes to other processes, actions and filesystems (UNIX's "file" includes all regular files, directories, block devices, character devices, sockets etc.). Every process, file, directory and action is labeled with an SELinux context, then a policy is defined what a context can do to other ...
First to clarify, Resize Partition is different than Resize File System, TWRP provides latter option. It resizes the ext2/3/4 filesystem to the size of partition it's created on. Filesystem size can be checked with df command when mounted, and partition size with blockdev.
Just like HDDs or SSDs on PC, Android's eMMC storage is divided into partitions (can ...
No. TWRP is only a custom recovery that replaces your stock recovery. But be sure to flash the right TWRP for your device.
Searching in this XDA thread
using your model number
would be a good idea (On some devices it is possible that root is lost, and you may need to root again)
Full credit to alecxs for this answer. Posting incase anybody else has the same problem in the future.
Download stock image(Mine was oneplus.com/uk/support/softwareupgrade/details?code=9)
Use extract_android_ota_payload-master to split the payload.bin inside the zip
(Method for step 2 https://pastebin.com/RfEHuvu7 , I did this on linux because my linux ...
If you have the habit of removing apps on a regular basis, then you can clear it regularly. Once a year or once every 6 months should be fine. If you have root, then you can use Titanium backup as stated on this answer to remove dex files not link to apps.
I have found the solution to my particular problem now, but if someone else knows more about this feel free to improve my answer or post your own.
Annoyed with what I thought to be heimdall's fault, I turned to odin (not in a religious way).
This, however, gave me the same error. Close to desperation, I decided to check everything that I did ...
Answer to your question is dm-verity:
The dm-verity feature lets you look at a block device, the underlying storage layer of the file system, and determine if it matches its expected configuration. It does this using a cryptographic hash tree. For every block (typically 4k), there is a SHA256 hash.
So /system and /vendor partitions are always mounted ...
I found that if upon receiving this error, before booting into LineageOS I can
Boot into the bootloader from TWRP,
Click on Reboot
Click on Bootloader
Boot into a new TWRP from the bootloader
Run twrp boot ./twrp.*.img
I can then install the gapps.
What cause this? Well my theory now is that the instructions on the Lineage OS suggest Wiping the System ...
While formatting with twrp results in an error, formatting with fastboot worked for me:
start phone, which will boot into twrp
reboot -> bootloader
fastboot format:ext4 userdata. This will of course delete all data from the phone.
The answer becomes clear once you read the install instructions:
You will need both files to install, as your device (OnePlus 6 aka enchilada) is an A/B device and thus has no recovery partition (recovery is part of the boot image there) – which means you cannot simply flash the recovery image using fastboot. So you download (or push) the ZIP to your device,...
You can always format from command-line to be sure where the problem is (if any). This will erase your whole /data partition which contains personal data, apps etc.
Boot to TWRP recovery.
Find block device for userdata partition. Usually it's symlinked at /dev/block/by-name/userdata or /dev/block/bootdevice/by-name/userdata. See FINDING BLOCK DEVICE section ...
I was in a similar issue on a Nokia running a stock ROM. Basically Magisk module killed my phone and the TWRP won't allow decryption.
I was able to boot successfully to system again by.. Removing Magisk, because in the absence of Magisk, the Magisk modules shouldn't load and hence the system should boot just fine. I did that by flashing my stock boot image....
thank you guys for your help
really appreciate it .. I solved the problem first by installing a custom ROM using TWRP. the system worked
then i discovered what i was doing wrong .. i was trying to flash a one-file stock OS .. which can only serve as an update
a 4-files stock ROM also worked.
Have you tried marking also the NAND ERASE option in Odin? Although marking the nand erase option would wipe the whole phone including the twrp and everything...and then try reflashing by going into download mode on your phone and then to Odin, you'll see a green/blue mark on the ICOM or something like that. If you pass on flashing and it gets stuck on ...
Remember that the custom ROM package will include the boot image too. And on A/B partition devices, the recovery rests is in the boot image. So, if the custom ROM has written your boot image, then your TWRP should be gone. What will load will depend on the recovery included in the boot image. It could be stock, something else or nothing.
i have experienced this with two other Xiaomi devices. first i could track it down to older unofficial variant of twrp 3.2.3 which is still decrypting with default password when official twrp 3.3.1 fails. so implementation of decrypting differs from each build, sometimes it is just a missing line in fstab, sometimes they forgot a flag during build.
But this ...
To boot into TWRP from LineageOS Recovery, from LineageOS Recovery
Click Reboot to Bootloader
Jump to the console on your machine, and run
fastboot boot twrp-*.img
That'll get you into TWRP from LineageOS Recovery.
Install the stock recovery first through fastboot. Then install twrp recovery again through fastboot. Then install the zip file of the stock rom. It worked for me. Get the stock recovery and stock rom from
Can you boot into TWRP? If you can I would try these steps:
- Boot into TWRP
- Once TWRP is booted you first need to wipe your /data partition or go into Wipe > Advanced Wipe and make sure Data is ticked then swipe to wipe.If this is your first boot into TWRP: swipe Wipe > Format Data from left to right and follow the instructions displayed onscreen.
- Once ...
After much try and waiting I couldn't get any satisfactory result out of it. So ultimately I had to flash the stock firmware. The name of the firmware could be deduced from the command fastboot getvar all
This is the link anyone who's facing the same ...
I have found a workaround to enter in recovery.
a)Turn off device
c)We enter in bootloader mode, with volumeup key we select the "recovery" and press power
d)Device reboot to twrp
The basic process of installing TWRP on every phone is to boot into TWRP itself first so TWRP could overwite the recovery partition and replace the stock Android recovery with TWRP itself.
Boot into bootloader / fastboot mode
Make sure that your device's boot loader is unlocked. If not, please follow this tutorial on forum.xda-developers....
TLDR: It works with Heimdall 1.4.2 (which at least in my case i had to compile myself from source code).
Unfortunatley i don't have the reputation i need to comment. But in my humble opinion... sbi you have not answered or solved your own question(at least you didn't solve the specific problem you have been dealing with)... and should unmark your answer as ...