rmr_md

Is your Legends Flashback the 2018 (50 games) or 2019 (100 games) version? You can't flash the firmware from the 2018 version in the 2019 FB. The only way to fix a soft-brick is reflashing the device using the Rockchip tools and a good backup. Are you familiar with soldering? You will need to short a couple of points to enable USB data transfer mode. I managed to do that with clear tape, but soldering the jumpers would be easier. If your Flashback is the 2018 model, I can help with the files to recover the device.

Search for imgRePackerRK in xda-developers, it can be used to extract the img file. This devices doesn't run Android, it runs a very optimized Linux build (14MB rootfs partition if I recall correctly)

This is not feasible in both hardware and software levels. HW: there is no analog output, at least easily available. SW: OS is hardcoded to output audio to HDMI. If you want this level of customization you need to start looking for a Raspberry Pi running Retropie.

It's technically possible, the device is almost the same as the Legends FB 2018. Problem is time and interest, I've worked in the Legends FB 2018 because I have the device. I don't have the Legends FB 2019 and I don't think it's fair to clone it to another device to work on the CFW. While the mods are somewhat safe, I don't like the idea to mod without any test. Also, the latest update removed the shortcut to add coins from the "console" cores, I've used this "hidden feature" to map arcade cores to console cores that were not available in the device.

The 2018 never got the SNES core. It has the entry in the menu but no core inside. I added it in the last cfw (based on v2.8.4)

MAME/Arcade games don't work with the official firmware. And there is no CFW for the Legends 2019 (the one with 100/110 games). Sega CD might work (I don't have a device to test) but you need the bios files in the same folder (bios_CD_U.BIN for US games)

It's broken, and don't expect it to be addressed by AtGames as it's not broken on 'their side'; That's the way the hack works, I'm using one of the unused cores and adding the custom core there. The new retroplayer doesn't have the shortcut to add coins anymore for console cores, I used the cores 'reserved' for Atari 2600 and Colecovision to replace with MAME2000 and FBA. The workaround is to use a Genesis controller (the Mode button works as coin when you press it twice) or use the Menu button on the device. Other solutions would be use the old retroplayer (downgrade to v2.6) or replace the emulator. I've tried to build RetroArch for this device a couple of times but the mali drivers are crappy and I couldn't run it - it built fine thought.

The new firmware for the FB2018 (v.2.8.4) is basically a copy of the 2019 FW, same menu and and same player, that's why you can see .fig and .a26 files but you can't load them, the additional cores were not added to the console. To make it 'worse', something was changed on the player and the not only some controller mapping were disabled but the shortcut to 'add coins' to non-arcade cores was also removed. This partially 'broke' the MAME 2000 core in my CFW, and the only way to 'add coins' in the MAME 2000 core now is pressing the Menu button in the console twice, or pressing "Mode" twice with a Genesis controller. The FB2019 is what is is, the reason I created a 'custom firmware' for the FB2018 was to enable additional extensions to the existing cores. Atari 2600 games (a26) won't load because there is not Atari core inside. For ColecoVision, try running the games with the extension .cv, I've seen some references to this extension inside the menu binary. And answering your other questions. The Mode button in the Genesis controller cannot be mapped. It's always mapped as the "Menu" button.

Add coins on the arcade games, I suppose... If you are using the CFW based on version 2.8.4, Use the shortcut start+down or try to access the menu twice. I use a Genesis controller to test the CFW and the mode button works as "menu", pressing mode twice add coins. I need to confirm how it works with the original controller.

This is for the Legends Flashback 2019 only, and it doesn't have the games. You can search for a tool called ImgRePackerRk to manipulate the .img files.

@BD-ROSS, this update should fix your problem with the 2 games: Legends Flashback (2019) Update 0.1.16 for users with issue with Super Star Wars 2 and 3 Let me know if it works. It's the same update from the site but I used the original file names for these 2 games in all-games.ini.

I haven't seen an official release notes but it seems that they ported the improvements from the Legends FB 2019. They also removed FBA from the device, so Ghouls 'n' Ghosts is running with MAME 2003 Plus. You should contact Atgames to report this issue. Super Star Wars was moved to the 'emulator' partition on this update, but the other 2 still in the 'rom' partition. all-games.ini (list of games) was moved to 'emulator' partition also, but all the references look correct. I don't have the device, but looking at the files inside the update everything should be good. [EDIT] I've found the issue. AtGames released an update in Nov-14 changing the ROM partition and they renamed Super Star Wars 2 and 3. This update was removed from the site and the new update replaces only the emulator partition, but they kept the new naming. I can create a non-official update with this corrected if you want to test, but I definitely would contact Atgames. @Bill Loguidice, could you take a look at this internally? The original games were named SuperStarWars2_splash_patched_20190715_1.fig and SuperStarWars3_splash_patched_20190715_1.fig, but the last update have them named as SuperStarWars2.fig and SuperStarWars3.fig!

It is, but the device is totally different from the Genesis FB 2018/Atari FB9/X/Legends Flashback. It has an older/slower processor and the OS is Android instead of Linux. The device can run RetroArch (after a lot of tweaking in the source code) with some cores, and it's possible to hack the menu apk to load a different emulator instead of the native emulator. I've been testing this for a while, and I CFW might be ready for release soon.

2019 model is not modded yet, so only built-in extensions support (genesis, NES and SNES).

I noticed the same thing playing with my Genesis FB and Legends FB 2018. I've tried to compile RetroArch, but I had no video output due to the X11 implementation of the Mali driver. I've tried OpenGL/OpenGL ES/SDL2/X11, no luck. After several attempts I just gave up... About Stella 6, I have my doubts it it would be possible, reading the Retron77 thread I had the impression that the devs had a hard time to port it, and the R77 runs on a quad-core processor.

Yes, there is something being worked for the Genesis Flashback HD 2017...

No, these are the extensions that fba supports, not what you can actually run. FBA needs some specific tweak to load these systems, and I personally not tried working on this.

The hardware is too weak for that, it's a dual-core processor. SNES can run with restrictions (older core) but you would need to sacrifice one core, as the cores and extensions are hard-coded in the menu. Linux has a lot of variables (X11, framebuffer, SDL) which makes it difficult to work if you are not a developer (and I'm not) or familiar with the OS. Optimize the OS is only possible if you have the source-code and drivers, and the only source code available for this hardware are for the libretro cores. Also, it's very difficult to work with a 14Mb partition. Some parameters can be changed with Linux/Rockchip tools (like GPU and CPU speed and voltage), but for the most part you are restricted to what you have. The 2017 hardware is different, while the processor is older, Atgames included a large NAND (2GB/4GB), and the device runs Android instead of Linux. Android is much more standardized so it's easier to run stuff after the menu apk was reverse-engineered, or you can just create a new menu. I've built RetroArch for this device running Android (Genesis Flashback HD 2017), the 2018 and Legends FB was a no-go... it compiled file but I couldn't load video.

Colecovision doesn't work with the Legends Flashback 2018. Only MAME, "Sega" (Genesis,SMS,GG) and NES. I don't have a Legends Flashback 2019 so I can't tell if Colecovision will be supported to load games from SD Card out-of-the-box.

The 'good news' is that the update file provided by Bill will have everything you need ?

The audio delay is caused by the emulator + core, not exactly by the CPU clock so I don't think there is a fix for that. By the way, I set the CPU to 1.2GHz instead of 1.3GHz. I think my first test was with 1.3GHz and a voltage higher than the recommended. I changed the voltage to 1.2V and the clock to 1.2GHz, which is a 'safe spot'. @eliofilhoSend me a message if you want to test this change.

I can add the same logic to my Genesis FB HD custom fw. You are correct, the retroplayer and the cores are hardcoded into retromenu so moving the /emulator partition to the SD Card will only change the place where the menu is loaded - this is useful to load different bezels. Using startup.sh also give some flexibility to run different code instead of retromenu, or a custom retromenu. I changed startup.sh in my Legends Flashback to load a retromenu-mod with a new path for the cores (/rom instead of /emulator). This enabled to load different cores (I could load the latest MAME 2003 Plus, or switch between GenesisPlus GX and Picodrive by renaming the Genesis core) only when the SD Card is loaded - and /rom is mounted from the SD instead of internal memory.

Based on the video another user has published, I would say it only has a larger NAND to store the 100 games. The list of games don't have anything that would need a hardware upgrade. I'm wondering if they changed the CPU speed, as the current device runs at 816MHz while the CPU supports up to 1.5GHz (default kernel supports up to 1.1GHz but it is possible to change it to 1.3GHz). I've played around 1 hour with my Legends Flashback after I changed the CPU speed to 1.3GHz and it did not overheat, so I don't think you will need to add a cooler.

Set the baud rate to 1500000 if your adapter supports. If you use the regular baud rates (57600, 115200), you will only see garbage.

Flashback HD 2017 and 2018 (and Legends Flashback) are very different. The 2017 version has an older SOC (RK3036), a larger NAND (2GB/4GB) and runs Android while the 2018 versions runs Linux in a much smaller NAND (128MB). Built-in emulators for Genesis and Master System are not great but the fact it runs Android make it easier to build/reuse a different emulator. I've been able to build a custom RetroArch for this device and it replaces the default emulator really well. Send me a PM if you want to try an overclocked firmware for your Legends Flashback, I was able to overclock the device but I don't have any time to test it properly. You can try it at your own risk.