Hi all,
I have a rooted moto G5 plus with TWRP, Magisk, and dotOS. Everything worked fine until the other day when the phone got stuck on the boot image (the phone ran out of battery over night). I was wondering if there is a way to go past this without loosing any data (including app messages such as in signal, etc), perhaps by fixing it from the TWRP terminal (e.g. replacing a corrupted file).
Any help/suggestion is appreciated.
I am making progress: I wiped the device, re-flashed dotOS + GAPPS, and then replaced /data with the old /data. Next I had to delete roles.xml and runtime-permissions.xml in /data/misc_de/0/apexdata/com.android.permission/. Now the device goes past the boot image; however, it doesnt recognize the pattern password. Is there a file from the old tree I should reinstate for the old password to work, or is there a file I can delete to get around this?
Thanks!
edit: I am doing this through adb in recovery mode (TWRP)
It's alive! I had to delete locksettings.db, locksettings.db-shm, and locksettings.db-wal from /data/system (infor here) and it worked. Everything seems to be there and working, that was a close call, backing up right now
Related
[unnecessary background information] A while back I decided to encrypt my OnePlus 2 - mostly to compare its performance with my Nexus 6P, which is also (obviously) encrypted. Today I decided I was tired of Oxygen OS and wanted to install CM13 since Grarak had gotten the fingerprint scanner working properly. I went ahead and unlocked the bootloader, installed TWRP 3.0.0.2, and excitedly flashed the shiny new OS (without making a backup, like an idiot)[/]
After booting up into CM13 the system asks me for my encryption key (sure, whatever) and then I get this big screen that says "Decryption Unsuccessful....The password that you entered is correct but unfortunately your data is corrupt" and goes on to say that a factory reset will fix the problem and any lost data can be re-downloaded from the cloud. I said "great!" and hit the "reboot now" button that reboots back into TWRP, runs a short script, and sends me back to where I started (presumably not on purpose).
Now, I tried doing a full wipe of the entire device via TWRP, which sent me into a new panic mode when I couldn't manage to get any files to transfer over when I tried to send them over MTP - I finally went about using the ADB Sideload feature in TWRP to once again install the same (and a different) ROM all of which garnered the same result.
Finally, the point of the story: Is there a way for me to fully remove encryption from the system from within TWRP? If not, am I totally hosed or does someone have another idea? Frankly, I'd be happy to just have a booting phone at this point.
Thanks in advance!!
So following up on my own thread, I found the setting in TWRP that specifically allows you to erase the data partition (something that I thought I had done when I did a standard wipe and/or when I did the advanced wipe and specifically told it to wipe everything) and rebooted and it finally booted happily into Android. I'm not sure if this is a bug in TWRP or a bug in CM's script that is causing issues but something isn't quite right.
I have rooted a Oneplus 6T with TWRP and Magisk. No problem. Today I uninstalled one system app I shouldn't have. Own stupidity, I know
On reboot the device is stuck on the Oneplus boot animation screen which never finishes. So I rebooted into TWRP. Current active slot is B. That is probably because I installed a system update before. In TWRP, I switch to slot A and reboot to system. However, I am thrown back into TWRP. I can keep changing slots and the behavior is the same. Slot A boot loops to TWRP, slot B shows the Oneplus boot animation forever.
Any ideas how to proceed?
The uninstaller app has made a backup of the uninstalled app but that is probably useless without successful boot since the partition is encrypted.
On TWRP start I select the read-only mode. Do I need to allow it to make modifications to successfully boot from slot A?
Is there a boot log I can check (like dmesg etc)?
deeepce said:
I have rooted a Oneplus 6T with TWRP and Magisk. No problem. Today I uninstalled one system app I shouldn't have. Own stupidity, I know
On reboot the device is stuck on the Oneplus boot animation screen which never finishes. So I rebooted into TWRP. Current active slot is B. That is probably because I installed a system update before. In TWRP, I switch to slot A and reboot to system. However, I am thrown back into TWRP. I can keep changing slots and the behavior is the same. Slot A boot loops to TWRP, slot B shows the Oneplus boot animation forever.
Any ideas how to proceed?
The uninstaller app has made a backup of the uninstalled app but that is probably useless without successful boot since the partition is encrypted.
On TWRP start I select the read-only mode. Do I need to allow it to make modifications to successfully boot from slot A?
Is there a boot log I can check (like dmesg etc)?
Click to expand...
Click to collapse
This is OnePlus 6 forum, but you need a full OOS zip file to flash and it will work. Flash oos, then TWRP, then reboot recovery and flash any other mods (if any) or just reboot after flashing TWRP.
Thanks. You have restored some hope I might be able to recover while keeping my data and settings. I am not yet sure how to flash the OOS zip (which I have downloaded). TWRP cannot decrypt the storage, so I cannot upload the zip to the device. I suspect I have to go back to the stock fastboot.
Anyhow, I have asked about this on the 6T forum: https://forum.xda-developers.com/on...4-ota-oneplus-6t-t3860953/page20#post78198874
Alright. Solved it by
wiping cache & system in TWRP
"fastboot flashall" with images from https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Then had to flash twrp and sideload magisk, as you said.
It even preserved all apps and settings and the lock code. I am not yet sure where this is stored. Data partition? Anyhow, it survived. Which saved me from the hassle of finetuning all settings etc again.
Hi Guys,
I unlocked the bootloader and flashed twrp following this tutorial - https://www.youtube.com/watch?v=tRcYUMBgvaI
I was getting an error while flashing a custom rom and gapps. It showed "storage space is insuffient". So I wiped internal storage and did a factory reset also.
After that I copied all the files (rom, gapps, magisk) to the internal storage from PC. But when i checked in the twrp there is not file.
I think its due to the twrp encryption. I used to get the initial message in twrp to allow modifications or something. But now its just rebooting to twrp and no files is there. But connected to PC I can see all files.
Please help. Its an urgent issue, that I took my wife's phone to flash and need to return it atleast in working condition. Else you guys know the consequences right:silly:. Its a kind request.
Thanks...
i have the same problem , when i load twrp it asks to put the decrypton code but it says that its wrong..
I wanted to clean-flash stock firmware and everything went successfully with installing TWRP recovery. However, when I restore a previous nandroid that worked perfectly fine won't boot past the secure startup. I already deleted the password.key files, etc. in /data/system.
If I use LGUP to install any firmware, it boots fine. It randomly did this secure startup thing. Any help would be appreciated. What I have done so far:
1) Installed different twrp. All have the same issue
2) Already followed the instructions on Dirtysanta post, i.e., formatted data
3) When I format data, no other 'data' is created in /data/ folder, which is weird
Is my phone bricked?
Hello there,
I had had LOS17.1 installed on my SGN3. Made a TWRP 3.4.0-1 backup, flashed a stock ROM for a few days and then went for restoring LOS17 again. But restoration wasn't successful.
First "Cannot restore Modem - mounted read only" log show up during restoration. Checking Modem in Mount did not help. So I unchecked modem, which "solved" the issue.
After restore completed, device rebooted but got stuck in what I would call a recovery loop. Black screen -> TWRP splashscreen -> black screen (repeat indefinitely). It can be broken up by entering Recovery (or Download) by appropriate hardware key combo.
But the issue is I cannot get into my system. Installing LOS17 from scratch works but I would like the data.
I tried multiple TWRP versions and fix_rootfs_label.zip I have found here on XDA with no success. Installing fresh LOS17 works and restoring only "data" lets me boot, but the system is not usable (but still trying).
Restoring more than "data" always ended up in the recovery loop.
What was interesting is that when I tried to install GApps to the restored backup, it threw an error saying that this GApps package is for Android 10, while Android 7 (SDK 25) was detected on the system.
Any help?
Thank you!
Did you flash Gapps or no? If yes try nano if no i can't help