K200_Noob
-
Posts
32 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by K200_Noob
-
-
22 hours ago, Red2 said:
Thanks Linux running.
Excellent. You have the proper fw_env.config?
try running fw_printenv...
-
6 minutes ago, K200_Noob said:
this one has been reconverted
-
7 minutes ago, Red2 said:
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?
here you go....Red2-dtb.zip
-
23 hours ago, Red2 said:
Don’t know how to get screen shots off the box but here are photos.
thinks that’s the relevant screens. Doesn’t show a revision
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.
-
4 hours ago, 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.
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
-
Hello,
Anyone know if this works with s905X3 with HW video decoder. Planning on getting a box to convert to Armbian running on emmc?
appreciate any input please..
-
7 hours ago, 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.
find your box recovery button. use toothpick mode to activate. using update method does not always work.
watch this:
-
2 hours ago, Red2 said:
Closer. Goes through boot up screen. But gets stuck at.
U 18.04 LTS vegas812 tty1
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
-
4 hours ago, Red2 said:
Running last update for the box, Kitkat 4.4.2 tried all the .dtb s that come with the images I’ve tried.
Do not have a stock boot image.
Try this. Rename it it to dtb.img and put it in the boot partition of 5.4.4
-
7 hours ago, Junoxe said:
So i copied file You kindly prepared m8m2_n200C_2G.dtb to root folder. Flashed SD card with Armbian_5.44_S812_Debian_stretch_3.10.108_xfce_20180521.img and it didnt worked. Or during booting i got in half noisy screen and i got
"E: footer is wrong
E: signature verification failed
Installation aborted"in recovery mode.
I tried with standard aml_autoscript and aml_autoscript.zip and with v05.
Or there is something more i should do which i missed?
Ill try with 5.77 also.
Not working. Also after trying to run 5.77 Wetek lost his dual boot. It means if SD card is inserted there is no info like "Press power button to boot from SD card." So after restore to factory settings now there is info about "Press power button..." but it again doesnt work. So I need to do prepare install CD card with LE. Ill hope it will work.
I am sorry for your troubles.. when you have it restored, take a look at page 11 of this post and do a search for the word wetek...
chataigne73
April 5, 2018
Hello balbes150
I'm trying to use your armbian s812 builds on my device : it's a Wetek Core, with Libreelec installed on nand.
From what I understand, I'm in a particular case since my box already supports booting from sdcard, but it doesn't work for your builds (sdcard not seen as bootable by my box).
So, I applied your autoscript to activate universal multiboot.
Now my box detect your builds on sdcard (not on usb), boot on it but is stuck (with screen no signal) with every dtbs I tried.
I think the wetek proprietary multiboot script is in conflict with your.
Here is my fw_printenv ... thank you if you can help me :
Reveal hidden contents
Edit : I manage to boot by using dtb and uimage of libreelec for my device (3.10.99)
Balbes : can you repost old 3.10.99 debian or ubuntu links ? they are no more on your yandex
-
3 minutes ago, Junoxe said:
There are 4 files. All should be copied to root folder after flashing SD card?
Thx a lot!
just use the dtb that was not in the zip folder as your dtb. it has be converted. the zip is the original extract that contains the kernel file. as a backup you can keep.
-
44 minutes ago, Junoxe said:
From that conversation (posts 100-103) below can be concluded that s812H can be on n200c board:
So i try and copy meson8m2_n200C_2G.dtb to root folder and change to dtb.img, copy v05 aml_autoscript and aml_autoscript.zip files and will see.
if you are going to change it to dtb.img use the 5.44 img to start with.
-
53 minutes ago, Junoxe said:
Im not sure if understand well.
At last i run dual boot on Wetek Core and now i can use WeOS (Android 5.1.1) on NAND and LE on SDcard. So looks like dual boot working. Or You mean something different.
Still i dont know how to get know which meson8m2 i should use.
I tried some of them and stuck on "noisy: half screen during boot. Will test rest of them.
I have suspisions:
or WeOS is blocked by vendor in some way
or Wetek Core should has own dtb file to run.
Thank You once again for Your support.
attached are the files i extracted from the boot img of your device.
-
5 hours ago, Junoxe said:
Sorry for late answer as i couldnt install back LE on my box. Now i can log in ssh to check if its meson8m2_n200 or n200c or else.
So lsblk is not working so i used df - cmd.
I got this:
LibreELEC:~ # df -h Filesystem Size Used Available Use% Mounted on devtmpfs 744.0M 112.6M 631.4M 15% /dev /dev/mmcblk0p1 511.7M 121.9M 389.9M 24% /flash /dev/mmcblk0p2 1.3G 11.2M 1.3G 1% /storage /dev/loop0 113.0M 113.0M 0 100% / tmpfs 746.0M 0 746.0M 0% /dev/shm tmpfs 746.0M 8.3M 737.6M 1% /run tmpfs 746.0M 0 746.0M 0% /sys/fs/cgroup tmpfs 746.0M 2.6M 743.4M 0% /var tmpfs 746.0M 0 746.0M 0% /tmp LibreELEC:~ #fw_printenv doesnt work as well.
LibreELEC:~ # fw_printenv -sh: fw_printenv: not found LibreELEC:~ #So, what is next step?
Ok since that is the case, we will need to follow @balbes150 instructions to get it activated.
Let me share with you want i was referring to first;
Below are the ones from my device;
notice that the mtdblock0 is the bootloader and the mtdblock1 is uboot env. I am reading this while booted from internal memory so it does not have a label but did when i booted from the sd card,
using;
/dev/system as my boot partition
/dev/data as my root
/dev/cache as my cache
I was looking at post which i wanted to adopt for my box to switch the partitions around and boot into LE or linux using below...its a work in progress;
Looking at the link @balbes150 posted, you will need to activate using sd card, I may have look some more into it. I would however suggest reading through that forum. I could not find the aml_autoscript. I will try to ping @balbes150 for help.
edit: tried to ping him but says he does not receive msgs. perhaps inbox is full.
Check out this post #317;
-
1 hour ago, Junoxe said:
I read from other sources that S812H is meson8m2. It has 2 GB and 1 Gbit. But none of meson8m2 files working.
And ill try to cat/fw_printenv.
Thx.
we can always extract it from your android firmware, the one for your device.
attached is an example.
is it meson8m2_n200 or n200c?
-
Just now, Junoxe said:
Wait, i thought i should cat uboot enviroment as im booted in Android. It doesnt matter im booted in LE or Android?
Thx for Your support.
android does not allow fw_print env. you can do both (cat and fw_printenv from LE). it wont change anithing to the uboot env. we just explore
-
I keep hearing which DTB would work with which image when it should be 1 DTB for you box for all images;
A device tree is a tree data structure with nodes that describe the physical devices in a system.
Helpful Info:
https://elinux.org/images/f/f9/Petazzoni-device-tree-dummies_0.pdf
-
5 minutes ago, Junoxe said:
Hi, as i can log via aah to LE im not sure if weteks stock firmware allows me. Ill check.
I can use cat cmd but what does it mean: uboot environment?
Hey, you seem to be on the right track and @balbes150 has the information for the wetek. and yes it would seem you have the multiboot. since i was not familiar with it i wanted to see how the kernel was being loaded to help you.
if you have ssh then do "lsblk" from the commandline and you will see which mtd partition has the uenv or uboot env. mine is /dev/mtdblock1.
i like to know what is going on behind the scenes and thats how i learn and helps me fix issues. Oh but wait since you have LE, you should be able to run this command which is more Human Readable "fw_printenv"
If you want to learn truely friend...this is where the fun begins!!!!
The real satisfaction in getting something working is knowing how you did it
-
26 minutes ago, Red2 said:
S8xxx_ArchLinux_20180331_4.16-rc6.img.xz
S812_ArchLinux_20170924_3_10_99.img.xz
Armbian_19.11.5_Aml-s812_buster_current_5.5.0-rc6_20200113.img.xz
Armbian_19.11.5_Aml-s812_bionic_current_5.5.0-rc6_20200113.img.xzand a couple from Armbian 5.44_S812...... both debian and Ubuntu
plus LibreELEC-S802.MXIII-1G.arm-7.0.2-2-devel.img.gz,
since it seemed to be proper boxmost go to the google.tv screen go black for a bit then get stuck in pixelated screen (for lack of a better term), some just seem to go to the google.tv splash screen then wait longer than usual before booting back to MBox and android
Libreelec actually gets to a text screen
... press anykey or wait 120 sec to abort ...
wait the 2 mins and then get something about READ ONLY file system blah blah blah this box is permanently ... something in the order of bricked, can't recall exact verbage, but if I reboot boots back into mbox with no issue
sounds like a .dtb issue. What dtb file are you using?
what android version is it running? if you have your stock boot.img use this script
command from same folder as your boot.img - ./extract-dtb.py boot.img it will create a folder with all your dtb files.
-
5 hours ago, Junoxe said:
Thank You for answer.
As i found linux of Wetek Core is Android 5.1.1 with kernel 3.10.33.
As i said about linux i meant this Android.
Which of build from this link below (its from @balbes150 post:
https://yadi.sk/d/wc2jqGsHuKy48
Any images of 3.10.108 kernel?
In this link i found also files like this:
firmware-aml-s812_5.73_armhf.debWhat is for?
The Kernel version is at the end right before the date compiled. 3.10.108 - 2019 March 26th.
All the images are compiled by @balbes150
not familiar with your device, but do you have a terminal and can you "cat" the uboot environment and paste here? if LE was started from SD card then using the aml_autoscript should get you going. if you fail with 5.44 give 5.77 a try due to the output mode.
i believe "firmware-aml-s812_5.73_armhf.deb" was a deb package was for the image 5.73 to be installed for missing binaries if not mistaken.
image 5.77 should have it all in the image file. I personally started with 5.44 to get things kick started...
before you get started, do you have a backup of the ROM or the factory firmware and aware of recovery if things go wrong. I had an SD image of the stock firmware which i could recover my box with? - my recovery image allowed me to recover the bootloader too.
-
7 hours ago, Junoxe said:
I thought it will be a bit simple. It will work or not.
Well, im so lame and n00b that i can't ask a proper question propably. So may be ill try to describe sitiation.
I have S812H (Wetek Core) box. LE is working smooth in its last supported version. Onboard system is kind of linux which is unable to log to google anymore. So i thought about exchange stock linux with i.e. armbian.Dualboot is enabled becuase i can boot LE or system with a remote button during start of box. Thats why i told is enabled. Propably i was wrong.
Whatever You wrote about such files like uboot env, kernels or scripts its too much for me.
May be You can simple tell if its possible to run armbian on my old box in a more or less simple way. For sure i can log via ssh or something like this. For sure i've never compiled anything.
from one noob to the other, i dont see why not. its similar to the 812 with an addition of Dolby DTS from what i read. is it rooted? when you say kind of linux do you mean android 5.1? also it is true LE or are you referring to Kodi?
-
4 hours ago, Red2 said:
I have an old tv box with S802
MXIII 4k 1g8g netxeon m82
Just wondering what the latest Linux image I can get it to run and where would I find an image file. Most I find seem to only be for 2g boxes or I'm misinterpreting the info, which isn't that unlikely. Everything I have tried has failed so it would be nice to know if someone else got Linux install on one and which version
Thank in advance
what have you tried so far?
-
5 hours ago, menthorul said:
So.To activate multi boot what do i have to do?
Just to format any usb stick in fat32 and copy to root of usb the aml scripts?
Or to use make uboot?
Sent from my SM-A530F using Tapatalk
Much simpler would be...Every Armbian image for the s802/s812 comes with it in the boot partition. When you burn the *.img to the SD card, turn on your box with the recovery button pressed in using the toothpick method. you do have a recovery button? the boot logo flashes once then let go of the button and should flash once more on its own. you will hear a faint piezo tone from the box when it flashes..but those are details. just watch for the logo flashing off and back on. and you're set.
-
On 1/7/2020 at 12:48 PM, menthorul said:
Hi there,
Minix Neo X8-h plus any tutorial or similar cpu?
I think it's aprox like s802 or s812... not sure
05-31-2017, 09:50
Updated images Armbian 20170531. Changes to scripts activate the multi-boot and run system from external media. In the new version of the scripts allow to start the system from any USB socket (if the is connected other USB media). Back support "nodm", now in the images is used in common with the main branch Armbian authorization system. If you want you can install the package "lightdm" in version Mate-that-be to have a graphical authentication when you log into the system (just don't forget together with the installation of lightdm, remove the nodm package, otherwise they will interfere with each other). Other changes see the description of changes to main branch Armbian (replacement browser on Chromium, etc.).
New scripts activate the multi-boot and system start-up can be found here. You can download them and use for old images. To reactivate the multi-boot again.
https://yadi.sk/d/cEPIULGW3Jgpee
https://yadi.sk/d/QCGU0PIv3G5kEa
New script to activate the multi-boot on the Minix models H8x and H8x plus.
https://yadi.sk/d/BU_pyfHW3JgpEP
Armbian for Amlogic S805 and S802/S812
in Amlogic CPU Boxes
Posted
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.