Difference between revisions of "How to Restore Android9 OS to the eMMC on NX8MM-35"
From ICOP tech wiki
(3 intermediate revisions by the same user not shown) | |||
Line 7: | Line 7: | ||
===<big>Tools you need before restoring the image to the eMMC:</big>=== | ===<big>Tools you need before restoring the image to the eMMC:</big>=== | ||
− | *'''NX8MM-35 2GB RAM image''' with the '''UUU burning software''':https://ftp.icop.com.tw/share/ | + | *'''NX8MM-35 2GB RAM image''' with the '''UUU burning software''':https://ftp.icop.com.tw/share/E-ZYSO0y |
*A 64-bit Linux host O/S on a PC (The virtual machine is not suggested to be used)\ | *A 64-bit Linux host O/S on a PC (The virtual machine is not suggested to be used)\ | ||
Line 17: | Line 17: | ||
*Find the SW1 on the NX8MM-35 and change the setting to Serial Download Mode according to the photo below: | *Find the SW1 on the NX8MM-35 and change the setting to Serial Download Mode according to the photo below: | ||
− | [[File: | + | [[File:NX8MM-35 JP.jpg|alt=|frameless|449x449px]] |
*Turn on the host PC and unzip the image file in it. | *Turn on the host PC and unzip the image file in it. | ||
*Connect the USB to micro USB to the host PC, but not connect to the NX8MM-35. | *Connect the USB to micro USB to the host PC, but not connect to the NX8MM-35. | ||
− | *Open a terminal on the host PC and access the location you’ve put the image file and input “sudo uuu | + | *Open a terminal on the host PC and access the location you’ve put the image file and input "sudo chmod a+x uuu" to enable uuu as executable command. |
+ | *Input “sudo ./uuu xxxx.lst” (check the xxxx.auto name in the file) ; you will see “Wait for known USB Device Appear” | ||
Installation command for different eMMC capacity: | Installation command for different eMMC capacity: | ||
Line 28: | Line 29: | ||
32.lst --> 32GB version | 32.lst --> 32GB version | ||
64.lst --> 64GB version | 64.lst --> 64GB version | ||
− | + | <br /> | |
− | *Connect the Micro USB to the NX8MM-35, and it will trigger the serial download mode to restore the image from the host PC. | + | *Connect the Micro USB to the NX8MM-35, and it will trigger the serial download mode to restore the image from the host PC.[[File:Linux Android image1.png|alt=|frameless|760x760px]] |
*After the restore process is done, it will show on the host PC as the image below: | *After the restore process is done, it will show on the host PC as the image below: | ||
Line 37: | Line 38: | ||
*Remove the USB to Micro USB cable on the NX8MM-35 (Power off), and set the SW1 to Internal boot as below. | *Remove the USB to Micro USB cable on the NX8MM-35 (Power off), and set the SW1 to Internal boot as below. | ||
− | [[File: | + | [[File:NX8MM-35 JP2.jpg|alt=|frameless|460x460px]] |
*Power on the NX8MM-35 and you can see the Android9 booting. | *Power on the NX8MM-35 and you can see the Android9 booting. | ||
Line 49: | Line 50: | ||
===Tools you need before restoring the image to the eMMC:=== | ===Tools you need before restoring the image to the eMMC:=== | ||
− | *'''NX8MM-35 2GB RAM image''' with the '''UUU burning software''':https://ftp.icop.com.tw/share/ | + | *'''NX8MM-35 2GB RAM image''' with the '''UUU burning software''':https://ftp.icop.com.tw/share/E-ZYSO0y |
*A Windows 10 host O/S on a PC (The virtual machine is not suggested to be used) | *A Windows 10 host O/S on a PC (The virtual machine is not suggested to be used) | ||
*USB cable to connect between the host PC and the NX8MM-35. (Ex: USB to micro USB) | *USB cable to connect between the host PC and the NX8MM-35. (Ex: USB to micro USB) | ||
Line 58: | Line 59: | ||
*Find the SW1 on the NX8MM-35 and change the setting to Serial Download Mode according to the photo below: | *Find the SW1 on the NX8MM-35 and change the setting to Serial Download Mode according to the photo below: | ||
− | [[File: | + | [[File:NX8MM-35 JP.jpg|alt=|frameless|449x449px]] |
*Turn on the host PC and unzip the image file to it. | *Turn on the host PC and unzip the image file to it. | ||
Line 78: | Line 79: | ||
*Remove the USB to Micro USB cable on the NX8MM-35 (Power off), and set the SW1 to Internal boot as below. | *Remove the USB to Micro USB cable on the NX8MM-35 (Power off), and set the SW1 to Internal boot as below. | ||
− | [[File: | + | [[File:NX8MM-35 JP2.jpg|alt=|frameless|460x460px]] |
*Power on the NX8MM-35 and you can see the Yocto Linux booting. | *Power on the NX8MM-35 and you can see the Yocto Linux booting. | ||
[[File:1.2.9.png|frameless|560x560px]] | [[File:1.2.9.png|frameless|560x560px]] |
Latest revision as of 20:53, 27 December 2023
Restore the Android9 OS via Linux host PC to the NX8MM-35
Contents
Restore the Android9 OS via Linux host PC to the NX8MM-35
Tools you need before restoring the image to the eMMC:
- NX8MM-35 2GB RAM image with the UUU burning software:https://ftp.icop.com.tw/share/E-ZYSO0y
- A 64-bit Linux host O/S on a PC (The virtual machine is not suggested to be used)\
- USB cable to connect between the host PC and the NX8MM-35. (Ex: USB to micro USB)
Write the image to the eMMC on the NX8MM-35.
- This section will introduce how to write the image to the eMMC on the NX8MM-35 step by step.
- Find the SW1 on the NX8MM-35 and change the setting to Serial Download Mode according to the photo below:
- Turn on the host PC and unzip the image file in it.
- Connect the USB to micro USB to the host PC, but not connect to the NX8MM-35.
- Open a terminal on the host PC and access the location you’ve put the image file and input "sudo chmod a+x uuu" to enable uuu as executable command.
- Input “sudo ./uuu xxxx.lst” (check the xxxx.auto name in the file) ; you will see “Wait for known USB Device Appear”
Installation command for different eMMC capacity: 08.lst --> 8GB version 16.lst --> 16GB version 32.lst --> 32GB version 64.lst --> 64GB version
- Connect the Micro USB to the NX8MM-35, and it will trigger the serial download mode to restore the image from the host PC.
- After the restore process is done, it will show on the host PC as the image below:
- Remove the USB to Micro USB cable on the NX8MM-35 (Power off), and set the SW1 to Internal boot as below.
- Power on the NX8MM-35 and you can see the Android9 booting.
Restore the Android9 OS via Win10 host PC to the NX8MM-35
Tools you need before restoring the image to the eMMC:
- NX8MM-35 2GB RAM image with the UUU burning software:https://ftp.icop.com.tw/share/E-ZYSO0y
- A Windows 10 host O/S on a PC (The virtual machine is not suggested to be used)
- USB cable to connect between the host PC and the NX8MM-35. (Ex: USB to micro USB)
Write the image to the eMMC on the NX8MM-35.
This section will introduce how to write the image to the eMMC on the NX8MM-35 step by step.
- Find the SW1 on the NX8MM-35 and change the setting to Serial Download Mode according to the photo below:
- Turn on the host PC and unzip the image file to it.
- Connect the USB to micro USB cable to the host PC, but not connect to NX8MM-35.
- Open a terminal with administration right on the host PC and access the location you’ve put the image file and input “_16.bat” to install 16GB eMMC version image , and you will see “Wait for known USB Device Appear”.
Installation command for different eMMC capacity: _08.bat --> 8GB version _16.bat --> 16GB version _32.bat --> 32GB version _64.bat --> 64GB version
- Connect the Micro USB to the NX8MM-35, and it will trigger the serial download mode to restore the image from the host PC.
- After the restore process is done, it will show on the host PC as the image below:
- Remove the USB to Micro USB cable on the NX8MM-35 (Power off), and set the SW1 to Internal boot as below.
- Power on the NX8MM-35 and you can see the Yocto Linux booting.