Previously I was using LineageOS 18.1, then I tried to revert to MIUI. I wiped Dalvik, Cache and Data. I was going to install the ROM from storage, but the storage appeared to be encrypted. So I restarted the phone, LineageOS reset but cannot access local storage. However, the system works.
Can I delete the encrypted partition and reinstall the ROM? I still want to use LineageOS
Related
This started happening with a working RR android 7.1 ROM I have used for several days. Today, I wanted to try out LineageOS 14.1 so I made a nandroid backup of data and internal storage. When I rebooted into RR the screen was flickering and a message constantly popped up stating that com.android.phone stopped and Calendar stopped and com.android.media stopped etc etc.
So I went on and did a full clean flash
I tried t remove my sim and the clean flash but to no avail. I do advanced wipe --> Dalvik/ART cache, System, Data, Internal Storage, and Cache before every flash today. Then i flash ROM and latest gapps, wipe cache/dalvik and reboot.
Even without flashing gapps, the problem is still there.
Running on TWRP 3.0.0 (worked for several days on RR android 7.1 ROM), but tried on 3.0.2-2, 3.0.2, and 3.0.1 with the same results.
How did this happen? Is my EFS and IMEI f'ed because of the nandroid backup of data and internal storage?
How do I fix this?
Kind regards and a happy new year!
Same here. Twrp is the culprit, I'm afraid. It isn't taking good backups. Just fresh install RR and download all your apps, it'll work. Can't wait for twrp update...
i needed to format system to ext 4 and now everything works!
Hi there, I have an Axon 7 with LineageOS that was working like a charm until I rebooted it today. It was in the normal lineage OS boot animation with the blue circle moving from right to left, except it never stopped. Now after trying a few more times, it just keeps playing the animation except the phone will vibrate slightly every several seconds. The phone is encrypted but that hasn't been a problem. When I reboot to TWRP, it says Unable to mount storage.
I tried wiping Cache and Dalvik / ART Cache, but this didn't help. Finally, I do have a backup from 7-20-2017 but I'd rather not have to go back to that...
Any recommendations?
Chrono7x said:
Hi there, I have an Axon 7 with LineageOS that was working like a charm until I rebooted it today. It was in the normal lineage OS boot animation with the blue circle moving from right to left, except it never stopped. Now after trying a few more times, it just keeps playing the animation except the phone will vibrate slightly every several seconds. The phone is encrypted but that hasn't been a problem. When I reboot to TWRP, it says Unable to mount storage.
I tried wiping Cache and Dalvik / ART Cache, but this didn't help. Finally, I do have a backup from 7-20-2017 but I'd rather not have to go back to that...
Any recommendations?
Click to expand...
Click to collapse
So you can't see the internal storage from TWRP? I'm guessing encryption actually plays a part here. Formatting data is probably the best course of action, though you should flash magisk or superSu if you do, to get rid of encryption. But you obviously lose everything that's on the internal storage.
Maybe make a system and boot backup and clean flash Lineage. Like, wipe system and caches, then flash the bootloader, modem, LOS and whatever else you flash
Choose an username... said:
So you can't see the internal storage from TWRP? I'm guessing encryption actually plays a part here. Formatting data is probably the best course of action, though you should flash magisk or superSu if you do, to get rid of encryption. But you obviously lose everything that's on the internal storage.
Maybe make a system and boot backup and clean flash Lineage. Like, wipe system and caches, then flash the bootloader, modem, LOS and whatever else you flash
Click to expand...
Click to collapse
Is it easier to just use the backup I have currently? If so, what are the steps necessary for that (sorry for newb questions, haven't messed with it in a while)
EDIT: Also, TWRP claims decryption is successful when it is loading up.
Chrono7x said:
Is it easier to just use the backup I have currently? If so, what are the steps necessary for that (sorry for newb questions, haven't messed with it in a while)
EDIT: Also, TWRP claims decryption is successful when it is loading up.
Click to expand...
Click to collapse
Again. Can you see the internal storage?
Don't restore the backup. Your problem is basically either on /system (clean flash of the ROM will do) or on /data (complete format of data is needed). So try the non destructive one first
Choose an username... said:
Again. Can you see the internal storage?
Don't restore the backup. Your problem is basically either on /system (clean flash of the ROM will do) or on /data (complete format of data is needed). So try the non destructive one first
Click to expand...
Click to collapse
I don't see any storage folder. So if I want to install the latest LOS and frankly just start from scratch, can I follow the guide here https://wiki.lineageos.org/devices/axon7/install#installing-lineageos-from-recovery starting from "Installing LineageOS from recovery"? Will I still need to install something to wipe the encryption?
Chrono7x said:
I don't see any storage folder. So if I want to install the latest LOS and frankly just start from scratch, can I follow the guide here https://wiki.lineageos.org/devices/axon7/install#installing-lineageos-from-recovery starting from "Installing LineageOS from recovery"? Will I still need to install something to wipe the encryption?
Click to expand...
Click to collapse
What? No... That's for normal phones. How did you manage to install LOS without knowing that you need the univ. bootloader and modem?
So, you can't access the internal storage via the file manager on TWRP i'm guessing.
Wipe - Format data, after that flash the Universal bootloader, modem, LOS, Magisk, GApps. Magisk takes care of dm-verity and disables encryption. Don't try to uninstall it though or your internal storage will get encrypted as soon as you do. But if you want to change ROMs you can just fpash it before booting and it won't ger encrypted.
My phone is X720, and I have flashed DotOS based on android 8.1.0 before. Now I want to return to Android 7.1.2, but I can't flash the ROM after I wipe system, data and cache. It said "failed to mount /dev/block/bootdevice/by-name/userdata at /data: device or resource busy". I can't restore the TWRP backup of my omni based on android 7.1.2. After restoring and rebooting, it said "encryption unsuccessful"...
What should I do? Thank you very much!
I did that too, after many oreo roms, each with goods and bads, I come back to omni 7 cause it works fine.
You have to search and download the all in one tool by manforio and erase/decrypt storage after makeing a full storage backup of the phone.
It will erase everything. After that just install a stock firmware and whatever rom you want. I installed an older version of twrp to be sure it works. I think it was 3.2.1.1
if you didn't do a backup of the storage, install an oreo rom make the backup and then erase it.
The simple answer is format your storage, reboot to recovery, advanced wipe> system, data, cache, dalvik. now flash whatever you want. Warning about Omni it may be good, its kernel will destroy your battery, change the kernel and you're fine.
Note: Originally posted in the official TWRP thread. I apologise for double posting.
So I did something profoundly stupid today.
I've been having trouble with my N9005 for a few days now. For some reason, having just woken up, I decided to try and wipe Dalvik cache from TWRP 2.8.7.0 4.4 (this is my maximum TWRP version at the moment due to a bug in certain N9005's that's been discussed elsewhere in this thread). TWRP was also giving me issues, asking repeatedly for my password and not accepting it. Unfortunately, in this state I ended up also swiping the Install SuperSU slider -- problem because I was running Magisk with RR 5.8 up until then.
This led to an expected bootloop.
I've flashed RR again after doing a factory reset, but I'm afraid that I may lose my encrypted internal storage, which (surprise surprise) contains a lot of stuff that should have been backed up but hasn't been. Neither TWRP nor RR recognize an encrypted portion of the internal storage, although RR shows a few GB of space occupied.
When I run
Code:
twrp decrypt <password>
I get
Code:
Failed, operation in progress
Additionally, in mount internal storage is left unchecked by default and checking it does nothing.
Is there anything that I can do at this point? I don't know which /dev/block would correspond to the data, and don't know what tools I would use to decrypt these files if I copied them over using ADB.
Any assistance would be incredibly appreciated!
TL;DR: I had encrypted internal storage. After a factory reset it doesn't show up in RR or TWRP. I need to know if this data is still there, and if so how to extract it.
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