Jump to content

Armbian for Amlogic S805 and S802/S812

masteripper

By masteripper
in Amlogic CPU Boxes

 Share

Recommended Posts

K200_Noob

K200_Noob

Posted
Posted
  On 1/25/2020 at 4:39 PM, Red2 said:

Closer. Goes through boot up screen. But gets stuck at. 

U 18.04 LTS vegas812 tty1

Expand  

that sounds promising. Whats is the make and model of your box? is it k200b or c ? and way to find android firmware online?

 

i would also suggest reformatting sdcard and reburning it else use another sdcard, 

 

run a dmesg on your computer. if you get a sdcard was not unmounted correctly, 

 

run 

 

sudo fsck -fy /dev/mmcblk0p1 and do the same for p2 depending you you system...seek by lsblk

K200_Noob

K200_Noob

Posted
Posted
  On 1/25/2020 at 12:52 PM, Junoxe said:

Thank You for a tip. It seems i missed this post. So I have same situation:

 

 

So step i missed was:

 

Now, i still dont know how to activating universal multiboot. Can You write step by step?

 

And then i can wait till @balbes150 kindly repost old 3.10.99 build.

Expand  

 

find your box recovery button. use toothpick mode to activate. using update method does not always work. 

 

watch this: 

 

 

 

 

1
Red2

Red2

Posted
Posted
  On 1/25/2020 at 6:51 PM, K200_Noob said:

that sounds promising. Whats is the make and model of your box? is it k200b or c ? and way to find android firmware online?

 

i would also suggest reformatting sdcard and reburning it else use another sdcard, 

 

run a dmesg on your computer. if you get a sdcard was not unmounted correctly, 

 

run 

 

sudo fsck -fy /dev/mmcblk0p1 and do the same for p2 depending you you system...seek by lsblk

Expand  

How do you know if it is a b or c? 

Inside I found Netxeon m82 v3.1 20140923 printed on board, and Netxeon (new DC jack) MXIII v3.1 S802AP61811G8G on a sticker on the other side. No k200 anywhere. 

K200_Noob

K200_Noob

Posted
Posted
  On 1/26/2020 at 12:22 PM, Red2 said:

How do you know if it is a b or c? 

Inside I found Netxeon m82 v3.1 20140923 printed on board, and Netxeon (new DC jack) MXIII v3.1 S802AP61811G8G on a sticker on the other side. No k200 anywhere. 

Expand  

you will have to load up android and see the details or you can download and run cpu-z and see board details. example below. may not even be a k200? - post a screenshot of yours

 

image.png.4f22def24bcc7241ae4205aa7c6a57ed.png

Red2

Red2

Posted
Posted
  On 1/26/2020 at 4:43 PM, K200_Noob said:

you will have to load up android and see the details or you can download and run cpu-z and see board details. example below. may not even be a k200? - post a screenshot of yours

 

image.png.4f22def24bcc7241ae4205aa7c6a57ed.png

Expand  

Don’t know how to get screen shots off the box but here are photos. image.png.45e3ca1f6853fb90176e37b2b666adbe.png

image.png.052db015f0bc72b9a3e8af51bfc21c9e.png

image.png.599f4fec84c976701ef434ba77a46481.png

 

thinks that’s the relevant screens. Doesn’t show a revision

K200_Noob

K200_Noob

Posted
Posted
  On 1/27/2020 at 2:12 AM, Red2 said:

Don’t know how to get screen shots off the box but here are photos. image.png.45e3ca1f6853fb90176e37b2b666adbe.png

image.png.052db015f0bc72b9a3e8af51bfc21c9e.png

image.png.599f4fec84c976701ef434ba77a46481.png

 

thinks that’s the relevant screens. Doesn’t show a revision

Expand  

It's a K200 without a revision. Try burning image to SD once more and try again. Possibly an issue with SD card. I will send  you a TWRP later today which you could use to backup your firmware and we can extract your DTB file. 

 

UPDATE: the attached is the TWRP recovery for k200 boards. you need to put it on sdcard and use toothpick mode to get to recovery. will help to backup your android system. 

recovery.imgFetching info...

Red2

Red2

Posted
Posted
  On 1/27/2020 at 3:38 PM, K200_Noob said:

It's a K200 without a revision. Try burning image to SD once more and try again. Possibly an issue with SD card. I will send  you a TWRP later today which you could use to backup your firmware and we can extract your DTB file. 

 

UPDATE: the attached is the TWRP recovery for k200 boards. you need to put it on sdcard and use toothpick mode to get to recovery. will help to backup your android system. 

recovery.img 10.56 MB · 1 download

Expand  

Tried using your image but box didn't let me pick any of the options for some reason.

 

I did use trwp and extracted my boot.img but how do I get the dtb out of it. seems the python script you posted earlier doesn't work on windows?

boot.imgFetching info...

Junoxe

Junoxe

Posted
Posted

OK. I gave up.

None of dtb files forces Wetek Core to upgrade. Toothpick method ALWAYS prowides to recovery mode in which i get:

""E: footer is wrong
E: signature verification failed
Installation aborted"

 

So, may be there is an good way, but i didnt find.

Thanx for support and patience.

 

P.S.

The last chance is i didnt  made activation universal multi boot properly. There is no exact instruction about it. Links follows to main freaktab forum site or to posts which do the same.

Can anyone put simple written instruction with link to just the file/script?

 

Thx in advance

Red2

Red2

Posted
Posted
  On 1/31/2020 at 1:54 AM, K200_Noob said:

Excellent. You have the proper fw_env.config? 

 

try running fw_printenv...

Expand  

 

Doesn’t work. 

 

Red@vegas812:~$ fw_printenv
Cannot open /dev/nand_env: No such file or directory
Red@vegas812:~$ sudo fw_printenv
Cannot parse config file '/etc/fw_env.config': Invalid argument
 

What is fw_env?

K200_Noob

K200_Noob

Posted
Posted
  On 2/1/2020 at 7:55 PM, Red2 said:

 

Doesn’t work. 

 

Red@vegas812:~$ fw_printenv
Cannot open /dev/nand_env: No such file or directory
Red@vegas812:~$ sudo fw_printenv
Cannot parse config file '/etc/fw_env.config': Invalid argument
 

What is fw_env?

Expand  

 

Its the uboot environmental variables that controls the fw settings. this will be needed if you want to install it to your internal memory. The best experience is when it runs from internal memory. its awesome. since you have the TWRP backup you can always restore android.

 

To fix that need to paste "lsblk" block information from running armbian. From your android system backup in the /etc folder you will need to get the fw_env.config file.

vvenz

vvenz

Posted
Posted (edited)

My box is s812 MXIII 4K Gigabit, which should be compatible with default meson8m2-mxiii-plus.dtb specified in uEnv.ini in nearly all images from here https://yadi.sk/d/wc2jqGsHuKy48/Armbian

 

Unfortunately, only images with 3.10.108 kernel work for me. The most recent image from greatly respected 

@balbes150

Armbian_19.11.5_Aml-s812_buster_current_5.5.0-rc6_20200113.img

does not want to boot. Here is the UART log:

  Reveal hidden contents

 

Actually, all i need is headless debian server on 5.x kernel with ethernet access only. No hdmi support, no WiFi, no BT, no IR port etc.
Thanks in advance.

Edited by vvenz
balbes150

balbes150

Posted
Posted

Checked the launch of the image 20.05 on the MXIII Plus (s812), the system starts and works normally with a wired network and USB. HDMI doesn't work, but you can manage it via UART or SSH.

RaptorSDS

RaptorSDS

Posted
Posted

i have tested your 20.05 image

1 run with menson_m8s.dtb its stop(5min waited) at flush journel request by PID 1

2 run with menson_m8s.dtb its stop at GPIO23 request loop and CPU 1,2,3 shutdown and starting loop

3 run with menson_mxplusiii.dtb root login , but no wifi modules

4 run  with menson_m8s.dtb now also root login!!! thanks super work

please, please can you at the RTL8723bs modules for the few that have this Realtek chip , i did not want use a usb wlan stick because i need both ports

 

is there a different between both dtb files ?

godfatheroo7

godfatheroo7

Posted
Posted

Hi,

 

i'm trying to use the latest 20.05 image with my minix neo X8-h.

 

I copied the meson-minix dtb file to the root and renamed it to dtb.img.

 

Unfortunately nothing really happens other than the bootsplash from amlogic.

 

Any clues? Am i using the right DTB file? Starting with o without the reset button does not make a difference... Also the 19-series did not come to life.

 

Lakka and alexelec are working on it.. :wacko:

RaptorSDS

RaptorSDS

Posted
Posted
  On 3/2/2020 at 7:02 AM, godfatheroo7 said:

Hi,

 

i'm trying to use the latest 20.05 image with my minix neo X8-h.

 

I copied the meson-minix dtb file to the root and renamed it to dtb.img.

 

Unfortunately nothing really happens other than the bootsplash from amlogic.

 

Any clues? Am i using the right DTB file? Starting with o without the reset button does not make a difference... Also the 19-series did not come to life.

 

Lakka and alexelec are working on it.. :wacko:

Expand  

yes after 5.7 image you do not need to copy the dtb file and do not rename it ; only edit UEnv.ini first line name and location of the dtb file

godfatheroo7

godfatheroo7

Posted
Posted
  On 3/2/2020 at 1:11 PM, RaptorSDS said:

yes after 5.7 image you do not need to copy the dtb file and do not rename it ; only edit UEnv.ini first line name and location of the dtb file

Expand  

Clear, i tried that as well... but which dtb file is used for the minix x8-h ? Because i tried a few without success.

godfatheroo7

godfatheroo7

Posted
Posted
  On 3/2/2020 at 6:22 PM, godfatheroo7 said:

Clear, i tried that as well... but which dtb file is used for the minix x8-h ? Because i tried a few without success.

Expand  

Only when i try the M8S file, the box passes the "amlogic" boot-splash but the screen remains black...

I did read about " HDMI not working"..... is that what's going on?

godfatheroo7

godfatheroo7

Posted
Posted

Maybe i should head back and install the default android on the box again? I did manage to find a 5.1.1 a fews years back, i remember it did upgrade some u-boot parameters compared to the 4.4 version.

 

 

Found my post from years ago about that 5.1.1 rom... :

https://forum.freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s802/minix/firmware-roms-tools-ab/635870-minix-neo-x8-h-5-1-1-lollipop

 

After that i installed some others, like alexelec and lakka.

RaptorSDS

RaptorSDS

Posted
Posted

Yes this version is without HDMI , you have to use Serial Terminal or Headless Network Terminal ; i think maybe the menson8-minix-neo-x8.dtb is maybe the one for your box; i have normally the M8S clone but the MXIII-plus also work for me

godfatheroo7

godfatheroo7

Posted
Posted

I don't get it, i tried all the MESON-DTB-files.. not one is working.

 

No dhcp request on the server either.

 

Should i go back to stock firmware? Lakka and LE are working on it.

RaptorSDS

RaptorSDS

Posted
Posted
  On 3/8/2020 at 7:39 PM, godfatheroo7 said:

I don't get it, i tried all the MESON-DTB-files.. not one is working.

 

No dhcp request on the server either.

 

Should i go back to stock firmware? Lakka and LE are working on it.

Expand  

i think this image has a static ip 192.168.0.100 or 192.168.1.100 maybe a crossover eth connect with a another pc help

godfatheroo7

godfatheroo7

Posted
Posted

I got back to stock firmware (thus the old U-boot).

 

Opened the thing and attached tx/rx/gnd@ 115200.

 

Got the bootprocess till:

 

[    5.194954] can: broadcast manager protocol (rev 20170425 t)
[    5.200598] can: netlink gateway (rev 20190810) max_hops=1
[    5.206257] Key type dns_resolver registered
[    5.210497] ThumbEE CPU extension supported.
[    5.214548] Registering SWP/SWPB emulation handler
[    5.219432] Loading compiled-in X.509 certificates
[    5.225246] Btrfs loaded, crc32c=crc32c-generic
[    5.237442] hctosys: unable to open rtc device (rtc0)
[    5.238655] Freeing unused kernel memory: 2048K
[    5.279706] Run /init as init process
[    5.280612] process '/usr/bin/sh' started with executable stack
 

Then it stops...

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept