Recent content by Bobby_Downgrades

No, it only supports up to 4.81 cfw, I will update soon, thank you

@MrMario2011 , unfortunately I have not found a way to limit downloads from there to be fw ver specific. I think I will need to remove it from the whats new and put the download option back to the packages section. It's such a shame that end users can no longer read and pay attention, I have so...

Hi guys, sorry for the late reply @DeViL303 . The app that @Hexxy Chan is talking about is the firmware updater, WHICH CLEARLY SAYS IN IT'S DESCRIPTION UNDERNEATH THE DOWNLOAD OPTION that it is to be used with Overflow 4.81 cex2dex or Overflow 4.81 dex2cex versions of the said cfw. Just for...

Using mods or no ?

If you are using windows 10 you need to put the files into windows folder instead of windows/system32

@DeViL303, I think Roxanne is correct, an old cfw pre 1.50 will be headache to make. That being said anything after that (up to 3.55) will be pretty easy, remember most patches will not need to be applied so could be quite clean cfw. Send me a list of which versions you wanted and I will try to...

To be honest I am not sure how you will do that, it is not something I have done before.

The idps and psid are both given to a console by sony at factory, part of the 3 ids (idps, psid and mac). Idps is used when going onto psn on your ticket as an identifier. Psid is used for game save data and other non online activity (and most likely store bought games license). Mac is same as...

You were quite lucky, it must have been the bd ribbon being slanted due to being taped in. Glad you got it sorted.

If you have bought a knock off "fake" e3 some of them do not allow a second update, if is already flashed with single console version then is stuck, if is already flashed with multiple console update then you are ok. So keep in mind that if you are trying to update e3 with mupltiple console...

Joonie is correct, the ps3 must have been on ferrox nobd version due to previous owner knowing blueray drive is broken/not plugged in correctly. I would bet that if you open ps3 the ribbon connector on the motherboard is broken (seems quite common in second hand cfw models these days)...

Thanks for the info, I will leave them out of cfw as static. Unless cfw with cobra 8.01 will need this hard coded sc 15 into lv2 in order to use it's full capabilities ?

@habib Firstly good job on the new cobra 8 payload, very good job removing stage 1. I noticed that you use system call 10 and 15 (put back into lv2), can you explain what these system calls are used for please and should I add these into cfw ?

I'm not sure system_plugin is a thing, I think it may be what ccapi's maker renames a file to take another files place, so I think when you install ccapi it renames sys_audio to sys_plugin and takes the place of sys_audio, I think. The way I use sys_init_osd means if you say install the mamba...

When I do testing like what your doing I normally disable qa flag and use custom pups with 9.99 syscons so they install over eachother but there's no way to get out of the 9.99 loop so only the test pups install. Good idea you have, I found that having only the xai plugin slot was a bit tricky...