SDMC DV8519 SoC Amlogic S905X2 Custom rom

Search This thread

goapy

Senior Member
Dec 30, 2021
156
39
If you can boot to temporary twrp, you could make a shell script that could enable adb on the next reboot of the regular os, which you could use to enable wi-fi and disable the tv app on the next boot of the regular os. in an adb shell.

All of those options may not work, but some should.

Code:
# echo "#!/bin/sh
resetprop persist.service.adb.enable=1
resetprop persist.sys.usb.config=mtp,adb
sleep 30
settings put global development_settings_enabled 1
settings put global adb_enabled 1
settings put secure install_non_market_apps 1" > /data/adb/service.d/enable-usb-debugging.sh

# chmod +x /data/adb/service.d/enable-usb-debugging.sh

The "#" at the start of the first and last line above represents your twrp terminal prompt, not something to type. Note the placement of the two quotation marks, one each at the beginning and the end.

If the above works to enable adb on the next boot of the regular os, you can use adb to execute the following:

svc wifi enable
pm disable-user --user 0 com.ug.eon.android.tv
pm disable-user --user 0 com.sdmc.standbyservice
pm disable-user --user 0 android.autoinstalls.config.sdmc
pm disable-user --user 0 com.sdmc.GlobalKey
pm disable-user --user 0 com.ug.eon.android.tv.ftu
pm disable-user --user 0 com.ug.eon.systemservice
pm disable-user --user 0 com.ug.eon.qoeagent
pm disable-user --user 0 com.ug.eon.rcu.t4h
pm disable-user --user 0 com.ug.eon.rac
pm disable-user --user 0 com.ug.eon.android.tv.eonotaupdater
pm disable-user --user 0 com.ug.eon.android.tv.customizationapp
pm disable-user --user 0 com.ug.eon.cdnresolver

If the above doesn't work, you can try the Dhiraagu firmware, which also uses a non-encrypted bootloader.
 
  • Like
Reactions: kalehrl

Y300-0100

Senior Member
Aug 11, 2014
310
267
Podgorica
Thanks for quick reply. Now I have another issue. My serial number is now 1234567890. Must be from previous custom rom and mac address is different. Any idea in which partition contains SN and mac address? Or how to edit that file in order to set info for new box? Also widevine is no level 3. :)
 

goapy

Senior Member
Dec 30, 2021
156
39
Did you have the erase boxes checked in the gui version of the usb burning tool? If so, all of that is probably gone.

If you didn't have the erase boxes checked in the gui version of the usb burning tool, what exactly did you do? Be specific.
 

kalehrl

Senior Member
Nov 22, 2017
761
321
Code:
# echo "#!/bin/sh
resetprop persist.service.adb.enable=1
resetprop persist.sys.usb.config=mtp,adb
sleep 30
settings put global development_settings_enabled 1
settings put global adb_enabled 1
settings put secure install_non_market_apps 1" > /data/adb/service.d/enable-usb-debugging.sh

# chmod +x /data/adb/service.d/enable-usb-debugging.sh
How to run this script in temprorary TWRP?
Where to save it?
What option to use when booted into TWRP?
 

Y300-0100

Senior Member
Aug 11, 2014
310
267
Podgorica
I have managed to burn original SN from label using USB burning tool. Overwrite SN. And now box shows original number but widevine is still 3. Any ideas fow widevine?
 

goapy

Senior Member
Dec 30, 2021
156
39
widevine is still 3. Any ideas fow widevine?

I flashed partition by partition.

When you flashed partition by partition, are you sure that you also flashed the copy of the bootloader partition from your untouched device?

L1 is probably erased from your prior adventures with the burning tool, but it is worth checking whether or not you're using the original bootloader.

Also, aml dtb in android 9 is encrypted. The copy provided by the dumping tool is not encrypted. In order to get the original encrypted dtb source, dump the first GB or so from mmcblk0 (on your untouched device) using dd. Then you can find the encrypted dtb using a hex editor, and flash it to your other device.
 

Y300-0100

Senior Member
Aug 11, 2014
310
267
Podgorica
When you flashed partition by partition, are you sure that you also flashed the copy of the bootloader partition from your untouched device?

L1 is probably erased from your prior adventures with the burning tool, but it is worth checking whether or not you're using the original bootloader.

Also, aml dtb in android 9 is encrypted. The copy provided by the dumping tool is not encrypted. In order to get the original encrypted dtb source, dump the first GB or so from mmcblk0 (on your untouched device) using dd. Then you can find the encrypted dtb using a hex editor, and flash it to your other device.
yes. and I also write my original serial number and gain widevine L1 using USB burning tool.
 

Attachments

  • xda.jpg
    xda.jpg
    137.6 KB · Views: 57

goapy

Senior Member
Dec 30, 2021
156
39
Well, I didn't know that you had saved keybox files. Congratulations on getting it working.
 

bboyg

New member
Jan 9, 2011
2
0
Hello, I also have the Bulgarian version, but I`m not very familiar with most of the terms here. Can someone create a image file with bypassed activation for EON TV in order to use the SD Card Update method as this is the only option I have?
I really like the box and the BT remote, but can`t use it :(
 

david0vich

New member
Oct 20, 2013
2
0
I have managed to change original FW on SDOTT0202 FCC ID: 2AUWA-ATV4K8519 PS 5V 2A with this one "[v9] Aidan's ROM (H96 Max X2) [S905X2] [ATV9] (u211 & u214) FB-Cruz Enrique García.img".
BT is working and WIFI works below CH 100 on 5Ghz.
Widevine I didn't test it.

NOTE: If your model is SDOTT0202 FCC ID: 2AUWA-ATV4K85198 PS 12V 1A
Do not try to flash or you will end up with non-functional WIFI and remote control that works only 20-30 cm from the device.:mad:
 
Last edited:

galaxy94

Member
Aug 26, 2015
10
0
Hi, which firmware is compatibile with 85198, i made mistake and flash.. remote conttrol works 20-30 cm..
 

galaxy94

Member
Aug 26, 2015
10
0
i can't find any compatibile firmware, did you flash your 85198? if not you can make twrp backup and share me.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1

    @kalehrl

    @galaxy94

    Hi, if it helps to make firmware image I have make a dump of SDOTT0202 / DV8519 following files using Amlogic dump utility.
    Pics in attach.
    Can you share the files?
    I can try to make an image out of those files using amlogic kitchen.
    1
    The wifi+bt combo module in the eon version (as pictured above in post #8) is the ap6398s, which uses the broadcom bcm4359.

    I have original firmware for a bunch of dv8519 and dv8535 devices, but I wouldn't suggest anyone flash any of them before verifying that the device tree and bootloader match. In order to do this, you'd have to dump at least the bootloader and the device tree blob from your device before you overwrite it with anything else.
    Hi. Can you please share original firmware for DV8519. Thx.
    1
    If you can boot to temporary twrp, you could make a shell script that could enable adb on the next reboot of the regular os, which you could use to enable wi-fi and disable the tv app on the next boot of the regular os. in an adb shell.

    All of those options may not work, but some should.

    Code:
    # echo "#!/bin/sh
    resetprop persist.service.adb.enable=1
    resetprop persist.sys.usb.config=mtp,adb
    sleep 30
    settings put global development_settings_enabled 1
    settings put global adb_enabled 1
    settings put secure install_non_market_apps 1" > /data/adb/service.d/enable-usb-debugging.sh
    
    # chmod +x /data/adb/service.d/enable-usb-debugging.sh
    
    The "#" at the start of the first and last line above represents your twrp terminal prompt, not something to type. Note the placement of the two quotation marks, one each at the beginning and the end.
    
    If the above works to enable adb on the next boot of the regular os, you can use adb to execute the following:
    
    svc wifi enable
    pm disable-user --user 0 com.ug.eon.android.tv
    pm disable-user --user 0 com.sdmc.standbyservice
    pm disable-user --user 0 android.autoinstalls.config.sdmc
    pm disable-user --user 0 com.sdmc.GlobalKey
    pm disable-user --user 0 com.ug.eon.android.tv.ftu
    pm disable-user --user 0 com.ug.eon.systemservice
    pm disable-user --user 0 com.ug.eon.qoeagent
    pm disable-user --user 0 com.ug.eon.rcu.t4h
    pm disable-user --user 0 com.ug.eon.rac
    pm disable-user --user 0 com.ug.eon.android.tv.eonotaupdater
    pm disable-user --user 0 com.ug.eon.android.tv.customizationapp
    pm disable-user --user 0 com.ug.eon.cdnresolver

    If the above doesn't work, you can try the Dhiraagu firmware, which also uses a non-encrypted bootloader.