Frequently Asked Questions
If you have a question, please read or search this page before asking. It saves time for everyone — especially you.
You can also search for the answer to your question.
Links
Links
How to use MSM tool
How to use MSM tool
Prerequisites:
- Qualcomm drivers
- MSM tool downloaded for your device model. Make sure to download for correct region.
- Run MsmDownloadTool Vx.x.exe as administrator
- On login window select Others in User type and click next
- Do not change any of the default settings
- Click Start button on top left
- Put your phone to EDL mode
- Process will start
If MSM does not connect to your phone then it's probably a driver issue.
How to enter edl mode
How to enter edl mode
Unlocking bootloader
Unlocking bootloader
Prerequisites:
- Google USB drivers installed
- Latest platform-tools on your PC
ALL DATA WILL BE WIPED!
Go to settings -> About phone -> Tap Build number 7 times to activate developer options
Insert your screen lock pin / pattern if necessary
Go to Settings -> System -> Developer options
Enable USB Debugging and OEM Unlocking
Connect your phone to PC with USB cable.
Check 'Always allow from this computer' and tap Allow
Open cmd in the folder where platform-tools are located.
Check that your PC finds your phone by typing adb devices. It should say:
List of devices attached 1b234567 device
Reboot your phone to bootloader
adb reboot bootloader
Check that your PC finds your phone by typing fastboot devices. It should say:
List of devices attached 1b234567 fastboot
Use command
fastboot oem unlock
Use volume keys to select 'unlock the bootloader' and confirm with power button
A13 flashing instructions when coming from OOS12 based custom ROM
A13 flashing instructions when coming from OOS12 based custom ROM
- Reboot to fastboot
- Flash recovery
- Reboot to recovery
- Sideload ROM
- Format data
Both slots? what? how?
Both slots? what? how?
About slots
Your phone has two slots. Both of them has full OS and firmware. Custom ROMs are based on certain version of official OnePlus firmware so both slots needs to have the same firmware. If they differ, then you are most likely to have problems after updating your custom ROM through OTA.
Flashing both slots
You do this by downloading the correct OOS full zip from the "#oos-repo" note in telegram group. Then use the local update feature in system update to flash the zip. After you reboot, use the local update feature to flash the same full zip again. By flashing it twice, you will guarantee that you have the latest firmware on both slots. It is very important that you DO NOT skip this step in the flashing instructions.
In OOS12 the local update options is disabled by default. You can enable it from developer settings or by using local update apk found in links section
fastboot: unknown option -- disable-verity
fastboot: unknown option -- disable-verity
- Use cmd, NOT powershell
- Make sure platform-tools is the latest version
- Make sure that the files you are going to flash are in the same folder with platform-tools
- Make sure you opened cmd in the folder where platform-tools are
adb error cannot read 'filename.zip'
adb error cannot read 'filename.zip'
- Make sure platform-tools is the latest version. If not, download from links. (Do not use Minimal ADB and Fastboot.)
- Make sure the files you are sideloading are in the same folder where platform-tools are
- Use cmd instead of powershell
How to root?
How to root?
- Make sure the magisk file is in the same folder with platform-tools
- You don't need to change the file extension from apk to zip
- Download Magisk 25.2
- Reboot to recovery
- Select Install update -> ADB Sideload
- Use command:
adb sideload Magisk-v25.2.apk
- Reboot
Maintain root after OTA update
- After OTA update, before reboot, go to Magisk, select Install, select Install to inactive Slot (After OTA)
Button combinations
Button combinations
I did not read instructions and updated from ota, what now?
I did not read instructions and updated from ota, what now?
The latest update for all currently supported devices is based on OOS12 firmware whereas previous builds were based on OOS11 firmware so updating through OTA will cause bootloop. The broken slot is beyond saving. If there is important data you need to save, follow these instructions.
Boot to fastboot mode (also known as bootloader)
From PC, check current active slot with command
fastboot getvar all
Look for (bootloader) current-slot If it says current-slot:a then use command
fastboot --set-active=b
and vice versa
Reboot
Save your precious data
Clean flash using correct procedure