Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

NEW - Beelink S82/S82H/M8/MXIII & Tronsmart S89/S89H - Finless 2.1 ROM

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Finless
    replied
    I doubt its the images. Remember I increase the default buffers so this is going to be it. The memory is set aside (allocated) to this buffer increase.

    Bob

    Leave a comment:


  • erica-renee
    replied
    kodi 14. stable release

    Originally posted by londonshore View Post
    Stick with gotham 13.2 xunitytalk isnt compatable for kodi and best addon vdubt25 under xunity repo check it out
    I am Running Both xunity and vdubt25 with Kodi.

    There is a issue with xunity thou... iSTREAM.. will not show content .

    Each time you restart i stream you first have to into xunity xunity maintenance xunity repair and repair.

    Not sure why

    Leave a comment:


  • dibnah
    replied
    Originally posted by londonshore View Post
    There is something up with this rom clean memory over 50 flashed erased twice and still get same results nothing in the background the stock oman rom dont go this high could it be the pics ? On ur rom
    I just tried this myself, Ram usage drops from 51% with this rom to 27% free when I use Oman's official 111k4 rom. I can only guess its what you think is going on here i.e. the images

    Leave a comment:


  • Magnus33
    replied
    Originally posted by sn123py View Post
    Hi,

    I have a Vega Elite S802-H (VEGA S89-H) with Android 4.4.2 (Build 109k4). When i try to run the automatic installation, it boots into Recovery with menu and the background says "Kein Befehl". When i try to install ROM manually from /sdcard, it says, that it cannot mount the blockdevice (see screenshot).[ATTACH=CONFIG]9461[/ATTACH]


    When i try to locate the ROM via update-app (see screenshot)
    [ATTACH=CONFIG]9462[/ATTACH]
    it reboots into recovery, and give the following error:

    [ATTACH=CONFIG]9463[/ATTACH]

    any ideas?

    the sd-card is 8GB, the box is not modified by me.

    thanks,
    macfly.
    Is the sd card formatted fat32 because recovery can't read ntfs.

    Leave a comment:


  • sn123py
    replied
    problems installing ROM

    Hi,

    I have a Vega Elite S802-H (VEGA S89-H) with Android 4.4.2 (Build 109k4). When i try to run the automatic installation, it boots into Recovery with menu and the background says "Kein Befehl". When i try to install ROM manually from /sdcard, it says, that it cannot mount the blockdevice (see screenshot).Click image for larger version

Name:	DSC_0261.jpg
Views:	1
Size:	192.2 KB
ID:	435720


    When i try to locate the ROM via update-app (see screenshot)
    Click image for larger version

Name:	DSC_0264.jpg
Views:	1
Size:	176.6 KB
ID:	435721
    it reboots into recovery, and give the following error:

    Click image for larger version

Name:	DSC_0263.jpg
Views:	1
Size:	195.6 KB
ID:	435722

    any ideas?

    the sd-card is 8GB, the box is not modified by me.

    thanks,
    macfly.

    Leave a comment:


  • Magnus33
    replied
    Originally posted by Finless View Post
    Sdcards over 32gb cannot be formatted fat32. They have to be formatted extfat or NTFS.
    Recovery only supports fat32.

    Bob
    Should have guessed that but i am on xmas turkey overload...lol

    Leave a comment:


  • londonshore
    replied
    NEW - Beelink S82/S82H/M8/MXIII & Tronsmart S89/S89H - Finless 2.1 ROM

    There is something up with this rom clean memory over 50 flashed erased twice and still get same results nothing in the background the stock oman rom dont go this high could it be the pics ? On ur rom
    Attached Files

    Leave a comment:


  • dlangejc
    replied
    NEW - Beelink S82/S82H/M8/MXIII & Tronsmart S89/S89H - Finless 2.1 ROM

    @Finless Thanks for the work on the rom, it works neat and snappy as hell, keep this up and I'll never have to buy another box 😉
    Two issues exists in the 111K4 stock rom; CEC changes language to Chinese even if it's not selected, also assigning a static IP address crashes the settings application. Will relay it to Oman.

    Leave a comment:


  • Finless
    replied
    Sdcards over 32gb cannot be formatted fat32. They have to be formatted extfat or NTFS.
    Recovery only supports fat32.

    Bob

    Leave a comment:


  • londonshore
    replied
    Stick with gotham 13.2 xunitytalk isnt compatable for kodi and best addon vdubt25 under xunity repo check it out

    Leave a comment:


  • tiguy82
    replied
    Originally posted by chrisbc View Post
    Kodi 14.0 Helix final seems to be working fine here too.
    I have no luck, some videos are slow. Had to install the XBMC provider with this update.

    Leave a comment:


  • chrisbc
    replied
    Mine installed easily using the Reboot app , I just inserted my 8GB Kingston MicroSD, selected reboot into Recovery, it rebooted & installed 2.1 auto-magically. Fastest upgrade I've ever done.

    Kodi 14.0 Helix final seems to be working fine here too.

    Leave a comment:


  • Magnus33
    replied
    I wonder if large format sd aren't support probably when installing.

    Leave a comment:


  • I-am-Logic
    replied
    Originally posted by tiguy82 View Post
    I had to use a 2GB SD Card. Mine 64GB was not working.
    Hello, mine have 2GB, also tested 8GB, but finaly 2GB and Tool worked.
    Have a nice Day.

    Leave a comment:


  • Magnus33
    replied
    Originally posted by I-am-Logic View Post
    Hello,

    i was sad and can`t understand why the 2.1 ROM will not Work and do be in search of this ......
    The ******* SD-Card was the Problem.
    SD-Card wit 2.0 ROM work well. Same Card wit 2.1 not ! Why ?????
    I formated the same Card with HP USB Disk Storage Format Tool 2.2.3

    Take the 2.1 ROM on it again ......... and it works !!!

    Ohhhh Man !!! I hate this SD-Cards .......

    So long ........
    Sounds like the cards damaged and in need of replacing.
    The older rom didn't write to the damaged area when it was put on and it worked.
    The newer rom did and it didn't.

    Once you reformated the bad area was marked and it wasn't written to.

    If it suddenly acts crazy then its gone bad if it keeps working fine then it was just a quirk.

    Leave a comment:

Working...
X