It has come to attention that whenever I try to restore my old backups in the latest version of TWRP, TWRP becomes stuck on running recovery commands and loops forever.
Downgrading to TWRP 3.1.1 solves this issue.
While TWRP 3.2.0 brings changes for Android Oreo, it seems it has broke basic TWRP functionality! Use older versions to solve this issue.
Also, post here if you have the same issues rather than development threads
Update: It seems that TWRP 3.2.1 has solved all of the issues
Need TWRP?
Here is the custom version of TWRP built by our LOS maintainer:
https://androidfilehost.com/?w=files&flid=142086
Related
I have noticed a few people including myself who have had TWRP or the recovery partition some how corrupted after flashing a 5.1/5.1.1 kernel or rom.
Usually what seems to happen is that a 5.1 kernel/rom is flashed (data/cache f2fs for me) which leads to a bootloop. Restarting to bootloader and on to recovery ends up with twrp not loading.
I've noted that this has happened for me with mkernel a75, and also to a user flashing the latest phantom alpha, and to someone who flashed optipop which uses the latest lean kernel.
Flashing twrp again did not fix for me, had to flash the latest factory image.
I have only noticed this after android 5.1 and only on grouper. Anyway, I was just wondering if others are running into this issue. Maybe we can figure out what going on.
I had the same issue when I fully reset the device, it wouldn't even load stock recovery. Flashing TWRP again solved my issue so I can't speak to why it would not flash for you.
i am using the latest hydrogen os..marshmallow...
but i can't restore previously backed up cm13 with the twrp used in installation of hydrogen os.....so i tried flashing normal twrp with fastboot....this led to not even getting to the recovery...i was stuck in the boot logo
so..i again flashed the hydrogen based twrp and tried flashing cm13 with it...but it didn't work either...
so guys...how can i use another rom..with my condition...i can't flash neither recover previous image...
help guys
Try flashing the latest community version of Oxygen OS first with the modified TWRP.
Then flash the stock recovery of Oxygen 2.1.2.
Now flash stock Oxygen 2.1.2 with the stock recovery.
Now you can flash the normal TWRP and restore CM13 image.
PS- I didn't try all these. But I think it should work.
This might help
I found a hybrid TWRP that claims to be compatible with Hydrogen. Oxygen, Vanilla Marshmallow etc., made for the OP2. Here you go.
http://forum.xda-developers.com/oneplus-2/general/recovery-twrp-3-0-2-hybrid-supports-oos-t3362904
With that you might be able to get into recovery again and install whatever OS you like. I found this searching for the TWRP decryption problem.
Fennec
Hi,
My OP5 worked like a charm with Resurrection Remix 5.8.5, but recently my pin was randomly unrecognised, and I solved it with lock key files suppression. I ended up to restore a backup but got a bootloop, that occured with every rom I tried.
I had bootloader unlocked and magisk flashed.
I finally managed to flash and boot Resurrection Remix 6.0 (after wiping every partition), but at every reboot, when in twrp 3.2.1.0 (also tried on 3.1.1), I'm unable to mount data partition. Also it doesn't ask for my pin as it did before all those reflashing. The rom seems to have no issue (except some bugs).
I tried reflashing twrp without result and deleting internal storage is working so far as long as I don't reboot. I found some threads with similar problems about Oreo's related roms but I don't know if they are related to my issue.
I'm currently on RR6.0, bootloader unlocked, twrp 3.2.1.0 and no root, and encrypted by default.
Do you have any idea on this ?
Thanks for your help.
nonnaryplayer said:
Hi,
My OP5 worked like a charm with Resurrection Remix 5.8.5, but recently my pin was randomly unrecognised, and I solved it with lock key files suppression. I ended up to restore a backup but got a bootloop, that occured with every rom I tried.
I had bootloader unlocked and magisk flashed.
I finally managed to flash and boot Resurrection Remix 6.0 (after wiping every partition), but at every reboot, when in twrp 3.2.1.0 (also tried on 3.1.1), I'm unable to mount data partition. Also it doesn't ask for my pin as it did before all those reflashing. The rom seems to have no issue (except some bugs).
I tried reflashing twrp without result and deleting internal storage is working so far as long as I don't reboot. I found some threads with similar problems about Oreo's related roms but I don't know if they are related to my issue.
I'm currently on RR6.0, bootloader unlocked, twrp 3.2.1.0 and no root, and encrypted by default.
Do you have any idea on this ?
Thanks for your help.
Click to expand...
Click to collapse
Are you using the twrp from twrp.me or a modded recovery like codeworkx or blu spark? The original recoveries from twrp.me don't work on oreo.
Try using these recoveries:
Codeworkx: https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Blue spark: https://forum.xda-developers.com/devdb/project/dl/?id=28224
Zohair.ul.hasan said:
Are you using the twrp from twrp.me or a modded recovery like codeworkx or blu spark? The original recoveries from twrp.me don't work on oreo.
Try using these recoveries:
Codeworkx: https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Blue spark: https://forum.xda-developers.com/devdb/project/dl/?id=28224
Click to expand...
Click to collapse
It worked Thanks ! I flashed codeworkx and all went fine : data is mounted at every boot, encryption unlock in recovery, flashing and restore.
I should have waited to flash oreo but this rom is the first to get me out of my bootloop hell so I'll stick with it for now.
Thanks again !
No problem Glad to see your issue got fixed.
I was using PIXEL EXPERIENCE 9.0. Then to update Rom i tried to install Twrp. I mistakenly booted nougat twrp from fastboot
Then after i noticed that i was trying nougat twrp instead of Oreo..i downloaded oreo twrp and booted...but when i tired to touch is was faulty..mean for suppose i triede to open mount menu it touch on Reboot in twrp.
Then i decided to flash stock rom.
I downloaded latest one and flashed but result was same... Touch problem...
PLEASE TELL.ME FIX
hey guys, so i used twrp to flash a OTA then flashed twrp again and rebooted and when i went to flash magisk i was just shown a list of all random numbers/letters. i booted into bootloader flashed twrp img, booted into recovery and all my files were there once again but i still cant get into the OS, can anyone please help?
why is flashing so complicated these days? even the recovery works different. the last time i rooted (4 years ago maybe) you could use twrp to make a backup and it was done simple as that (i did this on the oneplus 6t about 4 weeks ago and got the issue with my storage just being a list of numbers and letters and had to find a way to fully wipe and re install OOS) and the same for flashing, i could just flash something and it was fine, no issues.
Do you have an OTG adapter and pendrive? You can copy the full OTA zip, TWRP zip and Magisk zip on to that and flash from TWRP using that. Your internal storage is encrypted and you won't be able to access it until you can reboot OOS fully. If that didn't work, you may have to do a factory reset/wipe (including internal data) to get the phone to boot again. You will obviously lose any unbacked data.
Which version of TWRP are you using? Which version of OOS are you using? Most likely you just don't have the correct version, and you updated to the latest version OOS with the new security patch and it no longer can decrypt it.
Have you tried TWRP 3.3.1-7 from here? If you boot the .img file from fastboot, can you decrypt your data?
Most likely you just need to flash Magisk, and you will be fine. For updates, it's always as you did, flash the full OTA update, TWRP installer, reboot to recovery, Magisk. It is recommended to uninstall Magisk, however I usually don't do that personally. Official Instructions here. You just have to make sure you are using the correct version of TWRP, otherwise you can run into encryption issues, as you found out when there are updates.
OhioYJ said:
Which version of TWRP are you using? Which version of OOS are you using? Most likely you just don't have the correct version, and you updated to the latest version OOS with the new security patch and it no longer can decrypt it.
Have you tried TWRP 3.3.1-7 from here? If you boot the .img file from fastboot, can you decrypt your data?
Most likely you just need to flash Magisk, and you will be fine. For updates, it's always as you did, flash the full OTA update, TWRP installer, reboot to recovery, Magisk. It is recommended to uninstall Magisk, however I usually don't do that personally. Official Instructions here. You just have to make sure you are using the correct version of TWRP, otherwise you can run into encryption issues, as you found out when there are updates.
Click to expand...
Click to collapse
Latest twrp and latest full OOS OTA. If I fastboot the twrp. Img I can see all my data again. I've fixed it now, I flashed the twrp. Img in fastboot then rebooted system and it worked