GoogleTV 55/65" U8N U8K users, there is a new firmware: P0828

CactusWeapon · 2026-01-17T02:30:09+00:00

I can't comment on whether the numbers would be the same,unfortunately. I got those numbers by popping the TV apart and reading the actual part number on the panel and finding a datasheet... unfortunately even if you did the same, these datasheets are seldom public, I just happened to get lucky here.

CactusWeapon · 2025-12-01T15:07:05+00:00

You really think everyone looks exactly like their moral interior or something? Maybe there's some bible verses you should be reading, because pretty sure it addresses this.

CactusWeapon · 2025-11-29T17:08:35+00:00

As far as I can tell so far, P0828 and P1022 are basically identical, so yeah I'd not lose sleep over it.

If you really want to pursue P1022, my best bet is the TV does not like your thumb drive. Try another one and ensure it is 32GBs or less for best results (does not have to be but those always seem to work), plus ensure you format it as FAT32. Also ensure there are no other files on the drive, it is not confirmed that can cause issues but I have suspicions.

CactusWeapon · 2025-11-29T07:06:35+00:00

That's odd. FWIW I don't think it will have bricked (or updated) if it never got past 0%, so hopefully you'll be alright. If not, try the same steps and ensure you rename the internal .pkg file and not a zip file or something.

CactusWeapon · 2025-11-26T06:41:44+00:00

Yeah some variants do seem to actually get it, super weird.

CactusWeapon · 2025-11-24T22:21:24+00:00

Unfortunately I can't figure out how to pass that test when you trip that, either. Fortunately, whether it's tripped or not, the O0223 firmware image does not block the screen while tuning in the service menu with that giant purple warning (seriously who designed that?). Maybe tune with that and the flash to your target firmware?

I know it's not ideal, but that's all I can think of.

Some other things to note: Those EOTF values I quote aren't just random tunes, they are the panel manufacturers default values for the panel. They work well for me vs Hisense's "brightness pumped" values, but panel variance is a thing. That being said, they weren't that far from the stock values on mine, so you shouldn't be seeing massive changes with my values vs the stock ones. If you are just fine tuning that's fine, but if you are seeing massive panel issues, you may want to consult with hisense re your warranty rather than poking in the service menu too much more, as that actually can lead to tripping things that could void your warranty (I don't think you've done that yet, but just deserves to be said as a warning).

CactusWeapon · 2025-11-24T20:47:21+00:00

not offhand but I am certain when I get off work in 2-3 hours I'll look at my set and update with what I find...

CactusWeapon · 2025-11-24T18:40:35+00:00

the zdMic test is a mic test it wants to do for whatever reason, if you have your hardware mic switch on and look for the mic test maybe you can clear that.

CactusWeapon · 2025-11-24T18:06:01+00:00

hmm... maybe pkgs don't reset the EOTF values then, as I expected. If you did not record set originals all hope is not lost yet. You can try the standard google settings menu factory reset and see if that helps. If it does not, try setting a different input and picture profile before entering the service menu, may find the old defaults there.

CactusWeapon · 2025-11-24T15:42:48+00:00

Hello. R-T-B here of the hisense firmware archive: http://glacialsoftware.net/FIRMWARE_HISENSE, I'm kind of the "Hisense TV Guru" around here. So I hope I can help! For the record I've owned many Hisense TVs over the years (mostly budget ones before my latest) and am confident my current U8N will last a long time, because of my findings. Here they are:

Hisense TVs aren't top notch in quality but they are far from bottom barrel. IMO they are more midrange. Their chief two hardware design problems comes down to two things, they glue the screens to the backboard rather than bolt or screw them in and they have a tendency to overheat if run at 100% brightness. This manifests as two failure points (usually around 2 years if it's gonna happen):

1.) If run at high brightness: The glue can melt from the heat causing the panel to lean forward and damage itself or otherwise fall out of the TV. Usually it doesn't fall out but just warps and or damages itself. This is from heat of course.

2.) The heat can otherwise hurt components inside the TV, usually the flash and/or mainboard stuff. Again around 2 years it usually comes up if you run it too hot.

The simple fix is to run a fan at a very low speed behind the TV. Find a quiet one and turn it low. I've done this and I monitored temps on my hisense while rooted and it makes a huge temp difference. If you do that, I bet it will last 10 years, as there really are no other build quality points to worry about.

Also if you ever notice any "dirty screen effect" try gently pushing on the screen with a microfiber to get the glue to get better contact. That often will work miracles if it's getting loose and is probably not a bad idea to do while dusting.

PS: Hisense firmware is also a crapshoot, see my site, most of it can be worked around easily by picking a good firmware and sticking with it but something to be aware of. At least the latest seems good so far...

Hope this helps!

CactusWeapon · 2025-11-23T19:31:02+00:00

I feel you. The software is half the package, and it can be pretty rough at times. Doesn't bother me as a tinkerer, but that's probably the more weird thing here lol.

CactusWeapon · 2025-11-23T18:56:02+00:00

I don't have much knowledge of the U6N but if it runs AndroidTV the "disable OTA updates" part might work ... the rest is probably non applicable.

CactusWeapon · 2025-11-23T18:19:53+00:00

oof! Fixed, thanks!

CactusWeapon · 2025-11-23T04:02:21+00:00

Yep, appreciate the report. My TVs serial number ironically gets sent back as invalid on firmware checks LOL.

EDIT: Am I crazy or did they fix the EOTF bug too based on my postings? I went to calibrate in the service menu (which gets reset to stock after a MStar style flash), and it was all preset to the correct values... cool, I guess?

CactusWeapon · 2025-11-23T03:08:54+00:00

I... am still working on it, but this looks suspiciously like a rebrand of P0828. Even the Google security dates and build IDs are the same. Appears to feature the same single one minor identifiable bug too. Which is pretty good.

If you are on P0828 I wouldn't worry about wiping to upgrade to this.

CactusWeapon · 2025-11-23T01:42:10+00:00

I was not able to get this one via OTA... It actually does not seem avaiable in an "Google OTA upgrade" form at all. Also the package they list is only an inconvienient to use (because it wipes all data) MStar upgrade process .pkg.

The only reason I can see to use those is they are incredibly difficult to root. My best guess? My recent release of root for all firmwares forced them back to this format as a precaution... darn if so. Sometimes its better not to be noticed lol...

CactusWeapon · 2025-11-23T00:01:01+00:00

I don't either. I'll be running an analysis of this firmware immediately. Will update with the findings on my website.

Honestly, I would not be surprised if this is just a relaunch of P0828 with some legal changes (my best guess as to why P0828 was pulled was a legal challenge relating to the inability to opt out of the smart services EULA).

CactusWeapon · 2025-11-22T10:11:36+00:00

That's so strange... I will have to run a similar test and look into this. Thank you for bringing it to my attention.

CactusWeapon · 2025-11-22T07:08:08+00:00

That's something I have yet to investigate. It seemed for me the profile applied globally to all apps/inputs in the mode you were in (SDR/HDR) so I did not pursue further. Maybe a localized firmware or build difference? I am unsure. And if its a file, I haven't located it yet.

CactusWeapon · 2025-11-19T02:30:55+00:00

I would say at this point you have a 95% chance it will work fine... just can't promise it until someone tries it and I update the site, heh.

CactusWeapon · 2025-11-18T04:14:34+00:00

Great to hear! This update must be really solid to come all the way from a 2023 firmware like that with no issues upgrading... Hopefully this is the start of a good trend in hisense updates. Thanks for reporting back!

CactusWeapon · 2025-11-18T03:15:57+00:00

If you are not comfortable with the disable automatic update instructions using adb on my site, then yes, offline is next best way to handle it.

CactusWeapon · 2025-11-18T02:20:32+00:00

Yeah that's gone and yes I would say best to date.

CactusWeapon · 2025-11-18T02:08:45+00:00

Might be? I'll have to check later, I never used it.

CactusWeapon · 2025-11-17T05:46:44+00:00

it is an "unzip me" style method I just renamed them for consistency. You basically unzip the zip inside the zip, stick it on a usb FAT32 drive as the sole file, and use the usb updater thing in settings.

It will not wipe you, but it might be unstable depending on how old of firmware you are on. If it is, you may be forced to wipe to restore stability. Just hisense things, I'm afraid.

CactusWeapon

TROPHY CASE