[ROM] XannyTech Custom Mod Rom + TWRP Recovey built-in - for MINIM8SII and other devices see first post.

[Woogetybop]

Requesting help from anyone who can get me or help me retrieve the remote.conf file off of a TX95 or has a copy.

To XannyTech Let me start off by saying thank-you for all your hard work. I cant wait to try your XTMod Rom out. I've read some great stuff about it. Well done!!
I've been reading ALL these post for information. So far I'm at post 50 or about halfway. The price I pay for being a Noob at this android stuff.

I managed to buy one of the most unsupported TV boxes out there. there is very little info out there. I have a Kekilo TX95. This is generally know as a TX95 under names like Tanix, Zenoplige, Akaso, and QcoQce. It has the 9377 wifi according to the 77 in the serial number. Firmware build 20160930. Never a OTA update, and most likely never will. This stock firmware does not let me access the system (that I can see) tooth pick method does not work. I can access its simple recovery mode by rebooting and holding the menu key on the remote. It will only boot to internal Nand memory. Its a catch 22. I'm ready to upgrade to this XTMod 2.8 Rom, but need to retrieve my remote.conf file first.

[kevin1341]

Hi Woogetybop,
This is from a Tanix.

https://www.dropbox.com/s/jea1da6ijlyx86s/remote.zip?dl=0

Hope it helps.
Cheers
Kevin

[Woogetybop]

Hi Woogetybop,
This is from a Tanix.

https://www.dropbox.com/s/jea1da6ijlyx86s/remote.zip?dl=0

Hope it helps.
Cheers
Kevin

Thank you Kevin for your help. It is greatly appreciated.
Now I can proceed with the XTMod Rom upgrade!

[scooter2014]

8723xx - still not work bluetooth on this version of firmware, Xannytech. Why this chipset is not excluded from your list of supported chipsets, I dont understend. Few month ago more people talking about problems with 8723 on your firmware. Why you dont want to hear us, or dont want remove this chipset from your list of supported chipsets? Please arrange this list, Because people see their chipset in your post, Install your firmware and have more problems with not worked wifi, bluetooth etc.

He does listen and has fixed alot your wifi chip is supported bluetooth may not work (you cant have everything and ever device working in one firmware. ) Its the way things are asked that can piss off a Dev. So maybe next time say that you tried and wifi/bluetooth did not work on your device. The reason its in the post is someone reported it working. Maybe your device did not. We are happy that Xanny has taken on this project. Be a little more friendly in your comments going forward. Digitalriver as now we will be watching your posts.

Xanny keep up the great work The FreakTab Team supports you.


Best regards.

[Xannytech]

Xanny keep up the great work The FreakTab Team supports you.


Best regards.

Thanks mate

[Woogetybop]

Xannytech

TV Box Keliko TX95 w/9377 wifi.
Yesterday I installed the firmware posted here. At first I had a challenge getting a USB mouse to work with TWERP. Three different try's until I found a mouse that worked. (A combo keyboard/mouse) Installed your 9377 wifi .zip patch on SD card. 2nd time boot had wifi working perfectly. My remote.conf file still wasn't right, and had no working remote. Used your TX5 Pro remote.conf file and set permissions at 644. Remote was working perfectly except for power on. This I knew was an issue with the boot code being from another TV Box as I've seen posted here. After connecting my TX95 Box to my Sharp 4K TV with CEC enabled. TX95 remote would power unit on as well as the Sharp remote would also control the TX95 TV Box. A bonus I didn't count on. No issues found yet. Resolution auto switching in Kodi branch app, hdmi 5.1 surround working. (My system is only 5.1ch). Smooth playback of 1080p mkv files (before they played good on other 1080p tv's but playback stuttered on my Sharp 4K TV. Not something I could live with.
I am very pleased with having a solid performing TV Box that used to be a lemon.

Thank You XannyTech!!

[Xannytech]

It's an update file to be flashed through TWRP Recovery JUST for the users with AP6212A Chipset and 9082XX Chipset.

What's new:
- updated drivers for AP6212A Chipset;
- Lib to activate 9082XX wifi chipset on my rom.

DO NOT USE THIS FILE IF YOU OWN A 9377 CHIPSET!!!


I will not post this file on first page for now!

UPDATE TO 2_8_1

Enjoy

[gizmomelb]

really silly question.. is there an app to tell you which wifi chipset you have in your device please?

[scooter2014]

really silly question.. is there an app to tell you which wifi chipset you have in your device please?

No easiest way is open device take photo of wifi chip

[Dandroid534]

Or you can just browse through folders that are already on device, it will be one of them. Even if it's not you can always try and copy it across with permissions. Or just use ethernet.

[Igorbambus]

Hello, thanks for cool rom,
but can help me anyone customize for my board "A95X_DDR4 V1_1 20160906"

http://imgur.com/a/Ixe3F

clear flash original XTMOD 2.8 cause red led brick box,
only emmc reset help flash "stock rom" - cyx_NEXBOX-A95X_S905X_8189etv_8g1g_SD_USB.rar
I try "@steocullen91" instructions change bootloader.PARTITION, DDR.USB, UBOOT.USB files from stock
now rom boot up but cause boot loop and emergecy reset, I post serial console logs afternoon.
Thanks for any help.


Serial console log from stock

[5.144229@3] init: do_confirm_formated ext4 try mount
[5.153339@1] EXT4-fs (mmcblk0p8): recovery complete
[5.154236@1] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data mode. Opts: noauto_da_alloc

Serial console log from XTMOD 2.8 with change bootloader.PARTITION, DDR.USB, UBOOT.USB files from stock

[5.142999@1] init: do_confirm_formated ext4 try mount
[5.148698@2] EXT4-fs (mmcblk0p8): VFS: Can't find ext4 filesystem
[5.154334@2] init: do_confirm_formated mount fail,maybe firstboot, need format, try format now, dev:/dev/block/tee, mountpoint:/tee
[5.662840@3] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data mode. Opts: noauto_da_alloc
[5.699017@3] init: enter do_confirm_formated /dev/block/data, /data
[5.699736@3] init: do_confirm_formated ext4 try mount
[5.705193@3] EXT4-fs (mmcblk0p14): VFS: Can't find ext4 filesystem
[5.711152@3] init: do_confirm_formated mount fail,maybe firstboot, need format, try format now, dev:/dev/block/data, mountpoint:/data
[12.082451@2] random: nonblocking pool is initialized
[16.130014@3] EXT4-fs (mmcblk0p14): mounted filesystem with ordered data mode. Opts: noauto_da_alloc
[16.188549@3] init: enter do_confirm_formated /dev/block/cache, /cache
[16.189446@3] init: do_confirm_formated ext4 try mount
[16.194931@3] EXT4-fs (mmcblk0p3): VFS: Can't find ext4 filesystem

[Xannytech]

Hello, thanks for cool rom,
but can help me anyone customize for my board "A95X_DDR4 V1_1 20160906"

http://imgur.com/a/Ixe3F

clear flash original XTMOD 2.8 cause red led brick box,
only emmc reset help flash "stock rom" - cyx_NEXBOX-A95X_S905X_8189etv_8g1g_SD_USB.rar
I try "@steocullen91" instructions change bootloader.PARTITION, DDR.USB, UBOOT.USB files from stock
now rom boot up but cause boot loop and emergecy reset, I post serial console logs afternoon.
Thanks for any help.


Serial console log from stock

[5.144229@3] init: do_confirm_formated ext4 try mount
[5.153339@1] EXT4-fs (mmcblk0p8): recovery complete
[5.154236@1] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data mode. Opts: noauto_da_alloc

Serial console log from XTMOD 2.8 with change bootloader.PARTITION, DDR.USB, UBOOT.USB files from stock

[5.142999@1] init: do_confirm_formated ext4 try mount
[5.148698@2] EXT4-fs (mmcblk0p8): VFS: Can't find ext4 filesystem
[5.154334@2] init: do_confirm_formated mount fail,maybe firstboot, need format, try format now, dev:/dev/block/tee, mountpoint:/tee
[5.662840@3] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data mode. Opts: noauto_da_alloc
[5.699017@3] init: enter do_confirm_formated /dev/block/data, /data
[5.699736@3] init: do_confirm_formated ext4 try mount
[5.705193@3] EXT4-fs (mmcblk0p14): VFS: Can't find ext4 filesystem
[5.711152@3] init: do_confirm_formated mount fail,maybe firstboot, need format, try format now, dev:/dev/block/data, mountpoint:/data
[12.082451@2] random: nonblocking pool is initialized
[16.130014@3] EXT4-fs (mmcblk0p14): mounted filesystem with ordered data mode. Opts: noauto_da_alloc
[16.188549@3] init: enter do_confirm_formated /dev/block/cache, /cache
[16.189446@3] init: do_confirm_formated ext4 try mount
[16.194931@3] EXT4-fs (mmcblk0p3): VFS: Can't find ext4 filesystem

It's partition mess , some Nexbox, the newest one, cannot be falshed with my Rom, honestly dunno if there is a custom working on this kind of nexbox.

[Igorbambus]

It's partition mess , some Nexbox, the newest one, cannot be falshed with my Rom, honestly dunno if there is a custom working on this kind of nexbox.

Is any chance fix it? I want fix this myself if I know how, but don't know. Some push me? edit mount script unpack bootloader or whatever What should I do first?

I have some custom for fast flashing, emmc reset push button, reasemble for every brick is not fun (20x bricked), and output conector for serial , A-A USB


Storage part booot log from stock rom

[2.127978@0] storage: storage in base: 0xffffff8001800000
[2.133107@0] storage: storage out base: 0xffffff8001880000
[2.138580@0] storage: storage block base: 0xffffff8001900000
[2.144278@0] storage: probe done!
[2.148193@0] aml_sd_emmc_probe: line 3558
[2.151740@0] mmc driver version: 1.07, 2015-01-21: fix a bug in tuning which caused eMMC data CRC error
[2.161516@0] aml_sd_emmc_reg_init 1146
[2.164940@0] get property:                ocr_avail, value:0x00200080
[2.171403@0] get property:                    f_min, value:300000
[2.177479@0] get property:                    f_max, value:50000000
[2.183783@0] get property:             max_req_size, value:0x00020000
[2.190285@0] get property:                  pinname, str:emmc
[2.196024@0] get property:                card_type, value:1
[2.201733@0] get property:                gpio_dat3, str:
[2.207150@0] get property:                 hw_reset, str:
[2.212647@0] emmc:pdata->caps = c0000d47
[2.216550@0] emmc:pdata->caps2 = 0
[2.220036@0] storage 1, boot 1
[2.223105@0] get_storage_dev return 1
[2.258631@0] [aml_sd_emmc_probe] aml_sd_emmc_probe() success!
[2.264111@0] aml_sd_emmc_probe: line 3558
[2.264501@0] aml_sd_emmc_reg_init 1146
[2.266757@0] get property:                ocr_avail, value:0x00200080
[2.273261@0] get property:                    f_min, value:400000
[2.279342@0] get property:                    f_max, value:100000000
[2.285646@0] get property:             max_req_size, value:0x00020000
[2.292144@0] get property:                   irq_in, value:3
[2.297807@0] get property:                  irq_out, value:5
[2.303596@0] get property:                  gpio_cd, str:
[2.308943@0] get property:                  pinname, str:sd
[2.314565@0] get property:                 jtag_pin, str:
[2.320053@0] get property:                card_type, value:5
[2.325739@0] get property:                gpio_dat3, str:
[2.331226@0] sd:pdata->caps = 7
[2.334362@0] sd:pdata->caps2 = 0
[2.348561@1] emmc: BKOPS_EN bit is not set
[2.352054@1] emmc: try set sd/emmc to DDR mode
[2.352173@1] emmc: new DDR MMC card at address 0001
[2.356517@1] emmc: clock 50000000, 8-bit-bus-width
[2.361878@1] mmcblk0: emmc:0001 8WPD3R 7.28 GiB
[2.366402@1] mmcblk0boot0: emmc:0001 8WPD3R partition 1 4.00 MiB
[2.372505@2] [aml_is_card_insert] card OUT
[2.372646@1] [aml_sd_emmc_probe] aml_sd_emmc_probe() success!
[2.372683@1] aml_sd_emmc_probe: line 3558
[2.372793@1] mmcblk0boot1: emmc:0001 8WPD3R partition 2 4.00 MiB
[2.378931@1] aml_sd_emmc_reg_init 1146
[2.378985@1] get property:                ocr_avail, value:0x00200080
[2.378989@1] get property:                    f_min, value:400000
[2.378992@1] get property:                    f_max, value:200000000
[2.378994@1] get property:             max_req_size, value:0x00020000
[2.379001@1] get property:                  pinname, str:sdio
[2.379005@1] get property:                card_type, value:3
[2.379053@1] sdio:pdata->caps = 7810f
[2.379055@1] sdio:pdata->caps2 = 0
[2.379262@1] mmcblk0rpmb: emmc:0001 8WPD3R partition 3 512 KiB
[2.380395@1]  mmcblk0: unknown partition table
[2.381189@1] [mmc_read_partition_tbl] mmc read partition OK!
[2.381191@1] add_emmc_partition
[2.381427@1] [mmcblk0p01]           bootloader  offset 0x000000000000, size 0x000000400000
[2.381640@1] [mmcblk0p02]             reserved  offset 0x000002400000, size 0x000004000000
[2.381822@1] [mmcblk0p03]                cache  offset 0x000006c00000, size 0x000020000000
[2.382003@1] [mmcblk0p04]                  env  offset 0x000027400000, size 0x000000800000
[2.382177@1] [mmcblk0p05]                 logo  offset 0x000028400000, size 0x000002000000
[2.382343@1] [mmcblk0p06]             recovery  offset 0x00002ac00000, size 0x000002000000
[2.382515@1] [mmcblk0p07]                  rsv  offset 0x00002d400000, size 0x000000800000
[2.382681@1] [mmcblk0p08]                  tee  offset 0x00002e400000, size 0x000000800000
[2.382863@1] [mmcblk0p09]                crypt  offset 0x00002f400000, size 0x000002000000
[2.383031@1] [mmcblk0p10]                 misc  offset 0x000031c00000, size 0x000002000000
[2.383204@1] [mmcblk0p11]            instaboot  offset 0x000034400000, size 0x000020000000
[2.383368@1] [mmcblk0p12]                 boot  offset 0x000054c00000, size 0x000002000000
[2.383544@1] [mmcblk0p13]               system  offset 0x000057400000, size 0x000040000000
[2.383715@1] [mmcblk0p14]                 data  offset 0x000097c00000, size 0x00013a400000
[2.383757@1] card key: card_blk_probe.
[2.383761@1] emmc_key_init:527 emmc key lba_start:0x12020,lba_end:0x12220
[2.383764@1] emmc key: emmc_key_init:552 ok.
[2.384035@1] amlmmc_dtb_init: register dtb chardev
[2.384151@1] amlmmc_dtb_init: register dtb chardev OK
[2.384152@1] Exit aml_emmc_partition_ops OK.

[Xannytech]

Is any chance fix it? I want fix this myself if I know how, but don't know. Some push me? edit mount script unpack bootloader or whatever What should I do first?

I have some custom for fast flashing, emmc reset push button, reasemble for every brick is not fun (20x bricked), and output conector for serial , A-A USB

Not easy... just do some tests try to decompile your stock rom then delete system folder and put instead mine, recompile, if it boot, should lack of some script and my kernel, but it's a start point.
I doubt it will boot but if you want to experiment something, you should try.

[johnnewbie]

Hello. I wanted something with root access so I can flick between Android and Libreelec with reboot update without going to the reset button and for that it's perfect. Unfortunately, I cannot figure out why the remote is not working.

I have tried with the remote.conf from the original Yundoo Y6 firmware and also from the Libreelec sd card but can't get it to work and I can't think why. Works fine in Libreelec. Also, have enabled in the remote menu in settings. The remote.conf for the Y6 seem to be the same as the one X96.

Anybody any ideas what I am doing wrong?

Thanks - any help much appreciated.