Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

X96 MAX TV Box BLACK 4/64GB Amlogic S905X2, Android 8.1, Dual WiFi, Gig Lan,USB3.0, BT4.0

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

  • Xannytech
    replied
    Originally posted by BiBaBuTzE View Post

    Hi, the first flash was over the recovery menu and after the flashing it stocked by the bootlogo Beelink. I can't get in to the recovery now and can't flash with the Burning Tool. It connects over the USB 3 Port and I can hear and See the Status Connection success in the Tool, but after a few seconds the device disconnected. Thanks...
    I'm not in my home now, this evening i'll post a solution for you you should boot thru sdcard.

    Leave a comment:


  • BiBaBuTzE
    replied
    Originally posted by Xannytech View Post

    have you tried to flash the fw as it should? using USB burning tool 2.1.6.8 loading the fw, clicking start and then connecting the device thru the usb3 port with a usb male to male cable?
    Hi, the first flash was over the recovery menu and after the flashing it stocked by the bootlogo Beelink. I can't get in to the recovery now and can't flash with the Burning Tool. It connects over the USB 3 Port and I can hear and See the Status Connection success in the Tool, but after a few seconds the device disconnected. Thanks...

    Leave a comment:


  • Xannytech
    replied
    Originally posted by zap View Post
    Have you also rebuilt the modules from /vendor/lib/modules/? I'm trying to rebuild the kernel, and I have a hard time compiling the media_modules (amvdec_*.ko modules).
    The makefiles are for building the modules as part of the whole Android system, it seems I'll have to write my own.

    Also another question. Do you have an idea why they're continuing to build the 32-bit version of Android for a 64-bit CPU?
    about the last question it's a nerd matter, no use for these device to use 64 bit android.
    Anyway you can get problem to rebuilt modules because your sources are incomplete or the compiler it's not the right version, or etc. etc... no idea and it's O.T.

    Leave a comment:


  • zap
    replied
    Originally posted by Xannytech View Post
    Stock has not gapps has AOSP compiled binary apps, it's a different matter.
    Anyway used stock fw, but i used a different fw directly from manufacturer, anyway to be more specific, Vendor it's pratically new from me, system it's from GT1 Mini, Kernel rebuilt from original fw. it's a totally new rom nothing is equal from stock.
    These devices do not need full gapps, maps, or face unlock or similar things are useless.
    Have you also rebuilt the modules from /vendor/lib/modules/? I'm trying to rebuild the kernel, and I have a hard time compiling the media_modules (amvdec_*.ko modules).
    The makefiles are for building the modules as part of the whole Android system, it seems I'll have to write my own.

    Also another question. Do you have an idea why they're continuing to build the 32-bit version of Android for a 64-bit CPU?

    Leave a comment:


  • Xannytech
    replied
    Originally posted by BiBaBuTzE View Post

    I have tried everything now. I have bought a new USB 3.0 hub with power connection, but I still get only a short connection with the device and then its lost the connection. The USB burning tool shows connection successfully, but after a few second the connection goes off again. I think I have the bootloader and the recovery bricked. Has someone a Tipp or a solution to get a New Bootloader and recovery on the Box???
    Please Help!!! !!!!
    have you tried to flash the fw as it should? using USB burning tool 2.1.6.8 loading the fw, clicking start and then connecting the device thru the usb3 port with a usb male to male cable?

    Leave a comment:


  • BiBaBuTzE
    replied
    Originally posted by Herrnobiz View Post

    Exactly, at first i used my pc usb2 port and the box was'nt reconized; i suspect those weren't giving enough juice, the usb3 did the trick!
    I have tried everything now. I have bought a new USB 3.0 hub with power connection, but I still get only a short connection with the device and then its lost the connection. The USB burning tool shows connection successfully, but after a few second the connection goes off again. I think I have the bootloader and the recovery bricked. Has someone a Tipp or a solution to get a New Bootloader and recovery on the Box???
    Please Help!!! !!!!

    Leave a comment:


  • Xannytech
    replied
    Originally posted by elektro86 View Post
    ok, I will wait.
    Anyway test my rom if you like

    Leave a comment:


  • Xannytech
    replied
    Originally posted by zap View Post
    Did you use stock fw as base, or it.'s compiled from scratch with respective vendor-specific bits?
    I see you say nano gapps installed, stock had full gapps if I understand correctly.
    Stock has not gapps has AOSP compiled binary apps, it's a different matter.
    Anyway used stock fw, but i used a different fw directly from manufacturer, anyway to be more specific, Vendor it's pratically new from me, system it's from GT1 Mini, Kernel rebuilt from original fw. it's a totally new rom nothing is equal from stock.
    These devices do not need full gapps, maps, or face unlock or similar things are useless.

    Leave a comment:


  • zap
    replied
    Did you use stock fw as base, or it.'s compiled from scratch with respective vendor-specific bits?
    I see you say nano gapps installed, stock had full gapps if I understand correctly.

    Leave a comment:


  • elektro86
    replied
    Originally posted by Xannytech View Post
    hmm... we will see i'm working on many devices, but i can think about it, it's just a matter of freetime.
    ok, I will wait.

    Leave a comment:


  • Xannytech
    replied
    Originally posted by elektro86 View Post
    Great was the work on m8s ii, I would like to see the version of the ATV from you.
    hmm... we will see i'm working on many devices, but i can think about it, it's just a matter of freetime.

    Leave a comment:


  • elektro86
    replied
    Originally posted by Xannytech View Post

    It's standard, it's very familiar for you if you're used to my roms
    Great was the work on m8s ii, I would like to see the version of the ATV from you.

    Leave a comment:


  • Xannytech
    replied
    Originally posted by elektro86 View Post
    Hi Xannytech, this is an ATV or standard, I used your build on the M8S II
    It's standard, it's very familiar for you if you're used to my roms

    Leave a comment:


  • elektro86
    replied
    Hi Xannytech, this is an ATV or standard, I used your build on the M8S II

    Leave a comment:


  • Xannytech
    replied
    Very soon i'll open a thread, but if someone would like to test it HERE is my new FW for X96 Max 4/64 4/32, i'm working also on a 2/16 version and a Beelink Gt1 Mini version.

    Has Magisk root yet installed, but please do not update to magisk 18.0 or root will not work anymore, has selinux in permissive mode, is deodexed, tweaked and fixed, has the newest 0zm0sys busybox installed, has a new launcher and nano gapps installed, it's a first version has to be refined, but i'd like you to test it.
    Flash it with Amlogic Usb Burning Tools 2.1.6.8, load the fw, then after the check click start, plug the usb male to male cable in the blu usb and wait for completion.
    Let me know.
    Later on i will add TWRP, actually i need testing without it.

    Leave a comment:

Working...
X