OtherOS++ makes games stop with error 80010505

[butters]

Any news about this problem ?

[xPreatorianx]

Any news about this problem ?

Do you see an update to the thread, news, or a guide posted? No? Well then there's your answer.

When we have a solution you will know about it.

I'm currently in the process of making a complete newbs guide to linux which I'll be posting soon. If the solution doesn't come out by the time I get my guide posted, I will update my guide with the solution when it becomes available. Till then sit tight, relax, and enjoy yourself. If you can't wait, install Kamew 3.55 and just wait till the release comes out.

But please don't spam threads asking if there is any news. You will know when something is released because either gitbrew.org or the Rebug team will inform the scene and release something. Till then.......... you get it........

[OoZic]

I haven't been into it that much. I don't game on GameOS that often and I have a second PS3. Spending 6 hours to compare the 2 xregistry's didn't give me a lead or clue about the problem.

I find it strange not more users are complaining about this problem. Maybe the "Rebug OtherOS" FW is more compatible or has this error fixed? Don't know. Other things on my mind now.

The only difference with my correct working install before is the extra vflash6 usage. Maybe the PS3 wants to read from or write to this partition and it can't ?
If I have time I will look with dev_blind into flash to see if there is something causing this error.

[xPreatorianx]

I haven't been into it that much. I don't game on GameOS that often and I have a second PS3. Spending 6 hours to compare the 2 xregistry's didn't give me a lead or clue about the problem.

I find it strange not more users are complaining about this problem. Maybe the "Rebug OtherOS" FW is more compatible or has this error fixed? Don't know. Other things on my mind now.

The only difference with my correct working install before is the extra vflash6 usage. Maybe the PS3 wants to read from or write to this partition and it can't ?
If I have time I will look with dev_blind into flash to see if there is something causing this error.

No both have the exact same problems. People have basically switched back over to non linux firmware or just don't use games so they aren't making a fuss. But I've seen a decent number of people complain about rebug as well. Which is why there's a sticky in the rebug forum.

Also I have no idea on the extra vflash 6 usage. How did you even do that? Anyways I look forward to your findings.

[OoZic]

Old method (from my translated german guide with working trophies):

1. delete_vflash5
2. delete_vflash7
3. create_vflash5
4. resize_vflash
5. create_vflash7

Partition vflashg install.

New OtherOS method uses vflash 5,6 and 7. So the vflash6 partition is also altered now. It is now vflashh partition.

Fact is this kind of error (same problem, only F at the end and not 5) also showed with the 29 February thing. Sony never repaired the error but just waited 1 day for a correct date the PS3 would understand. The PS3 got impossible data it couldn't handle with exactly the same error screens and trophie problems.

So to my opinion it is an connection error or read/write error
Note: the 29 February error occurred with a full working network connection so the connection error isn't the real problem but not 100% sure about that.

[Pereb27]

Old method (from my translated german guide with working trophies):

1. delete_vflash5
2. delete_vflash7
3. create_vflash5
4. resize_vflash
5. create_vflash7

Partition vflashg install.

New OtherOS method uses vflash 5,6 and 7. So the vflash6 partition is also altered now. It is now vflashh partition.

Fact is this kind of error (same problem, only F at the end and not 5) also showed with the 29 February thing. Sony never repaired the error but just waited 1 day for a correct date the PS3 would understand. The PS3 got impossible data it couldn't handle with exactly the same error screens and trophie problems.

So to my opinion it is an connection error or read/write error
Note: the 29 February error occurred with a full working network connection so the connection error isn't the real problem but not 100% sure about that.

Hello,

I have that trophy bug aswell, and I'm 100% sure it has nothing to do with the vflash partition or anything like that, to me it definitely looks like a bug in one of the hypervisor patches.
I don't know if it's related but i get an error message when trying to update the time/date via Internet (if working it should prompt to update the system, but it just gives an error message instead) that I don't get with a firmware that doesn't have OtherOS++ enabled.

[Mack702]

Wait for it to be stable until then enjoy the bugs

[Pereb27]

Wait for it to be stable until then enjoy the bugs

Right now I'm running tests with PS3MFW builder to see which one of the patches in LV1 Hypervisor patches section causes the problem.
Maybe disabling just this one will get everything working fine until it's fixed.

I will update if/when i find something

EDIT : Found it. The patch that causes this problem is "Allow access to all SS services (needed for ps3dm-utils)".
Disabling this patch in PS3MFW Builder while creating your firmware will make trophies work again.
I'm a bit new to this so I don't know how ps3dm-utils works or how useful it is, but since it's apparently needed for accessing the BD drive among other things, it might be a problem for some people. But at least you can make a working OtherOS++ enabled firmware with working trophies by disabling that patch, until a fix comes .

[OoZic]

just to let you all know, I reformatted my HD today using my laptop (petitboot was unable to remove the region 7, error in line 39 script) and installed the latest OtherOS++ CFW (CFW355-OTHEROS++-22GB) and tested 1 game (COD MW2) which gave this error and now it runs without problem !!!

I installed the 22Gb CFW, losing 185Gb with the original half HD CFW was a little to much for me.

Now I will continu with installing petitboot and linux etc. and see if MW2 still runs before I will test other games.

Looks like they fixed it great job again !!

[xPreatorianx]

just to let you all know, I reformatted my HD today using my laptop (petitboot was unable to remove the region 7, error in line 39 script) and installed the latest OtherOS++ CFW (CFW355-OTHEROS++-22GB) and tested 1 game (COD MW2) which gave this error and now it runs without problem !!!

I installed the 22Gb CFW, losing 185Gb with the original half HD CFW was a little to much for me.

Now I will continu with installing petitboot and linux etc. and see if MW2 still runs before I will test other games.

Looks like they fixed it great job again !!

Sweet! Cheers m8 now I can add that in the guide when I work on it .