- Status
as I went over with you on the other thread - follow the wiki and it will work - I just flashed a build an hour ago, it works fine.
It's been a month and a half since we discussed the possibility of the tablet-flavored (non-TV) release. It seems that the number of complaints has decreased and the basic quality of builds has improved enough to bother you again in this regard: are there any positive changes in this direction, or it is not worth expecting to get a full-featured Android on dopinder? (I'm still following this thread carefully to make a buying decision.)
I've been watching this closely and at the moment I'm not going to be flashing it (the broken hardware omx is a bit of a breaker at the moment) but due to more recent experiments I've done is adoptable storage on LineageOS for these targets enabled and is it stable?
I forced it on Android TV 10 (stock) and it seemed to "work" but it made the whole OS unstable while accessing the drive. It would reboot randomly while transferring data or sometimes when just enumerating the installed applications. Occasionally it would fail to properly mount in the device and while it was listed it also said that the drive wasn't present. Eventually I gave up and removed it for the time being.
I forced it on Android TV 10 (stock) and it seemed to "work" but it made the whole OS unstable while accessing the drive. It would reboot randomly while transferring data or sometimes when just enumerating the installed applications. Occasionally it would fail to properly mount in the device and while it was listed it also said that the drive wasn't present. Eventually I gave up and removed it for the time being.
New builds are going up tonight/tomorrow with October ASB
hardware OMX isn't that big a deal, all media still plays, and there's no "battery life" to worry about.
And yeah, adoptable storage is a bad idea, it isn't internal storage, and is at USB2 speeds - yeah, nah.
I have a quick problem (hopefully) picked the Onn 4k Tv box last week got force updated on start running stock OS 10 QT 20210902 firmware 1.01.32 I'm hitting a wall OEM unlock doesn't show up and I cant fastboot option doesn't detect device. I feel like I might be missing something or they changed something and started locking out mods. I followed the instruction cant figure out what's wrong
First off, would like to start by thanking all the team for this project.
I just received my Onn device after two weeks of shipping
and was ready to start the flashing.
But, first, October’s build are not yet ready I think (`An unknown error occurred`), and second, after reading the message of @R3s1du3, I’m hesitant to boot my device. The instructions clearly specify that:
> Warning: Before following these instructions please ensure that the device is on the latest Android 10 firmware.
but at the same time, it seems that connecting it to the internet would force an update that, a priori, disables OEM unlocking, at least option not visible in the Developer options.
What should I do?
I just received my Onn device after two weeks of shipping
and was ready to start the flashing.But, first, October’s build are not yet ready I think (`An unknown error occurred`), and second, after reading the message of @R3s1du3, I’m hesitant to boot my device. The instructions clearly specify that:
> Warning: Before following these instructions please ensure that the device is on the latest Android 10 firmware.
but at the same time, it seems that connecting it to the internet would force an update that, a priori, disables OEM unlocking, at least option not visible in the Developer options.
What should I do?
I'm fairly certain the update doesn't block oem unlocking... worst case scenario bulkcmd commands are still available.
So, factory reset, set up (not on VPN or custom DNS), and go to dev settings, it's greyed out?
Hold off if you want but I struggle to believe they locked the bootloader forcibly.First off, would like to start by thanking all the team for this project.
I just received my Onn device after two weeks of shipping
But, first, October’s build are not yet ready I think (`An unknown error occurred`), and second, after reading the message of @R3s1du3, I’m hesitant to boot my device. The instructions clearly specify that:
> Warning: Before following these instructions please ensure that the device is on the latest Android 10 firmware.
but at the same time, it seems that connecting it to the internet would force an update that, a priori, disables OEM unlocking, at least option not visible in the Developer options.
What should I do?
Well, it works! Sure, "OEM unlock" does not appear in Developer settings, but I was able to unlock just fine. I also followed the instruction given by @criscodecookies in https://xdaforums.com/t/unofficial-...-g12-sm1-family-devices.4313743/post-85434073.
1. Settings > Privacy > Ads > Opt out of Ads Personalization ;
2. Disable automatic updates from Play Store ;
3. Enable "Developer options" and "USB debugging" ;
4. I recommend people to downgrade Android TV Home to version 2 :
5. Download and sideload F-Droid ;
6. Install Aurora Store from F-Droid app and spoof "Realme 5 Pro" within the app ;
7. Because Netflix TV is not yet supported by this ROM due to OMX, search and install Netflix from within Aurora Store ;
8. Generate and sideload an Android TV shortcut for the sideloaded Netflix using this generator :
9. Sideload MATVT and follow these instructions after installation to get a working virtual mouse (by default, long press on "mute button" will toggle between scroll and mouse mode) ;
That being said, I’ve not been able to login into Netflix using the remote :/
1. Settings > Privacy > Ads > Opt out of Ads Personalization ;
2. Disable automatic updates from Play Store ;
3. Enable "Developer options" and "USB debugging" ;
4. I recommend people to downgrade Android TV Home to version 2 :
Code:
adb install -d './com.google.android.tvlauncher_2.3.1-340788485-f-1010901809_minAPI26(nodpi)_apkmirror.com.apk'6. Install Aurora Store from F-Droid app and spoof "Realme 5 Pro" within the app ;
7. Because Netflix TV is not yet supported by this ROM due to OMX, search and install Netflix from within Aurora Store ;
8. Generate and sideload an Android TV shortcut for the sideloaded Netflix using this generator :
Code:
Name: Netlfix Launcher
Package: com.netflix.mediaclient
Logo: https://play-lh.googleusercontent.com/TBRwjS_qfJCSj1m7zZB93FnpJM5fSpMA_wUlFDLxWAb45T9RmwBvQd5cWR5viJJOhkI=s180
Banner: https://play-lh.googleusercontent.com/ybf8V_yUFpSgW-rs1r7oigzSAWIQcSHCwHd2EYkxRD0KGz8CNBp0DN8T1Rz17KvJJSYlThat being said, I’ve not been able to login into Netflix using the remote :/
Last edited:
Can someone confirm that this OTG cable works with dopinder? I would like to power it AND use the usb port.
It works for me but Amazon has terrible quality control so it should work for you
Any limitations to this version of Netflix? If it's software decoding, can it smoothly play 4K HDR?
I finally got it working not sure what the issue is had the sideload rom 3 times before it stopped erroring out aside from the Netflix and HBOmax issues I noticed everything displays fairly well on a 4K monitor but if i switch over to a 1080p display things are fuzzy (text apps) and I cant adjust display settings in OS
@npjohnson I am unable to ADB into the Walmart Onn UHD Box (dopinder). When I enable Developer Options, it says " Developer options are not available for this user". I would like to get LineageOS on this box. Any help is appreciated. Thanks.
Last edited:
cannot connect to 10.0.0.18:5555: No connection could be made because the target machine actively refused it. (10061) . This is the error I get when trying to connect to ADB wirelessly . I never get a prompt any reason why ?it never seems to want to connect . USB debugging is enabled I have tried to turn it off and on but no go .
- Status
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
29
Amlogic G12*/SM1 Family Devices
Code:- Your warranty is now void. - You have been warned. - Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Amlogic G12*/SM1 SoC family of devices.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed:
Official Builds:
Disclaimer: My unofficial builds have full Android TV Google Apps and some other goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.
Unofficial Builds:
- deadpool - Google ADT-3
- dopinder - Walmart Onn UHD Box
- sabrina - Chromecast with Google TV
- wade - Dynalink TV Box (4K)
We also support a few development boards, but at least (for now, until we have time to write up instructions), you're on your own to figure out the install process and set things up:
EDIT: The development boards don't boot on LineageOS 19.1 at the moment for some reason, we're looking into it.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
- Recent apps/Multitasking menu doesn't launch.
- (sabrina only) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
- (dopinder/sabrina) L1 is currently broken, this is what is holding up official builds for these devices.
- GApps are baked in on Unofficial builds - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
- Firmware is shipped in the ROM package for this device, so you'll end up on the newest version of compatible firmware after install. Please don't touch firmware partitions after install.
- On the unofficial OTA is provided the same way officials would have them.
- Find any more on an official build? Report them according to this guide.
- Does L1 Widevine DRM break when I unlock my bootloader?
Nope, it works fine. L1 certificates, and the mechanism that reports is all still exist and work as expected.
- Can I haz Netflix?
Yup! Play Store has it for you. Unless you're on dopinder or sabrina, but that will be fixed soon hopefully.
- Is this Android TV or Google TV?
Android TV, with some of the better components of Google TV.
- Can I go back to stock and relock the bootloader?
Yeah, grab the factory image for your device and flash it just like you would for a Pixel device, you can find the factory images here. Don't know it I'd relock though, consider that process largely untested on these device. Especially on sabrina, where you can't necessarily re-unlock should you ever want to.
- Are these the stock codenames for these devices?
Astute observation, no, they are not. The ADT-3 is actaully `adt3`, but earlier in production is was `deadpool`, which is much cooler. The Dynalink box internally is extremely similar to the ADT-3, so we coined it `wade` after Wade Wilson, AKA deadpool. The Onn box is in the same family, but different enough to coin it `dopinder`, after, well, go watch Deadpool the movie I guess. sabrina is actually the codename given by Google - no clue as to the reason.
- Does it pass SafetyNet?
Maybe - the only sure fire way it Magisk, as our boot loader is unlocked and can't be relocked safely.
- Does the stock remote work?
Yup, just like it would on stock, in-remote-microphone and all! If it's an IR remote like wade's, it will even work in recovery!
- Can we we support higher resolution than 4K, higher FPS, or HDR on non-certified screens?
Nope.
- I have a very similar device! Can I install these builds and use them?
No. Please don't do that. You will brick your device, as we include firmware and bootloader images.
If you're a developer looking to help port to a new device, contact me.
Kernel Source: https://github.com/LineageOS/android_kernel_amlogic_linux-4.9
Contributors:
- npjohnson
- bgcngm
- stricted
- webgeek1234
- deadman96385
- trautamaki
- luca020400
- aleasto
14
Found a procedure for dopinder without the need for keyboard/OTG.
The docs under "Installing a custom recovery using fastboot" state to use "adb reboot fastboot" which doesn't work for booting recovery, needed to do "adb reboot bootloader" instead.
Full command log (after unlocking bootloader and re-enabling USB debugging) of the install process with just a regular Micro USB to USB A cable:
Code: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
Successfully booted to LineageOS after this!6Note:
Since the Lineage Android TV Builds for this little box (aka Boxes), are stable for the most part, but seems
people are bouncing back in forth from Stock to Lineage and back to stock.
I created a batch file that will auto flash the stock images and wipe data and so on.. pretty much it will
make your box as it was when you first booted it after taking it home to try it.
2nd, I also created a batch file that will backup current images.. No need for a fancy recovery or anything like the
such. it will use the worldcup or what I like to say, USB Burn mode, and backup each and every partition.
as well as some not so much needed ones like, misc and metadata. (Just for giggles)..
backups will be copied to backup dir, I also created a separate batch file to restore your backup.
I am one that hates doing things the long way over and over, so I always create ways to make things simple
in the future for people.
This way, you all can test your hearts out all the new lineages and still have your full Stock backup (including data).
and restore back in forth as you wish.
I will upload the backup_restore zip package as soon as I can and with @npjohnson permission I will link
in thread. Otherwise you will have to just DM/PM me and ill link you the location.
I am just trying to help the many that I seen complain and dont understand how to go back in forth.
so with this script, it should take care of most on that. No Fancy Recovery needed...
you will need worldcup driver for Amlogic........ you can find that on your own.
Also, to get into USB Burn mode, press side button while plugging in USB cable.
Keep pressing till you see the LOGO or hear the sound from your computer.
then just run the batch file and wait..
if its easier for you:
Run the batch file, it will keep saying waiting for device..
Just press the side button while plugging in USB, when you see it start, then release button...........
and wait till finished..
Only TESTED On Dopinder Boxes, but im sure they are all the same as for the partition layouts.
