Same answer as the last dozen times this question was asked - NO.
Well, it does somewhat. I can flash a12 ROMs, but after that, it will only read otg and not internal storage. So I can flash ROMs using otg
Well generally when someone asks if something "works" they don't mean "somewhat" but ok lol.
ATM it still makes TWRP fairly useless then since you can't make/restore nandroids if it can't read internal storage and I think I'm not the only one who sees that as the main purpose of TWRP
.
I didn't say anything about it working lol. I was making a statement of what DOES workWell generally when someone asks if something "works" they don't mean "somewhat" but ok lol.
ATM it still makes TWRP fairly useless then since you can't make/restore nandroids if it can't read internal storage and I think I'm not the only one who sees that as the main purpose of TWRP
AnierinB
Recognized Developer
1. The A12 kernel source is incomplete (missing various things like touch panel driver and techpack)@infected_ now that the kernel source of 12.1 is out, will there be A12 support finally?
2. It doesn't work like that. The encryption/decryption algorithm in A12 has yet to be implemented correctly into any 3rd party recovery. And this is for all android devices running 12, not just op8 series.
Update: As of last night, enough of the kernel source has now been released to start the oplusification of 8 series. However this still doesn't change anything regarding the encryption algo in A12 from being implemented in twrp.
Last edited:
AnierinB
Recognized Developer
I'm happy to take education on this if you have a minute. Doesn't the ROM/A12 determine which encryption level is used, which is TWRP agnostic? Is there something newer than fbev2?
I'm referring to TWRP for op5, not any ROM in particular.
What?! No it's not
. OnePlus 7,8,9 Nord N200 (just the ones I can confirm) all use the same encryption methods. Which is metadata wrapped key for userdata that is stored on the metadata partition. Android 12 just still needs it figured out. Imma start working on the N200 today to see if I can get it working with stock A12. I gave up after getting it working on A11(after getting decryption without lock screen security functional) because A12 was right around the corner and will be the N200's final release version. Then I back track to N100 
You have no clue what you're talking about lol. I worked with the twrp devs on beta testing twrp for 6t and 8 pro. @infected_ will tell you the same thing I just did. 8 pro is a unique phoneWhat?! No it's not
The 8 is unique compared to the 6t. OnePlus 7 was configured more like the 6t in Android 10, that changed with Android 11 and even more so with Android 12. I am a TWRP developer. I have been making TWRP since Oreo was current. I have made TWRP very specifically for OnePlus devices and alot of "OnePlus 8 specific" changes had to be made to OnePlus 7 with the release of Android 11. You don't know what you're talking about, only what you've been told. I on the other hand brought up my own TWRP trees enough times to know what it is and what it isn't
Do I need to provide proof? I have access to enough devices to prove my point without having to use posts from others to back my viewpoints. It is only mainly the android version that differentiates OnePlus device configurations. Slight differences in partition naming, that's easily addressed. Android 13 is going to bring a whole new batch of problems for OnePlus 8,9,10,11 series devices. And because 11 is going to be the first to release with it, it's going to be "so much different than any other device" mostly because the dev working on OP10 will probably not be the one to work on OP11, it's probably going to be a OP8 or OP9 dev, leaving that gap in knowledge that makes it "so much different".
Don't provide your input on subjects that you don't understand
EDIT: forgot to meantion differences in boardconfig flags for avb and boot header version. Reaaaaaally small and normal differences.
I have worked with plenty of devs, lossyx, infected, wishmasterflo, varun date, etc....I have been rooting and modding android since droid 1 days. Even complied ROMs back in the dayThe 8 is unique compared to the 6t. OnePlus 7 was configured more like the 6t in Android 10, that changed with Android 11 and even more so with Android 12. I am a TWRP developer. I have been making TWRP since Oreo was current. I have made TWRP very specifically for OnePlus devices and alot of "OnePlus 8 specific" changes had to be made to OnePlus 7 with the release of Android 11. You don't know what you're talking about, only what you've been told. I on the other hand brought up my own TWRP trees enough times to know what it is and what it isn't
Do I need to provide proof? I have access to enough devices to prove my point without having to use posts from others to back my viewpoints. It is only mainly the android version that differentiates OnePlus device configurations. Slight differences in partition naming, that's easily addressed. Android 13 is going to bring a whole new batch of problems for OnePlus 8,9,10,11 series devices. And because 11 is going to be the first to release with it, it's going to be "so much different than any other device" mostly because the dev working on OP10 will probably not be the one to work on OP11, it's probably going to be a OP8 or OP9 dev, leaving that gap in knowledge that makes it "so much different".
Don't provide your input on subjects that you don't understand
EDIT: forgot to meantion differences in boardconfig flags for avb and boot header version. Reaaaaaally small and normal differences.
8 pro using ice, dynamic partitions, and a/b was a mess for getting twrp to work
Attachments
Because of new changes that came with android 10, the version of android Oneplus 8 shipped with. Thank you for the validation
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
12
1. The A12 kernel source is incomplete (missing various things like touch panel driver and techpack)@infected_ now that the kernel source of 12.1 is out, will there be A12 support finally?
2. It doesn't work like that. The encryption/decryption algorithm in A12 has yet to be implemented correctly into any 3rd party recovery. And this is for all android devices running 12, not just op8 series.
Update: As of last night, enough of the kernel source has now been released to start the oplusification of 8 series. However this still doesn't change anything regarding the encryption algo in A12 from being implemented in twrp.111
What?! No it's not. OnePlus 7,8,9 Nord N200 (just the ones I can confirm) all use the same encryption methods. Which is metadata wrapped key for userdata that is stored on the metadata partition. Android 12 just still needs it figured out. Imma start working on the N200 today to see if I can get it working with stock A12. I gave up after getting it working on A11(after getting decryption without lock screen security functional) because A12 was right around the corner and will be the N200's final release version. Then I back track to N100 -
61TWRP for OnePlus 8 and 8 Pro
TWRP is an open source, community project. TWRP development is done by a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers, and zulip-chat.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM".
Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no responsibility for any damage that may occur from installing or using TWRP.
Code:#include /* * * Yea, though I walk through the valleys of c++ and java, of the shadow of death on these forums, * I will fear no evil and i will develop and code restless: for thou art with me and my keyboard; * thy rod and thy staff they comfort me, and my mouse.. * */
A12 support is still a WIP, but most things are working, A12 is all new, keep that in mind.
WORKING:
Decryption
ADB Sideload
Format Data
Flashing zips (kernels and ROM's)
Backup/Restore
MTP is working
adb is working
vibration
stock firmware flashing
OTG
NOT WORKING
wip
A12
Download
:: SourceForge ::
:: AndroidFileHost ::
Instructions
Windows
Install oneplus usb driver, after disabling driver signature enforcement
Download and install platform tools, unzip and add the folder to Windows path,
"Settings > Advanced System Settings > Environment Variables > New"
Example -> http:///imgur.com/a/x8XOofQ
open command prompt, or powershell, and:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
Linux
Download and add to path (.bashrc) platform-tools:
export PATH=$HOME"/platform-tools:$PATH"
dont forget udev rules if you're using ubuntu based distro:
https://github.com/M0Rf30/android-udev-rules
open a terminal and:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
that's all.
Source Code:
https://github.com/infectedmushi/android_device_oneplus_instantnoodle-dev
https://github.com/infectedmushi/android_bootable_recovery
https://github.com/bigbiff/android_device_oneplus_instantnoodle
https://github.com/TeamWin/android_bootable_recovery
https://github.com/systemad/android_device_oneplus_instantnoodle
Credits:
@bigbiff
@Lossyx
@Captain_Throwback for original tree
@mauronofrio for original tree
TWRP team23uploaded beta 6.
changelog:
* Add custom kernel for recovery
* crypto: only set crypto state and type if not already set
* crypto: only show FBE error if device is encrypted
* digest: fix checking of digest on restore
* fs_mgr: allow deleting merged snapshots
* merges: allow user to perform snapshot merges in advanced menu
* mtp: don't create storage device after format data
* recovery: Allow kernel to read and write unlabeled files
* repacker: add root overwrite warning
regards.23uploaded beta 3. it's possible now to backup persist partition also.
twrp-op8-3.6.0_11-infected-b3.img
twrp-op8-3.6.0_11-infected-b3.zip
* 0c94cd7 - fstab: it's now possible to backup persist partition.
* b99d112 - module load: Try loading prior modules first
* 5ab53dc - libresetprop: use the latest header
* 60927bc - kernel_module_loader: Set a prop after completing
* 3a95d18 - fscrypt v1: support legacy ioctl
* 540c802 - build: add option to create recovery installer zip
* 7284ace - vndk: remove exclusion in recovery
* aa2f760 - update_engine: handle payload that contain xbl_lp5 partitions
* f1db62e - libresetprop: update to magisk HEAD
* b65b045 - soong: Add TARGET_LEGACY_HW_DISK_ENCRYPTION conditional
regards.22uploaded beta 8.
* sdcard: only bind mount sdcard after successful preparation of data
* Add TW_QCOM_ATS_OFFSET flag to manually set time/date offset
* System_Property_Get: Allow specifying multiple prop file paths
* update RECOVERY_INSTALLER_PATH to proper path
* fastbootd: Check for and run startup script if script exists
* Adding TARGET_OTA_ASSERT_DEVICE flag for custom device asserts
* theme: move TW_THEME_VERSION to variables.h
* theme: clean up TW_THEME_VERSION shell command
* prebuilt: update magiskboot to v24.1 stable
regards.
New posts
-
-
[ROM] [12.1] [OFFICIAL] AICP 12.1 [instantnoodlep]- Latest: Neil_Armstrong_
