User Ratings

★★★★★
★★★★
★★★
★★
★
1
0
0
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5

Rate This Project
Login To Rate This Project

User Reviews

  • 5 out of 5 stars
    Hi, I’d like to share my ColorOS 17 update experience. My device is a China-model PJZ110. I had unlocked the bootloader and was running an India ROM on version 16.xx.yyyy. I can’t remember the exact version, but I think it was an early-year build. I had relocked the bootloader and was not rooted. I unlocked the bootloader and upgraded directly to ColorOS 17 using Jonas’s Super_Flasher (17.0.0.102). Unfortunately, the phone was completely bricked and could only enter Qualcomm 9008 mode. I contacted OPPO Global Warranty Support, and they helped me flash it back to Android 16 for 3 dollars. After returning to ColorOS 16, I unlocked the bootloader again and upgraded directly to ColorOS 17 using Jonas’s Super_Flasher (17.0.0.102). The phone bricked again, but this time it could still enter fastboot, so I used Jonas’s Super_Flasher (16.0.10.600) and got it working again. I happened to see on XDA that there was support for upgrading to ColorOS 17, so I came here. I unlocked the bootloader again while on version 16.0.10.600 and ran GlobalCOS Flasher 13 IN on 17.0.0.102. Everything seemed fine, but I had no signal. I rebooted into fastbootd, flashed my_region.img, and then relocked the bootloader. That’s the whole story. I’m now running ColorOS 17 IN with the bootloader locked.
  • Previous
  • You're on page 1
  • Next