PS3 COBRA 7.52 (Homebrew Blocker for PSN & more) + REBUG TOOLBOX 02.02.13 (NEW Cobra Payload Updater)

It has been quite impressive seeing the progression of the COBRA payload over time, COBRA originally debut on the PS3 way back in 2011 as the CobraUSB (by Team Cobra) this refers to version 1.0 - 6.0 of the payload. This is the period that the device was closed sourced and locked down to Cobra's USB dongle. After the device was put aside and shelved by Team Cobra, it laid dormant for sometime, not keeping up with firmware updates and leaving user with many bugs for the early 4.2x CFWs. There was some public pressure for the team to release the source code and with Team Cobra at the time launching a new product in the ODE, the team folded to public pressure and we seen the source code release(s) and the Open Source Cobra (usb-less version) refers to v7.0+ (which currently we stand at version 7.52)

Since that source code release we have seen the likes of @Joonie, @habib, @KW, @deank, @_NzV_ & @aldostools. make various improvements to COBRA and the evolution continues with release and progression of version 7.52 by Joonie that has added various new elements to the payload like the new Homebrew Blocker (by KW & aldostools) that blocks various homebrew when CFW syscalls are disabled from being executed when connecting to PSN, user' have the ability to create custom cfg list to add any additional homebrew then the defaults offer (details listed in the release quote below). Also in v7.52 a fix was provided by Habib that repairs lv1 peek support within multiMAN.

Joonie, has an additional surprise as updating COBRA just got alot easier for REBUG user's as an update has been released for REBUG Toolbox with a new feature: that will allow you to download/update the payload directly from the toolbox, see the easy tutorial (w/ pics) that Joonie has provided. Please take note that this is ONLY for REBUG 4.81.XX CFW user's you should not use this on lower version or other COBRA CFW such as Habib's. ​

Release: COBRA 7.52 (via Joonie)

• 
  
  

  
  COBRA 7.52
  I updated the COBRA revision to 7.52 from 7.51 the source is available in this commit: https://github.com/Joonie86/COBRA-7......
  
  The Following Changes have been added:​
  
  
  
  Homebrew Blocker
  By default, COBRA can block following apps from being launched "ONLY AFTER" Syscalls are disabled by stealth plugins and homebrews​
  • BLES806XX Multiman and assorted tools are in the format BLES806**
  • BLJS10018 PSNPatch Stealth (older versions were already detected as non-NP/BC/BL)
  • BLES08890 PSNope by user
  • BLES13408 FCEU NES Emulator
  • BLES01337 Awesome File Manager
  • BLND00001 dev_blind
  • NPEA90124 SEN Enabler
  And custom config files can be used for white/black listing apps/homebrews/games as you need​
  
  Here's the original quote by @kokotonix about this feature:
  

  The code bellow adds the ability to read a custom blacklist (/dev_hdd0/tmp/blacklist.cfg) and a custom whitelist (/dev_hdd0/tmp/whitelist.cfg) – this is nice for advanced users wanting to do some extra tests.
  
  Priorities:
  

  • Custom blacklist has the higher priority over all the other tests.
  • Custom whitelist has the second priority.
  • The fixed tests has the lowest priority.

  
  So after disabling syscalls, launching homebrews will result following
  
  ​
  
  
  and also, I realized many people having hard time updating their COBRA binaries, I decided to add a new feature to REBUG TOOLBOX
  
  
  COBRA Payload Updater
  Currently the toolbox has a detection for lower revisions of COBRA.
  
  So any version "below 7.52 and 4.81.X" will be supported [REBUG REX / D-REX 4.81.1 and 4.81.2] REBUG 4.80 and below are NOT supported, neither NON-REBUG (Meaning CFWs like HABIB,FERROX and such). AGAIN NOT DECR!!​
  
  
  Here's a little tutorial that can help you understand how it works:
  
  Spoiler: Quick Tutorial

  
  REQUIREMENTS!!
  

  • REBUG 4.81.1 or 4.81.2
  • COBRA 7.31~7.51

  
  

  ​

  
  

  1. Firstly make sure you're on REBUG 4.81.X [1 or 2] and COBRA must be active prior to the update, otherwise the option will NOT be shown
  

  

  
  
  

  2. Locate the option COBRA Payload Updater
  

  

  
  

  3. Select "UPDATE"
  

  

  
  

  4. "COBRA payload updated!" will be shown when finished
  

  

  
  

  5. Exiting the toolbox will restart the system to apply the change
  

  

  
  

  6. Enjoy the new COBRA 7.52
  

  
  
  
  Here's the quick summary and the download link for the new toolbox 2.02.13​
  
  1. COBRA Payload 7.52 including
  
  • @habib's bug fix for lv1 peek support for multiMAN,
  • @deank's backup disc support for PS3 games
  • KW and @aldostools's homebrew blocker thanks to @kokotonix for informing
  
  2. COBRA Updater for REBUG 4.81.X
  
  
  
  IMPORTANT NOTE:
  REBUG 4.80 and below are NOT supported, neither NON-REBUG (Meaning CFWs like HABIB,FERROX and such) AGAIN NOT DECR!!
  .​

Download: REBUG Toolbox v02.02.13 (w/ new COBRA Updater Feature)


Source: www.psx-place.com​

 

I have a feeling the compatibility could vary depending on the media and the bd drive model

The BD drive model (of the reader or burner) i dont think, but the disc manufacturer media i think is posible
The other day you posted a message where you insisted in the disc manufacturer, and i think you was right in pointing at it

I remember perfectlly that for PS2 the best media manufacturer was MCC (Mitsubishi Chemicals Company), this can be seen on imgburn (or "DVD decrypter" that was the best program used at that time and was the antecessor of imgburn)
At that time, there was a few brands using discs made by MCC, the most known (and most relliable) was verbatim, but not all the verbatim discs was made by MCC, only a few (iirc it was the verbatim DVD-R series labeled as "AZO" that had some kind of metallic protection layer), so after buying the verbatim discs it was important to verify if the ones you bought was actually made by MCC to be sure that was "the good ones"

Nowadays i have no idea if MCC continues manufacturing discs for other companies, no idea if verbatim still continues working with MCC, no idea if MCC ever entered in the bussiness of manufacturing Blu-rays, and no idea if the quality of MCC and others companies follows the same rules
After all has passed lot of years but i just wanted to add this small bit of info for the people that reads this to take in consideration

The reason why people was worried about this is because PS2 laser lens was very picky with the disc media, and that verbatim discs manufactured by MCC was the best for the PS2 laser... with a big advantage over the others, there was no competition, verbatim + MCC was the clear winners

 

@sandungas My speculation with BD media and drive was based on the previous experience with Swapdisc stuff for ODE back then. But after all, Genps3iso v2.0 seems to be the solid solution for all those issues that were reported, however both of my e01 and a01 have hard time detecting burned media. Well those lens were manufactured in 2007 ish so It may have been worn out.. although it has no problem detecting retail discs..


Sent from my iPhone using Tapatalk

 

I imagined with PS3 ODE there has been some dscussions about this, i never did read about it thought but is something expected
Also, at the time of PS2 there was some cheap DVD brands (some that was not even branded) that was using MCC and those discs was very good

-------------------
Well, personally i refuse to use any geniso version, i dont really understand why people doesnt uses the makeps3iso code from estwald that is fully open source and without bugs known at this point
Well, actually i know why people uses genps3iso, is because some devs/sceners promotes it, but thats another story

I know you have been using almost all formats while testing and you have backups made by different tools (makeps3iso/geniso/3k3y) so you are not a "hardcore geniso fan"
I did the same too, i was testing all tools and being very picky to see the differences, not at hex level but in how the files are managed, and imo 3k3y is the worst, and geniso is the second worst (not because the problems people has been reported latelly in 2.5 but before that in previous versions it was doing some weird things i dont even remember)
What i did was to spent some days/weeks testing all them to decide wich one was the best... and then all my .iso files has been made using the same tool (the one from estwald), to keep some consistency in my collection

If at some point some backup managers stops giving compatibility with the .iso's created by estwald tool im fucked up though, but at this point doesnt worries me much... because managunz will support them

 

It was discussed numerous times: for burned PS3 discs (CD/DVD/BD) use ONLY genps3iso_2.0. The reason is that it doesn't add anything related to protection/encryption or other things that break the current burned disc support. Other tools/version may add encryption flags for eboot.bin/*self/*sprx files leading to 80000017 error.

Thank you @deank and @Joonie continue with your wonderful work. Problem solved used genps3iso_2.0

Media support was what was missing from the homebrew of ps3, let's see scene ps3 awaits more surprises. Ps2 and ps1 support in media is it possible in ps3 slim?

off : @deank could back to work on its fantastic , multiavchd video editing tool.? Giving 4k video support !!

 

The BD drive model (of the reader or burner) i dont think, but the disc manufacturer media i think is posible
The other day you posted a message where you insisted in the disc manufacturer, and i think you was right in pointing at it

I remember perfectlly that for PS2 the best media manufacturer was MCC (Mitsubishi Chemicals Company), this can be seen on imgburn (or "DVD decrypter" that was the best program used at that time and was the antecessor of imgburn)
At that time, there was a few brands using discs made by MCC, the most known (and most relliable) was verbatim, but not all the verbatim discs was made by MCC, only a few (iirc it was the verbatim DVD-R series labeled as "AZO" that had some kind of metallic protection layer), so after buying the verbatim discs it was important to verify if the ones you bought was actually made by MCC to be sure that was "the good ones"

Nowadays i have no idea if MCC continues manufacturing discs for other companies, no idea if verbatim still continues working with MCC, no idea if MCC ever entered in the bussiness of manufacturing Blu-rays, and no idea if the quality of MCC and others companies follows the same rules
After all has passed lot of years but i just wanted to add this small bit of info for the people that reads this to take in consideration

The reason why people was worried about this is because PS2 laser lens was very picky with the disc media, and that verbatim discs manufactured by MCC was the best for the PS2 laser... with a big advantage over the others, there was no competition, verbatim + MCC was the clear winners

Best media for ps2 was ridata, RITEK G04 and for dual layer xbox 360 ``azo`` verbatim mkm 001 or mkm003

http://www.ebay.com/itm/20-Verbatim...572243?hash=item258ffde993:g:VpkAAOxyJypTkhu2

We have sim verbatim in bluray
And continues with one of the best media brands

 

@Joonie @deank

I noticed the new toolbox must move the new cobra files rather than copy them.

I just tried the latest sman 1.06, setup my options scanned for games, restarted etc. and after 15 minutes of holding and banging on the start button with nothing happening (eventually threw an 80028F14 error when it did try to launch the menu), I thought maybe it was cobra 7.52 and its blocker messing with it.

So I manually copied cobra 7.51 back on (which didn't help with sman anyway)... Went to reinstall cobra 7.52 via the toolbox and got a message about no payload files detected and had to reinstall the toolbox package before I could update to cobra 7.52 again.

All in all a rather unsuccessful embarrassing night. lol

Back to square one.

 

To start sMAN you need to press L2+R2. The error you got was because you pressed [start] while at the /app_home entry. The shortcut was changed to L2+R2 few builds ago.

 

To start sMAN you need to press L2+R2. The error you got was because you pressed [start] while at the /app_home entry. The shortcut was changed to L2+R2 few builds ago.

Well don't I feel like an idiot.. hahah.
Guess I should of read up on it first with all that's going on before blindly downloading the latest sprx and having a go.

 

Well, personally i refuse to use any geniso version, i dont really understand why people doesnt uses the makeps3iso code from estwald that is fully open source and without bugs known at this point
Well, actually i know why people uses genps3iso, is because some devs/sceners promotes it, but thats another story

And why should I use makeps3iso (never heard of it, but still) when genps3iso 2.0 does what it is designed for. I have no problems with it using it since 2011 - not a single ISO had a problem - it never created incompatible discs nor had any problems. You say "opensource" - right - we've seen where it lead with 10 flavors of ISO generation tools, each one "claiming" to have fixed something and at the end you have 10 tools which in theory should create 1:1 ISO files from folders, but they don't.

Personally I don't care if people use this or that tool - I only mentioned genps3iso_v2, because it was the one I used for the last 6 years and it is also the same code that is used in multiMAN to create ISO from folder. As it seems it gives 100% compatibility with burned discs, so take it as you wish.

 

I remember messing with them, and preferring genps3iso to them all....i remember when i built my tool for iso generation, i defaulted to the latest genps3iso (at the time was 2.5 or 2.6) but i always used/preferred 2.0

 

And why should I use makeps3iso (never heard of it, but still) when genps3iso 2.0 does what it is designed for. I have no problems with it using it since 2011 - not a single ISO had a problem - it never created incompatible discs nor had any problems. You say "opensource" - right - we've seen where it lead with 10 flavors of ISO generation tools, each one "claiming" to have fixed something and at the end you have 10 tools which in theory should create 1:1 ISO files from folders, but they don't.

Personally I don't care if people use this or that tool - I only mentioned genps3iso_v2, because it was the one I used for the last 6 years and it is also the same code that is used in multiMAN to create ISO from folder. As it seems it gives 100% compatibility with burned discs, so take it as you wish.

Remember this ?, your own words
http://psx-scene.com/forums/f6/arti...webman-v1-34-a-125277/index3.html#post1153025

...mM/mmCM/genps3iso generate faulty iso files sometimes, but it is a problem with the iso creation and not the cobra itself. If you find a title that doesn't work, I'll try to obtain and get it to work.

Dean

And a message i wrote at that time related with this
http://psx-scene.com/forums/f6/arti...webman-v1-34-a-125277/index4.html#post1153108

When i was testing the tools i could find some bugs in ps3geniso myself, but now i dont even remember because i stopped using it so i cant report the exact details, i never made a list of the problems but i have to insist ps3geniso has bugs or/and small problems that never has been fixed, if noone believes me is ok, eventually someone will report them

Also a "funny" problem is only you have the source code, so how can other people fix the bugs ?, is imposible
After testing all the tools (there are only 3 formats not more) i decided to use makeps3iso because 1) doesnt seems to have bugs 2) is open source
genps3iso seems to lose in those 2 fields because 1) has bugs 2) is closed source and abandoned officially and unnofficially for some years when you was not active

For burned media i have no idea if the .iso files created by makeps3iso works, by reading the posts in this forum it seems nobody tryed

Edit:
More games reported not working with genps3iso
Transformers Devastation, Bayonetta, Crysis 3, Enemy Front
http://www.maxconsole.com/threads/transformers-devastation-returns-to-xmb.39476/

 

@Joonie @deank

I noticed the new toolbox must move the new cobra files rather than copy them.


So I manually copied cobra 7.51 back on (which didn't help with sman anyway)... Went to reinstall cobra 7.52 via the toolbox and got a message about no payload files detected and had to reinstall the toolbox package before I could update to cobra 7.52 again.

All in all a rather unsuccessful embarrassing night. lol

Back to square one.

Here's what the toolbox does for updating payload.

1. Firstly it detects if You're on Rebug rex/drex

2. Then it checks if you're on 4.81 and Cobra version is below 7.52

3. Deletes Stage2.cex,dex and .bak (in case someone messed it up) from the dev_flash

4. Then it copies stage2.xxx.update to dev_flash

5. After finished, it deletes stage2.xxx.update from the toolbox

So which was why you had to reinstall


Sent from my iPhone using Tapatalk

 

@sandungas My post about "sometimes faulty isos" was a wrong observation at that particular moment of time. What was the fix? Did people recreate the ISOs or we just fixed stage2?

There were only two times I suggested changes to stage2.bin and that was the fist occasion. The reason for games failing to start or crashing at some point were problems in the games themselves (like addressing //dev_bdvd or other wrong paths that path redirections didn't follow) and not the ISO. Also at that particular moment of time I modified mM's iso creation for a test and that's how I found out that the problem was not in the ISO.

I know that English is not your mother tongue, but did I say that genps3iso_v2 had bugs to be fixed?

Quoting messages from other forums about issues when people "resign" "eboots" left and right - come on... ODEs?! And btw Bayonetta works just fine - it was one of the problematic games back then (in 2014) and it was fixed by stage2 changes.

Anyway, it is way off-topic now. Use whatever tool you like and if you find it flawless - recommend it to other users. I think I never mislead anyone intentionally.

 

i have rebug 4.81.2 cobra 7.50 , i can update to cobra 7.52 or before i have to update to cobra 7.51

 

i have rebug 4.81.2 cobra 7.50 , i can update to cobra 7.52 or before i have to update to cobra 7.51

Supports patching Cobra 7.31 .. 7.51 and thus also 7.50

@Joonie would be possible to have the source code of the toolbox rebug? probably the languages are documented and not compiled

 

Supports patching Cobra 7.31 .. 7.51 and thus also 7.50

@Joonie would be possible to have the source code of the toolbox rebug? probably the languages are documented and not compiled

I'll update it when I get home

FYI
@Checcolino80 @smikk

https://github.com/Joonie86/Rebug-Toolbox/commit/14f48c589100adc65d300d183293f4e7dd6ac28a

I haven't added multi-lang support on new strings, this is the same code used for the english only version.

 

Here's what the toolbox does for updating payload.

1. Firstly it detects if You're on Rebug rex/drex

2. Then it checks if you're on 4.81 and Cobra version is below 7.52

3. Deletes Stage2.cex,dex and .bak (in case someone messed it up) from the dev_flash

4. Then it copies stage2.xxx.update to dev_flash

5. After finished, it deletes stage2.xxx.update from the toolbox

So which was why you had to reinstall


Sent from my iPhone using Tapatalk

Ahh ok, so we will have to reinstall the toolbox package if we ever change or reinstall the CFW or manually change cobra.
Can't just leave the .update files in place to save future hassles over the sake of ~160kb of hdd space?

Not that it really matters, I'll just have to keep the toolbox installer package on hand...
Just might save future questions being asked again and again.

 

Ahh ok, so we will have to reinstall the toolbox package if we ever change or reinstall the CFW or manually change cobra.
Can't just leave the .update files in place to save future hassles over the sake of ~160kb of hdd space?

Not that it really matters, I'll just have to keep the toolbox installer package on hand...
Just might save future questions being asked again and again.

TBH, I still don't feel comfortable providing COBRA updater after seeing the semi brick report caused by the corrupted stage2 inside the toolbox. I don't know how that even happened.

Maybe the corruption was little and ok enough for that corrupted pkg to be installed without an issue, then it lead the semi-brick after copying corrupted files,

I'll have to add more checks on the file before and after, make sure the copied contents are the same as the original pkg, then reboots for good

 

Remember this ?, your own words
http://psx-scene.com/forums/f6/arti...webman-v1-34-a-125277/index3.html#post1153025

And a message i wrote at that time related with this
http://psx-scene.com/forums/f6/arti...webman-v1-34-a-125277/index4.html#post1153108

When i was testing the tools i could find some bugs in ps3geniso myself, but now i dont even remember because i stopped using it so i cant report the exact details, i never made a list of the problems but i have to insist ps3geniso has bugs or/and small problems that never has been fixed, if noone believes me is ok, eventually someone will report them

Also a "funny" problem is only you have the source code, so how can other people fix the bugs ?, is imposible
After testing all the tools (there are only 3 formats not more) i decided to use makeps3iso because 1) doesnt seems to have bugs 2) is open source
genps3iso seems to lose in those 2 fields because 1) has bugs 2) is closed source and abandoned officially and unnofficially for some years when you was not active

For burned media i have no idea if the .iso files created by makeps3iso works, by reading the posts in this forum it seems nobody tryed

Edit:
More games reported not working with genps3iso
Transformers Devastation, Bayonetta, Crysis 3, Enemy Front
http://www.maxconsole.com/threads/transformers-devastation-returns-to-xmb.39476/

How much junk I read now

http://psx-scene.com/forums/content/ps3-iso-tools-updated-version-2-0-4781/
No longer is "makeps3iso" being used but instead "genps3iso_v2.5"
Tools equal

You do not seem to know the developer @ deank's.
It asks for tips to develop and fix bugs in the program. never indicated a bad tool

 

Yes I can test. I can not find this version for download.

EDIT 1
found it
http://www.psx-place.com/resources/genps3iso-burned-ps3-b-c-dvd-media-compatible.538/
I'll try

EDIT 2

GenPS3ISO v2.0 working perferct

tested two games
Ni no Kuni Wrath of the White Witch

Puppeteer

BD-R

You are a legend. Been looking everywhere for V2.0, but every link I've found so far was dead in the water.

Just bought a new 2TB drive to try out on the PS3 with NTFS so the Wii can have my FAT32 drive back and am about to rebuild / unsplit all my ISOs (*yawn*) to make it consistent and maybe try a few burnt games to see how things go.

If figure if @deank uses that and I'm using his software, I'll use that to keep things as directly comparable as possible when testing.