Bootloader B860h V5
Mariu Carlton
No Idea about the Vim2. But I doubt it will be as easy to get LE started as just flashing a SD card / USB Stick and then simply holding down the box's power button for 6 seconds or longer to start LE installation.
If the ZTE box is a Google Certified Device running Android TV OS, which then also includes proper Chromecasting capabilities. It is very likely the device will have to have a locked bootloader to get Google certified in the very first place.
I have a Tanix TX92 box running LE 8.2.4.1 and occasionally I will receive a pink screen at boot. If I power cycle the Tanix box it will be fine. Anyone else experience this issue? This is with a Samsung JS8500 TV.
I got two adapters - One 5.5mm and other 3.5mm. Unfortunately none of them would fit. 5.5mm too big and 3.5mm is too small. Am I missing something here? I tried to measure the size of hole and it seems more like 4mm. I have attached a photo. Can someone take a look and advise what adapter I should to buy? FYI. I need a power supply for Mecool M8S Pro L with a US plug. If you have a similar box, can you please tell me the adapter size? Thank you.
Then you have to deal with thermal heat control because you are really going to be pushing the CPU's hard so the S912 you choose better have a good heat sink or it will very likely overheat with extended 1080p Anime usage.
So just to be clear. This eMMC (with the included microSD adapter) paired with this Card reader is all I need for flashing the image, correct?
I'm sorry if being a little slow about this, but I have zero experience with eMMC.
There is no way to video hardware decode the "scene" video compression used with Anime releases. You have to use CPU software decoding. Only the S912's have enough raw CPU power to do that on AMLogic hardware.
The Bootloader is a piece of software that is executed every time the hardware device is powered up. It is executable machine code and thus ARCH-specific. It's quite heavily device-specific because its main task is to initialize all the low-level hardware details. The bootloader can be contained on a separate EEPROM (very seldom) or directly on flash storage (most common).
Being a piece of software, the bootloader is considered part of the firmware, but the bootloader is not part of OpenWrt!
Only on seldom occasions a change of the bootloader settings or the bootloader code is necessary to allow for booting/installing OpenWrt
There are a number of bootloaders under diverse software licenses
The bootloader's main function is to initialize the hardware, pass an abstraction of the initialized hardware, a hardware description, to and execute the Kernel. (A very nice technical example can be seen here or see a suggestion until finding a better example: here and here) After that the bootloader is done and not needed in memory any longer. Most bootloaders offer additional functions.
It's not. A bootloader is not required to boot Linux. The use of one (or several) bootloaders in a row to chainload (or bootstrap) a Kernel is not a categorical necessity, it is merely a very crafty method to start an operating system. The main advantage for OpenWrt is, that the existence of a bootloader offers users and developers additional possibilities to debrick a device.
The bootloader can be more or less sophisticated, and offer none to many additional functions. In many situations additional functions would give the user a huge advantage, so most bootloaders offer them, such as:
gini bang, itu kl sy nyalain cuma stuck di tulisan android, trus kl sy pake usb ttl, itu gak kebaca memory internalnya, kl sy coba masuk ke directory sdcard, itu ada error no such file or directory, padahal ada di list directory kl kita pake perintah ls.
Trus usb juga keduanya gak ada yg kebaca kl dicolok usb, dan mau coba flashing bingung krn driver gak kebaca di win10, di linux juga gk kebaca, satu2nya akses yg bisa membaca hanya pake usb ttl, kl usb male to male gk ada sama sekali kedetect, jd gk bisa flashing pake sp flash tool soalnya gak kedetect stb nya, kira2 gmn solusinya bang, makasih banyak infonya
ini file bawaan orisinil nya yak agan aponk? klo cuman boot.img, recovery.img, system.img doangan tanpa bootloader.img n sodar2 ny, ap bisa dflash via perintah update tool? usb to usb? tararengkiyu,,. ?
coba pakai komputer aja bang, yg win 7 atau 8. memang kalo b860h belum ada firmware official, kalaupun mencoba burn pakai sdcard coba ikutin susunan file yg ada di folder cache/upgrade. selanjutnya coba booting via sdcard.
masalahnya itu saya gak tau dimana ambil filenya bang, soalnya sy gak punya dan saya juga gak tau susunannya gmn, kl abang bisa share saya sangat berterima kasih, td sy coba boot dari sdcard, setelah sy coba udh gak muncul2 apa2 lagi di layar, gak ada signal katanya, padahal udh nyala stb nya, td sblm sy coba boot dr sdcard masih muncul tulisan android cuma stuck di st, skrg udh gak sama sekali, pke putty pun udh titik2 semua yg muncul, jd smkin bingung gmn atasinya hehe
Sorry gan nge-UP post lama. kalo mau unbrick bootloader B860H pakai file yang mana ya? di putty cuma muncul titik titik pake aml-* dari blog lain. saya bikin bootable pakai Linux (dd if=*.img of=/dev/sdX) karena gaada os windows di laptop. di post orang banyak yg berhasil, mungkin karena saya pakai file HG680P jadi beda filenya. disini kalo mau bikin bootable filenya yang mana ya?
Researched and developed by Team CoreELEC by @anon88919003, @Portisch and @vpeter, we proudly present the universal Amlogic SDIO debug board, the SDIO debug board will give you easy access to the UART interface without needing to open your device and/or without having to modify anything.
With dmesg you are limited to retrieving debug logs from the Linux kernel only, if you need logs from bootloader (u-boot) for example if you have a bricked device or a wake up issue from power off/suspend then this adaptor can be easily used to identify issues.
The 4 pin header is a TTL UART interface, you can use any standard TTL/USB UART adaptor to connect the adaptor to your host computer. The UART connection used is 8N1, 115200bps: 8 bit, parity none, 1 stop bit, baud rate 115200bps.
The Amlogic SDIO UART do have issues with fast character transfer. So a delay after each single character sent will be needed. Here is a modified version of Putty 0.74 for Windows which include a delay of 1 millisecond after each single character sent.
Thank you for the tip. For the first pcs I will solder it by reflow by myself as I have all the equipment.
Maybe when the stock needs to be increased I will take a look as it would need a bigger number of assembled boards ordered to get a good price.
It is recommended to boot Batocera off of a USB/other external drive and to use your BIOS boot selection menu to switch between Batocera and other operating systems that may already be on other drives. You can still use drives with other operating systems on them to host your userdata such as ROMs, BIOS files, saves, etc. This is the far simpler option to do instead of what you'll have to do if you only want to do everything from one drive. However, some people prefer to have Batocera directly installed on the main hard drive alongside another pre-existing OSes, this page is for that.
Before attempting any of this, make a backup of your data. There is a chance that the following actions (shrinking partitions, replacing boot loaders, etc.) can render the storage devices inoperable.
Ordinarily, Batocera utilizes Syslinux to boot, which is configured to only boot Batocera. Thus, for most dual boot setups we will be utilizing GRUB to show a boot selection menu after BIOS has loaded instead.
In case you install Batocera on your hard-drive, you may want to rename the BATOCERA partition to something unique like BATOPC. If you do, edit the grub.cfg file below to have label=BATOPC instead of label=BATOCERA. This allows you to still boot using Batocera installed on a USB without worry that the hard-drive will always take priority due to sharing the same label.
Download and install grub2win. It may come up as a false positive on anti-virus software, we are going to be overiding the boot manager which could potentially prevent Windows from booting so maybe they are right in that regard. Either way, just let it through to continue.
Pleillear keeps an updated copy of the file at this Google Drive link, so check that if this page hasn't been updated for a while. Note that the file at this Google Drive link is not up to date for v39, and would need set efibootmgr=/EFI/BOOT/bootx64.efi changed to set efibootmgr=/EFI/batocera/bootx64.efi
Although Windows can be hostile towards other operating systems (erasing their bootloaders on an update, clearing the master boot record without warning, etc.), Macs can be even more hostile. Keep this in mind and definitely have a secure method of restoring a backup when playing with the Mac's bootloader.
Install rEFInd Boot Manager and check that the system is still booting. Batocera might be automatically detected (but with a generic name); if so lucky you! Otherwise, Batocera can be added manually by adding the following to the refind.conf file.
Technically, this isn't really dual-booting, but booting a static image already loaded onto your drive's filesystem as its own mounted filesystem. It can ease the process of updating the image, however this is probably unnecessary as Batocera itself has its own updating tool. Nonetheless it could be useful for machines that otherwise don't have an internet connection and have to rely on another one to update or machines that absolutely refuse to boot via conventional manners.
c80f0f1006