Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks, i spent sever hours but finally have some progress. First of all i am not sure which kernel i had, i used this img before: Armbian_5.91_Aml-s905_Ubuntu_disco_default_5.1.0_desktop_20190708.img But yesterday started to play around with the rest of the dtbs and voila the nexbox a95x seems to be working, i have wifi, usb, eth etc. So finally i could boot from my SD card, then i started to move to emmc, i had some nightmares here. I used first the install-aml-s905-emmc.sh, seems to copied but after restart it did not want to boot from emmc But still could boot form SD. I have no idea why did not work, but i found that i should use install-aml.sh, so i did. This is bricked my device so deeply, that i have spent several hours until i could figure out how to short my emmc and restore my android. But after that i have boot again from SD card and i used at first the install-aml.sh and after reboot it did not boot automatically, i have to use an SD which has an u-boot or similar (created with USB Card maker but deleted all the files). Now it seems to be working and running from emmc. Wasn't easy..
  2. Okay it seems my issue is related to the dtb file, i have used the wetek-hub's dtb and it was booted..unfortunately usb is not working. But this is really strange, i am 100% sure i have to use gxbb p200 dtb.
  3. Yes, i have restored the Android and used this method: option A - Connect the prepared media to the device and turn on the power, boot into Android - Open the app "Update&Backup" - Click on "Select" local update and chose the file on the removable media aml_autoscript.zip - Start "Update" - System will reboot twice and start running the system from external media. For me the option B never worked. The only thing, that i guess it did not restart twice. btw is that normal that aml_autoscript.zip size is 0?
  4. Hi All, So i have decide to update my system with a clean install. First of all i have a Beelkink Mini MXIII S905 box, i had running so far 19.04 Ubuntu (updated to 19.10). I have downloaded this image: Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img.xz and wrote to an SD card, booted up. extlinux.conf: FDT /dtb/amlogic/meson-gxbb-p200.dtb APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 I use s905 u-boot > u-boot.ext The dtb should be the good one as i used that for my previous linux. When i boot i get this error: ALERT! LABEL=ROOTFS does not exists! I have tried 2 different SD cadrs, but the same. Anybody has any idea what can be the problem? Thanks
  5. Dear All, I have a Beelink s905 box with Armbian (Ubuntu 19.10). I have problems to install Mosquitto as it is required a package which i don't know how to install: The following packages have unmet dependencies: mosquitto:armhf : Depends: libwebsockets8:armhf (>= 1.6.0) but it is not installable E: Unable to correct problems, you have held broken packages. I am okay to use another type of Mqtt broker but couldn't find a solution I am searching for hours now.. Somebody has any ideas? Thank you in advance
  6. Okay i have created lot of logs, i hope this will help. uart-android boot.txt install.sh output.txt uart-armbian-external boot.txt after install.sh.txt armbian emmc boot with recovery sd card with uboot from the android img.txt
  7. Wait I guess this conversation went into a wrong way I have restored the Android and sent you the requested fdisk -l result. My issues is that after using the install.sh it is not able to boot Armbian from eMMC only if i use a recovery sd (which only contains an u-boot). This is where the log has been provided from the console. So the question how can i restore the u-boot to able to boot from eMMC without using the SD Card? I was able to unpack the original firmware image and i have the u-boot if that is help. But not sure what is the exact way to solve this. Thanks
  8. Yes, but how this help me to solve the issue with the missing u-boot?
  9. Trying to figure out how to make backup, not that expert..
  10. Can it be solved without deleting my armbian? I've installed lot if things, i dont want to loose them What if i burn the u-boot img from the stock rom into emmc? Like it is on the sd card?
  11. Additional comment, this point where you can see the end of the log, my armbian stops booting. This happens if i restart or just start, after replug the power cable, starting fine. Any ideas? boot with recovery sd.txt
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines