Posts by deimos

    Okay. I daily drive linux, so I'll dd it to the card, should that suffice?

    Regarding shorting the EMMC, do we know if there's a standard BGA169 to solder pad mapping?

    If you can't find a suitable IMG, you can try to configure and compile u-boot for your ddr memory type. You could use this log as a configuration basis for gxbb lpddr3 device. If necessary, we could try it together.

    Hi Bumerc,

    Thanks for taking the time to respond - I appreciate it! I'll take a look at the attached link, but yes I would appreciate any assistance in trying to keep this out of becoming e-waste :)

    Thanks for the feedback. Based on your comments + additional research around on different sites it seems that drastic measures have to be taken if I'd like to ever use the device again outside of a doorstop.

    I've decided to use this an a opportunity to refresh my micro soldering skills and attempt to transplant the eMMC to a writer in an attempt to source another image. My follow up question boils down from a partition/uboot perspective is if I was able to source another device/image running close enough hardware it "wouldn't really care", in theory could I dd that image to the bricked eMMC and would it operate again normal? Obviously i'd just be using uboot, and running armbian.

    You have erased (overwritten) u-boot on the internal storage. Android recovery files won't work as there is no u-boot to provide the recovery app, and imaging recovery.img to an SD card won't work as it contains u-boot for emmc, not u-boot for SD/USB.

    Create a USB or SD from https://test.libreelec.tv/12.0/Amlogic/w…etek-hub.img.gz and see if the device boots to LE?

    If yes, download this backup-file and transfer it to /storage over SSH, then run "emmctool w /storage/backup-hub.tar.gz" and it will expand and restore a raw emmc (dd) backup of the original Android OS to the box. You should then be able to boot the LE12 "box" image .. or have another go at ruining things with Armbian, as you like.

    If the device boots but gets stuck at u-boot, you found the issue that resulted in "wetek-hub" (booting upstream u-boot) images being discontinued. The box sees noise on the UART and boots to console. If you have the UART connected you should be able to access the console and run the commands in here: https://github.com/LibreELEC/Libr…_autoscript.src (or one of the other bootscripts in that folder) to boot into LE. If using a USB stick you might need to run "usb start" first.

    Hi chewitt, I seemed to have done the same during an attempt to install Armbian on my S905 based board. I am getting the same eMMC output over UART, hence how I ended up here via a google search. I'm using an MXQ Pro 4K. Any chance you'd be willing to provide assistance?


    I took your image, and modified the boot parition with the respective DTBs for my box. This was the looping output:

    GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:F3;SD:0;READ:0;CHK:0;
    no sdio debug board detected
    TE: 106615

    BL2 Built : 09:01:42, Oct 11 2016.
    gxb g88b04d6 - haixiang.bao@droid05

    set vcck to 1100 mv
    set vddee to 1000 mv
    Board ID = 2
    CPU clk: 1536MHz
    DDR chl: Rank0+1 same @ 912MHz
    PGSR0: 0x81c001ff.Retry...
    DX0GSR2: 0x00030001.Retry...
    DX1GSR2: 0x00030001.Retry...
    DX2GSR2: 0x00030001.Retry...
    DX3GSR2: 0x00030001.Retry...
    PGSR0: 0x81c001ff.Retry...
    DX0GSR2: 0x00030001.Retry...
    DX1GSR2: 0x00030001.Retry...
    DX2GSR2: 0x00030001.Retry...
    DX3GSR2: 0x00030001.Retry...
    PGSR0: 0x81c001ff.Retry...
    DX0GSR2: 0x00030001.Retry...
    DX1GSR2: 0x00030001.Retry...
    DX2GSR2: 0x00030001.Retry...
    DX3GSR2: 0x00030001.Retry...
    PGSR0: 0x81c001ff.Retry...


    Any help would be greatly appreciated, thanks!