Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

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

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Kuno
    replied
    Holy cow Xannytech you've been one busy coder. Hope to try out the new firmware soon, just need to find a new adapter for my Yundoo as it burned itself out so I am currently powering it through USB haha. I really hope your tip jar is getting full with all these new people coming here. Thank you for your hard work and dedication to this project. In the next week or so I will be trying out your new firmware and will let you know what I think

    Leave a comment:


  • MarkusP87
    replied
    Hello,

    just successfully flashed my T6 1G/8GB Box with your ROM and it's really smooth and less laggy than the stock firmware.

    Thank you for this ROM and the hard work


    greeTz,
    MarkusP87

    Leave a comment:


  • scooter2014
    replied
    If he posts off topic again hes gone.

    Leave a comment:


  • Xannytech
    replied
    Originally posted by pszab View Post

    I can accept that you're right but why. It has the q201 device.
    Where can i find proper s912 source for Android?
    For the second time you're OFF TOPIC, on XDA i can manage my thread here not, but do not take advantage of this flaw of the forum.
    Open a thread and we'll help you if we can.

    Kindly
    Xanny

    Leave a comment:


  • pszab
    replied
    Originally posted by Xannytech

    You're totally OFF TOPIC, anyway it's not a good idea to buld a S912 Kernel with S905X sources.
    I can accept that you're right but why? that's I asked it. The s905x sdk contains q201 and separate s912 is nowhere.
    If not a good idea where can i find proper s912 source for Android?
    You are not really helpful but the others wasn't so enemy.
    If you don't want to reply here, please reply under the proper thread I posted here or in PM. That would be the correct.
    Last edited by pszab; 07-21-2017, 15:17.

    Leave a comment:


  • johnnewbie
    replied
    Originally posted by Woogetybop View Post

    I've read enough to know that the power on function is built into the boot code. So I figured now that it's running on modified Mini m8s II firmware I was going to get me a Mini M8S II remote control and put that remote.conf back in the system. Then everything will work correctly. I have the TV and my sound system CEC turned on. Currently I have to turn the tv on and go to settings, HDMI, then tell it to turn the tv Box on. Too many steps. I tested by removing power and back on again on the TV Box. So it acted as the start and It powered everything on together. So with the remote on button issue fixed I'll be golden.
    I realised the 2 button can turn the box on so I have set it up on the Logitech remote. All works the way it should now but navigating on the android with a remote is painful so air mouse it will have to be.

    Leave a comment:


  • Woogetybop
    replied
    Originally posted by johnnewbie View Post

    I installed Terminal Shortcut from the Play Store, created a shortcut with the command "reboot update" check the run with root privileges checkbox. So much easier than fiddling about with the toothpick in the AV port.

    The only thing left to fix is the power on from the remote but would require re-installing original firmware and I can't be bothered at the moment.
    I've read enough to know that the power on function is built into the boot code. So I figured now that it's running on modified Mini m8s II firmware I was going to get me a Mini M8S II remote control and put that remote.conf back in the system. Then everything will work correctly. I have the TV and my sound system CEC turned on. Currently I have to turn the tv on and go to settings, HDMI, then tell it to turn the tv Box on. Too many steps. I tested by removing power and back on again on the TV Box. So it acted as the start and It powered everything on together. So with the remote on button issue fixed I'll be golden.

    Leave a comment:


  • johnnewbie
    replied
    Originally posted by Woogetybop View Post
    Two things that come to mind is location of the remote.conf file, and more overlooked is setting the remote.conf file properties to 644. This is easily done though the file commander app's file properties settings.
    Nah tried all of that. Also set it to 777 so that should definitely have worked. It might be because the installation of the rom didn't go flawlessly - it hanged for ages when installing and I had to turn it off and back on again and then it booted.

    Leave a comment:


  • johnnewbie
    replied
    Originally posted by Woogetybop View Post

    So a question to you. What method do you use to boot into Libreelec? That's what I'm going to try next.

    thank You,

    Woogetybop
    I installed Terminal Shortcut from the Play Store, created a shortcut with the command "reboot update" check the run with root privileges checkbox. So much easier than fiddling about with the toothpick in the AV port.

    The only thing left to fix is the power on from the remote but would require re-installing original firmware and I can't be bothered at the moment.

    Leave a comment:


  • Woogetybop
    replied
    Originally posted by johnnewbie View Post

    Never mind. Just reflashed and tried again and seems to be working now. No idea why.
    So a question to you. What method do you use to boot into Libreelec? That's what I'm going to try next.

    thank You,

    Woogetybop

    Leave a comment:


  • Woogetybop
    replied
    Two things that come to mind is location of the remote.conf file, and more overlooked is setting the remote.conf file properties to 644. This is easily done though the file commander app's file properties settings.

    Leave a comment:


  • johnnewbie
    replied
    Originally posted by johnnewbie View Post
    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.
    Never mind. Just reflashed and tried again and seems to be working now. No idea why.

    Leave a comment:


  • johnnewbie
    replied
    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.

    Leave a comment:


  • Xannytech
    replied
    Originally posted by Igorbambus View Post

    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.

    Leave a comment:


  • Igorbambus
    replied
    Originally posted by Xannytech View Post

    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
    Code:
    [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.
    Last edited by Igorbambus; 07-13-2017, 22:28.

    Leave a comment:

Working...
X