PS3 4.81 STARBUCKS COBRA 7.40 CFW by Habib

The PlayStation 3 Custom Firmware developer who has a focus on bringing new features to CFW is here with a new release for 4.81. Developer @habib has released 4.81 STARBUCKS COBRA 7.40 CFW , with an updated COBRA payload that has some interesting advancements such as a new syscall (15) added to execute any LV2 Internal function, as habib explains this will allow devs to execute their own payload at a specific address. Other details and feature about Cobra 7.40 update can be seen in the "Cobra 7.40" tab. Other features such as Cinavia protection removed so you can digitalize your personal collection without intrusion this handles all content from HDD, BDMV & BDVD, Habib cover's the new additions in the details provided..
​

-STLcardsWS​

​

Starbucks 4.81 About COBRA v7.40

• 
  
  
  4.81 STARBUCKS [w/ COBRA v7.40] CFW
  by @habib​
  
  CHANGELOG:
  
  1. MADE OUT OF 4.81 OFW
  2. HAVE INSTALL PACKAGE FILES AND APP_HOME
  3. HAVE reActPSN COMPATIBILITY
  4. PATCHED LV0 TO DISABLE ECDSA CHECK
  5. PATCHED LV2 TO ADD PEEK/POKE SUPPORT
  6. PATCHED LV1 TO DISABLE LV2 PROTECTION
  7. PATCHED LV1 TO ADD PEEK/ POKE SUPPORT
  8. IT CAN RUN GAMES SIGNED WITH KEYS UP TO 4.81
  9. CAN BE UPDATED OVER ANY CFW.
  10. CAN BE UPDATED OVER 3.55 OFW
  11. NOT ADDED NO BT/BD PATCHES
  12. RSOD BYPASS
  13. REACTPSN OFFLINE PATCH ADDED
  14. BETTER SYSTEM STABILITY
  15. REMOVED CINAVIA DRM FOR HDD CONTENT
  16. REMOVED CINAVIA FOR BDMV
  17. REMOVED CINAVIA FOR BDVD
  18. QA FLAG ENABLED BY DEFAULT IF PS3 WAS QA ON 3.55
  19. COBRA 7.40
  20. SYSTEM ACTS AS A COMPLETELY NORMAL CFW WHEN COBRA DISABLED
  21. FSELF COMPATIBILITY ADDED
  22. PATCHED DOWNLOAD PLUGIN FOR DEX PKGS(FOR E.G XMBPD)
  23. ENCHANCED REMOTE PLAY
  24. REMOTE PLAY SFO FLAG OBSOLETE
  25. NO EPILEPSY WARNING
  26. SYSCALL 15 ADDED TO EXECUTE ANY LV2 INTERNAL FUNCTION​
  UPDATE (v1.01) - day zero 1.01 update released.
  
  • fixed ps2 issue and whats new psn
  
  wanna buy me cookie?
  
  • btc:1GuLwCtL15gudk4MszwJLLUbLJ2QBeAt8f
• 
  COBRA 7.40 Changes:
  
  1. stage0_base updated for faster boot timings
  2. no more debug texts overwritten for devs
  3. syscall 15 added
  4. updates hashes to cobra internally​
  
  UPDATE HASH:
  
  • Make a text file named hash_recheck.txt
  • inside the file put new hashes in format filename:hash per line(e.g vsh.self:a0000101002e6534)
  • paste this file at /dev_hdd0/hash_recheck.txt
  • reboot ps3 and then reboot again
  SYSCALL 15:
  
  • allows calling of any lv2 internal function like internal memcpy to dump lv2. e.g(memcpy(dst, source, size, symbol)
  • this also allows developers to execute their own payload at an address e.g you paste payload at 0x3d98 and then execute through sc15
  • example has been attached with new include file named "sc10_15.h"
  OTHER CHANGES COMPARED:
  
  • with ALL the current cobra cfw released they have a stage0 bug which overwrites another function stack, which could cause instability
  • one i checked didnt had hdd cinavia patched, this has it done

Download: 4.81 STARBUCKS COBRA v7.40
MD5：15660d36c3aa5197c97c87643acdca3c
​

 

I was on rebug before. Same hdmi cable.

It blinks very rare. Not big issue.

 

I was on rebug before. Same hdmi cable.

It blinks very rare. Not big issue.

But this why it blinks
If we cant reproduce what you have, than you might even have this on next rebug which is due soon
If you want to contribute:
Try different cable or different output
Tell us how and when it happens and possible tests you can conduct which you think are related

 

he is trying telling you to copy it (the pup not the game... im sure it is a typo and ill correct it) to the hdd via ftp. its actually easier imo to use ftp than to format and copy a file to a usb stick.

there are a few guides that you can find that will show you exactly how to do this. its pretty easy and pretty much straight forward.

yes, I have a guide on how to do this.

@ext10 , have a look at pinky's ps3 tutorials. the guide is in there. it's under how to use update debug. update debug is under debug settings underneath network settings. when u click on debug settings, a new list of settings will appear. I think update debug is around the middle of the list iirc. not sure if I put it in my tutorials but u can actually have one folder with all updates instead of having 01, 02, etc. it works either way. good luck. we're here if u need further help with that.

He has replied actually.
He just told you that the pup gets copied to /dev_hdd1 before the firmware update takes place.
He suggested correctly to start by using another USB key formatted in fat32 to perform the update.
If you use a hdd instead of a key you may experience problems with firmware updates.
Your problem may have another cause (like internal hdd, hardware or file system ssue) but this is the most likely & the first thing to check.

Btw I assume you are in CEX mode before attempting to update to habib cfw... Because if you are in DEX mode it won't work of course...

I followed the update debug tutorial putting this .pup in hdd0/updater/01 folder, but when i go to update with the usb method option in xmb it won't displayed nothing to update.

 

But this why it blinks
If we cant reproduce what you have, than you might even have this on next rebug which is due soon
If you want to contribute:
Try different cable or different output
Tell us how and when it happens and possible tests you can conduct which you think are related

I understand

But it's not in 3d. It's on disc loading screen or in garage in GT 6. Very rare. Monitor has only hdmi

 

I followed the update debug tutorial putting this .pup in hdd0/updater/01 folder, but when i go to update with the usb method option in xmb it won't displayed nothing to update.

• You need to have your console QA flagged
• Then go to network settings (dont enter it) and input the button combo that enables the Debug settings (Hold L2 + L1 + R1 + R2 + L3 + D-pad Down)
• Then go into the debug settings and enable System Update Debug.
• Then you can update fw - go to "Update via System Storage", not "Storage Media"

 

I followed the update debug tutorial putting this .pup in hdd0/updater/01 folder, but when i go to update with the usb method option in xmb it won't displayed nothing to update.

Are you sure you read the complete tutorial properly?
Those debug updates will only appear after taking some steps to enable the feature & it is unrelated to the system update via standard USB device...

 

I understand

But it's not in 3d. It's on disc loading screen or in garage in GT 6. Very rare. Monitor has only hdmi

That doesn't help us to help you very much...
You can't find a TV to test your console on?
So far only you reported such an issue so we are curious & as habib mentioned we would all like to be able to prevent any bug to end up in the coming Rebug release...

 

I followed the update debug tutorial putting this .pup in hdd0/updater/01 folder, but when i go to update with the usb method option in xmb it won't displayed nothing to update.

it should say update via system storage. there will be a star next to it denoting a debug option.

 

it should say update via system storage. there will be a star next to it denoting a debug option.

FYI: Your tutorial does not have the step for entering the button combo to enable debug settings, I think that is why he had an issue.

 

FYI: Your tutorial does not have the step for entering the button combo to enable debug settings, I think that is why he had an issue.

thanks for noticing that. I just added it.

 

• You need to have your console QA flagged
• Then go to network settings (dont enter it) and input the button combo that enables the Debug settings (Hold L2 + L1 + R1 + R2 + L3 + D-pad Down)
• Then go into the debug settings and enable System Update Debug.
• Then you can update fw - go to "Update via System Storage", not "Storage Media"

Are you sure you read the complete tutorial properly?
Those debug updates will only appear after taking some steps to enable the feature & it is unrelated to the system update via standard USB device...

it should say update via system storage. there will be a star next to it denoting a debug option.

Yes, it's weird... i think i have my console qa flagged, i qa flagged it in 3.55 longtime ago... I see debug settings in xmb and system update debug on. I don't know why it is not showing update via System Storage, i only get internet update and storage media options.

 

not sure. I've never heard of this happening. ur on rebug, correct? check if qa is selected as ur mode in rebug toolbox. qa will be different from dex since dex has control over both qa and debug menu 2 (dex-only) options.

 

not sure. I've never heard of this happening. ur on rebug, correct? check if qa is selected as ur mode in rebug toolbox. qa will be different from dex since dex has control over both qa and debug menu 2 (dex-only) options.

Yes, i'm on rebug, effectively i have qa mode in rebug toolbox, not dex.

 

Yes, i'm on rebug, effectively i have qa mode in rebug toolbox, not dex.

no idea what's going on with ur system. boogs may know. I think he's asleep atm, so tomorrow, u might get a response from @bguerville (boogs).

 

Let's recap then.
What you did in the past cannot be relied upon so let's check what your current settings are:

1. You are using Rebug 4.80.1 in CEX mode.
2. In the Rebug Toolbox 02.02.10 Utilities Column, the first entry named Toggle QA shows enabled.
3. Back in the Selector column, you chose
Rebug System Mode
Debug XMB operation mode
CEX QA menu type.
4. You created at least one numbered folder named 01, the resulting path would be:
/dev_hdd0/updater/01/
then you copied a PUP file in it.
5. In XMB in the Settings column, you went into the Debug menu to toggle System Update Debug on.
6. In the Settings column of the XMB, System Update should now have 2 more entries marked with a star character: Update via system storage & delete update data on system storage.

 

Let's recap then.
What you did in the past cannot be relied upon so let's check what your current settings are:

1. You are using Rebug 4.80.1 in CEX mode.
2. In the Rebug Toolbox 02.02.10 Utilities Column, the first entry named Toggle QA shows enabled.
3. Back in the Selector column, you chose
Rebug System Mode
Debug XMB operation mode
CEX QA menu type.
4. You created at least one numbered folder named 01, the resulting path would be:
/dev_hdd0/updater/01/
then you copied a PUP file in it.
5. In XMB in the Settings column, you went into the Debug menu to toggle System Update Debug on.
6. In the Settings column of the XMB, System Update should now have 2 more entries marked with a star character: Update via system storage & delete update data on system storage.

Yes, thanks for the answer, i think my settings are correct:
1. Yes
2. Yes
3. Yes, nevertheless, in here i always changed from rebug mode to normal mode before an cfw update, i don't remember where i read it and if it true but it is related to something called rsod of red screen that may occur. Still i put that settings you mentioned.
4. Yes.
5. Yes.
6. I only have the regular 2 entries: internet update and storage media.

Maybe it is my file system that it's corrupted i don't know... It's strange...

 

6. I only have the regular 2 entries: internet update and storage media.
Maybe it is my file system that it's corrupted i don't know... It's strange...

then you either do not have qa enabled, or you have not went into debug settings and turned on update debug.

lets go all the way back to the beginning and redo a few things. go ahead into rebug toolbox and turn off qa flag. then reboot.

now go back into rebug toolbox and enable qa flag and reboot, then make sure update debug is on in debug settings on xmb.

now go to system update at top of setting column and see if the two new options for updating are available.

this may sound out of the ordinary, but i once had a system that was qa flagged on 3.55 but after updating to one of the 4.xx CFW along time ago (i think it was a cfw that had qa flagged enabled by default), it did infact disable qa somehow. not sure why or how but doing what i mentioned above solved the issue for me.

 

Yes, thanks for the answer, i think my settings are correct:
1. Yes
2. Yes
3. Yes, nevertheless, in here i always changed from rebug mode to normal mode before an cfw update, i don't remember where i read it and if it true but it is related to something called rsod of red screen that may occur. Still i put that settings you mentioned.
4. Yes.
5. Yes.
6. I only have the regular 2 entries: internet update and storage media.

Maybe it is my file system that it's corrupted i don't know... It's strange...

To post those answers did you actually do all the steps mentioned in post #76 or are you just answering what you believe to be the case?
I was asking you to do the former...
It's not possible that all the conditions are ok but the feature does not work.
You have to be making a mistake somewhere...

 

I would also like to mention internet update will be greyed out and unselectable

 

Anyone here can please tell me if multiman 4.80 work with this release?