wdtz

Members
  • Content Count

    29
  • Joined

  • Last visited

About wdtz

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I guess you have not read much of this thread, last5-6 pages would be good t9.dtb for 4.4.x kernel seems OK, I have not tried any 5.x, slightly different dtb (guess) Not on ups, 10d uptime,, H96max+, wifi dongle a bit unstable, needs powered hub, x11vnc Oh, and if hub back-feeds (many do) must unplug for reboot or power off For example, a 2 second power "blink", you will think box is dead, until you unplug hub power too
  2. @hexdump Thanks for your t9.dtb,, works fine with H96 max+ for me I could never figure out how the regulators worked, somehow you did Only thing lacking is module for SSV6051 I guess I should try to put patch in right place and make a kernel
  3. Board is labeled RK3328_8D4_V1.1, same as yours, wifi chip is indeed different, SV6051P Serial connection as shown in your photo I think the problem with sd card is power to socket, if you read this thread I have a few posts previous
  4. I have H96 max+,32gb, board is same, wifi is sv6051, no bluetooth Like you, most of the dtb give root fs not found, no /dev/block/mmc.... ,, or for the android versions a black screen, serial shows only a few lines of kernel load (<5) --edit-- you can make it work by writing image to both a uSD card and a usb stick, it will probably find the stick and run from it. The uSd can be small and slow Not so good with only 2 usb sockets
  5. Can you quote some specific models? My H96max+, android8.1 seemed OK,, SuperSU installed OK, root checker said all was well
  6. Err,, adb is not "android",, android is the graphical shell,, hypothetical example,, if you had firefox installed,, typing firefox in adb would NOT startup firefox But, for sure , adb is very powerful, despite being a considerable pain More on point, adb uses the su in /sbin,, android uses the su in /system/xbin,, it is no good
  7. Clearly,, you have not read whole thread,, about 5 pages back, but differently in adb# ,, ls -l /sbin/su; ls -l /system/xbin/su ,, notice that they are not the same? (google) verity off; mount -o remount,rw /system; cd /system/xbin; mv su su.bak; cp /sbin/su . and then root will work in android FWIW
  8. I have one of these, in the simple shell ls -l /dev/block will show at best mmcblk1 (the emmc), (almost) never the sd card I think it's something to do with the regulator,, pwm does not seem to work,, the android dtb seem to use simpleReg vrs rk805-regulator I did a "hack" bypassing gpio, barely works, lots of errors in dmesg (regulator errors,, boots and runs from sd) The other method is to copy rootfs to a usb stick, rename the partitions (e2label)
  9. Dmesg , if all is well, will give a message, ie (dmesg |grep firmw) usb 1-1.4.3: rtl8xxxu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin for a usb dongle
  10. Well, it varies, alas. The firmware files can be bin or fw or other. Usually from /lib/firmware or a folder there BUT can be in /usr/somewhere, this is not common I don't know how the ko knows where to find the firmware Firmware are for the wifi chip, are version and OS independent It is 1 of them, there are 9 or 10 in total plus uboot and miniLoader and ? Maybe I'm telling you something you already know, / in Android is only in mem, loaded from the boot part, a gz cpio. Most of the folders in / (android ) are links to the appropriate partition I would guess that these are the ones you need, try copy them to lib/firmware/rtlwifi
  11. As I said, usually an android dtb won't work for linux, but it is a guide on how to change an almost working dtb For wifi,, 3 things have to be "right". A reference in the dtb, a module, and the firmware You will really have to get dtc (device tree compiler) and learn how to use it, it is not that hard.. Harder is making the "right" device tree IMO,, you really should have a "perfect" boot with sdcard (everything works, no glitches) before thinking about overwriting emmc ----more-- For wifi the reference in the dtb is not at all important, only if you want it to work during boot. I have seen wrong wifi chip referenced in dtb, modprobe right module (if firmware is there) and the wifi works This assumes it is talking to the right gpio There is a discussion about that in this thread a few pages previous
  12. No, mmcblk0 is almost certainly your sdcard, just from the partitions on it It's really common for android to have boot0, boot1, rpmb on the emmc, that is likely where it is (blk2) If you have checked your evb.dtb by turning it into a dts, check dwmmc@ff500000, and @ff520000 for bus-width = < 0x04 >; or 0x08 and the aliases { ,, then you will know for sure You do know this will wipe out your android? Before you do that, it would be good to extract the android dtb because it is sometimes hard to get the right image for your hardware, there are so many slightly different images
  13. There are dozens of different tv boxes, easy to get wrong image, usually does not "work out" in output/Image (specifically my box, h96max+-ssv, from the vendor, ssv is wifi) ls -l *.img -rw-rw-r-- 1 d d 1048576 Nov 11 12:35 baseparameter.img -rw-rw-r-- 1 d d 1708536 Nov 11 12:35 boot.img -rw-rw-r-- 1 d d 19036180 Nov 11 12:35 kernel.img -rw-rw-r-- 1 d d 49152 Nov 11 12:35 misc.img -rw-rw-r-- 1 d d 168060 Nov 11 12:36 oem.img -rw-rw-r-- 1 d d 8971308 Nov 11 12:35 recovery.img -rw-rw-r-- 1 d d 5592576 Nov 11 12:35 resource.img -rw-rw-r-- 1 d d 1547079912 Nov 11 12:36 system.img -rw-rw-r-- 1 d d 4194304 Nov 11 12:35 trust.img -rw-rw-r-- 1 d d 4194304 Nov 11 12:35 uboot.img -rw-rw-r-- 1 d d 163962992 Nov 11 12:36 vendor.img and in output -rw-rw-r-- 1 d d 162126 Nov 11 12:33 boot.bin drwxrwxr-x 4 d d 4096 Nov 30 01:54 Image/ -rw-rw-r-- 1 d d 162126 Nov 11 12:35 MiniLoaderAll.bin -rw-rw-r-- 1 d d 724 Nov 11 12:35 package-file -rw-rw-r-- 1 d d 981 Nov 11 12:35 parameter.txt Still have to extract dtb from resource.img
  14. Ah, android.. No, if you run fdisk -l on your mmcblk2 file you will see 3 4mB partitions,, where is the rest?? 15 or 30 gB missing, right? The rest is in a mtd filesystem,, under the stanza "chosen" you may see something like this bootargs ......... mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(trust),\ 0x00002000@0x00006000(misc),0x00000800@0x00008000(baseparameter),0x00008000@0x00008800(resource),\ 0x00010000@0x00010800(kernel)...and so on (#'s are blocks/sectors,,,, length@offset (+12M)) You want the first 70k of resource, starts 2k in, magic is 0xd00dfeed, about 64k long. The rest is 2 png or jpg, the splash screen, 1st is for 720p, 2nd (larger) for 1080p I don't know how to mount mtd filesystems, AND I have had no luck converting android dtb to linux dtb,, nothing that I have found on google either Usually it just doesn't boot, fails very early on kernel load (serial console) ----- but usually with these tv boxes you have root in adb,, have you tried? If so, cd to proc, somewhere in there is the device tree, use busybox tar and write it to sdcard, and then to your computer (on an ext fs), then expand and use dtc -fs on the expanded directory,, then you will have the android dtb Or,, easier, if you have adb root,,, find which partition resource is , /dev/mmcblk2p??? ,, dd 70k to internal sdcard (I think this is ext fs,, vfat will lose permissions etc) then to computer, chop leading 2k, trim excess from end (hexeditor and dd) BTW the reason adb has root but not android... the su in /system/xbin is no good,, the one in /sbin is the right one Use verity off to make /system rw, then you can mv xbin/su xbin/su.bak and /sbin/su -> xbin and then get su in android
  15. Err, I have a mt7601u,, 148f:7601,, I don't think it is so good,, in iwconfig I see Tx excessive retries:35031 Invalid misc:1837 Missed beacon:0 (this is with uptime 9d 13h)