Skip to main content

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

Backing up persist​

warning

In order to make sure this process works correctly it's important to confirm whether the persist partition is currently valid. If your sensors (Proximity, Light etc.) then continue following the instructions otherwise MSM back to your device first (Instructions)

Backing up persist
note

Before continuing make sure the following requirements are met:

  1. Launch MsmDownloadTool V4.0.exe and select Others as the User type.
  2. Click Next and then press F8 to open the Firehose ReadBack.
  3. Select persist partition, enter oneplus as the password and press OK.
  4. Click the Read Back button from the main MSM window.
  5. Reboot to EDL.
  6. Once the readback is complete, find your now backed up persist.img at the root of your system drive. (C: for example).

Enabling Developer Options​

Enabling Developer Options
  1. You can unlock developer options by tapping the build number 7 times rapidly in About Phone/About Device. Open the Developer options and enable USB debugging. Connect your phone to PC and type adb devices.
  2. A pop-up will come up on your phone. Check always allow and then okay. Type adb devices again and you should now see your device in the output.

How to enter EDL Mode​

How to enter EDL Mode

There are upto three ways to boot into EDL depending on your device:

  • If you can boot into system and have debugging on run adb reboot edl.
  • Another way of getting into EDL mode is used if your phone no longer boots into Android. You have to completely power down the phone. Press both the volume buttons simultaneously and hold for 5 seconds (NO POWER BUTTON) and connect to PC. For devices older than the 7 series, only the volume up button for 5 seconds is required.
  • The last method of getting into EDL mode is using TWRP. It's the bottom option in the reboot menu. Note: This method doesn't require for TWRP to be installed. You can simply fastboot boot into TWRP to achieve the desire results.
info

Once properly in EDL, your screen will turn completely black (there's no text saying it's in EDL mode as if the phone is off) and automatically reboot in 10 seconds if not connected properly to MSM tool. Don't panic if you don't see anything on the screen and the phone reboots. This is normal.

How to use MSM tool​

note

Before using MSM make sure the following requirements are met:

  • Make sure you have the proper MSM downloaded which includes the proper device, region, and OS version from the OP community server.
  • Have the Qualcomm drivers installed.
  • ONLY use an original OnePlus red cable to connect to PC. This is the recommended cable for data transfer. Try to use a USB 2.0 port if your PC has one.
  • ALWAYS run the MSM.exe in administrator mode. Do this by either right clicking the .exe and choosing "Run as administrator" or permanently set this by right clicking the .exe and selecting Properties and then hit the Compatibility tab. Check the box that says "Run this program as administrator", hit the Apply button, and then the OK button.
How to use MSM tool

MSM uses Qualcomm's Emergency Download (EDL) mode to flash your phone to stock and relock your bootloader if unlocked. There are three methods to get into EDL mode:

  1. If you've not already, enable developer options and USB debugging on your device.
  2. If the device isn't authorized a pop-up will come up on your phone. Check always allow and then okay. Type adb devices again and you should now see numbers and letters. Now boot into EDL (Instructions).
info

Once properly in EDL, your screen will turn completely black (there's no text saying it's in EDL mode as if the phone is off) and automatically reboot in 10 seconds if not connected properly to MSM tool. Don't panic if you don't see anything on the screen and the phone reboots. This is normal.

  1. Run the MSM.exe as an administrator. When a menu comes up, choose "Others" in User type and hit next. Keep Sha256 and Auto Reboot checked. Do note the Start button at the top left.
  2. If your MSM screen comes up complete blank, keep the app open and put your phone in EDL mode. After the phone reboots and keeping it connected to the PC, put the phone back in EDL mode and hit the "Enum" button in the MSM tool. Your MSM screen should now have at least one COM port showing with connections status as N/A. If you have more than one COM port showing, that is okay.
  3. Once you have a COM port showing, put the phone in EDL mode (if it's not already), and the connection status should change to connected.
note

Special note for OnePlus 8T owners: The first few batches of 8T's were shipped with DDR4 memory and since then they have shipped with DDR5 memory. Your MSM tool has a tab to specifically select which RAM you have. Default is to flash to either, but this is slower. You can find out which RAM you have by opening a terminal app on the phone and entering getprop ro.boot.ddr_type or adb shell getprop ro.boot.ddr_type from PC. The results of this command is either 0 or 1. DDR4 is 0 and DDR5 is 1.

  1. Once connected, you only have 10 seconds to press the Start button at the top left before the phone will automatically reboot out of EDL mode, so be prepared.
note

There are reports from OP9 users that the any OP9 MSM tool from any region fails to flash their device with Sahara Communication Failed or preload param errors. The fix is to flash the device with the Indian 9Pro MSM and then you'll be able to flash the OP9 MSM.

  1. Once you press the Start button, the phone's A slot will be flashed to the firmware version you selected. It will take about 5 minutes to install. DO NOT touch the phone or close MSM during the process. You could potentially hard brick your phone. Once completed, your phone will be completely wiped, the bootloader will lock, and the phone will automatically boot into Android. You will set up the phone normally as if you had just taken it out of the box. As most MSM tools are from an older firmware version you're going to want to OTA or local upgrade to what is current.

How to unlock bootloader​

warning

Unlocking the bootloader will trigger a full system wipe so make sure to backup your important data first. Also, on some devices running OOS14+ sometimes the partitions break and hence it's not possible to boot into fastboot in order to follow the instructions. In this case you'll have to downgrade to OOS13 to continue.

note

Before trying to unlock your bootloader make sure the following requirements are met:

Unlocking bootloader
  1. Enable OEM Unlocking from developer options. (How to enable developer options?)
  2. Connect your phone to PC with USB cable.
  3. Open cmd in the folder where platform-tools are located.
  4. Check that your PC finds your phone by typing adb devices. It should say:
List of devices attached
1b234567   device
  1. Reboot your device into bootloader by using adb reboot bootloader.
  2. Check that your PC finds your phone by typing fastboot devices. It should say:
List of devices attached
1b234567   fastboot
  1. Use command fastboot flashing unlock and use volume keys to select unlock the bootloader and confirm with power button.
note

On some devices the above command might not work, in which case run fastboot oem unlock.

A/B Partitions Explained​

A/B Partitions Explained

Introduced with Android Nougat, A/B system updates use two sets of partitions referred to as slots (normally slot A and slot B). The system runs from the current slot while the partitions in the unused slot are not accessed by the running system during normal operation.

They allow for a bootable system and minimal downtime during an OTA update. When a device is performing a seamless update, all the transferring is done while one system partition is running. This approach makes updates fault resistant by keeping the unused slot as a fallback. If an error occurs during or after an update, the system can roll back to the old slot and continue to work.

Flashing both slots​

warning

Every nameless version works on a particular firmware version so it's important to make sure to flash the correct firmware on both slots to ensure safe OTA updates in the future.

You can ensure you're on the correct firmware on both slots by using one of the two mentioned methods:

  1. Download the full factory image of OOS from the list provided below based on the device you own then use the local update feature in system update to flash the zip. After you reboot, repeat the method to install OOS to the second (inactive) slot. It is very important that you DO NOT skip this step in the flashing instructions.
info

In OOS12 the local update options is disabled by default. You can enable it from developer settings or by using local update apk.

  1. If you're on a custom recovery (not stock) you can flash Wishmasterflo's Firmware Flasher which would automatically flash the firmware to both slots while also ensuring RAM compatibility in the cases where it's required.
note

Download the OOS factory images: OnePlus 8, OnePlus 8T, OnePlus 8 Pro, OnePlus 9, OnePlus 9 Pro, OnePlus 9R, OnePlus Nord

How to root?​

How to root?
note
  • 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 the latest version of Magisk or Kitsune Mask and rename the file to magisk.apk.
  • Reboot to recovery.
  • Select Install Update -> ADB Sideload
  • Sideload the APK using adb sideload magisk.apk.
  • Reboot.
note

In some cases the Magisk/Kitsune Mask app might not show up on the app drawer. If this happens just install the apk from above as a normal app and it should hook into the running prcocess and detect the installation. Sometimes the app might also ask for a reboot so go forward and do it.

How to maintain root?​

After installation of a new update you would normally lose root. In order to prevent that before rebooting to complete the update installation follow the following steps.

  • Open Magisk/Kitsune Mask app.
  • Click on install -> Install to Inactive Slot (After OTA).
  • Root would automatically be installed on the other slot and you'll be prompted to reboot.

Button Combinations​

Button Combinations

Recovery Mode​

  • Volume Down + Power

Fastboot Mode​

  • Volume Down + Volume Up + Power

EDL Mode​

  • Power off the phone, press Volume Down + Volume Up while connecting the USB cable.

Safe Mode​

  • Turn off your phone, turn it back on and keep Volume Down pressed while phone is booting.
note

The button combinations might differ from device to device so if these don't work for you make sure to google. Also in order to use the button combinations from safe mode you'll need to boot into it from the power menu atleast once.

Installing Google USB Drivers​

Installing Google USB Drivers
To install the Android USB driver on Windows, do the following:
  1. Connect your Android device to your computer's USB port.
  2. From Windows Explorer, open Computer Management.
  3. In the Computer Management left pane, select Device Manager.
  4. In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see.
  5. Right-click the name of the device you connected, and then select Update Driver.
  6. Click on Browse my computer for drivers.
  7. Click on Let me pick from a list of available drivers from my computer then Show All Devices and finally click on Next.
  8. Click on Have Disk, select the location where you've extracted the driver zip and click OK.
  9. Depending on your situation either install the Android ADB Interface (For System drivers), Android Bootloader Interface (For Fastboot/Bootloader Drivers).
  10. Click on Next on both the window and the pop-up and let the drivers install.

Common Problems​

Zygisk doesn't work even after enabling it from settings and rebooting.

Lsposed is currently broken on the latest release of nameless because it's based on A14 QPR2 and the vanilla version of lsposed is eol. Use this version instead https://github.com/mywalkb/LSPosed_mod/releases

Banking apps (and other apps) are just crashing on launch.

Most probably the issue is the apps detecting the unlocked bootloader and refusing to work. If you're not rooted then wait for the dev to update the device fingerprint and reboot (Google recently started banning custom ROM fingerprints). If you're rooted follow the instructions below:

If you're using Vanilla magisk:​

  1. Enable the options for Zygisk and Enforce Denylist from Magisk settings.
  2. After that add Google Play Services (GMS) and Google Play Store to the denylist.
  3. Optional: Install the Shamiko and PIF Next modules and reboot.

If you're using Kitsune Mask:​

  1. Enable the options for Zygisk and MagiskHide from Kitsune Mask settings.
  2. After that add Google Play Services (GMS) and Google Play Store to the MagiskHide list.
  3. Optional: Install the PIF Next module and reboot.
My Device isn't getting detected in EDL/Fastboot/Bootloader

This usually means there's a driver issue and your computer doesn't know how to handle this type of device. Install the Google USB Drivers properly from the Links section.

fastboot: unknown option -- disable-verity during a flash
  • Use cmd, NOT powershell.
  • Make sure Platform Tools is the latest version (Do not use Minimal ADB and Fastboot.).
  • Make sure that the files you are going to flash are in the same folder with platform-tools.
  • If you already have platform tools installed (i.e. You can run adb commands even when outside the platform-tools folder), you need to make sure you're using the local version of platform tools and not the global installed version. You can do this by prefixing all adb and fastboot commands with .\. For example: .\adb devices instead of adb devices.
adb error cannot read 'filename.zip' during an ADB sideload
  • Use cmd, NOT powershell.
  • Make sure Platform Tools is the latest version (Do not use Minimal ADB and Fastboot.).
  • Make sure that the files you are going to flash are in the same folder with platform-tools.
  • If there are any spaces in your path to the file you're trying to flash then encapsulate them with double-inverted commas (For ex. adb sideload "C:/Nameless CLO/nameless.zip") and drag and drop the file between the inverted commas instead of manually typing in the path to avoid mistakes.
Proximity and other sensors not working
warning

For this process you'll need to have previously backed up your persist partition. Please note that the persist partition contains calibration data for your device so flashing someone else's backup might make things worse.

note

Before trying to unlock your bootloader make sure the following requirements are met:

  • Open CMD and cd into the directory with the files. (DO NOT USE POWERSHELL!)
  • Reboot your device into fastboot with adb reboot fastboot if you're in system or fastboot reboot fastboot if you're in the bootloader or recovery.
  • Reboot into fastbootd with fastboot reboot fastboot while the device is in fastboot.
note

You can also boot into fastboot using the button combination

  • Flash the persist partition using fastboot flash persist persist.img.
  • Reboot to system.