PS3 4.76.1 REBUG LITE w/ COBRA v7.1

A new CFW release comes from Team REBUG as they officially release 4.76 REBUG LITE that comes equipped with Cobra v7.1 features. This release differs from many rebug releases as it will not contain any DEX features and will not have access to some REBUG features, but with Cobra v7.1 you get many great CEX based features so if you are not looking at all those features but want a reliable CFW then this latest REBUG CFW could be that fit. View all the[break]ss[/break] details provided and also be sure to read all the documentation over at rebug.me

Based on FW:	FW Type:	CFW Type:	Developer:
4.76	CEX	COBRA CFW	REBUG TEAM

THE LATEST REBUG FIRMWARE BUILD
(We are still looking for providers of DEX OFW for future "REX/D-REX" releases)
LITE Cobra 7.1 EDITION INSTALL ON CEX PS3 SYSTEM
​

---

FEATURE

• Cobra 7.1 (Disabled by default (Optional), Toolbox required to Enable)
  • Background Loading plugins (sprx) activated automatically on system boot
    
  • ISO Suppport: PS1/PS2/PS3/PSP/DVD/BluRay (Split ISO support on FAT32 drives)
    
  • Network Support: PS1/PS3/DVD/BluRay/PKGs
    
  • Blu Ray Movie region free functionality
    
  • NTFS HDD Support (prepNTFS, or multiMAN Required to scan contents)
    
  • PS2 ISO Support for BC (via hardware) / non-BC (via software emu) Consoles
    
  • Syscall 11 Cobra lv1 Peek
    
  • PSNPatch stealth plugin support
    
  • PS3MAPI support, allows you to attach process on both CEX/DEX via its own API app.
    
  • Backup Protection Removal, Add full PS3 Backup support on all multiMAN/webMAN,IRIS manager forks and Managunz.
    
  • Allow modification on Syscall 6/7/8/9/10.
    
• In Game Screenshot (Allows taking screenshots in Game)
• Enhanced Remote Play (This unlocks the limitation of working apps/games for remote play, by disabling SFO flag check)
• Cinavia protection fully disabled (Supports optical media/bd iso, AACS must be decrypted)
• QA Token compatibility
• OtherOS++ support enabled (Use Rebug Toolbox to Boot OtherOS with different LV1 patches)
• Package Manager (Replacement for the standard 'Install Package Files' option)

INCLUDED

• Rebug Toolbox 02.02.07 (Install included Rebug Toolbox or higher for full compatibility)
• 1.43.02 MOD REBUG EDITION (Full Webman intergration supports CEX 4.76)

PATCHED

• Appldr:LV2 memory hash check is disabled (Memory protection on LV2 is disabled in higher level)
• LV1: Disable System Integrity Check (Safe to use with mismatched COREOS/SYSCON versions or if PS3 is not QA enabled)
• LV1: Undocumented function 114 (Allow mapping of protected memory)
• LV1: Skip all ACL Checks (Needed to allow booting of OtherOS)
• LV1: Peek and Poke support (Unused LV1 call 182 and 183)
• LV2: Peek and Poke support (LV2 Syscall 6 and 7)
• LV2: Peek and Poke support for LV1 (LV2 Syscall 8 and 9)
• LV2: LV1 CALL System call (LV2 Syscall 10)
• Recovery: Prevent accidental OFW update while on Recovery mode
• VSH: Allow Unsigned act.dat and *.rif files
• VSH: Disable Unlinking/Deleting of act.dat (Improved patches applied)
• VSH: Disable NEW PSP DRM Check (Allowing unsigned PSP pkg contents on 4.75 or higher CFW)
• VSH: Disable Epilepsy Warning for Faster Boot-Up Speed

View rebug.me for full details
​

Download & Source: Rebug.me
​

 

I found it very strange the system refuse CFW.
When I put the HD formatted in the PS3,
it prompts to update, so I put the Rebug, but the PS3 did not agree.
So I put the HABIB 4.76 and the system accepted.
I tried Rebug three times and not work.
My friends reported the same problem.
I did the download direct of website Rebug.

at least you could tell us which model of ps3 you are having an issue with..

 

at least you could tell us which model of ps3 you are having an issue with..

Jonnie,The series is CECH-2511B

 

Jonnie,The series is CECH-2511B

I just pulled 128gb ssd out of my laptop, currently installing rebug 4.78.2 rex over 4.78.2 I have no idea where the issue is coming from...


Sent from my iPhone using Tapatalk

 

did u check the md5 for the rebug update before trying to install? if it's asking for reinstall each time u power on the system, something may be corrupted with the xregistry. try resetting to default settings in the recovery menu.

 

The rebug site never said it can be installed from recovery, only ever said "INSTALL: From XMB install..." . so I just assumed it was like that for everyone.

It isn't related to the HDD swap IMO as I can never install from recovery and I havnt touched my HDD.

If I just go into recovery and choose system update it wont work with rebug, but will work with other FW.

 

The rebug site never said it can be installed from recovery, only ever said "INSTALL: From XMB install..." . so I just assumed it was like that for everyone.

It isn't related to the HDD swap IMO as I can never install from recovery and I havnt touched my HDD.

If I just go into recovery and choose system update it wont work with rebug, but will work with other FW.

I think that the update annotation may be related to the hierarchy of where system updates r searched for. I believe I mentioned this to [MENTION=20]habib[/MENTION] , but the way updates r blocked on the 360 is by changing the $SystemUpdate folder to $$ystemUpdate, so u can still install updates by changing the folder name to the latter without compromising the blocking of updates. habib had said it wouldn't be difficult to implement that but it could cause issues for users unaware of the change since the change I mentioned is from a nand patcher which uses a .ini file to enable/disable patches on-the-fly while needing to be installed separately or directly to the update ur creating.

 

I think that the update annotation may be related to the hierarchy of where system updates r searched for. I believe I mentioned this to [MENTION=20]habib[/MENTION] , but the way updates r blocked on the 360 is by changing the $SystemUpdate folder to $$ystemUpdate, so u can still install updates by changing the folder name to the latter without compromising the blocking of updates. habib had said it wouldn't be difficult to implement that but it could cause issues for users unaware of the change since the change I mentioned is from a nand patcher which uses a .ini file to enable/disable patches on-the-fly while needing to be installed separately or directly to the update ur creating.

Not sure what you mean by that or how it applies to the ps3, what is "update annotation" , and "without compromising the blocking of updates" ? I would just like to be able to hold my power button, enter recovery and install Rebug FW from there if I have a soft brick.

EDIT: I do understand that we can change the folder the PS3 downloads updates to, or we can change the folder the ps3 updates from, I was just doing this today. I just don't see how it will help people who are having this issue like me.

 

Not sure what you mean by that or how it applies to the ps3, what is "update annotation" , and "compromising the blocking of updates" ? I would just like to be able to hold my power button, enter recovery and install Rebug FW from there if I have a soft brick.

oh, I was referring to the annotation about updates being blocked within the recovery menu. I seem to recall such a thing to prevent accidental updates to ofw from within the recovery menu. I was using my knowledge of the 360 to solve a problem with the ps3. there's no recovery menu with the 360 though, so it (updates) may or may not be connected with the ps3 xmb and recovery menu. a different self is involved, I know, but I dunno if there's any issue with searching for updates. I think they're different though since I can update without issues (network enabled; disc in drive) by selecting the update pup specifically. that image from [MENTION=29]Joonie[/MENTION] with rebug re is taken from the version.txt of the update pup while it's ignored in the xmb while u can't directly select the update. I hope that makes sense. that patch may be what's responsible for the issues. I've personally never had an issue. I've only bricked once on 4.78 when I was trying a corrupted, compressed sprx file. and, even then, I was able to fix it from the xmb update section. I've only bricked once with the xmb wave (while drunk mind u :p) . never with anything else. I rarely brick, so I may not have enough experience with installing through the recovery menu.

edit: I'm not sure if we should change the update pup name or the folder. 360s can't sign into live normally. they've changed the folder name since the update is multiple files lumped together. changing the name may be better with the ps3 since we can sign in to psn.

 

oh, I was referring to the annotation about updates being blocked within the recovery menu. I seem to recall such a thing to prevent accidental updates to ofw from within the recovery menu. I was using my knowledge of the 360 to solve a problem with the ps3. there's no recovery menu with the 360 though, so it (updates) may or may not be connected with the ps3 xmb and recovery menu. a different self is involved, I know, but I dunno if there's any issue with searching for updates. I think they're different though since I can update without issues (network enabled; disc in drive) by selecting the update pup specifically. that image from [MENTION=29]Joonie[/MENTION] with rebug re is taken from the version.txt of the update pup while it's ignored in the xmb while u can't directly select the update. I hope that makes sense. that patch may be what's responsible for the issues. I've personally never had an issue. I've only bricked once on 4.78 when I was trying a corrupted, compressed sprx file. and, even then, I was able to fix it from the xmb update section. I've only bricked once with the xmb wave (while drunk mind u :p) . never with anything else. I rarely brick, so I may not have enough experience with installing through the recovery menu.

edit: I'm not sure if we should change the update pup name or the folder. 360s can't sign into live normally. they've changed the folder name since the update is multiple files lumped together. changing the name may be better with the ps3 since we can sign in to psn.

I see. yes I was looking at ways to block system update in my pup without using an app but not completely of course, I want all my mods built into the PUP on install. I have it now so I can download CFW pups using XMBPD to the np-pkg folder, and I have it so system update debug looks in np-pkg folder for the updates..still messing with it though.

 

the ps3 should be able to tolerate both the folder and pup name. I'd suggest the latter since u can access psn. with the 360, there's a number of files in the $SystemUpdate folder, but the only file that updates the system is the file that starts with su (system update?) which I wrote a tutorial here for if not using the gui update apps. :p

 

the ps3 should be able to tolerate both the folder and pup name. I'd suggest the latter since u can access psn. with the 360, there's a number of files in the $SystemUpdate folder, but the only file that updates the system is the file that starts with su (system update?) which I wrote a tutorial here for if not using the gui update apps. :p

Oh yeah its no problem changing filename too, just a hex edit. I just needed it to download to np_pkg folder for other reasons

 

I just pulled 128gb ssd out of my laptop, currently installing rebug 4.78.2 rex over 4.78.2 I have no idea where the issue is coming from...


Sent from my iPhone using Tapatalk

Unfortunately Joonie in my case it did not work.
I do not understand why this denial was happening, but either way, thanks for everything.
after formatting the HD,i returned to Rebug using the XMB,yet I had to install before HABIB

 

Oh yeah its no problem changing filename too, just a hex edit. I just needed it to download to np_pkg folder for other reasons

which file r u hex editing?

 

did u check the md5 for the rebug update before trying to install? if it's asking for reinstall each time u power on the system, something may be corrupted with the xregistry. try resetting to default settings in the recovery menu.

I checked the MD5 yes, before formatting the HD, I was using Rebug, but after formatting has not accepted.
I had to do an update by another CFW to then return to Rebug, but now everything is fine, in fact I was very curious why this was happening, my friends have had the same problem.

 

which file r u hex editing?

software_update_plugin.prx for changing the path that system update debug uses. Im sure I could change the filename there too as "PS3UPDAT.PUP" is mentioned a few times, would just need to do a bit of testing to see which reference is important, could just change em all too. might work.

 

software_update_plugin.prx for changing the path that system update debug uses. Im sure I could change the filename there too as "PS3UPDAT.PUP" is mentioned a few times, would just need to do a bit of testing to see which reference is important, could just change em all too. might work.

u should be able to tell for sure with IDA and debugging the prx. the register should tell u which is the right one. iirc, the offsets r off between a normal hex editor and IDA.

 

The rebug site never said it can be installed from recovery, only ever said "INSTALL: From XMB install..." . so I just assumed it was like that for everyone.

It isn't related to the HDD swap IMO as I can never install from recovery and I havnt touched my HDD.

If I just go into recovery and choose system update it wont work with rebug, but will work with other FW.

I was lucky to have other CFWS available for to update the PS3 or I would have to wait to launch other CFWS for to upgrade, because really with Rebug dont was possible.
I think we should have some problem with my PS3 because Joonie make the update in your PS3 and gave all right,but of
Any way thank you for your help.

 

u should be able to tell for sure with IDA and debugging the prx. the register should tell u which is the right one. iirc, the offsets r off between a normal hex editor and IDA.

Just did a quick test, changed one to "PS2UPDAT.PUP" , and it worked. PUPs with that name are now read from usb , I don't need IDA or debugging. Just pure instinct :p

 

Just did a quick test, changed one to "PS2UPDAT.PUP" , and it worked. PUPs with that name are now read from usb , I don't need IDA or debugging. Just pure instinct :p

what offset is that?

 

0004DEA0 = filename for usb update / probably disc too.

0004DDF0 = path for system debug update