If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
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.
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.
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 :
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
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.
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.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment