TWRP for Amlogic devices.

[Ichijoe]

I'd like to ask something further more for the custom twrp.with this can i flash fw updates?img files only or the zip ones? Also with every fw update is necessary for a new update of twrp?f.e twrp for beelink gt1 is 103, now that 104 is up, there's need for a newer version of 104?tnx

Στάλθηκε από το Broken powered G2 D802 μου

I'm pretty sure you can flash both *.zip, and *.IMG Files through TWRP. But the biggest boon in using it is the ability to make Backups. In case you either need it, or want to start again from a cleaner state.

In my experience One version of TWRP is enough for anyone, yes there might be more going on in the background, and updating it would have its advantages. But, assuming that it was already working 100% for you then it shouldn't matter.

As always you should eventually rename the download File to 'recovery.zip', then place it on the root of your MicroSD Card, and test it before replacing the actual 3e Recovery.

[vrwmiaris]

I'm pretty sure you can flash both *.zip, and *.IMG Files through TWRP. But the biggest boon in using it is the ability to make Backups. In case you either need it, or want to start again from a cleaner state.

In my experience One version of TWRP is enough for anyone, yes there might be more going on in the background, and updating it would have its advantages. But, assuming that it was already working 100% for you then it shouldn't matter.

As always you should eventually rename the download File to 'recovery.zip', then place it on the root of your MicroSD Card, and test it before replacing the actual 3e Recovery.

Tnx, eventually is like how it works on android phones

Στάλθηκε από το Broken powered G2 D802 μου

[Ichijoe]

Tnx, eventually is like how it works on android phones

Στάλθηκε από το Broken powered G2 D802 μου

Exactly like it does on Phones.... TWRP should be the industry standard Recovery.

[calc]

And, as to enabling Debug Mode... I had already thought of that, and enabled it. Still couldn't get ADB on Linux Mint to pick up on it though. But, if I'm honest I think the WiFi & Bluetooth Chip on my YokaTV is wonky. As neither work the 2.4GHz (b/g/n), is up, and down more often then a 2$ Hooker, and 5GHz not at all. The Bluetooth also seems to be dead. Though the Device does seem to find, both my 5GHz SSID, and my Bluetooth TV. Connecting these things is an entirely different matter. So that could have well been the main issue. And, TBH I wasn't terribly assed to figure out where the /lan0 (or whatever) was located so as to go through the wire. When I already knew how to use the TerminalEmulator.

My box has a serial port header so I was able to get in that way while working on building CM13 recovery tonight. I'm not sure if the adb in mint is new enough since its for Android 5 instead of 6. You might have to build the new one to get network support. I'll have to take a look later to see if there is a way to do adb over usb without the otg port.

[Ichijoe]

My box has a serial port header so I was able to get in that way while working on building CM13 recovery tonight. I'm not sure if the adb in mint is new enough since its for Android 5 instead of 6. You might have to build the new one to get network support. I'll have to take a look later to see if there is a way to do adb over usb without the otg port.

Huh is that so?! Well there could be a simple way for me to test that theory out. In as far that I'm already running CM13 off, of my Phablet. And, the USB to that Device is not gonna be an issue for me. That said I should be getting a male to male (Type A) USB Cable anytime now.

Granted it's early days... But instead of the cheap HDMI Cable, and the additional useless Travel Plugs. I could almost wish that they've instead had packed up such an Update Cable instead. Or just kept continuing to have used Micro USB instead. That might have been enough to prevent me from having sent the first one back. Assuming it was somehow just some random softbrick. Though how that could have happened, while just surfing the Web though the Stock Browser, is lost on me.

Now all I want to do is to flash the BB2 Image over it in some hope that the WiFi, and Bluetooth may work again.

But, what I really like to know is. Is CM13/14 the end game here? And if its possible to do it here... How about CM12/13 for something like the S802? (MXIII)? Or would you think that a Bridge to far?

[calc]

I managed to get TWRP 3.0.2+ (git) built and loaded on my SunnyTV S912 but for some reason it looks really bad. Anyone happen to know how to make the current one display correctly? I never could get CM13 recovery to load all the way (hung on splash) and the guys in the dev irc channel said just to use twrp instead, lol.

I'm getting the following in recovery.log, It's giving me an error about "cannot find/open a drm device: No such file or directory" and also seems to be using the wrong pixel format, which is why it looks really weird. I also think I need to somehow disable the 'Swipe to Allow Modifications' slider since it would be very hard to do with a remote.

I'm trying to work towards getting CM13/14 working on it or perhaps OmniROM 6/7, but stuck at getting current recovery to work properly.

TW_NO_REBOOT_BOOTLOADER := true
RECOVERY_SDCARD_ON_DATA := true
TW_NO_BATT_PERCENT := true
I:Lun file '/sys/class/android_usb/android0/f_mass_storage/lun0/file' does not exist, USB storage mode disabled
I:Find_File: Error opening '/sys/class/leds/lcd-backlight'
I:Unable to locate brightness file
I:LANG: en
Starting the UI...
setting DRM_FORMAT_RGB565 and GGL_PIXEL_FORMAT_RGB_565
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
  vi.bits_per_pixel = 32
  vi.red.offset   =  16   .length =   8
  vi.green.offset =   8   .length =   8
  vi.blue.offset  =   0   .length =   8
setting GGL_PIXEL_FORMAT_BGRA_8888
double buffered
framebuffer: 0 (1920 x 1080)
Using fbdev graphics.
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 1.000000x and height 0.900000x, offsets x: 0 y: 0
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page splash
I:Switching packages (splash)
Found mouse 'aml_keypad'
(lots more)

[Ichijoe]

I would tend to agree with the IRC Devs on this matter... Cut to the quick and just use TWRP instead. That or maybe Philz Touch. But, in most instances TWRP wins hands down for what it is, does, and needs to do. Its the Recovery we need, (For every Device), and do not deserve.

But, onto the notion of porting CM1x. I was under a severe impression, that One had to have access to the Amlogic SDK in order to actually do it... Not that it (porting CM12 - or Stock Lolipop) wasn't possible for the older S802 SoC's. Just that you pretty much had to buy into the SDK, at some Bulk Commerical rate, and, sign some kind of NDA that you could never release anything built under it. Upshot... Buy our new Box instead! Which is why we've thus far never seen something like CM1x on Amlogic. Though I think there may have been a few Rockchip Devices that had managed a port.

But, boy how I would welcome an Android TV bent version of CyanogenMod.
Actually I find myself wondering why the heck they're not already dumping the AndroidTV OS into these Boxes as is.
I get that it was a bandage before. But if it weren't for the fact that the Xiaomi Mi Box only had 1Gb of RAM in it I'd have gone with that over this Box in a heartbeat. If only cause it ships with the AndroidTV OS, and not just Tablet Android.

[calc]

But, onto the notion of porting CM1x. I was under a severe impression, that One had to have access to the Amlogic SDK in order to actually do it... Not that it (porting CM12 - or Stock Lolipop) wasn't possible for the older S802 SoC's. Just that you pretty much had to buy into the SDK, at some Bulk Commerical rate, and, sign some kind of NDA that you could never release anything built under it. Upshot... Buy our new Box instead! Which is why we've thus far never seen something like CM1x on Amlogic. Though I think there may have been a few Rockchip Devices that had managed a port.

But, boy how I would welcome an Android TV bent version of CyanogenMod.
Actually I find myself wondering why the heck they're not already dumping the AndroidTV OS into these Boxes as is.
I get that it was a bandage before. But if it weren't for the fact that the Xiaomi Mi Box only had 1Gb of RAM in it I'd have gone with that over this Box in a heartbeat. If only cause it ships with the AndroidTV OS, and not just Tablet Android.

You were mostly correct, but I do not want to comment on this at the moment...

[Ichijoe]

You were mostly correct, but I do not want to comment on this at the moment...

Well in any case best of luck to you...

[abdul_pt]

Yep... That's what happens when you neglect to troll through 70+ Pages 😌

And, as to enabling Debug Mode... I had already thought of that, and enabled it. Still couldn't get ADB on Linux Mint to pick up on it though. But, if I'm honest I think the WiFi & Bluetooth Chip on my YokaTV is wonky. As neither work the 2.4GHz (b/g/n), is up, and down more often then a 2$ Hooker, and 5GHz not at all. The Bluetooth also seems to be dead. Though the Device does seem to find, both my 5GHz SSID, and my Bluetooth TV. Connecting these things is an entirely different matter. So that could have well been the main issue. And, TBH I wasn't terribly assed to figure out where the /lan0 (or whatever) was located so as to go through the wire. When I already knew how to use the TerminalEmulator.

*Quick update*
I went back to page 75, and found the link to the YokaTV KB2.... Sadly unlike some other S912 version I tried earlier this would also seem to be an incorrect version.
For startes that version, can NOT pickup on my MicroSD Card, where I keep these Firmwares (more or less safe). Secondly when I try to flash the BB2 (Mecool Firmware), in whatever hopes of recovering both the WiFi, and Bluetooh. I'm greated by an Error 17. This is a BB2 / KB2 Firmware, and this is a "p212" Device. So I fear that I'm not going to get very far with that Recovery

*Further update*
That other Recovery which was the one above the One ment for my Yoka Box... lol!
The Nexbox A1(IIRC), which unlike the former is able to see the MicroSD Card
However the same Error 17 incorrect Firmware type (as above), remains.

Thanks....

Try this one - www.freak-tab.de/abdul_pt/aml/TWRP_Yoka_KB2.img

That error you can fix it by editing the updater-script and removing the assert check in it.

[abdul_pt]

Here is the data for the SunnyTV Q9S (Amlogic S912):

http://www.mediafire.com/file/jwhilb...ecovery.tar.gz

Try this one - https://www.freak-tab.de/abdul_pt/am...unnyTV-Q9S.img

[abdul_pt]

I managed to get TWRP 3.0.2+ (git) built and loaded on my SunnyTV S912 but for some reason it looks really bad. Anyone happen to know how to make the current one display correctly? I never could get CM13 recovery to load all the way (hung on splash) and the guys in the dev irc channel said just to use twrp instead, lol.

I'm getting the following in recovery.log, It's giving me an error about "cannot find/open a drm device: No such file or directory" and also seems to be using the wrong pixel format, which is why it looks really weird. I also think I need to somehow disable the 'Swipe to Allow Modifications' slider since it would be very hard to do with a remote.

I'm trying to work towards getting CM13/14 working on it or perhaps OmniROM 6/7, but stuck at getting current recovery to work properly.

TW_NO_REBOOT_BOOTLOADER := true
RECOVERY_SDCARD_ON_DATA := true
TW_NO_BATT_PERCENT := true
I:Lun file '/sys/class/android_usb/android0/f_mass_storage/lun0/file' does not exist, USB storage mode disabled
I:Find_File: Error opening '/sys/class/leds/lcd-backlight'
I:Unable to locate brightness file
I:LANG: en
Starting the UI...
setting DRM_FORMAT_RGB565 and GGL_PIXEL_FORMAT_RGB_565
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 16 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 0 .length = 8
setting GGL_PIXEL_FORMAT_BGRA_8888
double buffered
framebuffer: 0 (1920 x 1080)
Using fbdev graphics.
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 1.000000x and height 0.900000x, offsets x: 0 y: 0
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page splash
I:Switching packages (splash)
Found mouse 'aml_keypad'
(lots more)

add this to BoardConfig.mk

TARGET_RECOVERY_FORCE_PIXEL_FORMAT := "RGB_565"

might solve it, i would need to know more to be sure.

CyanogenMod recovery, since CM12 is very much alike the stock 3e recovery. If i were you i wouldn't waste time on it.

[abdul_pt]

Wireless ADB usually is enable by default on this devices. Normally only works over Ethernet.

if not adding this lines to build.prop might be enough to make it work

service.adb.tcp.port=5555
persist.service.adb.enable=1

On my images you can flash boot,recovery and logo as standalone images, other partitions need to be throw zip. Full image Rom's aren't supported

[calc]

Try this one - https://www.freak-tab.de/abdul_pt/am...unnyTV-Q9S.img

Thanks! Works great.

Do you happen to have the repo you used to create these public somewhere? I've been fighting with it for a while now and still can't determine what I'm doing wrong.

[abdul_pt]

No, i'm in the process of cleaning them for upload.

But if you have yours throw me a link so that i can help out. I would also need to know what source are you using to build TWRP. Like CM or Omni and branch