Jump to content

Tucano2000

Members
  • Posts

    11
  • Joined

  • Last visited

Posts posted by Tucano2000

  1. Quote

    I mean: did you try again, after bricking the board, to run the multitool from sdcard?

     

    No, I got Multitool backup files, dtb, dts, Android Tool Image before bricking when original Android yet was installed. This links are with this files.

    Multitool don't work more after bricking.  Now here show red led, no more blue led blinking and no image to TV/Monitor (hdmi) when power on tv box using Multitool on SD card.

     

    Quote

    You need a serial adapter (USB-to-TTL or RS-232-to-TLL) for that, boards usually have debug serial pads in rows of 3 of 4 holes where the serial adapter wires can be soldered to send and receive characters.

    Looking at the board photos, I think the four vertical pads in the left-bottom corner of the first photo are probably the serial pads. Commonly they are GND, Tx, Rx and 3v3, but the order changes. 3v3 must not be used, but if you connect the adapter GND to the GND of the board, Rx of the adapter to Tx of the board and Tx of the adapter to Rx of the board you can send and receive message on your computer. This is pretty a must have.

     

    It must be a few days before I get one. In the meantime, I'm going to look for it and maybe someone got it and posted it somewhere how to force maskroom mode. Thanks.

     

  2. Quote

    Did you try to put the multitool on a sdcard and try to boot it? If the bootloader you installed on eMMC is corrupted, the SoC will try to boot from sdcard (but not USB) and the multitool will allow you to recover or install armbian again.

     

    Yes. I did here on this link a Multitool backup image and resend Android Tool image again but I don't know if it work.  The mmcblk2boot files I get with dd command.  The dtb and dts files (don't works here) I got using Termux on Android. I don't know if this will interest you.

     

     

     

    Quote

    If the multitool does not boot, I'm afraid your only option is finding the eMMC clock pin and shorting it to ground to force maskrom mode. I have no such board, so I have no experience with that unfortunately.

     

    I soldered a wire to the ground and placed a 1k ohm resistor on the other end to look for the eMMC clock pin. I don't know if I should use a lower value to be able to find it. But my concern is to cause a short and burn some port on the chip. I don't know what the technique is to look for

     

     

     

    Quote

    If you have a serial adapter it may be worthy connecting it to understand what's going on.

     

     

     I don't know this method. You could put a link here showing how I should proceed to achieve this. 

     

     

     

    Edit: Include comment about mmcblk2boot, dtb and dts files.

     

  3. Quote

    Yes it is a known problem of lightdm. A couple of posts above @kruzer suggested to do an upgrade of the package. If you are able to run apt update && apt upgrade this issue will probably be fixed.

    Thanks for this tip !!!

    Quote

    Anyway I'm very glad the image works for you. If you have the chance to post some photos of the board and have a link to the original firmware would be great for better support.

    Don't forget ro run rk3318-config too.

     

    I have the firmware image here that I extract with the Android Tool:

     

    After that, my device bricked yesterday, when I tried to put the RK3328 firmware. :( ... I did a stupid method !!!

     

    Now I can't get it to be recognized by USB, even if I press the button with the toothpick inside the AV connector.

     

    I took some pictures of the pcb and as it only has a badge chip, I can't do the EMMC pin to force the Maskroom mode. I didn't find anyone who did this for this box. I'm a little lost.

     

     

     

    b4UKU3n.jpg

     

    wQ28M8E.jpg

     

    Pnd2CP1.png

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines