Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

MECOOL KM3 Android Amlogic S905X2 Android 9.0 DDR4 4/64GB ROM Dual WiFi BT4.1

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

  • exotic34
    replied
    Hello all..How to root Mecool KM3 (4/64) Collective ? Thanks and Happy New Year




    Leave a comment:


  • Dicentim
    replied
    Originally posted by b2oba17 View Post
    you need to use this recovery.img ,it's launch from a flash drive https://mega.nz/#F!VtJ1TQTS!hFXf9r8d...w0MOw?V1R1DKCR
    Thanks again but we can only flash .zip file from flash drive, so I have to zip the .img file or using USB burning tools ?
    And is it the stockrecovery or a custom one ? Thanks.
    Your rom seems great hope I'll be able to flash it again.

    I found this : https://forum.xda-developers.com/and...to-pc-t3914587
    Second post is very interesting as I encounters the same exact problem.
    Last edited by Dicentim; 19 December 2019, 13:54.

    Leave a comment:


  • b2oba17
    replied
    you need to use this recovery.img ,it's launch from a flash drive https://mega.nz/#F!VtJ1TQTS!hFXf9r8d...w0MOw?V1R1DKCR

    Leave a comment:


  • Dicentim
    replied
    Yes of course I Launched cmd.exe in administrator mode.

    I tried the command "fastboot devices" or "adb devices" and nothing appears.
    The box is well detected by USB burning tools but not by cmd.exe.

    Or maybe it's beause the last command line " fastboot oem reset" failed during the 1st flash...

    Leave a comment:


  • b2oba17
    replied
    you launch all in administrator mode ?

    Leave a comment:


  • Dicentim
    replied
    Hi Bo2ba17, unfortunately your link is dead : https://adbdriver.com/upload/ADBDriverInstaller.exe
    I installed this one that is certainly the same : https://adb.clockworkmod.com/

    And still the same issue, my box is not recognized by the command lines.
    Here is the way my box appears on Windows :

    Click image for larger version  Name:	Capture.JPG Views:	4 Size:	55.8 KB ID:	792870

    It's ok using USB burning tool but I can't enter any command line.

    The first time I intalled your ROM it was ok, I was able to access command line and I could enter :

    update bulkcmd fastboot
    fastboot flashing unlock
    fastboot flashing unlock_critical

    I only got an error with the last command : fastboot oem reset
    But it was ok the box booted on your rom, but with this slight voice remote bug I decided to reflash again and now no way to enter ant command line.
    As soon as I try to enter update bulkcmd fastboot I have the error I wrote in my previous post.

    I use the same cable, the same USB port, I even tried on another PC. Honestly I don't understand why... What changed between the 1st time and now ?

    Maybe it's stupid but I think that as your rom was root , it changed the recovery and I need to flash the stock recovery to get adb/fastboot commands back. No ?

    Or is it possible to install your ROM (.zip format) using USB update ?
    If not I'll keep the stock firmware. Sigh...
    Thanks.
    Last edited by Dicentim; 19 December 2019, 12:50.

    Leave a comment:


  • b2oba17
    replied
    Originally posted by Dicentim View Post
    Hi,
    I tried using another PC (Windows 7), always the same : my box is not recognized by command lines.
    I can only flash using the stock ROM usingUSB burning tools.
    Maybe I have to do this but I'm afraid doing some wrong things :
    https://forum.freaktab.com/forum/mai...180#post781180
    You need to install adb universal drivers

    Leave a comment:


  • Dicentim
    replied
    Hi,
    I tried using another PC (Windows 7), always the same : my box is not recognized by command lines.
    I can only flash using the stock ROM usingUSB burning tools.
    Maybe I have to do this but I'm afraid doing some wrong things :

    Leave a comment:


  • Antoyax
    replied
    If Netflix 4K is working with this box, it will be the perfect cheap box for me.

    Leave a comment:


  • Dicentim
    replied
    Hi,
    I managed to flash the KM9 Rom, and the autroframerate worked great but as I had no support for the voice remote I tried to flash again but this time I couldn't enter the command lines.
    The KM3 device is well detected in USB burning tool, but not when I try the "fasboot devices" command line.
    And I get an error when I try to enter "update bulkcmd fastboot".
    So without using the command lines the box has bootloop during the first boot.
    Fortunately I was able toreflash the stock firmware back.

    I'll try tomorrow using another computer, or wait for a zip update of your ROM.

    The error I get in command line :

    C:\soft>update bulkcmd fastboot
    AmlUsbBulkCmd = fastboot rettemp = 1 buffer = fastboot
    Read status usbReadFile len=512,ret=-5 error_msg=libusb0-dll:err [submit_async] submitting request failed, win error: Un pÚriphÚrique attachÚ au systÞme ne fonctionne pas correctement.

    return len=-1, buffer=
    ERR: AmlUsbBulkCmd failed!
    Last edited by Dicentim; 18 December 2019, 15:02.

    Leave a comment:


  • Dicentim
    replied
    Thanks B2oba17 !
    One last question, the main difference between the KM9 Pro and KM3 is the double wifi band for the KM3.
    With this ROM will the wifi of the KM3 remains as efficient as the stock ROM?
    Thanks a lot.
    Cheers from Reunion Island.

    It would be so good if you can patch Netflix 4K, this box should be a great alternative to Nvidia Shield for third of the price.

    Leave a comment:


  • b2oba17
    replied
    Originally posted by Dicentim View Post
    Hi b2oba17, welcome back !
    Unfortuantely nobody managed to inject the keys to get Netflix 4K working on KM3, although we strictly followed your procedure.
    We all got the same DiskInitial error, any further information please ? Thanks


    [18:18:38 807][Global][Inf]--OpenImg C:\Users\PC-Dicentim\Desktop\Mecool KM3\wv-key\wv-key.img
    [18:18:38 807][HUB3-4][Inf]--Connect path=Contr?leur d’h?te am?lior? USB ? circuit microprogramm? Intel(R) de la s?rie 6/C200 - 1C2D/P0/P0/P3
    [18:18:38 807][HUB3-4][Inf]--Start burning...
    [18:18:38 876][HUB3-4][Inf]-------------Download DDR.USB-----------
    [18:18:38 876][HUB3-4][Inf]--0-7-0-16
    [18:18:38 876][HUB3-4][Inf]--Upload encrypt at 0xc8100228
    [18:18:38 891][HUB3-4][Inf]--ulValue = 0x6c9da79f
    [18:18:38 891][HUB3-4][Inf]--Enctypt!
    [18:18:38 891][HUB3-4][Inf]--No need download
    [18:18:38 891][HUB3-4][Inf]--0-7-0-16-0-0-0-0
    [18:18:38 891][HUB3-4][Inf]--No need download
    [18:18:38 891][HUB3-4][Inf]-- low_power
    [18:18:38 891][HUB3-4][Inf]--Send command success
    [18:18:38 891][HUB3-4][Inf]--Read command status success
    [18:18:38 891][HUB3-4][Inf]-------------Download meson1.dtb-----------
    [18:18:38 891][HUB3-4][Inf]--0-7-0-16
    [18:18:38 891][HUB3-4][Inf]--Enc(0x6c9da79f)
    [18:18:38 891][HUB3-4][Inf]-- download mem dtb normal 141312
    [18:18:38 891][HUB3-4][Inf]--Send download command success
    [18:18:38 907][HUB3-4][Inf]--Read command status success
    [18:18:38 922][HUB3-4][Inf]--Transfer complete
    [18:18:38 922][HUB3-4][Inf]--Send download get_status command succeed
    [18:18:38 938][HUB3-4][Inf]--get_status success
    [18:18:39 456][HUB3-4][Inf]-------------ERASE FLASH-----------
    [18:18:39 456][HUB3-4][Inf]--disk_initial 0
    [18:18:39 456][HUB3-4][Inf]--Send command success
    [18:18:39 508][HUB3-4][Err]--failed:[18:18:39 508][HUB3-4][Err]--Check command return failed
    [18:18:39 508][HUB3-4][Err]--[0x32030201]Uboot/Get result/DiskInitial error
    [18:18:39 508][HUB3-4][Inf]--Close device handle 0x00000a30
    [18:18:52 708][Global][War]--User click stop button

    Edit : About the ROM you just posted, here is the update_manual.txt file :

    Ðàñïàêîâàòü soft.zip â îòäåëüíóþ ïàïêó íàïðèìåð C:\soft
    Óñòàíîâèòü USB Burning Tool 2.1.7.3 (â àðõèâå)
    Ïðîøèâàåì img êàê îáû÷íî ÷åðåç USB Burning Tools
    íå çàáûâàåì íàæàòü Stop ïî îêîí÷àíèè ïðîøèâêè
    íå ïåðåãðóæàÿ çàïóñêàåì â êîììàíäíîé ñòðîêå Windows èç ïàïêè C:\soft òàêèå êîììàíäû:

    update bulkcmd fastboot

    fastboot flashing unlock
    fastboot flashing unlock_critical
    fastboot oem reset

    Ïîëüçóåìñÿ!

    Do you have an english version please ? Cause I can't understand these characters. Thanks a lot !
    i need to rework on netflix patch please wait

    for rom :


    Unzip soft.zip into a separate folder, for example C: \ soft Install USB Burning Tool 2.1.7.3 (archived) Flashing img as usual via USB Burning Tools Do not forget to click Stop at the end of the firmware without overloading, run the following commands in the Windows command line from the C:\ soft folder:
    update bulkcmd fastboot fastboot flashing unlock fastboot flashing unlock_critical fastboot oem reset enjoy
    Last edited by b2oba17; 17 December 2019, 10:55.

    Leave a comment:


  • Dicentim
    replied
    Hi b2oba17, welcome back !
    Unfortuantely nobody managed to inject the keys to get Netflix 4K working on KM3, although we strictly followed your procedure.
    We all got the same DiskInitial error, any further information please ? Thanks


    [18:18:38 807][Global][Inf]--OpenImg C:\Users\PC-Dicentim\Desktop\Mecool KM3\wv-key\wv-key.img
    [18:18:38 807][HUB3-4][Inf]--Connect path=Contr?leur d’h?te am?lior? USB ? circuit microprogramm? Intel(R) de la s?rie 6/C200 - 1C2D/P0/P0/P3
    [18:18:38 807][HUB3-4][Inf]--Start burning...
    [18:18:38 876][HUB3-4][Inf]-------------Download DDR.USB-----------
    [18:18:38 876][HUB3-4][Inf]--0-7-0-16
    [18:18:38 876][HUB3-4][Inf]--Upload encrypt at 0xc8100228
    [18:18:38 891][HUB3-4][Inf]--ulValue = 0x6c9da79f
    [18:18:38 891][HUB3-4][Inf]--Enctypt!
    [18:18:38 891][HUB3-4][Inf]--No need download
    [18:18:38 891][HUB3-4][Inf]--0-7-0-16-0-0-0-0
    [18:18:38 891][HUB3-4][Inf]--No need download
    [18:18:38 891][HUB3-4][Inf]-- low_power
    [18:18:38 891][HUB3-4][Inf]--Send command success
    [18:18:38 891][HUB3-4][Inf]--Read command status success
    [18:18:38 891][HUB3-4][Inf]-------------Download meson1.dtb-----------
    [18:18:38 891][HUB3-4][Inf]--0-7-0-16
    [18:18:38 891][HUB3-4][Inf]--Enc(0x6c9da79f)
    [18:18:38 891][HUB3-4][Inf]-- download mem dtb normal 141312
    [18:18:38 891][HUB3-4][Inf]--Send download command success
    [18:18:38 907][HUB3-4][Inf]--Read command status success
    [18:18:38 922][HUB3-4][Inf]--Transfer complete
    [18:18:38 922][HUB3-4][Inf]--Send download get_status command succeed
    [18:18:38 938][HUB3-4][Inf]--get_status success
    [18:18:39 456][HUB3-4][Inf]-------------ERASE FLASH-----------
    [18:18:39 456][HUB3-4][Inf]--disk_initial 0
    [18:18:39 456][HUB3-4][Inf]--Send command success
    [18:18:39 508][HUB3-4][Err]--failed:[18:18:39 508][HUB3-4][Err]--Check command return failed
    [18:18:39 508][HUB3-4][Err]--[0x32030201]Uboot/Get result/DiskInitial error
    [18:18:39 508][HUB3-4][Inf]--Close device handle 0x00000a30
    [18:18:52 708][Global][War]--User click stop button

    Edit : About the ROM you just posted, here is the update_manual.txt file :

    Ðàñïàêîâàòü soft.zip â îòäåëüíóþ ïàïêó íàïðèìåð C:\soft
    Óñòàíîâèòü USB Burning Tool 2.1.7.3 (â àðõèâå)
    Ïðîøèâàåì img êàê îáû÷íî ÷åðåç USB Burning Tools
    íå çàáûâàåì íàæàòü Stop ïî îêîí÷àíèè ïðîøèâêè
    íå ïåðåãðóæàÿ çàïóñêàåì â êîììàíäíîé ñòðîêå Windows èç ïàïêè C:\soft òàêèå êîììàíäû:

    update bulkcmd fastboot

    fastboot flashing unlock
    fastboot flashing unlock_critical
    fastboot oem reset

    Ïîëüçóåìñÿ!

    Do you have an english version please ? Cause I can't understand these characters. Thanks a lot !
    Last edited by Dicentim; 16 December 2019, 19:52.

    Leave a comment:


  • b2oba17
    replied
    Originally posted by Dicentim View Post
    Hi, is the auto frame rate working for anyone? If yes could you please tell me the trick? Thanks
    Certified google
    all work,cast ork
    rooted and AFRD work for km9 pro and km3 ;-)

    https://mega.nz/#!d4oA1AJb!cpdJ6HB8z...Y9i0RTkjVkDdiI

    Leave a comment:


  • jadesse
    replied
    Originally posted by jadesse View Post
    I have not been able to get Amazon Prime to work. Sometimes if there is a preview before the show/movie that will play. Once my show/movie starts I might get audio & and black screen or just a black screen. I have tried several versions of the Amazon Prime off of Aptoid TV & non have worked. I don't understand how it works for some & not others. Any help is appciated.

    KM3 Ver - 905300090316

    Two of the many veersion that I have tried.

    4.14.3-googleplay-armv7a
    4.8.69-googleplay-armv7a

    I found one for the Xiaomi Mi Box that I had download quite a few months ago that is working. I am curios to know what the difference is though?

    Leave a comment:

Working...
X