How to dump the bootloader from UA65ES8000

[E3V3A]

Ok, success at last! The problem was "2".

Looking at:

Code: Select all

shell>cat /proc/iomem
...
40200000-54afffff : System RAM
  40225000-404f6fff : Kernel text
  404f8000-4057da1b : Kernel data
a4e00000-afffffff : System RAM
...

we see that kernel "code" region is in what is referred as "Kernel text", so to avoid getting mostly zero's, I dumped using this:

Code: Select all

readmem 0x40225000 0x100 /dtv/usb/sda1/zmema4.bin

This worked, so HERE is the result.

Or in HEX:

SpoilerShow

Code: Select all

$ hexdump -C zmema4.bin
00000000  0d c0 a0 e1 30 d8 2d e9  04 b0 4c e2 00 40 a0 e1  |....0.-...L..@..|
00000010  0d 00 a0 e1 7f 2d c0 e3  98 30 9f e5 3f 20 c2 e3  |.....-...0..? ..|
00000020  14 00 92 e5 90 20 9f e5  00 21 92 e7 02 50 93 e7  |..... ...!...P..|
00000030  02 10 83 e7 66 a3 00 eb  80 30 9f e5 00 30 93 e5  |....f....0...0..|
00000040  03 00 54 e1 0b 00 00 3a  74 00 9f e5 73 8d 00 eb  |..T....:t...s...|
00000050  00 00 50 e3 02 00 00 0a  68 00 9f e5 04 10 a0 e1  |..P.....h.......|
00000060  45 70 09 eb 60 30 9f e5  00 20 93 e5 01 20 82 e2  |Ep..`0... ... ..|
00000070  00 20 83 e5 05 00 00 ea  04 00 a0 e1 5e 50 01 eb  |. ..........^P..|
00000080  00 10 a0 e1 0c 30 90 e5  04 00 a0 e1 33 ff 2f e1  |.....0......3./.|
00000090  a6 a2 00 eb 0d 10 a0 e1  7f 2d c1 e3 14 30 9f e5  |.........-...0..|
000000a0  3f 20 c2 e3 14 10 92 e5  0c 20 9f e5 01 21 92 e7  |? ....... ...!..|
000000b0  02 50 83 e7 30 a8 9d e8  e8 42 02 c0 a4 28 30 c0  |.P..0....B...(0.|
000000c0  80 94 30 c0 e4 4f 28 c0  81 c2 2b c0 a0 b7 31 c0  |..0..O(...+...1.|
000000d0  0d c0 a0 e1 f0 d8 2d e9  04 b0 4c e2 88 d0 4d e2  |......-...L...M.|
000000e0  40 30 90 e5 00 40 a0 e1  3c 50 90 e5 20 20 13 e2  |@0...@..<P..  ..|
000000f0  1f 30 03 e2 02 10 a0 13  04 10 a0 03 13 00 53 e3  |.0............S.|

@xorloser: This should help you navigate around my memory...

[xorloser]

Ah you mean you tried to read the address (0x40000000) in my example? That was just to show how to use it and what the expected output should be. Anyway that dump you got was just what was needed, I now know where in memory it is loaded and so I can look at adding support for your kernel.

[xorloser]

E3V3A: Ok attached is updated source and binaries that should support your kernel.
Use it like this:

Code: Select all

mmcdump /dev/mmcblk0p0 /tmp/bootloader.bin

Hopefully it will work fine first go.
I take no responsibility if it kills your TV

[E3V3A]

Thanks! Very nice.

I take no responsibility if it kills your TV :)

However, I only have one TV and I need it for the next few days, so I'm reluctant to risk a brick at this time. Perhaps some other friendly TV developer who have more than one, could try this and confirm it works? I've looked at the code and can't see why it would not work, but I'm unsure about what the patch actually does. If this works, I might have some other useful patches as well...

Also, I'm looking to rewrite part of the code for wider support . This could be very useful.

[xorloser]

If you weren't going to run it then why did I waste my time looking into it for you?! Next time just say so from the start.

The patches it does could quite easily be automated, but the reason I don't do so is so that I can first verify it by looking at a particular kernel to ensure the patches are correct before including them in the tool. If you don't know what the patches actually do then you aren't really in a position to "see why it would not work" or to "rewrite part of the code for wider support". Besides automating the patching there isn't much more to do for wider support, it already uses a patch table at the start of the source so that all you have to do is add a new entry to the table. I guess you could put the patch table into an external file, but that just allows adding patches without recompiling.

Did you try any of the rooting methods? They all come with the standard if it bricks, it's your problem disclaimer.

[E3V3A]

If you weren't going to run it then why did I waste my time looking into it for you?! Next time just say so from the start.

No need to get insulted! Like I said, I'm going to run it, but not right now. That's all. And you certainly didn't waste your time, since it has been very helpful for me to understand a whole bunch of things. And in addition I'm sure there a several dozens of people, passively following this thread.

... If you don't know what the patches actually do then you aren't really in a position to "see why it would not work" or to "rewrite part of the code for wider support". Besides automating the patching there isn't much more to do for wider support, it already uses a patch table at the start of the source so that all you have to do is add a new entry to the table.

I think we have a slight communication problem. I'm talking about something different, that I'm working on. As you now, I already ran the SmartReport stuff and that works just great and was what I needed. I don't need the bootloader code right now, but that same code can be reused to get other useful things that I'm looking into. I'm not discussing this in public, so send me a PM (or send me an IRC channel where I can find you) if you want more details. When and if I have something of interest to post, I will do so. Cheers!