[OnePlus 3 Guides, News, & Discussion] dbabaev21:
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://xdaforums.com/showpost.php?p=70698410&postcount=112

Otherwise, check this thread: https://xdaforums.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685 This guide uses the .28 twrp

(NOT RECOMMENDED, BUT USE TWRP FROM [MENTION=3873953]eng.stk[/MENTION]) to use Stock Recovery, which I think is a bit more complex.

OR: https://xdaforums.com/showpost.php?p=70415499&postcount=33

My guide uses only bootloader, Stock Recovery and TWRP from [MENTION=3873953]eng.stk[/MENTION]. 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://xdaforums.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://xdaforums.com/oneplus-one/general/guide-formatting-ext4-to-f2fs-losing-t3352116

Furthermore, [MENTION=5376694]cpt.macp[/MENTION] 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 [MENTION=3873953]eng.stk[/MENTION] -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 [MENTION=3873953]eng.stk[/MENTION]. Unofficial TWRP is to be used

with LineageOS 14.1 & Experience v10 ROMs. Also, here is the reason why: https://xdaforums.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://xdaforums.com/oneplus-3/development/recovery-official-twrp-oneplus-3-t3539129 ;

https://xdaforums.com/showpost.php?p=70574596&postcount=34 ; https://xdaforums.com/showpost.php?p=70622726&postcount=97 ;

https://xdaforums.com/showpost.php?p=70622760&postcount=98 ; https://xdaforums.com/showpost.php?p=70622849&postcount=102 ;

https://xdaforums.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://xdaforums.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://xdaforums.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://xdaforums.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://xdaforums.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.​