So, I've been through a few threads that showed up but I don't seem to find any working solution regarding rooting process after the oreo update.
Also, since encryption is enforced, it's hard to get TWRP working with mounting the sd card and other partitions
Related
Hi,
I'm on the edge to take a leap towards encrypting my N7100 but before i do that i got question that i could not find answer. IF i have rooted rom and i encrypt my device what happens when i next time make OTA update, of course i will lost my Root for a moment, but will i be able to flash root back with odin if my internal memory is encrypted?
Also, if i got encryption in both internal and external (ext sd) memory will CWM work? Can it read system?
EDIT: Kies => Odin
Hello,
I have attempted to install twrp - (newest available version for ether) and it installs and boots, but twrp does not see the internal storage. I can't install SU because I can't see the storage.
Does anyone have a root guide for 7.0 on the ether? Or any idea what I am doing wrong?
I have searched and can't seem to find any discussion regarding root for the 7.0 release.
tweaked said:
Hello,
I have attempted to install twrp - (newest available version for ether) and it installs and boots, but twrp does not see the internal storage. I can't install SU because I can't see the storage.
Does anyone have a root guide for 7.0 on the ether? Or any idea what I am doing wrong?
I have searched and can't seem to find any discussion regarding root for the 7.0 release.
Click to expand...
Click to collapse
It doesn't see internal because it's ENCRYPTED. You need to format data then sideload either SuperSu or Magisk. Note: this will wipe internal storage and reset the device. The root method for 6.0 is literally the same for 7.0 on the Robin.
Flashing SuperSu or Magisk will disable the forced encryption. The reason you have to format data is to reset the partition and remove the encryption on the partition.
Hello everyone, first post here.
[pre-submitting edit: I'm new so no external links, sorry if they are garbage]
tl;dr
Installed LOS 16 on crackling, the LOS Wiki should be updated, here the issues I had to solve:
When preparing the phone, TWRP complains about /system having squashfs filesystem; solved by formatting the /system with ext4 filesystem;
Sideloading LOS 16 on stock Android 7.1.2 gives an unbootable OS; solved by downgrading first to stock CynogenOS (Android 6);
Encrypting the phone does not work; solved by resizing /data via TWRP.
Long story
I installed LineageOS on a Wileyfox Swift running the stock Android 7.1.2, I followed the wiki wiki_dot_lineageos_dot_org/devices/crackling/install but I had to solve a couple of issues that were not documented there. Before proposing any changes to the wiki, I would like first to understand if the issues are well known and what causes them.
Issue 1: TWRP complains about /system partition being formatted with the squashfs filesystem
Following the wiki, at wiki_dot_lineageos_dot_org/devices/crackling/install#installing-lineageos-from-recovery, step 5 says:
...tap Advanced Wipe, then select the Cache and System partitions and then Swipe to Wipe.
Click to expand...
Click to collapse
here TWRP complains about the partition /system being formatted as squashfs. The problem does not permit a successful sideloading of LineageOS, and the solution seems to be formatting the partition with the filesystem ext4.
Questions:
Is it common to have the partition /system with squashfs filesystem? Or is it only the Swift having it like this?
TWRP complains about it just because it does not support squashfs? Or are there other reasons?
Do other recoveries support the squashfs filesystem?
Issue 2: LineageOS 16 is unbootable if sideloaded on stock Android 7.1.2
If sideloading LOS 16 on stock Android 7.1.2, the phone only reboots at fastboot. I found some possible solutions at www_dot_reddit_dot_com/r/LineageOS/comments/9pcgrh/cant_start_lineage_stuck_at_fastboot/: downgrading first at CyanogenOS, or installing crDroid, or using the FoxyKernel. As per the discussion, the problem looks like being the 'new bootloader'. I tried downgrading first to CyanogenOS, which should have installed the 'old bootloader', and it solved the problem.
Questions:
When was the 'new bootlaoder' introduced (Wileyfox Android 7?) and what is wrong with it?
Does the problem lies at kernel level? If so, only crDroid and FoxyKernel have the required changes?
Issue 3: Encrypting the phone fails because of something wrong with the /data partition
After a fresh installation and first configuration of LOS, encrypting the phone just fails: the phone shows a black screen, it flashes the main screen after every few seconds, then it reboots after an hour or so without being encrypted at all. The solution is suggested at gitlab_dot_com/LineageOS/issues/android/-/issues/700: to perform a filesystem resize of the /data partition via TWRP.
Questions:
What is wrong with the /data partition after following the LOS installation procedure?
What does the TWRP filesystem resizing actually do? I don't think it increased/decreased the /data partition at all!
And bonus question: Did someone else experienced the same issues? Are they known?
Had issue 2 once, found a workaround thanks to @beroid, https://forum.xda-developers.com/showpost.php?p=66158015&postcount=2 can't answer precisely your question unfortunately.
The official OS messed with the file systems when they went from the original CyanogenOS based Android 6 to whatever they used for 7 with the Russian launcher
Helllo,
I tried to root my Samsung A5 2017 and also too change to LineageOS. I installed TWRP. In TWRP I selected my Lineage-Zip and OpenGApps-Zip. TWRP finished the installation succesfully. When I startet the phone, Lineage said, that it isn`t working. Now i flashed the StockROM with Odin and Android worked again. I flashed TWRP a second time and tried to wipe the Phone. This doesen´t works. Log says: "Unable to mount storage" "Failed to mount ´/data´(Invalide argument)". Then I tried to install Lineage without wiping, but the Log brought the same result.
Thank you for any help.
First of all, I think your thread belongs to the Q&A section.
To answer your question, or try at least, I'm guessing that the storage is encrypted by the Samsung stock ROM. This encryption sadly can't be removed in any other way than completely formatting the data partition.
You can do this in TWRP in the "Wipe" section with "Format data". This will also wipe your internal storage, so you should have all the important zips for installation on a microSD card or your PC, so you can install them after the wipe (I'm guessing you already did that, since you installed without having access to /data).
If you want to keep the data partition unencrypted in the future but still use the stock ROM, you can flash Magisk after removing the encryption.
Hope I could help.
In short, I installed a Vyper Os V6.1 custom rom and ended up encrypting the sd card through TWRP 3.5.1.9.2, in a way that only serves to read files. When I tried to decrypt the SD through TWRP, I went straight into the dev/block folder and renamed the "mmcblk" file "from 0 to 1"; and that generated the hard brick in my moto g5 xt1672 cedric.