WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • inflex
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Originally posted by Maxpower3
    For decoding Customer ID

    0000000 1111111 2222222 3333333 4444444 5555555 6666666 7777777 8888888 9999999
    efgefge fghfghf ghighig hijhijh ijaijai jabjabj abcabca bcdbcdb cdecdec defdefd
    Oh my, how did you conjure this up? Inside knowledge or just worked out the crypt?

    Regards, Paul.

    Leave a comment:


  • Maxpower3
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Originally posted by inflex
    Removing the password is trivial.

    I took a file which has a password in it, and removed the string that occurs after the .G34S string and set the string length byte to 0. Now is readable in TeboView 4 without requesting the password.
    For decoding Customer ID

    0000000 1111111 2222222 3333333 4444444 5555555 6666666 7777777 8888888 9999999
    efgefge fghfghf ghighig hijhijh ijaijai jabjabj abcabca bcdbcdb cdecdec defdefd

    aaaaaaa bbbbbbb ccccccc ddddddd eeeeeee fffffff ggggggg hhhhhhh
    3453453 2342342 1231231 0120120 9019019 8908908 7897897 6786786

    iiiiiii jjjjjjj kkkkkkk lllllll mmmmmmm nnnnnnn ooooooo ppppppp
    5675675 4564564 vutsrqp wvutsrq xwvutsr yxwvuts zyxwvut kzyxwyu

    qqqqqqq rrrrrrr sssssss ttttttt uuuuuuu vvvvvvv wwwwwww xxxxxxx
    ikzyxwv mlkzyxw nmlkzyx onmlkzy ponmikz qponmlk rqponml srqponm

    yyyyyyy zzzzzzz
    tsrqpon utsrqpo

    First Number
    0 e
    1 f
    2 g
    3 h
    4 i
    5 j
    6 a
    7 b
    8 c
    9 d

    a 3
    b 2
    c 1
    d 0
    e 9
    f 8
    g 7
    h 6
    i 5
    j 4
    k v
    l w
    m x
    n y
    o z
    p k
    q l
    r m
    s n
    t o
    u p
    v q
    w r
    x s
    y t
    z u



    75785zn
    badcaps
    Attached Files
    Last edited by Maxpower3; 11-20-2021, 07:55 AM.

    Leave a comment:


  • inflex
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Anyone want to throw a theory on why some of the TVW files have this extended sort of header before the first labelled layer?

    Seems there's a few occurrences of the 0 3 2 1 sequence in it.

    This is the Gigabyte file that was attached in a slightly earlier post here in this thread.
    Attached Files

    Leave a comment:


  • mmu
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Oddly the Gigabyte file didn't open in TeboView 4 even after stripping the password… But forcing the previous string to "G34…" stopped it from complaining about license :-)
    Opened a PR with a python tool to strip the password.

    Leave a comment:


  • inflex
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Removing the password is trivial.

    I took a file which has a password in it, and removed the string that occurs after the .G34S string and set the string length byte to 0. Now is readable in TeboView 4 without requesting the password.
    Attached Files

    Leave a comment:


  • RethoricalCheese
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    https://www.badcaps.net/forum/showpo...&postcount=354

    Leave a comment:


  • inflex
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Originally posted by DerekChen65535
    Thanks for that - at least the outline renders on that one
    Attached Files

    Leave a comment:


  • DerekChen65535
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Attached Files

    Leave a comment:


  • RethoricalCheese
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Yeah, looks like these files were meant to be opened by boardviewer, not teboviewer.

    Leave a comment:


  • inflex
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Originally posted by RethoricalCheese
    There are different teboview programs. The ones which are password protected in one, are not in the other one.

    Which of the files had the password? I think I can send you the right program, which doesnt ask for password.
    Boardviewer doesn't let the password stop it, but the official Teboview v4 does.

    Lenovo\ Legion\ Y540-15IRH\ -\ NM-C221\ REV0.1\ Boardview\ /NS-C222.tvw

    It's just more amusing that it's not really doing any real protection, and in honest though, I'm *glad* it's not.

    On the upside, I've already worked out a few more of the header fields because of those new files, thanks.

    Leave a comment:


  • RethoricalCheese
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    There are different teboview programs. The ones which are password protected in one, are not in the other one.

    Which of the files had the password? I think I can send you the right program, which doesnt ask for password.

    Leave a comment:


  • inflex
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Found something interesting, well, two things;

    1) the loose 1-byte 0-value in the header sandwiched between two other strings is actually, as it should have been expected, an empty string. One of the new files I tried broke my parser and it was because there was a 3rd string in there.

    2) Some TVW files are password protected when used in the official Teboview program, but the contents are not in any way encrypted that I can tell; it's akin to stopping people from getting in to an open space by placing a doorway in their face. Very interesting.

    Leave a comment:


  • inflex
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    HeLP - Need MOAR Teboview files. Gotten to the point now that I need more files of different sources so I can cross-check/differentiate various flags/bytes.

    Big or small - you can email them to me if you prefer, pldaniels@gmail.com

    Leave a comment:


  • mmu
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Yay!

    Leave a comment:


  • inflex
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Interestingly, our sample file had a more complicated outline routing system. There's some segments that are prefixed with 0x08 instead of 0x0A, and with those you read only 2 int32's after the tool int32, and there's no trailing 0-value uint32.

    I'll add that in to the documentation later.

    I'm sure there's other little traps like that out there but we'll find them in due time.
    Attached Files

    Leave a comment:


  • inflex
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    I present to you... the very first image for TeboView decoder for FlexBV.

    This is actually a board outline for the Lenovo X240 Yoga board.
    Attached Files

    Leave a comment:


  • inflex
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    I made the THREAD change on my own build.sh, so at least that's one file fixed

    Leave a comment:


  • inflex
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Originally posted by mmu
    Great, let me know if you need more.
    Many thanks. I'll PM you in a bit after this.


    Yeah, mingw works not too bad, I recall building VLC with it (quite slow though).
    I think most of build.sh can probably be done right in CMake though.
    Likely so - for me, it's a case of "It still works, I'm not going to break it"

    I already proposed a patch in my Haiku PR. :-)
    I saw that come through this morning - it'll likely be piernov who handles that as I am very much hands-off with OBV now. Put the years in to get it to a level and did the promotional work with/via Louis Rossmann, but after that is about when I forked off with FlexBV. I still push back things like file formats and bug fixes but aside from that I keep a fair distance now.

    Leave a comment:


  • mmu
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Originally posted by inflex
    Thanks for the PR. I've already pushed in some small changes too (the 3-2-1 sequence appears to be a header/lead-in as opposed to a suffix).

    All scrappy at the moment but it's definitely workable now for generating the source code.
    Great, let me know if you need more.

    Originally posted by inflex
    As for OBV, the build.sh is meant for linux and macOS, we don't really build on windows any more because it was making the development cycle too slow and we ran in to show-stopper incompatibilities when working with gcc as well as VS that just made everything a nightmare. Subsequently the build for windows is just done on linux with mingw64; makes everything vastly easier when it comes to cross-platform development.
    Yeah, mingw works not too bad, I recall building VLC with it (quite slow though).
    I think most of build.sh can probably be done right in CMake though.

    Originally posted by inflex
    As for why the /proc/cpuinfo ... not sure what it's for, probably to determine the flags for the build within CMake.
    Yes, it's a classic idom to detect the number of cores to do parallel builds, except it's very Linux-specific while there's a much simpler and portable method. I fixed this in MuseScore some years ago. I already proposed a patch in my Haiku PR. :-)

    Leave a comment:


  • inflex
    replied
    Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

    Thanks for the PR. I've already pushed in some small changes too (the 3-2-1 sequence appears to be a header/lead-in as opposed to a suffix).

    All scrappy at the moment but it's definitely workable now for generating the source code.

    As for OBV, the build.sh is meant for linux and macOS, we don't really build on windows any more because it was making the development cycle too slow and we ran in to show-stopper incompatibilities when working with gcc as well as VS that just made everything a nightmare. Subsequently the build for windows is just done on linux with mingw64; makes everything vastly easier when it comes to cross-platform development.

    As for why the /proc/cpuinfo ... not sure what it's for, probably to determine the flags for the build within CMake.

    Leave a comment:

Related Topics

Collapse

  • ahmedtou
    HOW CAN I UPDATE HL-DT-ST BD-RE GGW-H20N XA02
    by ahmedtou
    Hi everyone,
    help me please


    I have an HL-DT-ST BD-RE GGW-H20N with ROM version: XA02.




    When I tried to burn a 25GB Blu-ray disc using ImgBurn, I got an error.
    I will share all the details with you, including the disc information.




    Code:
    HL-DT-ST BD-RE  GGW-H20N XA02 (ATA)
    Current Profile: BD-R
    
    Disc Information:
    Status: Empty
    State of Last Session: Empty
    Erasable: No
    Free Sectors: 12,219,392
    Free Space: 25,025,314,816 bytes
    Free Time: 2715:27:17 (MM:SS:FF)
    Next
    ...
    08-27-2025, 08:49 AM
  • m1ch43lzm
    Notice to users of XGecu TL866II Plus / T48 / T56 / T76 programmers regarding BIOS backup file size
    by m1ch43lzm
    Hi everyone
    I noticed on the Xgpro software the BIOS backup files have extra bytes at the end when reading some chips, this is because the Xgpro software also reads the OTP region of those flash chips, and by default will append that region to the saved file
    Programmer models: XGecu TL866II Plus / T48 / T56 / T76

    Example: GD25LQ128D (1.8V), IC size is listed as 0x1000000 Bytes (16777216 bytes) + 0xC00 bytes, those extra 0xC00 bytes will be appended to the end of the saved file by default, resulting in a file size of 16780288 bytes
    There's also an extra OTP Secu.R...
    09-06-2025, 05:47 PM
  • to5it0
    Need Clean BIOS/EC Bin File for Lenovo ThinkPad Yoga 11e 2H1703-27220F Rev. A Marked as U2501 on the motherboard.
    by to5it0
    Need Clean BIOS/EC Bin File for Lenovo ThinkPad Yoga 11e - Stuck with 0275 Error CMS

    Hello everyone,

    I am attempting a repair on a Lenovo ThinkPad Yoga 11e that is currently stuck at boot with the error: "0275 error CMS" even after setup new bios battery and will not allow me to enter the BIOS/Setup.

    This is a critical issue that I believe requires flashing the BIOS chip directly using a programmer (e.g., CH341A/RT809H), as standard software updates or resets are not possible.

    I have opened the laptop and identified the main BIOS chip...
    10-24-2025, 01:35 AM
  • testaccgta
    Unable to verify IC or write/erase/flash BIOS file to XMC QH128AHIG SPI chip using NeoProgrammer/AsProgrammer
    by testaccgta
    Hi, everyone!

    I've recently acquired two brand new SPI chips to replace the one currently in my Acer A514-54G laptop MB (FH5AT LA-K092P). The reason why I'm replacing the current SPI chip is because I had some difficulties with a third-party IT assistant who pretty much lacked the soldering skills and ended up destroying the current SPI chip soldered to my MB from factory.

    I've decided to do this on my own because I spent the past month or so learning some soldering skills and BIOS modding through Badcaps and WinRaid forums, hence the attempt. I've also chosen to buy...
    09-01-2024, 08:24 PM
  • Forest79
    Lenovo ThinkStation P520 BIOS file needed
    by Forest79
    Hello,

    I got a Lenovo ThinkStation P520 (Type 30BF) from a friend, asking me for a repair. Windows 11 offered a firmware upgrade as an optional update, and it failed.
    The emergency flash procedure from the hardware manual has also failed. So, I asked an acquaintance with better skills to flash the BIOS directly.

    However, the chip (a Macronix MX25L25673GMI-08G) has a size of 32 MB, and the BIOS file from the Lenovo website (extracted with UEFITool) has a little more than 16 MB. Thus, the software my acquaintance used (SiberiaProg v1.45, with a CH341A Programmer)...
    07-23-2023, 07:39 AM
  • Loading...
  • No more items.
Working...