RG351MP stuck after splash screen on first boot

[eduardantonio]

Describe the Issue (If applicable)

Hello, Christian, I hope you are doing fine!

I wanted to report an issue that I'm currently observing in a RG351MP device.
I have been trying to install ArkOS using the download items from the wiki using both links Mega and GDrive (specifically for the RG351MP version), but so far I always get stuck after the splash screen.

I have followed the steps from the wiki:
1, I have used a SanDisk Ultra (from Amazon) and two different PYNY (from BestBuy) SD XC cards (all of them 64gb) but facing the same result.
2. I have prepared the SD cads using USB Image Tool, Win32DiskImager and even ETCHER (sorry, I read the warning in the wiki, but just in case :D)
3. I insert the SD card in the RG351MP (no other SD card is inserted in the TF2/EXT slot)
4. And then turn the device on, but always experiencing the same behavior:

IMG-0222.MOV

After splash screen is dimmed, the device gets stuck in the black screen that you can see from the video.
I was reading this thread and I have tried with the rk3326-rg351mp-linux.zip file that you shared in there, but still seeing the same behavior. (I also read from the same thread that another user reported good results after going back to the previous rk3326-rg351mp-linux file it worked, but unfortunately on my side this was not the case)

Is there any other version that I can try for the device (maybe an older version and then do an update?)
Or if there any way to debug the script files to see at what step the device is getting stuck?

I 'm sorry about the bother, I know this has been asked before, but just wanted to double check in case there has been any news about the RG351MP device.
Please let me know if you need something from my side and I will be able to provide it.

Thanks a lot for your time!

What device are you using?

A RG351MP from Amazon.

What version of ArkOS are you on?

Trying to install ArkOS_RG351MP_v2.0_11052021 from GDrive and Mega.

[christianhaitian]

I'm still working on resolving this issue for some rg351mp units. I was able to acquire a unit that exhibits this issue so now I can replicate it which is helpful.

[eduardantonio]

That sounds good, and thanks a bunch for the heads up!
If you need anything from my side, please don't hesitate to let me know.
Have a nice day! :D

[AriFarugie]

Hello all,
I have the same issue and I hope you will fix it soon :)
I am very thankfull christian for your effort :D

[christianhaitian]

I need to get back to working on this unit. I've been having fun with the rg503 lately.

[reaperofpower]

Following this, Same issue :(

[christianhaitian]

For those that can't boot the RG351MP using ArkOS, please take the rk3326-rg351mp-linux.dtb file that's in the attached zip file and copy it to the BOOT partition of your ArkOS sd card overwriting the existing one in there. Then see if you're able to boot into ArkOS. I was able to boot ArkOS on the unit I have using this updated dtb file. It disables the ability for the RG351MP to even think it's capable of 1.5Ghz as it seemed to cause the unit to not be able to boot.

Please report whether it's successful for you or not.

Thank you,

rk3326-rg351mp-linux.zip

[reaperofpower]

For those that can't boot the RG351MP using ArkOS, please take the rk3326-rg351mp-linux.dtb file that's in the attached zip file and copy it to the BOOT partition of your ArkOS sd card overwriting the existing one in there. Then see if you're able to boot into ArkOS. I was able to boot ArkOS on the unit I have using this updated dtb file. It disables the ability for the RG351MP to even think it's capable of 1.5Ghz as it seemed to cause the unit to not be able to boot.

Please report whether it's successful for you or not.

Thank you,

rk3326-rg351mp-linux.zip

That did it, it now booted and allowed me to complete the setup

[christianhaitian]

Excellent. Thank you for confirming. I've updated the available image for the RG351MP on the wiki with this fix and the latest updates pre included.

[eduardantonio]

Thanks a lot, Christian! I can also confirm that now this is working fine in my unit! Really appreciate the fix 😁👌

[aliankarali]

It disables the ability for the RG351MP to even think it's capable of 1.5Ghz as it seemed to cause the unit to not be able to boot.

@christianhaitian Interesting. I don't know if it is relevant but my 351MP also didn't boot any custom linux firmware except the stock one. I also used this .dtb you provided but it didn't work (not sure if I used it with ArkOS or something else) then just by trial and error I used the overclock version of the .dtb in AmberElec and it worked for both AmberElec and Lakka (so I assume it would work for other linux based firmware)

So just for people who tried this .dtb here and didn't work, they can give the solution above a try, replacing rk3326-rg351mp-linux.dtb with rk3326-rg351mp-linux-oc.dtb that can be found in AmberElec images.

Also stock firmware has this check in the boot.ini

if test ${hwrev} = 'v11'; then
sysboot mmc 1:1 any ${scriptaddr} /extlinux/rk3326-odroidgo2-linux-v11.dtb.conf
elif test ${hwrev} = 'v10-go3'; then
sysboot mmc 1:1 any ${scriptaddr} /extlinux/rk3326-odroidgo3-linux.dtb.conf
else
sysboot mmc 1:1 any ${scriptaddr} /extlinux/rk3326-odroidgo2-linux.dtb.conf
fi

I don't really understand all that is happening there but maybe it is relevant and a similar check can be added in ArkOS so people wouldn't need to search for solutions.

[christianhaitian]

That check is a carry over from the Odroid Go Advance and Super by HardKernel and has nothing to do with these Ambernic units. They just copied them and left them there apparently.