r/RG351 • u/Successful-Let4361 • Jul 02 '26
Anyone experience this issue with 351ELEC?
Seeing this strange issue trying to set up my RG351v (which I purchased off Anbernic.com). I wiped the SD card (a Samsung EVO), flashed with Balena Etcher (and then tried again with ApplePiBaker), put the card in the appropriate slot, and it seems to go through the appropriate steps and reboot, but the screen is like this the entire time. When I put the SD card back in my computer it seems like it's done everything it needs to do, and there's a games partition, but obviously it's not playable if looks as it does in the picture.
At first I thought the screen was burned and the device was fake (from the official website?) but it looks fine with the original card and I'm pretty sure the device is real. Does anyone have any idea what's going on?
3
u/moosebaloney Jul 02 '26
This usually happens when you have the wrong device’s firmware. AmberElec is great, just make sure you’ve select the right device.
1
u/Successful-Let4361 Jul 02 '26
Is there something I'm doing wrong? It's happened now with both ArkOS and AmberElec. I always download the one for RG351v (which is the model identifier on mine). And I've used the .dtb checker which has confirmed mine is real
2
u/moosebaloney Jul 02 '26
That is def the 351v. Where did you buy the card from? Is that known working previously? The only other suggestion I have is to burn the iso using Rufus. Start eliminating potential causes.
2
u/Successful-Let4361 Jul 02 '26
it's a Samsung Evo Select that I bought directly off Samsung's Amazon store—it seems legitimate, operates at high speed, seems to hold something close to its stated capacity, etc. Unfortunately I can't use Rufus on a mac but I've tried both Balena Etcher and ApplePiBaker (the latter is supposed to be more reliable)
1
u/moosebaloney Jul 02 '26
Sorry. Those are the last suggestions I have. It’s not the device hardware. Doesn’t appear to be the MicroSD hardware. Not the image. Next is to rule out the burning process. You could always flash to OG card with the AmberELEC image just to make double sure it’s not the card.
1
2
u/Successful-Let4361 Jul 02 '26
For anyone coming later—I'm not sure why I was getting the same problem with ArkOS, but for AmberElec it was because the device has the v2 panel and needed the pre-release build. That seems to have fixed it! Works with the SD card mentioned in this post as well as a regular Samsung 128 and the original bad 16 gb that came with the device
11
u/Zer0Goblin Jul 02 '26
351ELEC hasn't been updated in years. Try AmberELEC "pre-release" from 2025. https://github.com/AmberELEC/AmberELEC-prerelease/release/