Hello,
I require help please, here is my situation:
After trying to encrypt my phone, it immediately rebooted and now it's loop booting.
I still have access to TWRP 3.3.1.1
I try reinstalling the rom by dirty flashing it (it's an old crdroid rom, 5.8) but i still have the same problem.
I really would like to not delete my data, because I have a duo config (2FA) and i realized that for one config, the master key backup that i have is not working.
Thanks a lot
I had to flash the factory rom, and i have an extra backup of my 2FA, so everything fine eventually
Related
Hi all,
I have A6000 with OOS 9.0.5. I installed magisk and TWRP with this guide. I did a full backup, however I cannot restore it. I get error 255 on tarExtractFork(). I use official TWRP 3.3.0. After failed restore I can still boot to (now freshly wiped after attempted restore) system. Even backups of this clean system cannot be restored.
For the record, I don't have a second profile, no "999" user id, I didn't change slots, I removed screen lock before making backup. I still have this problem even if I backup just data, with all other options unticked.
Any help? I come from a device, which didn't have any problems with backup/restore so this is a bummer for me. But I'm sure that users of OP6 can do backups and restores.
Thanks!
For anyone that also has the same problem:
This helped me. I have a feeling that flashing just data through fastboot could be enough, but I didn't have an occasion to check it, as even subsequent restores worked.
I used this to flash device in fastboot mode.
Hello,
My problem is that I can not access my SD card data because TWRP does not ask me for encryption password. I can see the files but they are all gibberish
How did I end up here?
I was using RR 7.0.2. and doing random magisk module testing and suddenly everything started to misbehave. I panicked and ran Nandroid backup but restoring failed to tar fork something. Then I decided to factory reset and flash original Resurrection Remix rom which I was using and bluespark TWRP which I was using before. I tested TWRP installation by rebooting to recovery.
Booting went well but TWRP never asks encryption password/pattern, which causes sd card data to be encrypted. Is there way to get sd card data decrypted or is it all lost?
-Athum
You lost your encription keys Im afraid, all data is lost, next time decrypt before flashing any custom ROMs for your own data sake.
Whenever I make a backup in TWRP, and later try to restore it, I get no errors, the restore seems to go fine, but when I reboot, I never get anything but a bootloop on the Mi logo. Even if the system was working when I made the backup, working before I do the restore, and haven't changed the encryption (same password, same ROM, no /data wipe) the restore breaks it. It's happened on Xiaomi.EU, it's happened on AOSiP, ArrowOS, several versions of mauronofrio's TWRP (including the latest) and Sky Hawk recovery - I've just never had a successful restore on this phone. Am I doing something wrong?
Hi. I tried to encrypt the storage but it got stuck for several hours so I decided to reflash. I wiped the storage, reflashed and bootloop. So, I have again wiped the storage using TWRP now including Internal storage, reflashed, and bootloop. I also tried fixing SeLinux and filesystems and reflashing. Again bootloop.
So I took my stock ROM Backup, flashed it and it booted up. So then I went into recovery, deleted encrypted data partition, reflashed pixelexperience through adb sideload, and just another bootloop. So I tried reflashing through TWRP and again bootloop. It now always gets stuck in the bootloop no matter what. I don't understand what could be wrong. It worked previously and I had it flashed twice due to making a mistake, but it woked both times.
It's moto G5s Plus and I used PixelExperience 11+. Do you have any ideas on how to fix this? I'll probably just try different custom ROM, probably Lineage OS. But I like pixelexperience so I want to use it.
Thanks for help.
Alright, I just got it working!!! I reformatted the memory card just to be sure, then placed the stock ROM backup on it and PixelExperience ROM. I went into TWRP and wiped everything (except Micro SD card, of course). Then I restored my backup of stock ROM which I previously made in TWRP. This time I included the recovery image. I rebooted, quickly set it up and checked if it works. Fine, works (and somewhere in the process it got rid of bloatware ). I then rebooted into fastboot and reflashed custom recovery. Then I opened custom recovery, wiped data and restored installed PixelExperience package. Then I rebooted and SUCCESS!
So, just as a reminder, BACK UP YOUR SYSTEM WITH STOCK ROM BEFORE MODIFYING IT.
Installed Lineage 18.1 OS, TWRP 3.6.0_11-0 and Magisk, booted system, added PIN and fingerprints, all was good. Booted back into TWRP and made a full backup of all partitions. Tried a test restore of Super and Data partitions. Upon reboot, I get the lineage splash/boot screen, then "phone is starting" forever. From reading around, this is due to the system trying to access encrypted data. Questions: 1) I'd like to be able to use TWRP for two things: a) restoring to a new device should this one break, and b) reverting back to previously backed up state of operation on the same device. What partitions should I be restoring for each of these? 2) Is there a fix or proper method to make restorable backups using TWRP?
Exactly the same situation. And have exactly the same questions.
Had the same problem, wiped data, repaired data file system, rebooted into system to disable the pin. Then restored my TWRP data backup again, now it boots into system, just had to reboot twice because the gestures and staturbar didn't work first. Now I just have to tweak some little details again to get it how it was.
Didn't solve my main problem though, SMS not working. Wiped and repaired data again, now it works. Welp, guess I have to set it all up again from here.