Jump to content

Lambert

Members
  • Posts

    23
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Lambert reacted to jock in RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND   
    Glad to read that. Strange you had to write the trust.img and uboot.mg back onto the sdcard, they are already installed in the same position you burned again. Strange, I will check the scripts but thanks for reporting!
     
    Ok, an amount of sectors of the eMMC are gone. I suggest you to erase it and leave it alone.
    Once the eMMC is erased, you may try to burn the armbian image I gave you on the sdcard, it should boot directly.
  2. Like
    Lambert got a reaction from jock in RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND   
    I was run Multitool at last!
    It could only start this way:
    1. Rufus+Multitool.img
    2. dd if=trust.img of=/dev/sdb seek=24576
    3. dd if=uboot.img of=/dev/sdb seek=16384
     

  3. Like
    Lambert reacted to jock in RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND   
    Odd.
    I read the log in the post above and the line SdmmcInit=0 NOT PRESENT says that the sdcard is not detected at all.
    Can't say anything more at the moment, you need to use the maskrom mode if you want to proceed further.
  4. Like
    Lambert reacted to caruso in Armbian for TV box rk3328   
    Hi everyone,
     
    I would like to share my work which leads to boot from sdcard device based on RK3318 to desktop armbian.
     
    I've was using Armbian_19.11.3_Rk3328-tv_eoan_legacy_4.4.154_desktop_20191126.img and end up with booting to desktop
    What doesn't work for me:
    onboard wifi (usb dongle works, old tp-link tl-wn725N) onboard bluetooth My box is same as picture below:

    https://androidpctv.com/review-h96-max-opinion/
     
    I've burned image with rufus on windows and my first boot trial finished with boot hang up:
     

     
    I've solved this issue by invoking following code where /dev/mmcblk0 is sdcard device in linux, and trust.img was extracted from rk3318_9.0_hcy_20191114_v002 updage image.
     
    dd if=trust.img of=/dev/mmcblk0 seek=24576 sync After that boot sequence went further. I'm not sure but I guess that debug vs release version of bl31 might be problem here.
     

     
    Also, I've used rk3318-t9.dtb file prepared based on rk3328-t9.dtb posted in this thread, with removing cpu freqencies > 1.1GHz, as box was unstable with such high frequencies.
     
    I didn't find option here to attach file so temporaraly you can find my modified file here rk3318-t9.dtb and other useful files here:
    https://freeshell.de/~tiloc/armbian/
     
    I hope it will be useful for somebody
     
     
     
  5. Like
    Lambert reacted to jock in RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND   
    You may try this very work in progress build effort made by @fabiobassa, @hexdump and me.
     
    Burn it on a sdcard and try, but your mileage may vary
  6. Like
    Lambert got a reaction from Werner in RK3318 device (Magicsee N5 Nova 4g/64g) with dead NAND   
    That's it! My fault. Thanx!
    But I can't edit it no longer.
    Thanx a lot for help!
    I'll try yours image definitely soon! There is only one common card left.
    Until I was waiting for an answer - did something: figured out RX & TX.
    In order:
    1. I burn bionic image (Armbian_20.07_Rk3328-tv_bionic_current_5.7.8.img) first. But SDcard even wasn't found I guess:
    2. Then I burn "trust.img" (by: "dd if=trust.img of=/dev/sdb seek=24576") and put "rk3318-t9.dtb"(from here) in the root of SDcard. I got "trust.img" from stock Android Firmware. The log has become much longer this time:
    what is more password does it required? "1234" mismatch.
    ---
    How can I post more than one per day? It's too slow!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines