[GUIDE] OOS v4.0.3 ---> FLASH & ROOT STOCK -OR- CUSTOM ROM WITH EASE & CORRECTLY

Did this guide solve your issues?

  • Yes!

    Votes: 44 81.5%

  • No!

    Votes: 2 3.7%

  • More information needed in it

    Votes: 6 11.1%

  • Nope. I used a different guide

    Votes: 1 1.9%

  • Both options 3 and 4

    Votes: 1 1.9%
  • Total voters
    54
D

dbabaev21

Senior Member
Jan 3, 2017
186
123
0
Jan 14, 2017 at 4:59 AM
[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?


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]
  1. Boot to bootloader by holding Volume Up and Power buttons.
  2. Connect the phone to the computer via USB cable.
  3. 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”.
  4. In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
  5. When you could see that your device is recognized, write “fastboot flash recovery recovery_op3.img” to flash Stock Recovery of OxygenOS.
  6. Disconnect the device, press volume up once, then press the power button once to turn off the phone.
  7. Boot into recovery by holding Volume Down (-) and Power button down for a few of seconds.
  8. 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.
  9. 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]
  10. 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”.
  11. In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
  12. 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)
  13. Reboot and you have OxygenOS v4.0.3!
  14. 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
  15. 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):
  1. 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.
  2. Now go to: Settings > Backup & reset > Factory data reset. In “Optional” select “Erase internal storage” and press “RESET PHONE”. Confirm by pressing “ERASE EVERYTHING”.
  3. It will reboot to Stock Recovery and wipe your data. When it’s done, it will reboot to the OS.
  4. 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
  5. 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)
  6. 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]
  7. Reboot to Stock recovery v2.0
  8. 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”.
  9. In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
  10. 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)
  11. 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!
  12. 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):
  1. Boot to bootloader by holding Volume Up and Power buttons.
  2. Connect the phone to the computer via USB cable.
  3. 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”.
  4. In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
  5. 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.
  6. Disconnect the device, press volume up once, then press the power button once to turn off the phone.
  7. 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]
  8. Press “Wipe” > “Advanced Wipe”, and select “Dalvik / ART Cache”, “System”, “Data” and “Cache”. Then swipe “Swipe to Wipe” for a clean flash.
  9. 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]
  1. Boot to bootloader by holding Volume Up and Power buttons.
  2. Connect the phone to the computer via USB cable.
  3. 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”.
  4. In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
  5. When you could see that your device is recognized, write “fastboot flash recovery recovery_op3.img” to flash Stock Recovery of OxygenOS.
  6. Disconnect the device, press volume up once, then press the power button once to turn off the phone.
  7. Boot into recovery by holding Volume Down (-) and Power button down for a few of seconds.
  8. 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”.
  9. In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
  10. 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)
  11. Reboot and you have OxygenOS v4.0.3!
  12. 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
  13. Boot to bootloader by holding Volume Up and Power buttons.
  14. Connect the phone to the computer via USB cable.
  15. 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”.
  16. In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
  17. 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.
  18. Disconnect the device, press volume up once, then press the power button once to turn off the phone.
  19. 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.
  20. Connect you OnePlus 3 to your computer and copy the SuperSU v2.79 (Stable) to your device.
  21. 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
 
Last edited:
  • Like
Reactions: Organhaendler, ptblad, Stefa. and 43 others
D

dbabaev21

Senior Member
Jan 3, 2017
186
123
0
Jan 14, 2017 at 4:59 AM
FAQ (Q&A):​
  1. 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.

    [*]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):
    [*]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.​
 

Attachments

Last edited:
  • Like
Reactions: Organhaendler, hyperorb, Kelsios and 12 others
D

dbabaev21

Senior Member
Jan 3, 2017
186
123
0
Jan 14, 2017 at 4:59 AM
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:
 
Last edited:
  • Like
Reactions: Donglip, necromorph_lover, bedalus and 3 others
J

jackiass

Senior Member
May 22, 2011
917
611
113
Jan 14, 2017 at 6:36 AM
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?
 
  • Like
Reactions: dbabaev21
P

playerboys10

Member
Jan 6, 2014
28
1
0
Jan 14, 2017 at 9:43 AM
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?
 
Y

yohan_xda

New member
Sep 23, 2016
1
1
0
Jan 14, 2017 at 1:17 PM
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.
 
  • Like
Reactions: dbabaev21
VincentJoshuaET

VincentJoshuaET

Senior Member
Jun 5, 2016
1,293
474
93
21
Angat
Jan 14, 2017 at 6:02 PM
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
 
Last edited:
  • Like
Reactions: dbabaev21
D

dinesh7208

Member
Jan 15, 2017
16
0
0
Jakarta
Jan 15, 2017 at 3:59 AM
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
 
D

dbabaev21

Senior Member
Jan 3, 2017
186
123
0
Jan 15, 2017 at 7:22 AM
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...
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...
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...
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...
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...
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...
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...
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...
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...
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...
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...
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.
 
  • Like
Reactions: Explorer23
M

mit2nil

Senior Member
Dec 25, 2014
51
4
0
Los Angeles
Jan 15, 2017 at 7:32 AM
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.
 
D

dbabaev21

Senior Member
Jan 3, 2017
186
123
0
Jan 15, 2017 at 8:06 AM
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...
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.
 
M

mit2nil

Senior Member
Dec 25, 2014
51
4
0
Los Angeles
Jan 15, 2017 at 8:12 AM
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...
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.
 
D

dbabaev21

Senior Member
Jan 3, 2017
186
123
0
Jan 15, 2017 at 8:14 AM
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...
Then start from the beginning.
I was scared to death that I bricked my phone, but managed to get out quickly.
 
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone