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
​

 

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

multiman 4.80 is reported to mount games on 4.81 CFWs however it has not been updated by deank yet so it would not be surprising if at least some of the numerous features didn't work ok....
Until multiman gets updated, you have Irisman 4.81 & webMAN-MOD 1.45.04 offering full support anyway.
Also it might be a good time to try Managunz 1.26 which is the most interesting backup manager currently under development along webMAN-MOD.

 

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...

maybe it's the update pup? I'm not sure what would happen if u enabled update debug yet had updates in the updater folder. the selection may not appear. did u ftp the update or use ur flash drive? also, did u check the md5 before transfer?

 

maybe it's the update pup? I'm not sure what would happen if u enabled update debug yet had updates in the updater folder. the selection may not appear. did u ftp the update or use ur flash drive? also, did u check the md5 before transfer?

If there was no valid pup, the feature would be greyed out & not selectable but it would still be displayed...
Every single step & requirement has to be double checked, one after the other, before anything else...

 

If there was no valid pup, the feature would be greyed out & not selectable but it would still be displayed...
Every single step & requirement has to be double checked, one after the other, before anything else...

I see. I'm at a loss as to y he's having this problem especially if everything has been double or triple checked.

 

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.

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...

No, i did the steps you mentioned, but like noobzilla mentioned somehow qa flagged got disabled.

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.

At the end it was like you said: i turned off qa flag, reboot, enabled it again and reboot again making sure system update debug was on and now i finally saw the two star system update options. And finally could install the cfw. Thank you all for your help...

 

No, i did the steps you mentioned, but like noobzilla mentioned somehow qa flagged got disabled.



At the end it was like you said: i turned off qa flag, reboot, enabled it again and reboot again making sure system update debug was on and now i finally saw the two star system update options. And finally could install the cfw. Thank you all for your help...

Sorry but it's not exactly the same thing...
QA got disabled that's one thing but if
QA was disabled then it didn't show as enabled in the Toolbox...
You didn't follow the steps I gave you because you did not check whether QA was enabled or not. You just assumed it was...

 

It can happen that qa flag is disabled but the option in toolbox still shows enabled, Im not sure why but I have seen the advice given before to disable it and enable it again to be sure.

 

I see. I'm at a loss as to y he's having this problem especially if everything has been double or triple checked.

Sorry but it's not exactly the same thing...
QA got disabled that's one thing but if
QA was disabled then it didn't show as enabled in the Toolbox...
You didn't follow the steps I gave you because you did not check whether QA was enabled or not. You just assumed it was...

You're right. I tweak with the options in rebug toolbox, except QA assuming that it was enabled. At least we finally found the solution...

 

No, i did the steps you mentioned, but like noobzilla mentioned somehow qa flagged got disabled.



At the end it was like you said: i turned off qa flag, reboot, enabled it again and reboot again making sure system update debug was on and now i finally saw the two star system update options. And finally could install the cfw. Thank you all for your help...

glad u got it sorted. I assume this means u were able to install habib 4.81?

 

ive had it happen more than once on the systems i owned. im wondering if it has anything to do with default enabled qa flag cfw.

 

As I thought, in this case, the flag status was not checked properly because assumptions were made.. Never mind, problem solved & am glad it works now... [emoji6]

ive had it happen more than once on the systems i owned. im wondering if it has anything to do with default enabled qa flag cfw.

But you never had a disabled QA flag showing as enabled in the Toolbox, did you?

@DeViL303
You are saying this actually happened to you? Several times? Disabled QA flag showing as enabled in the Toolbox?
If you are correct I think you should let the Rebug Team know about this because then there's a bug, either in the Toolbox, the QA implementation or wherever, that would probably need fixed/worked around or investigated at the very least...

 

glad u got it sorted. I assume this means u were able to install habib 4.81?

Correct, following your tutorial via system update debug.

 

It's not just rebug firmware that looses qa flag it happens on any firmware it might be @Joonie who spotted it with me while messing with idpset in the past. where qa would suddenly turn off and need to be re-flagged again
Didn't get to the bottom of why but as it was easy to re-flag it wasn't ever seen as a big issue

I've got around 15 update pups on my hdd all the way from 3.55 to 4.80.1 rex. I have every rex cfw that's been released I believe. and, I have a downgrader pup which is useless now with qa flagging.

Pinky can you p/m me what cfw's you have
If I don't have any you do have would you be ok uploading them for me please
I have a lot more than 15 cex cfw firmwares though but I'm still looking for hard to find ones.



Sent from my iPhone using Tapatalk

 

It can happen that qa flag is disabled but the option in toolbox still shows enabled, Im not sure why but I have seen the advice given before to disable it and enable it again to be sure.

That is very possible when your qa toggle is enabled but your idps is permanently changed. Because the token gets read from eeprom by peeking, but your token is invalid due to changed idps. I've had the same symptom in the past. That's not really a bug

Qa token is tied to idps. So when its idps is changed, token remains and shown as enabled in toolbox


Sent from my iPhone using Tapatalk

 

yes, i have had to reset qa atleast on 3 or 4 different occasions. all of which were fsm downgraded to 3.55 and then qa flagged. i just cant remember what cfw i updated to because its been so long ago. just had to run the toggle qa app twice. then do the button combo. i think i did once get the problem in rebug toolbox too, but its just been so long ago i dont really remember. but it was solved by disabling it, then enabling it again.

 

It's not just rebug firmware that looses qa flag it happens on any firmware it might be @Joonie who spotted it with me while messing with idpset in the past. where qa would suddenly turn off and need to be re-flagged again
Didn't get to the bottom of why but as it was easy to re-flag it wasn't ever seen as a big issue


Pinky can you p/m me what cfw's you have
If I don't have any you do have would you be ok uploading them for me please
I have a lot more than 15 cex cfw firmwares though but I'm still looking for hard to find ones.



Sent from my iPhone using Tapatalk

the token consists of idps
also i think i made it so idps is read from eid5, not sure if qa will even work after idps change

 

There you go it was a simple reason


Sent from my iPhone using Tapatalk

 

the token consists of idps
also i think i made it so idps is read from eid5, not sure if qa will even work after idps change

It does work xD the signature is ignored anyways, it toggles and does its feature regardless


Sent from my iPhone using Tapatalk

 

So to be clear guys, using idpset to set a different idps permanently in eid5 WOULD disable QA as a direct result for sure?

 

You're right. I tweak with the options in rebug toolbox, except QA assuming that it was enabled. At least we finally found the solution...

So was it saying it was already enabled in your case and you assumed it was enabled, fair assumption, or did you not check it and assume it was enabled but really it was disabled and said it was disabled?