Sponsored Links

Sponsored Links

JaicraB on Cobra USB JIG Protection RTOC Trick for PS3


Sponsored Links
177w ago - Today Spanish PlayStation 3 developer JaicraB has explained the Cobra USB JIG protection RTOC trick implemented for the PS3 against cloning the device.

To quote, roughly translated: Flynn sent me this text explaining this protective carrying the Cobra, I hope it will open the eyes of those interested in reversing the dumps.

EXPLAIN RTOC COBRA TRICK

The JIG Cobra has several protective measures to ensure that your code could not be used correctly even if your code could be dumped.

This trick RTOC in the registry is the first used for this purpose in addition to hinder analysis.
Registration is initially RTOC stored in the battery to keep the RTOC of lv2 and power it back later:

[Register or Login to view code]


At this point we have to explain that the OFFSET DELTA. DELTA OFFSET is a method used in the x86 in its original moments in the creation of computer viruses, to calculate the memory address in which we are in the sea of ​​bytes in RAM.

In the original time a computer virus when I did not know where he was pulled into an executable,
depending on the executable it could be an initial site or another, for it was invented DELTA OFFSET.

DELTA OFFSET can be used in any system, the procedure is:

  • Using the record that indicates the current execution address (or the next depending on the system)
  • Reducing the size of the previous code we use the value obtained from the registry.

Knowing this, and taking for example the x86 processor where the EIP register can not be read directly invented the trick make a call to a "subfunction" which is simply the following line to the call:

[Register or Login to view code]


X86 call instruction saves the top of the stack the address of the next instruction to itself. Thus using pop draw from the top of the stack this value, and stored in eax for example, and having the memory address where we only subtract the above would be missing and we have the exact calculation.

The PowerPC can use this trick using the BL instruction is equivalent (LINK BRANCH), which jumps to a "subfunction" but before you save LR in the record the following address to BL.

[Register or Login to view code]


At this point we see the trick used for the creation of the RTOC of charges at this time. If you look both r0 and RTOC are passed to 0:

[Register or Login to view code]


Subsequently, given the value 0x11DE0 to RTOC:

[Register or Login to view code]


A r0 is given the value 0x920:

[Register or Login to view code]


R0 is subtracted from the value of RTOC:

[Register or Login to view code]


Unlike the PowerPC x86 LR register can be read directly with mflr instruction, we put in RTOC the value obtained by the delta offset:

[Register or Login to view code]


To calculate the delta offset subtract final instructions executed before the delta offset, which were 4, or 16 bytes:

[Register or Login to view code]


Finally we add the value of r0 at the end of the delta offset RTOC, storing the result in the RTOC and this already takes RTOC suitable for this hook:

[Register or Login to view code]


It takes having the RTOC stored in the stack 3 arguments that the hook received:

[Register or Login to view code]


You call the function of the charges where the first argument will check for command 0x8202 (a special command to the usual):

[Register or Login to view code]


After making the necessary steps as charged, the battery recovers the original RTOC, like the arguments the hook received, it executes the original instruction that was overwritten in the syscall entry 379 (in this case) to have our hook, and call the original syscall lv2:

[Register or Login to view code]


Upon returning to retrieve the original LR from the stack and returns to the prompt

[Register or Login to view code]





Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!

Comments 1057 Comments - Go to Forum Thread »

• Please Register at PS3News.com or Login to make comments on Site News articles. Thanks!

PS3 News's Avatar
#632 - PS3 News - 55w ago
Below is an Install CFW 4.46 Mixed with Cobra 7.00+Play PS3/PS2/PSP ISO GAMES Tutorial by Nicolas19 for use with Cobra CFW as follows:

Hi guys, here is another nOOb Tutorial that help users that how use all Features of Cobra 7.00 that Mixed in Rogero CFW 4.46 v1.0

Step 0: Important Notes

  • Always Check CFW with PS3 PUP Check [MD5 VERIFY]
  • Use a FAT32 flash memory that has the files needed to install CFW
  • Eject any disk you have in the drive because if there is a disc in the PS3,Your PS3 ]will be upgraded with Update File That is inside the game disc
  • This CFW is installed only on consoles With OFW 1.00--3.55 and All CFW/MFW 3.55 or CFW +3.55 (Even CFW 4.50) with spkg sig check patched
  • If you still using True Blue/JB-King dongle or any DRM Dongle, Unplug and Then Put it in Recycle Bin and start Tutorial From Step 1
  • If your console is Spoof to +3.55 Versions ,you do not need to disable it
  • CFW Users With Downgraded PS3,no need to dehash (Qa Flag) PS3 but if you like dehash your PS3,Use Toggle QA

Step 1: Download Rogero 4.46 v1.00 Mixed with COBRA 7.00

First to start, Download CFW 4.46 Mixed with Cobra 7.00

Download: [Register or Login to view links]

MD5: 549EC14879306BD807029C2640713AD0

Step 2: Installing CFW via XMB

After Download above Package,Extract it and Rename the Downloaded File to "PS3UPDAT.PUP" and copy like below in a FAT32 Flash memory :

PS3/UPDATE/PS3UPDAT.PUP

Go to XMB==>> System Setting ==> System Update and select Update via Storage Media.
It's all done.

Step 3: Installing multiMAN Backup Manager

I Created a Package That is include Latest Version of multiMAN With Support CFW 4.46 Mixed with Cobra 7.00

Download: [Register or Login to view links]

After Download extract The Package and Then copy "multiMAN ver 04.50.04 BASE CEX (20131103)" into a FAT32 Flash memory and Go to Install Package in XMB and Install it

Extra award 1: How Making & Playing Blu-Ray backups

In "mmCM mode" users can be Backup original blu-ray movies but backups won't work because of AACS copy protection. However, you can transfer these backups to your PC, decrypt them using some tool such as AnyDvd HD, DVDFab, etc, and transfer the decrypted iso back to the PS3

If you have a blu-ray reader on your computer, you may want to do the full process there instead.

Making Blu-Ray backups:

1. Start multiman from the XMB
2. Go to HOME column and select "Switch between mmCM and multiMAN"
3. Now Insert a blu-ray (BD-ROM, BD-R, BD-RE). It will appear in the video section.
4. Select it, press triangle, and choose "Create ISO".

Playing Blu-Ray backups:

1. Start multiman from the XMB
2. Go to HOME column and select "Switch between mmCM and multiMAN"
3. Choose a backup in the video section and press X.
4. mmCM will mount the backup and exit. You can play your movie backup using the XMB player.
5. When you are done playing the backup, you can start mmCM again if you wish to unload the backup.

mmCM uses the following directories to load/write Blu-Ray backups in iso format:

· /dev_hdd0/BDISO
· /dev_usbXXX/BDISO

Iso files can be split using the same naming convention used for game backups in iso format.
Blu-Ray backups are not limited to movies; any kind of iso file having a file system recognized by the PS3 can be mounted as a Blu-Ray.

Extra award 2: How Making & Playing DVD backups

In "mmCM mode" users can be Backup original DVD movies but backups won't work if they use CSS copy protection. In these cases, it is a better idea to do the backup in a computer using any program that removes CSS, and then transfer the unprotected backup to the PS3.

Making DVD backups:

1. Start multiman from the XMB
2. Go to HOME column and select "Switch between mmCM and multiMAN"
3. Now Insert a DVD (DVD-ROM, DVD+/-R or DVD+/-RW). It will appear in the video section.
4. Select it, press triangle, and choose "Create ISO".

Playing DVD backups:

1. Start multiman from the XMB
2. Go to HOME column and select "Switch between mmCM and multiMAN"
3. Choose a backup in the video section and press X.
4. mmCM will mount the backup and exit. You can play your movie backup using the XMB player.
5. When you are done playing the backup, you can start mmCM again if you wish to unload the backup.

mmCM uses the following directories to load/write DVD backups in iso format:

· /dev_hdd0/DVDISO
· /dev_usbXXX/DVDISO

Iso files can be split using the same naming convention used for game backups in iso format.
DVD backups are not limited to movies; any kind of iso file having a file system recognized by the PS3 can be mounted as a DVD.

Extra award 3:How Making & Playing PSX backups

In "mmCM mode" users can be Backup original PSX game or a backup in a CD-R disc.

Making PSX backups:

1. Start multiman from the XMB
2. Go to HOME column and select "Switch between mmCM and multiMAN"
3. Now Insert a original PSX game or a backup in a CD-R disc.It will appear in the games section.
4. Select it, press triangle, and choose "Create ISO".Wait for the copy to complete. If the game only contains the data track, the backup will be in iso format;
if it contains more tracks, cue/bin format will be used instead.

Playing PSX backups:

1. Start multiman from the XMB
2. Go to HOME column and select "Switch between mmCM and multiMAN"
3. Choose the backup from the list in the "Retro" section and press X.
4. mmCM will mount the backup and exit. You can start the psx game backup from the XMB.

mmCM uses the following directories to load/write PSX backups:

· /dev_hdd0/PSXISO
· /dev_usbXXX/PSXISO

Allowed format are:

· Iso (mode 2/2352).
· Cue+bin. Data track must be mode 2/2352.

Playing PSX backups in CD-R:

"CFW 4.46 Mixed with Cobra 7.00" allows PSX backups in CD-R discs to be transparently started from XMB without the need ofmultiMAN (mmCM mode)

PSX region

"CFW 4.46 Mixed with Cobra 7.00" bypasses psx region for original psx games and backups in both CD-R and iso/cue format

Extra award 4: How Making & Playing PS2 backups

In "mmCM mode" users can be Backup original PS2 game or a backup in a DVD+/-R or CD-R. Support for PS2 isos in non BC consoles using ps2_netemu. You can use it in the same way as before, just load an iso and launch from disc icon, No need for encrypted isos, isos patched with limg sectors, etc. Just your normal PS2 isos dumped from discs or taken from somewhere. Don't forget to set the memory cards in XMB, in the old memmory card utility for PS/PS2, as ps2_netemu won't let you assign them in game.

Making PS2 backups:

1. Start multiman from the XMB
2. go to HOME column and select "Switch between mmCM and multiMAN"
3. Now Insert a original PS2 game or a backup in a DVD+/-R or CD-R.It will appear in the games section.
4. Select it, press triangle, and choose "Create ISO".

Playing PS2 backups:

1. Start multiman from the XMB
2. go to HOME column and select "Switch between mmCM and multiMAN"
3. Choose the backup from the list in the "Retro" section and press X.
4. mmCM will mount the backup and exit.You can start the PS2 game backup from the XMB.
Don't forget that you must assign slots to virtual memory cards in the XMB if they aren't alreadyassigned.

mmCM uses the following directories to load/write PS2 backups:

· /dev_hdd0/PS2ISO
· /dev_usbXXX/PS2ISO -> currently, only for transferring, not loading

Allowed format are:

· DVD backups: iso files with 2048 bytes per sector.
· CD backups:

1. ISO files with 2048 or 2352 bytes per sector; CD backups with 2352 bytes per sector are more compatible.
2. Cue+bin: Data track must be mode 2/2352.
.
PS2 iso backups are automatically unmounted when returning to XMB from the game.
Because of the special nature of the PS2 emulator,

Playing PS2 backups in CD-R/DVD+-R:

"CFW 4.46 Mixed with Cobra 7.00" allows PS2 backups in CD-R/DVD+-R discs to be transparently started from XMB without the need ofmultiMAN (mmCM mode) However, there is no support for optical discs in ps2_netemu (None BC console) but BC consoles will still use their respetive emulators (ps2_emu, ps2_gxemu), which have much better compatibilty and also support optical discs, original or backup but these backups must be burn from an iso with a mds file. Without an appropiated mds file describing layer break, dual layer backups won't work.

PS2 region

"CFW 4.46 Mixed with Cobra 7.00" bypasses all region checks for original, optical backups and backups in iso format.

Extra Award 5:How Playing PSP ISO Game in "mmCM mode" users can be Playing PSP games

Playing PSP iSOs:

First Download Cobra-USB_PSP-Launcher in Below:

Download: [Register or Login to view links]

Now install the "Cobra-USB_PSP-Launcher.pkg"

Do not run this package when you see the "NO GAME" icon or the PS3 will crash/reboot.

Once PSP-Launcher is installed:

1. Start multiman from the XMB
2. Go to HOME column and select "Switch between mmCM and multiMAN"
3. Choose the backup from the list in the "Retro" section and press X.
4. mmCM will mount the backup and exit. Now PSP-Launcher has the icon of the PSP backup and you can start the game from there.

mmCM uses the following directories for PSP backups:

· /dev_hdd0/PSPISO
· /dev_usbXXX/PSPISO

Allowed format are:

·ISO, the typical backup format used by the psp homebrew community. CSO format is not supported yet. EBOOT.BIN in the ISO can be either encrypted or decrypted.

Extra Award 6: How Making & Playing PS3 ISOs

"CFW 4.46 Mixed with Cobra 7.00" allows Playing PS3 Games in ISO Format. The genps3iso tool may be used to generate .iso images from a directory structure of a game dumped using CFW. Split type files generated by the tool are also supported.

Making PS3 ISO Games in PC:

In order to generate a valid ISO, run genps3iso and specify the correct directory (The parent directory which contains the PS3_GAME directory) and the output .ISO file, as well as whether or not to split the ISO into 4GB files. Splitting the ISO into 4GB files is only useful if you want to use a FAT32 drive.

Download: [Register or Login to view links]

Making PS3 ISO Games in PS3 :

1. Start multiman from the XMB
2. Go to Game column and press triangle, and choose "Create ISO".

Playing PS3 ISOs:

1. Start multiman from the XMB
2. go to HOME column and select "Switch between mmCM and multiMAN"
3. Choose the ISO from the list in the "Game" section and press X.
4. mmCM will mount the ISO and exit.You can start the PS3 game That Loaded from the XMB.

mmCM uses the following directories for PS3 ISOs:

· /dev_hdd0/PS3ISO
· /dev_usbXXX/PS3ISO

Extra award 7: How to Play PS3 games (PS3ISO, BDISO, DVDISO) through pc network

ps3netserver, the pc server for netiso.sprx, has been updated in "CFW 4.46 Mixed with Cobra 7.00"with support of games in jailbreak directory format, so it is not longer restricted to isos.

Step 1 - Computer Setup

Windows 7

Go to "Control Panel" and under "Network and Internet" click "View network status and tasks" To open "Network and Sharing Center". On the left side panel click "Change adapter settings". Identify which device is the LAN port you will be using, right click on it and select "properties". Click on the item "Internet Protocol Version 4 (TCP/IPv4)" then click the button "Properties". Click "Use the following IP address:" and "Use the following DNS server addresses:"

Windows XP

Go to the start menu and hover over "Connect to". Select "Show all connections". Identify which device is the LAN port you will be using, right click on it and select "properties". Click on the item "Internet Protocol Version 4 (TCP/IPv4)" then click the button "Properties". Click "Use the following IP address:

Fill out the box so it appears as below:


IP Address: 192.168.1.101
Subnet Mask: 255.255.255.0

Leave the DNS settings and Default Gateway blank and press OK. Close all the other dialogues, you're done here for now.

Step 2 - PS3 Setup

Go to the settings tab on the XMB, then select "Network Settings" followed by "Internet Connection Settings". Push ok on the prompt and select "Custom", "Wired Connection", "Auto-Detect" then "Manual". Fill out the form as follows.

IP Address 192.168.1.100
Subnet Mask 255.255.255.0
Defualt Router 192.168.0.1
Primary DNS 192.168.0.1
Secondary DNS 0.0.0.0

Select "Automatic", "Do Not Use" and "Disable". Push X to save the settings. Test connection to verify you can acquire an IP Address. Internet Connection should fail.

Step 3 - PS3netsrv Setup

First Download PS3netsrv that Released By deank :

Download: [Register or Login to view links]

After Download,Extract Package inside Folder jailbreak directory format Games (or Any Other Like PS3ISO,DVDISO,BDISO) that you want Load From network like Below:


Now in Folder GAMES, Hold "Shift button" and Press Right Click and select "open command window"


Type in the following into the cmd prompt window:

[Register or Login to view code]

Now hit enter ,The cmd window will now say: Waiting for client...


Now goto your PS3 and under the XMMB settings coloumn (second column on the far left) scroll to Network Servers and click on it.
In the side menu that pops open select /nethost0 - Enable and then follow the onscreen prompts entering your IP/PORT/Friendly Name
now you must enter your PC's IP: 192.168.1.101

Now you should see the cmd window say something like: "Connection from 192.168.1.100" If all is working as it should you can now goto the the File Manager and you should see net_host0 listed there (or what ever friendly name you gave it) ,click on that and all your ISO (if in the folder) should show up for you.

P.S: I've ordered English User Guide from Cobra Team and remove unnecessary instances and Added More Explain. Now it looks more beautiful and more understandable.

Thanks Cobra Team for Release Source Code of Cobra USB Dongle
Thanks deank For Awesome Backup manager
Thanks CaptainCPS-X for Patched SYSCON Rogero 4.46 v1.00 Mixed with COBRA 7.00 to 4.50
Thanks Mahmoud For Download Links
Thanks peyman47 For Help me in Extra award 7

PS3 News's Avatar
#631 - PS3 News - 56w ago
Below is the Unofficial Dongleless Cobra 7.00 with details as follows, which is implemented into Rogero 4.46 v1.00:

Download: [Register or Login to view links] (235.12 MB) / [Register or Login to view links] (Mirror) / [Register or Login to view links] (Mirror #2)

MD5: D6721344ED0CDC2E8A054A68B7EBC365

Cobra USB main developer has released a cleaner better release of Cobra USB's source, and he has also implemented it on Rogero 4.46 v1.00 CFW!

Cobra USB main developer has shared a cleaner and better release of the dongle's source code.

The release, called "COBRA 7.00", doesn't require USB and can be used by anyone on any hackable PS3. He also implemented it on Rogero's 4.46 v1.00 as a sample, but of course that it's compatible with other CFWs (see Readme file inside RAR).

Here's the info:

COBRA 7.00

Hello, I'm Cobra USB main developer. First of all, this is an unofficial personal release from me, and not something from Team Cobra. Don't contact them for anything related with this release.

Second, no, no USB reqired, it can be used by anyone on any hackable ps3. That's why I called this mess of a release COBRA 7.00 and not Cobra USB 7.00.

Why this release?

Mainly because I can't stand things not done properly. The original source code of Cobra USB 5.X was released, and yes, all PS3 functionality is there, but also a lot of unnecessary things.

Had I been contacted before the release of the source code, I would have prepared something better.

And rather than seeing someone coming with a bad or incomplete release of a CFW or payload using the source, I prefer to lead the way with a first clean release. I don't think I will do any other.

Second, I wanted to have in a CFW both the functionality of Cobra and a regular CFW, and without that slow device delaying each lv2 boot by several seconds, which caused some side effects in version 6.00 (4.30) on pads, and that I had to fix with one of those ugly hacks/incomplete workarounds that I tend to hate.

Lastly, but no less, I was bored, lot of free time lately, that kills your brains...

WHAT IS COBRA 7.00

What is not? COBRA 7.00 is not a CFW "per se".

COBRA 7.00 is a set of 7 files: lv2_kernel.self, ps2_emu.self, ps2_gxemu.self, ps2_netemu.self, stage2.bin, ps2hwemu_stage2.bin and ps2gxemu_stage2.bin, from those 7, the first 4 are mix of 4.46 CEX OFW files and COBRA code, the others being new and not present in OFW.

Those 7 files are expected to be mixed with existing regular 4.46 CEX based (totally CEX) CFW, to make a CFW that would mainly mix the functionality of both, except for any thing that the regular CFW may do in lv2_kernel.

About "theoretical" compatibility, check the readme in BIN/CFW_BUILDS. Theoretical because only one has been tested. This is, Rogero 4.46 1.00.

A sample PUP of mix of COBRA 7.00 and Rogero 4.46 1.00 is there as well. Mainly included for convenience, for having something end-user friendly.

This CFW has been tested by me on three very different models, a CECHA, a CECHC, and a SLIM.

But because it has only been tested by a single person, caution is to be expected. You are the only responsable of what you install in your machine.

Additionally, there are other parts, like netiso.sprx or cobralib, that are not technically part of COBRA 7.00. They are things expected to be used by managers.

No real change was done to them, just removed something unnecessary in netiso.

There are also some PC tools, the only one relevant to users being ps3netsrv, which has been updated with a new feature (see CHANGELOG).

Although there is no manager that uses that feature atm of writing this.

The source code of components is in SRC folder. The main components of Cobra expect the toolchain found at BSC page, with gcc 4.1.1.

bsc.es/projects/deepcomputing/linuxoncell/cellsimulator/sdk3.0/CellSDK-Open-Fedora/ -> install all ppu* files for your architecture.

Extra things expect either Sony SDK or psl1ght.

PC tools expect gcc. Some of the tools may not compile under mingw32 or won't work in win32. Some tool could give compilation warnings in 32 bits systems, not compile or binary may not work, this wasn't tested. (watch out ps2netemu_gen446)

WHY 4.46 AND NOT 4.50

1. I had already most symbols from 4.46 from some time ago, lazyness.
2. Because there was no good reason to update to 4.50. COBRA does the sfo version patch and sdk version patch on RAM, games for 4.50 are expected to work without changes.
3. Because new versions of 4.46 CFW's are unlikely to appear, then current release would support almost all of them. Minimal modification on some files causes COBRA not to detect some modules, see the readme in BIN/CFW_BUILDS.
4. An OFW bug causes pad synchronization problems when playing PS2 games in CECHA/CECHB in 4.50. I didn't want this one to be endorsed to me.

INSTRUCTIONS

Install a 4.46 CEX cfw mixed with the 7 files of COBRA 7.00.

A sample of a mix of Rogero 4.46 1.00 and Cobra is provided in BIN/CFW_BUILDS/
Check the txt there for compatibility with other cfw.

Install mmCM_04.18.pkg, which has been included here for convenience (it has only been repackaged to avoid version error with multiman).

This won't delete your current version of multiman (if any), it will instead add mmCM to it.
After installation of this package, multiman can run in two modes, "multiman" and "mmCM", by default it will run in "mmCM" mode under Cobra.

Check CHANGELOW below about how to force COBRA 7.00 to run multiman in "multiman mode", this only makes sense if you installed both, mutiman and mmCM.

(More info contained in the rar)

Remember to be careful when testing. Try it at your own risk!

And for those wondering, YES is answer to the question is Team Rebug working on this for updated REX/CEX/DEX firmwares!

Advantages of Cobra CFW over others:

  • Playing PS3 games from network (eg from PC hdd) - TOTALLY DISCLESS
  • Playing PS3 ISOS - TOTALLY DISCLESS
  • Playing PS2 ISOS (without encryption)
  • Playing PSP ISOS
  • Playing BD Movie ISOS

Update: From CaptainCPS-X: COBRA 7.00 - Test Result #1: I took time to transfer most of my PS3 game backups to my NTFS HDD and connected it to my PC. After this was done I started testing the new PS3NETSRV modified by deank with the latest multiMAN, and as expected everything been working flawlessly, even when I don't have a Blu-Ray Drive on my PS3 at this moment, it has been completely removed.

Games tested over LAN (WIRED / NO-BDDRIVE):

OK - BLUS31270-[Call of Duty Ghosts]
OK - BCUS98298-[Beyond Two Souls]
OK - BCUS98174-[The Last of Us]
OK - BLUS30767-[Dragons Crown]
OK - BLES01588-[WARRIORS OROCHI 3]

Load times are fast, only moment I experience loading slow downs are when the Networked HDD has any read/write activity on the PC (Ex. Copying files). My recommendation is to select a HDD on your Networked PC with little to no activity by that PC Operative System. In my case I have my NTFS HDD connected via USB 2.0 to my PC.

I will soon start testing PS1, PS2 and PS3 game backup in ISO format and will report back my results. These tests will be over Network again.

PS: I will work on a guide later on to explain how to setup the Network Share using Wired connection between the PS3 console and the PC. This without loosing access to the internet on both ends. SeeYa!

[Register or Login to view code]



COBRA 7.00 (Mixed w/Rogero 4.46 v1.00) CFW [Patched SYSCON to 4.50, by CaptainCPS-X:

Download: [Register or Login to view links] (193.69 MB)

Hi guys! here I bring a patched COBRA 7.00 CFW to allow its installation over 4.50 CFW(s) without needing to downgrade.

As easy as installing it over XMB, took me just 3 minutes to switch from MLT 3.3.1 [4.50] to COBRA 7.00 [4.46] (no data was lost in the process).

I been hinted that, the originally released COBRA 7.00 CFW already could be installed over 4.50 CFW, but I decided to leave this published, if many believe this is unnecessary I will immediately request its removal. Here is the "readme" with all detailed information:

[Register or Login to view code]








Finally, from akela: greetings from Russia...


From haz367: akela to the rescue... so the diff was the 2 extra patched values > 44 60 > 34 00 thx for example..

looks a bit like sys_param values or whatever... wtf it makes the diff... fixed self.. just for the fun:

Download: [Register or Login to view links]

From JonahUK: Please Note: This will only launch INTERNAL iso files until webMAN has NTFS support

Create a HTML page to look/feel however you want it: Link Format:

[Register or Login to view code]

Create the file for the XMB (fb1.xml) (goes into /dev_hdd0/xmlhost/game_plugin/):

[Register or Login to view code]

Create the link to the above file on the XMB in category_game.xml (/dev_flash/vsh/resource/explore/xmb):

[Register or Login to view code]

I originally used Dean's "category_game.xml" so I simply renamed "fb.xml" to "fb1.xml" and made the changes. Put your index.html into /dev_hdd0/index/ with all the jpg files and you should be good to go. Reboot the PS3 to make all the changes.

From Hells Guardian comes the following tutorial as well: Boot PSP ISOs with Cobra PSP Launcher in PSP Remaster Mode Guide

Download: [Register or Login to view links]

1. First install a cobra compatible CFW.
2. Second Install PSP launcher
3. Third install PSP game to internal OR external HDD in the PSPISO folder
4. Fourth copy the attached Param.sfo (extract it from the rar) to dev:hdd0/game/PSPC66820/
5. Finally boot any PSP game through the launcher and quit.

The next time you load a game through the PSP launcher it will load as a PSP remaster.

Here is an updater set of instructions from Mad Mike 96:

USE cobra launcher in PSP mini or PSP remaster mode.

1 Install a Cobra CFW
2. Install PSP launcher
3. Install attachched Param File to dev:hdd0/game/PSPC66820/
4. change the folder name from PSPC66820 to PSPC66821
5. Rebuild Data base through recovery menu
6. Instsall PSP launcher again
7. mount a PSP game with MMCM
8. Load your game through either the minis launcher or the PSP remaster launcher depending which mode your game calls for. (Note that the PSP remaster launcher will not show the game icon but its mounted. just load it.)

Enjoy this folks. now you can choose what mode your PSP game loads in.

PS3 News's Avatar
#630 - PS3 News - 57w ago
Below is the Cobra ODE v1.6 update and related details, as follows:

21 - 10 - 2013: Cobra ODE News - Update

The much anticipated 1.6 firmware update is now available for download.

The biggest feature of this update is the addition of the new auto-eject feature. You can now switch games without rebooting and without ejecting discs. All from the comfort of your couch. The new auto-eject feature does not require any modifications to the ODE, nor does it require any new accessories or soldering, it is now available to all ODE users, from all models, with the simple update of your Cobra ODE.

We have also added periodical polling of the HDD to prevent hard drives from going to sleep mode which made some games freeze if they had been paused for a while. The HDD polling can be disabled or configured from the cobra.cfg file.

When Cobra ODE was first released, we had seen a huge amount of positive feedback, although many users had two major concerns, the first being the use of homebrew to achieve game selection, and the second being the need to reboot or eject discs in order to switch games. With the Cobra ODE browser support which was added in v1.5 and the auto-eject feature added in v1.6, we have resolved both of these concerns for our users. Today, the Cobra ODE looks like a brand new device with a completely new user experience, which we think will make most of you happy.




The Cobra Team is the first to bring true "no eject, no reboot" feature to the PS3 ODE world for all models and we will continue to bring you new exciting features in the future.You can now grab the 1.6 update form the downloads section. Please refer to the user manual for updated instructions on how to use the auto-eject feature.




We are also releasing an update to ps3genextra tool which generated the Cobra ODE Browser, please use this version with the 1.6 update.

Concurrently, we are releasing an update to the Cobra ODE Manager which adds support for the auto-eject feature and in parallel releasing an update to the third party integration library which allows third party managers to use the auto-eject feature.

Enjoy

Finally, below is a guide from magneto on How to Unbrick Your Cobra ODE, as follows:

For those rare users who have bricked their device by cutting power while the bootloader or fpga1 was being updated, here is how you can fix it.

First, there are four methods to unbrick your ODE, only one will work for you depending on what your situation is, so please read carefully and follow the instructions appropriate for your situation.

For v3 and v4 boards (3.0, 3.10, 4.20, 4.20 QSV and 4.30), it is possible that either the flash is corrupted, if you interrupted a bootloader update, or that the FPGA1 is corrupted. If the FPGA1 is corrupted, it is likely that it will hold the MCU in RESET mode which will prevent the MCU from powering.

If when you connect power to the ODE, you see the clipon PCB flash green very quickly then turn off, then the MCU powered itself but couldn't start the bootloader, you will need to unbrick the ODE using your PC, follow the instructions in the unbrick using USB method section. If you do not see any green light quickly flashing, then the MCU is not powered and is probably being held in RESET, follow the instructions in the unbrick using RESET method section.

For v5 boards, if an error occured when updating the fpga image, then the device may be bricked. It can be restored to factory settings easily, make sure you follow the unbrick method for v5.x boards.

If you followed the right instructions carefully and could not fix the issue, then it is possible that the ODE is damaged.

Unbrick method for v5.x boards

  • Remove power from the ODE
  • Short the R6 pins. This means put a wire between the two solder pads of R6. You can find R6 on the lower right corner of the main chip, just below the yellow component in this image: cobra-ode.com/images/V5_QSV.jpg
  • Put power back to the ODE
  • You can now stop shorting R6.
  • The ODE should then unbrick itself by restoring the FPGA to factory settings, it will now accept a new update from a USB 2.0 device.

Unbrick using RESET method for v3.x boards

  • Power the ODE
  • Short the pin 3 and pin 8 of the U5 component. The U5 component is the chip with 8 pads in the top left corner of the board, as seen in this picture: cobra-ode.com/images/MainBoard.jpg. The pin 8 is the one in the top right corner of the U5 component, adjacent to the corner of the EXP connector, while pin 3 is the on the other side, closest to the border of the board, the third pin counting from the top.
  • As soon as you short pin 3 and pin 8 of U5, the MCU should power up and the clipon PCB light will blink green. Keep those pins shorted while you update the fpga1.dat again using a USB stick.
  • Once the fpga has been restored, and the update completed, you can stop shorting pin 3 and pin 8 of U5, then power cycle your ODE.

Unbrick using RESET method for v4.x boards

  • Power the ODE
  • Short the TP3 and TP4 test points under the RST label. It is located in the top left corner of the ODE, as seen in this picture : [Register or Login to view links]
  • Stop shorting the TP3 and TP4 points
  • If the ODE did not boot, then short the TP3 pad with the eight pad of the U5 component. The eight pad is the one in the top right corner of the U5 component, adjacent to the corner of the EXP connector, as seen in this picture : [Register or Login to view links]
  • As soon as you short TP3 and pin 8 of U5, the MCU should power up and the clipon PCB light will blink green. Keep those pins shorted while you update the fpga1.dat again using a USB stick.
  • Once the fpga has been restored, and the update completed, you can stop shorting TP3 and pin 8 of U5, then power cycle your ODE.

Unbrick using USB method for v3.x and v4.x boards

Requirements

You will need:

  • A PC
  • A USB-A Male to USB-A Male cable
  • A USB stick or HDD formatted in FAT32
  • Zadig appication
  • dfu-util application
  • unbrick.rom file

You can download Zadig here: [Register or Login to view links]
You can download dfu-util here: [Register or Login to view links]
You can download unbrick.rom here: [Register or Login to view links]
You will first need to create a USB-A to USB-A cable. A USB-A connector is the standard USB connector that connects into your PC. This is what a USB-A connector looks like: [Register or Login to view links]
You can make such a cable by cutting two USB cables and then connecting together the green, red, white and black wires of the two cables to create a USB-A to USB-A cable.

Instructions for Unbricking the ODE

  • Turn off the power on the PS3
  • Wait 5 seconds
  • Turn on the power on the PS3
  • Immediately connect the USB cable from your PC to the clip-on PCB where your HDD would normally go
  • Your PC should detect the USB device as a "USB device with DFU capabilities"
  • Let windows finish installing drivers for the USB device
  • Open Zadig
  • Select "List all devices" from the menu
  • Select "USB device with DFU capabilities" from the list in Zadig
  • Select "WinUSB" for the driver
  • Select "Install driver" or "Replace driver"
  • Wait until Zadig successfully installs the WinUSB driver for the USB device
  • Open a command prompt by typing "cmd.exe" from the start menu
  • Go to the directory where you extracted dfu-util
  • Run the command : dfu-util.exe -d 0471:df55 -D C:\Path\To\unbrick.rom
  • Wait until it finishes uploading the unbricking firmware successfully
  • Disconnect the USB cable from the PC
  • Reconnect the USB cable from the PC
  • The light on the clip-on PCB should turn Blue now. If it doesn't not, then something went wrong, go back to the beginning and make sure everything is done correctly
  • Disconnect USB cable from clip-on PCB
  • Copy ldr.rom and mcu.rom to the root of the FAT32 USB stick
  • Insert the USB stick into the clip-on PCB
  • LED should turn purple and flash a few times until it becomes solid red or solid green depending on whether your USB stick has the cobra manager and database
  • Your device is now unbricked, you can use it normally.

If something is unclear or does not work for you, let me know. I have only tested this on a Windows 7 machine, and I don't know if I missed any steps in case my system is set up differently.

Updates: Added link to LPCXpresso for the DFU driver and added USB ID identifiers. If you wish to manually brick the device in order to use this method to flash it, then you can short the SPI Flash chip to force it to enter DFU mode and use the above instructions to flash your device.

Shorting the SPI Flash chip will not permanently brick the device, it will only brick it as long as it is shorted. If you reboot the device without shorting the pins, it will work again as it did before.
To short the SPI Flash, you can use a screwdriver or anything metallic like some change (money) and connect it to the three pins closest to the inside of the board.

The SPI Flash is the chip in the corner of the board between the JTAG connector and the EXP connector and it has 6 pins, 3 on each side. Short the 3 pins that are closest to the EXP connector then connect the power to the board, and the LED will very briefly flash green before turning off. Without shorting those pins, the LED will flash green slightly longer before turning off.

Cobra ODE IDPS Dumper (Dump Your IDPS using Cobra ODE - Unofficial) by atreyu187

I hereby present to you the (Unofficial) Cobra IDPS dumper. A friend of mine (which i shall not name) found a way to dump the IDPS on OFW. I created a neat cobra package from this. You can put this in your PS3_GAMES directory and run it from XMB.

Download: Cobra IDPS Dumper.zip

Usage:

1. Put a fat32 formatted USB key in the USB000 (most left) or USB001 or right port
2. Run the homebrew program, and it will exit again to the XMB
3. IDPS.bin is on your USB drive.

For now this IDPS.bin is not very useful (yet) but we might need it in the future.

Anonymous/Senaxx

dj1138's Avatar
#629 - dj1138 - 58w ago
does anybody know how to get reactpsn to work (or any other app i can get my rock band 3 DLC to work) with cobra 4.3x usb?

hey69's Avatar
#628 - hey69 - 58w ago
same issue

Sponsored Links

Sponsored Links
Sponsored Links

Sponsored Links







Advertising - Affiliates - Contact Us - PS3 Downloads - Privacy Statement - Site Rules - Top - © 2014 PlayStation 3 News