yashsingh1/xdaforums huggingface dataset:
[Google TV General] npjohnson:
Then you're doing something massively wrong. That's not what it should do.

And I just realized, the device you're talking about has nothing to do with the thread you're in.

Please go to the g12 devices thread for support.
[Google TV General] fixsony:
https://xdaforums.com/t/unofficial-...-family-devices.4313743/page-14#post-85659729
[Google TV General] kennkanniff:
Most worthless comment yet.
[Google TV General] vandyman:
And how is it worthless?

You can buy a Walmart Onn cheaper than a Google Chromecast TV and achieve the same results.

Either you are clueless or starting trouble, which is it?
[Google TV General] kennkanniff:
How is it not? The nearest Walmart to my house is 5800 km.
[Google TV General] vandyman:
Again, how is my post worthless?

Edited; I see you changed your post comments., but I have quoted it in my above post.
[Google TV General] p0werpl:
It's not that your post is worthless, but you made a blanket comment that the WM device is unequivocally better than this given its price. Is it? How is the stock software on that device? Have you looked at the list of bugs in the LineageOS flavor for the device?

For many users, the device in this thread is fine on Google's software. They just want to unlock the bootloader and root it.
[Google TV General] vandyman:
I understand, but I was pointing out that there are alternatives.

And it is less than the price of trying to buy one on Ebay for an original 2019 GTV.

Some people are here to learn something new.

There is nothing wrong with the information that I posted.

Yes, I have 2 GTVs, and would like to be able to root them. That is why I have read this whole thread and following it.

The spoon feeding in the G12 thread makes for a long read......

Edit: Never installed LinageOS on any of my devices. I do not need it. Root and I can handle the rest.
[Google TV General] dante_ov:
Can somebody who unlocked and rooted CCwGTV create eMMC partitions dump and share for further analysis?
[Google TV General] npjohnson:
what partitions do you want? dumps.tadiphone.dev has full proprietary files dumps
[Google TV General] elliwigy:
if u want alternatives nothing compares to 2019 nstv pro
[Google TV General] retyre:
The partition layout on this device leaves a lot to be desired. There's almost 1G less for /data on this device compared to the Onn device (that has a smaller super partition). And losing 800M to cache is wrong (I'm sure OTA can be downloaded to a location in /data instead).

Reclaiming the space from /cache to expand /data might offer two advantages: more storage (obviously) and the inability to OTA because there's no space to save the update.zip?

BTW, you can block updates by blocking android.googleapis.com on the router or adding it manually to AdAway's hosts list. Keep in mind that that will block Play Store and some other Google services as well.
[Google TV General] npjohnson:
AOSP still requires /cache on non-A/B - not sure why - but it's a thing.

And that's not how it works - we can't reclaim space from super to data without repartitioning which will break a lot and would be super dangerous (you'd lose all the keys in hidden partitions).

And yeah, that blocks it, but it wouldn't proceed, that's why the modified firmware solution is way better - you can actually use it now.
[Google TV General] npjohnson:
meh - yeah - only LineageOS 17.1 for that atm - we're trying to get 19.0 up quickly but it's a tough ongoing process.
[Google TV General] rocker0:
Can someone else confirm that on stock DISNEY+ is limited to HD, netflix/amazon prime isn't playing at all?

My chromecast is not rooted, just bootloader unlocked
[Google TV General] Bright09:
worth using if use my chromecast daily? i bouught mine back late aug
[Google TV General] npjohnson:
if you use it daily you probably updated it and can't use this.
[Google TV General] Bright09:
oh is it munch worth it if able to is wifi working
[Google TV General] npjohnson:
Huh?

If you updated your device it won't be unlockable, like the OP days.
[Google TV General] grave35:
del.
[Google TV General] npjohnson:
I'll look into it.
[Google TV General] yan2xme:
omg... seems like the ccwgtv is much overall trickier to exploit but has easily realeased an LOS port for this device. Unlucky for me I am really late at this fiasco and I would not be able to find stocks of this manufactured before Dec, 2020 cause I'm in Asia. And I'm still a newbie bout this and I'm afraid can't proceed with this cause this requires executing this with delicate procedures with dumping all these delicate files...

which In me I might easily brick my device, idk should I still upgrade to this from being an Amazon Fire TV 4k unlocked bl use (which is still crap on how limited the FireOS is and not a single custom ROM is released to this device, doesn't have systemwide uvc and USB Dac support or option to route audio into usb without using 3rd party apps) still i love the hard work you hath done... clap clap clap
[Google TV General] npjohnson:
your risk of bricking in running this exploit is nearly null. Feel free to run it on any firmware version, but newer ones will just say "Password protected, won't work".

And thanks!
[Google TV General] yan2xme:
and If I exploited an exploitable device, can I still install right away Google TV without those OTA's that burn the efuses? or I can just install LOS to not get OTA? Is there a way to block them?
[Google TV General] npjohnson:
After the exploit you are booted to bootloader and can directly install LineageOS. You don't need to reboot to OS and take the OTA's.
[Google TV General] bydo:
Found another old June 2020 device. Would like to keep this one on stock google android image but block OTA updates so I can try Lineage in the future. I presume the script needs to be updated to use parts of current qts1.210311.036 instead of qts1.210311.008 to prevent the initial activation/setup process from force updating to qts1.210311.036? Anyone try this yet?
[Google TV General] blaze2051:
Is the GCTV GSI support?
[Google TV General] npjohnson:
Link me the images for the newer firmware and I'll do it :)

Yup. They work fine, so long as they're small enough.
[Google TV General] blaze2051:
what would the limit size be for the image Os?
[Google TV General] npjohnson:
Idk, probably like 1.5gb if you delete system, product, and system_ext dynamic partitions first.
[Google TV General] bydo:
The file that was linked a few posts earlier won't work? Looks like some sort of patch or partial image based on the 150 MB file size:
[Google TV General] Kalentia:
I've started having issues with playback in most major streaming apps on my Chromecast in the past few months. Any chance this is related to the new update being released but not installed?
[Google TV General] npjohnson:
Unlikely
[Google TV General] Kalentia:
I guess that's reassuring, maybe it's the fact that I've rooted the device. I'll keep troubleshooting!
[Google TV General] 96carboard:
I have a friend with a Sabrina dongle. Completely unmodified, and running a pixel 2 xl, also completely unmodified. She's been having crazy trouble with casting and remote control for a few months. I honestly think that this stuff is pretty weakly implemented and unreliable.

Personally, I don't use cast OR remote, since I've decided to degoogle myself completely. GrapheneOS on Pixel 6 Pro is very nice. Best just to install your software on the TV dongle and be done with it. I also have a couple of ADT-3's that are supposed to be delivered today (although its a pretty serious snow storm here today, so might have to wait a bit longer) to replace my Sabrina dongles, since they're basically the same but unlocked from factory. Yes yes, no netcrax -- I don't like them anyway.

The big problem I see with this casting and remote stuff from gooble, is that they've decided to pull an apple and reinvent everything unnecessarily. There are standardized casting technologies that actually work reliably, and a phone can be programmed to be a USBHID device without needing to use undocumented network protocols to accomplish the exact same thing.
[Google TV General] npjohnson:
Where did you order ADT-3's? US store is out of stock.
[Google TV General] 96carboard:
Right here: https://store.askey.com/adt-3.html
[Google TV General] 96carboard:
Tiny bit of information for anyone trying to flash the factory system images (or probably anything else) to an ADT-3... make sure that when you run flash-all.sh, you UNPLUG THE HDMI. I wasted about an hour trying to figure out why it stopped near the end and never finished. Unplug the HDMI and goes straight through on the first try.
[Google TV General] Kalentia:
Weirdly enough, my issues aren't with casting or remote control. I'm having issues just doing regular content playback from the apps on the Chromecast... Netflix says "This title is not available to watch instantly", and Prime/Hulu/etc give similar errors when attempting to play content. My media server and casting local files work fine, so I know it's not an issue with video playback at the core.
[Google TV General] 96carboard:
Well, nettards basically treat their customers like criminals, which really gets in the way of things working correctly. This is the main reason I don't buy their crappy service. Why pay somebody to treat you like a criminal? This is especially since the only point of paying for their service is so you DON'T feel like a criminal by finding the content for free on the internet.
[Google TV General] Kalentia:
Alright, I've gone through the process of factory resetting and reflashing the Chromecast using the script (but without the Magisk boot image this time). Still facing the same issues, I've eliminated the idea that it could be a local network issue by connecting to a hotspot and the problem persists. I wonder if it's a DRM issue, given that Google couldn't "authenticate" the Chromecast upon setup and I had to set it up with the TV instead of my phone. Or maybe it's related to the fact that the TV I'm using only supports SDR... if anyone has suggestions please let me know.
[Google TV General] :
The explanation on github about this exploit mentions "flags that disable update mode" and "the config that forces it (burn mode)".

For a device that does not use secureboot, are these flags/config changeable in a normal non-secure environment? Or, can they only be changed via execution before the run_preboot_environment_command, as with this exploit?

I'm trying to enable v2 usbburning mode (update in the uboot menu) on a device that does not have it enabled, but does not use secureboot.
[Google TV General] npjohnson:
check the u-boot source linked in the exploit, it shows both of those flags being re-enabled.
[Google TV General] rezendes:
Can anyone confirm if this enables the software locked USB 3 speeds of the SoC for the Chromecast with Google TV?
[Google TV General] kennkanniff:
I also have the same problem on two devices. Prime and ATV+ do not work. Casting works fine.
[Google TV General] kennkanniff:
After rerunning the script I bricked a device. It does not boot to fasboot but is stuck at androidtv logo.

EDIT: I bricked another, this one is stuck at G logo. In both cases I flashed lineage-19.1-20220421-recovery-sabrina.img just before running the script. It is stuck at:

Creating filesystem with 4096 4k blocks and 4096 inodes

Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'metadata' (44 KB) OKAY [ 0.006s]
Writing 'metadata' OKAY [ 0.005s]
Finished. Total time: 0.640s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >

EDIT2: Is there any hope?
[Google TV General] npjohnson:
not bricked, hold button to get into burn, run exploit, chose to flash functional image in script.
[Google TV General] kennkanniff:
They dont boot into fastboot after the exploit. They are stuck at boot logo.
[Google TV General] p0werpl:
Can someone upload the super.img of QTS1.210311.036.7814738 from a device that has updated to that version? The only link available is an incremental update. Thank you.
[Google TV General] kennkanniff:
If you can guide me through it I can definitely help. I currently have two sabrinas on lineage 18.1. PM me.
[Google TV General] ubergeek77:
I went through this process today, but SetupWizard still tries to do a system update before letting me get to anything. There's probably already an official update newer than the one the script automatically installs. I cut the internet connection before it could finish the system update, but I'm pretty much stuck until I can figure out how to bypass that. At the moment I cannot enable OEM unlocking or ADB, since I have no way to get to the Settings app.

Since I'm on sabrina and the included LineageOS 19.1 recovery image isn't working, I flashed the 18.1 recovery image and it works fine. Although, it's a bit annoying to get into recovery mode, since I have to re-run the exploit every time just to get into fastboot and then boot to recovery, since I can't actually access the setting to enable ADB (is there a button combo or something to get into the Lineage recovery without attempting a factory reset every time? That would be nice).

I can access an ADB shell from the Lineage 18.1 recovery, but I'm hesitant to install Lineage 18.1 without properly unlocking the bootloader first (fastboot oem unlock fails), which I can't do without access to the Settings app.

Since I have root shell access from recovery, can I just disable SetupWizard from there, or enable ADB from there so I can spawn the Settings activity manually?
[Google TV General] npjohnson:
The exploit _unlocks_ your boot loader lol - if you ran it once you're unlocked.
[Google TV General] ubergeek77:
Gotcha. I figured, but I wasn't 100% sure since the first instruction on the Lineage page is to run the unlock command.

Well, time to install Lineage 18.1. No other option at the moment 😬 Nevermind, I just hacked my way through forcing stock to skip the setup wizard.
[Google TV General] ubergeek77:
I don't use Disney+, but Netflix and Amazon Prime Video aren't working on stock for me. Netflix and Netflix TV won't open at all (error ui-800-3 307006). Amazon Prime works "fine" until you actually start to play something, then it says "something went wrong."

I disabled the stock launcher entirely, and I've seen at least a few people mentioning that might be related to Netflix not working (can't imagine why though). But I've got no clue what's wrong with Prime Video.

I do have Magisk installed, and I tried adding both apps to Zygisk's denylist, as well as installing the Universal SafetyNet Fix. Still can't get either apps working.

Does anyone else here have either of these apps working? Any details on what your setup looks like would be great (stock launcher or not, Magisk installed or not, app sideloaded or installed from Google Play, etc).
[Google TV General] npjohnson:
Heres the deal - I can get a fully up to date image prepared that will work with DRM and all - but I need either:

* A firmware package of the newest firmware

* A dump of a device on the newest firmware.

Given we can't persist root or bootloader unlock to newer versions, this gets hard.

If someone gets me that I can make this all work fine.
[Google TV General] ubergeek77:
Ah, that makes sense. So these services are just blacklisting older firmwares for these devices? That sounds about right. Is this going to be an endless cat-and-mouse game for the DRM? Every time Google releases one, within a few weeks, everyone with a Chromecast gets their DRM shut off until they update?

Monitoring the device while it's in the middle of an update probably wouldn't be too hard, but I assume that only gets you a link to an OTA. And since it sounds too easy, I don't suppose you can "just" force the updater to skip the OTA and pull the factory image, making this tricky indeed.

Honestly, it sucks they don't just post these in the first place. I kinda understand why, but having literally every Pixel factory image ready to go for the last 3+ years has really spoiled me.

Do you know which apk is responsible for pulling those updates? I honestly don't think I'll find anything that hasn't already been looked into, but I can look anyway.
[Google TV General] npjohnson:
The newest "full image" can be queried and it's the one I used for the modded image currently.

If someone can get links to the two subsequent OTA zips on top of that one I can apply them locally and make a new modded image.

And no, good news is Google never updated this dongle :p haha.

Logcat during download would work
[Google TV General] ubergeek77:
Oh, interesting. I can manage a logcat during download, but I'll have to cut the network connection right after it starts to prevent it from updating and locking me out. And since you mentioned there's two OTAs, I probably won't be able to get the second one like this. Maybe we can do them one at a time?

I'm definitely interested in getting this for you, and I can give it a shot tomorrow. Some preliminary questions:

Is the full URL just simply logged on one line in logcat, no shenanigans?

Is it printed immediately as it starts, or will I need to wait a bit?

What's better? The Setup Wizard updater, the Settings updater, or does it not matter?

Knowing what to expect will make it a lot easier to get in and get out without an accidental update 😅
[Google TV General] npjohnson:
Yup, printed immediately, and settings.

Grep for googleapi
[Google TV General] ubergeek77:
Alright, I've got at least one of them, it's 158MB. Security patch level on the update screen says October 2021, so this is definitely the first of two like you mentioned.

I noticed people seem to avoid posting the direct links to these, so I'm assuming that's a bad idea for whatever reason (or maybe the link just expires quickly). I'll upload this somewhere, and maybe you can get me a factory image out of this that I can then use to get the second one.
[Google TV General] npjohnson:
Nah, link is fine. Pls post. It's not identifying. I will dump it locally
[Google TV General] npjohnson:
And yes I can get you booted on that firmware to get the next one.
[Google TV General] ubergeek77:
Alright, here you go:

https://android.googleapis.com/packages/ota-api/package/4351348667e5a100f58e0a8096f23959c1f30c5f.zip

Opening it up, this seems to be a partial OTA that takes the device from QTS1.210311.008 to QTS1.210311.036.
[Google TV General] npjohnson:
Perfect. Thx. Will aim to look this weekend.
[Google TV General] :
What you'll be putting together is a unified archive of the newest versions of all the partitions for the factory os, but also patched so that they can be safely used without risk of efuse changes that could disable usbdl?
[Google TV General] npjohnson:
To be exact, the bootloader partition is the only thing that is actually dangerous to flash.

You can flash every other image from newer packages and be fine just fine, but it won't boot.

On the vendor partition there are some TEE applets called TEETZ, they are files that end in .ta.

Those files have to match the installed bootloader, so what I do is unpack the latest full image that's available, apply all of the available OTAs via a python script.

Then I unwrite protect them, then pull the teetz files from the latest exploitable firmware, which match the bootloader that I expect you all to have to be able to run the exploit.

Then I package it up into a factory image and hand it to you all.

That way you're getting the newest firmware with just the TEE applets being old enough to interact with the bootloader that's much older.
[Google TV General] p0werpl:
Were you able to create a full image of the latest OTA (QTS1.210311.036.7814738)?
[Google TV General] npjohnson:
No, I aim to soon as I can. Work is crazy atm.
[Google TV General] npjohnson:
Got it working. It boots and all - grabbing newest OTA after setup and then gonna use that URL to gen an updated package. Most things work and no OTA pending.
[Google TV General] npjohnson:
okay, unlock script and repair script updated with newest version of stock.
[Google TV General] p0werpl:
Thank you. The flash script references dtb.img (should be dt.img).
[Google TV General] npjohnson:
Whoops.
[Google TV General] grave35:
In scripts repair.sh and unlock.sh missing vendor.img. Thank you for the work done!
[Google TV General] npjohnson:
Incorrect, OTA images have it as dt.img, and no pointing changing it, it flashes to dtb either way.

Fixed.
[Realme 7 Pro Questions & Answers] NickOp:
my phone is in bootloop bootloader is unlocked but the bootloader is rebooting again and again and i am not able to flash the stock rom file in it plz help
[Realme 7 Pro Questions & Answers] JSTN44:
did you fixed it?
[Realme 7 Pro Questions & Answers] JacobBoi_:
I had a similar problem and fixed it by Flashing a new Recovery screen.

(The custom recovery screen was: This )
[Realme 7 Pro Questions & Answers] iachino87:
same here! anyone can help me!?
[Advantage X7500, MDA Ameo ROM Development] anahi03:
Hello just got a X7510 and it is all in chinese lettering, how can I change it all to english?
[Advantage X7500, MDA Ameo ROM Development] elite-fusion:
same here,
[Google Pixel 5 Questions & Answers] Sean Hicks:
Hey Everyone,

I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."

I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.

Has this happened to anyone and is there a solution out there somewhere?
[Google Pixel 5 Questions & Answers] andybones:
Buying it "unlocked" means you bought it free of a carrier, such as Verizon, who lock the bootloader, and can't be unlocked.

But you still need to unlock the bootloader, it comes locked, for security reasons. So if you never unlocked it, it's locked.

I haven't installed beta 12 yet.

Do you have the latest SDK tools? (adb, fastboot, etc)

I was under the impression though, that you can't downgrade with a locked bootloader. But not sure.
[Google Pixel 5 Questions & Answers] AsItLies:
This probably isn't of any help now, but going forward, it may be. In Developer options, you can enable 'OEM unlocking'. As you can see now, it may well be a very good idea to enable that **before** you start messing with the phone, because if something does go wrong (as it has for you), then you can (hopefully) still get to fastboot and do 'fastboot flashing unlock'.

So, knowing this, you may want to keep an eye out for some tool or something that will allow you to possibly turn on oem unlocking (because your device won't boot).

Another thing to try is switching slots and see if the other slot boots? If you can get to fastboot try; fastboot --set-active=(a or b), then fastboot reboot. (If you don't know which slot is active, do 'fastboot getvar all', in the output it will tell you which is current.

cheers
[Google Pixel 5 Questions & Answers] jeboo:
Your bootloader being locked should not affect your ability to restore factory images/OTAs from Google. They are signed by Google and will pass the signature checks. You should try to download the latest factory image (either 11 or 12beta) and flash it via recovery => adb sideload.
[General Questions and Answers] pumukyPERFOMANCE:
I have an A20E sm-a202F with firmware A202FXXU3CUE9_A202FOXM3CUG1_PHE.

I am trying to flash with odin the AP file to remove the MDM, and it always gives me failure. I have tried with different ROMs and files and cannot remove it.

Can you help me?
[General Questions and Answers] pumukyPERFOMANCE:
help me, please
[General Questions and Answers] behtjes:
Did you find a solution?