logo elektroda
logo elektroda
X
logo elektroda

Installing Official & Unofficial Android on Orange Pi Plus 2: EMMC, KitKat 4.4.2, PhoenixCard

strikerbest 4662 6
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 16376707
    strikerbest
    Level 12  
    Hello. I recently bought Orange Pi Plus 2. After reading a few toturials and watching a few videos on YouTube, I downloaded the official Android from the manufacturer's website and the unofficial Android KitKat 4.4.2 (new1_e_w_work.img). Using the PhoenixCard app, I recorded an official Android image to the SD card. I was able to start the device and test it for a while. Curious about the operation of the unofficial software (KitKat), I recorded it according to the instructions again using PhoenixCard and, according to some YouTube video, I started it on my OPI Plus 2. I noticed that the system starts to install in the internal memory, unlike the official firmware. I used KitKat for almost a month. Once, for unknown reasons, it was reset to factory settings.

    Unfortunately, last weekend, while watching some material on YT, OPI shut down. The fan was spinning, but the LED was not glowing red. After several attempts to connect and disconnect the power, I found that the device has probably reset and the system should be re-loaded. Unfortunately, after re-uploading the image to SD, Android turns on and works only from the SD card. In addition, it has completely lost its smooth operation and stability. The simple task of opening SETTINGS or Google Play takes a lot of time and is often impossible to complete.

    When creating a system image to an SD Card via PhoenixCard, there are two options (basically three) to choose from. The first "PRODUCT MODE" and the second "STARTUP MODE". As I guess, depending on the choice, PRODUCT MODE is a system that installs on the internal EMMC memory. In my case, after creating such an image with KitKat, the D8 diode lights red for a moment and then starts blinking and the image shows a green installation progress bar in a red dust jacket on a black background. This is where the whole process ends. Just like it would hang. The futile waiting of 30 minutes did not change anything.

    In the case of STARTUP MODE the D8 diode lights for a moment in red and the H3 logo appears. Then D7 turns green and finally the LEDs change again and D8 lights up red again. The system boots up and runs from the SD card.

    Can anyone tell me what I can do to reinstall Android on the internal EMMC memory? Or maybe my Orange PI Plus 2 has been damaged after a month and it is no longer possible to use it fully functionally?
  • ADVERTISEMENT
  • #2 16377375
    Anonymous
    Anonymous  
  • ADVERTISEMENT
  • #3 16377514
    strikerbest
    Level 12  
    I bought a 16GB class 10 SD card yesterday. They wrote on foreign-language forums that with these cheap cards it works differently. After recording on the card, the device works much faster, but still this operation is limited only to the SD card and the EMMC memory is not moved. Perhaps it would need to be formatted somehow from under some other operating system. I also started Armbian and Lubuntu. I am not very strong on these systems so I need some help.
  • ADVERTISEMENT
  • #4 16377549
    Anonymous
    Anonymous  
  • #5 16378001
    strikerbest
    Level 12  
    It looks like the picture. Debian Jessie.
    There are supposedly three carriers:
    - mmcblk0p1
    -mmcblk0p2
    -mmcblk1p2
    Installing Official & Unofficial Android on Orange Pi Plus 2: EMMC, KitKat 4.4.2, PhoenixCard
  • ADVERTISEMENT
  • #6 16378079
    Anonymous
    Anonymous  
  • #7 16378137
    strikerbest
    Level 12  
    I am using several SD cards alternately at the moment: 4, 8, 16 (the latter is in class10).
    The internal memory of the Orange Pi Plus 2 is 16GB.

    Is it something like that?

    orangepi@OrangePI:~$ sudo fdisk -l
    sudo: unable to resolve host OrangePI
    
    Disk /dev/mmcblk0: 7.2 GiB, 7746879488 bytes, 15130624 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x7a47e671
    
    Device Boot Start End Sectors Size Id Type
    /dev/mmcblk0p1 40960 172031 131072 64M b W95 FAT32
    /dev/mmcblk0p2 172032 2953216 2781185 1.3G 83 Linux
    
    Disk /dev/mmcblk1: 14.6 GiB, 15634268160 bytes, 30535680 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x00000000
    
    Device Boot Start End Sectors Size Id Type
    /dev/mmcblk1p1 * 4923392 30601215 25677824 12.3G b W95 FAT32
    /dev/mmcblk1p2 73728 106495 32768 16M 6 FAT16
    /dev/mmcblk1p3 1 4816896 4816896 2.3G 5 Extended
    /dev/mmcblk1p5 106496 139263 32768 16M 83 Linux
    /dev/mmcblk1p6 139264 172031 32768 16M 83 Linux
    /dev/mmcblk1p7 172032 1744895 1572864 768M 83 Linux
    /dev/mmcblk1p8 1744896 1777663 32768 16M 83 Linux
    /dev/mmcblk1p9 1777664 1843199 65536 32M 83 Linux
    /dev/mmcblk1p10 1843200 3416063 1572864 768M 83 Linux
    /dev/mmcblk1p11 3416064 3448831 32768 16M 83 Linux
    /dev/mmcblk1p12 3448832 3481599 32768 16M 83 Linux
    /dev/mmcblk1p13 3481600 3514367 32768 16M 83 Linux
    /dev/mmcblk1p14 3514368 3579903 65536 32M 83 Linux
    /dev/mmcblk1p15 3579904 3612671 32768 16M 83 Linux
    /dev/mmcblk1p16 3612672 4923391 1310720 640M 83 Linux
    
    Partition table entries are not in disk order.
    Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    orangepi@OrangePI:~$

Topic summary

The discussion revolves around the installation of both official and unofficial Android versions on the Orange Pi Plus 2. The user successfully installed the official Android and an unofficial KitKat 4.4.2 image using the PhoenixCard application. However, after using the unofficial software for a month, the device unexpectedly reset to factory settings and subsequently failed to boot, indicated by a non-glowing LED despite the fan operating. Other participants shared experiences with unofficial Android versions causing boot loops and bricking issues, suggesting that the problem may not be hardware-related. The user also explored the internal EMMC memory and various SD cards, noting performance differences and the need for proper formatting to utilize the EMMC memory effectively.
Summary generated by the language model.
ADVERTISEMENT