Jump to content



Recommended Posts

Hello everyone. I have a REMIX MINI with 2GB Ram and 16 Rom. 
I am trying to boot with microSD with Armbian_22.08.1_Pine64_jammy_current_5.15.63_xfce_desktop.img.xz image.
I paste it with Balena and then paste TOC0
   wget https://github.com/ssvb/sunxi-tools/raw/toc0/bin/fel-sdboot.toc0
   dd if=fel-sdboot.toc0 of=/dev/sdX bs=1024 seek=8

But I can't.
Any idea?

I managed to connect the device in fastboot mode to the PC, this is what I see?

Bus 001 Device 006: ID 1f3a:1010 Allwinner Technology Android Device in fastboot mode.

Can I do some backup from console with sunxi-tools or enter the device?

Translated with www.DeepL.com/Translator (free version)

Link to comment
Share on other sites

Armbian Linux community supported weekly builds download

This device is not a supported by Armbian.  I moved this post to unsupported -> Off Topic. 

A search of the forum leads to the following two older discussions about this device:




Link to comment
Share on other sites

Thank you for your response.
I saw all the posts about Jide Remix on this site but I can't get it to start.
I don't know if I should really use the Pine64 image or the Banana Pi M64 image.

With a system information apk, I got this chipset identifier (sun50iw1p1), which makes me suspect that it is the one used in banana pi m64.


Where am I going wrong? What are the steps I should do to try to boot armbian correctly ?



Link for the Kernel at JIDE REMIX MINI.



Modelo: Remix Mini (rm1g)
Fabricante: Jide
Versión de Banda Base: No disponible
Versión RIL: No disponible
Número de compilación: LMY47I.B2017030801
Construir Huella Digital: Jide/rm1g/rm1g:5.1/LMY47I/B2017030801:user/release-keys
Gestor de Arranque: unknown
Java VM: ART 2.1.0
Versión de Sistema Operativo: Lollipop MR1 (5.1)
SDK: 22

Resolución: 1240x644 pixels
Densidad de Software: 160 dpi (mdpi)
Frecuencia de actualización: 60 Hz

Arquitectura del CPU: ARMv8-A
Tablero: exdroid
Chipset: sun50iw1p1
Nucleos: 4
Frecuencia del reloj: 480 MHz - 1152 MHz
Conjunto de Instrucciones: arm64-v8a
Caracteristicas del CPU: fp asimd aes pmull sha1 sha2 crc32
Regulador de CPU: No disponible
Versión del Kernel: 3.10.93
Arquitectura del Kernel: aarch64

Renderizador: Mali-400 MP2
Proveedor: ARM
Versión OpenGL: OpenGL ES 2.0

Total: 1985 MB
Java Heap: 192 MB

Interno: 12 GB
Externo: 992.7 MB

Bluetooth: Si
Bluetooth LE: Si
USB Accesorio: Si
WiFi: Si
WiFi Direct: Si

Tecnología: LiFe
Salud: Bueno

No disponible

Creado por Droid Info


Edited by MSabino
Link to comment
Share on other sites

I don't think you understand.  First your device isn't supported.  Per the previous discussions on the site that I linked and you confirmed you read, no one has successfully installed armbian on your device.  And finally the information contained in the previous posts indicates that it isn't possible to put armbian on your device.

This is open source, so feel free to work on this yourself if you desire, but you aren't going to get any additional help from armbian maintainers on this.

Link to comment
Share on other sites

From all I could find, the CPU is Allwinner H64, I think it's the only model that has this particular CPU. I don't know if another one is compatible. A64 maybe?


CPU1: Allwinner H64 (1.2 GHz, 4 cores)


Stock bootloader: U-Boot  2014.07

Stock FW OS: Linux 3.10.87 ReMix OS 2.0



Boot log






Link to comment
Share on other sites

I think good informations are also on 




The SoC has the "secure boot" fuse burned, so it will not accept any standard eGON boot media (on an SD card or on the eMMC). Instead it expects TOC0 wrapped boot code. Fortunately there does not seem to be any actual ROTPK HASH key burned into the fuses, so it will not try to match against a certain key, but will load boot code (SPL) signed with *any* key.




Allwinner H64 is targetted for OTT boxes and A64 for the tablets. Both are quad core Cortex A53 processors with a Mali-400MP2 GPU, H.265 4K video playback with basically the same interfaces and peripherals, but H64 also supports H.264 at 4K resolutions, while A64 is limited to H.264 @ 1080p, and H64 adds a TS interface


Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...