• Content Count

  • Joined

  • Last visited

Everything posted by Janaboy

  1. 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
  2. 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 so
  3. Yes, but how this help me to solve the issue with the missing u-boot?
  4. Trying to figure out how to make backup, not that expert..
  5. 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?
  6. 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
  7. I was able to access the console, this is the message: GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:17A;SD:800;USB:8;LOOP:1;EMMC:0;READ:0;CHK:17A;SD:800;USB:8;LOOP:2;EMMC:0;READ:0;CHK:17A;SD:800;USB:8;LOOP:3;EMMC:0;READ:0;CHK:17A;SD:800;USB:8;LOOP:4;EMMC:0;READ:0;CHK:17A;SD:800;USB:8;LOOP:5;EMMC:0;READ:0;CHK:17A;SD:800;USB:8;LOOP:6;EMMC:0;READ:0;CHK:17A;SD:800;USB:8;LOOP:7;EMMC:0;READ:0;CHK:17A;SD:800;USB:8; and this when i plugin the sd card: D:800;USB:8;LOOP:16;EMMC:0;READ:0;CHK:17A;SD:800;USB:8;LOOP:17;EMMC:0;READ:0;CHK:17A;SD:0;READ
  8. 2. I always used the Update&Backup and start the aml_script.zip from Android and then used the install.sh, not sure is this the proper step? What i found it is. About the UART logs, unfortunately no UART port specified on the board, so not sure how to get access to the console. But i was able to start the Armbian form the emmc, this way: used the android image and the Boot SD card maker software, with the img burned to an SD card (which is interesting so far only my 4GB SDHC is working), the tool reformatted my sd card (and i understand properly burn the uboot img into the
  9. Okay very-very insteresting situation.. So i am working to resolve the booting issue, so i looked for some solutions. I've used the AML Boot SD card maker software to recover my android. This software reformatted my sd card (i have a 16 mb unknown at the beginning of the card), and copied 3 files, i have deleted all the three files and without doing anything special step (like using the reset button) the Armbian on the eMMC just booting fine. Any idea why? Or how i can solve this without using the SD Card? Update: I've tried to compare my /boot partition
  10. Hi @balbes150, I hope i can ask a little help from you. I have a Beelink Mini MXIII box (S905, 2G/16). I have downloaded this img: Armbian_5.91_Aml-s905_Ubuntu_disco_default_5.1.0_desktop_20190708.img installed on a 8gb sd card and renamed the dtb in uenv.ini and extlinux.conf to meson-gxbb-p200.dtb. From Android i have selected the Update&Backup and used the aml_script.zip to install/start my linux. It is starting just fine, but i would like to move the whole thing to the eMMC. I saw in the dmesg that my emmc is mmcblk0, so i renamed it in install.sh,
  11. You were right, my inside mmc is on mmcblk0 and in the script it was set to mmcblk1, this is my dmesg: [ 2.883038] meson-gx-mmc d0074000.mmc: allocated mmc-pwrseq [ 3.078893] mmc0: new HS200 MMC card at address 0001 [ 3.079860] mmcblk0: mmc0:0001 NCard 14.5 GiB [ 3.083401] mmcblk0boot0: mmc0:0001 NCard partition 1 4.00 MiB [ 3.089259] mmcblk0boot1: mmc0:0001 NCard partition 2 4.00 MiB [ 3.094559] mmcblk0rpmb: mmc0:0001 NCard partition 3 4.00 MiB, chardev (241:0) [ 4.303249] meson-gx-mmc d0072000.mmc: Got CD GPIO [ 4.538643] mmc1: new high speed SD
  12. I would like to request for a little help, my Ubuntu was running on an SD card (Beelink Mini MXIII) and i wanted move to emmc, used the ./install.sh command. It was doing for around 10 minutes and ending with this: tar: var/cache/man/it: file changed as we read it tar: var/cache/man/ja/index.db: file changed as we read it tar: var/cache/man/ja: file changed as we read it tar: var/cache/man/nl/index.db: file changed as we read it tar: var/cache/man/nl: file changed as we read it tar: var/cache/man/es/index.db: file changed as we read it tar: var/cache/man/es: file chang
  13. Thanks @erew You are right, probably easier to buy a cheap dongle which is comptablie as it is not working out of the box, but you know, i like to use those devices. btw it has RTL8723BS chip in it, and tried some topics, but couldn't make it work. So i won't spent much time with it. However would be great to know about a 100% working dongle, so i hope someone will send me a model.
  14. Would be great to see how the bluetooth could be activated? I have a Beelking Mini MXIII (s905,2/16) using with gxbb-p200 dtb, and the wifi is working, but the bluetooth is not
  15. @erew: your post is really helpful and solved my installing issues in 2 minutes. The first post should be updated with this. Thanks.