OK, the standard firmware has already been downloaded. Update.exe returns an error.where there is a will, there is a way.. download the firmware said in topic.. for your device.
flash it from update mode.. if you dont have the command update.exe mode, I will upload a copy and all you have to do is add the images you downloaded into the images directory and click the restare.bat file and wait..
I personally custom a script that will auto flash everything back as if it was first bought.. that might help you..
just let me know.
EDIT: OOPSIE: I mean the stock firmware.. Download that for your device.. Not the Lineage ones..
you can do the lineage ones after you restore your device..
update mwrite dtb.img mem dtb normal update partition _aml_dtb dtb.img update bulkcmd "disk_initial 0" update partition dtbo dtbo.img update partition recovery recovery.img update partition super super.img update partition vbmeta vbmeta.img
Yes, I use wade-qt.20210326-factory.zip . Most likely I accidentally started flashing the firmware from adt-3 ((I can't help but notice the Cyrillic. Is the dynalink a popular device in Russia?
How did your device fail? Was it after installing this lineage release?
What are you using for "standard firmware". Is it the files within wade-qt.20210326-factory.zip, or another source?
I did this not too long ago, but I didn't keep any notes. I vaguely remember using commands like the following (using the files from wade-qt.20210326-factory.zip):
update mwrite dtb.img mem dtb normal update partition dtbo dtbo.img update partition recovery recovery.img update partition super super.img update partition vbmeta vbmeta.img I may have also used (but I'm not sure): update bulkcmd "disk_initial 0"
I think I got an rb error for boot.img and bootloader.img, but the existing partitions must have been okay, or else I was able to use fastboot by then to flash those partitions. Note that I hadn't used update before, so I was unfamiliar with its usage.
I have the TiVo Stream 4k as well. and I flashed that so called user debug build.. problem is this, when youWhat's the most direct and efficient way to "use burn mode to unlock by hand"?
And is that mode of unlocking what is happening when the user debug build for the tivo stream 4k (ts4k) unlocks the bootloader after being burned via the USB Burning Tool (as described in a previous post here).
As an aside, the bootloader on the ts4k is unlocked after burning the user debug build via the USB Burning Tool.
However, much care has to be used in unchecking both of the erase options in the tool, or else subsequent use of burn mode will be lost!
But if such care is exercised, the bootloader on the ts4k can be repeatedly unlocked simply by burning the user debug build as described above.
Burn the user debug build: bootloader unlocked
Allow OTA after burning the user debug build: locked
Burn the user debug build again: unlocked.
and so on, ad infinitum.
I'm curious about the mechanism by which this is happening. Is this sort of lock/unlock sequence an effect of using burn mode, or simply the nature of the distinction between the userdebug and user builds themselves?
It doesn't seem like it could be merely the builds?
Adding the ts4k to the list of compatible devices for this lineage release may be worthwhile at some point, given that tivo seems to be bailing on android/google tv while moving to its own embedded OS for smart tvs. Plus, the ts4k is still using version 9 of atv, so this lineage release may be an especially good repurposing of the ts4k.
I have the TiVo Stream 4k as well. and I flashed that so called user debug build.. problem is this, when you
goto setting it up so you can turn debugging on, it updates it self then locks everything down again.
So I never had a chance to really test it.. but I will say, the TiVo is fast with that DDR4..
I think I have way to many Android TV Boxes.. I retired from Development on Phones and got bored, so moved into Android TV Boxes as well as Routers.. Plus Love using TiViMate for my TV Viewing Pressures..
adb shell am start -a android.settings.SETTINGS
Hi, I have the same problem whis onn ((where there is a will, there is a way.. download the firmware said in topic.. for your device.
flash it from update mode.. if you dont have the command update.exe mode, I will upload a copy and all you have to do is add the images you downloaded into the images directory and click the restare.bat file ...
ill try again when I get time.. I know I have built bootloaders in the past for other amlogic devices.. and yes they worked.. compiling a bootloader is so confusing too.. but once you get the hng of it. its pretty easy. asuming I can get done what you said.. if I can find the bootloader board code for that device.. maybe change out the bootloader.. but as far as I know, even with that userdebug edition, the bootloader is still locked and cant overwrite it.. but ill look into it once again soon.. just done have the time right now.Userdebug builds are a real thing, not some sketchy so-called sort of thing. Userdebug is the type of build fingerprint that is seen in all of the FCC docs when a new device is submitted.
Usb debugging and root are already on in the userdebug build. So, if you have usb connected, you can open settings via the adb shell before you setup a wifi connection during the initial setup wizard:
adb shell am start -a android.settings.SETTINGS
And then following a process similar to this one from earlier in this thread, the ota update can be bypassed. At least for a while anyway.
What I was wondering in my prior post though is what the SoC and uboot know about this userdebug build, or userdebug builds in general. Do they automatically unlock the bootloader for any userdebug build, but not for a user build? Or do these particular builds (both user and userdebug) set bootloader lock/unlock status as they boot for the first time, and therefore the unlock obtained (by flashing the userdebug build) could be used for an alternative build like the lineage release that is the subject of this thread?
No, since my Onn's are in unwrapped boxes waiting for this ROM to be finished (not a very risky investment, because cheap).
And I would like to annoy you again with another noobish question (sorry): are any of these boxes equipped with HDMI surge protection? I have heard that the HDMI ports of cheap set-top boxes sometimes die because of the economy on extra diodes, and that the third-party solutions do not quite protect against this.
I don't think so?And I would like to annoy you again with another noobish question (sorry): are any of these boxes equipped with HDMI surge protection? I have heard that the HDMI ports of cheap set-top boxes sometimes die because of the economy on extra diodes, and that the third-party solutions do not quite protect against this.
When you say "the bootloader is still locked and cant overwrite it", do you mean uboot (the bootloader board code in ddr_enc.usb)? Which is distinct from "unlocking the bootloader" with fastboot commands in order to allow flashing?
If erase bootloader and flash are not unchecked, USB mode changes to GX-CHIP (from worldcup) and then USB burn mode access is lost, at least with the included password.bin. What causes this to happen? Something must be overwritten, what is it?
If the change from worldcup to GX-CHIP is because "the bootloader board" code is overwritten (when those two tool options are not unchecked), then the secure image must contain new bootloader board code, correct?
Do you remember offhand in which version of the firmware they disabled oem unlock (unlocking the bootloader to allow flashing)? Do you have a copy of the firmware for the last version that allowed this?
i get the sameNoob here. Having trouble with the install.
I believe I have the Onn unlocked ok and have the new Recovery img loaded.
When I try to push the new OS down using ADB I get this:
E: failed to verify whole-file signature
Update package verification took 38.9 s (result 1).
E:Signature verification failed
E: error 21
Install from ADB completed with status 2.
When I restart the device, it just loads the stock OS as if nothing happened.
I'm using the latest Lineage zip file on the downloads page for the Onn device.
Onn device has Firmware 1.01.32
Android security patch level August5. 2021
Build onn-user 10 QT 20210902 release-keys
Any idea what I'm doing wrong?
its not really a mod. its just a helper script for the devices listed in thread..
- Your warranty is now void. - You have been warned. - Use at your own risk.
adb reboot bootloader fastboot flash recovery lineage-18.1-20210805-recovery-dopinder.img fastboot boot lineage-18.1-20210805-recovery-dopinder.img adb reboot sideload adb sideload lineage-18.1-20210805-UNOFFICIAL-dopinder.zip # if successful then load bootloader and factory reset adb reboot bootloader fastboot -w fastboot reboot
this ended up being _wayyyyy_ to much, as this is the full value of the partition vs just the space to reserve, both will work, but we want to split it amongst partitions. One of our guys recalculated it and got it working.
Netflix and Amazon Prime 4k work with Magisk on stock, safetynet ctsProfile does fail but looks like it doesn't matter like OP said.This is is exactly what I've been waating to do just didn't want to go through the tedious parrt of figuring out the keymap remapping scheme . Could you share your changes or point me in the right direction? Also can I get some clarification on DRM is it working or not working ? The OP is a little confusing. If I understand correctly it is not working but only because od broken HW omx not bootloader unlock so it's just a bug not a limitation. Or is that incorrect? (I'll help with development btw, synced tree last night . Gonna dive in tonight)