Hi, I'll try to be as detailed as possible but just know that I am somewhat of an amateur with android and I only have surface level knowledge.
I have an Axon 7 that I successfully installed OrdenKrieger's unofficial LineageOS 16.0 a few months ago (build 20181114). I saw recently that there was a new build so I booted to TWRP to flash it, but found that I could not access my file system. I am able to select (in the mount menu) system, cache, and persist, but not data. I then tried to reformat my data based on a thread I found, but then I booted back to TRWP the same problem was still there.
If anyone could help me solve this it would be very much appreciated. I have a few other problems too with root installation and dac selection, but this I am just not able to figure out why is happening.
I am on a vendor partition, but I do not remember which tool I used, just that it was one of the first to come out after Lineage 16 was released for the Axon 7. My TWRP version is 3.3.1-0 and I am not sure which bootloader/modem I installed either.
Maybe try reformating/changing your vendor partition size
I have the same problem, installed LOS 16.0 recently and TWRP is unable to mount internal storage. Anyone have a fix for this? Have tried flashing the latest TWRP via fastboot but didn't help
Related
Sorry ppl, need some spoon feeding. I have searched but to not avail.
I unlocked my 6p, flash TWRP and installed chroma rom + despairs kernel. All was fine in TWRP
But when I boot into the TWRP after installing my apps, it says password to decrypt and I skip that but allowing it to mod system files. Tried to install zip but internal storage shows 0mb. Can't seem to find my files in SD card folder
My phone is still encrypted.
Never experienced such issues with my nexus 6. Any help?
Chroma works perfectly
Make sure you have the latest version of TWRP for the 6p. Initially it only worked if you decrypted, but a few weeks ago a newer version was released that does not require decryption and will see your files.
Here is a quick review of what happened:
The phone was running well on Lineageos 14.1, encrypted with a pattern, with TWRP 3.1.1 as recovery. I’ve then been notified of an LOS update to 15.1 Oreo and got excited. Booted in recovery, entered my pattern to decrypt, took a full TWRP backup, flashed Oreo modem and firmware and dirty flashed (I know, bad idea) the LOS 15.1 zip.
It got stuck at boot logo. Even if I didn't have high expectations for it to work I just thought I would try the lazy way to see and use my fresh backup to restore in case of failure like I always did successfully since my Nexus One.
This time was different because as I rebooted in TWRP to restore, it didn't ask for my pattern. You guessed it, the data partition is encrypted, no access to my backup or anything on the external storage. I can mount data and see the weird encrypted file names but that's it. I tried different version of TWRP, but it never ask the pattern. Even the terminal command 'twrp decrypt *******' doesn’t work.
I then tried to wipe data and flash LOS 14.1 again but it gets stuck saying that android has no access to data partition because it’s encrypted and that I need to format. I pulled out my sim card and started to use my old oneplus one while waiting for the new version of TWRP 3.2.1.1 with the feb security patch support thinking it might then be able to decrypt but no luck still.
I can go without the phone for a while, I’ll buy another one if I have to because there is some precious data on that phone and I can’t make my mind that the data is there, I know the encryption key but I have no access to it. There must be a way, I just don’t have enough knowledge about how this encryption thing is working.
Any help would be appreciated, Thank you
jpitou said:
Here is a quick review of what happened:
The phone was running well on Lineageos 14.1, encrypted with a pattern, with TWRP 3.1.1 as recovery. I’ve then been notified of an LOS update to 15.1 Oreo and got excited. Booted in recovery, entered my pattern to decrypt, took a full TWRP backup, flashed Oreo modem and firmware and dirty flashed (I know, bad idea) the LOS 15.1 zip.
It got stuck at boot logo. Even if I didn't have high expectations for it to work I just thought I would try the lazy way to see and use my fresh backup to restore in case of failure like I always did successfully since my Nexus One.
This time was different because as I rebooted in TWRP to restore, it didn't ask for my pattern. You guessed it, the data partition is encrypted, no access to my backup or anything on the external storage. I can mount data and see the weird encrypted file names but that's it. I tried different version of TWRP, but it never ask the pattern. Even the terminal command 'twrp decrypt *******' doesn’t work.
I then tried to wipe data and flash LOS 14.1 again but it gets stuck saying that android has no access to data partition because it’s encrypted and that I need to format. I pulled out my sim card and started to use my old oneplus one while waiting for the new version of TWRP 3.2.1.1 with the feb security patch support thinking it might then be able to decrypt but no luck still.
I can go without the phone for a while, I’ll buy another one if I have to because there is some precious data on that phone and I can’t make my mind that the data is there, I know the encryption key but I have no access to it. There must be a way, I just don’t have enough knowledge about how this encryption thing is working.
Any help would be appreciated, Thank you
Click to expand...
Click to collapse
Try flash codeworkx TWRP ...
it should decrypt your data partition ...
https://downloads.sourceforge.net/project/cheeseburgerdumplings/15.1/cheeseburger/recovery/twrp-3.2.1-0-20180309-codeworkx-cheeseburger.img?r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fcheeseburgerdumplings%2Ffiles%2F15.1%2Fcheeseburger%2Frecovery%2F&ts=1521806282&use_mirror=netix
PS-DEV said:
Try flash codeworkx TWRP ...
it should decrypt your data partition ...
https://downloads.sourceforge.net/project/cheeseburgerdumplings/15.1/cheeseburger/recovery/twrp-3.2.1-0-20180309-codeworkx-cheeseburger.img?r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fcheeseburgerdumplings%2Ffiles%2F15.1%2Fcheeseburger%2Frecovery%2F&ts=1521806282&use_mirror=netix
Click to expand...
Click to collapse
I had tried it when it came out and I just tried it again. No difference!! It looks like twrp doesn't even see that my phone is encrypted. I've read a lot and tried many different things and I'm out of idea. All of the people I've seen with this problem have given up so they could get their phone back and running by formatting the partition, losing their data. This option is not one for me. I'd rather buy a new phone hoping for an eventual possible solution. I know the data is there, and I know the pattern key...... I mean, there's got to be a way......
Hi folks,
I need some help. I have had my X820 I ordered from bangood for about a month now. I have tried a variety of ROMs on this device, and twrp-3.2.1-0-x2.img. This morning I tried to give the latest lineageOS a try. I did the typical wipes, and flashed lineageOS & gapps. After reboot google play started to throw all types of errors.
I booted back into TWRP, and this time it would only mount in read only. I tried the trick to change the /data partition fron ext2 back to ext4, did wipes again, installed ROM + Gapp, reboot but still have crashing playstore and google background processes.
I went from an already installed AICP to LOS. I did do a complete TWRP backup of AICP beforehand. The weird thing is that if I do a complete wipe again from TWRP, and do a fresh install of Pixel Experience [AOSP] all works normally. And after I did another wipe from TWRP after Pixel Experience, and restored my AICP backup all is working fine now both in TWRP & AICP. Has anyone had something simular happen like this before?
You have to install the latest unofficial TWRP build in order to use see your /data partition with the latest LineageOS installed. It's indicated on the thread's FAQ.
So I am trying to upgrade my version of LineageOS from 14 to 15.1. I was having problems because my phone didn't have the '/vendor' partition. I heard that re-installing OxygenOS will mount '/vendor' so that's what I tried to do. However, I was still getting the error about not having '/vendor' mounted, so I tried using a version of TWRP that removed the check for '/vendor'. Unfortunately, I still could not install OOS. Then, I tried to just flash updated firmware for my phone, which should install the '/vendor' partition, but now I am stuck on the Lineage loading screen.
When I boot back into recovery, TWRP does not ask me for my phone password, and all the files are encrypted (or hashed, or whatever). This could be a problem for my phone loading?
walker_flocker said:
So I am trying to upgrade my version of LineageOS from 14 to 15.1. I was having problems because my phone didn't have the '/vendor' partition. I heard that re-installing OxygenOS will mount '/vendor' so that's what I tried to do. However, I was still getting the error about not having '/vendor' mounted, so I tried using a version of TWRP that removed the check for '/vendor'. Unfortunately, I still could not install OOS. Then, I tried to just flash updated firmware for my phone, which should install the '/vendor' partition, but now I am stuck on the Lineage loading screen.
When I boot back into recovery, TWRP does not ask me for my phone password, and all the files are encrypted (or hashed, or whatever). This could be a problem for my phone loading?
Click to expand...
Click to collapse
Have you used latest blu spark or codeworkx recovery with vendor partition support? Also mounting the created vendor partition within twrp might be necessary after flashing stock oos and proceed further.
I’ve just picked up a new Samsung Galaxy Tab s6 Lite and installed LineageOS on it. I’m using TWRP 3.5.0.
All was working great until today. I was using LineageOS 17.1 nightly 20210310 and had OpenGApps installed.
Today an update was available for Lineage so I updated using the Setup app. The upgrade went well but killed GApps.
I decided to do a fresh flash. I was having a problem with Android Audio which appears to be caused by OpenGApps. I’ve read that NikGApps doesn’t have this problem.
I copied the latest Lineage zip and NiksGApps zip to the device using ADB and booted into recovery. I used advanced wipe to remove the existing install. I’m only seeing options to wipe dalvik/ART Cache, Metadata, cache, data, internal storage, micro sd card, and usb otg. There is no system option. I wiped dalvik, metadata, cache, and data. I successfully flashed both Lineage and NiksGApps.
When I booted I found a very unstable system. Google services and apps crashed all the time.
I used the Format Data option this time followed by a wipe of the same four partitions. I rebooted back to recovery and installed LineageOS again. During the Lineage flash NiksGApps were backed up and restored. This surprises me. How could the data be available for backup after a format?
I’ve reflashed multiple times. I’ve tried both 17.1 and Linux4’s unofficial build of 18.1. I’ve tried OpenGApps and NiksGApps. I can’t get a stable install. I have had several flashes that wouldn’t even boot (booted into recovery). I'm currently in a non-booting state now.
Am I doing something wrong? Is there something wrong with TWRP? Should I use Lineage Recovery?
Thanks,
Bob
bdushok said:
I’ve just picked up a new Samsung Galaxy Tab s6 Lite and installed LineageOS on it. I’m using TWRP 3.5.0.
All was working great until today. I was using LineageOS 17.1 nightly 20210310 and had OpenGApps installed.
Today an update was available for Lineage so I updated using the Setup app. The upgrade went well but killed GApps.
I decided to do a fresh flash. I was having a problem with Android Audio which appears to be caused by OpenGApps. I’ve read that NikGApps doesn’t have this problem.
I copied the latest Lineage zip and NiksGApps zip to the device using ADB and booted into recovery. I used advanced wipe to remove the existing install. I’m only seeing options to wipe dalvik/ART Cache, Metadata, cache, data, internal storage, micro sd card, and usb otg. There is no system option. I wiped dalvik, metadata, cache, and data. I successfully flashed both Lineage and NiksGApps.
When I booted I found a very unstable system. Google services and apps crashed all the time.
I used the Format Data option this time followed by a wipe of the same four partitions. I rebooted back to recovery and installed LineageOS again. During the Lineage flash NiksGApps were backed up and restored. This surprises me. How could the data be available for backup after a format?
I’ve reflashed multiple times. I’ve tried both 17.1 and Linux4’s unofficial build of 18.1. I’ve tried OpenGApps and NiksGApps. I can’t get a stable install. I have had several flashes that wouldn’t even boot (booted into recovery). I'm currently in a non-booting state now.
Am I doing something wrong? Is there something wrong with TWRP? Should I use Lineage Recovery?
Thanks,
Bob
Click to expand...
Click to collapse
It's very likely caused by TWRP, I said multiple times to NOT use TWRP for installing OTAs exactly because of things like this.
TWRP is now discontinued anyways