YT YouTube2Text

YouTube2Text → Transcripts → ЯНДЕКС-С-ТАНЦАМИ. Оживить ТВ Станцию: UART, дамп и тупик!

ЯНДЕКС-С-ТАНЦАМИ. Оживить ТВ Станцию: UART, дамп и тупик! — Transcript

by Отто Вайнингер · 11,246 words · 1,983 segments · language en · Watch on YouTube

Open in transcriber Summarize with AI Download SRT/VTT

Full transcript

0:02Hello, dear subscribers and guests of
0:04the channel. Otta and Kostya are on the
0:07line. It’s been a while. I'll tell you
0:10right away what you'll see today. Today
0:12there will be a TV repair.
0:15Well, a "TV", I wouldn't even call it a
0:18TV in the first place.
0:20You’ll understand from the context what
0:22we’re talking about now.
0:24The backstory.
0:26We have a good colleague who works
0:29professionally in TV repair, so
0:32programming is also not a problem for
0:35him.
0:36He calls me, or "calls" me, Kostya will
0:39correct me,
0:40>> calls,
0:40>> doesn't call. Anyway, he calls and says
0:43: "Listen, there’s this device that
0:45won't turn on at all.
0:47Will you take the repair?" I say: "
0:49What’s the matter, can't you handle it?
0:52" Greetings to you, Alexey.
0:54But he says: "You know, I opened the
0:57cover,
0:59and I closed it right back up." I say: "
1:01Why is that?" He says it just scared him
1:04.
1:05And he says, "I don't even want to look
1:07at it, you guys should do it and maybe
1:10film a video."
1:12Well, he brought us some great content.
1:15Uh-huh.
1:34And I say: "What kind of TV is it anyway
1:36? What is it at all? What's the deal?
1:37What is this thing?"
1:41And then he named it for me.
1:44I was like Professor Philip Philipovich
1:47Preobrazhensky in that moment, I just
1:49yelled like this
1:50>> like a knife to the heart. Excellent.
1:54Bring it here right now. Right now.
1:58>> Look, gentlemen, Kostya, show it in
2:00close-up.
2:02Damn it, the electronics we deserve.
2:05This, gentlemen, is not a TV, it's a
2:08Yandex Station.
2:10Show this abbreviation, please, Kostya.
2:13Yandex 0092.
2:18Yandex TV Station.
2:21Pay attention, please,
2:25what is written here?
2:27Manufacturer, Alice Laboratory,
2:29Moscow-Russia, but made in China.
2:31Warranty 1 year, service life 2 years.
2:38So, just to note, the production date is
2:43September 2023.
2:47Well, in general, that's the production
2:48date.
2:49It was clearly sold in 2024 or something
2:51like that.
2:53The result.
2:56Back in the summer of this year, it was
2:59summer, it died completely.
3:01How it happened according to the owner.
3:04It just didn't turn on one morning.
3:07And it didn't just not turn on in the
3:08sense that it hung on some screen or
3:10anything.
3:11It didn't turn on at all.
3:15An interesting case. And it's an
3:16interesting case, I'll explain why.
3:19Two years ago, if someone had asked me,
3:22and us technicians are often asked by
3:25clients and acquaintances, which TV
3:28would you recommend buying today?
3:33Honestly, I try not to give anyone any
3:35advice at all, because it’s the most
3:37thankless task.
3:39All that nonsense will backfire, and the
3:42shadow will fall on you.
3:44I’ve had the experience: I recommended a
3:46TV to someone, and it died 9 days later
3:48.
3:50And it wasn't that I was incompetent or
3:52anything. I really tried to apply all my
3:54knowledge.
3:55Well, it’s just one of those situations
3:57.
3:57But anyway, that’s just poetic filler, a
3:59digression.
4:01But if you had asked me 2 years ago, "
4:02With the money you have now, what TV
4:04would you want to buy?"
4:06I would have said, "Damn, the Yandex TV
4:08Station is an interesting model." What’s
4:10the deal?
4:12These are so-called subsidized TVs.
4:17It’s a situation where for little money
4:21you get more of a quality TV, but with
4:24one caveat.
4:27It has all this subscription stuff, and
4:29, well, in essence, you’re hooked into
4:31some kind of micro-loan, or whatever you
4:33call it.
4:35Basically, they give you the device—the
4:38hardware itself—at a discount, and then
4:41you pay for it over a longer period.
4:44>> You're always in debt,
4:46>> yeah, you're always indebted, that kind
4:48of thing.
4:51I don’t remember, with the Americans, I
4:54think, yes, there’s that Amazon thing
4:56where they give away a TV for free, but
4:58you’re obligated to watch ads. Alright,
5:01we’ll talk more about that later.
5:03Specifically, this device right here.
5:04Look, let’s move on to the patient.
5:06Kostya, show it. What a huge beast. 50
5:09inches. Well, not huge, just normal. How
5:12does it behave? I won’t drag this out.
5:15Anyway, let’s go. What do we have here?
5:19Look. According to the wattmeter.
5:22Well, it's in some standby mode,
5:24consuming about 2 watts. God knows what
5:27it’s doing. Uh-huh. Moving on. Let’s
5:29look. I already took the cover off so I
5:32wouldn’t drag this out. Kostya and I
5:34were discussing how to film this video
5:36today.
5:37Forget about all those covers and screws
5:39.
5:40For anyone who’s going to take it apart
5:42, here’s my advice right away.
5:45Right here, this bottom panel is
5:47attached. There are these rubber pads,
5:50you won't even see the screws there, and
5:52you might break it. Well, actually, as
5:54happened here already. In short, there
5:57are these little rubber nubs. Well,
5:59alright, you’ll figure it out. That’s it
6:02for disassembly. To hell with it. When
6:04we now...I wonder what he saw there that
6:07was so scary? He says, "I just saw the
6:10interior," he says, "and I closed the
6:12cover and that was it.""And ran away
6:14from it, why bother?"
6:16She says it won't turn on. Look, I'm
6:18pressing Power.
6:20Kostya, show them, there's absolutely no
6:22reaction on the wattmeter. There's no
6:24reaction here, no standby mode at all.
6:29Here.
6:31I'll unplug it now and flip it over.
6:33Let's take a look inside.
6:35This is trash. This, ladies and
6:37gentlemen, is trash.
6:38Those of you used to fixing Chinese TVs
6:41are going to be shocked.
6:44Bam.
6:47Well, go ahead and examine it, for
6:49heaven's sake. Well, obviously, the PSU
6:51here is nothing interesting. What is all
6:53this?
6:54Why is there so much of it? It's simple
6:57.
6:58This TV features so-called adaptive
7:01backlighting.
7:05Unlike all that Chinese junk, there are
7:08192, I think—I won't lie to you—
7:10something like that, just a ton of LEDs
7:13here.
7:15You might think:
7:18"Why go to all that trouble?" Yes,
7:22it's a good TV, awesome backlighting,
7:25reliable, yes, everything is simple.
7:28In reality, the panel here is complete
7:30garbage. Its contrast ratio is, well,
7:33terrible. So, to make something
7:36watchable, the guys implemented adaptive
7:40backlighting. But you can read about how
7:43this whole thing works.
7:45Basically, there are a lot of dimming
7:49zones, and thanks to this crazy
7:52contraption processing the image, the
7:56black color ends up looking a bit better
8:00.
8:01I mean, not that greyish look you're
8:04used to seeing on regular Chinese TVs,
8:07but here, everything is much better.
8:09Moving on.
8:11They're quite decent. There are even
8:14speakers that are like a subwoofer.
8:17I mean, they are genuinely two-way.
8:20Alright, let's look at the mainboard
8:23hardware.
8:25But I'll tell you right away so we don't
8:27drag this out.
8:28Under the hood, there's a fairly
8:31powerful processor plus 3GB of RAM.
8:35And notice, it's DDR4 RAM.
8:39That's no joke.
8:42And this is why I told you it’s not a TV
8:45. Not at all.
8:48Kostya, show the mainboard closer.
8:50Do you see a tuner anywhere here?
8:54It's not here.
8:57When I—well, you understand—spent some
9:01time messing with this TV, I gathered
9:04some information.
9:08We have a lot of people in the comments
9:11, in reviews on DNS and other platforms
9:14, writing: "Guys, please tell me, where
9:18do I plug the antenna into this TV?"
9:22Well, you don't.
9:23It's not there. This is not a TV. It's
9:27some kind of, damn it, fifty-inch tablet
9:29or something. What should I call it?
9:31What is this thing?
9:33>> A gadget.
9:35In short, it’s some kind of creature
9:38that is definitely not a TV.
9:41You can only consume content through
9:43these standard Yandex features.
9:46Alice is here, there are six microphones
9:48installed. She listens to all of this
9:51and keeps an eye on you. Well, we'll
9:53skip that for now. We haven't even
9:55started this piece of hardware yet.
9:59And, honestly, I have no idea if we'll
10:00get it running in the end or not.
10:04Maybe we'll make all those baboon-haters
10:06happy.
10:08"Ah, finally, you didn't do a damn thing
10:09."
10:10>> Turn it off and replace the matrix.
10:13>> Yes, by the way, theoretically you can,
10:15but we'll talk about that a bit later.
10:18Those matrices used to come in Xiaomis.
10:21But then we'd lose all this adaptive
10:23stuff and all this beauty. Anyway, since
10:27this is Yandex with its dances, well,
10:31let's dance then.
10:33Starting from scratch, from the power
10:36supply. I've prepared for the shoot.
10:39Kostya, I'm already so sick of this
10:41device. I'll go get the multimeter now,
10:43just to be basic.
10:45And I'll probably turn it around, or
10:47maybe I won't. Off to get the multimeter
10:49.
10:50>> Let's get to it.
10:51>> Well.
10:53There. And at this stage, I want to tell
10:56you one thing.
10:58When I started looking into the repair
11:01practices for these Yandex stations, I
11:03was extremely surprised.
11:06There is zero info.
11:09The only thing that popped up was that
11:11sometimes their screens die, like in
11:13Samsungs where they get lines, and
11:15people start gluing the ribbons and all
11:18that, but regarding internal components
11:20, firmware, or power-on issues, there is
11:23absolutely zero info.
11:26It's as if, you know, it's all weighed
11:30down by the reason I say, "Bring this TV
11:33to me."
11:35Well, because the TV is relatively new,
11:38and we, as repairmen, don't have enough
11:41practice working with them yet. So I'm
11:45thinking, what should I do with this
11:46mainboard? Let's go by the classics and
11:48start from the beginning, shall we?
11:50Let's clap. Let's go. First things first
11:53. Well, something should be coming in
11:55from the power supply here. I don't even
11:57know where to right now.
11:59Okay, let's go.
12:04Where are you, power?
12:07Anybody home?
12:12Oh, I can't seem to find the power rails
12:16here.
12:23Ah, well hello there. That's it, we have
12:26power. 15V has arrived. So the mainboard
12:30is powered. There is consumption. We saw
12:32that with the wattmeter. Let's check the
12:35main power rails at the inductors. So
12:37what do we have from the input, let's go
12:39.
12:40Pop. Let's see what's there, Kostya.
12:45Strange stories. It's zeroed out. Well,
12:47alright. Let's see what this is.
12:52Aha.
12:531.2 V. But that's likely the RAM power
12:58supply.
13:00As I already told you, according to the
13:03internet, it's DDR4.
13:06Alright. What is this inductor?
13:09Uh-huh. 5 V is generated. Excellent. I
13:13predict 3.3 V on this inductor.
13:16That's right. 3.3 V. So, let's go see
13:20what else we have here.
13:280.9 V. This is likely the CPU core
13:30voltage.
13:32And there's some other 0.8 V source here
13:34too. Lord knows what that is. Anyway,
13:36here is what I want to say. The board is
13:39powered. Why should we guess? We are
13:41experienced people, aren't we?
13:45We know how to diagnose all these little
13:48beasts via the so-called debug
13:53or also called UART.
13:58Well, the thing is, it's impossible to
13:59do from the outside. There's no special
14:01connector for that here.
14:04I sat down and started studying it.
14:07I'll put on my glasses, because this is
14:09just crazy.
14:11Kostya, show it really close up. I'm
14:12going to probe around.
14:14First of all, I find a debug port right
14:16here,
14:19an actual connector. See? I have no idea
14:21what kind of debug this is. And even if
14:24that were it, don't look there, there's
14:27another debug here.
14:31It's labeled right there. Who are you,
14:33anyway?
14:36And so, I guessed and guessed.
14:38I think looking for a hint on the forums
14:41—nobody has any idea at all.
14:44I looked for a long time. It turned out
14:46, actually, gentlemen, look where the
14:49debug lives in these TVs. Remember it,
14:51I'm showing you once. Kostya, please
14:54show this. The debug lives here. Right
14:57here, you see?
15:02Now let's study this part in general.
15:03What is this?
15:05When I started deciphering the startup
15:08logic, what kind of processor is this?
15:11Is this actually a processor?
15:13Well, I don't remember which one it is
15:14anymore, it doesn't really matter.
15:17I thought maybe it's something like the
15:20"Welltrend" chip in Samsungs, but no.
15:23Anyway, I won't bore you.
15:27This took me a hell of a lot of time.
15:29But I'll simply explain it to you.
15:32This processor works specifically with
15:35this board.
15:37Kostya, show this board, okay? This big
15:39hunk of metal.
15:42These are the drivers that form our
15:44backlight, that is, the dimming zones.
15:49So this whole brain—it's like 400 MHz I
15:53think, it's quite a snappy processor—
15:56it's optimized for only one thing: to
16:00process data from the main processor
16:03about the image and control these three
16:07drivers, which in turn control the LEDs
16:10.
16:11You need to grasp one thing, gentlemen.
16:15Tell me, please, you don't just have
16:18these things here, as we call them,
16:20strings, strips that light up.
16:23You have a personal line for each LED
16:27here, through which these drivers light
16:31them up. See what kind of ribbons are
16:34going out.
16:37Cool, cool, right? We've seen this in
16:40top-tier TVs.
16:42We had a video there, I don't know,
16:44maybe I'll leave a screenshot, maybe not
16:45, where there was RGB backlighting in
16:47general.
16:49But anyway, that's not the point right
16:51now.
16:51Our main processor, which lives under
16:54this large plate, isn't starting up.
16:59So what's next?
17:02Since we've figured out that there's a
17:03debug port here, I'm hooking up our
17:05dongle.
17:09If anyone has questions now, a
17:12screenshot from our channel will appear
17:15somewhere here on the side; the video
17:18was titled something like "Master's
17:22Secrets: How to Diagnose Any TV Port."
17:27If you're interested, go watch it again
17:29. Everything is described there in full
17:32detail. But in short, it's clear. Show
17:35that connector again.
17:37I'll take a look at it too.
17:40It says GND here, which means ground.
17:45Well, it doesn't really matter, you can
17:47hook onto any point. Here's RX, here's
17:49TX.
17:50I just took it quickly for my own
17:52convenience. I didn't want to struggle
17:54with it here. I just soldered it from
17:56the backside.
17:57Now we'll connect with the laptop and
18:00see what comes of all this.
18:02Let's go.
18:05So, gentlemen.
18:07Let's launch any terminal emulator.
18:09Secure.
18:12Connecting.
18:16There we go, power is on.
18:20Up.
18:23Show it closer so people can see the
18:25details clearly.
18:29Watch what's happening now. Just a short
18:32log like that, and that's it.
18:34And it all repeats. Let me explain
18:38briefly. Maybe some people didn't know
18:40this at all. Maybe I missed this before
18:43.
18:44This practice is starting to really
18:46scare me.
18:47I'll explain why. The thing is, what is
18:50actually happening right now.
18:53Essentially, it's the same story that
18:55happens, well, on computers, for example
18:58, on laptops, right, regarding the
19:00microprocessor.
19:04Well, that's a rough explanation, but
19:06nonetheless, it's now called a
19:08system-on-a-chip, because there are
19:10cores, a video core, and in this
19:12specific TV, there is also an APU for
19:14working with artificial intelligence.
19:17It's a quite powerful processor. We'll
19:19see it a bit later. Well, hardware-wise
19:23, it's a really peppy TV.
19:25The TV is a peppy Yandex Station tablet
19:29.
19:30I thought for a long time about what
19:32kind of naming that was, but after
19:33messing with it for a couple of weeks, I
19:34understood the naming.
19:36In principle, it's all correct. So, it's
19:39just quite powerful.
19:41And even if it wasn't a cool one, the
19:43principle is roughly the same. Just like
19:45on a PC.
19:46Some microcode loads, then the BIOS,
19:48then it moves on to the actual operating
19:50system.
19:51What is happening now?
19:53You can look at our previous video about
19:55Xiaomi, right, Kostya, I think we talked
19:58about it.
19:59Well, it's roughly the same story there
20:01.
20:02An extremely short log, meaning a piece
20:05of code from the processor starts, tries
20:09to reach the bootloader located on the
20:12eMMC chip, and gets nothing.
20:16And it thinks, "Aha, well, maybe it's
20:18just a coincidence, a power glitch, or a
20:20glitch on some data bus."
20:22So it starts repeating this process all
20:24over again.
20:26And that's it. And it ends up spitting
20:27out this nonsense.
20:30If our eMMC were at least somewhat alive
20:32, well, there would be some sort of
20:34intelligible log, and it would cut off
20:36somewhere, something would have happened
20:38.
20:39But when we see nonsense like this, our
20:43experience tells us that in 95%of cases
20:47, the chip has just died completely.
20:52Meaning it isn't even being detected by
20:55the TV's own microprocessor.
20:58Damn. Well, in general, TVs, and that's
21:02bad, gentlemen.
21:04Especially in TVs similar to this one.
21:07The fact is that
21:12these TVs likely have a bunch of keys
21:15and all sorts of bindings to these
21:17Yandex servers.
21:20To give you an idea, the repair of this
21:22TV started a month ago.
21:25I've been messing with it for a month
21:26already.
21:27And back then, there wasn't even this
21:29situation with the Yandex data centers.
21:32And yet, I already understood that if we
21:36didn't pull the original firmware from
21:39here now, it would be a total disaster.
21:45You'll see this whole story now, maybe
21:47not all at once, so pour yourselves some
21:50tea.
21:52One still needs to observe safety
21:55measures.
21:57Get ready, pour some with sugar, because
21:59your brain will have to work now. There
22:01.
22:02Anyway, alright, let's go. What do we
22:05see?
22:06Our processor doesn't see the eMMC at
22:09all.
22:09Or is this sad?
22:12We need, so you understand, to intervene
22:17as little as possible, try not to heat
22:21the processor or the chip, and somehow
22:25try to read what's left on this eMMC.
22:34And do you know what the saddest part is
22:36? The TV is only 2 years old.
22:39How does that happen? Look at the trend
22:42.
22:43The 2024 Xiaomi worked, lasted 2 years
22:46and crapped out, but at least the
22:48firmware was simpler there.
22:52The Yandex one worked for 2 years and
22:55crapped out.
22:59This is some kind of unhealthy situation
23:00. Konstantin Petrovich, admit it. He
23:03supported it.
23:05>> There.
23:06Oh well. What are we doing now?
23:10We’re removing this mainboard, going to
23:14the computer, and we’ll try to carefully
23:18connect via the ESP protocol without
23:21desoldering the chip.
23:26That means we’ll neatly solder wires to
23:28the test points so we don’t have to
23:30remove the chip or heat it up, because
23:33it’s already, damn it, apparently sick
23:37and all that.
23:39And we’ll try to read as much data from
23:43it as possible.
23:45Well, let’s go, let’s give it a try.
23:49Gentlemen, before we continue, a brief
23:51message.
23:52Thanks to everyone supporting our
23:54channel. Only thanks to you does it
23:57continue to exist. You know that there
23:59is no monetization on YouTube right now
24:01. The economic situation in our country
24:04is extremely unstable.
24:07And only your donations allow this
24:10channel to live and make new videos like
24:13these.
24:14And there will be more, if all goes well
24:17.
24:18You can send your donations using the QR
24:21code here.
24:23This is Donation Alerts. Available from
24:25any country in any currency. It is safe
24:28. These funds don't go directly to us in
24:31the Russian Federation; they go to an
24:32intermediary.
24:34We then receive them from the platform.
24:37Thanks to everyone who supports us. Also
24:39, if it's hard for anyone to scan this
24:42QR code, there will be a link in the
24:44description of this video, as well as in
24:47the pinned comment.
24:49Follow the link to support me,
24:51Konstantin, and our entire huge team.
24:55Thank you for your attention. Let’s
24:57continue.
25:01So, gentlemen, here is the moment. I
25:04basically cut out the lion's share of
25:06the recorded material. We took a look
25:08and realized that otherwise, this would
25:10drag on for a long time.
25:11So, I'm going to breeze through it.
25:13Let’s go. The heatsink. This heatsink
25:18here, unlike those Xiaomi ones, look, is
25:20smartly designed with clips. You just
25:22need to press them. That’s it, you’ve
25:24removed it.
25:25Let’s take a look at the internals. Look
25:27at that beauty.
25:29You see the processor and everything
25:31looks professional. The RAM is placed
25:34externally
25:36and right next to it is the eMMC. Right
25:38, let’s talk quickly about the processor
25:40. It’s an Amlogic T982.
25:43To give you an idea, four A55 processor
25:46cores, that’s already good.
25:49Mali-G 52 graphics processor.
25:52But look, this processor also has a
25:55built-in NPU, and it’s an AI accelerator
25:59with 2.6 teraflops of performance for AI
26:03tasks and image processing. There you go
26:06.
26:08Meaning, all these things that Alice
26:10processes, plus whatever else they’re
26:13monitoring, all of that is handled not
26:15just by the central processor, but also
26:17by this additional NPU.
26:20Support for Android 11. That’s important
26:24, mind you.
26:28Alright, what did I cut out?
26:31Well, you see, here, so you understand,
26:34I’ll try to attach a larger image now.
26:39This is a 32-gigabyte Samsung chip, an
26:42awesome microchip.
26:46There. And it just went and kicked the
26:49bucket. Look, I’ll show you the picture
26:52quickly now. Stas, show it briefly.
26:56And after that, when you switch the
26:58camera to me, I’ll pin it in high
27:00quality so people can get a good look.
27:03Look, we need to take a programmer, be
27:07it an ENT, right, with the ability to
27:10solder via the ISP protocol, or an RT809
27:13, it really doesn't matter.
27:17Even a UFPI, right?
27:20So, I'll use this picture, bam, I'll
27:22pause it right now, this picture for 3
27:25seconds.
27:27If you can't make it out immediately,
27:29you can take a screenshot.
27:30Everything is written here in detail. So
27:32, all connections are made on the back
27:35side of the board.
27:37That is, the D0 bus, clock, cmd, power,
27:42and all that. But I draw your attention
27:46to this, here's the thing: the CPU can
27:48interfere with the operation and prevent
27:51you from seeing your chip.
27:54For that, you'll need to look here where
27:56there's a quartz crystal.
28:00You'll need to carefully short it under
28:03a microscope so the processor stops
28:05clicking and holding the bus.
28:10And what did I cut out? Anyway, I
28:12struggled with this. Well, give or take
28:14two working days. So, with some
28:16periodicity, the chip isn't detected. I
28:19tried playing with the clock speed of
28:23the programmer and this whole mess.
28:27I tried adjusting the voltage a little
28:29bit.
28:30There were tips that you could raise or
28:33lower it slightly.
28:35In short, it's useless.
28:38Given this unfortunate circumstance, we
28:41will just have to blow it off here and
28:44try doing all this in a socket.
28:48Let's go.
28:53Uh-huh. So, look guys, what's up? Is
28:56there sound? Yes.
28:58RT809H programmer.
29:01Our original chip is in the socket.
29:05Smart detect 1.8 V.
29:11We are trying to detect it.
29:16That's it. Time.
29:20Ah,
29:22gentlemen, look, I’ve tried everything.
29:26I won’t delay you now and show you all
29:28of it again, just take my word for it. I
29:30tried the ENT, I went to a friend with a
29:34UFPI, I tried here in the settings. You
29:38can
29:40change, say, instead of 1.8, make it 3V
29:44; I’ve even tried everything, thinking
29:48maybe higher voltage. I hit blank.
29:52That's it, the chip is dead.
29:58So you don't have any doubts, I’ll take
30:01this dead chip out and put in
30:07one known to be working.
30:16So, select 1.8, because it’s alive.
30:23Blank, stop.
30:27Bad contact, see?
30:31Oh, come on!
30:38One more time. Blank.
30:46>> No, everything is fine now. It was just
30:48poor contact. This once again confirms
30:51to you that the RT809 programmer
30:55has very good pin detection.
30:58If the pins on that chip, well, our dead
31:00one, weren't making contact, it would
31:02have given me something like that too.
31:05But look at what's happening there,
31:07gentlemen.
31:09All the pins are making contact,
31:12everything is fine, but the translator
31:14is crashing.
31:16When I was talking to the artificial
31:20intelligence, it gave me this story that
31:24these Samsung chips, which seem to be
31:27very high quality, if they are used too
31:31actively, sooner or later the translator
31:35fails.
31:37I’m just telling you what I was told.
31:40What does that mean? That’s a very
31:42interesting fact. Remember this point.
31:44What does "too actively" mean?
31:48The chip isn't even 2 years old.
31:51Well, or it is, give or take. Oh well,
31:54never mind.
31:55What do we have in the end, gentlemen?
31:59The original dump for this board is lost
32:02. What are we going to do with this?
32:05I have absolutely no idea.
32:08A quick Google search showed that
32:12firmware for the Yandex 0092 TV doesn't
32:17exist at all.
32:23No, I've already gone through this
32:25process. I'm just going to take a break
32:27now. I'm completely out of patience, so
32:30I'll record a snippet for you. Turn off
32:32, let go.
32:36So, gentlemen, let’s try to write
32:39something already.
32:41We at least need to get the platform up
32:43to understand if the panel and the rest
32:46of the hardware are working.
32:48Ah, let's go to the well-known forum
32:51Remont-Aud.net
32:55and do a live search for the firmware by
32:58name. But look, you don't need to type
33:02in here, well, this
33:06our well-known signature Yandex 092,
33:13because we won't find anything here, yes
33:16, and that’s sad.
33:18We need to type our motherboard model
33:21into the search.
33:24Yes, that happens. And look, there's an
33:27extra letter T in the part number here.
33:30Let's shorten everything so it pulls up
33:32the maximum number of results.
33:35And hooray, we have a victory.
33:38First of all, we see Yandex TV Station
33:40101.
33:43Well, it's certainly not our TV, but
33:45it's at least something.
33:47Let's see what's here. Read from a
33:49working unit, reset with the latest
33:51update in the archive, for a small price
33:53.
33:55What will be very useful to us?
33:57Board connections, all on the back side
33:59, short the quartz.
34:01Powered from the power supply unit,
34:03there are two types of boards. There is
34:05a T-Con soldered onto the board, mine
34:07doesn't have one.
34:09The T-Con is separate, the boot is the
34:11same for both, but it's not used.
34:14It boots from the CPU. Searched for the
34:17firmware for a long time, never found it
34:18. Need to replace it. So, good luck
34:20everyone. Great. Thanks, buddy.
34:24Well, here, in short, look, the contents
34:28of the archive. There are some pictures
34:31here. The point is that I will also
34:33download this firmware, because there
34:35are no other options, there simply
34:37aren't any.
34:38Zero comments on this post, but it's at
34:41least something.
34:43Therefore, there is also some second
34:47option. The second option is even
34:49funnier. I'll show you now.
34:54Look, the mainboard seems to be ours,
34:58but no specific device is mentioned,
35:02nothing is clear.
35:05The archive has nine files, the CRCs
35:07match, no password.
35:10And here, look, a very important and
35:12interesting thing.
35:13Crucially, the dump was taken from a
35:15specific device.
35:17Inside, the serial number, MAC address,
35:19and HDCP keys are visible. After writing
35:22, you need to edit it for your own
35:24device.
35:24Thank you, kind person, you described it
35:28amazingly. But how do I actually do that
35:30, huh?
35:33I mean, okay, thanks for uploading it at
35:34least.
35:39But the description, I don't know how it
35:40passed Remaud's moderation, but
35:42nevertheless.
35:43And we don't have any other options.
35:47We need to write something to this
35:49platform to try and get it running.
35:53Look what I did. To keep the video brief
35:56, I naturally downloaded all this stuff
35:59in the background.
36:01Here. And I ended up with this situation
36:04.
36:05I'll show you now.
36:09Here they are, these two archives. I've
36:11already unpacked them. Here is the
36:14archive from the 101.
36:17There are some useful things here in the
36:19form of images, but I'll draw your
36:20attention to that later.
36:22Or maybe I already have, I don't know
36:24yet. Alright, fine.
36:27And there is a second archive from some
36:30unknown TV. No description at all.
36:33It's there, but it doesn't specify what
36:35model it is.
36:37So, look, let's try our luck and see if
36:40we get lucky.
36:42We will launch the HxD application.
36:48It is a hex editor.
36:52Okay. And let's load
36:58first the file where we know it's the
37:02Yandex 101.
37:04Wait, I went to the wrong place for a
37:06second.
37:09Right, here we see Yandex 101.
37:19Okay. Now look at what I'm doing. Press
37:23Ctrl + F,
37:27and we get into the search panel.
37:31Here we need to enter
37:35the following phrase: "Product model".
37:39So here we will now try to find where in
37:42this firmware the model is defined.
37:46Pressing it.
37:56Well, I'll probably speed this up. Let's
37:58see, so you don't have to wait too long
38:00.
38:28Here. Hooray.
38:31Look, the firmware explicitly states: "
38:35Product model" is Yandex 101.
38:42You can see it.
38:45And now let's load this unknown second
38:49firmware, but we have no other options.
38:54I mean, we just have the understanding
38:56that it's the same board, but which TV
38:58it's from, God knows.
39:02Let's try to load this one.
39:12And now let's perform the same operation
39:14. So, let's make this go a bit faster.
39:17Well, it's somewhere around here, yeah,
39:20let me scroll a little.
39:23Let's try Ctrl + F "Product model" here
39:26.
39:28Look, the data type we are looking for
39:30is text string, don't make a mistake,
39:33not hex value, that is, not a
39:35hexadecimal value, we are looking
39:37specifically for a text string, product
39:40model.
39:42And this rule, well, is followed in many
39:45firmware versions, that is, with modern
39:48Androids.
39:51If you don't understand which specific
39:54TV model the firmware is configured for
39:56and with what parameters, and you just
39:59have the date code of this board, or as
40:02they call it, the part number, you can
40:04try, I'm not saying it will work 100%,
40:07but you can try to search this way.
40:11Alright, let's go. Searching.
40:14Which TV model is this firmware actually
40:18for?
40:21So, I think this will take some time
40:23again. Let's fast forward.
40:38Gentlemen, look, it seems we got
40:41incredibly lucky.
40:45This, in essence, nameless, poorly
40:47described firmware.
40:49It turned out to be from a Yandex 92.
40:52Hooray.
40:56So, now, gentlemen, we are preparing the
40:59chip. Launching Netu.
41:05And we took the chip from a phone.
41:10You can look right here somewhere, there
41:12will be a screenshot of our previous
41:14video, I think it was about a Xiaomi TV
41:16.
41:18Be sure to watch it if you haven't seen
41:20it. A very funny story. There. And now
41:24we have more or less of a supply of
41:27chips that we can be absolutely sure
41:30about, because we desoldered them with
41:33our own hands and, in general, got them
41:36cheaply.
41:38The thing is, the work is starting, you
41:40see, with large volumes. 32 GB is really
41:43no joke anymore. Alright, let's go.
41:47So, look, we must specify in the
41:50programmer here an extended access mode
41:54, and because of timing, we won't have
41:58to flash 32 GB right now.
42:02We are just going to configure the chip
42:04for future writing.
42:07I will perform the actual writing later
42:10using the RT809H programmer, which will
42:14use all eight data lines.
42:18Unlike the configuration I'm doing now.
42:22Well, here somewhere there will be a
42:23picture of how all this gear looks.
42:27Okay, done, connecting to the chip.
42:29Let's go.
42:43So what do we see here?
42:45Look, the chip is in perfect condition,
42:48but since it was used by us before, we
42:52already have a key written to the RPNB
42:55area, so we must definitely flash it, or
42:59rather, flash the firmware of the EMMC
43:02controller itself.
43:08For this, we go into Advanced and say
43:13flash EMMC firmware. We select this item
43:17here and run it. We already have it
43:21prepared, I'll find it quickly now.
43:26As you can see, there was the Xiaomi
43:27video.
43:28Well, it was released recently.
43:32Here I already have a modified firmware
43:34that will completely zero out our chip
43:37now.
43:39Okay, let's verify that this is
43:41definitely BG2.
43:44And let's go.
43:46Click.
43:47Erasing, transferring new firmware,
43:50verifying. Everything went through
43:53successfully. Why did I insist that you
43:57lower the speed?
43:59It goes fast enough here, but if you do
44:01it at standard speed, there might be
44:04data transmission issues.
44:06Okay, all good. Click here, accept the
44:09serial number.
44:11Let it be standard.
44:14Okay, let's see what happens once more.
44:19See, the key is now unprogrammed,
44:21meaning the chip has returned to its
44:23factory state.
44:25Everything is perfect.
44:28Let's disconnect from the chip and
44:30remove the power.
44:31Why is this done?
44:33So the chip restarts its internal
44:38software, preventing any further
44:42glitches.
44:46The next thing we need to do is write
44:51the CSD.
44:55We'll take it from the firmware we
44:57downloaded.
44:59To do this, we perform a restore CSD.
45:05Hmm. Okay, now
45:12let's find where I saved it.
45:18Aha, here you see the CSD file.
45:22It will now configure the chip correctly
45:25, where to boot from, the bus width, and
45:29if the reset is set.
45:31Well, for those who find this point
45:34unclear, study the basics and watch our
45:37previous videos.
45:39I went over it there in some detail. I
45:42won't dwell on it now, because there's
45:44still a lot of info to cover. Let's go.
45:47See, registers 162, 179, and 177 have
45:51been written.
45:53All good, the chip is configured. And
45:57you can see here, previously it was set
46:01to "boot from eMMC not used."
46:06Let me reconnect now and let's see what
46:09the protocol outputs.
46:19See, the boot 1 partition is used for
46:23booting. There we go. Everything is
46:25correct. Okay, let's move on. All that's
46:29left is to flash boot 1 and boot 2.
46:33And the user partition, the user one is
46:35huge.
46:36This will take about an hour and a half
46:39to flash even in the 809 at 8 bits.
46:42So, let's open boot 1.
46:47Going back into the firmware folder.
46:55Okay, here is boot 1.
46:58Skip the RPMB partition.
47:00Forget about it. The RPMB partition will
47:03be written later by the processor itself
47:05. Okay, opened boot 1, writing.
47:16Okay, write finished successfully.
47:18Moving to boot 2.
47:22Let's open boot 2.
47:26Writing.
47:35Well, gentlemen, I'm anticipating
47:38setting this chip for a ninety-minute
47:42write and going to take a break.
47:47Okay, half the job is done.
47:52Let's go to the other program.
47:56So now, gentlemen, we launch the RT809H
47:58software.
48:08Now, while this whole procedure is
48:11happening, you'll see a photo; this
48:14programmer will write via all eight
48:16lines.
48:18So, you press Smart, well, autodetect.
48:21You must set it to 1.8 V here. We have a
48:25modern chip, 32GB, 5.1 generation, so it
48:29shouldn't be 3.3 V, but 1.8 V.
48:33Pressed.
48:37Right, now go to the set settings.
48:40You need to uncheck the boxes here. We
48:42already flashed boot 0, we already
48:44flashed boot 2. We already flashed the
48:46ext.
48:47Here you need to limit the area the
48:49programmer works on, so it only touches
48:52the user area.
48:54That's it, accepted.
48:58Now what? Press WR. Here, unlike the
49:01Medusa, I've already mentioned it in
49:02other videos, it's the other way around
49:04. You press the operation first, and
49:06then choose the file. And let's go and
49:09select our file.
49:22Right, there is our user file.
49:25And that's it.
49:27We press it and go drink some coffee.
49:30This is not a quick process. Let's time
49:34it now.
49:36Will it show how many seconds this
49:39process takes?
49:41Everything is ready, it started.
49:46Well, let's wait, drink coffee, and pray
49:49that everything works for us.
49:55When the process finishes, or gets close
49:57to completion, I'll turn it back on.
50:00Signing off for now.
50:03So, gentlemen, I will be brief. As you
50:06can see, the process took 1,470 seconds
50:10here.
50:11Well, give or take 24-25 minutes.
50:15Well, that's just for the record.
50:18Everything went successfully. Now let's
50:20quickly solder it back on.
50:22The process typically contains no tricks
50:24in principle.
50:26I'll solder it and we'll go boot it up.
50:29Let's go.
50:32Well, gentlemen, it seems everything
50:34worked out. Everything is soldered, I
50:35put it back. I won't bore you with these
50:39trivial things.
50:41In general, the first launch.
50:44I connected the terminal immediately,
50:47well, just to see it with my own eyes.
50:50Okay, here we go.
50:53Oh, oh, oh, Kostya, it's a victory. Look
50:56, the terminal text is running.
50:59Oh, everything is loading, it seems.
51:02Wait.
51:06Oh, for heaven's sake. Oh,
51:08>> damn it.
51:09>> Oh, jeez.
51:20Disappointment. Yeah.
51:33How did this happen?
51:40But, in principle, it's expected.
51:43We partially flashed an absolutely
51:46unverified, random dump. But, gentlemen
51:49, look, we have already gained a huge
51:53plus.
51:54Clearly, the image is distorted now, it
51:57seems this was a batch with different
52:00matrices. Who cares. The most important
52:02thing we've verified. Otherwise, the
52:05processor, RAM, backlight, matrix,
52:08everything is alive.
52:11So, what does it offer us here? Recovery
52:14. Try again, factory data reset.
52:17Right, we have remote control here.
52:21The CK buttons. See?
52:23Look here, it says: "Use Volume Up/Down
52:26and the Power button."
52:29Well, just like on phones, some sort of
52:31similarity. There. Let's press it. Come
52:34on. What are we doing? Factory data
52:36reset. Let's try pressing it.
52:39Come on, buddy, are you going to press
52:42or what?
52:45What's up with you?
52:47What happened?
52:51Well.
52:54Yeah. What are you going to do?
52:59What should I do?
53:08The thing is, this TV has absolutely no
53:12buttons except for this one Power button
53:16and some obscure connector.
53:19It's just awful here.
53:23Yeah, for crying out loud.
53:28And to close it up, you’d need to build
53:32a monument to the people who invented
53:35this mess. Alright, let's see, will you
53:39work?
53:40No. Okay, we'll fight with this
53:43off-camera and come back.
53:50Alright folks, anyone repairing these
53:51Yandex TVs, keep in mind, this is the—I
53:54don't know, I've never seen a worse
53:56connector.
53:58I mean the one that connects to the
54:00panel.
54:01Anyway, I had to reconnect it and reboot
54:05the TV. And then, look at the screen,
54:07just look. See? I'm pressing the volume
54:10up and down buttons, everything is
54:13working now.
54:15So, we don't really have many options.
54:18Try Again or Factory Data.
54:20Let's go with Factory Data Reset. Let it
54:22restore from some backup. What? Let's go
54:25. Factory data asks again: "Are you sure
54:28?" Yes, we're sure. That's it. It's all
54:30just like on phones. It's running down
54:32there. Show it, Kostya. That's it, it's
54:34—Oh, well, it's already gone.
54:36In short, it cleared all caches and
54:38wiped the data area.
54:41Now it's probably going to...what is it
54:43going to do? Something from the backup.
54:47The image is shifted.
54:53The image is clearly wrong.
54:56How does something like this even work?
54:58Look, Konstantin Petrovich, we checked
55:00the firmware inside the device together
55:02.
55:04It has that 92nd Yandex version.
55:14You show the screen, I'll fast-forward
55:16to see what happens.
55:19>> What?
55:28Anyway, folks, this is a sad state of
55:30affairs.
55:31I don't know what to do with this yet.
55:38Let's get to the key moments so as not
55:40to drag out the video. I'll try to show
55:42what happens next.
55:46>> Cut it for now.
55:49>> Nice to meet you. I live in this TV. Now
55:52we will set it up.
55:57>> So, anyway, it’s about to set something
55:59up. It's Alice writing: "Connecting
56:02remote."
56:05To understand, the remote here is
56:06Bluetooth, and it doesn't initialize
56:08right away.
56:11There.
56:13Or does it?
56:15Who knows what it needs. Connecting to
56:19the internet. Set up the TV for a home
56:22with Alice.
56:23Alright, I'm pressing a button.
56:40And there, folks, look, the next step.
56:48Look, but this is already a result.
56:51At least the whole system is working.
56:53Let’s take a look at the log to see
56:54what’s here. Well, you see, the log is
56:56fine too.
56:58So the operating system is doing
57:00something here.
57:03Oh, let me connect to Wi-Fi now.
57:07Aha, the Wi-Fi module was detected. Good
57:09,
57:12let's go.
57:16I don’t think there’s any point in
57:17hiding the password here.
57:21Oh, by the way, a moment.
57:24Let’s see, gentlemen, I have a keyboard
57:28.
57:29Right, we don’t need the terminal for
57:31now. Let it rest for a bit.
57:35I have a keyboard.
57:38Well, computers are computers, right?
57:45Come on, let’s try it.
57:53Click.
57:55Oh, gentlemen, the wireless keyboard is
57:59working. I’ll type the password here now
58:02.
58:05You don't have to show it.
58:06>> Well, don't show it now.
58:09>> No, just show that the keyboard works.
58:11I’ll type some nonsense now. Look. Oh,
58:15the keyboard started working. Oh, now
58:17turn the camera to me. I’m entering the
58:20password here.
58:22So, what do we have here? Aha.
58:28Enter isn't working. Enter...
58:41What?
59:01I hope it just scrolled through. That's
59:03a victory. Look, I’m connecting to the
59:05internet. That's it.
59:08Aha,
59:30gentlemen, because of this distorted
59:32screen, well, it just so happened that
59:35you saw, the keyboard was also acting
59:37all wonky there.
59:39Well, I added an extra character to the
59:40password. Anyway, there was a little bit
59:43of confusion here. Everything is fine
59:45now. I entered the password.
59:48Look at what is happening now. Some
59:50update is happening now.
59:53So, Yandex servers, everything is a
59:55success, everything is working.
59:57Here is the idea.
1:00:00If everything goes smoothly now, and all
1:00:03the updates finish, we have plenty of
1:00:05ways to switch the screen to the, well,
1:00:08to the correct one.
1:00:11We can connect via...or change the panel
1:00:14.
1:00:15Well, those who understand, you can
1:00:18choose a list of panels, see which ones
1:00:20, well, you can choose and actually set
1:00:23your own.
1:00:25Or we can even try, using this remote
1:00:28that has no numbers, to enter the
1:00:31service menu and choose the panel we
1:00:34need.
1:00:36I don’t remember, something like
1:00:37configuration, up-down, up-down, back,
1:00:39and generally you get into the service
1:00:40menu.
1:00:42Anyway, what do I propose?
1:00:44Let’s wait for these updates to finish,
1:00:46and we will turn back on and see what
1:00:49comes of this.
1:00:51Signing off for now.
1:00:55Dear viewers, we'll take a quick break.
1:00:58I’ve already talked in a video about how
1:01:00to support our channel, but for some
1:01:02people, it’s problematic, or due to
1:01:04their own personal beliefs, they don't
1:01:06want to use platforms like DonationPay,
1:01:09DonationAlerts, and the like.
1:01:11There is a simpler way for Russians.
1:01:14Konstantin Petrovich, our highly
1:01:16respected cameraman, has a shop on Ozon
1:01:19. You are all likely aware of the
1:01:22situation with marketplaces.
1:01:24We have very few parts left there.
1:01:28Specifically, there are chargers for
1:01:30lithium-ion batteries that are used in a
1:01:33huge number of devices, ranging from
1:01:35various speakers and flashlights to some
1:01:38robot vacuums, and so on.
1:01:41The price is low, 200-300 rubles.
1:01:43Especially now with the discounts, we
1:01:45need to sell this stock off faster.
1:01:47We are already at nearly 55,000
1:01:49subscribers or so.
1:01:52Please, if you want to support us, the
1:01:53easiest way is to follow the link in the
1:01:55description, or it will also be in the
1:01:57pinned comment.
1:01:58Order something useful for yourself,
1:02:01maybe it will come in handy someday. It
1:02:03will be good and useful for you, and it
1:02:06will support us in these difficult times
1:02:08. Well, that's all, thanks. But back to
1:02:10the point. Let's keep watching,
1:02:14my friends.
1:02:16Dusk was falling, but finally, a victory
1:02:19.
1:02:20After installing either two or three
1:02:23updates, we have this on the screen.
1:02:26Dmitrovich, show them, please.
1:02:29The matrix is messed up to hell.
1:02:35But look at this workaround.
1:02:39We currently have a login window.
1:02:47But look, we can't get into the service
1:02:49menu right now because until we log in
1:02:52here, we won't get the service menu.
1:02:55There.
1:02:57And so, even though it's hard to see, we
1:03:00can still read this digital code.
1:03:04Look, here is what it says.
1:03:06Open the page with two-factor
1:03:09authentication or something and enter
1:03:11this code.
1:03:16You need to go to the page
1:03:17yandex.ru/activate and enter this code.
1:03:21Okay.
1:03:22Which is what we are going to do. I have
1:03:24prepared a tablet.
1:03:28Just so you understand, I even have two
1:03:29Yandex ID accounts.
1:03:31What should we enter there? 58 59
1:03:37So, what is it? 0 325.
1:03:42Yes, Kostya, 205.
1:03:46Alright, let’s go. Log in on the device
1:03:49. And magic, voila,
1:03:55and we get
1:03:57>> nothing at all.
1:04:02Well, there.
1:04:07Fine, if it’s the first attempt, look,
1:04:09show what it says here.
1:04:13Excellent.
1:04:16Alright, let's try again, because, well
1:04:18, it doesn't always log in on the first
1:04:20try. Let’s re-enter something like 2030
1:04:23.
1:04:26So, no mistakes, gentlemen. 2035.
1:04:317 6 2
1:04:35300.
1:04:37Press the button, please.
1:04:41>> 300.
1:04:43>> Tractor drivers
1:04:47>> and artists
1:04:49>> it won't log in.
1:04:52So what are we going to do, gentlemen?
1:04:54We are in a vicious cycle.
1:04:58As long as we don't get in deeper to the
1:04:59desktop.
1:05:02We, actually, cannot change the panel.
1:05:08So. But
1:05:10there is a tricky maneuver. We do have
1:05:13UART, gentlemen.
1:05:19So let's do this.
1:05:24We need to hold down the Ctrl + Z keys.
1:05:31and turn on the TV. And now it will
1:05:34launch us into the service menu.
1:05:51Gentlemen, this video is a bit staged,
1:05:53so you understand.
1:05:55I was fighting with this crap for, I
1:05:58don't know, several days.
1:06:00And here is the point.
1:06:02I am just cutting out a huge chunk of
1:06:05this video now, because many people hate
1:06:08me for talking too long about things.
1:06:13I am trying to speed everything up for
1:06:14you. In short, what is the point?
1:06:18Yandex doesn't employ fools.
1:06:22Yandex programmers blocked UART, but
1:06:24they blocked it in such a sneaky way.
1:06:26Let me explain that signature, Kostya,
1:06:29show it again.
1:06:31Some kind of key is generated here, and
1:06:33with every session, that is, with every
1:06:35launch, it's different.
1:06:38For some unknown reason—I am not a
1:06:40Yandex programmer, and I don't have any
1:06:42documentation for this.
1:06:45And our esteemed gentlemen from Yandex
1:06:47just don't give a damn about all the
1:06:49users if they run into any problem.
1:06:52But you will see more about that later.
1:06:55In short, what's the point?
1:06:58It is waiting for some response code
1:07:01that the system needs to enter quickly
1:07:04to give me access to UART.
1:07:07That's it, forget about it. UART is gone
1:07:10to hell.
1:07:12If I had gotten into UART, I could have
1:07:15displayed a list of commands, gotten a
1:07:18list of panels, set the panel I needed,
1:07:20and everything would be fine.
1:07:23Okay, fine, UART didn't work out. Let's
1:07:26go back,
1:07:32back to our desktop again.
1:07:35Well, it's running a log. Alright,
1:07:36everything is fine. Basically, it's not
1:07:38even interesting to anyone anymore.
1:07:41Forget about UART,
1:07:44so you see, here is the logic: limit
1:07:49everything.
1:07:52If you see an open UART on Chinese
1:07:55devices, that's easy.
1:07:57But here, they know how to impose limits
1:08:00.
1:08:01You understand what the goals are.
1:08:03Alright, that's not the point.
1:08:07What other options do we have?
1:08:11Again, I'm shortening this video to the
1:08:14maximum.
1:08:17To get to the operating system desktop,
1:08:22we need to log in. And here, after
1:08:25chatting with artificial intelligence
1:08:28for a long time, it throws this story at
1:08:31me.
1:08:32If logging in via the code I enter here
1:08:37on the tablet doesn't work, there is a
1:08:42chance to try logging in via a QR code,
1:08:47which, well, you will see on the desktop
1:08:52right now.
1:08:58Well, what is it?
1:09:19So, gentlemen, let's continue.
1:09:23Our goal is to get to the desktop of
1:09:26this TV.
1:09:28the TV, again.
1:09:30In short, we talked for a long, long
1:09:33time and it offered me this
1:09:37version.
1:09:39The thing is, if logging in with a code
1:09:42doesn't work, you have to try logging in
1:09:45via a QR code.
1:09:47Take a look at this one.
1:09:52This QR code won't scan because our
1:09:54panel has shifted.
1:09:57This QR code isn't being recognized. So
1:10:00what am I supposed to do? I'm in a
1:10:02vicious cycle.
1:10:03I can't set up a working panel to see a
1:10:07clear QR code and test this version.
1:10:12And at the same time, I can't read this
1:10:15QR code with a distorted panel. So what
1:10:18should we do, Constant Petrovich? What
1:10:20are your theories?
1:10:23>> Can we rig something up?
1:10:26And then,
1:10:31I'm telling you this chronologically,
1:10:33news comes in that something happened
1:10:36with their data centers.
1:10:41And now this equation has, damn it,
1:10:44three variables,
1:10:48X, Y, Z. Darn it, is the QR code not
1:10:51scanning, or did the data centers go
1:10:54down? Or maybe I didn't flash something
1:10:58correctly in the firmware.
1:11:02If you recall, someone wrote that you
1:11:05need to enter the serial number and the
1:11:08MAC address so that these stations don't
1:11:11duplicate.
1:11:14I'll tell you right now, that's all been
1:11:16done off-camera, and nothing helps.
1:11:20Oh well.
1:11:23Experts are going to tell me: "Come on,
1:11:26you're smart."
1:11:28There's this thing called ADB.
1:11:31ADB is, off the top of my head, Android
1:11:34Debug Bridge or something like that.
1:11:38In short, a rabbit hole.
1:11:41It's a special channel you can use to
1:11:45connect to this damn TV and try to
1:11:49change its settings.
1:11:52I'm honestly quite weak at this because
1:11:54I never worked with phones back in the
1:11:56day.
1:11:58But I can tell you a few things.
1:12:01Now we'll go to the computer and try to
1:12:05connect to it via ADB.
1:12:07Because we have no other options. Let's
1:12:11go, Stani Petrovich.
1:12:15So, dear colleagues, to connect via this
1:12:19Android Debug Bridge system, we need to
1:12:22find the IP address that this TV has
1:12:25obtained.
1:12:28To help you understand, it's quite
1:12:29simple since it's on the Wi-Fi network
1:12:31now.
1:12:32Go into your router.
1:12:34I have a D-Link; I'll ask Kon Petrovich
1:12:37to show it. Look here, Yandex TV Station
1:12:41.
1:12:42It has the address 192.168.0.41.
1:12:46That's the local address.
1:12:51Next, we need an application. It's
1:12:54called like this. ADB App Control.
1:12:59I already tried to connect to it.
1:13:03Now, right before your eyes. Show them,
1:13:05Kostya, that it's online.
1:13:07Just turn the camera that way. Uh-huh.
1:13:11It's online right now, look.
1:13:16I'm trying to connect.
1:13:19It says. Cannot connect.
1:13:23The connection was not established
1:13:25because the target machine actively
1:13:27refused it.
1:13:31My deepest respects to you,
1:13:35Yandex security team.
1:13:37You even locked down ADB. And what am I
1:13:40supposed to do with this now? Who do I
1:13:42call and what do I do with this?
1:13:45Damn it all.
1:13:52I have a suspicion that this video will
1:13:54end in some kind of fiasco.
1:14:02Alright, I'll go and think about it.
1:14:08Gentlemen, as you can see, I'm trying my
1:14:11hand at acting.
1:14:13Get it? I've been battling this crap for
1:14:15more than a day now.
1:14:17And all of this is staged for now.
1:14:22We just moved from one spot to another.
1:14:24What's the gist of it? I've been
1:14:26fighting this junk for a week, with zero
1:14:28results.
1:14:29ADB is closed, UART is closed.
1:14:35I sat down with—I just don't want to
1:14:37show it on screen right now.
1:14:40I'll just explain it in a nutshell so it
1:14:44isn't so dragged out.
1:14:47I sat in a hex editor following AI
1:14:50advice, trying to change the lanes—that
1:14:54is, the matrix and how many lines it has
1:14:57.
1:14:59I tried changing some other parameters
1:15:01too. In short, keep in mind, especially
1:15:05since this is Android 11.
1:15:08Any changes made to the code just cause
1:15:11it to drop into recovery, meaning total
1:15:15panic, and everything restores from a
1:15:18backup. How? Why are the people at
1:15:22Yandex far from stupid? They've
1:15:24essentially locked everything down.
1:15:27And that is, in principle, correct, but
1:15:29the device still needs to be fixed.
1:15:31What am I supposed to do with this?
1:15:43I'm starting to have some really sad
1:15:45thoughts.
1:15:47First.
1:15:50I'll turn it off for now.
1:15:55Option number one. Baboon-style repairs
1:15:58.
1:16:01Take it, buy some board like this, damn
1:16:06it,
1:16:08anyway, buy a board, pay some money for
1:16:11it, but it's not a fact that it will
1:16:13even start up.
1:16:15But the problem is, as you've realized,
1:16:18we have an awesome adaptive backlight
1:16:20there.
1:16:23I could, of course, force it into
1:16:25full-on emergency mode by shorting a
1:16:27test point, but that's a mediocre
1:16:29solution, just pure monkey business.
1:16:33So that option was dismissed immediately
1:16:35.
1:16:37Option number two. Let's go to the
1:16:40computer now.
1:16:46So, gentlemen, so as not to put it on
1:16:49the back burner, let's try not to stress
1:16:52and actually find a motherboard for the
1:16:55Yandex 0092 or whatever it is.
1:16:59Aha, 392.
1:17:01Entered the search wrong. Okay.
1:17:07Well, obviously, there's all sorts of
1:17:09junk here. Here is your first offer for
1:17:129500.
1:17:14I would like to draw your attention to
1:17:16something right away.
1:17:18It's completely unclear what people are
1:17:20selling.
1:17:22Look, if you take a photo of our board,
1:17:25we have an additional chip right here.
1:17:29We have the adaptive backlight right
1:17:32here. There's no processor here at all.
1:17:34What is this? How are you supposed to
1:17:36buy this?
1:17:38Not an option at all. Okay, let's keep
1:17:41going.
1:17:45This board is more or less similar, but
1:17:47it's actually from a 96.
1:17:48See, the chip is missing.
1:17:51LVDS, or VBY1, is located in this plane
1:17:54. There is no adaptive backlight chip.
1:17:57How does this even work?
1:17:59Okay, let's find out what all this is
1:18:02for.
1:18:03Here is some kind of board. It's
1:18:05completely different.
1:18:09If you are looking for a replacement
1:18:13board on marketplaces like Avito.
1:18:16By the way, this one looks similar to
1:18:18ours, but it's not the right one at all
1:18:20. This is from a 91 model. Why is it
1:18:22here in the search results? Oh, whatever
1:18:24. Here is the 8905 board.
1:18:27TV Station. Oh, by the way, gentlemen,
1:18:3192.
1:18:33See?
1:18:36And it would seem that everything
1:18:38matches, but no such luck.
1:18:41A photo will be attached here comparing
1:18:44our board and this one.
1:18:47I don't understand how this whole mess
1:18:50works.
1:18:51I came across one listing somewhere.
1:18:57I'll try to find it now, but maybe I
1:18:59won't find it at this moment.
1:19:02But I saw that one listing had two
1:19:04varieties of boards, and it's unclear
1:19:06which one you'd get.
1:19:10Hold on, hold on, I'll try to find
1:19:13something for you. Yeah, in short, it's
1:19:16all very sad. Let's try searching by
1:19:19this board then
1:19:22simply by typing it in here like this.
1:19:26Look, oh, 4,000 rubles. 96th Yandex.
1:19:31This is yet another configuration.
1:19:35It lacks both adaptive backlight and the
1:19:38chip that handles our specific matrix
1:19:41connection interface.
1:19:43Anyway, I'm sick of this whole mess.
1:19:46Here is another such board,
1:19:49it would seem, but again, this is not
1:19:52our version.
1:19:55In general, if you are looking for one
1:19:57that looks like ours, this might be it,
1:20:00yes, but again, I draw your attention,
1:20:02this is not our version.
1:20:04This is for a 43-inch matrix or
1:20:07something.
1:20:09As a repair technician, how would you
1:20:12take on such a responsibility? I can't
1:20:14even imagine. There's one for 11,000
1:20:17here.
1:20:18What is this? How do you deal with this
1:20:20? 43 inches. That's not our version
1:20:24either.
1:20:27Anyway, I don't know, guys.
1:20:31After digging through this mess, I
1:20:34realized that our hardware is basically
1:20:37working, but the firmware is faulty.
1:20:43What should we do about it? And, by the
1:20:45way, notice that there are very few
1:20:48listings, and even if they do exist, the
1:20:51prices are just insane. If you, well,
1:20:56in despair, decide to try and buy
1:20:59something here, I really don't envy you
1:21:01.
1:21:02In case your compatibility doesn't work
1:21:06out, well, by the way, this board is
1:21:09quite similar to ours.
1:21:12I mean, it has the coprocessor that
1:21:15forms the VBY signal.
1:21:18We have the adaptive one here. But again
1:21:21, nothing is clear. Who are you? Where
1:21:25from? What product was this taken from?
1:21:28Where in the Minsk region are you from?
1:21:33This is a real disaster.
1:21:35Alright, I'll log off for now.
1:21:38So, a quick insert for those who didn't
1:21:41get it.
1:21:43Using AI, it started advising me: "You
1:21:45need to change the region here to VyOne
1:21:48.
1:21:50You don't have the second region, which
1:21:52we have in the firmware here, but the
1:21:54first one."
1:21:56I tried everything. Basically, I just
1:21:58took a mass approach.
1:22:01Since I counted about 16 entries of V1,
1:22:04the second region, I changed them,
1:22:06following its advice, to VBY1, the first
1:22:09region.
1:22:12And, naturally, after that, I had to
1:22:15remove it and install it again. It was,
1:22:19all in all, a quest.
1:22:21I did this, I don't know, maybe five or
1:22:23six times.
1:22:24It’s of no use.
1:22:27A panic always occurs, it all falls into
1:22:30recovery, and everything restores from a
1:22:34backup.
1:22:35Either there's a checksum somewhere, or
1:22:38a legitimacy check. That's it. I don't
1:22:41know how it's implemented. Well, because
1:22:44it just doesn't work any other way. Okay
1:22:47.
1:22:48It suggested I extract from this
1:22:50firmware, uh,
1:22:54let's say, the partitions. None of that
1:22:57worked.
1:22:59The thing is, uh, starting roughly from
1:23:02Android 5, uh, they increasingly
1:23:04introduced encryption mode.
1:23:08This is Android 11. Everything here is
1:23:11encrypted tight. How it works, I can't
1:23:15say for sure. The only thing I managed
1:23:18to do, I'll show you now using the DMDE
1:23:21program.
1:23:22There is a program called DMDE.
1:23:26I'll show it to you quickly right now.
1:23:28It’s a very cool little program.
1:23:31It knows how to, uh,
1:23:37recover files by signatures directly
1:23:40from the binary.
1:23:42All I managed to do is put them here in
1:23:46the media folder.
1:23:49Just some nonsense like this.
1:23:51>> Oh, sorry, the film got stuck. We'll fix
1:23:53everything soon.
1:23:54>> Uh, I don't know. Wait, stop. Well, look
1:23:58, some pictures. That's all it could
1:24:01extract. There’s nothing useful here.
1:24:05Well, I'll show you some funny stuff now
1:24:06.
1:24:08>> Well, for example, like this.
1:24:10>> The film got stuck. We'll fix everything
1:24:12soon.
1:24:13>> Are you kidding me?
1:24:14>> Oh, sorry, the film got stuck. soon,
1:24:29well, for example, like this.
1:24:33What does that give me? Absolutely
1:24:35nothing.
1:24:37Well, anyway, you get the idea.
1:24:45Well, for example, these splash screens
1:24:46.
1:24:48Oh, well.
1:24:51And this, ladies and gentlemen, is a
1:24:53dead end. I cannot break the firmware
1:24:55down into components. How does it all
1:24:58work? I can't log in.
1:25:02I can't change the panel because my OR
1:25:05is locked, and my ADB is locked.
1:25:10Well, I’ve already shown you, because
1:25:13the target computer rejected the
1:25:15connection request.
1:25:16The guys at Yandex are certainly no
1:25:19fools either.
1:25:23Well, something like that. Alright,
1:25:25let’s disconnect for now.
1:25:28So, dear colleagues, let’s take stock of
1:25:30our interim results. What do we have as
1:25:33of today? We have a perfectly functional
1:25:37panel and a working backlight.
1:25:41A working mainboard, but it just won't
1:25:43log in.
1:25:45And the reason for the failed login is
1:25:47completely unclear. Moreover, we have a
1:25:51misaligned image,
1:25:55which, again, prevents us from seeing
1:25:58the QR code, that very secret QR code,
1:26:04which would finally allow us to access
1:26:06the desktop of this mysterious beast.
1:26:11And it would seem that’s it, the end.
1:26:13What is one to do with this?
1:26:15Actually, I took a break of about a week
1:26:18.
1:26:18It just sat here for a week.
1:26:21I thought, maybe something would appear
1:26:23on the internet, maybe someone on Remaud
1:26:25would write something.
1:26:28But no such luck; it’s silence.
1:26:32And all this time I was walking around
1:26:34thinking, "What am I supposed to do with
1:26:35this?"
1:26:36"I mean, sure, I could give up, I could
1:26:39do a half-assed repair, but I’ve really
1:26:42gotten hooked on this."
1:26:45I’ve decided to see this through to the
1:26:48end.
1:26:49And here is what I want to tell you.
1:26:54First, we are planning a stream today.
1:26:59I am going to ask for the community's
1:27:01help.
1:27:02After all, there are 60,000 subscribers
1:27:04. Well, almost.
1:27:08That is huge support.
1:27:11I’ve already had one experience where
1:27:14our community helped me sort out a
1:27:17seemingly unsolvable problem.
1:27:21That is why I am inviting you today at
1:27:254:00 PM Moscow time for a stream.
1:27:30Let’s try to tackle this problem
1:27:33together. But that’s not all. I will
1:27:36continue just a little bit more.
1:27:41Please, ring the bell, hit like, so you
1:27:43don't miss the stream and notifications
1:27:46, or just anything that comes through
1:27:48YouTube.
1:27:50Let’s get to the bottom of this topic.
1:27:52It is absolutely relevant, because there
1:27:55is some strange stuff going on right now
1:27:58.
1:28:00Well, you know, like with Konstantin
1:28:01Petrovich and the Yandex data centers,
1:28:03right?
1:28:04And surely many will encounter such
1:28:08problems.
1:28:09>> Yeah, we can't talk about that. But how
1:28:11are we supposed to survive?
1:28:13What are we supposed to do? The TV is
1:28:16good, after all. Well, as a TV, you know
1:28:19, obviously. The Yandex Station is good
1:28:22.
1:28:23And people, you know, are not prepared
1:28:26to pay 59,000 at all.
1:28:29Every single year, damn it, you know,
1:28:32for these kinds of jokes.
1:28:35So, I spent a week on this, and then,
1:28:38honestly, in the middle of the night, a
1:28:42thought hit me: "I have this
1:28:44acquaintance, let's call him Mr. X for
1:28:47now.
1:28:48In the second part of this video, which
1:28:51definitely won't be filmed today, I'll
1:28:54introduce you to him."
1:28:57Maybe online, maybe, well, the point is
1:29:01that
1:29:05And what is the point? Android 11 is
1:29:08completely encrypted.
1:29:10I won't be able to extract any
1:29:12partitions from it.
1:29:14I won't be able to fix anything there or
1:29:16fix any checksum.
1:29:19If you've seen our previous video where
1:29:21I was fighting with the PMI, well, there
1:29:23will be a link to it somewhere here;
1:29:25check it out if you're interested.
1:29:28I was doing some so-called reverse
1:29:31engineering there too.
1:29:34I managed to overcome it all by myself
1:29:36back then, but in this case, my brain
1:29:38isn't enough.
1:29:41The thing is, my knowledge of Linux and
1:29:44all these artificial intelligences is,
1:29:48you know, just me trying things, which
1:29:51is why I asked a good friend of mine to
1:29:55get involved with this problem.
1:29:59Let's call him Mr. X for now. All this
1:30:02will be later.
1:30:07Here is what I did.
1:30:10I explained the problems to him.
1:30:13The TV won't log in. The TV's display
1:30:16panel is misaligned. Every single port
1:30:19that could be locked.
1:30:21Thank you, Yandex programmers. You
1:30:24locked it all to hell.
1:30:28All your services are down.
1:30:32I'll talk about the services in the
1:30:33second part.
1:30:35I'll explain the whole setup to you, why
1:30:38, why everything turned out so poorly.
1:30:42But anyway. What is the point?
1:30:46I tell him: "Look, I'm already, in
1:30:48principle, without much hope." I say: "
1:30:51I have the EMMC,
1:30:54actually, the binary."
1:30:57And so you understand, the guy works
1:31:00with, well, how to explain it?
1:31:03Databases and web development. Yes,
1:31:05Kostya
1:31:06>> does it.
1:31:07>> Well, he works with it.
1:31:09And unlike my GM, he has access to the
1:31:15paid
1:31:19version of ChatGPT.
1:31:22As it turned out, gentlemen, this is
1:31:25actually, look, I've been into this
1:31:28artificial intelligence stuff for, well
1:31:31, how long, half a year or about a year
1:31:34now, right?
1:31:36But this was a new discovery for me.
1:31:41I say: "I have the binary, but it's from
1:31:44Android 11, and it's completely
1:31:47encrypted."
1:31:49I say: "Maybe your model can overcome it
1:31:51, parse it, and fix at least the display
1:31:54panel for me."
1:31:56If he fixes at least the display panel
1:31:58for me, I'll be able to see the QR code
1:32:01.
1:32:03And you understand that when I see the
1:32:05QR code, it could solve absolutely all
1:32:08the problems.
1:32:10If I log in via QR code with a normal
1:32:12legitimate matrix, well, that's it, it's
1:32:15a victory.
1:32:17He says: "Well,
1:32:21I'll tell you straight up. Hell if I
1:32:23know." Well, let's give it a try.
1:32:30I'll explain briefly. I understand very
1:32:32little of this, but I'll explain it like
1:32:35a TV guy, just a TV guy. So,
1:32:39I say: "Well, I have this binary file,
1:32:41what should I do with it?"
1:32:44He says: "Just put it on your hard drive
1:32:45."
1:32:47on the computer.
1:32:51Give me access, and I'll tell it what to
1:32:54do, how it works.
1:32:58Honestly, without any faith in the
1:33:01outcome, I say: "Well, let's give it a
1:33:03try."
1:33:05But that was, you know, it was already a
1:33:07gesture of despair. Well, let's give it
1:33:10a try.
1:33:13This happened around, Constantine
1:33:15Petrovich, well, at the end of the
1:33:18workday, yeah, maybe around 4:00 or 5:00
1:33:20PM.
1:33:23>> After that, all the money disappeared
1:33:25from our card.
1:33:27>> No, we're just kidding, Constantine
1:33:29Petrovich is joking.
1:33:32Anyway, gentlemen, I come to work in the
1:33:35morning, and I have a message: "Is
1:33:38everything ready?
1:33:41You can flash the eMMC and try to start
1:33:45the TV."
1:33:47And ChatGPT had been working on this all
1:33:50night.
1:33:53Hell if I know. No harm in trying.
1:33:56Here's a small digression.
1:33:59This board turned out to be incredibly
1:34:01resilient, because up to this point, so
1:34:04you understand, I’d removed this eMMC
1:34:06maybe six or seven times already.
1:34:09Well, removed, installed, removed,
1:34:11installed. Well, did you see?
1:34:13>> 27.
1:34:14>> I don't know. I, in short, didn't keep a
1:34:17log. Well, in general,
1:34:19>> and then something happened.
1:34:26I said, damn, can't it just break all
1:34:28this down into partitions and put it
1:34:30back together so all the checksums match
1:34:32and everything?
1:34:34He says: "Well, let's give it a try."
1:34:37Well, let's give it a try.
1:34:39Anyway, what am I doing now?
1:34:44I'm reflashing the eMMC image generated
1:34:48by the AI, but not according to the
1:34:51advice of this free GM, but what the AI
1:34:54itself generated for me and put on the
1:34:57disk.
1:34:59Well, let's go try. Hell knows what will
1:35:02come of this.
1:35:07So, gentlemen, it's practically the last
1:35:10stand and our final opportunity to rely
1:35:13on artificial intelligence, so to speak
1:35:16, the war of the machines.
1:35:19What did I do? I flashed the image
1:35:22prepared by ChatGPT.
1:35:28Trying to boot up.
1:35:34It's showing something.
1:35:44No way,
1:35:47it happened.
1:35:58.
1:36:12Now this is interesting, gentlemen.
1:36:16Look, the matrix has aligned.
1:36:21And that's all total nonsense. It
1:36:23aligned and it aligned.
1:36:26You just, well, sort of realize this.
1:36:30Anyway, he fought all night, decrypted
1:36:32all the partitions.
1:36:34Took them apart, fixed something, and
1:36:37put them back together.
1:36:40Honestly, this is a complete mystery to
1:36:42me. I have no clue how this even works.
1:36:45Look,
1:36:49he connected the remote, and now he's
1:36:52connecting to the internet, but I left
1:36:55him a build that was already logged into
1:36:59Wi-Fi and the remote.
1:37:10I'm signing off for now. I really don't
1:37:11know what to do with this.
1:37:14Gentlemen, it's already 2:00 AM. Time to
1:37:17wrap up this video. It’s worn both me
1:37:19and you out. So, let's try something
1:37:23with the code for a bit.
1:37:42Well, honestly, I won't lie to you.
1:37:48This is the final point of this video.
1:37:51Let me explain the deal.
1:37:53Naturally, I already tried all of this
1:37:56off-camera.
1:37:58And with this properly generated QR code
1:38:01, I tried to log in, but nothing works.
1:38:09Write in the comments what I did wrong.
1:38:13Yeah. Also, I invite you to join today
1:38:18at 4:00 PM Moscow time if you have
1:38:21something useful to say.
1:38:26Let's hold a stream and think together
1:38:29about what we should do next.
1:38:33There are actually plenty of options
1:38:35left. I just don't know which way to go
1:38:38.
1:38:40Yeah.
1:38:43Though,
1:38:46see you later. Anyway, I'll see you on
1:38:48the stream.
1:38:50Let's organize a brainstorm, guys, and I
1:38:53hope we can make it work.
1:38:56That's it, thanks everyone for the shoot
1:38:58. Bye everyone.
1:39:06>> That's it.
1:39:08>> And that's all.
1:39:10>> What?
1:39:12What do you need?
1:39:15>> Done.

About this transcript

This page contains the full transcript of ЯНДЕКС-С-ТАНЦАМИ. Оживить ТВ Станцию: UART, дамп и тупик! by Отто Вайнингер, generated from the public captions YouTube serves with the video. The transcript has 11,246 words across 1,983 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.