How should we flash this if we already have twrp?
I will try it. Thanks for your tip.Does the A/B flashable zip with the TWRP ramdisk in it work to install it? Might be able to skip the vendor_boot steps that way.
broooooooo, now you are helping all op9p usersThis is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by most Android 12 and 13 ROMs.
As always I'm not responsible any bricked device or data loss resulting from the use of this TWRP version. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...forum.xda-developers.com
In the case you just want to test TWRP without installation, please skip steps 5-7.
- Get your rom's vendor_boot image. For most ROMs this can usually be downloaded. For OOS based ROMs you can get it for example by extracting it from the official payload.bin with payload-dumper-go. A third universal option, if you have root, is to use the command "dd if=/dev/block/by-name/vendor_boot_SLOT of=/sdcard/vendor_boot.img" on your device. This writes the vendor_boot image to your sdcard folder, but you have to substitute SLOT with either a or b, depending on your currently active slot.
- Reboot to bootloader.
- Run "fastboot flash vendor_boot vendor_boot.img" with the TWRP vendor_boot image.
- Run "fastboot boot boot.img" with the TWRP boot image.
- Go to Advanced > Flash Current TWRP.
- After that is done, if you were using a custom kernel, reflash it now.
- If you were using magisk, reflash it now.
- Reboot to bootloader.
- Run "fastboot flash vendor_boot vendor_boot.img" with the ROM vendor_boot image from step one.
Permanent installation works fine for me with crdroid 13 and magisk installed. I have not tested any other ROMs or custom kernels. After permanent installation you can at any time reboot to recovery without reflashing vendor_boot. During a ROM update use the "Automatically reflash TWRP after flashing a ROM" option in the install zip menu to preserve TWRP.
- TWRP: https://github.com/TeamWin/android_bootable_recovery
- Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8350
- Device Tree:
Please let me know.
- TWRP team
Does the A/B flashable zip with the TWRP ramdisk in it work to install it? Might be able to skip the vendor_boot steps that way.
I tried it out over latest Lineage and it does seem to work! I even then re-rooted with Magisk and re-flashed blu_spark from within TWRP.
Yes, your twrp install script works for me too. Tanks for that.I tried it out over latest Lineage and it does seem to work! I even then re-rooted with Magisk and re-flashed blu_spark from within TWRP.
Only issue (but it's pretty big) is that vibration is broken and it seems to hang the UI hard any time it tries to vibe, so my workaround is to hit Cancel at the Decrypt page, go to Settings and turn all the vibration down to 0, then go back to Mount and Decrypt Data from there. (You can also just be verrrrrry patient when doing pattern.)
Not sure if this is because I installed the whole ramdisk directly like that or because it's over Lineage. I'm guessing the latter, with some kind of modules mismatch?
Any ideas how to resolve that? Disabling vibration entirely might be needed, since I recall @Nebrassy never got it working across all ROMs.
Either way, being able to use the TWRP zips will save a lot of headaches for rooted users.
P.S. Also great that vendor_boot is only need for fastboot tempboot, since that means my twrp_ab addon.d-v2 script should work for us already!
P.P.S. We need to get you in the TWRP Development Zulip if you're not lurking there already: https://rebrand.ly/teamwin-recovery-zulip-community
You flash the twrp one in order to boot twrp, then after permanent install, you flash yours or it won't boot to os
Now that there's a TWRP zip you could skip vendor_boot shenanigans altogether by, a) flash from Magisk app, or even b) flash from custom ROM recovery like Lineage Recovery.
Actually no, when you boot this twrp, it will not boot to twrp without the twrp vendor_boot. Likewise, the os won't boot unless you replace it with the original vendor_boot from stock, rom, etc.
Can you please send me a logcat and recovery log. I have seen an initscript related to timestamps in Nebrassy's op7 device tree. Maybe this would solve the problem.
First of all, edit your old post instead of making a new one each time you try...
I could reproduce your issue when restoring backup with pattern set. It looks like super and data shouldn't be restored at the same time.Restore doesn't work on LOS 19.1. Force checked twice...
I made the backup without pattern/pin, now when it comes to restoring I try to do a factory reset first, I restart I enter the OS, I go back to TWRP and I do the restore, I restart and the lineageos logo stays loading, it restarts only a couple of times, I enter TWRP to get the logs (it doesn't ask for a pin) but I'm going to mount the files and it's empty, it seems that everything has been deleted, in the "mount" option there is a button that says decrypt data, but it asks for a password (text)....
If you flashed boot then that's the problem. You don't flash boot. You boot it first.