TheLinuxBug

Members
  • Content Count

    38
  • Joined

  • Last visited

About TheLinuxBug

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    https://h3droid.com

Profile Information

  • Gender
    Male
  • Location
    United States of America

Recent Profile Visitors

725 profile views
  1. TheLinuxBug

    Sunvell H3 2GB RAM + 16GB ROM TV Box

    Assuming you are not talking about the OLD Sunvell R69 model with 1gb ram, 8gb eMMc and you are talking about the newest version with 2GB of ram: You must have gotten lucky, mine won't boot normal images with regular settings, seems I got one with shitty ram modules that are way under-clocked like some others have. Additionally, the board has NAND not eMMc, this is why you can't see it and you won't be able to. There is no support for NAND in Linux, there is only a proprietary FTL driver implementation that is licensed which Android manufacturers use, such as in this case. So while you can boot other Linux images and such off SDcard you won't be able to use the NAND except with their specific image, sadly. Cheers!
  2. TheLinuxBug

    Sunvell H3 2GB RAM + 16GB ROM TV Box

    To note, if you check that Youtube video there seem to be a lot of people in the comments there observing the same issue. They state they also have this exact same board and it won't boot at all either. I am guessing bad quality memory, like in the last box, except in the last box it simply prevented any good use of 1080p cause the DRAM wasn't fast enough. In this version is seems it causes the need to likely set DRAM super low for it to boot. Will probably take using uboot/fex for OPi Zero +2 and trying to figure out something usable from that. I really wanted to get H3Droid working with this board for our next release but at this point with the mix of quality / revisions that are possible this may be in vain, because even if I get it working, may not work for others. No going back now though... will just have to keep at it! Cheers!
  3. TheLinuxBug

    Sunvell H3 2GB RAM + 16GB ROM TV Box

    Super odd! They must have made revisions of this board and some are different. I promise you mine will not even boot that Beelink X2 image mention in the video. The ONLY think I have gotten to boot was OPi Zero +2 image and its severely crippled. I will post images of mine below, maybe there is some subtle difference I am missing? So far my link seems limited so I am guessing they made some change mid-run of these, like using sub-standard memory that needs an extremely low DRAM setting to operate. Only thing that seems to make sense as to why all other images won't boot. Will continue to update if I make any progress here. Cheers!
  4. TheLinuxBug

    Sunvell H3 2GB RAM + 16GB ROM TV Box

    @Jani-Matti Thanks for the video, I now understand what you were saying better, the Armbian image for Beelink X2 should supposedly work. I am actually going to test that one now and will report back if I am successful or not. Thanks!
  5. TheLinuxBug

    Sunvell H3 2GB RAM + 16GB ROM TV Box

    Okay, it seems I missed something; supposedly the Orange Pi 0 +2 H3 image does boot on the NEW Sunvell (R69) H3 2Gb Ram, 16GB Rom image (NAND will not work obviously). However, it boots without USB, ethernet, wifi... basically anything but HDMI and UART. So obviously need to get fex figured out but I guess I at least got it booting. Still looking for any suggestions from anyone that has it running well already. Will update as I make more progress... @Matthew Hodgson Please realize there is 2 different R69's now, the old one, yes you could run almost any image and the Beelink X2 image worked, so did H3Droid out of the box. Problem here is, this new box is not the same. It uses NAND storage and it seems has some very specific configurations needed in the fex which are custom (thinking possibly very low DRAM settings or some specific setting in the fex that is only available in the OPi Zero +2 image). It is either you are thinking of that box or you got a different revision as I spent hours trying to get different images booting and the only success I had was the OPi Zero +2 H3 Armbian image and that only works somewhat with most of the peripherals missing. Since I am still working to make it work with H3Droid, at least that is my goal, I welcome any feedback which may help and will be sure to update here as I make progress. Cheers!
  6. TheLinuxBug

    H2: Sunvell R69 Android TV Box (AliExpress)

    You must have some weird SDcards, cause on the old R69 I had no problem booting at anytime from and SDcard. And I did a lot of booting while I was testing H3Droid. So it seems maybe you need to stay away from those no-name brand SDcards. This however has no effect on the new box. I have been testing and am yet to get anything to actually boot. I did notice in the other thread someone mentioned the OPi0+2 uboot seemed to partially load, so may test that later. Cheers!
  7. TheLinuxBug

    H2: Sunvell R69 Android TV Box (AliExpress)

    Well, I have been working on trying to get the new Sunvell (interestingly it is still labeled R69 but not marketed as such) ( it is actually an H3 with 2GB of memory and 16Gb NAND) working... already wishing I hadn't purchased it. First off, NAND sux ass and has nearly no support outside of proprietary drivers for Android, so don't think much will be happening with it. Secondly, while I can see it will boot from SDcard, the U-boot fails much like you have shown. Which I assume means that there is something lacking in the fex that needs toggled, or even worse I have been wondering if they burnt the secure fuse on this so nothing unsigned can be booted. The latter is what I am leaning towards, but have no way yet to tell. Has anyone gotten Armbian yet booting on this new version of the board? Also posted over in a bit earlier which looks to be a post specifically on the board. Cheers!
  8. TheLinuxBug

    Sunvell H3 2GB RAM + 16GB ROM TV Box

    I finally for some stupid reason got one. All I can say is unless you can perform some magic I don't think this is running anything but whats packaged. The fun part, and I don't know if this is some mid-production change, but even if I have UART hooked up, all I can do is watch it boot, I can't interact with it (U-boot). Additionally, it appears that if you have any SDcard in the slot at boot time, it will try to boot but freeze. The from LED light will not come on, it just sits dead with an SDcard in it. Haven't tried to FEL boot, not quite sure directly how to get to FEL, maybe it will read a FEL boot SDcard, not sure. Effectively though, can't boot from SDcard, I am almost convinced its they are using secure boot (burned eFuse?) also, but I can't confirm: https://paste.ee/p/51PcB They outdid them selves this time, a gorgeous piece of trash that is statically set to 1Ghz per core anyways because they can't afford a cooling solution, so really, the H2+ would have been the exact same here pretty much (haven't pried off the heatsink yet to confirm, would take bets its actually an H2+ under there). All you gain here with this version is a headache. No 'usable' eMMc (NAND instead), no way to boot sdcards that I found yet and having access to UART is worthless for u-boot, but you can access console on Android that on the box and you can 'su' to root. It looks like they are using killing cores again as their thermal solution as cores keep being killed left and right... [ 1675.588747] CPU1: shutdown Regardless of the SDcard I try, I get some errors. The following is our default H3droid u-boot and this is the output on UART: U-Boot SPL 2017.07-00494-g19d1f1a-dirty (Nov 17 2018 - 16:17:38) DRAM: 2048 MiB Trying to boot from MMC1 ** First descriptor is NOT a primary desc on 0:1 ** Booting from an Armbian loaded SDcard results in: U-Boot SPL 2017.11-armbian (Jun 11 2018 - 11:58:21) DRAM: 2048 MiB Trying to boot from MMC1 In both cases it Freezes right there, no other information it output and it doesn't boot. It is either lacking a valid matching fex (DT) or there is some magic missing in u-boot. What's more, it won't even boot the generally compatible-with-alll H3 boards u-boot we have for H3Droid based on OPi Plus 2E which almost every other H3 boards I have ever tested will at least post with. Also, the tag on mine looks identical to the one a few posts up so I likely have the same board version. Still not able to get it to boot from SDcard at this time, still trying.. if anyone has any thought, please let me know! Cheers!
  9. TheLinuxBug

    H2: Sunvell R69 Android TV Box (AliExpress)

    Well, it wasn't that weekend, it took me a while but I did eventually make a blog post for it: Sunvell R69 - My adventures with a cheap TV Box Additionally, Sunvell R69 is fully supported by H3Droid but we do suggest the use of a fan for sure! Cheers!
  10. TheLinuxBug

    H2: Sunvell R69 Android TV Box (AliExpress)

    Did you try re-writing H3Droid or Armbian to the SDcard first before trying to boot from it again? It would be odd if it isn't booting SDcard and its bootable. Cheers!
  11. TheLinuxBug

    H2: Sunvell R69 Android TV Box (AliExpress)

    Yeah, its a bug. Just unplug and replug a few times, it will boot from SDcard.. this just happens... cheap implementation where its locked to 1.2volts so u-boot has a tizzy sometimes it seems. By default the unit should always boot from SDcard first, so either your SDcard doesn't have a valid u-boot on it, or you hitting the bug where it causes it to skip MMC cause of that voltage bug. Cheers!
  12. TheLinuxBug

    H2: Sunvell R69 Android TV Box (AliExpress)

    Are you sure its not just doing its normal glitching, I have had cases where when it boots it actually errors and freezes sometimes, if you unplug power and hdmi for a minute, then replug it should boot SDcard. By default it should always try to boot SDcard first.. UART is definitely useful and helps, not trying to discourage you on that, just saying that is probably whats going on here. Cheers!
  13. TheLinuxBug

    H2: Sunvell R69 Android TV Box (AliExpress)

    Actually, it dawned on me the moment i hit reply, there is an easier solution to this. Load H3ii on your SDcard, let it boot and install and boot to H3resc, once in H3resc you can spawn a shell. Once in the shell, now I want you to cd to /mnt/boot and review, you should be able to find the u-boot and fex files in this folder (/mnt/boot/uboot/u-boot-sunxi-with-spl.bin-orangepi_plus2e). Why this is important is, once you have performed the write of the Armbian image as you tried before, once it completes write the correct u-boot back in place (Orange Pi Plus 2E) from the u-boot file you find in /mnt/boot. All you are needing in this case it to replace the u-boot, that will do that for you. You should be able to use the script /mnt/boot/change-uboot (just make sure to manually update the destination so it writes to eMMc which will be mmcblk1 in this case) Cheers!
  14. TheLinuxBug

    H2: Sunvell R69 Android TV Box (AliExpress)

    I understand, what I am trying to say to you is the image you wrote to the eMMc was using old FEX as it effectively write u-boot and fex in that image to eMMc (which lacks what you are needing for eMMc?). You may do better to clone H3Droid over (or write H3ii to the eMMc) and then use H3resc to install Armbian, then once in Armbian you could just remove the Android partitions and increase the size of your Armbian one., etc. Just a thought for you so you don't lose the u-boot and fex that work. Cheers!
  15. TheLinuxBug

    H2: Sunvell R69 Android TV Box (AliExpress)

    That's because when you write the image (Armbian) back over mmcblk1 you overwrote u-boot and fex again (that are in the beginning part of the image your writing to the card). You should instead of doing that, use the options available in H3resc to re-size the SDcard (option #55 in H3resc) and then load Armbian along side (Option #57 in H3resc). If you are using an 16GB SDcard, resize to 7650 I think and then you should have more than enough room to install Armbian along side (it needs about 4GB and that should give you about 8GB). If you have any questions or need help just stop by on irc. Cheers!