Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Seems is working all
- Android Q Support
- Android 11 Decryption
Install guide (Reccomended):
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
Other Install guide (More articulated but fully functional):
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Choose the recoveryimgfilename.img
9. Swipe to install
OLD Install guide (Much more articulated but perfectly functional):
1. Follow this guide to root your device: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205
2. Flash the TWRP installer like a magisk module
3. Flashing the TWRP installer you will lose the root, so you will need to flash magisk again from magisk manager before reboot the device or you can reboot the device and flash magisk in twrp
HOW TO UPDATE a ROM and KEEP TWRP and ROOT:
Before all Disable all magisk modules for boths methods
- Put rom.zip, twrp installer.zip and magisk.zip on your internal storage;
- Flash Rom;
- Flash TWRP Installer;
- Flash magisk;
- Reboot.
If you want you can also update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- Menu/modules/+ button/select the twrp installer.zip and flash it;
- Always in Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
BugReport:
Please all, when you got a problem, bootloop, error in twrp, unable to do something, please be sure you have followed the guides properly and when you write here you have problem just follow this guidelines for the bugreport:
- Write what rom and version you have actually;
- Write which device you have, gm1910, gm1913, gm1917, gm1915, gm1920, gm1911.
- Write which twrp you are using (Unofficial, Officia and the version);
- If you got an error in the twrp flashing a zip, after got the error make a log using this command : "cat /tmp/recovery.log" or if you are using adb with "adb shell cat /tmp/recovery.log". Copy the output in a text file and send me it.
- Write what are you trying to do;
- Write how you flash the twrp and magisk, just write what you do.
If you don't give me this infos i can't help you.
If something doesn't work, don't just complain, but try to get the problem resolved by giving all the information you have.
Tips:
If android Q TWRP .img doens't work, reboot in fastboot again and try the Pie TWRP
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
India Fake Partition Deleter by mauronofrio
Official Builds
TWRP 3.4.0-10 Unified Unofficial Q by mauronofrio
TWRP 3.4.0-10 Unified Unofficial Installer by mauronofrio
TWRP 3.4.0-0 Unified Unofficial Q by mauronofrio
TWRP 3.4.0-0 Unified Unofficial Installer by mauronofrio
Spoiler: Show old builds
TWRP 3.3.1-79 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-79 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-79 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-76 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-76 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-76 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-75 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-75 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-75 Unified Unofficial Installer by mauronofrio / Mediafire
TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-74 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Installer by mauronofrio
TWRP 3.3.1-65 Unified Unofficial by mauronofrio
TWRP 3.3.1-65 Unified Unofficial Installer by mauronofrio
Official Builds
OnePlus 7 Pro 9.5.3 stock boot.img
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_oneplus_guacamole_TWRP
https://github.com/mauronofrio/android_device_oneplus_guacamole_unified_TWRP
Android Pie IMG: https://gitlab.com/HolyAngel/op7
Android Q IMG: Precompiled stock one
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
Thanks to @Titokhan for the tests
Thanks to all Telegram Test Group
Thanks to @HolyAngel for the kernel
Thanks to @rsyhan for the help with the reserve script
Thanks to @arter97 for the help with the Android Q Kernel
Created 2019-05-18
Before you start asking, i don't know if this twrp will work on OnePlus 7, it should works too, but i'm not sure.
Do you have any idea if it's region specific or not? Since the stock OxygenOS zips are region and serial specific
tych_tych said:
Do you have any idea if it's region specific or not? Since the stock OxygenOS zips are region and serial specific
Click to expand...
Click to collapse
I think you can flash it without problems on all region variants
Hello, after I do fastboot reboot it bootloops oos. And I followed the tutorial step by step
E:\Desktop\akbar\platform-tools>fastboot getvar current-slot
current-slot: a
finished. total time: 0.005s
E:\Desktop\akbar\platform-tools>fastboot --set-active=_b
Setting current slot to 'b'...
OKAY [ 0.045s]
finished. total time: 0.046s
E:\Desktop\akbar\platform-tools>fastboot flash boot test-twrp-3.3.1-1-guacamole.img
target reported max download size of 805306368 bytes
sending 'boot_b' (55972 KB)...
OKAY [ 1.191s]
writing 'boot_b'...
OKAY [ 0.292s]
finished. total time: 1.484s
E:\Desktop\akbar\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.002s
mingo_mgx said:
Hello, after I do fastboot reboot it bootloops oos. And I followed the tutorial step by step
E:\Desktop\akbar\platform-tools>fastboot getvar current-slot
current-slot: a
finished. total time: 0.005s
E:\Desktop\akbar\platform-tools>fastboot --set-active=_b
Setting current slot to 'b'...
OKAY [ 0.045s]
finished. total time: 0.046s
E:\Desktop\akbar\platform-tools>fastboot flash boot test-twrp-3.3.1-1-guacamole.img
target reported max download size of 805306368 bytes
sending 'boot_b' (55972 KB)...
OKAY [ 1.191s]
writing 'boot_b'...
OKAY [ 0.292s]
finished. total time: 1.484s
E:\Desktop\akbar\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
try to manually reboot in recovery mode, there is something be understood for now. If it doesn't boot in twrp in any method just flash stock boot.img.
EDIT:
TWRP 3.3.1-2:
Fixed vibration:
TWRP 3.3.1-2 Unofficial by mauronofrio
TWRP 3.3.1-2 Unofficial Installer by mauronofrio
mauronofrio said:
try to manually reboot in recovery mode, there is something be understood for now. If it doesn't boot in twrp in any method just flash stock boot.img.
Click to expand...
Click to collapse
Will try, but my device has oos 9.5.1, and I can't find the full rom zip anywhere
mingo_mgx said:
Will try, but my device has oos 9.5.1, and I can't find the full rom zip anywhere
Click to expand...
Click to collapse
you should update, the twrp is made with 9.5.3
Please can someone confirm if unlocking the bootloader makes you lose Widevine L1 on this device please ?
mauronofrio said:
try to manually reboot in recovery mode, there is something be understood for now. If it doesn't boot in twrp in any method just flash stock boot.img.
EDIT:
TWRP 3.3.1-2:
Fixed vibration:
TWRP 3.3.1-2 Unofficial by mauronofrio
TWRP 3.3.1-2 Unofficial Installer by mauronofrio
Click to expand...
Click to collapse
From looking at the source of device extracted. There are a few changes we need to make .
The first I noticed is that we have a recovery partition again.
Along with the metdata encryption.
Not sure about the v3 synthetic keys on this but looking at the fstab from device I believe it is. Even if it's not on May security patch. Can anyone confirm this?
twinnfamous said:
From looking at the source of device extracted. There are a few changes we need to make .
The first I noticed is that we have a recovery partition again.
Along with the metdata encryption.
Not sure about the v3 synthetic keys on this but looking at the fstab from device I believe it is. Even if it's not on May security patch. Can anyone confirm this?
Click to expand...
Click to collapse
recovery partition is not there, i checked the partitions, there is only a string on the fstab, it is not in may security patch
mauronofrio said:
recovery partition is not there, i checked the partitions, there is only a string on the fstab, it is not in may security patch
Click to expand...
Click to collapse
Hangouts or telegram?
It's better that way
twinnfamous said:
Hangouts or telegram?
It's better that way
Click to expand...
Click to collapse
telegram still mauronofrio
Sapper Morton said:
It shouldn't be possible to maintain security level 1 without a secure bootloader. So yes, it will break Netflix and such in High Definition.
You can read more at:
https://storage.googleapis.com/wvdocs/Widevine_DRM_Getting_Started_Devices.pdf
Click to expand...
Click to collapse
Well my unlocked Nexus 6P says otherwise, still widevine L1..
Harry Pothead said:
Well my unlocked Nexus 6P says otherwise, still widevine L1..
Click to expand...
Click to collapse
Maybe OnePlus devices are different? For sure the Essential Phone and maybe the Pixel phones still have Widevine L1 when unlocked and rooted.
bmg1001 said:
Maybe OnePlus devices are different? For sure the Essential Phone and maybe the Pixel phones still have Widevine L1 when unlocked and rooted.
Click to expand...
Click to collapse
Could be of course. the question is why implement it to behave differently if you don't discourage people from unlocking the bootloader, would be really annoying from oneplus...
Harry Pothead said:
Could be of course. the question is why implement it to behave differently if you don't discourage people from unlocking the bootloader, would be really annoying from oneplus...
Click to expand...
Click to collapse
What the hell is going on then ?
Plus it's doing the exact opposite of discouraging me unlocking the bootloader = Cancel my Netflix and Prime subs, and stream their shows over Plex in 1440p HDR quality.
Remember all of you streaming providers : There is only one side who suffers when implementing DRM, and it's very rarely the user side
Harry Pothead said:
Could be of course. the question is why implement it to behave differently if you don't discourage people from unlocking the bootloader, would be really annoying from oneplus...
Click to expand...
Click to collapse
I'd assume these other phones implement: "The Widevine keybox must be stored in a region of memory that is erased or is inaccessible when the device bootloader is in an unlocked state."
My OnePlus 7 Pro bootloader is unlocked and according to the DRM Info app, I am now L3.
UnrealEgg said:
I'd assume these other phones implement: "The Widevine keybox must be stored in a region of memory that is erased or is inaccessible when the device bootloader is in an unlocked state."
My OnePlus 7 Pro bootloader is unlocked and according to the DRM Info app, I am now L3.
Click to expand...
Click to collapse
So, do you confirm is something safe to be done?
Safe for winedive, of course!
Sent from my OnePlus 5 using XDA Labs
Actually there are some problems to flash the twrp, so use it carefully
Related
Team Win Recovery Project 3.0.4-1 (unreleased)
Notice #1: Please don't wipe your data partition if TWRP cannot decrypt it. Instead, make an effort to gather logs to help solve the issue!
Notice #2: Themes from 3.0.0 to 3.0.3 are incompatible with 3.0.4. Sorry! (small theme engine changes regarding backlight control)
This is a unified build for both the OnePlus 3 and the OnePlus 3T!
WARNING: The OnePlus 3 & 3T stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/oneplusthree.html
Use 3.0.4-1 for now, rather than the builds on twrp.me until an official release happens. You will have problems with 3.0.3 on Nougat!
For now, please download the build from:
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-1-oneplus3.img
Officially 3.0.4 has not been released yet, but it has critical fixes for this device on Nougat, so please be patient.
There is a download link there, as well as instructions on how to flash it.
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Extract/install adb & fastboot to your computer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download TWRP for OnePlus 3 & 3T (oneplus3).
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run the command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted with SuperSU:
Download the latest SuperSU Stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.0.4-1 (build.nethunter.com) - Fix crash when trying to reboot that resulted in TWRP restarting, CAF kernel updates
v3.0.4-0 (build.nethunter.com) - Capability restoration for Nougat, F2FS backport support, EXT4 decryption support
v3.0.3-0 (twrp.me) - Same as 3.0.3-1-rc2. In sync with the OnePlus 3T device tree (3.0.3-1).
v3.0.3-1-rc2 (build.nethunter.com) - Redo the device tree for OOS 4.0, including dynamic encryption support (pull libs from ROM)
FEATURES
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Allows OnePlus full OTA flashing
KNOWN ISSUES
F2FS takes a long time to boot, see below.
If your device is taking more than 10 minutes to boot, you probably have a misc flag enabled that disables passing cmdline, see below.
Reboot buttons don't work in TWRP (restarts TWRP) - disable Ask to install TWRP App on settings page, fix on the way. - fixed in 3.0.4-1
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
WHY WON'T MY DATA DECRYPT / WHY IS MY PASSWORD INVALID IN TWRP?
In order for encryption to work in TWRP, it must pull the encryption libraries from your current ROM. It does this during TWRP boot logo. If you have no ROM installed, then it will fall back to the default OxygenOS 4.0.2 encryption libraries included in the TWRP image.
The crypto daemon in recovery will not be able to decrypt unless the version of the encryption key matches the version of the libraries. This is an unusual restriction that was added by OnePlus.
You can usually fix this by simply booting into your ROM and changing your boot up password. You can change it back or remove it if you want immediately after. This will generate a new crypto key which should be compatible when you next enter TWRP.
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-7.1)
Device tree: https://github.com/TeamWin/android_device_oneplus_oneplus3 (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_oneplus_msm8996 (twrp-7.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project for the OnePlus 3 & 3T, Tool/Utility for the OnePlus 3
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3
Version Information
Status: Stable
Current Stable Version: 3.0.4-1
Stable Release Date: 2017-01-21
Created 2017-01-23
Last Updated 2017-02-07
Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
For the OnePlus 3 only:
OxygenOS 3.2.8: http://s3.amazonaws.com/oxygenos.on...6_OTA_017_all_1611182000_fbe1471194d64b3e.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...16_OTA_039_all_1701140133_89fcc9baba94e4c.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
For the OnePlus 3T only:
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...3TOxygen_28_OTA_041_all_1702081824_e3a712.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
jcadduono said:
Team Win Recovery Project 3.0.4-0 (unreleased)
Click to expand...
Click to collapse
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
peshellas said:
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
Click to expand...
Click to collapse
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
RohanAJoshi said:
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
Click to expand...
Click to collapse
You re Right mate, i know, i have been here since the very old days, I thought i had deleted ot, and continued, apparently not. Thanks for the tip, didn't know about the bug.
ext4 decrypted fine on OnePlus 3 OOS 4.0.2.
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
fbf2201 said:
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
Click to expand...
Click to collapse
Both EXT4 and F2FS should work out of the box now.
No flashing needed.
Hello and thanx for the hard job.
I wanted to try a clean install starting from stock, hoping to correct my issue with twrp black screen.
I need your help. Here is what I've done :
- Restore stock with the unbrick tool
- Update to Nougat 7.0 and OOS4.0.2 via oneplus update
- Unlock bootloader
- Flash twrp 3.0.4-0 via fastboot
- Flash no-verity-opt-encrypt-5.0
- Flash RR rom
- Wipe data and Dalvik
- Reboot.
This is the first time it made it to me. It ask me a password when it boot. I saw a lot of post about that, but I can't understand how to solve it.
Can someone help me please ? My phone is OP3T
Hello, thanks for the super-useful tool. TWRP has been my goto recovery for as long as I have been rooting (days of htc-hd2). I am experiencing the following issues with v3.0.2-1 (all my checkpoint backups are in that version).
* Device = op3
* If it helps, this was a OOS 4.0.1 backup. I was trying to restore it because of a 4.0.2 upgrade failure attempt
* restore hangs at 100% after the backup is complete.
* After waiting for nearly 15 mins, I used the power down to restart the phone - i had lost recovery
* tried to re-install recovery. but when twrp boots - it doesn't get to main menu
* Oddly enough op recovery installs and boots into fine. Which is what I am on.
I am currently on stock recovery without root unable to restore backup ups in twrp and in titanium backup
any thoughts?
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
Its a unified version
ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Thanks your reply was really helpful:laugh:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Abaddon said:
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Click to expand...
Click to collapse
There was two links in the OP, one for 3.0.3-1 mentioning "unified", and one for 3.0.4 with only "oneplus3".
As I knew the dev was working on both version and still supplies 3.0.3-1 test releases in Op3T thread that were newer than the 3.0.4 he built ; and as the changelog did not mention the unification for 3.0.4, for sure, OP was not clear at all.
Is this 3.0.3.x or 3.0.4.0 backward compatible with Marshmallow ROMs?
chancex said:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Click to expand...
Click to collapse
You want to update a custom rom which by definition has no issue with dm-integrity (only present in stock boot image), so if you don't have any issue keep your recovery.
It seems though that latest version has a minimized risk of issues with f2fs so why not updating it?
cultofluna said:
Thanks your reply was really helpful[emoji23]
Click to expand...
Click to collapse
He was right, the thread's title says clearly 3 and 3T.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/discovery
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][OFFICIAL][discovery][9] LineageOS 16.0, ROM for the Sony XA2 Ultra
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2019-03-01
Last Updated 2020-02-28
How to flash latest firmware
[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261769960 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?
Flashed this morning and it works beautifully. Fast, sweet pie. Thanks @LuK1337!
newbie here. Just wondering after flash custom firmware, is it still possible to restore the xa2 ultra to stock ota?
Thanks.
WangYcca said:
newbie here. Just wondering after flash custom firmware, is it still possible to restore the xa2 ultra to stock ota?
Thanks.
Click to expand...
Click to collapse
Yes.
great work thanks you i have flash the rom 1/3/19 and test now all items so is fast and stable whith root magisk work su work my only problems is 2 now i dont know how to install in phone twrp and second big problem is how to hide in start phone the black boot logo of sony unlocking bootloader screen ,( if iknow any body please tell me how to fix this thanks a lot ) . thanks again for great work guys save my phone respect.
sorry for my bad english
install os in my xperia xa2 ultra 4213
the system works well. However the 15.1 root addon seems not working on 16.
In the developer options, I do see root access option for apps/adb, but doesn't matter which one is chosen, still no root access.
WangYcca said:
the system works well. However the 15.1 root addon seems not working on 16.
In the developer options, I do see root access option for apps/adb, but doesn't matter which one is chosen, still no root access.
Click to expand...
Click to collapse
Who'd have thought that something meant to be used with 15.1 won't work with 16.0.
I can't seem to get the radio working after following these instructions. I downloaded the latest firmware for my phone. H223 Customized US. Flash seemed to go fine. When typing the fastboot command I get the following error: Setting current slot to '`' FAILED (remote: 'Invalid Slot Suffix')
Finished. Total time: 0.004s
I tried setting it manually to both A and B but neither worked. I have no idea what I'm doing wrong
GhostCow said:
I can't seem to get the radio working after following these instructions. I downloaded the latest firmware for my phone. H223 Customized US. Flash seemed to go fine. When typing the fastboot command I get the following error: Setting current slot to '`' FAILED (remote: 'Invalid Slot Suffix')
Finished. Total time: 0.004s
I tried setting it manually to both A and B but neither worked. I have no idea what I'm doing wrong
Click to expand...
Click to collapse
Join my irc channel?
(see my signature)
Anyone else getting bad screen freeze? Like the touches dont read right?
Scruffdog1978 said:
Anyone else getting bad screen freeze? Like the touches dont read right?
Click to expand...
Click to collapse
In my case, while an app is launching, the screen will freeze about a second. Once it is launched, it runs smoothly.
Many thanks for your outstanding contribution. I have flashed build 02.03.2019, gapps nano, rooted with magisk 18.1 and it is working pretty much good exept few things. Every time after instaling any magisk module phone is going to bootloop right after restarting, volume up and power 2,3 times fix the restart. Fingerprint reader stop working and it's menu disapper sometimes from settings/securitym,restart helps. Button recent sometimes does not show recent apps, restart helps. Chrome FC after attemt to instal any apk downloaded. No downloaded galery app is allowed to delete any picture from storage. Radio FM is working really well, much better than stock one.
Update to 20190304 with "updater" (OTA) gives a bootloop? Can i download new build, flash using TWRP and Keep user data?
jnappert said:
Update to 20190304 with "updater" (OTA) gives a bootloop? Can i download new build, flash using TWRP and Keep user data?
Click to expand...
Click to collapse
You probably have mismatched firmware between A and B if that's a thing. Follow #2.
LuK1337 said:
You probably have mismatched firmware between A and B if that's a thing. Follow #2.
Click to expand...
Click to collapse
But is there a way to flash the update in twrp or the lineage recovery?
Aklenz07 said:
But is there a way to flash the update in twrp or the lineage recovery?
Click to expand...
Click to collapse
What update?
LuK1337 said:
What update?
Click to expand...
Click to collapse
The ROM update?
Aklenz07 said:
The ROM update?
Click to expand...
Click to collapse
Why would you do that?
LuK1337 said:
Why would you do that?
Click to expand...
Click to collapse
Because I get a bootloop if I do the normal way and I don't have time to do #2 to get it working.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Backups works
- Flash Rom works
- Fastboot boot command support
- Compatibility.zip error fixed
- Vela fully supported
- Android Q Support
- Android 11 Decryption
Download:
TWRP 3.4.0-10 Unofficial by mauronofrio
TWRP 3.4.0-0 Unofficial by mauronofrio
TWRP 3.3.1-3 Unofficial by mauronofrio
TWRP 3.3.1-2 Unofficial by mauronofrio
TWRP 3.3.1-0 Unofficial by mauronofrio
Official Builds(The unofficial one is always more updated and more supported)
To Flash the TWRP:
if it's the first time you flash the TWRP or you are getting problems of TWRP lost or device doesn't boot after flashed magisk or something else you need to flash a script to patch your vbmeta:
VBMETA PATCHER
To flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
Flash the VBMETA PATCHER and reboot.
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_pyxis ( It will be available when the twrp will be fully tested)
Using precompiled stock kernel
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
Created 2020-01-04
This TWRP is not tested, but it should work for all. This TWRP should support pyxis and vela at the same time. If someone test it, please let me know. TWRP is perfectly working
mauronofrio said:
This TWRP is not tested, but it should work for all. This TWRP should support pyxis and vela at the same time. If someone test it, please let me know.
Click to expand...
Click to collapse
Worked Perfectly
Many thanks
and best regards
m_a_omar said:
Worked Perfectly
Many thanks
and best regards
Click to expand...
Click to collapse
On which device you tested it?
Thanks for your work.
Installed without problems. Now I make a copy of security and restored, no issues. Later I try to flash a ROM.
kgtlrt said:
Thanks for your work.
Installed without problems. Now I make a copy of security and restored, no issues. Later I try to flash a ROM.
Click to expand...
Click to collapse
Which device do you have?
Mi 9 Lite works!?
Working great on pyxis, just used to flash Magisk 20.2
Thank you!
Pixys
Running smoothly on Mi 9 Lite Pixys: D Thanks!
Finally multilingual and no self-promotion like other TWRPs here. Very good! Flash with Miui11 on Android 10 base ok.
-> Mi 9 Lite
So it's compatible for both Android 9 and 10?
Has anyone tried to create TWRP back up with this version?
Sent from my MI CC 9 using Tapatalk
Seems to work but somehow i messes up my device
WHat i noticed:
Booting the recovery works, backups to external SD also seems to work. I did a factory reset and wiped /system but after that i could not boot to the recovery anymore. It showed:
downloading 'boot.img'...
OKAY [ 1.937s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.953s
Additionally, the recovery only shows garbled names when browsing /sdcard. Is this a bug?
KRKroenen said:
WHat i noticed:
Booting the recovery works, backups to external SD also seems to work. I did a factory reset and wiped /system but after that i could not boot to the recovery anymore. It showed:
downloading 'boot.img'...
OKAY [ 1.937s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.953s
Additionally, the recovery only shows garbled names when browsing /sdcard. Is this a bug?
Click to expand...
Click to collapse
No this is not a bug, it's just something new in android, you shouldn't wipe system and vendor or you will take always these problems, to fix this you have to flash a fastboot rom.
k3lcior said:
So it's compatible for both Android 9 and 10?
Click to expand...
Click to collapse
It's compatible with both
Install to mi 9 Lite and when try to backup get error 255
Sent from my MI 9 Lite using Tapatalk
mauronofrio said:
No this is not a bug, it's just something new in android, you shouldn't wipe system and vendor or you will take always these problems, to fix this you have to flash a fastboot rom.
It's compatible with both
Click to expand...
Click to collapse
So what i noticed is, that the contents of /sdcard show properly when /data was encrypted and you provide the correct password to decrypt it. If you do a factory reset, /data is unencrypted automatically and the contents of /sdcard show up as strange names.
Xiaomi mi9 lite, works this TWRP.
I have installed through twrp, I do not put the password and the folders in Install appears with numbers and letters only in internal storage (and correctly in SD).
I have put the security password of the mobile, and the folders appear correctly in Install.
In both cases, folders appear with their correct namer in the internal TWRP browser.
Backup done correctly in 384 seconds. Thanks.
SORRY, I HAVE ANDROID 9 PFCEUUXM 11.3.4.0 ESTABLE
minotavros said:
Install to mi 9 Lite and when try to backup get error 255
Sent from my MI 9 Lite using Tapatalk
Click to expand...
Click to collapse
This is usually caused from double apps or multi users
minotavros said:
Install to mi 9 Lite and when try to backup get error 255
Sent from my MI 9 Lite using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632/amp/
mauronofrio said:
Which device do you have?
Click to expand...
Click to collapse
mi 9 lite android Q
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
I built this from source because I love crDroid and our main camera doesn't work at all (and other various small nuisances) on the OnePlus 9 Pro crDroid rom. Proceed with caution, this is my first rom. However, things seem stable enough to call it weekly.
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Download LOS recovery
Download Tiny ADB & Fastboot
Download arm64 gapps (tested with NikGapps Canary Core Gapps)
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20211212-recovery-lemonade.img
Reboot to recovery with following command fastboot reboot recovery
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Now adb sideload latest gapps package with adb sideload gapps.zip
(if Gapps fails saying it could not mount system, boot to rom, then back to recovery and try sideloading Gapps again)
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
Might not work until we are official again.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://crdroid.net/lemonade
Changelog:
Changelogs from OP9Pro crDroid since last build should mostly apply:
Initial crDroid 7.13 code base
Updated to December 2021 security patches
Updated to clang 14.0.0
Updated SQLite
Updated libjpeg-turbo
TWRP is included
Some other small changes
Misc fixes and overall improvements
Updated translations
Known issues:
Flashing via USB C Thunderbolt 4 ports may brick your device to edl only mode requiring multiple msm restores to fix.
USB-OTG not working for me at least.
Looking for additional feedback to see.
Visit official website @ crDroid.net
crDroid Lemonade/Lemonadep Telegram
crDroid Community Telegram
Donate to help the crDroid team pay server costs
Donate to buy the maintainer a beer
Reserved
What is the way to go back to normal root 1.2.7.7 if I dont decide to revert back?
Do I still do ADB Sideload even with TWRP?
Don't use twrp for now, use lineageos recovery. When oneplus9 pro crdroid can flash from twrp I will make that ability available here.
If you have a backup made from twrp, I don't see why restoring from it wouldn't work.
Alright sounds good brother.
Glad to see this here for the 9 stoked. I ran on my Verizon variant op8 unlocked for a long time. Very nice.
audalics said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
I built this from source because I love crDroid and our main camera doesn't work at all (and other various small nuisances) on the OnePlus 9 Pro crDroid rom. Proceed with caution, this is my first rom.
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Until TWRP is ready, this version of crDroid comes with prebaked core Gapps
Download LOS recovery
Download Tiny ADB & Fastboot
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20210615-recovery-lemonadep.img
Power off and reboot to recovery by pressing VOL down + Power from shutdown state
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
When ready
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://www.dropbox.com/s/xkd5augxh37cfdk/crDroidAndroid-11.0-20210625-lemonade-v7.7.zip
Changelog:
Main camera sorta works
Camera cutout size and position corrected
Fingerprint hardware fixed
Fingerprint ui element fixed
Other various fixes for op9 vs op9pro
Known issues:
Camera app crashes when switching modes or to selfie camera.
Video recording not working.
Looking for additional feedback to see.
Visit official website @ crDroid.net
crDroid Lemonade Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Click to expand...
Click to collapse
Hi why i have ' E:error 21
package is for product oneplus9 but expected oneplus9pro
Even when i have oneplus 9?
papad13 said:
Hi why i have ' E:error 21
package is for product oneplus9 but expected oneplus9pro
Even when i have oneplus 9?
Click to expand...
Click to collapse
You sure you sideloading correctly?
mattie_49 said:
You sure you sideloading correctly?
Click to expand...
Click to collapse
Yes but i flashed the oneplus 9 pro version of 'crdroid' in the begining .
And noew i see in the product name lahaina. I thing this is the oneplus 9 pro name ?
papad13 said:
Yes but i flashed the oneplus 9 pro version of 'crdroid' in the begining .
And noew i see in the product name lahaina. I thing this is the oneplus 9 pro name ?
Click to expand...
Click to collapse
Op9p is pro
papad13 said:
Hi why i have ' E:error 21
package is for product oneplus9 but expected oneplus9pro
Even when i have oneplus 9?
Click to expand...
Click to collapse
I have updated op to include instructions for resetting the device name if you've previously flashed a op9pro rom
I also have the same error. I tried it a hundred times.
illusiveairforce said:
I also have the same error. I tried it a hundred times.
Click to expand...
Click to collapse
Have you flashed the boot.img I added to the op? I also received this error in testing since I had flashed the OP9Pro crDroid build.
illusiveairforce said:
I also have the same error. I tried it a hundred times.
Click to expand...
Click to collapse
Your coming from aospa and it's built for op9 pro. So if you didn't msm between there is your issue.
mattie_49 said:
Your coming from aospa and it's built for op9 pro. So if you didn't msm between there is your issue.
Click to expand...
Click to collapse
I did msm already but no fix for the name
audalics said:
Have you flashed the boot.img I added to the op? I also received this error in testing since I had flashed the OP9Pro crDroid build.
Click to expand...
Click to collapse
Yep you are the man, Thanks. That worked
Yeah I guess I didnt msm. Now I kind of got all screwed up. I had to reset and wipe a bunch of times. fastboot the 1.2.7.7DA and then installed Magisk. Now my phone bootloops FOREVER but then finally gets to the homescreen. im talking like 15-20mins. It actually does the boot screen twice. I am lost. Can someone help me get back to square one?
Should I update local storage and do 1.2.7.7 all over again or what
illusiveairforce said:
Yeah I guess I didnt msm. Now I kind of got all screwed up. I had to reset and wipe a bunch of times. fastboot the 1.2.7.7DA and then installed Magisk. Now my phone bootloops FOREVER but then finally gets to the homescreen. im talking like 15-20mins. It actually does the boot screen twice. I am lost. Can someone help me get back to square one?
Should I update local storage and do 1.2.7.7 all over again or what
Click to expand...
Click to collapse
Msm now if one is available for your variant. Or use fastboot stock rom in the threads.
ok please help me out.
So I do adb devices and my device shows up.
i do adb reboot bootloader, works and goes to Fastboot, but then nothing i type works. I do fastboot boot patched_boot_11.2.7.7.LE25DA.img and it just waiting for device.
Now heres another. When I turn my game on, Pubg mobile. It says please enable permissions and I do it. But it still says media only. wont let me do files. i dont get it. Is it cause I accidently mounted system or something.
Please help
illusiveairforce said:
ok please help me out.
So I do adb devices and my device shows up.
i do adb reboot bootloader, works and goes to Fastboot, but then nothing i type works. I do fastboot boot patched_boot_11.2.7.7.LE25DA.img and it just waiting for device.
Now heres another. When I turn my game on, Pubg mobile. It says please enable permissions and I do it. But it still says media only. wont let me do files. i dont get it. Is it cause I accidently mounted system or something.
Please help
Click to expand...
Click to collapse
Make sure your instructions call for fastboot boot <img> instead of fastboot flash boot <img>, mixing up the two would cause issues.
As for the Pubg issue with permissions, I am unsure of what you mean.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-S with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning, we would like to thank:
LineageOS & CM (R.I.P.) team
Evolution X Team & @AnierinB
GZOSP team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Whole Android Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 17.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal (and others) GApps packages could have issues, so try using MindTheGapps if you have any issues with other GApps packages
MindTheGapps: Download from HERE
Due to new light sensor, autobrightness is a mess for now. But will be fixed soon I hope.
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases, these apps include proprietary libs/code and cannot be included in the device trees on GitHub or we risk having the ROM banned from GitHub. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from GitHub, and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is how users can/should install updates most of the time, this can be done with the built-in updater service or with a custom recovery.
Q. How do I 'dirty flash' builds?
A 1. For "A only" devices: Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
A 2. For "A/B" devices": Wipe the ART/Dalvik cache. Flash the ROM, reboot to the recovery, flash GApps, your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android S. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)16.08.2022 Weeklies were the last builds based on OOS11 base.Starting with 23.08.2022 Builds, we are switching to OOS12 Base.BE ADVISED !!!!DO NOT FLASH NEW WEEKLY OVER 16.08.2022 Builds via OTA. Please follow the instructions in the 2nd post for FW update first, then you can flash New Weeklies.
If you are flashing using adb sideload, GAPPS needs to be flashed on every dirty flash as it's mentioned above.
If you are flashing using OTA, no need to flash GAPPS, .
Currently supported Root Solution:
Magisk versions >= feel free to report. Didn't tested myself.
Instructions for OTA ("Over-The-Air" Updates) on "A only" devices (not A/B):
Using on board recovery will be enough mostly for your operations.
Instructions for OTA ("Over-The-Air" Updates) on "A/B" devices:
Open the updater app, download the update, then press install and wait for the process to finish (feel free to let it run in the background), then press reboot when prompted, there isn't any need to flash GApps separately
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
GitHub - AICP/kernel_oneplus_sm8250
Contribute to AICP/kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Device tree source:
AICP/device_oneplus_instantnoodle
Device tree for OnePlus 8. Contribute to AICP/device_oneplus_instantnoodle development by creating an account on GitHub.
github.com
Follow this guide if you want to extract the vendor blobs
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on GitHub
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)
Information:
ROM OS Version: 12.1
Kernel: Linux 4.19.11-perf
ROM {Firmware|Vendor} required: Latest OOS 12 (At least C20/21 firmware)
Status: STABLE
Release Date: 23-08-2022
You want to see a "normal" night at the "DEV office", click here!!
For further support you can visit our TG Channel:
AICP Support Channel for OnePlus 8 Devices
PLEASE BE ADVISED - YOU MUST UPDATE TO OOS12 FIRMWARE BEFORE INSTALLING THE 8/23 UPDATE.
If you are on OOS11 based Stock or Custom ROM:
Best approach is to flash stock OOS11 and update to the latest for your device OOS12 OTA.
While it's done, you can follow the flashing instructions over stock OOS12 given below.
Click to expand...
Click to collapse
The current firmware upgrade path is available here as found on the Op8 series Telegram support group:
Spoiler
1. Boot up AICP recovery
2. Go to "Advanced" -> "Enable ADB"
3. Check your DDR type using the following command:
adb shell getprop ro.boot.ddr_type
or in case getprop returns an empty value, use:
adb shell cat /proc/devinfo/ddr_type
4. Download firmware (C33 recommended, minimum C20/21 required) from here:
FirmWares - Google Drive
drive.google.com
5. Go to "Advanced" -> "Enter fastbootd"
6. Execute following commands after opening a command line in the fw directory:
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
7. Flash correct XBL files
* For DDR type 0 (DDR4):
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
* For DDR type 1 (DDR5):
fastboot flash --slot=all xbl_config xbl_config_lp5.img
fastboot flash --slot=all xbl xbl_lp5.img
8. Boot your recovery from here and then install the new update:
Android12L - Google Drive
drive.google.com
9. Now, you can update via OTA safely.
IF YOU ARE ON STOCK OOS12
These instructions are for you:
Spoiler
Thanks to @Anierin_Bliss
First Time Install / Clean Flash
1. Have an unlocked bootloader & OOS 12 (C20 - C33) flashed to both slots.
2. Download vbmeta, recovery, ROM and GAPPS (optional) for your device from here: https://drive.google.com/drive/folders/1A2SeD6YFKJ2S-iiAKmyfgnrEeJz8zjNm
3. Reboot to bootloader
4.
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload ROM.zip -> reboot recovery -> adb sideload GAPPS.zip
7. Format data, reboot to system & Enjoy !
Hi thanks all for your tremendous efforts
If we are on OOS 12 then do we have to revert to OOS11 ?
adsxlnc said:
Hi thanks all for your tremendous efforts
If we are on OOS 12 then do we have to revert to OOS11 ?
Click to expand...
Click to collapse
We are preparing OOS 12 based trees. Till then, yes - please go back to latest OOS 11 then flash AICP. 12.1
What a pleasant surprise, love your work semdoc, can't wait to get home and flash this.
Wow great rom, I was looking for one with the built in adblock and no gapps. Fast, smooth, and very light weight. I also love the custom work you did on the QS <3
Amazing work, I like the easy to follow instructions as well. I was on the Tmobile version that was OOS 11. After a long research I flashed the global version of OOS 10, then OTA to OOS 11. I tried to flash multiple different A12 roms, but all of them crashed. This was the only A12 rom that worked for me. The system runs smoothly, I also like all the added features. I used MindTheGapps and Magisk 25.1, both work correctly. I then used Konabess to overclock the gpu to 925 MHz.
Issilar said:
Amazing work, I like the easy to follow instructions as well. I was on the Tmobile version that was OOS 11. After a long research I flashed the global version of OOS 10, then OTA to OOS 11. I tried to flash multiple different A12 roms, but all of them crashed. This was the only A12 rom that worked for me. The system runs smoothly, I also like all the added features. I used MindTheGapps and Magisk 25.1, both work correctly. I then used Konabess to overclock the gpu to 925 MHz.
Click to expand...
Click to collapse
Have you try Nameless rom ever brother,, i have the same t mobile version of ur phone,, nameless isnt work for me. qualcomn crash damp happened
Hiya! I've turned on the always-on display, and have noticed that i have to turn the screen on to get the fingerprint sensor to work (most of the time. I think it's active a few seconds after screen lock?)! Is there any way around this? OxygenOS seemed to turn the sensor on with a finger press no matter the AOD state
cheers!
Hey I was on T-Mobile Android 11. I tried to unlock the bootloader and flashed this ROM. The phone does not capture the network anymore. Also the GAPPS installation via adb sideload is failing. Any idea?
ditomathew said:
Hey I was on T-Mobile Android 11. I tried to unlock the bootloader and flashed this ROM. The phone does not capture the network anymore. Also the GAPPS installation via adb sideload is failing. Any idea?
Click to expand...
Click to collapse
I've had other roms do this before, run MSM restore tool, then unlock bootloader (and adb debugging) then re do the installation
RogueVisual said:
I've had other roms do this before, run MSM restore tool, then unlock bootloader (and adb debugging) then re do the installation
Click to expand...
Click to collapse
Thanks I did that, and now I reinstalled.
allen-evan said:
Have you try Nameless rom ever brother,, i have the same t mobile version of ur phone,, nameless isnt work for me. qualcomn crash damp happened
Click to expand...
Click to collapse
Nameless works just fine on my device, TMO OP8
Small but IMPORTANT note for anybody experiencing issues coming from OOS and trying this for the first time. I could not get the ROM to boot until I flashed the "copy partitions" zip from Lineage. (https://wiki.lineageos.org/devices/...suring-all-firmware-partitions-are-consistent).
Until I flashed this I would install the ROM and then try to reboot to recovery and it would go straight to the bootloader. If I switched back to the other slot I could get back to recovery but could not proceed further.
So my install instructions looked like this: (because I was doing some trial and error I had installed the ROM a few times hence it being here twice)
adb sideload ROM.zip (I believe you can skip this one but cannot say for certain) -> adb sideload copy-partitions.zip -> adb sideload ROM.zip -> reboot to recovery -> adb sideload GAPPS.zip -> reboot to system
If you get stuck on the bootloader you can use fastboot to check your active slot and then switch back to the previous slot to get back into recovery.
Check current slot:
Code:
fastboot getvar all
Look for the line that says:
Code:
(bootloader) current-slot
The two options are "a" or "b". Then switch to the other slot with:
Code:
fastboot --set-active=a
OR
Code:
fastboot --set-active=b
Another small note, "Apply Update > Install from ADB" (terms are from memory, should be close enough) inside of the Lineage Recovery is what you are looking for to enter adb sideload mode. I had used TWRP previously and didn't know how to get this working at first in Lineage Recovery.
is it possible
to install with official twrp recovery ??
Does this rom works with OnePlus 8 Verizon 5G UW (IN2019)? Does the SIM work?
I tried using the Android 12 based builds but end up in soft-bricked state every time where only MSM can recover. Why is this?
I have T-Mobile OP8, unlocked. I just MSM back to A10, unlock bootloader, convert to global, update to latest A11, install lineage recovery, flash EU A12 firmware, flash ROM, reboot to bootloader -> softbricked at this point with QDLoader in device manager.
Tried asking in telegram but the bot banned me for flooding for sending exactly 1 message.
graycorgi said:
I tried using the Android 12 based builds but end up in soft-bricked state every time where only MSM can recover. Why is this?
I have T-Mobile OP8, unlocked. I just MSM back to A10, unlock bootloader, convert to global, update to latest A11, install lineage recovery, flash EU A12 firmware, flash ROM, reboot to bootloader -> softbricked at this point with QDLoader in device manager.
Tried asking in telegram but the bot banned me for flooding for sending exactly 1 message.
Click to expand...
Click to collapse
ROM {Firmware|Vendor} required: Latest OOS 11
Larkin24 said:
ROM {Firmware|Vendor} required: Latest OOS 11
Click to expand...
Click to collapse
They have ones for Android 12 firmware on their support telegram channel for this device (link in OP). I only posted here because their telegram bot bans you without warning if you type too long of a message.
graycorgi said:
They have ones for Android 12 firmware on their support telegram channel for this device (link in OP). I only posted here because their telegram bot bans you without warning if you type too long of a message.
Click to expand...
Click to collapse
SORRY NO OOS 11
I have the same phone OOS 11 Firmware.
Latest tmoble Firmware
OnePlus Updates Tracker
An automated channel that tracks OnePlus Oxygen and Hydrogen OS ROMs releases. https://github.com/androidtrackers/oneplus-updates-tracker More automated channels that you may like: @yshalsager_projects Developed by: @yshalsager
t.me