Open Jacosci opened 2 years ago
Thank you for your feedback. I've not tested this scenario, but I guess it is due the payload is being removed from the internal HDD during the RFS.
You can try loading the payload file (mamba_488C.bin) from dev_flash instead of loading it from the internal HDD.
If you get any issue (e.g. black screen on startup), entering to Recovery Menu should delete the boot_plugins_nocobra.txt and the system should boot fine again.
Thanks for the quick response! Just a couple more questions. Do I need to put it in a specific folder or anywhere within dev_flash is fine as long as I edit the txt file accordingly? If it's the latter, does that mean the Mamba payload can be placed anywhere on the internal HDD with boot_kernel_nocobra.txt pointing to it?
Yes, the payload file can be loaded from any path.
Occurred consistently on Rebug 4.84.2 REX and Evilnat 4.88.2. Both with Cobra disabled obviously. I tested back and forth several times between those two CFWs (with a few clean installs, no less) and I always could reproduced this issue. It didn't matter whether Restore File System being triggered automatically or manually. The blackscreen freeze always occurred after RFS completed its process and reboots the console.
I already pulled my HDD and plugged it on my PC then checked it with Harddisk Sentinel and HDD Regenerator and found no problems. This issue doesn't occur when I'm using Cobra. As an additional info, on Evilnat 4.88.2 the blackscreen freeze also occurs when I use the reboot LV2 from the CFW menu.
I hope you can help me because Mamba performs better in my console. Using Cobra makes Diablo 3 stuttering like crazy but with Mamba the stutters are very minimal and the temps are lower as well.