Steve0007
Inactive Recognized Developer / Retired Forum Mod
Creating a clone app like whatapp creates a second user. There is an ADB command to look at profiles / users
adb shell pm list users if iam right
Creating a clone app like whatapp creates a second user. There is an ADB command to look at profiles / users
How should we flash this if we already have twrp?Update
Hi everyone,
I just uploaded a new build. It fixes some missing firmware files and kernel module loading.
USB OTG, vibration and battery status is now working.
Download:
29.11.22 - Google Drive
drive.google.com
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.
![]()
GitHub - osm0sis/twrp_abtemplate: TWRP A/B Installer Zip Template
TWRP A/B Installer Zip Template. Contribute to osm0sis/twrp_abtemplate development by creating an account on GitHub.github.com
The only tested method for updating is the default installation procedure. But if you want you cant test the update method used for the official builds.
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:
![]()
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
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
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
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.
Source Code:
- TWRP: https://github.com/TeamWin/android_bootable_recovery
- Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8350
- Device Tree:
Bugs:
Please let me know.
Thanks to:
- Nebrassy
- TWRP team
- LineageOS
Update
Hi everyone,
I just uploaded a new build. It fixes some missing firmware files and kernel module loading.
USB OTG, vibration and battery status is now working.
Download:
29.11.22 - Google Drive
drive.google.com
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.
![]()
GitHub - osm0sis/twrp_abtemplate: TWRP A/B Installer Zip Template
TWRP A/B Installer Zip Template. Contribute to osm0sis/twrp_abtemplate development by creating an account on GitHub.github.com
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 osQuick question.
The following is not clear to me.
In step 1 it says to download your own vendor_boot.
In step 3 it says to flash it but which one? My own one or the TWRP one. (I'm currently on CrDroid13)
Thx for the quick answer. That workedYou 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.You flash the twrp one in order to boot twrp, then after permanent install, you flash yours or it won't boot to os
Your welcome, anytime
When flashing from magisk, do we flash to inactive slot?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.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.![]()
No it will automatically install to active slot. You can change slots but no reason to.
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.So first off ...thanks for the awesomeness! But ... I'm having an issue with roms not flashing because of a "timestamp" issue? Is there a workaround?
That error is related to kernel module loading. All custom roms install kernel modules to vendor_dlkm, but OOS does not. It uses vendor and vendor_dlkm doesn't exist. So this error isn't nice, but just cosmetic.But it didn't, and the smart folks in the OP 9 Telegram group said that's because fastbootD is broken in TWRP. I always ended up with that error and no matter if I tried to get to fastbootD via fastboot command or TWRP, I always ended up in the same spot again. I was told I should restore stock boot.img and then root + install TWRP again after flashing that abl file, but that seemed like a lot of hassle when using the Firmware Flasher achieved the same thing and was so simple![]()
Getting the same firmware to both slots? That doesn't make the orange state go away, does it? You have to flash the right abl.img.He doesn't need to edit in your abl file if he uses the Firmware Flasher. I'm not sure what exactly that flashes, but we end up with the same firmware on both slots (which I think is good for when we want to go to a custom rom?) AND without that warning. So 2 birds with 1 stone so to speak - but no editing/modifying anything is needed![]()
It does make the orange state go away, I'm guessing it has the correct abl.img included already? And it's really simple too - just flash it from (custom) rcovery and that's it, no hassle at all.Getting the same firmware to both slots? That doesn't make the orange state go away, does it? You have to flash the right abl.img.
Or, the firmware you are flashing has the abl.img without warning? That might be the case.
This is a very useful guide and it has more than one way to safely flash abl.img without hassle if you are rooted.
But it didn't, and the smart folks in the OP 9 Telegram group said that's because fastbootD is broken in TWRP. I always ended up with that error and no matter if I tried to get to fastbootD via fastboot command or TWRP, I always ended up in the same spot again. I was told I should restore stock boot.img and then root + install TWRP again after flashing that abl file, but that seemed like a lot of hassle when using the Firmware Flasher achieved the same thing and was so simple
First of all, this is a thread for OnePlus 9/Pro; not Samsung. Please refer to your phone's forum for better support.Hello, I installed an Android 13 custom rom on a Samsung device with twrp-3.7.0_9-0 but unfortunately there is no encryption. Does encryption depend on the rom or on TWRP and will this TWRP version work on a Samsung phone? And is there some trick to enforce encryption when flashing custom rom with TWRP?
I can't reproduce your issues too, and it's the same for the sideloading issues addressed by @Rallyharry. I tested under windows and linux with the latest builds. The only thing I noticed was that I had to switch drivers under windows manually to WinMTP and I couldn't use mtp and adb simultaneously. But the whole windows driver system is a mess anyway.I can'y thank you enough @der_akinator for reviving the TWRP recovery for OnePlus 9 Pro. I'm really happy for it.
Thank you so much, everything works fine, except MTP. I can't see my storage when connected to my PC using USB cable.
if you can fix this it would be great.
Thank you again.