Related
[GUIDE] OOS v4.0.3 ---> FLASH & ROOT STOCK -OR- CUSTOM ROM WITH EASE & CORRECTLY
If you think that I need to add more information to this guide, please post your request. I'm not able to guess what you want from me to add to this guide.
Thank you!
INTRODUCTION:
This guide is mainly for users who tried flashing OxygenOS v4.x.x the easy and short way (like in post #9 in this thread), which had issues in the process.
I covered the most common issues with flashing OOS v4.x.x in this guide. However, you can use this guide to flash OxygenOS (latest Stable and Beta versions)
and root them OR flash your custom ROM. Just follow the instructions.
Now, you ask “why I decided to write this guide?”. Well here’s my story:
I had FreedomOS v1.7 with Google apps installed (including Dialer and Contacts from OpenGApps), encrypted, official twrp (v3.0.2-1), Xposed (v3.1.1), framework (v87),
AdAway v3.2, YouTube AdAway and SuperSU v2.79 (stable). Also, stock kernel, no Dolby ATMOS or A.R.I.S.E apps.
So, when OOS v4.0 came out, I waited for FreedomOS v2.0 to come out too. Once it did, I downloaded the ROM, OpenGApps, modified twrp .28 and started
the flashing process (I backed up my data first).
First, I flashed twrp .28 (had no problems booting into it), and clean flashed FOS v2.0. I selected “Yes” in “Pin/Pattern backup in data partition”, so I wouldn’t have issues with encryption. I selected the regular apps (for OOS to work properly) and installed the OS.
When it was done, I rebooted the device to the OS. I was confused with the new “dm-verity” message popping from nowhere, but the OS booted successfully.
When I rebooted to the twrp (to install OpenGApps), it asked for a password. I couldn’t enter the right password, because it wouldn’t accept any and it blocked
my access to my internal storage.
I started panicking, looking for answers, and I was afraid that I bricked my phone. However, after some research, I calmed down. I realized that my bootloader was still working and could roll back to OOS v3.2.8 (with stock recovery), which I did. From there I flashed FOS v1.7 and waited for more information about the new Nougat update for OnePlus 3.
Now, I’m using Stock OygenOS v4.0.3 with Stock Kernel (see FAQ #16) and so far, no issues (no dm-verity message or password upon entering modified twrp).
I tried to repeat the dm-verity issue and fixed it (see FAQ #6). I was so frustrated that no one posted a proper guide on how to fix these issues, or they were too advanced. I didn’t want to mess around with the core of the system too much. Therefore, I decided to post a simple-to-follow guide.
DISCLAIMER & IMPORTANT:
I am not responsible for any damages done by this guide. You are tinkering with your phone and held responsible for that. This is not an advanced guide. Therefore, I will refer you to the advanced guides when needed. Furthermore, this guide is based on the issues that I and other users encountered while
flashing OOS v4.x.x ------------>***BACK UP PERSONAL DATA BEFORE PROCEEDING ANY FURTHER***
This guide is intended for owners of OnePlus 3. But, after some poking in OnePlus 3T forums, you can use this guide. The only differences the OnePlus 3T
have are a newer processor, newer front camera and a different color from OnePlus 3. Make sure to use the appropriate tools (Stock recovery, TWRP,
OxygenOS v4.0.3, etc.) for OnePlus 3T. Again, I will not be responsible for any damages caused by this guide.
Please follow this guide to get rid of: dm-verity, encrypted twrp, encrypt or decrypt your device (as OnePlus 3 comes encrypted by default), change your file system from EXT4 to F2FS (vice versa as well). Also, flash a Marshmallow or Nougat Stock OOS (Stable or Beta versions), root them OR unroot your device, OR flash a custom ROM.
As far as I know, tested and read in forums, Android v6.0.1 (OxygenOS v3.x.x) supports only EXT4 file system, and Android v7.0 (OxygenOS v4.x.x) supports both EXT4 and F2FS file systems. However, F2FS is recommended for Android v7.0 (OxygenOS v4.x.x). When you perform, a full factory reset in OxygenOS v4.x.x, the file system changes from EXT4 to F2FS. ONLY “Data (userdata)” is affected by this. If you want to go back to Marshmallow, OxygenOS v3.x.x will change your file system from F2FS to EXT4 when you sideload it.
OxygenOS v4.0.3 still comes with some issues, bugs, and some rooting services are not fully supported yet (i.e. Xposed for Nougat). Luckily, OnePlus released kernel sources of Nougat, and we need to wait a little longer for Xposed and other rooting services to be supported. Therefore, I advise staying away from it,
for a little while, until those issues are fixed, and new ones don’t pop up. Also, until rooting apps are fully supported. Follow OnePlus community forums and
XDA forums for updates, troubleshooting, and solutions for your issues. MAKE SURE TO BACK UP YOUR PERSONAL DATA, time to time.
Before posting questions or issues or requests, check FAQ and posts in this thread. Thank You!
WHAT WILL YOU NEED?
You don't need to download everything in this section, only what you prefer to roll with.
ADB drivers installed on your computer (I have version 1.0.32 installed)
Unlocked bootloader (if you haven't done it yet, follow this guide: https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733)
DiskInfo app from the Play Store:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=en
OxygenOS v3.2.8 OTA:
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
OxygenOS v4.0.3 OTA:
https://www.androidfilehost.com/?fid=457095661767136075 OR http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
*** Download speeds might be slow. Be patient. ***
OxygenOs Beta 11 (Nougat):
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_11/
Stock Recovery v2.0 (compatible with OOS v3.x.x and OOS v4.x.x):
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Official TWRP (v3.0.2-1 for OxygenOS v3.x.x ; v3.0.3-0 for OxygenOs v4.x.x):
https://twrp.me/devices/oneplusthree.html
Unreleased Official TWRP v3.0.4-1 for Nougat (OxygenOS v4.x.x): *** Recommended for Nougat ***
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Unofficial TWRP (v3.0.3-0 for LineageOS v14.1):
https://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
Modified TWRP v3.0.3-x blu_spark v16 from @eng.stk:
https://forum.xda-developers.com/devdb/project/dl/?id=23082
SuperSu v2.79 (Stable):
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
OpenGApps (latest version):
http://opengapps.org/
Your desired custom ROM (I tested FreedomOS v1.7 and v2.3 and v2.4-CE, Experience ROM v10.1 [Stable and Beta 11], LineageOS v14.1):
https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348 (FreedomOS - Stable [v1.7 - OOS v3.2.8 ; v2.3 - OOS v4.0.2])
https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-ce-1-7-t3470660 (FreedomOS - Beta [v2.4-CE - OOS Beta 11])
https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259 (ExperienceOS - Stable and Beta 11 [v10.1])
https://forum.xda-developers.com/oneplus-3/development/rom-cyanogenmod-14-1-oneplus-3-t3496850 (LineageOS v14.1 - based on Andriod v7.1.1)
Code:
[I][SIZE="4"][B] * I'LL BE USING OOS v4.0.3, OFFICIAL UNRELEASED TWRP v3.0.4-1 AND FreedomOS
v2.3 AS AN EXAMPLE FOR THIS GUIDE. OTHER VERSIONS OF OOS AND TWRP
(PROVIDED) ARE APPLICABLE TO BE USED IN THE GUIDE (ONLY WHAT I TESTED).
[COLOR="Red"][I] * If you don't have dm-verity issue, file system change issue or password
upon entering TWRP, then go to Section C (FLASHING YOUR CUSTOM ROM)
-OR- Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT).
* If you do have dm-verity issue, file system change issue or password upon
entering TWRP, then continue to Section A (DM-VERITY).[/I][/COLOR]
[/B][/I][/SIZE]
A - PROCEDURE (DM-VERITY):
Code:
[I][SIZE="4"][CENTER][B]***** Check FAQ #5 before proceeding any further! *****[/B][/CENTER][/I][/SIZE]
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery recovery_op3.img” to flash Stock Recovery of OxygenOS.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into recovery by holding Volume Down (-) and Power button down for a few of seconds.
Now, for some people, it will ask a password. If not, continue to #9 and ignore #8. If it asks you to enter a password to decrypt your data, choose “Forgot password” and let it erase all your data and let it reboot. (MAKE SURE YOU BACKED UP YOUR PERSONAL DATA BEFOREHAND). Most likely, it will reboot to the OS, so boot it to recovery again. Go to #10.
For those who doesn’t have to enter a password, press “English”. Press “Wipe data and cache” > “Erase everything (Music, pics, etc.)” > “This cannot be undone, continue?”. Moreover, let it wipe your data. Most likely, it will reboot to the OS, so boot it to recovery again. Go to #10.
Code:
[CENTER][I][SIZE="4"][B]AT THIS POINT IF YOU HAD DM-VERITY ERROR/ISSUE, IT SHOULD BE FIXED AND GONE.
IF IT STILL APPEARS, DON'T WORRY IT WILL BE GONE AFTER #12
IT CAME BACK TO ME ONE MORE TIME, BUT I GOT IT FIXED.
***** Check FAQ #6 for more information *****[/B][/I][/SIZE][/CENTER]
Select “English” > “Install from ADB” > “Ok”. Connect your phone to your computer. Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “adb sideload OnePlus3Oxygen_16_OTA_041_all_1702081756_0f1e56a75f.zip”
to flash OxygenOS v4.0.3. (See FAQ #4 and #17 if you have issues)
Reboot and you have OxygenOS v4.0.3!
Sign-in into your Google account and Download the “DiskInfo” app from the Play Store. Launch it, and press “Data (userdata)”. You should see:
- Encrypted: yes
- Decrypted block device: /dev/block/dm-1
- Mount point: /data
- File system: f2fs
A. If you see that it is in F2FS file system format, proceed to Section C (FLASHING YOUR CUSTOM ROM) OR Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT).
B. However, for some people (for some reason) it does not happen. You would see that your file system format (for userdata) is still on EXT4. Don’t be frustrated. A little bit more work needed to be done. Therefore, go to Section B (CHANGING FILE SYSTEM FORMAT AND ENCRYPTING OR DECRYPTING YOUR DEVICE). It will solve that problem.
Code:
[I][SIZE="4"]* Your phone needs to be encrypted by default. It comes like that from the
manufacturer. See the following links:
1. [url]https://forums.oneplus.net/threads/encrypted-oneplus-3.452572/page-2[/url]
2. [url]http://www.androidpolice.com/2015/10/19/android-6-0-will-finally-require-manufacturers-to-enable-full-disk-encryption-by-default-on-new-devices/[/url]
3. [url]http://arstechnica.com/gadgets/2015/10/android-6-0-re-implements-mandatory-device-encryption-for-new-devices/[/url]
4. [url]https://source.android.com/security/encryption/[/url]
5. [url]http://www.howtogeek.com/141953/how-to-encrypt-your-android-phone-and-why-you-might-want-to/[/url]
6. [url]http://www.extremetech.com/mobile/216560-android-6-0-marshmallow-makes-full-disk-encryption-mandatory-for-most-new-devices[/url]
[/I][/SIZE]
B - PROCEDURE (CHANGING FILE SYSTEM FORMAT AND ENCRYPTING OR DECRYPTING YOUR DEVICE):
Go to: Settings > Security & fingerprint > Encryption (located at the bottom). Make sure it says “Encrypt phone (Encrypted)”. To make sure
you will need to do a factory reset.
Now go to: Settings > Backup & reset > Factory data reset. In “Optional” select “Erase internal storage” and press “RESET PHONE”. Confirm by pressing “ERASE EVERYTHING”.
It will reboot to Stock Recovery and wipe your data. When it’s done, it will reboot to the OS.
Again, download the “DiskInfo” app from the Play Store. Launch it, press “Data (userdata)”. Now you should see (it wouldn’t show “Encrypted: yes” at all):
- Mount point: /data
- File system: f2fs
Now go to: Settings > Security & fingerprint > Encryption (located at the bottom). Make sure it says “Encrypt phone” and that you can press it. (DON’T ENCRYPT YOUR PHONE WITH THAT OPTION)
Now you successfully changed your file system to F2FS and decrypted your phone!
Code:
[I][SIZE="4"] * With Official TWRP v3.0.3-0 and modified TWRP v3.0.3-x v16 (from [user=3873953]@eng.stk[/user])
you are able to use the phone in encrypted mode, password request at
boot up and with Stock or rooted OOS v4.0.3 (Also, I tested it myself).
* Therefore, I will ask you to encrypt the phone back again. Proceed with
the following instructions:
[CENTER]***** Check FAQ #9 for more information *****[/CENTER][/I][/SIZE]
Reboot to Stock recovery v2.0
Select “English” > “Install from ADB” > “Ok”. Connect your phone to your computer. Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “adb sideload OnePlus3Oxygen_16_OTA_041_all_1702081756_0f1e56a75f.zip”
to flash Oxygen OS v4.0.3. (See FAQ #4 and #17 if you have issues)
Reboot your device. Now you back to being encrypted and “userdata” was changed successfully to F2FS file format on Stock Oxygen OS v4.0.3!
Go to Section C (FLASHING YOUR CUSTOM ROM) to properly flash your custom ROM. *** IT’S YOUR CHOICE ***
OR Go to Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT) to remain in stock, root or unroot. *** IT’S YOUR CHOICE ***
C - PROCEDURE (FLASHING YOUR CUSTOM ROM):
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery twrp-3.0.4-1-oneplus3.img” to flash Official Unreleased TWRP v3.0.4-1.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into the TWRP by holding Volume Down (-) and Power button down for a few of seconds.
It takes a little bit more time to boot to blu_spark’s, Official and Unofficial TWRPs. Be patient.
Code:
[I][SIZE="4"] * The “PASSWORD UPON ENTERING TWRP” should not be an issue any longer (only
if you followed the whole guide). It is caused by the TWRP being modified
(has an issue with encryption), not being officially released and fully
supported for the Nougat update. Versions “.28”, “.22” and “.19” are known
for that issue. Therefore, DO NOT USE THEM. If one of them works for
you, then use it at your own risk.
[CENTER]***** Check FAQ #9 for more information *****
[/CENTER][/I][/SIZE]
Press “Wipe” > “Advanced Wipe”, and select “Dalvik / ART Cache”, “System”, “Data” and “Cache”. Then swipe “Swipe to Wipe” for a clean flash.
After it’s done, go back to the main menu. Press “Install” and look for your desired custom ROM and press on the zip file to install it.
* I used FreedomOS v2.3 as an example and I didn't have any battery drain issues. (For more information, see FAQ #10)
D - PROCEDURE (FLASHING AND ROOTING STOCK OOS OR UNROOT):
Code:
[I][SIZE="4"][COLOR="Red"][I] * If you don't have dm-verity issue, file system change issue or password
upon entering TWRP, then go to #1.
* If you came from having dm-verity issue, file system change issue or
password upon entering TWRP (solved by using Procedure A and/or B),
then go to #12.
[/I][/COLOR][/I][/SIZE]
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery recovery_op3.img” to flash Stock Recovery of OxygenOS.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into recovery by holding Volume Down (-) and Power button down for a few of seconds.
Select “English” > “Install from ADB” > “Ok”. Connect your phone to your computer. Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “adb sideload OnePlus3Oxygen_16_OTA_041_all_1702081756_0f1e56a75f.zip”
to flash OxygenOS v4.0.3. (See FAQ #4 and #17 if you have issues)
Reboot and you have OxygenOS v4.0.3!
A. UNROOT - At this point, if you want to unroot and go back to completely stock, then use this guide: https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/
*** Most of the procedures for unrooting you have already done. Only locking bootloader is left. Good Luck! (YOU CAN STOP HERE)
B. ROOT - Continue to #13
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery twrp-3.0.4-1-oneplus3.img” to flash Official Unreleased TWRP v3.0.4-1.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into the TWRP by holding Volume Down (-) and Power button down for a few of seconds.
It takes a little bit more time to boot to blu_spark’s, Official and Unofficial TWRPs. Be patient.
Connect you OnePlus 3 to your computer and copy the SuperSU v2.79 (Stable) to your device.
Pick up your phone. From the main menu, press “Install” and look for the SuperSU v2.79 (Stable zip file). Press it to install the root and after it's done, reboot to the OS.
That's it! Everything should be working properly
(except the bugs and issues on OxygenOS Nougat update).
ENJOY!
CREDITS:
@NevaX1 --------------> For FreedomOS ROM
@jamal2367 -----------> For ExperienceOS ROM
@cpt.macp ------------> For in depth dm-verity remover guide
@Adithya R -----------> For in depth file system formating from EXT4 to F2FS guide
@eng.stk --------------> For modified TWRP that supports F2FS file format
@LELBOT --------------> For in depth dm-verity remover and file system formating from EXT4 to F2FS guides
@Naman Bhalla ------> For in depth bootloader unlocking, flashing TWRP, rooting, nandroid backup guide
@calvinistmac --------> For providing an unroot for OnePlus 3 guide
@Nishidh --------------> For providing OxygenOS v4.0.3 and Beta 11 OTA download links
@jcadduono ----------> For providing Official TWRP
@dianlujitao ----------> For providing Unofficial TWRP and LineageOS 14.1 ROM
@th3g1z ---------------> For providing an easy solution for Dm-verity issue
--------------------------> OnePlus Community and XDA forums for providing with issues, solutions and requests
FAQ (Q&A):
Q: I can’t boot into TWRP! What to do?
A: Try using the previous TWRP or Stock Recovery.
[*]Q: I can’t boot into the OS! What to do?
A: Most likely some of the OS files are damaged or executed incorrectly. Try flashing or sideloading the OS again.
[*]Q: I can’t transfer files to my OP3 after wiping Internal storage OR Data folder/s in TWRP! What to do?
A: Don’t panic. Reboot to TWRP. It will create a folder so you can transfer files again.
[*]Q: I got an error sideloading the OS. Why is that?
A: Sometimes it occurs when the USB cable is wiggled side to side (the process stops at 92% with an error). Try again without touching
or moving the USB cable and the phone. Alternatively, it could be that USB debug is not enabled (not sure about that).
[*]Q: Is there an alternative way to get rid of dm-verity issue?
A: One simple command-line (enable) in bootloader can solve it. Check this post: https://forum.xda-developers.com/showpost.php?p=70698410&postcount=112
Otherwise, check this thread: https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685 This guide uses the .28 twrp
(NOT RECOMMENDED, BUT USE TWRP FROM @eng.stk) to use Stock Recovery, which I think is a bit more complex.
OR: https://forum.xda-developers.com/showpost.php?p=70415499&postcount=33
My guide uses only bootloader, Stock Recovery and TWRP from @eng.stk. Either way, they are the same guides.
[*]Q: The "dm-verity issue" came back after flashing OTA of stock OOS v4.0.2 via the TWRP! What to do?
A: Simply follow "Section A" instructions until #13. After you sideloaded the OTA it will be gone. It happened the second time when I tried to
flash the OTA via TWRP. Therefore, don't flash OTA of stock OOS v4.x.x via TWRPs. Only via Stock Recovery v2.0
I got it fixed only after sideloading the OTA via Stock Recovery v2.0 (Check post #29 for more information)
If it still doesn't work check this thread and read it thoroughly: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-t3539129
For more information, read FAQ #12
[*]Q: Your guide to change file format doesn’t work, OR I want to change “Cache” and “System” to F2FS as well. What to do?
A: Simply go to this link and at your own risk: https://forum.xda-developers.com/oneplus-one/general/guide-formatting-ext4-to-f2fs-losing-t3352116
Furthermore, @cpt.macp mentioed in post #34 in this thread that "/system and /cache need not to be f2fs . Oneplus Supports only /data
as f2fs and nothing else ."
[*]Q: I can’t log in into Snapchat after a clean flash of my desired custom ROM or after rooting my device. How to fix this?
A: I had the same issue, and it doesn’t occur to everybody. Before DIRTY flashing (wiping System, Cache and Dalvik only) the custom ROM
-OR- rooting your device, install Snapchat and log into it (on stock OOS v4.x.x). It might be a SuperSU (root) issue with Snapchat
(they enforced their security with rooted devices).
Also, OnePlus 3 has an issue with on-screen navigation bar. So, disable it in the "Buttons" menu until OnePlus fixes the glitch/bug.
[*]Q: Why did you choose TWRP v15 from @eng.stk -OR- Official TWRP v3.0.3-0 -OR- Unofficial TWRP v3.0.3-0?
A: They all work with the phone being encrypted, requesting a password on bootup to the OS and support F2FS file system.
.28 – had issues with encryption and F2FS file system, but for some users it works wonders.
.22 and .23 – I did not test, but I have read that .23 worked (decrypted).
.19 – Tested and solved the password issue, but had a mouse pointer in the middle of the TWRP (wasn’t a big deal). Worked in decrypted mode.
P.S. The official TWRP has issues with the name of the device. If you encounter those issues, then let the developer of the ROM
you're using know about it. So, he could fix it (it's a small fix). OR use TWRP v15 from @eng.stk. Unofficial TWRP is to be used
with LineageOS 14.1 & Experience v10 ROMs. Also, here is the reason why: https://forum.xda-developers.com/showpost.php?p=70593986&postcount=53
Also, Official TWRP v3.0.2-1 doesn't support Nougat. Therefore, you won't be able to boot to this TWRP. Don't use it for Nougat.
[*]Q: I am experiencing a battery drain. Why?
A: Facebook was the main issue for that, but it is now fixed (some users said that it still exists). I use Freedom OS v2.2 and no
issues so far with the battery. I got 5 hours SOT (Screen On Time) with 45% left (on the first day), and 5½ hours SOT with 26%
battery left (on the second day). Now, I think the OS is balanced because I get almost 8 hours of SOT. Try looking for a solution
in the forums. Also, disable mobile data when using WIFI and vise versa. Furthermore, battery life may vary with the applications
you use on a daily basis, screen brightness, how much and long you touch the screen, etc. (See the attached thumbnails)
[*]Q: I am experiencing issues with the Play Store app (It’s stuck on downloading). Is there a fix?
A: When you first launch it, it tries to update itself. It will crash 1-2 times. After that, everything works just fine. Also, uninstall or don’t
install Truecaller app (well known to cause this issue). It was fixed in OOS v4.0.2, but some users still experience this issue.
In addition, if nothing works, then try uninstalling the Play Store app and reinstall it via OpenGApps. For those who are not rooted,
try finding the Play Store app via the web (install it under your own risk, as I'm not responsible for the damages).
[*]Q: Why do you use stock recovery to sideload the OS?
A: First of all, you’re going to sideload OTA of Oxygen OS, which you can’t flash in the TWRP (some people can and you might get dm-verity
issue). Secondly, the stock recovery is simple and easy to use. Thirdly, If you flash the OTA from the official TWRP, you will get a dm-verity
message. Besides, OnePlus provided only with "OTA" zips and not "signed flashable" zips.
THE DM-VERITY ISSUE (CHECK THE FOLLOWING SOURCES FOR MORE INFORMATION):
https://www.xda-developers.com/qualcomm-maintains-its-dedication-to-security-with-secure-boot/ ; https://www.xda-developers.com/stri...r-correction-to-come-with-android-7-0-nougat/ ;
https://source.android.com/security/verifiedboot/ ; https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-t3539129 ;
https://forum.xda-developers.com/showpost.php?p=70574596&postcount=34 ; https://forum.xda-developers.com/showpost.php?p=70622726&postcount=97 ;
https://forum.xda-developers.com/showpost.php?p=70622760&postcount=98 ; https://forum.xda-developers.com/showpost.php?p=70622849&postcount=102 ;
https://forum.xda-developers.com/showpost.php?p=70622999&postcount=104
[*]Q: What if I want to go back using Oxygen OS v3.2.8 (Andriod v6.0.1) or custom ROMs based on it?
A: Simply instead of using Stock Oxygen OS v4.0.2 OTA in this guide, use Stock Oxygen OS v3.2.8 OTA.
It will bring back EXT4 file system and you can use Xposed.
[*]Q: After clean flashing my Custom ROM in TWRP, I get the following message: "No OS Installed. You Sure You Want
To Reboot". What to do?
A: Try dirty flashing your Custom ROM. (Source: https://forum.xda-developers.com/showpost.php?p=70622460&postcount=5291)
[*]Q: Android System WebView is disabled in the Play Store. When I try to enable it, it won't do anything. Unless I tap
it rapidly and it's still in disabled mode. What to do?
A: No need to worry here. It is normal due to Chrome being the new WebView in Android Nougat.
(Sources: http://www.androidpolice.com/2016/07/20/google-explains-chrome-will-become-webview-android-7-0/ AND https://productforums.google.com/forum/#!topic/nexus/Ni35XW6eRR0
https://www.reddit.com/r/GooglePixel/comments/5ayh5d/android_system_webview_not_enabled/ AND https://www.reddit.com/r/Nexus6P/comments/57t1hw/android_system_webview_keeps_disabling/)
[*]Q: Should I flash a custom Kernel (ElementalX or Blu_spark) on a custom ROM?
A: You can, but you might have CPUs being on max load and overheating issues (it's not caused by the kernel itself).
They work best, and only, if you have stock OOS v4.0.2 installed and rooted with SuperSU v2.79 Stable. Yes, for some
users the custom kernels work. But, for some they won't, due to firmware issues. You can try them on your Custom
ROM, but it's not guaranteed to work. The developers of FreedomOS and ExperienceOS solved this issue.
**Some users found a solution by setting SELinux to Permissive mode instead of Enforced.
I do not recommend setting your SELinux in Permissive mode! (as well as the developer of ElementalX)!
For more information, check this thread: https://forum.xda-developers.com/oneplus-3/how-to/potential-fix-cpu-battery-drain-aosp-t3543369
Also, check these articles: https://www.xda-developers.com/onep...ng-of-selinux-to-permissive-mode-in-fastboot/ ; https://www.xda-developers.com/onep...lus-33t-bootloader-vulnerability-in-next-ota/
[*]Q: I'm getting the error (cannot read "image.zip") when trying to sideload Stock OOS. Why and how to fix this?
A: For some reason, the thread added a space in the OOS file name. If you copy the file name for Stock OOS v4.0.2 from this thread,
make sure it doesn't have spaces in it (-OR- in any other file -OR- in the console).
** Also, make sure to enable USB Debugging in Developer Options.
** Follow these guidelines separately (if the first one doesn't work, use the second or third guideline):
Reinstall OnePlus Drivers using the attached zip (OnePlus_USB_Drivers_Setup.zip) and try again. In addition,
make sure your file name is not ending with ".zip.zip" or written like that in the console.
Bootup to your OS and connect the phone to the computer (make sure to choose transfer files mode).
Copy Stock OOS v4.0.2 OTA zip to the device and reboot to recovery. Select "Install from Internal Storage",
look for the OTA file and install it.
Read the following threads/posts/articles: https://forum.xda-developers.com/showthread.php?t=1990405&page=2 ;
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ ; https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/ ;
https://www.reddit.com/r/oneplus/comments/504qgv/adb_cannot_read_error/ ; https://www.androidexplained.com/fix-cannot-read-sideload-update/ ;
https://forum.xda-developers.com/android/general/guide-how-to-adb-to-push-pull-files-t3372710
[*]Q: Every second song in Google Play Music gets skipped. What to do?
A: Make sure to disable AdAway, then reboot the device. Everything should come back to normal.
P.S. I will add more questions and answers if they get repeated in the forums, or the issue can be solved.
Updates & News:Updates:
January 14th, 2017 ---> Reverted modified TWRP v3.0.3-x v12 from @eng.stk back to v3.0.2-0 v11
(Reason: https://forum.xda-developers.com/showpost.php?p=70556176&postcount=2540)
January 15th, 2017 ---> Added an introduction section; Modified sections A, B and C for more fluent and easier guidelines; Added one more Q&A
January 20th, 2017 ---> Added Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT) ; Modified sections A, B and C ; Modified FAQ (Q&A)
and added more Q&A ; Updated to OOS v4.0.2, Beta 11, Official TWRP v3.0.3-0, Unofficial TWRP v3.0.3-0, Modified TWRP v14 from blu_spark ;
Modified Intoduction, "Disclaimer & Inportant" and "What will you need?" sections.
January 23rd, 2017 ---> Updated to latest Modified TWRP v3.0.3-x blu_spark v15 from @eng.stk
January 25th, 2017 ---> Added Unreleased Official TWRP v3.0.4-1 for Nougat ; Minor updates to the guide and FAQ.
February 9th, 2017 ---> Added and updated the thread with OxygenOS v4.0.3 ; Added one more FAQ and a new story
February 10th, 2017 ---> Updated to latest Modified TWRP v3.0.3-x blu_spark v16 from @eng.stk
News:
January 14th, 2017 ---> Oxygen OS v4.0.2 coming next week! Confirmed.
(Sources: https://forums.oneplus.net/threads/4-0-2-in-works-roll-out-by-next-week-confirmed.488348/ AND https://twitter.com/OnePlus_ITA/status/819200734067617792 AND
http://www.androidsage.com/2017/01/14/oneplus-3-and-3t-oxygen-os-4-0-2/)
January 15th, 2017 ---> We as a community of developers and users, urge OnePlus to release kernel sources by complying with GPLv2.
(Source: https://www.xda-developers.com/xda-developers-urges-oneplus-to-comply-with-gplv2-and-release-kernel-sources/)
January 18th, 2017 ---> OnePlus said that OxygenOS 4.0 doesn’t use a Debug Kernel
(Source: https://www.xda-developers.com/oneplus-oxygenos-4-0-doesnt-use-a-debug-kernel/)
January 20th, 2017 ---> Seems like OnePlus released Kernel Sources for OnePlus 3/3T. Finally!
(Sources: https://www.xda-developers.com/oneplus-releases-android-nougat-kernel-sources-for-the-oneplus-33t/ AND https://github.com/OnePlusOSS/android_vendor_qcom_thulium/commits/oneplus/QC8996_N)
January 20th, 2017 ---> The Best ROMs, Kernels, and Mods for the OnePlus 3
(Source: https://www.xda-developers.com/oneplus-3-best-stuff/)
January 21st, 2017 ---> Remap your phone’s hardware buttons with "Button Mapper" app
(Source: https://www.xda-developers.com/xda-...an-app-to-remap-your-phones-hardware-buttons/)
January 21st, 2017 ---> How to move Chrome’s address bar to the bottom without a visual bug?
(Source: https://www.xda-developers.com/psa-...ar-to-the-bottom-no-longer-causes-visual-bug/)
January 22nd, 2017 ---> Enable this Chrome Flag to Lock Rotation in Fullscreen Videos
(Source: https://www.xda-developers.com/enable-this-chrome-flag-to-lock-rotation-in-fullscreen-videos/)
January 22nd, 2017 ---> Deeply Integrated Progressive Web Apps (WebAPKs) are Live for Chrome on Android
(Source: https://www.xda-developers.com/deep...-apps-are-already-live-for-chrome-on-android/)
January 25th, 2017 ---> Open Betas updates are paused for a month for OnePlus 3/3T due to Chinese New Year
(Source: https://forums.oneplus.net/threads/...s-3-and-3t-will-be-paused-for-a-month.492623/)
January 25th, 2017 ---> Security Analysts Identify a Trojan that Quietly Purchase Apps, a Rootkit that takes over your Device,
and Ransomware that Locks your Device
(Source: https://www.xda-developers.com/secu...device-and-ransomware-that-locks-your-device/)
January 28th, 2017 ---> An update from @rovo89 about developing Xposed for Nougat
(Source: https://forum.xda-developers.com/showpost.php?p=70773752&postcount=41)
February 1st, 2017 ---> OnePlus got caught red-handed in Benchmark cheating and came clean
(Sources: https://www.xda-developers.com/benc...ght-red-handed-and-what-theyve-done-about-it/ ; http://www.androidauthority.com/oneplus-meizu-just-got-busted-benchmark-cheating-746640/)
February 9th, 2017 ---> Two Critical OnePlus 3/3T Bootloader Security Flaws Discovered, One Patched and Other being Addressed
(Source: https://www.xda-developers.com/two-...overed-one-patched-and-other-being-addressed/)
Very easy to follow guide. I ended up at B8 "Now you successfully changed your file system to F2FS and decrypted your phone!". I would like my phone to be encrypted, but if I do it through the OS, TWRP does not accept my password for the data partition?
Thanks so much, mate. This is a really good job which is gong to help to many people
Hi,
thanks :good:
For info: new twrp-3.0.3-x_blu_spark_v12-op3 is out
source: https://forum.xda-developers.com/showpost.php?p=70541197&postcount=2519
@+
Hi, i have oxygen os 4.0.1 rooted and twrp v11 bluspark...But its normal when i deletet some file i dont see immeditely the free space unti i reboot the phone...this happened sometimes and sometimes not...Its a bug?
I have flash as you post, when flash done i check file system by diskinfo, it displayed "userdata not mounted". how do i fix it. plz help me. thank you very much.
Lol this is just what I did:
1. Flash latest @eng.stk TWRP, swipe to allow modifications
2. Wipe system, data, cache
3. Install 1.4GB 4.0.1 zip
4. Wipe dalvik and cache
5. On Mount, check Mount /system as read-only
6. Reboot to system
You now have stock 4.0.1 system, kernel, and recovery.
7. Boot to recovery. TWRP is overwritten by the OOS 4.0.1 recovery.
8. Wipe everything. /data is now f2fs
Optional: flash TWRP, swipe to allow modifications, and do not check Mount /system as read-only to keep it.
No issues at all.
Sent from my OnePlus 3 using XDA Labs
Thank you! Solved my problem with Dm-Verity. Do you think, for the future *4.0.2* update or whatever number will be, that we will be able to flash OTA via TWRP or we'll need stock recovery? Only full zip with TWRP?
You might want to change that TWRP v12 back to v11. Eng.stk found some issues with v12 and pulled it.
And great guide BTW ?
Sent from my OnePlus 3 using Tapatalk
Greetings ?,
After reading this guide i just need to ask several thinks to make clear.
Recently my brothers give me his op3 as he changes to op3t ; . I want to change the phone font and afaik its to impossible to do so without root.
Im currently on 4.0 ; will this guide applicable on my phone ? Or is there a way to change font without root. Thanks in advance
laupuy said:
Hi,
thanks :good:
For info: new twrp-3.0.3-x_blu_spark_v12-op3 is out
source: https://forum.xda-developers.com/showpost.php?p=70541197&postcount=2519
@+
Click to expand...
Click to collapse
I cant't download it from that thread v12 - says file might have been deleted.
mit2nil said:
I cant't download it from that thread v12 - says file might have been deleted.
Click to expand...
Click to collapse
Go to the thread's Downloads tab, download the first file. Ugh it was just mentioned above that v12 was removed.
Sent from my Lenovo A3300 using XDA Labs
VincentJoshuaET said:
Go to the thread's Downloads tab, download the first file. Ugh it was just mentioned above that v12 was removed.
Sent from my Lenovo A3300 using XDA Labs
Click to expand...
Click to collapse
Yup my bad. I was on first page and just used reply button. Never mind.
Answers to your concerns:
I apologize for the late response. I was doing a bit of research to answer all of your questions.
Thank you for your patience!
jackiass said:
Very easy to follow guide. I ended up at B8 "Now you successfully changed your file system to F2FS and decrypted your phone!". I would like my phone to be encrypted, but if I do it through the OS, TWRP does not accept my password for the data partition?
Click to expand...
Click to collapse
Seems like "sideload"ing OOS v4.0.1 didn't change your file system, correct?
I would recommend to start over. When you are done B7, "sideload" OOS v4.0.1 to encrypt the device again. After that's done, continue to section C.
Crazyhat said:
Thanks so much, mate. This is a really good job which is gong to help to many people
Click to expand...
Click to collapse
You're welcome!
Thank you!
I tried very hard on gathering the right information and doing the testing on my OP3.
I almost got it bricked because of OOS v4.0.0, so I decided to post an easy to follow guide.
laupuy said:
Hi,
thanks :good:
For info: new twrp-3.0.3-x_blu_spark_v12-op3 is out
source: https://forum.xda-developers.com/showpost.php?p=70541197&postcount=2519
@+
Click to expand...
Click to collapse
Thank you very much! I have updated the thread.
UPDATE: Reverted back to v11 due to data corruption issues.
playerboys10 said:
Hi, i have oxygen os 4.0.1 rooted and twrp v11 bluspark...But its normal when i deletet some file i dont see immeditely the free space unti i reboot the phone...this happened sometimes and sometimes not...Its a bug?
Click to expand...
Click to collapse
I think it's not normal and you should see an immediate change in your free space.
I couldn't find any information about that.
Your best options are to follow this guide (if you didn't already) AND/OR post this issue in OnePlus 3 community forums.
yohan_xda said:
I have flash as you post, when flash done i check file system by diskinfo, it displayed "userdata not mounted". how do i fix it. plz help me. thank you very much.
Click to expand...
Click to collapse
Did you "sideload" stock OOS in stock recovery OR flash custom ROM via TWRP (I think this one)?
Also, where did you stop (section and number)?
VincentJoshuaET said:
Lol this is just what I did:
1. Flash latest @eng.stk TWRP, swipe to allow modifications
2. Wipe system, data, cache
3. Install 1.4GB 4.0.1 zip
4. Wipe dalvik and cache
5. On Mount, check Mount /system as read-only
6. Reboot to system
You now have stock 4.0.1 system, kernel, and recovery.
7. Boot to recovery. TWRP is overwritten by the OOS 4.0.1 recovery.
8. Wipe everything. /data is now f2fs
Optional: flash TWRP, swipe to allow modifications, and do not check Mount /system as read-only to keep it.
No issues at all.
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Yes, that might be the easy way when you have no issues. But, this guide deals with common issues (dm-verity, twrp password etc.) users face when they tried to update to OOS v4.0.x
If you'll face these issues in the future, you'll know where to find the related guide to fix them.
Hurizen said:
Thank you! Solved my problem with Dm-Verity. Do you think, for the future *4.0.2* update or whatever number will be, that we will be able to flash OTA via TWRP or we'll need stock recovery? Only full zip with TWRP?
Click to expand...
Click to collapse
You are very welcome!
You could flash OTA via TWRP (full size zip and not the small 40mb zip), but I'm afraid that it might "break your root" (you wouldn't have it anymore). It can be fixed by flashing SuperSU.
Technically, you could dirty flash (wipe System, Cache and Dalvik only) the new OTA. If you would have issues after dirty flashing, post your bugs/issues, and most likely you would have to clean flash the OTA.
Give it a try (backup your personal data and dirty flash) or wait for user feedback on the new OTA.
VincentJoshuaET said:
Go to the thread's Downloads tab, download the first file. Ugh it was just mentioned above that v12 was removed.
Sent from my Lenovo A3300 using XDA Labs
Click to expand...
Click to collapse
Thank you for replying back to him! I appriciate it!
mit2nil said:
I cant't download it from that thread v12 - says file might have been deleted.
Click to expand...
Click to collapse
I appologize about that. I have updated the thread.
Explorer23 said:
You might want to change that TWRP v12 back to v11. Eng.stk found some issues with v12 and pulled it.
And great guide BTW
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
With a bit of delay, I've put back the link to v11.
Thank you, and I hope it helped you!
dinesh7208 said:
Greetings ,
After reading this guide i just need to ask several thinks to make clear.
Recently my brothers give me his op3 as he changes to op3t ; . I want to change the phone font and afaik its to impossible to do so without root.
Im currently on 4.0 ; will this guide applicable on my phone ? Or is there a way to change font without root. Thanks in advance
Click to expand...
Click to collapse
Personally, I don't mess around with fonts. But, this guide will be applicable for rooting your phone.
Check the following threads for the fonts: https://forum.xda-developers.com/oneplus-3/help/change-font-t3426785
https://forum.xda-developers.com/oneplus-3/help/how-to-change-font-one-plus-3-t3434351
https://forum.xda-developers.com/android/themes/fonts-flashable-zips-t3219827
https://forum.xda-developers.com/oneplus-3/help/cb7-custom-fonts-t3509759
I hope they help.
I wish I had found this guide before but never mind. I was following original rooting guide by Naman on my OP3 running stock OOS 4.0.1. I used twrp v28 of blue spark and as observed by many I ended up in encryption issues and couldn't take nandroid backup so I didn't proceed.
Now, it seems it has been fixed with latest twrp (v11) by blue spark. My /data partition is already f2fs and cache is /ext4.
What steps should I follow to get back correct recovery and hopefully root as well? I am hoping that I do not need to sideload 4.0.1.
mit2nil said:
I wish I had found this guide before but never mind. I was following original rooting guide by Naman on my OP3 running stock OOS 4.0.1. I used twrp v28 of blue spark and as observed by many I ended up in encryption issues and couldn't take nandroid backup so I didn't proceed.
Now, it seems it has been fixed with latest twrp (v11) by blue spark. My /data partition is already f2fs and cache is /ext4.
What steps should I follow to get back correct recovery and hopefully root as well? I am hoping that I do not need to sideload 4.0.1.
Click to expand...
Click to collapse
I've had all of the issues in this guide. So, I decided to post one because nobody posted in-depth guide to deal with OOS v4.0.1
Also, TWRP v28 has issues with encryption being on and F2FS issues too. It caused all of my problems. I was a bit lucky to find TWRP v19 (had a mouse pointer in the middle of the TWRP, no big deal). It worked with EXT4 and F2FS file systems but wasn't perfect due to working only in decrypted mode.
It seems like you don't have any issues. Am I correct? (No password request in TWRP, dm-verity message)
If you don't, go to section "C - PROCEDURE (FLASHING YOUR CUSTOM ROM)".
About file system - leave it be. Only "/data" should be F2FS, "/Cache" and "/System" as EXT4. To much work to change them to F2FS and TWRP formats them to EXT4 when you wipe them.
dbabaev21 said:
I've had all of the issues in this guide. So, I decided to post one because nobody posted in-depth guide to deal with OOS v4.0.1
Also, TWRP v28 has issues with encryption being on and F2FS issues too. It caused all of my problems. I was a bit lucky to find TWRP v19 (had a mouse pointer in the middle of the TWRP, no big deal). It worked with EXT4 and F2FS file systems but wasn't perfect due to working only in decrypted mode.
It seems like you don't have any issues. Am I correct? (No password request in TWRP, dm-verity message)
If you don't, go to section "C - PROCEDURE (FLASHING YOUR CUSTOM ROM)".
About file system - leave it be. Only "/data" should be F2FS, "/Cache" and "/System" as EXT4. To much work to change them to F2FS and TWRP formats them to EXT4 when you wipe them.
Click to expand...
Click to collapse
I do have both issues DM verity message as well as encryption issue. I just stopped doing any further changes and decided to keep using phone as it after I hit password encryption issue with TWRP as I couldn't take nandroid backup.
mit2nil said:
I do have both issues DM verity message as well as encryption issue. I just stopped doing any further changes and decided to keep using phone as it after I hit password encryption issue with TWRP as I couldn't take nandroid backup.
Click to expand...
Click to collapse
Then start from the beginning.
I was scared to death that I bricked my phone, but managed to get out quickly.
OOS stable for Oneplus 6T Global
This thread is an attempt to make things clean for OP6T users.
It will contain latest zip links for OOS stable.
It will contain a brief guide on how to root, install TWRP , how to update with or without those elements.
6T global edition is supported by thread readers and me, and T Mobile converted specific concerns will be handled by community under the supervision of @Scott, thanks to him for the help.
It will not contain basics like ADB and Fastboot connection with a computer. Experiment, read, there are many and many tutorials on the internet for that. Don’t forget there is a world outside XDA and that you can perform a search on any search engine to grab information.
It will not cover by decision the ‘patching boot.img’ method for gaining root. It’s not necessary to use it when we have a working TWRP and Fastboot. If you want to try it search on the internet about ‘extracting boot.img from payload.bin’ and then use Magisk Manager to patch it.
Please NO discussion about: Magisk itself, custom kernels, debloating (whatever method you want to use), custom ROMS… Only STOCK STABLE OOS.
If you just want to flash custom kernels, no need to have TWRP, Ex Kernel Manager and Franco Kernel Manager for example can take care of that (see Play Store to grab those apps), and backup your stock kernel.
ALWAYS USE LATEST VERSIONS of the different tools used. Don’t ask for help if you’re using 6 months old TWRP or Magisk. Update it first.
First a bit of what I have understood about our phone, and its main specificity, i.e A/B slots.
A/B slots, what else ?
This structure is meant to enable to have two different versions of the SAME ROM, one slot will contain the previous version of the ROM, the other slot will contain the updated one. If you are on slot A and running 10.3.0, the update process will lead to have 10.3.0 on slot A and 10.3.1 on slot B. On next boot the bootloader will automatically boot updated one (i.e slot B will be flagged as the active one). In case of issues during boot process the bootloader will switch the active slot back to the ‘old’ version(here slot A) that was booting fine.
This means that IT’S NOT a dual boot feature!! If you want to run a custom ROM it’s better to have the same custom ROM on both slots and not a mix of OOS and custom ROM. But that’s already OT so let’s stay focus, each custom ROM should provide clear instructions about that.
Having a slot phone means that there is no Recovery partition. So if you ‘fastboot flash boot twrp.img’ it will overwrite your boot partition and thus the ROM kernel and can lead to issues. The .img file is only meant to be temporarly booted. Recovery (stock or TWRP) is a part of the boot ramdisk.
Some simple facts about slots and flashing in TWRP:
Flashing a whole ROM (OOS for example) will automatically flash it to the currently inactive slot and switch it to be the active one (that works also with stock recovery, when performing a ‘local update’)
Flashing a ROM overwrites completely the boot partition (in recent Android versions, flashing process is using partition RAW images and not files like it was before): that means that TWRP and Magisk (if present) will be ERASED.
Flashing TWRP installer will flash it AUTOMATICALLY ON BOTH SLOTS (and will erase Magisk if present)
Magisk (and GAPPS but it only applies to custom ROMs), when flashed with TWRP is only flashed in ACTIVE slot. That’s why you must REBOOT to recovery BEFORE flashing Magisk to have it installed on the active updated slot. And that explains why you must flash it last.
That said, if you stay on OOS, YOU DON’T care about slots, just remember those basics to understand why you have to respect some steps, and let the recovery take care of slots. Messing manually with them results often in soft bricks
Downloads
OOS stable full signed zips: thanks to @Some_Random_Username, @Titokhan, @trollavin (their thread here)
If the above doesn’t work anymore just let me know I’ll find something else.
FYI you can still go to Oneplus website but they take time to update it to latest version… And there is no archives.
XDA:DevDB Information
OOS Stable thread support, ROM for the OnePlus 6T
Contributors
Striatum_bdr, Scott
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-02-05
Last Updated 2020-02-06
Rooting
CHANGELOGS
OOS 10.3.4:
System
Updated launcher version to 4.1.6
Updated Android Security Patch to 2020.05
Improved system stability and fixed general bugs
Phone
Fixed the issue with default country in assisted dialing when SIM2 is in roaming state
Newly added Work-Life Balance to help prioritize notifications and allocate time wisely (India only)
Newly added Epic Games in Game Space (India only)
OOS 10.3.3:
System
Fixed the issue with a black screen randomly appearing while playing games
Updated GMS package to 2020.02
Updated Android Security Patch to 2020.04
Improved system stability and fixed general bugs
Network updates
Integrated VoLTE & VoWifi support for Telenor – Denmark
Integrated VoWifi support for RJIO – India
Phone
Newly added OpSoprts features in the shelf
Added OnePlus Roaming feature: choose a plan without worrying about the SIM card while traveling
Cloud Sync updates [India only]
Updated the CloudService to Version 2.0
OOS 10.3.2:
Changelog 10.3.2
System
• Fixed the screen flickering issue while swiping up to unlock
• Improved system stability and fixed general bugs
• Updated Android security patch to 2020.02
OOS 10.3.1:
Changelog 10.3.1
System
Fixed the issue with a black screen appearing after unlocking the device using fingerprint
Fixed the issue with the animation logo while rebooting the device
Fixed the issue with device heating up while charging
Fixed the random disconnection issue with 5Ghz Hotspot
Improved system stability and fixed general bugs
Updated Android security patch to 2019.12
Camera
Optimized the image preview time in the Pro mode
Fixed the camera crash issue
Gallery
Fixed the issue with videos and images not displaying in Gallery
OOS 10.3.0:
Changelog 10.3.0
System
Updated system to Android 10
Brand new UI for Android 10
Fixed the automatic reboot issue
Added the notch area display option in the Settings (Settings - Display - Notch display - Hide the notch area)
Fixed the issue with lock screen appearing even after unlocking the device with the password
Fixed the issue with Navigation bar after upgrade
Fixed the Digital wellbeing option missing in the settings
Updated Android security patch to 2019.11
Fingerprint
Fingerprint unlock functionality improvement
Enhanced the fingerprint animation
Camera
Camera performance improvement
Wifi Connectivity
Fixed the issue of Wifi connection to 5Ghz networks
OOS 10.0.1:
Changelog 10.0.1
System
Updated system to Android 10
Brand new UI for Android 10
Updated Android security patch to 2019.10
Fixed the fingerprint identification issue
Fixed the animation lag for fingerprint unlock
Fixed the automatic reboot issue after upgrade
Camera
Improved the performance and fixed known issues
Wifi Connectivity
Fixed the 5Ghz WiFi connection
OOS 10.0.0:
Changelog 10.0.0
System
Upgraded to Android 10
Brand new UI design
Enhanced location permissions for privacy
New customization feature in Settings allowing you to choose icon shapes to be displayed in the Quick Settings
General bug fixes and improvements
Full Screen Gestures
Added inward swipes from the left or right edge of the screen to go back
Added a bottom navigation bar to allow switching left or right for recent apps
Game Space
New Game Space feature now joins all your favorite games in one place for easier access and better gaming experience
Contextual Display
Intelligent info based on specific times, locations and events for Ambient Display (Settings - Display - Ambient Display - Contextual Display)
Message
Now possible to block spam by keywords for Message (Messages - Spam - Settings - Blocking settings)
ROOTING (+/- TWRP)
Magisk zip is to be found here
TWRP latest .img and installer are to be found here
Don’t use all-in-one tools, you’re a grown up person you can to it by yourself. Yes you can.
If you're not rooted and run an OOS version older than 10.3.1, update your phone normally to latest OOS stable version then do as below
If you’re not rooted and running 10.3.1 or higher, those are the simplest steps to gain root.
Unlock your bootloader (will wipe everything…): “fastboot oem unlock” from a computer (see beginning of OP to know why I don’t detail this) with phone in fastboot mode
Grab latest Magisk zip on your phone and latest TWRP .img on your computer (AND TWRP installer .zip on your phone if you want to install TWRP permanently). Boot in fastboot mode your phone.
Then :
“fastboot boot twrp_latest.img” (adapt to the name and path of your twrp file)
within TWRP, flash TWRP installer .zip if you want to keep TWRP
flash Magisk zip (always AFTER flashing TWRP)
Reboot
(you can theoretically use the TWRP feature ‘install recovery ramdisk’ to avoid flashing twrp installer but never tested)
Note: please STOP using blue_spark TWRP!!! Support for OP6T has been stopped long time ago, only OP6 twrp is still actively supported by eng.stk (errors are mandatory if you flash it on 6t). I even see people that use a 3.2.x version of blue_spark...
UPDATING WITHOUT ROOT
If your bootloader is locked (meaning no root no TWRP, factory state), the update process is trivial, OOS (or Oxygen Updater if you use it) will grab a patch file (around 100MB max usually) and will apply it and will ask you to reboot. Everybody should be able to do this as it’s the normal way every phone on earth updates itself… If major changes are present sometimes you’ll have the whole ROM file. It doesn’t matter anyway it leads to the same destination.
If your bootloader is unlocked but without root, the only difference is that OOS (or Oxygen Updater) will download the WHOLE ROM (around 1.8GB) and will apply it then ask for rebooting
UPDATING WITH ROOT (+/- TWRP)
Whole ROM update is mandatory. You can wait for System Update to download it or grab manually the zip file or use Oxygen updater. You then go in Settings > System > System Update > clic on the upper right cogwheel then choose ‘Local Update’ and select the zip file (If you download the OTA .zip file manually you must place it in the root of user data, like /data/media/0/ i.e the user internal storage, or eventually in the .OTA folder if there's one. If you use Oxygen Updater or System automatic donwload it will be right placed).
The following update method is the preferred one (even if you have TWRP, recommended by some TWRP devs) due to frequent changes in partitions by OnePlus
apply the ROM update via Settings > System > System Update > Local Update
DON’T REBOOT
Open Magisk Manager
[If you have TWRP, go in Modules menu, clic on ‘+’ and choose latest TWRP installer zip file on your phone. Don’t use Retention A/B Script Magisk Module I had issues with it] [then stay in Magisk Manager and do the next step]
On main screen of the app clic on ‘install’ next to Magisk paragraph
On the pop up menu confirm ’Install’
On the next pop up menu clic on the last entry: install on inactive slot (after OTA update)
Then only reboot.
The order can be changed (the most important thing to preserve is Magisk, TWRP is easy to flash back):
Update without taking care of TWRP, just Magisk part ("install to other slot after OTA thing")
Once rebooted to updated system, flash TWRP as a module with Magisk Manager
Install Magisk again using Magisk Manager ("direct install" option)
There are infinite debates about uninstalling or not Magisk Modules before updating. Most of the times nothing to touch, sometimes there could be issues, instead of uninstalling perhaps just inactivate them by precaution before updating.
Note: If you are rooted and run an OOS version older than 10.3.1, the above method should work, but you can also update your ROM to latest stable without taking care of root/TWRP and then root again as described in post #2
If you want to try TWRP way:
Reboot to TWRP
Flash OOS update
Flash TWRP installer
Reboot to Recovery
Flash Magisk
Reboot System
IF YOU ARE INTO A SOFT BRICK
Don't forget the Vol+/Vol-/Power_button combo that can save you from a non responding phone...
If you can boot in fastboot mode, flash the stock ROM with fastboot. A little trick is to edit the flash-all-partitions**.bat and remove ‘-w’ (-w means that the partition will be wiped before flashing) from the script, it will prevent personal data wipe. Or flash manually all partitions one by one, without ‘-w’ flag evidently. Some partitions can’t be flashed with fastboot, for that once booted back to OOS, download and install by ‘local update’ method the same ROM version you’ve just restored with fastboot (see the linked thread to know why, emojis issues for example sometimes).
If you can’t go in fastboot mode, use Oneplus MSM tool. See there and there.
Thank you for the time and effort for this thread as I just came from a Sony XZ1 as I was a bit confused by the different posting on how to do what...
Thanks for a detailed post.
Can I update my rooted OP6T 9.0.17 (TWRP 3.3.1-2+ Magisk) directly to rooted 10.3.1 using the following guide :-
1. Reboot to Twrp 3.3.1-2.
2. Flash Twrp 3.3.1-31 installer.
3. Rebbot to recovery twrp 3.3.1-31.
4. Flash Magisk uninstaller
5. Flash 10.3.1 OS
6. Flash TWRP 3.3.1-31 installer
7. Reboot to recovery.
8. Flash Magisk.
9. Reboot to system.
Goormeetsingh said:
Thanks for a detailed post.
Can I update my rooted OP6T 9.0.17 (TWRP 3.3.1-2+ Magisk) directly to rooted 10.3.1 using the following guide :-
1. Reboot to Twrp 3.3.1-2.
2. Flash Twrp 3.3.1-31 installer.
3. Rebbot to recovery twrp 3.3.1-31.
4. Flash Magisk uninstaller
5. Flash 10.3.1 OS
6. Flash TWRP 3.3.1-31 installer
7. Reboot to recovery.
8. Flash Magisk.
9. Reboot to system.
Click to expand...
Click to collapse
That sounds correct
Thank you for taking the time to do this. I am now subscribed
Very nice. Subscribed. Thank you.
I've been trying to do this for the past 8 hours.
Here's what I do, please tell me where am I going wrong
- msm 9.13
- update to 9.17
- local upgrade to 10.3.1
- boot system to enable oem unlock, usb debug
- boot to fb, unlock bootloader
- boot system
- boot fb, boot twrp
- flash twrp, both slots
- reboot twrp
here I get different results:
- try to install magisk, all internal storage encrypted. sideload, but still no cigar. try to install on both slots by rebooting twrp to a and b and sideloading magisk, still no cigar
OR
- flash magisk, boot system, no magisk
OR
System boots, we have root, we have everything, but file manager shows emptyness. Can't modify any files on internal storage. Via phone and via PC.
Now tell me what am I doing wrong, please
jazzgott said:
I've been trying to do this for the past 8 hours.
Here's what I do, please tell me where am I going wrong
- msm 9.13
- update to 9.17
- local upgrade to 10.3.1
- boot system to enable oem unlock, usb debug
- boot to fb, unlock bootloader
- boot system
- boot fb, boot twrp
- flash twrp, both slots
- reboot twrp
here I get different results:
- try to install magisk, all internal storage encrypted. sideload, but still no cigar. try to install on both slots by rebooting twrp to a and b and sideloading magisk, still no cigar
OR
- flash magisk, boot system, no magisk
OR
System boots, we have root, we have everything, but file manager shows emptyness. Can't modify any files on internal storage. Via phone and via PC.
Now tell me what am I doing wrong, please
Click to expand...
Click to collapse
I think you should format data after unlock. I think it's kinda safety feature if some1 try to get into your storage by unlock bootloader. But wait by some1 to confirm
jazzgott said:
I've been trying to do this for the past 8 hours.
Here's what I do, please tell me where am I going wrong
- msm 9.13
- update to 9.17
- local upgrade to 10.3.1
- boot system to enable oem unlock, usb debug
- boot to fb, unlock bootloader
- boot system
- boot fb, boot twrp
- flash twrp, both slots
- reboot twrp
here I get different results:
- try to install magisk, all internal storage encrypted. sideload, but still no cigar. try to install on both slots by rebooting twrp to a and b and sideloading magisk, still no cigar
OR
- flash magisk, boot system, no magisk
OR
System boots, we have root, we have everything, but file manager shows emptyness. Can't modify any files on internal storage. Via phone and via PC.
Now tell me what am I doing wrong, please
Click to expand...
Click to collapse
I know you managed to sort things as you posted it in another thread. Anyway I don't understand why you had to do all those steps .... But anyway the goal is achieved
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Scott said:
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Click to expand...
Click to collapse
THANK YOU VERY MUCH. Several of us out here!
Scott said:
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Click to expand...
Click to collapse
Welcome back sir Scott!
---------- Post added at 03:27 AM ---------- Previous post was at 03:26 AM ----------
Thank you for this thread.
Scott said:
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Click to expand...
Click to collapse
hodgestl said:
THANK YOU VERY MUCH. Several of us out here!
Click to expand...
Click to collapse
I second this, thank you and also thanks to OP!!
Is there any way we could get a change log for the stable update?
hodgestl said:
THANK YOU VERY MUCH. Several of us out here!
Click to expand...
Click to collapse
r3dp0is0n2012 said:
Welcome back sir Scott!
---------- Post added at 03:27 AM ---------- Previous post was at 03:26 AM ----------
Thank you for this thread.
Click to expand...
Click to collapse
..Cory.. said:
I second this, thank you and also thanks to OP!!
Is there any way we could get a change log for the stable update?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Your all welcome!
I love this phone and like to help so lets see how this goes down :good:
...
---------- Post added at 10:48 PM ---------- Previous post was at 10:39 PM ----------
As far as the change log, that could be a challenge. I have never been able to find the full change log for the international version. The T-Mobile Version is here: https://www.t-mobile.com/support/devices/android/oneplus-6t/software-updates-oneplus-6t. Because this is something we can direct link to, I dont think it should be included in full text here on XDA. I think a link the in first or second post under "useful info" would be sufficient.
As far as the international version goes, I know every verison number by heart.. worst case scenario, I could just google each OTA version and grab the change log from the from the first Android news site that pops up. Unless someone else knows of where one might be at? We could also start at version 10.0.0 because I feel anything older than that is irrelevant.
For changelogs it could be done eventually by grabbing them on the net. There is clearly something between Oneplus and changelogs....
I'm ask for an extra reserved post to have more space and avoid too long posts.
Changelogs added in post #4
Scott said:
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Click to expand...
Click to collapse
Awesome. I've been running a converted TMobile phone and can't wait b for them to related A10 so I can have android pay back without root
Installing Lineage
Few quick things.
LOS 18.1 is now official so the guide will now just be covering that.
I also want to address a common question, you can use Windows for this process. I prefer Linux, and Fastboot just works in Linux without driver issues. If you have Fastboot and ADB working in Windows already feel free to use that if you want.
Frequently asked Questions:
This looks like a lot of work, is there an easier way to install? Try the LOS Wiki Method.
Using TWRP 3.5.2_9-01. Start off Fresh. Install OOS using the Fastboot ROM.
Start off with a fresh install of OOS. You need the latest version of OOS 10. I typically use a the fastboot ROMs for this as it will do both slots for me at once. (Alternatively you can use TWRP and install the ZIPs and do it twice to get it on both slots, or my least favorite, the MSM Tool if you want. Doesn't matter how OOS ends up on both slots, as long as it ends up on both slots.)
I use Linux, and honestly I feel like it's easier and more reliable for fastboot and ADB so that's what I'm including here in these steps. It's easy to boot from a USB.
To create a bootable Linux flash drive you can use Unetbootin, which you can download for free here (Your other option would be to burn the ISO straight to a DVD and skip the unetbootin step):
https://unetbootin.github.io/
For Linux, I'm using Linux Mint Cinnamon, You can download for free here:
https://www.linuxmint.com/download.php
Then run unetbootin (yours will look a little different, I'm running it in Linux):
{
"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"
}
Point it to the Linux ISO, and tell it where an empty flash drive is. It will erase everything on the flash drive. Afterwards you can load whatever you want on the flash drive. However be aware when booting Linux from this drive you can't access what is on the drive (at least not by normal methods).
After this has successfully completed, reboot the PC, and boot from the USB drive. Your PC will boot into Linux (turning off the PC and removing the USB drive will make it boot up like normal again).
Next we need to install fastboot and adb. You need to open up the "start menu" and open the "synaptic package manager". You can find this stuff in the menus, however the easiest way to get to these items is to just start typing the name of the item. See below:
Search fastboot, click the boxes, choose install. Then search for ADB, click the boxes, choose install and then click apply. It's that easy it will download everything that's needed and install.
Time to open up a terminal:
Just to make sure we don't run into any problems we need to update adb and fastboot. In the terminal run these commands to update fastboot and adb (this is downloading them directly from Google).
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
sudo cp platform-tools/adb /usr/bin/adb
sudo cp platform-tools/fastboot /usr/bin/fastboot
You will also need the appropriate fastboot ROM. Fastboot ROMs available in this thread. The catch being that thread is no longer updated. So we will need to make our own fastboot rom. To do this we need two things:
1. The stock rom zip (OP Site).
2. Payload dumper. I've yet to get the one from the GitHub link to work, so I've been using the one from this Article. Direct Download Link
You need to extract the payload.bin file from the stock rom zip. Extract the payload_dumper files as well, and place everything in the same folder. Payload_dumper requires python3. Open up Synaptic again, search for python3.6 and install it. Now open a terminal so we can extract the images from the payload.bin.
Navigate to the location of payload_dumper and your payload.bin file. In my case my commands are:
cd Desktop <-- switches to the Desktop folder
cd payload_dumper <-- switches to the payload_dumper folder on the Desktop
python3 payload_dumper.py payload.bin <-- runs the payload_dumper "program" and extract the images from the payload.bin
Now would be a good time to back everything up. The phone will get wiped. Extract the fastboot images to a folder that is easy to find. I would recommend the Desktop.
Now it's time to flash all those images we just extracted using payload dumper. Place the phone in fastboot mode. You can do this using the advanced reboot menu, ADB, or the key combinations (all key combos listed below for reference):
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
You can flash the images one by one or use a script. My script is available here. Flashing the fastboot ROM should look something like this:
That image explained:
cd Desktop <-- Switched the directory to the Desktop the default directory when you open up the terminal is the /home directory.
cd flash <-- I put my fastboot images in a folder called flash. This stuff is case sensitive. My folder was all lowercase.
sudo fastboot devices <-- Is just checking to see if my PC can see my phone, and making sure it's in fastboot. Sudo is necessary for this distro, as both fastboot and ADB must be run as root.
sudo sh FlashThese.sh <-- Tells the terminal to run my script, since the script contains fastboot commands it must be run as root.
At the end you should get something like this:
Then just choose start form Fastboot (If you were previously on a custom ROM go straight to recovery and wipe everything). Not booting and getting dumped off at the OnePlus recovery screen is nothing to worry about. Choose your language of choice, Wipe data and cache, Erase everything (Music, pics, etc), This can not be undone, continue. After that the phone will boot. Once booted enable developer options, advanced reboot, and reboot to fastboot.
2. Installing TWRP.
First step is to boot the correct TWRP image. Grab the current TWRP from the official site. You need both files, the img file, and the installer. Once again from the terminal:
The image explained:
cd Desktop <-- Switched the directory to the Desktop the default directory when you open up the terminal is the /home directory.
sudo fastboot devices <-- Is just checking to see if my PC can see my phone, and making sure it's in fastboot. Sudo is necessary for this distro, as both fastboot and ADB must be run as root.
sudo fastboot boot twrp-3.5.2_9-0-fajita.img * <-- Sends that TWRP image to the phone to be booted temporarily. Only boot this, never run the command "flash".
Once in TWRP the phone should show up as a media device so you can copy files to it. Copy the TWRP installer over to it. Choose Install from the TWRP menu and navigate to where you placed the TWRP installer. Press on it, and swipe to confirm flash. When it is done hit the back button until you are back out to the main menu.
From the main menu choose reboot, and choose Recovery:
The first time you try and reboot the official version of TWRP it will ask you if you want to install the TWRP app. Do NOT install the app. In the settings you can disable this prompt. Your other option is just uncheck both boxes at the screen you see below when you get to it, and then click the button that says do not install. Do use the slider. At that point the phone will reboot as to recovery as you selected.
Now that you are back in TWRP that is now installed, time to wipe the phone. From the main menu choose Wipe. Swipe the factory reset slider at the bottom. Then hit back. Next hit Format Data. Type Yes to Continue. Hit back to continue. Keep hitting back till you get to the main menu.
Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. So go back into the reboot menu, choose reboot to recovery again (swipe to allow modifications if it asks). You must do this after formatting data.
3. Install Lineage
Links:
Lineage 18.1 XDA Thread
Official 6T Lineage Downloads
The phone should still be in TWRP at this point. You now need to copy Lineage to the phone. From TWRP's main menu choose install. Then navigate to your ROM .zip location and click on it. Then swipe to confirm flash.
Lineage will replace TWRP, so you need to reflash TWRP as well. Run the TWRP installer again. If it's not on the phone, just copy it over again real quick. On A/B devices ROMs get flashed to the opposite slot. Things like Gapps, Magisk, etc get flashed to the current slot. We need Lineage on both slots, so it must be flash again. Flashing it twice only needs to be done the first time as we need to get rid of OOS. For updates it just gets flashed once. After the TWRP installer has run, back out to the main menu, and choose reboot, then recovery:
Once back in TWRP flash Lineage again. From TWRP's main menu choose install. Then navigate to your ROM .zip location and click on it. Then swipe to confirm flash.
Now run the TWRP installer again. Back out to the main menu, and reboot to recovery.
4.Optional, Gapps
Links:
NikGapps <-- For Lineage 18.1 (Use the R Folders for Android 11. I recommend the "Core" version. I also tested Basic though if you want that level of Gapps. I strongly recommend you grab setup wizard out of the R Addons Folder, I used the regular setup wizard, not the pixel one.)
MindTheGapps <-- It's worth mentioning here Lineage recommends MindTheGapps for 18.1. Take your pick. I personally use NikGapps as I can use a "leaner" Gapps package.
Now that your phone is back in TWRP for the last time before booting up Lineage, it's time to install Gapps if you want them. This step is optional. Same as the other steps here, go to install, choose your OpenGapps package, Then navigate to your .zip location and click on it. Then swipe to confirm flash.
5. Very Optional, Magisk
These steps are very optional. However this is how I, root, pass safety net, and get a various apps to appear in the Play store.
Flash Magisk in TWRP. For Magisk 23, you now have to rename the Magisk.apk to Magisk.zip. Then flash it in TWRP. If you wanted to uninstall it, you rename it to uninstall.zip. If you already had an older version of Magisk installed, make sure you do not have it hidden / nenamed when installing Magisk 23 for the first time. Restore the original package before installing 23.
Magisk <-- Flash this right after Gapps.
These items are add-ons are flashed in Magisk after the first boot (Don't flash these in TWRP anymore):
MagiskHide Props Config
Busybox
To flash modules in Magisk press the puzzle piece icon. Then choose install from storage. Now just choose your addons. After flashing the icons it will have a reboot icon at the bottom. You can reboot or you can press back and flash another. After you are done reboot.
You will also need a Terminal Emulator. I personally use:
Terminal Emulator for Android
Once all these are installed the first step is setup Magisk. Under Magisk go to settings:
In version 20.4+ Magisk Hide is no longer on by default. So make sure the Magisk Hide, Hide Magisk from various forms of detection switch is flipped. Then press Hide Magisk Manager. This will bring up a box for you to choose a random name for the Magisk Manager, type whatever you want here. You can leave it Manager if you wish, but I typically change this.
Now open Magisk again. It will ask you to download it again, click ok, then manually open the app again as it says. Now we need to open Magisk hide. This is now under the shield icon, then click the arrow at the top:
These are the apps you don't want to know that you have root. Less is better. You can cause instability problems by just choosing everything. My general rule of thumb is, Google, steaming video, music, and payment apps get selected. In my experience if I come across an app that needs it and I didn't select it, I just clear cache and/or data and re-open the app and it works. There are some big multiplayer apps that ban hardware / people, so do your research (don't ask me, I don't play those games).
Next time to change the device fingerprint using MagiskHide Props Config Module. We do this using the terminal emulator. In the terminal emulator, type "su" to gain root privileges. Then type props to run the module:
Now it's just following the menus. Choose option 1 - Edit device finger print. (type 1, hit enter)
After this you will see a menu of devices. It doesn't matter what device you pick really. If you want apps / Google to think you have a OPPO or Samsung pick one of those Fingerprints. However there's a bit more to passing Safety-net than that. Since Google has changed how things work not all those fingerprints that used to work will work now. Also now you may get an error when you turn on the phone because of the security dates. The OP6T Android 10 fingerprint has no issues at this point, so use that if you want:
After choosing the fingerprint you want, it will ask you if you want to reboot. Choose yes. After rebooting, you may need to clear the cache from the play store for some apps to appear in it. You should now pass safety net. Check this in Magisk:
6. Very Optional, Ad Blocking with a Host File.
You can block many things with a hosts file, most popular would be ads. I've been use StevenBlack's host file which is a compilation of several hosts files. This is located on Github:
https://github.com/StevenBlack/hosts (Scroll down you'll see the options of what you can block)
Direct link to the hosts file I use. This will block Adware / Malware.
Unfortunately for quite some time now on this device you can no longer just use a root browser to swap the hosts file. The easiest way is to use TWRP.
First we have to make the hosts file. The hosts file must use unix / linux line endings. If you are using linux, don't worry about this, just create the file. If you are using Windows, the easiest thing to do is use Notepad++ (Free).
Notepad++ Downloads
Next one other caveat. The hosts file is quite large. I've never had much luck copy and pasting it from any other browser than Firefox (Windows or Linux), but however you get it into Notepad++ is not a big deal.
Once in you have the hosts file into Notepad++ go to Edit, EOL Conversion, and Choose Unix (LF).
Now save the file as "hosts" no ending. This does mean under file type you will need to change it to All File types *.*. Move this hosts file to your phone. Then reboot to recovery. From the main TWRP menu, choose mount. Then mount system:
Hit the back button and go to the advanced menu. Choose File Manager:
You will find your hosts file under /sdcard, wherever you placed it. In my case I placed it in a folder called ROMs. Once you locate it, press and hold it for a moment, and relase. Then choose copy file:
At this point you need to tell TWRP where you want to paste the hosts file. It belongs in the /etc folder. The only hic-cup here is depending on what you were doing in TWRP this could be (on this device) /system/etc or /system/system/etc (you will see similar folders to the image below if you are in the right place). Once you are there, press "paste?" button in the lower right corner:
After this just swipe to confirm:
You can now reboot the device, and your hosts file should now be in place. Your ad block should now be active for all apps as it's global for all connections.
7. Reboot to system.
Updating Lineage
1. Flash Lineage.
Reboot to recovery. You can use the advanced reboot menu, or Volume Down + Power while turning the phone on. Don't wipe anything. From TWRP's main menu choose install. Then navigate to your ROM .zip location and click on it. Then swipe to confirm flash.
Lineage will replace TWRP, so you need to reflash TWRP as well. Run the TWRP installer again. After the TWRP installer has run, back out to the main menu, and choose reboot, then recovery:
2. Optional, Gapps (if you installed them once you must continue to install them or do a clean install)
Links:
NikGapps
Now that your phone is back in TWRP for the last time before booting up Lineage, it's time to install Gapps if you want them. This step is optional. Same as the other steps here, go to install, choose your OpenGapps package, Then navigate to your .zip location and click on it. Then swipe to confirm flash.
3. Reboot to system.
Last updatedSince I don't want people to have to wonder if these instructions are current, I am going to periodically test and update this post with my results. Please note I'm testing with a 6T, TMobile 6Ts are different. You can generally assume previous versions of LOS and OOS were also tested, but if you are unsure feel free to ask in this thread.
Last tested with:
OOS 10.3.7 and LOS 17.1 12-31 with TWRP 3.4.0-2
OOS 10.3.11 and LOS 18.1 05-27 with TWRP 3.5.2_9-0
This method has also been tested with:
OOS 10.3.3 and Omnirom 5-24 MicroG and Omnirom 5-24.
Cliff Notes
*TWRP 3.5.0_9-0+ Must be used with LOS 18 / 18.1
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery (This step wipes the device, make sure you backed everything up!)
- Factory Reset. (This is the slider at the bottom, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else)
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the AOSP rom on both slots, only do this for the first install)
- Flash Gapps (Optional)
- Flash Magisk (Optional) (Remember for ver 22 the Magisk.apk gets renamed to Magisk.zip, can also be renamed to uninstall.zip for uninstalling)
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
After this you should be able to update Lineage as normal.
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Optional, but if you flashed them once you have to keep flashing them.)
- Flash Magisk. (Optional)
- Reboot to system.
- No loss of data, or anything.
Thanks for the guide, able to flash los 17.1 successfully.
How to go back to OOS?
Does anyone have a guide on how to go back to OOS after flashing Lineage according to Lineage's instructions?
fordjonathan said:
Does anyone have a guide on how to go back to OOS after flashing Lineage according to Lineage's instructions?
Click to expand...
Click to collapse
Back up your data, use Step 1 of these instructions. That will put OOS back on your phone.
MSM Tool, always my least favorite option, but always an option.
MSM Tools for Regular 6T (TMobile uses a different one)
installed 17.1!
OhioYJ said:
Installing Lineage...
Click to expand...
Click to collapse
Massive thanks for your instructions!
- at first, I tried upgrading from LOS 16.0 to LOS 17.1. I followed the instructions on the wiki, but it landed me in the qualcomm crashdump mode.
- after that I ran into your instructions, and tried to follow your update guide, but it didn't help (not very surprising I guess, but I haven't had much to lose at this point ).
- after that, I just followed your fresh install guide (i.e. flashing the fastboot room and starting from scratch), followed every step and it worked!
I wonder if it's worth updating lineage OS wiki and pointing to your instructions? There is bunch of people in this thread, who also bricked the phone into crashdump, so perhaps it could help to prevent it for someone else.
Updating to LOS 17.1 ?
Dasseem said:
Thanks for the guide, able to flash los 17.1 successfully.
Click to expand...
Click to collapse
Initially I had problems with updating LOS, so I returned to Stock. As more people attempted to install LOS, and this fine Original Poster "Ohio" offered such excellent, and detailed instructions, I have been running LOS 16 since February.
However, I have not updated it, since I have had Zero Issues.
But to clarify, you used this method to update to LOS 17.1 ?
- coming from LOS 16 - without first returning to a fast-boot ROM ?
Did you up-date GApps accordingly during this Flash ?
Thank You, in advance, for any assistance!
:good:
barguybrady said:
But to clarify, you used this method to update to LOS 17.1 ?
- coming from LOS 16 - without first returning to a fast-boot ROM ?
Click to expand...
Click to collapse
Hi, I updated my previous reply to make it a bit more clear!
Yep, I was on LOS 16. Haven't had any issues, but figured why not update if I'll have to do it eventually
So I downloaded 17.1 and used the wiki instructions, which messed the phone up
Ended up flashing fastboot rom and starting from scratch, flashed gapps and magisk according to OhioYJ's instruction and it worked.
Flashing method
barguybrady said:
But to clarify, you used this method to update to LOS 17.1 ?
- coming from LOS 16 - without first returning to a fast-boot ROM ?
Did you up-date GApps accordingly during this Flash ?
Thank You, in advance, for any assistance!
:good:
Click to expand...
Click to collapse
I was using carbon ROM previously, had to move to OOS latest for flashing the lineage 17.1, believe it needs to be done if you are coming from pie, people know better correct me if I am wrong here.
As Karlicoss mentioned, it's better to follow the method posted by Ohio.
OhioYJ said:
Cliff Notes Versions
Installing Lineage
- Install fastboot ROM boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk if you use Magisk. Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone may restart once, then Lineage will start up and all will be good.
Updating Lineage
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (Optional If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
Click to expand...
Click to collapse
Updating failed for me, as it shows everything encripted once I reboot the second time to recovery on slot B...
badpanda said:
Updating failed for me, as it shows everything encripted once I reboot the second time to recovery on slot B...
Click to expand...
Click to collapse
Usually this means you didnt format data, or you are using an old version of TWRP. Did you do a clean install?
I just tried it on my phone, was running 4-12 build, using 3.3.1-32 TWRP, updated to the 4-14 build, using 4-14 Gapps (nano), everything went smoothly here.
OhioYJ said:
Usually this means you didnt format data, or you are using an old version of TWRP. Did you do a clean install?
I just tried it on my phone, was running 4-12 build, using 3.3.1-32 TWRP, updated to the 4-14 build, using 4-14 Gapps (nano), everything went smoothly here.
Click to expand...
Click to collapse
No, no clean install. Just wanted to update to today's newest build os.
bump...
Thanks a lot for your guide. Very helpfull.
I'm using it with /e/ rom.
installing android 10 roms
I followed exactly as it was written. Same issues arose for me. After the phone is off then turned on no LTE. It makes phone calls and also text stuff. HOWEVER when you take out and reinsert sim LTE is enable. What is the problom?????????
sickpoppy said:
I followed exactly as it was written. Same issues arose for me. After the phone is off then turned on no LTE. It makes phone calls and also text stuff. HOWEVER when you take out and reinsert sim LTE is enable. What is the problom?????????
Click to expand...
Click to collapse
Just cycling airplane mode doesnt work? This isn't a TMobile 6T is it? You are in Sim slot 1? You maybe better asking in the LOS thread, and provide log it not working and then it working when you reinsert it. Im not quite sure whats going on there.
OhioYJ said:
Usually this means you didnt format data, or you are using an old version of TWRP. Did you do a clean install?
I just tried it on my phone, was running 4-12 build, using 3.3.1-32 TWRP, updated to the 4-14 build, using 4-14 Gapps (nano), everything went smoothly here.
Click to expand...
Click to collapse
So this means you do have to always format data for every single update??
---------- Post added at 09:07 PM ---------- Previous post was at 09:05 PM ----------
sickpoppy said:
I followed exactly as it was written. Same issues arose for me. After the phone is off then turned on no LTE. It makes phone calls and also text stuff. HOWEVER when you take out and reinsert sim LTE is enable. What is the problom?????????
Click to expand...
Click to collapse
Change your sim card to the other slot...
---------- Post added at 09:11 PM ---------- Previous post was at 09:07 PM ----------
@OhioYJ So for an update you boot to recovery flash LOS latest version then flash twrp again and then reboot to recovery second time then format data to possibly decript encrypted system and, transfer files both gapps and magisk to device and then install gapps and magisk, lastly just reboot to system?
reply
yes it is a tmobile but it was flashed to global. TWRP is the version you are using. downloaded the lastest ROM. Weird it finds LTE at first then like I said when then phone shuts off LTE doesnt work til I take sim out.
badpanda said:
So this means you do have to always format data for every single update??
Click to expand...
Click to collapse
No that would be ridiculous. Not necessary at all. You have something else going on, but I dont know what. My update procedure is exactly as listed on the OP, on two 6Ts, two different carriers.
sickpoppy said:
yes it is a tmobile but it was flashed to global. TWRP is the version you are using. downloaded the lastest ROM. Weird it finds LTE at first then like I said when then phone shuts off LTE doesnt work til I take sim out.
Click to expand...
Click to collapse
A TMobile "converted" to global does not equal a global 6T. Logs posted in the LOS thread, may help out other TMobile users? The TMobile 6Ts introduce all sorts of quirks, and Im afraid I dont have any experience with them, so hopefully another TMobile user will be able to help.
NOTICE: crDroid 7.x (Android 11) is now in maintenance-only release mode, and will probably be End-Of-Life'd soon.
I'll be merging monthly Android Security Bulletins from upstream as they're available, and pushing releases, but they're blind builds at this point and I don't have time to troubleshoot them any longer.
Please consider updating to crDroid 9.x (Android 13):
crDroid 9.x XDA thread - OP 6/6T
{
"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"
}
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring you many of the best features in existence today.
Features
A quick glossary and primer on flashing & slots for A/B devices (like ours):
Spoiler: Show/Hide
- "Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip (usually by either wiping or formatting data, see below).
- "Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
- "Wipe data": Synonymous with "factory reset", accomplished from TWRP recovery by selecting "Wipe", then performing the "Slide to factory reset". Clears user data without erasing any partitions, removing encryption, or deleting contents of internal storage.
- "Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
- "User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
- "OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system.
- Some partitions are duplicated (system, vendor, boot, and probably a couple others, but not data) and have a "slot A" & "slot B" copy.
- "Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
- Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" (and booted from) and "inactive" upon next reboot.
- The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
- You can install multiple OTA zip packages one after the other without rebooting in both the stock recovery and TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
- We don't use what are called "delta" updates, which can patch existing partitions by block or by file; we use full filesystem images. So for us, OTA zip packages are really just a bunch of partition filesystem image files all wrapped up into a "payload.bin" with some extra instructions & metadata/checksums, so when you flash a ROM, it overwrites entire partitions at a time instead of individual files or filesystem blocks within that partition. So if you've changed something in a partition like system that gets written as part of flashing an OTA zip, all your changes are gone. The only thing in the system partition afterward will be what was in the system.img that was included in the ROM zip payload.
- The partitions that crDroid, LineageOS, and most custom ROMs for OnePlus 6 & 6T install to when flashing are boot (contains recovery & kernel), dtbo, system, and vbmeta. Some ROMs (like Syberia) build the vendor partition from source instead of just trying to work with the existing OEM vendor partition, so they flash that one too when installing. So you definitely need to flash stock vendor before switching from Syberia or another source-built vendor ROM to one like Lineage or crDroid that uses prebuilt.
- "Prebuilt vendor" vs. "source-built" vendor partitions: when first trying to get a custom ROM working on a new device now that we have separate system & vendor partitions & Google's "Project Treble" is a thing, you'll often just leave the contents of the vendor partition alone, because that's where all the proprietary or device-specific stuff lives (manufacturer specific hardware drivers & interfaces, any DRM libraries, custom frameworks & selinux policies for talking to them), and you make a compatibility map of what framework versions you're compiling against in system and what vendor version they're compatible with or supersede or you overlay updated things that should replace stuff in the vendor partition and keep it in system_ext instead. But you're also limited in that if there are some things in vendor, you CAN'T work around it from the ROM side (like, OnePlus Camera working correctly). So often, once the basics are functioning, the goal is to move to building the contents of the vendor partition from source, because you then have the freedom to fix problems with sepolicy, library/framework mismatches, etc. and make things work with the custom ROM instead of only working with the OEM's flavor of Android, and you can still copy individual pre-compiled files from the stock vendor filesystem image if needed (like if there's no open-source equivalent for some driver). Unfortunately, OnePlus SDM845 (enchilada & fajita, the OP6 & OP6T) never got a proper source-built vendor bringup by the LineageOS team (upon which crDroid is based). And while Syberia has had source built vendor in Android 11 (possibly 10?), it was only done for enchilada and NOT fajita, it's not trivial to unroll & commonize what they've done to apply to other ROMs, and some of the proprietary files they keep are imported from other similar devices/similar chipsets rather than source-built (presumably because the OnePlus ones are modified in a weird way that the open-source components can't hook into, but still not ideal). So for fixing a lot of the issues we still face with lack of things working quite right, or hardware features not available in custom ROMs (especially compared to newer OnePlus devices like the 7, 8, or 9 series), we're kinda stuck, because you can't just implement it against the stock prebuilt vendor.
- "Updating firmware" simply means we're flashing updated contents from the manufacturer into all the OTHER partitions besides the ones that the ROM OTA zip touches. There are another dozen or more of those, besides system & boot, that the full OxygenOS OTA zip would normally write to when you install it. The contents of the system partition in custom ROMs for our device are generally built against a particular version of OxygenOS (mostly the contents of the OEM vendor partition), and we've recently had an entire major Android version update come through from OxygenOS. Some people are still on older firmware that is now dramatically different than what the current custom ROM was intended to deal with (that is, all the stuff from OxygenOS is still based on Android 10, while the ROM is expecting compatibility with Android 11), and while I tend to agree that OxygenOS 10 was better than the current state of OOS 11, that doesn't matter when you're talking about installing the custom ROM over it. So please, keep an eye out in the release notes for what the recommended/required firmware versions are, and remember to update (procedure below).
Notes on custom recoveries with OxygenOS 11 firmware:
Spoiler: Show/Hide
- My understanding (from people smarter than me) is that the android-11 tree of TWRP is kind of a mess at the moment. I had made some 3.6.0_11-0 unofficial builds for both enchilada & fajita, but now they don't even seem to boot and I don't know why. TWRP android-11 tree refuses to mount the system partition where it belongs, and so addon.d OTA survival scripts don't work correctly any longer (which means you're hosed if you use NikGapps and update while booted from a TWRP version ending in "11-0", or if you have Gapps installed as a module and forget to reboot recovery & re-flash Magisk after flashing an update from TWRP).
- Trying to `fastboot boot` an Android 9-based TWRP image (like official 3.5.2_9-0 twrp.img) after installing OxygenOS 11 doesn't work, and will drop you into Qualcomm Crash Dump mode. Don't try to flash it as your boot partion, either.
- Meanwhile, stock LineageOS-based recovery, for all its shortcomings, has working fastbootd (aka "Userspace fastboot", which is what happens when you go to "Advanced", then choose "Enter fastboot" and the background colors go from purple to orange) that lets you flash both slots at once and unlocks critical partitions, while the OnePlus OEM bootloader (where it says "Fastboot Mode" in a square, then goes to the big green "START" text over white & dark red terminal font type text) can't be used to flash every partition to update firmware. Personally, I still think of it as wannabe-class and not a "real" custom recovery until the Lineage team 1) implements userdata decryption so you can manage files in /data and install updates from internal storage, and 2) allows for a factory reset the way we've always all understood it ("wipe data") WITHOUT nuking the contents of internal storage for no good reason ("formatting data"). But since crDroid is LineageOS-based, it's what we've got, and fastbootd is the best way to update firmware.
- With all that being said, since it's likely TWRP will only get MORE broken with Android 12 looming large, we're officially only going to support the built-in LineageOS-based recovery & OTA updater moving forward, until things change dramatically. If you want to try different custom recoveries (new builds of TWRP, OrangeFox, PBRP, whatever), feel free; and let us know how it works! But you're on you're own doing that.
- And on the system update side, applying system OTA updates seems to work correctly using the built-in Updater tool (Settings > System > Updater) both with new OTA releases and when choosing a file from "Local Installation". It executes OTA survival scripts correctly from /system/addon.d/ as well. I've personally tested and it correctly preserved Magisk v23 canary and MindTheGapps & NikGapps (on tester fajita) and MinMicroG "system" install package on my daily driver enchilada.
- ...however it has an accidental dependency on Magisk, due to things beyond my control upstream in the ROM. Whoops. Won't work if you don't have Magisk installed.
- FLASHING the old official TWRP 3.5.2_9-0 INSTALLER zip (or newer) on top of OOS 11.x DOES seem to work for now, but you need to be in a recovery environment that allows you to flash that installer in the first place (either by booting into an already-installed TWRP recovery before updating firmware, or by having an Android 11 compatible recovery boot.img to be able to `fastboot boot`). I don't know if it'll keep working in Android 12 or with crDroid 8.
- Look, if you really want to stick with TWRP, I don't blame you. I made bootable Android 11 compatible TWRP images for enchilada & fajita back at 3.5.2, and they still work well enough to `fastboot boot` them and then flash the old official 3.5.2_9-0 installer zips. Look at the attachments at the end of post #2. Also, you may want to try one of Siddhesh's custom recoveries; they probably work even better.
- TL;DR: I prefer TWRP too but current official releases are kinda broken and it's a chore to get the old version installed correctly, so built-in LineageOS-based recovery and Updater app are the supported way to install & update moving forward.
Prerequisites:
- Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
- Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, with a known-good USB cable (see links in post #2).
- Make sure you've downloaded the most recent full OxygenOS OTA installer zip (11.1.2.2), crDroid zip, matching crDroid boot.img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
- Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
Let's get started!
Updating firmware:
- Reboot to bootloader (with no USB cable connected).
- If you're not already using the stock (LineageOS-based) recovery, you'll need to `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.
- Reboot to bootloader again (actually loads new bootloader that you just flashed).
- Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot stock recovery (white & purple on black color scheme, LineageOS logo in the middle).
- Tap "Advanced", then tap "Enter fastboot" (the already-selected first option), and color scheme should change from purple to orange.
- Follow the instructions for extracting the partition images from the official OxygenOS Updater full OTA zip you already downloaded using the "payload-dumper-go" utility, and flashing them one at a time, from https://wiki.lineageos.org/devices/fajita/fw_update, except for the very last command ("fastboot reboot").
- Since those instructions were updated for Android 12, and this is still Android 11-based & depends on using the OxygenOS prebuilt vendor partition contents, you'll also need to run fastboot flash --slot=all vendor vendor.img at the end of the list of commands in the linked LineageOS Wiki article above.
- If you're only updating firmware and were already on crDroid, you can just "fastboot reboot" which will go back to system. If this is part of coming to crDroid from another ROM, continue with the instructions below.
First time installing crDroid to your OP6T, coming from stock OxygenOS 11.x or another ROM (stock LOS-based recovery):
- Update to OxygenOS 11.1.2.2 firmware as described above if you haven't already.
- At the end of that procedure, (re)flash the crDroid boot.img to the `boot` partition of both slots, then reboot to recovery.
- Once you're rebooted into stock recovery (and lo, it was most purple), ADB sideload the crDroid installation zip. It might prompt you with "Install anyway?" on the phone, so don't just walk away from it.
- After the adb sideload has finished and the purple menu at the top comes back, hit the back arrow, then choose "Wipe data" (which WILL format internal storage -- you backed up as noted above, right?).
- Reboot to recovery (causes it to switch slots so any further installations will be on top of the slot that it just installed crDroid into).
- ADB sideload Magisk and/or any GApps packages you want to use. Please note that any time you install something via ADB sideloading, that the install file is technically renamed "sideload.zip" in transit by the ADB protocol, which might cause problems with installers that try to get too clever for their own good and alter behavior based on renaming the installation zip (like MinMicroG), so you might have to get even MORE clever with changing up installation order (like flash MinMicroG/GApps before Magisk so it won't install as a module. I dunno, talk to the package installer authors to get them to just build multiple packages or talk to the LineageOS devs to allow you to decrypt internal storage, copy stuff to internal storage via MTP, and install stuff from internal storage like a proper custom recovery (or at least maybe `adb push` to an unencrypted temp dir in the data partition).
- Reboot system.
- ???
- Profit!
OTA updating from Updater app with OOS 11.x firmware (recommended):
- This is the preferred way now. You just go to Settings > System > Updater, and... install an update. It processes addon.d OTA survival scripts correctly (tested with Magisk, MinMicroG, MindTheGapps, and NikGapps).
- Please note that there's currently an accidental depencency on Magisk being installed for this to work. I don't know if this will get fixed; that's definitely above my pay grade. This appears to have been fixed; huzzah!
- If you're trying to do a "Local Install" of the downloaded zip, please note you NEED to download on a computer & transfer to internal storage via USB cable; downloading files from an app on the phone associates it with a particular app thanks to Android 11+ Scoped Storage/SAF bull**** and will cause the file to be unreadable to the updater app process.
-- Old TWRP-based instructions below the fold (not recommended, but keeping for historical value... probably not accurate but I'm not going to update them more) --
Spoiler: Show/Hide
OTA updating from TWRP with OOS 11.x firmware:
You don't need to remove device protection; it works fine with PIN. Be sure you have a PIN set, or have looked up whatever that arcane chart of pattern > numeric incantations in case of pattern unlock. It's awful.
- Boot into TWRP recovery.
- Choose install, then select crDroid.zip, select additional zips, choose the TWRP installer zip, then slide to confirm flash.
- Reboot recovery.
- Choose install, then select Magisk zip (if using), select additional zips, choose GApps/microG (if using), slide to confirm flash.
- Please keep off of the grass, shine your shoes, wipe your... dalvik.
- Reboot system.
OTA updating from TWRP with OOS 10.x firmware:
- Don't. Update firmware to 11.1.2.2 first.
Reporting bugs:
I'm a parent of three young kids whose industry disappeared in the pandemic and is now full-time house husband & parent-in-charge while my wife is teaching full-time, I'm trying to save my small live-event-turned-streaming-studio company in my spare time. I'm doing in-home caregiving for a family member overnight one day a week. This is the back-up spare-spare-time hobby. I'm not a software developer nor do I know any programming languages, I just wanted a ROM with signature spoofing support and more customization than the unofficial microg-compatible LineageOS builds. So if there are bugs or feature requests, I go over to the crDroid dev chat and ask if someone has time to hold my hand & help. Don't make me get yelled for annoying them, mmkay? That said...
- Logs/screenshots/recordings or it didn't happen. Either the built-in Matlog app, or Syslog (free, open source, available on Play store and F-droid) are your friends here.
- I try to keep an organized notebook of roadmap, feature reqeusts, bug reports, etc. I won't always be able to fix it, but I'll at least look and do my best to ask the actual devs.
- I don't sign into XDA much, so if I haven't said anything, check out the Telegram group. Lots of helpful folks there.
- Please keep your questions in this thread instead of PMing me with them directly, so that the entire class can benefit from the discussion and you can find out if it's just you or if this is a widespread issue.
It's your device to use the way you want of course, and I use Magisk & microG and like to tweak things myself. But don't expect much support if you:
- didn't do a clean flash.
- aren't using the built-in kernel.
- are using extensive modifications (besides Magisk) like Xposed/Riru, Dolby Atmos, Viper4A, etc.
- immediately start using "finalize.zip" or flashing migrate restore zips instead of following the actual instructions.
- are running decrypted.
- re-locked your bootloader for some reason... you're on a custom ROM; don't do that.
crDroid Website - Download here!
Donate - Support development!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_fajita/tree/11.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/11.0
- hardware/oneplus/ HALs: https://github.com/crdroidandroid/android_hardware_oneplus/tree/11.0-op6
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/11.0
Notes:
- crDroid 7.x (based on Android 11 & LineageOS 18.1) is no longer being actively developed, and I don't know how long someone on the dev team will keep merging monthly security updates. I'll try to keep building releases as long as there are updates, but all my limited time is focused on 9.x/Android 13 bringup now. We're in maintenance mode now, so any outstanding bugs are likely to just remain for perpetuity.
- Yes it supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
- Maintainer does not use GApps, so cannot answer questions about which packages work best from firsthand experience. In general, go with the smallest package you can and then install other Google apps from the Play Store. Please note that if you replace the stock dialer with Google Dialer, you may lose access to the Phone Info menu (*#*#4636#*#*) until you install another dialer. For recommendations, see https://wiki.lineageos.org/gapps.
- Requires OOS 11.1.2.2 firmware (last official release). You should consider using an Android 10 ROM if you want to continue using Android 10 firmware.
- Tested against latest Magisk 24 (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 7.30 - May 2023 ASB release notes/changelog:
Changelog since v7.29 official release:
- Merged May 2023 Android Security Bulletin from upstream.
- Whatever the ROM dev team changed upstream in LineageOS and crDroid sources (not much? they're busy with Android 13).
- No changes to device-specific files.
Known issues:
Fajita-specific:
- If you use App Lock and/or Face Unlock, you'll likely run into issues with the FOD circle view starting to flicker randomly into view when it shouldn't be there (like it's not dismissing properly because one part of the security handling is fighting with or doesn't notify the other part that it's done and doesn't need to try to accept a fingerprint any longer). As a knock-on effect, this will also cause "Disable Night Light when FOD is visible" to freak out. I have one person who doesn't use either report that they were getting the random FOD circle anyway, so... if you're having this problem, please make sure you've given MatLog permission to manage files so that it can actually save logs to internal storage and capture a logcat & send it to me. Logs or it didn't happen, etc etc.
Common:
- No f2fs-formatted userdata support, sadly. Doesn't work with the prebuilt vendor partition required for this version of Android. You'll need to reformat data to ext4 before being able to boot (you can fastboot flash the crDroid 8.x or 9.x boot.img if you need a recovery that will let you choose).
- Google Hotword recognition might be kinda broken right now (on more than one custom ROM/device, not just us), and may cause some screw-up that prevents microphone audio from being allowed to go anywhere else if it's enabled.
- If you are stuck at "Android is starting..." looping endlessly, then press power, reboot to bootloader, and follow the instructions for updating firmware to OxygenOS 11.1.2.2 in the first post. It doesn't wipe data, you shouldn't lose anything.
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
Helpful links:
Download ROM
Android platform tools (adb & fastboot)
OxygenOS 11.1.2.2 Full OTA
Firmware update instructions (LineageOS Wiki)
(Please note that since crDroid 7.x/Android 11 for this device depends on the prebuilt OxygenOS vendor partition, you'll also need to add fastboot flash --slot=all vendor vendor.img to the list of commands in the instructions, just before the final fastboot reboot.
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)
Magisk (use latest)
Official TWRP 3.5.2_9-0 install zip (good luck)
MaWalla99 said:
Download: coming soon!
Click to expand...
Click to collapse
will this work with verizon?
Tomkumato said:
will this work with verizon?
Click to expand...
Click to collapse
I don't know since I'm not in the US.
MaWalla99 said:
I don't know since I'm not in the US.
Click to expand...
Click to collapse
Thanks
hi dev thanks for this rom i have successfully installed now, so there is a small info i like to share, that is installing any version of nikgapps apart from core nikgapps will result in bootloop or after even format the data, rom will boot but set up screen says it crashed, so i have installed with core version of nikgapps, rom booted successfully. that's all i have info to share now.
Hi dev ROM is working fantastically after installed all the application I used before, so thanks for it, it has enough customization thanks for it too.
Does NOT work on Verizon.
Hi devs i don't know the reason why this happening, the problem is when i change default launcher to nova launcher system ui automatically crashes, i can't specifically pinpoint the reason, but after launching the Paytm app for first time then paytm also crashed so i don't know what to do now. I have attached logcat from matlog so I think I have captured required info.
Thanks for the ROM. Where is the best place to get A11 gapps?
wangdak said:
Thanks for the ROM. Where is the best place to get A11 gapps?
Click to expand...
Click to collapse
nik gapps
hi all,
I'm on fajita with crdroid 5.11 - Android 9.
i'd like to bump up to this thread's version. any tips for how to go about that - step by step?
I assume it would be something like -- update TWRP, update firmware, then flash rom as usual with instructions in first post?
many thanks
autologic said:
hi all,
I'm on fajita with crdroid 5.11 - Android 9.
i'd like to bump up to this thread's version. any tips for how to go about that - step by step?
I assume it would be something like -- update TWRP, update firmware, then flash rom as usual with instructions in first post?
many thanks
Click to expand...
Click to collapse
1 - remove any passwords used to unlock screens - 2 - Backup all your important data, - 3 - Make sure you're on latest TWRP for Fajita and that you have latest OOS firmware, Gapps, TWRP installer and the ROM you want to install (zip files) copied to your "Downloads " directory, then reboot into recovery mode, - 4 - make sure you're on slot A (tap "reboot", tap slot "A" and reboot to recovery again), 5 - tap "Wipe", "advanced wipe" and select " Dalvick Art/Cache", " data" and "system", - 6 - swipe to wipe, 7 - tap "install" and select OOS, then swipe to install, 8 - install TWRP zip file, 9 - reboot to recovery, - 10 - install OOS on the second slot, 11- install TWRP, 12 - reboot to recovery, 13 - install the new ROM, 14 - tap "Wipe", advanced Wipe", "Dalvick Art/Cache" and "Data", 15 - swipe to wipe, 16 - install TWRP and reboot to recovery, 17 - install GAPPS, - wipe " Dalvick Art/Cache and reboot to system. That's it!
autologic said:
hi all,
I'm on fajita with crdroid 5.11 - Android 9.
i'd like to bump up to this thread's version. any tips for how to go about that - step by step?
I assume it would be something like -- update TWRP, update firmware, then flash rom as usual with instructions in first post?
many thanks
Click to expand...
Click to collapse
Boot in latest TWRP
Flash latest OOS 10
Flash CR Droid Zip
Flash Finalize.zip
Flash latest TWRP
Format data -type Yes to confirm
Reboot to recovery
Flash Gapps & Magisk (Optional)
Coming from a different version of Android, format data is recommended. Backup your data before you do this
Hi LiveDisplay color profile doesn't work ,setting a profile ,once you exit it resets back to normal again
Excellent ROM.
Thanks!
Hi dev i attached a video, in which i try to explain a problem, i can't pinpoint say amazon app only having this kind of problem, but i can say irresponsible of which app suddenly ui will have some kind of problem, it will appear from nowhere after that phone will hang and i need to restart the phone or else battery drains very fast. Kindly look into it. I reinstalled the rom two time freshly, even though it having same kind of problem presist, but i really loved one good feature that is finger print working fantastic even after reboot. OS is not crashing and reboot by itself, app also not crashing but suddenly some part is acting wired. Anyway i will upload the video for proof. I have attached gif file as per xda rules.
I have one last idea in my head instead of using app called migrate to take back up of application installed in my phone and restore to newly installed rom. Better use play store to install all app one by one and see there is any difference, i really love this rom thats why i reinstalling freshly again and again to see any difference possible
I've never used micro g a whole lot in the past but I'm all for it now due to the unbelievable amount of permissions apps ask for and while I love Android I'm no Google person either. I flashed 7.2 CrDroid two days ago and didn't install gapps. Then I went back in twrp and flashed micro g and fdroid from (stable) nano droid installer thread here on XDA. Going to read up more about micro g ..etc.. Op, if you are testing anything that has to do with this or anything feel free to msg me anytime. Ill run whatever through everything possible and gather logs if need be and send them to you properly. Thanks for this rom!! Great job!! Always loved CrDroid! Think i 1st used CrDroid back in 2013 or so. Fantastic rom!! My Screen time on 7.2 CrDroid.
flash713 said:
I've never used micro g a whole lot in the past but I'm all for it now due to the unbelievable amount of permissions apps ask for and while I love Android I'm no Google person either. I flashed 7.2 CrDroid two days ago and didn't install gapps. Then I went back in twrp and flashed micro g and fdroid from (stable) nano droid installer thread here on XDA. Going to read up more about micro g ..etc.. Op, if you are testing anything that has to do with this or anything feel free to msg me anytime. Ill run whatever through everything possible and gather logs if need be and send them to you properly. Thanks for this rom!! Great job!! Always loved CrDroid! Think i 1st used CrDroid back in 2013 or so. Fantastic rom!! My Screen time on 7.2 CrDroid.
Click to expand...
Click to collapse
Yeah I feel you I'm right where you are I think it's time to ditch Google and get a similar setup. Wonder if there's a thread in the 6t section yet? Google still my friend she'll teach me how to set it up, lol
Update: March 24 2022: This ROM has been retired and a new one based on LOS 19.1 (and TWRP based on Android 11) have taken its place. New thread here: https://forum.xda-developers.com/t/...4-2020-lineageos-19-1-and-twrp-3-6-1.4421365/
---
Update 9:46am EST July 15 2021: new builds of TWRP and LineageOS with TWRP touch fixed and LOS w/ space for Gapps is now live.
WARNING: USE AT YOUR OWN RISK.
I have successfully ported TWRP and Lineage OS 18.1 to the Samsung Galaxy Tab A7 10.4 (2020), aka SM-T500. This is my first time porting TWRP or LOS, so there may be issues unknown about at this time. Thus far, the only known issue is that the touchscreen in TWRP does not work. This can be worked around by using a USB mouse and/or accessing the device via ADB.
Here are the steps to follow:
Update your device to the latest stock ROM (as of this writing) either using the built-in system updater or via Odin. You want the build that ends with "3BUF3".
Unlock device bootloader using instructions from other threads. This will wipe your device.
Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.
Boot device back into download mode and flash TWRP via Odin in the "AP" slot. If you boot up into the stock ROM rather than booting directly back into download mode then go through the initial setup process of the stock ROM and enable developer tools and ensure OEM Unlocking is still enabled (VaultKeeper can possibly undo OEM Unlocking if you get to the ROM but don't go into Developer Tools and view OEM Unlocking is enabled, so make sure to do this).
Boot device into TWRP (recovery mode) and format (not wipe) your data partition. Then reboot back into TWRP.
Push LineageOS (super.new.ext4.img) to device. Ideally push it to an SD card formatted with ExFat or EXT2/3/4 (FAT/FAT16/FAT32/VFAT won't work due to file-size limitations).
Install LineageOS image to "Super" partition. Make sure to select "Install from Image" in order to show .img files in the install selector screen.
(Optional) Push NikGapps Omni to your device and install the zip. Make sure you include a "nikgapps.config" file in your "/tmp" folder that is configured to install to "system" rather than "product" or "default".
Reboot to system. You should now be in LOS with Gapps.
(Optional, but recommended): Install Magisk via TWRP
(Optional, but recommended): Run fix script to fix brightness slider not working and to make Magisk work. If you didn't install Magisk but only want the brightness fix, just enter "n" when prompted in the script. To run the script:
NOTE: Script has .txt file extension to allow hosting on AFH. Remove that so it's just .sh to match the instructions below.
Download and push to device when booted into TWRP
adb push sm-t500_fixes.sh /tmp
Enter an adb shell
adb shell
Change directories and set permissions
cd /tmp
chmod +x /tmp/sm-t500_fixes.sh
Run script
/tmp/sm-t500_fixes.sh
Tips:
If you are not seeing all of your storage space in the OS on the internal flash, boot to TWRP and format data.
Flash TWRP via "AP" slot and flash VBMeta_Disabler via "Userdata" slot in Odin.
Flash LineageOS as an Image, not as a Zip.
For Gapps, use the latest NikGapps for ARM64 and Android 11/R.
For Gapps, make sure you install to the System partition and not Product. To do this you need to slightly modify a nikgapps.config file. Instructions on that can be found on the NikGapps site.
Downloads:
LineageOS 18.1 20210615 Beta 2: https://www.androidfilehost.com/?fid=14943124697586369438
TWRP 3.5.2 Beta 3: https://www.androidfilehost.com/?fid=14943124697586369439
vbmeta_disabled_R: https://www.androidfilehost.com/?fid=14943124697586369440
Fixes for brightness and Magisk (sm-t500_fixes.sh): https://www.androidfilehost.com/?fid=14943124697586369521
Known Issues:
OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
Brightness controls don't work: Fixed via "sm-t500_fixes.sh script.
TWRP touch screen doesn't work (use USB keyboard or adb). Should be fixed with TWRP Beta 3.
TWRP formatting external SD card may hardbrick device. Do not do this! Fixed with TWRP Beta 2.
Source (device tree for TWRP from my Github): https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Source (kernel sources from Samsung): https://opensource.samsung.com/uploadSearch?searchValue=Sm-t500#
agreenbhm said:
I have successfully ported TWRP and Lineage OS 18.1 to the Samsung Galaxy Tab A7 10.4 (2020), aka SM-T500. This is my first time porting TWRP or LOS, so there may be issues unknown about at this time. Thus far, the only known issue is that the touchscreen in TWRP does not work. This can be worked around by using a USB mouse and/or accessing the device via ADB.
Here are the rough steps to follow:
Unlock device bootloader using instructions from other threads.
Patch stock ROM (AP) using Magisk, then flash rooted ROM. Will likely need to wipe device after this.
Boot into rooted ROM and ensure "OEM Unlocking" is still enabled in "Developer Tools".
Boot back into download mode and flash "vbmeta_disabled_R.tar" to disable verified boot.
Boot device back into rooted stock ROM to ensure things are still functional (may require a device wipe at this step).
Boot device into download mode and use ODIN to flash TWRP recovery.tar file via "AP" slot.
Boot device into TWRP to verify functionality (hold Vol-Up + Power during boot).
Access TWRP via adb using "adb shell" or with USB mouse (touch functionality currently not working).
Format data partition on device.
Via ADB shell: twrp format data
Via USB mouse: Wipe -> Advanced -> Format Data
Boot device into download mode.
Via ADB shell: twrp reboot download
Via USB mouse: Reboot -> Download
Flash LineageOS tar file via ODIN using the "AP" slot.
If device boots into TWRP after flashing LineageOS, use USB mouse to select: Reboot -> System
Device should boot and stall for ~1m at the Samsung logo screen with red text below, then should go blank and then display LineageOS boot image.
Downloads:
LineageOS 18.1 20210615 with TWRP 3.5.2: https://mega.nz/file/vMVglThZ#TepIHvdEypezq3z4S_4Lln7FRFVfC7CUjVGq3ByFb6U
TWRP 3.5.2: https://mega.nz/file/GYU1yCCQ#JsthI8BYNtfB08Pzt1eeXta2Lb1zCkUI185Zm88dEW4
vbmeta_disabled_R: https://mega.nz/file/iMFx3CQI#8cP4mPoRaQNwDATqt0vKD8wxqRWSTz1EL79U0fNpW8M
Click to expand...
Click to collapse
Great news!! But I think you need to post it in the ROMs, Kernels, Recover thread.
awesome. Will try after work. Also I think you posted in the wrong section.
Which slot to flash the vbmeta?
wizzdome said:
Which slot to flash the vbmeta?
Click to expand...
Click to collapse
AP
Thanks,
After flashing the vbmeta it booted into recovery automatically after what looked like a bootloop in progress, so I wiped with factory reset and then it rebooted fine. (still not sure exactly what the vbmeta does I was hoping it would make it so i didnt get that stupid pop up asking me to hit power button to continue booting due to it having the patched os) anyhow booted fine and twrp installed as you stated without touch screen but mouse with otg works fine. (great job so far) On to LOS... I think I should have checked oem lock before flashing LOS as when I installed I get stuck at boot screen that says oem lock is on... must have been from my factory reset... (facepalm)
Nope... Still sticking on boot with the following showing on the screen...
RPMB fuse not set
RPMB Provisioned
Current BInary: Custom (0x30f)
FRP Lock : OFF
OEM Lock : ON (U) {this was off verified before flash}
KG Status : Checking
Waranty Void : 0x1 (0xE02)
Quallcomm Secureboot : Enable
RP SWREV : B3 (1,1,1,3,1,1) k3 s3
secure download : enable
grdm status : normal (d0000501)
did : 041ce2d22dba
this is displayed in the corner on the bootscreen and looks like it belongs on the download screen, anyhow booting into twrp from this point works however factory reset fails with unable to mount key(something and key(something else) i figure i will let it sit a while as I know sometimes it just takes first boot a while to go through however it doesnt seem to be the problem. Have you had a positive install of the LOS? I am wondering if I had maybe gotten a bad copy of the file. When i go to install I get a pass in odin so not quite sure where to go from here other than back to the factory image any help to get this going would be great... I took on this task cause i needed someting to take my mind off the severely crappy week I have had... so looking forward to anything you can share here...
Actually, userdata is the slot I always use. It might work in both though.
Something to mention: there is not enough space on the /system partition to flash Gapps. I created a build that supports it (with a resized /system partition) but I couldn't get it to flash via Odin. The only way I got it to work was by flashing it via TWRP as an img file. I will be posting that soon. Unfortunately that will be the end of development for now as I hard-bricked the device and need to wait for a repair or replacement. Should be back developing in 2 weeks.
Nevermind what I said here.
jayzarry84 said:
Anyone get this to work? I just flashed the TWRP part but have not been able to get into TWRP
Click to expand...
Click to collapse
Get adb access in the OS and then run "adb reboot recovery"
agreenbhm said:
Get adb access in the OS and then run "adb reboot recovery"
Click to expand...
Click to collapse
question. I don't have an OTG cable and TWRP keeps booting. I've tried rebbot, rebbot bootloader, reboot system. any advice?
jayzarry84 said:
question. I don't have an OTG cable and TWRP keeps booting. I've tried rebbot, rebbot bootloader, reboot system. any advice?
Click to expand...
Click to collapse
You may need to get an otg cable for a USB mouse and choose "reboot system" from the gui. Alternatively, look at the /dev/block/by-name/misc partition and try blanking that out with dd. That has worked sometimes.
jayzarry84 said:
question. I don't have an OTG cable and TWRP keeps booting. I've tried rebbot, rebbot bootloader, reboot system. any advice?
Click to expand...
Click to collapse
Also, from an adb shell, try "twrp reboot". Supposedly that should boot to system, but I feel like in testing I got mixed results. According to the TWRP documentation though that should be the answer.
agreenbhm said:
Also, from an adb shell, try "twrp reboot". Supposedly that should boot to system, but I feel like in testing I got mixed results. According to the TWRP documentation though that should be the answer.
Click to expand...
Click to collapse
Not working. I'll wait for my otg cable to come in
jayzarry84 said:
Not working. I'll wait for my otg cable to come in
Click to expand...
Click to collapse
I was able to use adb to run the TWRP Format Data command and it rebooted the tablet and now LOS has booted up. I think I'm good!
Looking forward to see how this develops
Rom is fast and snappy. Brightness control does not work. I haven’t played too much because of work but that’s what I’ve found so far
Can a mod move this to the rom release section?
agreenbhm said:
Something to mention: there is not enough space on the /system partition to flash Gapps. I created a build that supports it (with a resized /system partition) but I couldn't get it to flash via Odin. The only way I got it to work was by flashing it via TWRP as an img file. I will be posting that soon. Unfortunately that will be the end of development for now as I hard-bricked the device and need to wait for a repair or replacement. Should be back developing in 2 weeks.
Click to expand...
Click to collapse
I've not been able to flash this yet but I know that the latest TWRP versions have a way to fix the system partition to accept gapps. /Wipe/Advanced check system then resize. Sometimes you have to do it more than once if it is a large gapps.
lewmur said:
I've not been able to flash this yet but I know that the latest TWRP versions have a way to fix the system partition to accept gapps. /Wipe/Advanced check system then resize. Sometimes you have to do it more than once if it is a large gapps.
Click to expand...
Click to collapse
I will look into that, but I'm not optimistic it will work. This device does not separately present the system partition, rather it uses a super partition which contains system, vendor, product, and odm. TWRP only shows me the super partition for working with. I was able to resize the system partition by expanding the Lineage image and file system on my pc to match the original stock system partition, then rebuilt the super image with the other partitions it needs.