DownloadsWiki

Prerequisites:

Qualcomm drivers
MSM tool downloaded for your device model. Make sure to download for correct region.

  1. Run MsmDownloadTool Vx.x.exe as administrator
  2. On login window select Others in User type and click next
  3. Do not change any of the default settings
  4. Click Start button on top left
  5. Put your phone to EDL mode
  6. Process will start

If MSM does not connect to your phone then it's probably a driver issue.

Method 1: Physical buttons

  • Turn off your phone
  • Push volume up and volume down together
  • Connect the USB cable to your phone
  • Phone should boot to edl mode and screen stays black.

Method 2: using adb

  • Phone needs to be in recovery or in OS
  • From cmd issue command
    adb reboot edl
Prerequisites:

Google USB drivers installed
Latest platform-tools on your PC

NOTE: ALL DATA WILL BE WIPED!
  1. Go to settings -> About phone -> Tap Build number 7 times to activate developer options
  2. Insert your screen lock pin / pattern if necessary
  3. Go to Settings -> System -> Developer options
  4. Enable USB Debugging and OEM Unlocking
  5. Connect your phone to PC with USB cable.
  6. Check 'Always allow from this computer' and tap Allow
  7. Open cmd in the folder where platform-tools are located.
  8. Check that your PC finds your phone by typing adb devices. It should say:

    List of devices attached
    1b234567   device

  9. Reboot your phone to bootloader
    adb reboot bootloader
  10. Check that your PC finds your phone by typing fastboot devices. It should say:

    List of devices attached
    1b234567   fastboot

  11. Use command
    fastboot oem unlock
  12. Use volume keys to select 'unlock the bootloader' and confirm with power button
  • Reboot to fastboot
  • Flash recovery
  • Reboot to recovery
  • Sideload ROM
  • Format data

Prerequisites:

  • Working brains, common sense, lots of coffee
  • OOS12 C.62-C.64 in BOTH SLOTS! DO NOT SKIP THIS!
  • Latest platform-tools
  • Google USB driver
  • Developer options enabled: Settings -> About phone -> Tap Build number at the bottom seven (7) times
  • ADB enabled: Settings -> System -> Developer options -> USB debugging
  • Required images: dtbo.img, vendor_boot.img, lineage-19.1-xxx-recovery-xxx.img (put these in the same folder with platform-tools)
    Get images from downloads page
  • ROM zip (put it in the same folder with platform-tools)
  • Unlocked bootloader
    NOTE: For unknown reason some devices cannot be unlocked in OOS12 so better to do it in OOS11
  1. Reboot your phone to fastboot mode
  2. Open cmd and go to the folder where platform tools are (DO NOT USE POWERSHELL!)
  3. Enter following commands by copypasting one by one:
    fastboot flash dtbo dtbo.img

     

    fastboot flash vendor_boot vendor_boot.img
  4. Temporarily flash recovery:
    fastboot flash boot lineage-19.1-xxx-recovery-xxx.img replace the filename with the actual filename
  5. Reboot your phone to recovery mode, click "Install update" -> "ADB Sideload"
  6. In cmd enter command: adb sideload Nameless-AOSP_xxx.zip (replace the filename with the filename of rom zip you downloaded)
  7. Wait until your device shows Step 2/2 and back arrow appears. Click back arrow, then click "Factory reset" -> "Format data/factory reset" -> "Format data"
    NOTE: Progress on your pc will stop at around 47%. It is normal behaviour.
  8. Click back arrow in recovery, then click "Reboot to system"

Prerequisites:

  • Working brains, common sense, lots of coffee
  • OOS12 C.33-C.35 in BOTH SLOTS! DO NOT SKIP THIS!
  • Latest platform-tools
  • Google USB driver
  • Developer options enabled: Settings -> About phone -> Tap Build number at the bottom seven (7) times
  • ADB enabled: Settings -> System -> Developer options -> USB debugging
  • Required images: boot.img, vbmeta.img, vbmeta_system.img and recovery.img (put these in the same folder with platform-tools)
    Get images from sourceforge
  • ROM zip (put it in the same folder with platform-tools)
  • Unlocked bootloader
    NOTE: For unknown reason some devices cannot be unlocked in OOS12 so better to do it in OOS11
  1. Reboot your phone to fastboot mode
  2. Open cmd and go to the folder where platform tools are (DO NOT USE POWERSHELL!)
  3. Enter following commands by copypasting one by one:
    fastboot flash boot boot.img

     

    fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

     

    fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img

     

    fastboot flash recovery recovery.img

     

  4. Reboot your phone to recovery mode, click "Install update" -> "ADB Sideload"
  5. In cmd enter command: adb sideload Nameless-AOSP_xxx.zip (replace the filename with the filename of rom zip you downloaded)
  6. Wait until your device shows Step 2/2 and back arrow appears. Click back arrow, then click "Factory reset" -> "Format data/factory reset" -> "Format data"
    NOTE: Progress on your pc will stop at around 47%. It is normal behaviour.
  7. Click back arrow in recovery, then click "Reboot to system"

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.

NOTE: 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

  • 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
  • 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

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.

    1. Boot to fastboot mode (also known as bootloader)
    2. 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

    3. Reboot
    4. Save your precious data
    5. Clean flash using correct procedure