Hi, I recently upgraded from Lineage 16 to 17.1 and now wifi is off and when I turn it on phone reboots but wifi is still off, location no longer works, camera flash is not working. I have looked online to try to find out what may have caused this and it seems from what I've read that TWRP has corrupted the callibration data in the persist partition. I have updated TWRP to 3.4.0-0 but I am not sure how to proceed to fix the issue. IE: Do I format and reflash 17.1 or does the persist partition need to be repaired first. Any help on how to fix this would be appreciated. Thanks in advance.
Related
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 guys, i'm stuck in Rock and a hard place here and couldn't figure this one out. I've installed CyanogenMOD previously but that was a while ago and different process. What happened is I installed LineageOS 2 days ago and everything worked fine except No Sim Card is detected so I can't make phone calls and log into my Google account to sync.
Hence to resolve the Sim Card issue, what i did is to attempt to flash Bootloader, System , Radio images but it didn't work when i try to flash and also install LineageOS zip file. And in order to try resolving Mount issue, I proceed to Advanced Wipe -> checked System, Data, Cache -> Repair and Change File System -> changing ext4 to ext 2 . This formated all my User data which includes the ROM zip file i needed to install and load. I tried using Nexus Root Toolkit to restore into stock but it says no Fastboot/ ADB detected. And my computer couldn't detect my Nexus 6p.
Please provide solutions. Desperate here.
@Psuche To fix the no sim bug in Oreo you simply turn off lockscreen security once and reboot. Your phone is probably boogered because you switched to a filesystem the 6p isn't compatible with. Similar thing happened to me switching to f2fs without compatible kernel. So hopefully if you have and can still boot into twrp can repair filesystem in there back to EXT4. Obviously selecting ExT4 instead of F2FS.
Exodusche said:
@Psuche To fix the no sim bug in Oreo you simply turn off lockscreen security once and reboot. Your phone is probably boogered because you switched to a filesystem the 6p isn't compatible with. Similar thing happened to me switching to f2fs without compatible kernel. So hopefully if you have and can still boot into twrp can repair filesystem in there back to EXT4. Obviously selecting ExT4 instead of F2FS.
Click to expand...
Click to collapse
Thank you for replying Exodusche. But i have switched back to EXT 4 and finds the system formatted and user data deleted! Plus my computer is unable to recognize my phone while i'm stuck at Bootloop =( Talk about difficult situations. So i'm unable to test your no sim solution at this point. Need to retrieve deleted files or at least push files from Desktop to Phone.
Any ideas?
Hey guys.
Sadly the screene of my 6T broke and i have sent it to repair.
Tomorrow it should come back from repair and the service center has replaced my screen (not the mainboard -> nothing else).
I have readed that the erasing the whole phone and i have to set it up again
Luckily, i did an TWRP backup a few days before the screen died.
My setup was:
OOS 9.0.11 or 9.0.12 (cant remember, hope this isn't an issue on restore)
Face unlock & fingerprint was active
Magisk 18.1 with ~1 module, mainly for root
adaway
My thoughts are:
Boot the repaired phone and make all OTAs
Unlock bootloader
flash TWRP
restore backup
hope it boots up
Whats the recommended way to restore my TWRP backup?
Do you think that works also with faceunlock & fingerprint?
Are this data stored on the /data/ partition ttoo -> included in TWRP backup?
Thanks a lot
pOpY
popy2006 said:
Hey guys.
Sadly the screene of my 6T broke and i have sent it to repair.
Tomorrow it should come back from repair and the service center has replaced my screen (not the mainboard -> nothing else).
I have readed that the erasing the whole phone and i have to set it up again
Luckily, i did an TWRP backup a few days before the screen died.
My setup was:
OOS 9.0.11 or 9.0.12 (cant remember, hope this isn't an issue on restore)
Face unlock & fingerprint was active
Magisk 18.1 with ~1 module, mainly for root
adaway
My thoughts are:
Boot the repaired phone and make all OTAs
Unlock bootloader
flash TWRP
restore backup
hope it boots up
Whats the recommended way to restore my TWRP backup?
Do you think that works also with faceunlock & fingerprint?
Are this data stored on the /data/ partition ttoo -> included in TWRP backup?
Thanks a lot
pOpY
Click to expand...
Click to collapse
Only restore data and apps.
No need to restore the full ROM.
I never restore ROM. You can flash that clean.
Thanks for your suggestion.
Sadly something went wrong on restore of data, see the complete story here: https://forum.xda-developers.com/showpost.php?p=79120819&postcount=2233
pOpY
running rom after twrp restore after installation.
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
I have PE 10 in my phone (just updated it) and I am now having problems with the proximity sensor not working right. I found out that those problems happen because the persist partition is corrupted. But I don't want to take the chance of flashing the stock image onto my device through fastboot and then having a bricked phone unless it is absolutely neccesary. Any way to find out what's in the title? Any help would be extremely appreciated.