ASUS ROG Phone 3 unbrick tool is now available
Over the last couple of years, ASUS has managed to establish itself as a true gaming smartphone brand through its Republic of Gamers (ROG) series. The recently launched ROG Phone 3 packs in some of the most powerful hardware you can find in a smartphone, like the flagship Qualcomm Snapdragon 865+ chipset, up to 16GB of RAM, a 6,000mAh battery, two USB-C ports, and a 144Hz high refresh rate AMOLED display panel. The Taiwanese brand has also been receptive to the aftermarket developer community on XDA, as you can already pick up the official bootloader unlock tool as well as the kernel source for this phone from ASUS’ download portal.
ASUS ROG Phone 3 XDA Review: The King of Gaming Smartphones is back
However, modifying your device is not without its risks, and it can even lead to you temporarily bricking your phone. If you don’t want to pay a visit to a service center or ship your phone to one but like to bring your monster gaming phone back from the dead, you need to find an appropriate flashing tool that can communicate with the device using the built-in Emergency Download Mode (EDL) of the Qualcomm Snapdragon SoC. Luckily, XDA Senior Member deadlyindian has collected all the required packages, so that you can use them to flash your ASUS ROG Phone 3 (including the Chinese Tencent variant) back to stock.
Unbrick tool for the ASUS ROG Phone 3
You need a PC running Microsoft Windows 7 or newer to run the flasher. There are two batch files: The first one is required for sending the low-level software binaries (usually referred to as programmers) in the EDL mode, while the second one is intended for flashing the actual firmware using the Fastboot interface. The flashing process will wipe your phone and re-lock the bootloader. Make sure to use the USB Type-C port on the side of the phone for the whole operation.
Buy the ASUS ROG Phone 3 from Flipkart
The post ASUS ROG Phone 3 unbrick tool is now available appeared first on xda-developers.
from xda-developers https://ift.tt/3guF5Ad
via IFTTT
No comments: