Butcher wrote:Wird not show 6.61 PRO-C2 ,i have perm on my all PSP 100x-200x and show i have 6.60 PRO-C2 and on 300x PSP i have LCFW 6.60 PRO-C2 (And show 6.60 PRO -C2).
Wird glich u have but if work all CFW ignor that not show correct system info witch CFW maybe some LCFW glich relaunching FW
Hey Butcher,
Thank you for the reply bro
I appreciate your help/insight into this very much
Yeah, I assumed that the updated CFW would have fixed that issue for me, but I guess it didn't.
Hhmm I'm guessing it could also be a small glitch too, as I am confident that my PSP is not the culprit in this situation al all. (It works as it should, it's just the UMD drive failed a few weeks back
hence the reason to revert to using CFW.)
KIND NOTE: Please Bear in mind though, that I am not comfortable at the moment to permanently flash my PSP, I prefer the common way of safely rebooting into a CFW, which re-assures me that I can have a fully maintainable PSP system, without the hassle of it running into soft/hardcore errors. (Every user has a sustainable preference in life hehe and I'm one of them
.)
Butcher, I will be taking a video of my PSP running the CFW PRO-C(2) {661_PRO-C2_14-02-2015.zip}, indicating that I am not messing with anyone's head here at all
.
I'll upload it within 24 hours, which will show DarkSpeed, 10 Emulators, PSX, PSP iso's, and the System FW/CFW version all running smoothly, just not indicating the PRO(2) in the System OS details section. I'll also transfer a few plugins to show they run fine too.
But I'm pretty sure this could be a problem possibly not identified in the FastRecovery method of the CFW, as a lot of people (probably 90%) tend to permanently flash their PSP rather than use the FastReceovery method that I like best.
I know that using FastRecovery is only a temp version of the CFW, it deletes the files straight away either in the event that the console is turned off/rebooted (correct me if I'm wrong), but it should still indicate that I'm using PRO-C2 <-- in this case the 2 is still missing upon every boot regardless.
To sum it up, there are currently 2 small problems found in the CFW build 661_PRO-C2_14-02-2015.zip, that I have stumbled across, or may not have been identified either way here they are:
1) When using FastRecovery to boot into the CFW, consistently (100% of the time) when checking under the
System Settings >> System Information >> System Software >> Version: 6.61 PRO-C(2), the #2 is never showing up in there, its missing hence it shows up as 6.61 PRO-C even though its on build 661_PRO-C2_14-02-2015.zip.
2)
(Now this method happens 2 out of 10 times not so often in other words) Again when using FastRecovery to boot into the CFW, then checking the same procedure as above, the 6.61 PRO-C(2) firmware details are now initially missing from the System Software section altogether, it will instead revert back to showing
Version 6.61 (its OFW). However, there is a twist to this, when this problem occurs, the plugins/.iso's/themes/VSH menu etc. all are functioniong as they should, it's weird right?. However the PSX games will not load under this glitch, instead you receive the usual {F########} error with the licensing load up issue.
In this case, all I do is turn the PSP off (restart it), then boot into FastRecovery, the CFW loads up and the system is back to normal in PRO mode, I check the System Software section and it indicates CFW Version 6.61 PRO-C running everything runs smoothly including the PSX games. (Please note the 2 is still not showing up).
If assumption is taken into account here about using/applying DarkSpeed (which could be the problem then I can clearly state this has got nothing to do with it
), please bear in mind that I used/applied DarkSpeed on the CFW build 661_PRO-C2_14-02-2015.zip. The problems encountered above arose since the previous CFW build 6.61 PRO-C2_22-01-2015.zip that I was running right into build 661_PRO-C2_14-02-2015.zip.
Those are the only issues affecting the build that I am currently using. To me its not much of a fuss, so long as everything is running fine in the end. However if someone else ends up having the same problems, then to them it can be a bit of a constant head banging scenario, by where they need it fixed/resolved (kind of resembling a guilty conscience running inside you and you need it cleansed ASAP
).
In the end I am grateful that the CFW works, its saved me a lot time in having to re-assemble a new UMD drive in which I just don't have the time to do nowadays.
I'll upload the video within 24 hours sowing the above.
Thanks
TJ