I think you should not release an exploit for 4.83 OFW. Why did people update to 4.83 in the first place? It was obvious that Sony would be fixing ps3xploit with that update. Now these people say that we updated to 4.83 "accidentally". It asks for confirmation a lot of times. I know that it is not an accident but something done purposely. Now people want to know when an exploit for 4.83 will come. For them it's just a joke but you have to put in a lot of hard work and efforts to make an exploit. If you release an exploit, you are just asking them not to be careful!

Some people used a claimed dualboot CFW and ended in OFW. You would say the same about them?
I had this ps3 in cfw since 3.55 is an irony that "probably" the last firmware of the ps3 is the one i ended used, just because the developer didn't did an install test. (I'm just guessing here but that's what it looks like)
Of course is my fault as well because no one forced me to install that CFW, but now I'm stuck in these OFW CFW attempt.
So this is a different case, i didn't update by accident, i knew exactly what i was doing the problem was the CFW i used didn't do the thing that claims to do.
 
Theres a good thing going on though. I hope all the modders, who DESTROY OTHERS PEOPLE'S GAMES BY MODDING THEMSELVES TO A WIN, update to 4.83 "accidentally" to loose their CFW abilities....

Gesendet von meinem BLA-L29 mit Tapatalk
 
Theres a good thing going on though. I hope all the modders, who DESTROY OTHERS PEOPLE'S GAMES BY MODDING THEMSELVES TO A WIN, update to 4.83 "accidentally" to loose their CFW abilities....
Those who blatantly abuse SEN and use mods in online multiplayer to gain an unfair advantage are more likely to be reported, and therefore more likely to get banned.
 
Well, as it seems peoples have some issues to make a working 4.83 Dualboot firmware, I made one based on @haxxxen PS3MFW mod task (https://github.com/haxxxen/ps3mfw-builder-0.2.1-mod/blob/master/tasks/23_patch_db.tcl).

So "littlebalup's" Dualboot 4.83: http://www.mediafire.com/file/nohp1m422o35ld2/DB_4.83_littlebalup.PS3UPDAT.PUP
MD5 : 4CF60DAE7DA5071A5AD21803C9376E97

Patched isoldr and spu_pkg_rvk_verifier to disable ecdsa protections and allows to install CFW4.83+ over it (tested!).
Core OS patched files (lv0 and spu_pkg_rvk_verifier.self) have exact same size than the original ones.
Code:
isoldr.elf
FileSize: 0x1453b bytes
Search Pattern:  3FE1128518014206
Mask Pattern:    FFFF00FFFFFFFFFF
Replace Pattern: 40800003
Replace Offset:  0x08
----PATCHED AT:000036C0
----PATCHED AT:00003EA8
Code:
spu_pkg_rvk_verifier.elf
FileSize: 0xf7d7 bytes
Search Pattern:  2100030304002A03
Mask Pattern:    FFFFFFFFFFFFFFFF
Replace Pattern: 40800003
Replace Offset:  0x08
----PATCHED AT:00003154

Tested on both NOR (CECH-2004B) and NAND (CECHC04).
Hello again :)
It appears i am not the only one struggling to make 4.83 dualboot FW,
And i taught i am the only one facing this problem.
The problem i faced is that for some reason the software i use fails to apply the patches to isoldr
 
Hi just wanna know if theres any rebug news?
No.
I don't get it, why it's so important to update CFW (from user view point)? There isn't any game that require new firmware anymore, is it just for PSN? We already have Ferrox, ´course I love rebug too but if psn is so necessary ferrox will do the work
 
No.
I don't get it, why it's so important to update CFW (from user view point)? There isn't any game that require new firmware anymore, is it just for PSN? We already have Ferrox, ´course I love rebug too but if psn is so necessary ferrox will do the work
Does it hurt asking?
Hi just wanna know if theres any rebug news?
You can always check in rebug.me
 
@bigbossu You're right. Users going from a CFW like Ferrox Cobra 4.82 (like I was for the best part of a year) to Ferrox Cobra 4.83 aren't going to notice any appreciable difference other than accessing PSN services, which always poses a ban risk anyway. I'm currently on Rebug REX 4.82.2 but I have the PUP files for 4.82 and 4.83 Ferrox Cobra stored on my USB external drive in case I ever decide to go back to Ferrox. That said, I'm happy with Rebug for the time being. :)
 
Louay u nailed it but you might wana hide you psid
Hahhahaha there is no PSID nor IDPS (CID) shown in video there is just the ip adress which given by router and mac adress of the wireless card those info will not harm the ps3 so there is no point in hiding that screen step
 
Hahhahaha there is no PSID nor IDPS (CID) shown in video there is just the ip adress which given by router and mac adress of the wireless card those info will not harm the ps3 so there is no point in hiding that screen step
Sony is known to ban consoles by mac addreses too,
This is not a good idea.
 
Back
Top