Difference between revisions of "Template:RockchipUnbrick"
From FriendlyELEC WiKi
(updated by API) |
(updated by API) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
* '''Get the loader''': Visit [http://112.124.9.243/dvdfiles/ here], enter the tools directory corresponding to your CPU model, and download '''MiniLoaderAll.bin'''. | * '''Get the loader''': Visit [http://112.124.9.243/dvdfiles/ here], enter the tools directory corresponding to your CPU model, and download '''MiniLoaderAll.bin'''. | ||
==== Enter Maskrom Mode to Erase the Storage Device ==== | ==== Enter Maskrom Mode to Erase the Storage Device ==== | ||
| − | |||
* Start '''RKDevTool''' on your computer. | * Start '''RKDevTool''' on your computer. | ||
| − | * | + | {{#switch: {{{1}}} |
| + | | NanoPi-R5C = | ||
| + | * Press and hold the “Mask” key, power on the board. After the status LED has been on for at least 3 seconds, release the Mask key | ||
| + | * Use a USB A-to-A cable, connect {{{1}}} to a PC as follows, connect to the USB port on the side near the TF card | ||
| + | | NanoPi-R4SE | ||
| + | | NanoPi-R5S | ||
| + | | NanoPi-R6S | ||
| + | | NanoPi-R6C = | ||
| + | * Press and hold the “Mask” key, power on the board. After the status LED has been on for at least 3 seconds, release the Mask key | ||
| + | * Use a USB A-to-A cable, connect {{{1}}} to a PC as follows | ||
| + | | NanoPC-T6 | ||
| + | | NanoPC-T6-LTS | ||
| + | | CM3588 = | ||
| + | * Press and hold the “Mask” key, power on the board. After the status LED has been on for at least 3 seconds, release the Mask key | ||
| + | * Use a USB C-to-A cable, connect {{{1}}} to a PC | ||
| + | | NanoPi-R3S | ||
| + | | NanoPi-R2S-Plus = | ||
| + | * Press and hold the “Mask” key, Use a USB C-to-A cable, connect {{{1}}} to a PC，After the status LED has been on for at least 3 seconds, release the Mask key | ||
| + | | SOM-RK3399 = | ||
| + | * Press and hold the "Recover" key, Use a USB C-to-A cable, connect {{{1}}} to a PC，After the status LED has been on for at least 3 seconds, release the "Recover" key | ||
| + | | #default = | ||
| + | * Press and hold the “Mask” key, Use a USB cable, connect {{{1}}} to a PC，After the status LED has been on for at least 3 seconds, release the Mask key | ||
| + | }} | ||
| + | {{#switch: {{{1}}} | ||
| + | | NanoPi-R4SE = | ||
| + | [[File:Nanopir4se-usba-to-usba.jpg|frameless|400px]] | ||
| + | | NanoPi-R6S = | ||
| + | [[File:Nanopir6s-usba-to-usba2.jpg|frameless|400px]] | ||
| + | | NanoPi-M6 = | ||
| + | [[File:Nanopim6-usba-to-usba2.jpg|frameless|400px]] | ||
| + | | NanoPi-R6C = | ||
| + | [[File:Nanopir6c-usba-to-usba.jpg|frameless|400px]] | ||
| + | | NanoPi-R5S = | ||
| + | [[File:Nanopir5s-usba-to-usba2.jpg|frameless|400px]] | ||
| + | | NanoPi-R5C = | ||
| + | [[File:R5C-usbflash.jpg|frameless|400px]] | ||
| + | | NanoPi-R2S-Plus = | ||
| + | [[File:R2SPLUS-usbflash.jpg|frameless|400px]] | ||
| + | | NanoPi-R3S = | ||
| + | [[File:Xianshua-R3S.jpg|frameless|400px]] | ||
| + | | NanoPC-T6-LTS | ||
| + | | NanoPC-T6 = | ||
| + | [[File:T6LTS-usbflash.jpg|frameless|400px]] | ||
| + | | CM3588 = | ||
| + | [[File:Cm3588-usbflash.jpg|frameless|400px]] | ||
| + | | NanoPi-Zero2 = | ||
| + | [[File:Zero2-usbflash.jpg|frameless|400px]] | ||
| + | | #default = | ||
| + | }} | ||
| + | * You will see '''Found One MASKROM Device''' displayed at the bottom of the '''RKDevTool''' interface, as shown below: | ||
[[File:Rkdevtool_found_one_maskrom_device.png|frameless|600px]] | [[File:Rkdevtool_found_one_maskrom_device.png|frameless|600px]] | ||
* Click the '''Advanced Function''' tab in the '''RKDevTool''' interface. | * Click the '''Advanced Function''' tab in the '''RKDevTool''' interface. | ||
| Line 24: | Line 72: | ||
}} | }} | ||
* At this point, {{{1}}} is restored to its initial state and can be normally booted via SD card or eMMC. | * At this point, {{{1}}} is restored to its initial state and can be normally booted via SD card or eMMC. | ||
| − | ===Linux | + | ===Linux Users=== |
====Download the Required Files==== | ====Download the Required Files==== | ||
| − | * '''Get the necessary tools''': Visit [https://dl.friendlyelec.com/{{{1}}} here] and find '''upgrade_tool_v2.30_for_linux.tgz''' | + | * '''Get the necessary tools''': Visit [https://dl.friendlyelec.com/{{{1}}} here] and find '''upgrade_tool_v2.30_for_linux.tgz''' in the '''05_Tools''' directory and download it locally. |
* '''Get the loader''': Visit [http://112.124.9.243/dvdfiles/ here], enter the tools directory corresponding to your CPU model, and download '''MiniLoaderAll.bin'''. | * '''Get the loader''': Visit [http://112.124.9.243/dvdfiles/ here], enter the tools directory corresponding to your CPU model, and download '''MiniLoaderAll.bin'''. | ||
====Installation for upgrade_tool==== | ====Installation for upgrade_tool==== | ||
| − | + | Using the following commands: | |
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
tar xzf upgrade_tool_v2.30_for_linux.tgz | tar xzf upgrade_tool_v2.30_for_linux.tgz | ||
| Line 62: | Line 110: | ||
}} | }} | ||
* At this point, {{{1}}} has been restored to its initial state and can boot the system normally via SD card or eMMC. | * At this point, {{{1}}} has been restored to its initial state and can boot the system normally via SD card or eMMC. | ||
| + | ===Mac Users=== | ||
| + | Our tests found that upgrade_tool_v2.25 does not work properly on macOS. Therefore, we recommend using Windows or Linux unless an updated version of upgrade_tool becomes available. | ||
Latest revision as of 09:37, 22 November 2024
Contents
1 Unbricking Method
If the ROM is not installed correctly, causing the development board to become bricked, and you might not have the opportunity to reinstall the ROM via an SD card, you need to enter Maskrom mode to unbrick it by erasing the storage device.
1.1 Windows Users
1.1.1 Download Required Files
- Get the necessary tools: Visit here, find RKDevTool_v3.19_for_window.zip and DriverAssitant_v5.12.zip in the 05_Tools directory, and download them to your local machine.
- Install Rockchip USB driver and RKDevTool: Extract DriverAssitant_v5.12.zip to install the Rockchip USB driver, and extract RKDevTool_v3.19_for_window.zip to obtain the Rockchip flashing tool RKDevTool.
- Get the loader: Visit here, enter the tools directory corresponding to your CPU model, and download MiniLoaderAll.bin.
1.1.2 Enter Maskrom Mode to Erase the Storage Device
- Start RKDevTool on your computer.
- Press and hold the “Mask” key, Use a USB cable, connect {{{1}}} to a PC，After the status LED has been on for at least 3 seconds, release the Mask key
- You will see Found One MASKROM Device displayed at the bottom of the RKDevTool interface, as shown below:
- Click the Advanced Function tab in the RKDevTool interface.
- In the Boot text box, select MiniLoaderAll.bin, then click the Download button.
- Select EMMC, click Switch Storage, then click the EraseAll button to erase the eMMC.
- At this point, {{{1}}} is restored to its initial state and can be normally booted via SD card or eMMC.
1.2 Linux Users
1.2.1 Download the Required Files
- Get the necessary tools: Visit here and find upgrade_tool_v2.30_for_linux.tgz in the 05_Tools directory and download it locally.
- Get the loader: Visit here, enter the tools directory corresponding to your CPU model, and download MiniLoaderAll.bin.
1.2.2 Installation for upgrade_tool
Using the following commands:
tar xzf upgrade_tool_v2.30_for_linux.tgz cd upgrade_tool_v2.30_for_linux sudo cp upgrade_tool /usr/local/sbin/ sudo chmod 755 /usr/local/sbin/upgrade_tool
1.2.3 Enter Maskrom Mode to Erase the Storage Device
- Connect {{{1}}} to the computer using a USB data cable.
- Disconnect the power from {{{1}}}, hold down the MASK button, connect the power, and release the button after 4 seconds.
- Check the connection with the following command:
upgrade_tool LD
A result similar to "DevNo=1 Vid=0x2207,Pid=0x350b,LocationID=13 Mode=Maskrom SerialNo=" indicates that the device has been detected.
- Erase the eMMC with the following command:
upgrade_tool EF MiniLoaderAll.bin
- At this point, {{{1}}} has been restored to its initial state and can boot the system normally via SD card or eMMC.
1.3 Mac Users
Our tests found that upgrade_tool_v2.25 does not work properly on macOS. Therefore, we recommend using Windows or Linux unless an updated version of upgrade_tool becomes available.
