Database Info

[Recovery] Official TWRP for the OnePlus 3 & 3T

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.

[TWRPv3.x.x]Tank Xtreme Pro Recovery

{
"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"
}
.
Screenshots attached below.
TeamWin Touch Recovery for BLU Tank Extreme Pro
Code:
* [U][B]Disclaimer[/B][/U]
* Your warranty is now void.
* I am 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 recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Older Version
CHANGELOG for 3.1.1-0:
TWRP 3.1.1 is Out, Brings Minor Fixes
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
FEATURES
Backup & Restore fully functional
Micro SDcard and USB OTG storage support
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
Full SELinux support
Built with android-7.0 TWRP tree
CHANGELOG for 3.2.0-0:
TWRP 3.2.0 is now out
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP’s backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
CHANGELOG for 3.2.2-0:
TWRP 3.2.2-0 brings ADB fixes and improvements to OTA updates
adb backup fixes
OTA style update zips will now install automatically without prompting for decrypt
minor tweaks to handling date/time on Qualcomm devices
updates to some language translations
CHANGELOG for 3.2.3-0:
TWRP 3.2.3-0 is out now for most currently supported devices.
Fix automatic installing of OTA zips on encrypted devices
Remove SuperSU from TWRP
Support both md5 and md5sum file extensions when doing MD5 checking for zip files
BUGS:
MTP NOT Recognize Driver--So No mtp connection-- work-around for this now, is to use "mount as USB drive", this will allow similar function as MTP, but only for your micro-SDcard
SUPPORT: Post your questions below. I'll answer whenever I get time.
INSTALLATION
Most devices can be updated quickly and easily within TWRP if you already have version 3.x.y-z or higher installed
1) Download the latest version from DOWNLOAD TAB
2) Copy that file to your sdcard
3) Reboot to TWRP
4) Hit INSTALL and tap the "Images..." button in the lower right
5) Browse to the location of the TWRP image (recovery.img) on your device and select it
6) Select RECOVERY from the PARTITION list and swipe to flash
7) Go to Menu: Reboot recovery
If First time install
You can install with spft as described in following link BUT FIRST NEED unlock bootloader.
Instructions for Flash stock recovery or Custom recovery MEDIATEK devices only
You can also install with fastboot commands after unlocking bootloader.
****UNLOCKING BOOTLOADER WILL CAUSE WARNING ON SCREEN WHEN POWERING ON****
****WARNING WILL PAUSE THE BOOT PROCESS FOR % SECOND DELAY , Not big problem****
BOOTLOADER UNLOCK
How to Unlock Bootloader via Fastboot
1. Setup ADB and Fastboot on your PC.
2. Enable USB debugging and OEM Unlock on your Android device.
1). open settings
2). scroll to about phone
3). tap "Build number" 7 -8 times
4). go back, now you have new menu option"Developer options
5). open and make sure "off" switch at top is slid to right to turn on
5). slide switches for OEM unlocking and ADB debugging
6). Now connect usb cable from PC to Phone
7). phone should have popup window asking for authorization to connect with ADB
3. Connect your device to the PC with a USB cable.
4. Open a command window on your PC.
5. Boot your device into bootloader mode using the following command:
Code:
adb reboot bootloader
└ You may get a request to authorize USB debugging on the device, accept it.
6. Once your device is in bootloader mode, issue the following command to unlock bootloader:
Code:
fastboot oem unlock
You get a confirmation screen on your device. Press Volume Up button to highlight Yes and press Power button to select it.
This will begin bootloader unlocking process, which shouldn’t last more than couple of minutes.
7. Once bootloader is unlocked, your device will reboot into bootloader mode. You need to boot it into system now using the command below:
Code:
fastboot reboot
During reboot, your device will go through a factory reset and then finally boot into system.
RECOVERY INSTALL
1. make sure developer options is enabled
1). open settings
2). scroll to about phone
3). tap "Build number" 7 -8 times
4). go back, now you have new menu option"Developer options
5). open and make sure "off" switch at top is slid to right to turn on
5). slide switches for OEM unlocking and ADB debugging
6). Now connect usb cable from PC to Phone
7). phone should have popup window asking for authorization to connect with ADB
2. Reboot to bootloader
Code:
adb reboot bootloader
3. Test recovery works for your device
(example commands assume you have the 3.2.0 version of recovery downloaded to the desktop)
Code:
Fastboot boot Desktop/twrp-3.2.0-recovery.img
4. If recovery boots good, then return to bootloader and flash (commands work from in booted twrp)
These steps are what I find to be best order to prevent the stock rom from replacing the stock recovery on boot.
Code:
adb reboot bootloader
fastboot flash recovery Desktop/twrp-3.2.0-recovery.img
fastboot boot Desktop/twrp-3.2.0-recovery.img
adb wait-for-device
adb reboot recovery
ROOT
If your device haven't ROOT:
Thanks to @Chainfire for the file!
Rooting instructions: put the SuperSu...zip on sdcard. Go to TWRP and tap INSTALL. Search the zip file and select. Swipe to install. Reboot system.
Dowload: SuperSU V2.82
DOWNLOADS In Download Tab
SCATTER File
Stock boot ----- Stock recovery
TWRP 3.1.1 ------ TWRP 3.2.0 ------ TWPR 3.2.1 ------ TWPR 3.2.2-0 (based in stock V7.0.04.04_GENERIC 24-05-2018)
-----Added--TWRP 3.2.2-0(repacked)Has ro.secure=0; ro.adb.secure=0; to allow adb while data is wiped.
TWRP 3.2.3-0 [Has ro.secure=0; ro.adb.secure=0; to allow adb while data is wiped.] (based in stock V7.0.04.05_GENERIC 06-08-2018) download in post#2
Note:
After TWRP3.2.2 the partitions for the backup save have been modified to: /dev/block/platform/mtk-msdc.0/by-name/
So if you have a version older than TWRP3.2.2 you should copy the
Root [Internal Storage or MicroSD] / TWRP/ BACKUPS / VCIBIZMR7HT8GES8 / year-month-date-hour-minute-second_BLU_T0010UU_V70040x_GENERIC_dd-mm-yyyy
folder to the new one folder
Root [Internal Storage or MicroSD] / TWRP / year-month-date-hour-minute-second_BLU_T0010UU_V70040x_GENERIC_dd-mm-yyyy
of the version TWRP3.2.2 or last.
We've added the partition for internal storage if you want to create a backup of it. But keep in mind that the more files there are in the internal storage, the larger the size of the backup made and this will depend on your choice and how you can save it to other larger storage capacity.
So be more careful!
Contributors
@lopestom
@Dees_Troy
@teamwin
@vampirefo
Version Information
Status: Beta
Current Beta Version: 3.2.3-0-20181013
Beta Release Date: 2017-12-24
XDA:DevDB Information
Tank Xtreme Pro Recovery, Tool/Utility for all devices (see above for details)
Contributors
mrmazak, lopestom, vampirefo
Version Information
Status: Beta
Created 2017-12-08
Last Updated 2018-10-13

Instructions to unlock and relock bootloader
Instructions to unlock and relock bootloader soo... :silly:
https://youtu.be/5ZVW-XzPCXE
https://youtu.be/Zf6hMqGbC_4

With older version TWRP, does MTP work? I see you list it not working on 3.2.
MTP to me is more important than version of TWRP used.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
With older version TWRP, does MTP work? I see you list it not working on 3.2.
MTP to me is more important than version of TWRP used.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
No, mtp not working at all on this device. The recovery that I used to port older version is yours from life Max. Boh of these on this thread came from lopestom.
Suspect something in kernel, like touch on life Max was problem in kernel. As of last time I checked, sources we're not published from blue yet.

mrmazak said:
No, mtp not working at all on this device. The recovery that I used to port older version is yours from life Max. Boh of these on this thread came from lopestom.
Suspect something in kernel, like touch on life Max was problem in kernel. As of last time I checked, sources we're not published from blue yet.
Click to expand...
Click to collapse
Ok, thanks I will compile a recovery for Tank, see if I have any better luck with it.
I suspect it's the recovery looking for MTP in the wrong place, Android 6 and 7 access to MTP would be different.
Blu Life Max is Android 6, so MTP would be in platform, while tank is Android 7 so would be in virtual.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
Ok, thanks I will compile a recovery for Tank, see if I have any better luck with it.
I suspect it's the recovery looking for MTP in the wrong place, Android 6 and 7 access to MTP would be different.
Blu Life Max is Android 6, so MTP would be in platform, while tank is Android 7 so would be in virtual.
Click to expand...
Click to collapse
@mrmazak tested some TWRP and we have same issue with driver mtp in PC/laptop like Indisponible driver so the device is recognized but cannot open mtp. If we boot ROM so that's recognizing and open.
I tried with libtwrpmtp.so from sbin folder: replacing from other, open to know if need more informations and compared with same lib name of Android 6 as I have mtp working..... So no luck!
Remember: TWRP3.1.1 and 3.2.0 from me is based in Android 7 Nougat TWRP base x32.
As I'm no good with programming to open libtwrpmtp.so to see if have or need specific info so... I hope that you can help better on it...
Congrats and enjoy...
Sent from my BLUBOO Xtouch using XDA Labs

lopestom said:
@mrmazak tested some TWRP and we have same issue with driver mtp in PC/laptop like Indisponible driver so the device is recognized but cannot open mtp. If we boot ROM so that's recognizing and open.
I tried with libtwrpmtp.so from sbin folder: replacing from other, open to know if need more informations and compared with same lib name of Android 6 as I have mtp working..... So no luck!
Remember: TWRP3.1.1 and 3.2.0 from me is based in Android 7 Nougat TWRP base x32.
As I'm no good with programming to open libtwrpmtp.so to see if have or need specific info so... I hope that you can help better on it...
Congrats and enjoy...
Sent from my BLUBOO Xtouch using XDA Labs
Click to expand...
Click to collapse
I don't know about your 3.2 recovery, mrmazak used my Blu Life Max recovery, I told that recovery to look in platform for MTP, that's why I suspect my Blu Life Max recovery is the problem.
If I am correct, just rebuilding a new recovery telling it to look in virtual for MTP should work, if I am wrong it won't, doesn't hurt to try.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
I don't know about your 3.2 recovery, mrmazak used my Blu Life Max recovery, I told that recovery to look in platform for MTP, that's why I suspect my Blu Life Max recovery is the problem.
If I am correct, just rebuilding a new recovery telling it to look in virtual for MTP should work, if I am wrong it won't, doesn't hurt to try.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
I assume you already looked, but, the recovery log shows mtp error , over and over again.
Code:
E:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] response write returned -1, errno: 5, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 22
pretty sure it happens with all versions

The stock boot img has "init.usb.configs.rc"
in this file it sets usb_gadget # for mtp.
there is nothing that I find similar in the twrp.
I am thinking to add this rc file to twrp and import it with the init.rc to see if it changes anything.
***UPDATE*** No change with adding this configfs file
Attached is a listing of all mentins of "mtp" in the stock boot.img ramdisk
this link is in Russian , but google translate helps.
posts #1354 and 1355 reference the same error I see in the recovery log. Also mention addressing the usb_gadget #
.

mrmazak said:
The stock boot img has "init.usb.configs.rc"
in this file it sets usb_gadget # for mtp.
there is nothing that I find similar in the twrp.
I am thinking to add this rc file to twrp and import it with the init.rc to see if it changes anything.
***UPDATE*** No change with adding this configfs file
Attached is a listing of all mentins of "mtp" in the stock boot.img ramdisk
this link is in Russian , but google translate helps.
posts #1354 and 1355 reference the same error I see in the recovery log. Also mention addressing the usb_gadget #
.
Click to expand...
Click to collapse
Oh, well if MTP doesn't work it doesn't work, I compiled my own today, removed MTP tab and just use Mount USB Storage instead, works fine for micro sdcard. I compiled mine using TWRP 8.1 source, and uploaded it to needrom.

vampirefo said:
Oh, well if MTP doesn't work it doesn't work, I compiled my own today, removed MTP tab and just use Mount USB Storage instead, works fine for micro sdcard. I compiled mine using TWRP 8.1 source, and uploaded it to needrom.
Click to expand...
Click to collapse
I just gave this a try, I have noticed something, could be intentional , not sure.
On your other recovery you could flash system as image, this one you cannot.

mrmazak said:
I just gave this a try, I have noticed something, could be intentional , not sure.
On your other recovery you could flash system as image, this one you cannot.
Click to expand...
Click to collapse
Correct something I don't use, that's controlled by recovery.fstab
just use this recovery.fstab if you want that option, unpack recovery and replace recovery.fstab

vampirefo said:
Correct something I don't use, that's controlled by recovery.fstab
just use this recovery.fstab if you want that option, unpack recovery and replace recovery.fstab
Click to expand...
Click to collapse
thanks, is it ok to add this version to the downloads of this thread?

mrmazak said:
thanks, is it ok to add this version to the downloads of this thread?
Click to expand...
Click to collapse
Thanks fine with me.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
Thanks fine with me.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
I've added you as contributor and added your version, with the fstab that has system_image and also cache enabled (because of an error message in recovery.log that stated could not mount cache)

sorry for asking,, can i use this recovery into blu tank xtreme 5.0??
im looking everywhere the method how to root blu tank xtreme 5.0 android 6

gabmika69 said:
sorry for asking,, can i use this recovery into blu tank xtreme 5.0??
im looking everywhere the method how to root blu tank xtreme 5.0 android 6
Click to expand...
Click to collapse
No!
Each device should have the own Custom Recovery.
Sent from my BLUBOO Xtouch using XDA Labs

Please HELP!
Was hung on boot with TWRP installed. Fixed the problem by installing SuperSU to unlock the bootloader. No help needed.

[ROM][Android 10][Android 11]Meizu E3 LineageOS 17.1/18.1 ROM Porting (20210418)

{
"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"
}
Hi there,
I prepared an alpha version of LineageOS 17.1/18.1 for Meizu E3 for your taste about it. Now it so more useable as dev-phone for outdoor YouTube viewing. Do play with it your own risk. I am not responsible any liability, nor any technical support too. So please think twice before taking action. AND be safe to backup ALL partitions before and action taken.
You can visit another thread of Meizu E3 unlock bootloader tutorial from your author, to unlock Meizu E3 without any external tool.
Instruction:
(0) to make it align with latest flyme v8000 fw, update system to v8000 is highly recommended. (20200926)
(1) get the phone unlocked bootloader as above mentioned.
(2)download below mentioned fw (boot.img.signed, system.img, vendor.img, recovery.img) in to a folder like "E3_LOS17.1", unzip and get "vendor_image.emmc.win", "system_image.emmc.win" and "boot.img.signed", rename them as boot.img, system.img, recovery.img and vendor.img
(3)hold power+vol_down and do "fastboot.exe boot recovery.img"
(4)in twrp, backup all partition to /sdcard, aka, "/sdcard/system.img", "/sdcard/persist.img"
(5)in host PC backup from phone and upload all above downloaded and unzip rom.img to phone, procedure like open cmd.exe, "mkdir E3", "cd E3/", "adb.exe pull /sdcard .", "adb.exe push E3_LOS17.1 /sdcard"
(6) twrp install, choose install img, select /sdcard/E3_LOS17.1/system.img, system partition, go
(7) twrp install, choose install img, select /sdcard/E3_LOS17.1/vendor.img, vendor partition, go
(8) twrp wipe, choose data partition, go (your data partition got WIPED, all data are LOST)
(9) wait above finish, go back to PC terminal, cmd.exe, issue "adb.exe reboot-bootloader", then "fastboot.exe boot boot.img"
(10) wait for LOS17.1 boots up
optional steps
(2a) you can choose to phh's quack build instead of jasmine_sprout system image as well. download it from phh's github release channel, unpack the zip, use simg->img tool to get regenerated system.ext2.img; check with linux "file" util and get
[email protected]:/mnt/jasmine_vendor# file /mnt/c/d_drive/whyred_temp/los17_20200111_phh_system.img
/mnt/c/d_drive/whyred_temp/los17_20200111_phh_system.img: Linux rev 1.0 ext2 filesystem data, UUID=05050abd-8baa-4dd4-905c-903071f9ac68, volume name "system" (extents) (large files) (huge files)
Click to expand...
Click to collapse
Note:
(1)Please sure to DO backup all the partitions
(2)Please sure DO NOT to flash boot.img to boot partition, every time use fastboot to boot into LOS17.1 thus can easily restore to flyme8 rom
(3)please sure when revert back flyme8, please DO use your own twrp backup to restore all partition is your first choice. Second choise is by flyme8's recovery from recovery partition, or at least the flyme8 recovery downloaded below. DO NOT use TWRP restore the flyme rom directly, and this can avoid many issues; otherwise you are compulsively to reflash flyme once again at least and all your data partition backup become useless; and if you force restore data partition, it wont help, due to internal hw keystore and crypto salt changes. so step (5) "adb.exe pull /sdcard/ ." is essential.
(4)use twrp recovery to restore data partition might not work at all. so once again, backup by using "adb.exe pull /sdcard ." is important. As said, some partition might get changed by bootloader and internal fw, so hw crypto and salt, keystore partition might get changed too after first boot LOS17.1; and you cant backup these partition at twrp screen operation. and even through if you are expert enough, restoring those partitions in adb shell also might not work at all due to same reasoning.
(5)using "adb.exe pull /sdcard ." is important! this is important so as i said 3 times.
(6)backup all partition by "adb shell" if possible. TWRP only list some of usual partition, and some rarely used partition are not listed. Like i suffered from persist partition wiped out and cant restore without a copy. so do a "dd if=/dev/block/bootdevice/by-name/XXX of=/sdcard/XXX" is a good idea.
(7)I had tried my best to make the all mount as "r/o" as possible, but i CANT guarantee all other partition are safe. So best is do as note(6) said.
Release Alpha 13
==================
Latest alpha release on LineageOS 18.1, camera is not working, check below for detail:
Release Alpha 13 · 99degree/android_vendor_meizu_m851q
This release (Alpha 13) is an alpha release that based on brand new Nokia PL2 LineageOS 18.1 release. Detail refer to below: https://lineageos.org/Changelog-25/ This release have an issue about cam...
github.com
Release Beta 2
==================
Latest stable ROM on LineageOS 17.1
Release Beta 2 (20210221) · 99degree/android_vendor_meizu_m851q
This release aimed to get entire system updated to Feb-05 Security bulletin. Changelog: Update to LineageOS Amber 20210214 Known issue: LineageOS clean (wipe data in TWRP) and first time startup wi...
github.com
Older release:
Release note 20210124
==================
Update dts and libmmcamera module. Camera should be alright, actuator is still in progress.
download release 20210126
Release note 20201214
==================
Update to CAF LA.UM.8.2.r2-03400-sdm660.0
Based on LineageOS Nokia PL2 Dragon build 20201208
This is no longer pure CAF due to adreno older fw logic fail.
Selinux enforced now on
Release note 20201011
==================
Update to CAF LA.UM.8.2.r2-02700-sdm660.0
LineageOS Amber 20201011 release, kernel is no longer pure rely on CAF anymore.
It is due to a adreno fw checking logic fail on older fw.
Release note 20200813
==================
Update to CAF LA.UM.8.2.r2-02500-sdm660.0
LineageOS Amber 20200809 release
Release note 20200705
==================
Some sensors are available.
external speaker (TAS2560 SmartAmp) functioning.
Release note 20200701
==================
(1)Special release! Voice-out-loud for social injustice!
(2)Mobile feature enablement
https://github.com/99degree/LineageOS/releases/tag/20200701
Release note 20200613
==================
First version with earphone sound playing. So YouTube is more than possible! This version shifts to official LineageOS.org Yandex Amber build
https://mirrorbits.lineageos.org/full/Amber/20200607/lineage-17.1-20200607-nightly-Amber-signed.zip
Release note 20200303
==================
Workaround the wifi problem, now wifi is working. boot.img.clear is updated.
Release note 20200223
==================
This is a ported version of LineageOS 17.1 based on this thread so you can download the original version of the build over there. In case of preference in phh's treble quack release, it seemed system.img is working well too.
The solo modification in vendor.img included:
(A) fstab.qcom to disable persist partition mount by "r/o", so no longer as "r/w" mode in order to protect it against lost wifi firmware, lost signal, mac address etc.
(B) replace all file lived in /vendor/firmware/* with flyme8's
The modification in system.img:
NIL
Things verified to work:
LCD PANEL
TOUCH PANEL
BLUETOOTH
USB
CHARGING
WIFI
vibration
earphone w/button
mobile feature
speaker and incoming ringing
GNSS
sensors (luminous, proximate, compass, magnet)
selinux-enforced
front camera
back imx362 camera
back imx350 camera(not tested)
Things not working:
those not listed above is considered not working
ROM download:
https://github.com/99degree/android_vendor_meizu_m851q/releases/tag/20210418 for LOS18.1
https://github.com/99degree/android_vendor_meizu_m851q/releases/tag/20210221 for beta 2
release 20210126
release 20201214
https://github.com/99degree/LineageOS/releases/tag/20201011
https://github.com/99degree/LineageOS/releases/tag/20200813 for boot.img and recovery.img
https://github.com/99degree/LineageOS/releases/tag/20200705 system and vendor image
https://github.com/99degree/LineageOS/releases/tag/20200701
https://github.com/99degree/LineageOS/releases/tag/20200613
https://github.com/99degree/LineageOS/releases/tag/20200223
https://github.com/99degree/LineageOS/releases/tag/20200303 for boot.img.clear
Repositories:
https://github.com/99degree/
kernel https://github.com/99degree/android_kernel_meizu_m851q
vendor & release https://github.com/99degree/android_vendor_meizu_m851q
So if you wanted to cook it yourself, please find necessary file with you. All needed files are hosted either in GitHub and LineageOS official Amber/PL2 build),
Please consider to show your support by donation or even YouTube clicks. Last and most importantly, happy ROM flashing and stay away from corona-virus outbreak!
Regards,
99degree

Can you public source code of kernel with device driver? Thank mate

thinhx2 said:
Can you public source code of kernel with device driver? Thank mate
Click to expand...
Click to collapse
Yes, I am on the way to clean up those code. once ready will upload to github and take vlog. Stay tuned.

99degree said:
Yes, I am on the way to clean up those code. once ready will upload to github and take vlog. Stay tuned.
Click to expand...
Click to collapse
Nice sir

99degree said:
...
kernel https://github.com/99degree/android_kernel_meizu_m851q
...
Regards,
99degree
Click to expand...
Click to collapse
How did you manage to port the kernel from code aurora? Any guide or so? I have Santin K1 (almost the same hardware as meizu) Wanna try to port kernel source.

Spencer_D said:
How did you manage to port the kernel from code aurora? Any guide or so? I have Santin K1 (almost the same hardware as meizu) Wanna try to port kernel source.
Click to expand...
Click to collapse
No! Not the way you through. I managed to clone kernel from CAF and search for hardware info. By app "device info hw", google and find some public available driver (basically touch driver and sound driver), add them to CAF tree then analysis the device tree dtb->dts difference. Move them to new dtsi and compile it with kernel as a whole. Then make use of LineageOS Yandex Amber ROM, modify and make it boots into LineageOS, that's it.
So best wish your development on SantinK1.

[oneplus3/t][Official] Droidian (Debian Bookworm) for OnePlus 3/T

Code:
/*
* I am 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 me for messing up your device, I will laugh at you.
*/
{
"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"
}
Droidian is a GNU/Linux distribution based on top of Mobian, a Debian-based distribution for mobile devices. The goal of Droidian is to be able to run Mobian on Android phones.​This is accomplished by using well-known technologies such as libhybris and Halium.​​## What works​
WIFI
Audio
Video Playback
USB-OTG
Cellular Data
Calls/SMS
Bluetooth
Wireguard
Flashlight
GPU (Works well in WayDroid, partially in Droidian)
See full list here
## What doesn't work​
Camera
VoWifi
You tell us
Old UNOFFICIAL installation steps
Spoiler
This steps and UNOFFICIAL build of droidian have been abandonned and is deprecated, you're on your own there ! We recommand to follow official steps below​
## Required Files​
ADB commands and stuff
TWPR Treble : https://mega.nz/folder/UgdQRYSD#8s-_u2HJQZDEqNnFOnejxQ
You'll find it in : Recovery_(System-As-Root_Compatible) > twrp-op3treble-3.3.1-1.img
Latest firmware for your phone (at the writing time: 9.0.6) : https://github.com/nvertigo/firmware-3t/tree/master/archive (like version oxygenos-9.0.6-no-alipay-firmware-3.zip or oxygenos-9.0.6-firmware-3.zip if using a OP3)
WARNING ! Firmware are device-specific, be careful to take a OP3 or OP3T depending on your device !
LineageOS Treble: https://drive.google.com/drive/folders/1vnJEKkhO3xqH-fWWG55-yxwx5K1EeKq7
You only need the file LineageOS Treble
droidian-api28-arm64.zip : https://github.com/droidian-images/droidian/releases
NOTE: As we are flashing LineageOS 16 (android 9), pay attention to use and flash Droidian API28 (which is the version for Android 9)
Please do not use generic halium anymore, @Bettehem made a special version combining both files for OnePlus 3/T here : https://gitlab.com/Bettehem/op3-halium-waydroid Please prefer this version
Below, generic halium files that this tutorial does not recommend
halium-boot.img : https://mirrors.lolinet.com/firmware/halium/oneplus3/halium-boot.img
halium-ramdisk.zip : https://mirrors.lolinet.com/firmware/halium/GSI/tools/halium-ramdisk.zip
GSI patch by @Bettehem : https://gitlab.com/Bettehem/op3-gsi-fix-droidian
You can have alpha version from CI/CD artifact : https://gitlab.com/Bettehem/op3-gsi-fix-droidian/-/jobs/artifacts/main/browse?job=makezip
## Installation​
First treblize your phone with the instructions from here: https://github.com/OP3-Halium/Documentation#treblelizing-your-op3t--firmware--twrp
Basically, all you have to do is :
Flash the special TWRP Treble previously downloaded
Boot it up and go to "Advanced" -> "Terminal", Type treblize and run
Reboot to recovery
Click to expand...
Click to collapse
Then follow the instructions here: https://github.com/OP3-Halium/Documentation#installing-using-erfan-gsi
Basically after you've treblized your device and installed the latest firmware, the install steps are as follows:
Flash the custom LineageOS Treble,so you get the /vendor partition populated.
Reboot to check that everything works. If so, reboot back in to recovery.
Go to advanced wipe and wipe everything except /vendor.
Reboot back into recovery.
Flash the droidian .zip (adb sideload droidian-api28.zip)
Deprecated steps
Flash halium-boot.img
⚠ This shouldn't be done with adb sideload, instead use those two lines :
adb push ./halium-boot.img /tmp/
adb shell "dd if=/tmp/halium-boot.img of=/dev/block/bootdevice/by-name/boot"
Flash halium-ramdisk.zip.
Now just flash @Bettehem's halium-boot.img
Flash @Bettehem's op3-gsi-fix-droidian.zip
⚠ Do NOT flash the regular op3-gsi-fix.zip which is for ubports and not this project ⚠
### Out of storage​A note from @Bettehem 's GSI fix :
It was made possible to move the user's home dir to the phone's userdata partition, so you can utilize the full 64/128GB storage on the device. By default when you install Droidian, the user's home dir is on the 8GB system image, and that's not very much space for both the OS and your home dir
So after installing and booting the device, you can perform the first time setup if you want or skip it for now. Then open a terminal and run the command move-home
Click to expand...
Click to collapse
OnePlus3 is officially supported by Droidian now, here's the updated step by step install :
## Required Files​
Download the latest recovery flashable zip droidian-OFFICIAL-phosh-phone-oneplus_oneplus3-api28-arm64_XXXX.zip: https://github.com/droidian-images/droidian/releases
## Installation​The step-by-step installation comes from this guide : https://github.com/Droidian-oneplus3/device-page#requirements
Treblize your device:
Instructions here: https://forum.xda-developers.com/t/treble-unofficial-lineageos-16-0-treble-for-oneplus-3-3t.3830455/
After you have installed the custom twrp and you have a /vendor partition, install the custom LineageOS 16 build from the guide.
With LineageOS 16 installed, reboot and verify that everything works. Then reboot back into TWRP.
In TWRP, go Wipe -> Advanced Wipe -> Select everything except Vendor and USB-OTG, then Swipe to Wipe.
Reboot into recovery
Flash the droidian .zip using the recovery's install menu or adb sideload
Reboot
Congrats, you're all done, just restart your phone and enjoy using Droidian
## Troubleshoots​
It had been reported some failing with the sideload function to flash parts of this tutorial.
If you enconter those problems, we recommend you to push the files to the device using adb push /path/to/your/file /tmp/ and then use TWRP's own install method
## Notes:​
### First boot​The first boot can take up to 30 seconds. If you see the green droidian's logo on boot, don't worry for the following black screen, just your phone doing its stuff. Once you're os finally booted and ready to use, you'll have the screen showing time and icons.
### Default password​The default password is 1234.
### Wrong UI scale​Some applications aren't designed to fit well on to tiny mobile screens, so if you encounter a problem where buttons/text doesn't properly fit on the screen, do the following:
1. Open the application which doesn't fit well on your screen
2. Open the Mobile Settings application and navigate to the Compositor menu
3. Turn on the toggle for the application which doesn't scale well
Now every time you open the application, it should get scaled down to fit your screen.
### Status
Droidian GSIs are experimental! Bugs and missing features are expected.
OnePlus 3 isn't officially supported by Droidian
OnePlus3 is offically supported since 19/06/2023
@Bettehem's patch is a WIP
### SSH access​Connect your phone to your computer and type ssh [email protected]<OP3-WIFI-IP>, the password is 1234
### Applications​You can find a list of mobile-friendly Linux applications at LinuxPhoneApps
# Credits​
Thanks the Droidian team and the Mobian team for bringing Debian on mobile https://droidian.org | https://mobian-project.org
Thanks to the HaliumProject for all the hard work they do making this whole possible https://halium.org
Thanks to everyone contributing on https://github.com/OP3-Halium for those comprehensive tutorials
Thanks to simonsmh, dianlujitao, chenxingyu, for working and building the LOS Treble (Source Code: https://github.com/OP3Treble )
A huge and special thanks to @Bettehem (Telegram, Gitlab, XDA) for developing the patch and did help me to have it up and running on my phone
Thanks to you for giving a try to this and following this tutorial

# Troubleshooting​## WiFi not connecting​Droidian detects two wifi cards, and only one seems to work at a time.
If Droidian is trying to connect using the wrong card, you can easily change it by running the command nmtui, then select "Activate a connection" and then select the WiFi network you want to connect to.
## Mobile data not working​In settings go to mobile network and press the "Unlock" button. Then close the settings app and open again, because the UI doesn't get updated automatically.
You should now be able to manage your mobile connection from here. To get correct Acces Point Name (APN) settings for your carrier, look here: https://apn.how
After you have set up the APN settings, then just toggle the "Mobile Data" setting off and back on again. If mobile data still doesn't work, you may want to restart the ofono service by running this command: sudo systemctl restart ofono.service. Then reopen settings and toggle the "Mobile Data" setting off and on again.
## Changing audio device​There's a known issue with changing the audio device inside the Settings app. You can use something like pavucontrol, ncpamixer or even just run pactl/pacmd commands directly.
You need to change the sinks port from the primary_output sink for it to work. Changing the port from the deep_buffer sink doesn't work.
# Random screenshots​

I'm working on getting this installed. Can't seem to get past bootloader (oneplus icon).
Attempting to build on my system and see if that helps.

@undrwater Are you on OP3 or OP3T ? And did you exactly follow each step for the tutorial ? 'cause it all worked fine for me ^^"

RoiArthurB said:
@undrwater Are you on OP3 or OP3T ? And did you exactly follow each step for the tutorial ? 'cause it all worked fine for me ^^"
Click to expand...
Click to collapse
I'm on 3t. And while I have some confidence that I followed the directions exactly, there's room for doubt.
I'll try again when I can look at it without distractions.

undrwater said:
I'm on 3t. And while I have some confidence that I followed the directions exactly, there's room for doubt.
I'll try again when I can look at it without distractions.
Click to expand...
Click to collapse
The problem may come from the firmware link I did put before. It wasn't for 3T, so I just updated it and it would prevent similar errors
Please tell me when you'll retry and if now it works well

Actually, looking somewhat closer, I think the issue is finding the correct droidian zip to sideload. several are available, and the few I've tried fail with:
E: No hybris-mobian image found
Click to expand...
Click to collapse
/vendor is populated, lineage is flashed and booted halium boot image dd'ed.

undrwater said:
Actually, looking somewhat closer, I think the issue is finding the correct droidian zip to sideload. several are available
Click to expand...
Click to collapse
Hey, the good version is Droidian API 28 ('cause you're using a base Android 9) ARM64 (which is the Snapdragon in OP3/T)

My OP3 seems to boot into droidian but I have no display, I can tell booting finished because I get sounds when I adjust the volume or connect a charger. Does anyone have an idea why this might be?
Steps I took:
- Flashed latest firmware
- Installed treble TWRP
- ran treblize in TWRP console
- wiped all partitions with advanced wipe (including vendor)
- sideloaded / installed lineage 16 zip and rebooted to test
- wiped all partitions other than vendor in TWRP
- sideloaded / installed "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip"
- installed hallium-boot in bootloader using "fastboot flash boot hallium-boot.img"
- rebooted

the-blind-bandit said:
My OP3 seems to boot into droidian but I have no display, I can tell booting finished because I get sounds when I adjust the volume or connect a charger. Does anyone have an idea why this might be?
Steps I took:
- Flashed latest firmware
- Installed treble TWRP
- ran treblize in TWRP console
- wiped all partitions with advanced wipe (including vendor)
- sideloaded / installed lineage 16 zip and rebooted to test
- wiped all partitions other than vendor in TWRP
- sideloaded / installed "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip"
- installed hallium-boot in bootloader using "fastboot flash boot hallium-boot.img"
- rebooted
Click to expand...
Click to collapse
Hi, you need to install op3-gsi-fix-droidian.zip to get it working on the OnePlus 3.
You can download it from here: https://gitlab.com/Bettehem/op3-gsi-fix-droidian/-/jobs/artifacts/main/browse?job=makezip
So after flashing the droidian-api28-arm64.zip, just flash op3-gsi-fix-droidian.zip and you should be good to go.
Also remember to run the move-home command in terminal after booting for the first time. It will allow you to use all of the storage on the device

Bettehem said:
Hi, you need to install op3-gsi-fix-droidian.zip to get it working on the OnePlus 3.
You can download it from here: https://gitlab.com/Bettehem/op3-gsi-fix-droidian/-/jobs/artifacts/main/browse?job=makezip
So after flashing the droidian-api28-arm64.zip, just flash op3-gsi-fix-droidian.zip and you should be good to go.
Also remember to run the move-home command in terminal after booting for the first time. It will allow you to use all of the storage on the device
Click to expand...
Click to collapse
Thank you. I'm not sure how I missed that in the OP, I saw the bit in red for step 7 and just stopped there I guess
Anyway it's working now and OMG it's actually kinda good. Last time I tried a linux distro for an android phone, which wasn't that long ago, it froze almost all of the time. This seems quite responsive and actually has quite a good keyboard too. My hope for linux on phones (other that android) has been restored

the-blind-bandit said:
Thank you. I'm not sure how I missed that in the OP, I saw the bit in red for step 7 and just stopped there I guess
Anyway it's working now and OMG it's actually kinda good. Last time I tried a linux distro for an android phone, which wasn't that long ago, it froze almost all of the time. This seems quite responsive and actually has quite a good keyboard too. My hope for linux on phones (other that android) has been restored
Click to expand...
Click to collapse
Yeah I like Droidian quite a lot. I have been using it as my daily driver for some time now. Only camera doesn't work but hopefully I'll solve that issue at some point in the near future

I'm having problems with installing.
I followed the steps as instructed, treblized the phone (3T) and installed Linage 16. Lineage is booting fine. I checked the vendor partition which is populated.
After the wiping step (vendor left untouched) I installed droidian (tried droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip and droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-nightly_20221003.zip) and halium-boot.img. I also installed the patch "op3-gsi-fix-droidian.zip".
Droidian isn't loading. When using the halium-boot.img (15.41 mb) linked in this thread, the phone shows the bootscreen (1+) and reboots after some time. Using the halium-boot from this instruction: https://github.com/OP3-Halium/Documentation (15.8 mb) the phone just shows the 1+ logo without rebooting ...
what am i missing?

prosch said:
I'm having problems with installing.
I followed the steps as instructed, treblized the phone (3T) and installed Linage 16. Lineage is booting fine. I checked the vendor partition which is populated.
After the wiping step (vendor left untouched) I installed droidian (tried droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip and droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-nightly_20221003.zip) and halium-boot.img. I also installed the patch "op3-gsi-fix-droidian.zip".
Droidian isn't loading. When using the halium-boot.img (15.41 mb) linked in this thread, the phone shows the bootscreen (1+) and reboots after some time. Using the halium-boot from this instruction: https://github.com/OP3-Halium/Documentation (15.8 mb) the phone just shows the 1+ logo without rebooting ...
what am i missing?
Click to expand...
Click to collapse
Hi, this tutorial recommand using Bettehem's halium-boot file.
If you did checked the Github's documentation, you should have saw a note part for flashing the halium-boot.zip ( https://github.com/OP3-Halium/Documentation#note ) describing 3 differents methods to do it. Did you follow them all or how did you do it ? It may be recommended to use the old technic :
Flash halium-boot.img ⚠ This shouldn't be done with adb sideload, instead use those two lines :
Code:
adb push ./halium-boot.img /tmp/
adb shell "dd if=/tmp/halium-boot.img of=/dev/block/bootdevice/by-name/boot"
Click to expand...
Click to collapse

I used fastboot and the TWRP push method, no difference. I used all the files linked in this tutorial and all of those in the github documentation. After flashing, when rebootIng, TWRP complains that there is noch OS installed... Lineage Installation is no problem. I just tried the ubports installer to install Ubuntu Touch. This stops while pushing the files... Installing OxygenOS works... kinda strange
Update: It's working now. I also had to do "format data / factory reset" after step 2 and repair the fs of cache, system and data to ext4 after rebooting. Using the files from the OP3-Halium-Documentation Droidian is now loading.

I'm installing Droidian, but for some reason I'm getting a booting Ubuntu Touch. I flash in the following order:
* wipe everything but /vendor
* `ubports_GSI_installer_v10.zip`
* `droidian-devtools-api28-arm64_20220804.zip`
* `op3-gsi-fix-droidian.zip`
If I try to wipe `/system` before flashing `droidian-devtools-api28-arm64_20220804.zip`, I'm getting an error: `No hybris-mobian image found`
What am I doing wrong?

marmistrz said:
I'm installing Droidian, but for some reason I'm getting a booting Ubuntu Touch. I flash in the following order:
* wipe everything but /vendor
* `ubports_GSI_installer_v10.zip`
* `droidian-devtools-api28-arm64_20220804.zip`
* `op3-gsi-fix-droidian.zip`
If I try to wipe `/system` before flashing `droidian-devtools-api28-arm64_20220804.zip`, I'm getting an error: `No hybris-mobian image found`
What am I doing wrong?
Click to expand...
Click to collapse
You shouldn't be installing ubports_GSI_installer if you want Droidian. UBports is Ubuntu Touch.
To get Droidian running, follow the instructions on this page or https://github.com/OP3-Halium/Documentation#installing-droidian
For Droidian, you shouldn't be using ubports or droidian-devtools, as neither of those are used in this installation.
droidian-devtools is optionally used with very old droidian images and is not at all needed in the newer ones so don't use it.

Hi, I installed droidian on op3t as described, it works from beginning. I used "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip" an made an "apt-get (update, upgrade, dist-upgrade) to get the latest bookworm version.
The only problem atm: the phone cannot suspend. The blue LED blinks and if it ends the screen with the PIN login turns on (that does happen in a loop). Any hints?

sfoslino said:
Hi, I installed droidian on op3t as described, it works from beginning. I used "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip" an made an "apt-get (update, upgrade, dist-upgrade) to get the latest bookworm version.
The only problem atm: the phone cannot suspend. The blue LED blinks and if it ends the screen with the PIN login turns on (that does happen in a loop). Any hints?
Click to expand...
Click to collapse
Hi, I'm not sure why it does that but I'll try to investigate

Bettehem said:
Hi, I'm not sure why it does that but I'll try to investigate
Click to expand...
Click to collapse
If I remember right it could sleep if I disable wifi. I tried to work around with a script running 'onsuspend' but had no luck, always a probleme because the wifi adapter was shown twice in phosh settings.

Development [ROM][13][UNOFFICIAL] LineageOS 20 for Xiaomi 12

{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
To find out more about LineageOS visit the official Website.
All the source code for LineageOS is available in the LineageOS Github organization. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation
Warning: These instructions only work if you follow every section and step precisely.
Do not continue after something fails!
Basic requirements​
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
LineageOS is provided as-is with no warranty. While we attempt to verify everything works you are installing this at your own risk!
Warning: Before following these instructions please ensure that the device is currently using Android 13 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 13, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).
Unlocking the bootloader​Note: The steps below only need to be run once per device. They require a machine running Windows 7 or newer.
Warning: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from LineageOS once installed.
Tip: It is highly recommended to have the latest official MIUI stable package installed on the device, before proceeding with unlock.
Create a Mi account on Xiaomi’s website. Beware that one account is only allowed to unlock one unique device every 30 days.
Add a phone number to your Mi account.
Insert a SIM into your phone.
Enable developer options in Settings > About Phone by repeatedly tapping MIUI Version.
Link the device to your Mi account in Settings > Additional settings > Developer options > Mi Unlock status.
Download the Mi Unlock app (Windows is required to run the app).
Run the Mi Unlock app and follow the instructions provided by the app. It may tell you that you have to wait up to 30 days. If it does so, please wait the quoted amount of time before continuing to the next step!
After device and Mi account are successfully verified, the bootloader should be unlocked.
Since the device resets completely, you will need to re-enable USB debugging to continue.
Flashing additional partitions​Warning: This platform requires additional partitions to be flashed for recovery to work properly, the process to do so is described below.
Download the following files from here.
boot.img
dtbo.img
vendor_boot.img
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Down + Power. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
Flash the downloaded image files to your device by typing (replace <...> with the actual filenames!):
fastboot flash boot <boot>.img
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
Booting a custom recovery using fastboot​
Download Lineage Recovery. Simply download the latest recovery file, named recovery.img.
Important: Other recoveries may not work for installation or updates. We strongly recommend to use the one linked above!
Connect your device to your PC via USB if it isn’t already.
If your device isn’t already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable (preferably use a USB Type-A 2.0 one or a USB hub) and port!
Tip: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ..., fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
Flash a recovery on your device by typing (replace <recovery_filename> with the actual filename!):
fastboot flash recovery <recovery_filename>.img
Note: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to recovery__a /recovery__b rather than recovery_a / recovery_b if you try to flash recovery. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to recovery__a, you must flash to recovery_a.
Now reboot into recovery to verify the installation.
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Note: If your recovery does not show the LineageOS logo, you accidentally booted into the wrong recovery. Please start at the top of this section!
Installing LineageOS from recovery​
Download the LineageOS installation package that you would like to install or build the package yourself.
(Optionally): If you want to install an application package add-on such as Google Apps (use the arm64 architecture), please read and follow the instructions on Google Apps page
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
Return to the main menu.
Sideload the LineageOS .zip package but do not reboot before you read/followed the rest of the instructions!
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Tip: Normally, adb will report Total xfer: 1.00x, but in some cases, even if the process succeeds the output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error or adb: failed to read command: Undefined error: 0 which is also fine.
All set!​Once you have installed everything successfully, you can now reboot your device into the OS for the first time!
Click the back arrow in the top left of the screen, then “Reboot system now”.
Note: The first boot usually takes no longer than 15 minutes, depending on the device. If it takes longer, you may have missed a step, otherwise feel free to get assistance.
Download link:
Builds are released here: Releases on GitHub
Warning: These releases include builds for other devices i own, make sure to download files from a release for Xiaomi 12, for example: "LineageOS 20.0 for Xiaomi 2201123G (cupid)"
Note: There are two variants which are not necessarily released at the same time. Vanilla builds are pure LineageOS without additional apps and GMS builds include Google services. The GMS builds are too big for github releases, so they will be uploaded to this shared folder on Google Drive instead
Source Code
Please read this thread about the OSS kernel on Xiaomi 12.
All kernel related source code can be found here.
Device trees for LineageOS can be found here.
Donate to support development:
Donate via PayPal to ArianK16a
Donate via PayPal to LineageOS

MiuiCamera for LineageOS on Xiaomi 12
I have created a Magisk Module to get the MIUI camera app on LineageOS 20. It's extracted from MIUI V14.0.2.0.TLCMICM.

For "new" users you could also give a step by step instruction how to update. Because format data is not always necessary.

i get " low resource device detected" error when trying to install Gapps

Will go official?

McFlypants said:
For "new" users you could also give a step by step instruction how to update. Because format data is not always necessary.
Click to expand...
Click to collapse
I will add that soon
quardier said:
i get " low resource device detected" error when trying to install Gapps
Click to expand...
Click to collapse
That's because the system partitions use erofs, a read only file system without reserved space. You can use the GMS variants if you want to use Google services or install Google apps that use overlay over the partitions.
vyvy said:
Will go official?
Click to expand...
Click to collapse
I aim to get this official one day in future, but this is not really close yet because of a different builds process due to GKI compliance which isn't supported officially in lineage.

outstanding work from the ROMs developer. thank you for bringing stable Lineage to our device

Xiaomi 12 currently no Lineage ROM bug?

Kkjin said:
Xiaomi 12 currently no Lineage ROM bug?
Click to expand...
Click to collapse
It has an error - cannot install Gapps, in TWRP it throws error 1

funciona no redmi note 12 4g?
Mod translation: it works not redmi note 12 4g?

Jadson note12 4g said:
Mod translation: it works not redmi note 12 4g?
Click to expand...
Click to collapse
Greetings, and welcome to XDA. As a friendly reminder, we ask all members to please post in English as stipulated by XDA Rule #4:
Spoiler: XDA Rule #4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Thank you for your cooperation, and have a pleasant day.
-Regards: Badger50

Volte und voWifi calls sometimes show a strange number format.
Sometimes it's the caller number and my own number after each other, sometimes it's both numbers with a & or a + inbetween.
Even if the contact is known, the number in wrong format is shown.
Any help? I'm still on the 20230316 build. Is it fixed on the newest one?

NeoArian said:
MiuiCamera for LineageOS on Xiaomi 12
I have created a Magisk Module to get the MIUI camera app on LineageOS 20. It's extracted from MIUI V14.0.2.0.TLCMICM.
Click to expand...
Click to collapse
Is it possible to make the Xiaomi Leica camera inbuilt? Or a Magisk Module of the Xiaomi Leica Camera App?

Someone tried NFC payment and banking apps with this ROM ? Thank you