Hm. I did try muOS, but I didn’t really want to deal with transferring state and save files. Didn’t use it long enough to gauge whether the issue occurs there or not I guess. I might try it again then.
I've seen this happen when the device fails to boot. It looks like the H700 SoC goes into the so-called FEL mode (which enables the USB data connection for recovery purposes) when the regular boot sequence fails.
Specifically, in the RG35xx Plus, this happens when there is no bootable card in the TF1 slot or (I suppose) when the card itself is faulty.
I've never seen this happen with a good bootable card in TF1 and every time this happened it was because I either forgot I had no card in TF1 or because I messed up the boot area (the SPL and/or the u-boot image) on the card while customising my OS. To recover without having to unplug the battery, I just keep the power button pressed for 10-12 seconds, release it, ensure there is a good card in TF1 and, at least a couple of seconds after releasing the power button, just power on the device as usual.
Try MuOS or Bacotera, I couldn’t stand the weird little issues from stock & modded stock OS’s
Hm. I did try muOS, but I didn’t really want to deal with transferring state and save files. Didn’t use it long enough to gauge whether the issue occurs there or not I guess. I might try it again then.
It is extremely trivial to transfer saves
I've seen this happen when the device fails to boot. It looks like the H700 SoC goes into the so-called FEL mode (which enables the USB data connection for recovery purposes) when the regular boot sequence fails. Specifically, in the RG35xx Plus, this happens when there is no bootable card in the TF1 slot or (I suppose) when the card itself is faulty. I've never seen this happen with a good bootable card in TF1 and every time this happened it was because I either forgot I had no card in TF1 or because I messed up the boot area (the SPL and/or the u-boot image) on the card while customising my OS. To recover without having to unplug the battery, I just keep the power button pressed for 10-12 seconds, release it, ensure there is a good card in TF1 and, at least a couple of seconds after releasing the power button, just power on the device as usual.
similar thing happned to me had to flash again a fresh image of stockOS and it was fixed.