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
Related
OK some background here. I was running CM 11 nightly and had encrypted my device. Today i decided to flash my device to CM12 and hence went into recovery. When I tried to do a clean wipe it gave me errors because my data is encrypted. I did some research on google and i found solution to it. I dont know what came to my mind but for some reason I ran this command without thinking much.
Code:
mke2fs -t ext4 /dev/block/mmcblk0p12
This snippet is from the link given above.
I usually never do something foolish like this without enough research.
Now my device mounts on the PC as if it's an external drive rather than a tab. I can see all the partitions mounted when I connect it to the PC. It won't boot into recovery or bootloader. Am lost. Can someone please guide me as to what are the probable solutions to this?
When I opened GParted and saw the partitions of my device it shows that no partition table exists. I think that's what the main issue is. Can someone guide me as to what I can do to restore or rebuild the partition table?
I had come across this bug in TWRP recovery where the /system partition was unable to mount.
And i wasn't able to flash any new ROM or even backup current ROM.
Hopefully I had another ROM backed up before and I simply formatted the system and VIOLA! the problem was gone.
I posted this for anyone who might get such a problem in the future and doesn't end up cursing themselves.
Its a common bug and very easy to fix. So, Happy Flashing!
This basically work for any partition not mounting error.
Hit thanks if it helped
Help me fix my twrp
Pls, I have been on this platform for some time now. I have a challenge presently with my phone Tecno LB8A. I have been trying to upgrade it to version 10. I have unlocked the bootloader, rooted it and also flash twrp into it. I downloaded Lineage 17 and havoc but I bricked my phone severally. In twrp, I discovered there is no system partition there. Pls I need your guide on how to make the system appear. What I have on the partitions there are: dalvic cache, cache, data,sdcard, otp and internal storage. The second question bis how do I flash Lineage into it without bricking the phone
I've recently updated my htc 10 to Android 7.0 using the 2.38.617.6 firmware and added twrp to use for backup purposes. I have attempted to root the device with chainfire's supersu, but failed due to data being in the wrong format.
First off, I managed to find out the the system partition is ridiculously large (17,592,186,044,365 MB) leading me to believe that the system partition has been corrupted.
I've checked the format type for each partition (data, system and cache) they check out to be ext4.
As the title of the post states, I've also ran into that problem before the system partition size issue.
Also, when trying to reboot the system through twrp, I get the message, "No OS Installed! Are you sure you..." but the phone boots up just fine.
Any help is appreciated.
ensure you flashed the latest unoffical twrp from the xda twrp thread. not the official one.
j to the 4n said:
ensure you flashed the latest unoffical twrp from the xda twrp thread. not the official one.
Click to expand...
Click to collapse
I have fixed the issue. I had to find and flash the latest ruu because I had restore the /data partition from when I had the phone rooted and downloaded xposed. I ran through the same process after the flash without restoring the data partition and now it work.
Only downside is that I can't restore my data until xposed has a compatible framework. Thanks for replying.
I got a clean backup of the twrp formatted the sd card with external memory I mounted the backup in the external sd and restored the system .... With that I was successful:dedos cruzados::dedos cruzados:
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
I think the decryption key is somehow embedded into the internal storage as wiping /data does not delete the PIN/pattern. Might be a hidden partition or something similar that is not wiped when wiping /data as long as it is ext4.
Your data is gone. It failed to completely encrypt and now there's nothing that can be done. Format /data as ext4 and let it try encrypting again
I have the same problem exactly. Can you explain in steps you have installed then format or how?
I have the same problem exactly. Can you explain in steps you have installed then format or how?
Click to expand...
Click to collapse
I had the exact same problem. But it is an easy fix but does require wiping your internal storage.
So the save way of doing this would be:
1. Backup all your data by going to TWRP or your ROM if that still works. Plug in an USB cable and use MTP or the adb pull command to backup your data
2. Reflash OB1 with no root (like Magisk of SuperSU) if you have TWRP. This will cause you to have the stock recovery again. I also recommend to do a clean flash (Wiping system and data before flashing the rom).
3. Download the rollback build from Oneplus [HERE] and copy this to the internal storage.
4. Boot into the stock recovery flash the rollback build. THIS STEP WILL WIPE YOUR INTERNAL STORAGE.
5. Now you have OxygenOS 4.7.5. Download OxygenOS 4.7.6 Incremental Update [HERE]
6. Go back to the Stock recovery and flash the incremental 4.7.6 zip.
7. You have the latest version now. So boot to fastboot reflash TWRP and flash SuperSU or Magisk in TWRP to regain root
Guys I did a fail, i had OB3 installed, and I wanted to try RR so I wiped system and when I tried to install I have seen error 7 saying its for dumpling not for oenplus5t.
So I restored.... But instead restoring OB3 I have restored stock Nougat rom -.- I have even stock recovery now, what is the best way to fix it?
Can i change to FAT and stay and dont go back to ex4 again?
Hi i don't know if u r reading this but if you are please help me cause I'm so lost and confused over this since yesterday...
so 2 days ago my phone started lagging and hanging and freezing until i realized i have got this issue with data encryption
i have a rooted sony z2 with TWRP Custom recovery
first i didn't know it was with data encryption failure so i literally factory reset and installed all my apps and data again and again!!! after every time my phone started to lag !!
after one whole day of trying everything i finally realized its actually with the data encryption and i should change my ex4 to something else... so here again i wiped the phone and changed to ex3 and installed and all my data and apps all over again
but after a couple hours...same problem again.....
im literally so tired of not knowing what to do ! my head hurts so much due this ugh....
i havent changed to FAT from ex3 so im wondering if it will finally solve my problem permanently if i change to FAT ??
And if it did can i just keep it on FAT forever ?
Please guide me thanks ...!
Lasersdude said:
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
Click to expand...
Click to collapse
Finally. Thank you so much!
Hi! I've got lineage 14.1 and I want to format /data as ext4 to avoid flashing the f2fs module since I install a lot of modules and it exceeds the size of /cache resulting in a bootloop. I also installed Valyrian kernel and everything works almost flawlessly except the camera, it is not showing
in the app drawer and I cannot open it. It's installed but it doesn't open . And also the torch isn't working ( I think it's related to the camera app that doesn't work). The question is: can I format /data as ext4? Does the ROM start?
Sorry if it seems a noob question, but I don't want to brick it, it's my primary device. Thanks in advance.
Edit: delete post