Monday 23 May 2016

It’s official, the Cobra Black-Fin (PSVita piracy dongle) is real, and it’s back… soon (c) via wololo

It seems the latest rumors about the blackfin resurfacing may have been more than rumors. The Cobra Blackfin team have updated their website today, announcing that the Cobra Blackfin is ready (both on the hardware and software front), and currently being sent to some websites for reviews.

I have emailed the Cobra Blackfin team to get a sample and will let you know if they send me one (Hey, we’re the biggest Vita underground community, it would be weird if I don’t get one, right? Right?)

The new announce on the Cobra Blackfin comes with documentation and the necessary software to run the device.

As explained before, the Blackfin is a game “sharing” device that lets you share games you own with your “friends”. Technically, you insert up to 6 legit games in your Cobra device, plug that to your internet-connected PC, and the games are ready to be shared for anyone who wants it.

The documentation hints at a possibility to have the games shared on your own local network, which might allow you to actually share games with only a circle of close friends (something that might be more legally acceptable than sharing it on the Cobra public server).

The Cobra Blackfin manual basically confirms everything we thought about the device and how it will work. You will be sharing your original games online and those will be used at the “authentication” process by other gamers who will only need a “backup” of the game. The Blackfin also ships with all the hardware and software required to dump the cartridges.

blackfin_software 


Cobra Black fin not compatible with firmware 3.60

Perhaps the most surprising thing of today’s announce is that Cobra Blackfin is not currently compatible with firmware 3.60. The Blackfin team advises people to stay on 3.57 or lower for now, but promise they are working on 3.60 compatibility.

A veteran hardware console hacker, whose name I’ll keep anonymous at this point, has confirmed to me the Blackfin is 100% real, but also told me he’d expect Sony to block it within a week of launch. Ouch.

Source: Cobra blackfin site

PS3DumpChecker Build 488 by Littlebalup Out with PS3 4.80 Support

PS3DumpChecker.png
Following the previous updates and NORPatch v4.80, PlayStation 3 developer littlebalup has updated the PS3 Dump Checker homebrew app to PS3DumpChecker v1.0 Build 488 which now includes PS3 Firmware 4.80 support.
Download: PS3DumpChecker.exe (7.7 MB) / PS3DumpChecker.exe (Mirror) / PS3DumpChecker GIT

Changelog:
Build 488 2016-04-29:
  • Changed: The embedded 4.78 patch replaced by a 4.80 patch build from the FERROX 4.80 CEX custom firmware CoreOS.
  • Added: OFW and Patched 4.80 ROS hashs.
Finally, from the ReadMe file, to quote:

PS3DumpChecker

A PS3 NOR/NAND Dump Checker/Verifier

NOTE: Nobody takes ANY responsibility for any false negative/false positive given by this app, the responsibility that your dump is valid is YOURS and yours alone... this tool should be treated as an easy way to make a quick check to see if it's at all worth looking closer at, to really verify your dump read the latest information here: http://www.psdevwiki.com/ps3/Validating_flash_dumps

You may use this tool any way you like, you may also use the code on this repo any way you like If you find any bugs let me know so i can fix them! if i don't hear about bugs i can't fix them

;)
swizzy[at]xeupd.com is my e-mail if you have any bug reports to give or just wanna talk... I'm also available on the irc network Efnet if you wanna contact me in person, i ussually go by the name "Swizzy" or "_Swizzy"
source :http://www.psxhax.com

Free Memory Card Boot (FMCB)

(FMCB) :

Update 2016/05/21: v0.971 (FMCB v1.951) released.
Update 2016/01/04: v0.97 (FMCB v1.95) released.
Update 2013/10/13: v0.96 (FMCB v1.94) released.
Update 2013/10/13: v0.95 (FMCB v1.93) released.
Update 2013/08/22: v0.94H (FMCB v1.92) released.
Update 2013/08/19: v0.94H (FMCB v1.91) released.
Update 2013/08/17: Beta v0.94D & H released.
Update 2013/07/20: Beta v0.94C released, minor bugfix and translation update.
Update 2013/07/16: Beta v0.94B1 released, minor bugfix.
Update 2013/07/14: Beta v0.94B released, minor bugfix.
Update 2013/07/12: Beta v0.94A released, minor bugfix and features update.
Update 2013/07/11 03:21: Added a translation template.
Update 2013/07/10: Beta v0.94 released!
Update 2012/11/04: Beta v0.93B1 released!
Update 2012/04/07: Beta v0.93B released!
Update 2011/11/14: Beta v0.93A released! (Late update)
Update 2011/10/03: Beta v0.93 released!
Update 2011/09/20: Beta v0.92 released!
Update 2011/09/16: Beta v0.91 released!
Update 2011/09/14: Beta v0.90 released!

Quick jump


  1. Preface
  2. How to use this
  3. Changelog
  4. Known bugs
  5. Additional notes
  6. Warnings against potential pitfalls
  7. Notes regarding the sources
  8. Supported languages
  9. Downloads/links

                                            Preface

This is an Free Memory Card Boot (FMCB) installer. It was previously known as the "Unofficial FMCB v1.8C" installer.
No part of it was directly re-used from FMCB v1.7 itself, but parts of it were based or referenced from the code of FMCB v1.7.
The files in the fmcb-install folder are from Jimmikaelkael's PS3MCA project. Of course, I didn't include the questionable files which Sony claimed as a breach of their copyright.
Since FMCB v1.9 was born, the FMCB installer has been used for installing both versions of FMCB (v1.8C and v1.9x).

                                    How to use this


  1. Download the archive linked to in the downloads section
  2. Extract the contents into one of these places:
    1. A USB device
    2. A CD/DVD
    3. A Memory Card (Not the memory card that FMCB will be installed to)
  3. Launch the installer with your Playstation 2 console
Option name Description
Install Performs a normal installation of FMCB
Multi-Install Performs a "multi" installation of FMCB. A multi-installation can boot on all consoles of any region, and not only on the console it was installed with.
Uninstall FMCB Removes a normal installation of FMCB from a memory card.
Uninstall MI Uninstalls a multi-installation, turning it back into a normal FMCB installation.
Format MC Formats a Memory Card.
Dump MC Dumps a Memory Card to an image installer's directory.
Restore MC Restores a Memory Card from an image located in the installer's directory.
Shutdown Switches off the Playstation 2 console.
Exit Exits the installer and returns back to the OSDSYS menu.

As of 2014/06/29, FMCB v1.8C will no longer be circulated from here as the FMCB v1.9 appears to have achieved proven stability.

                             Changelog for FMCB

Changelog for v1.951:
  1. Fixed USB device support; added 2s delay to the boot process + 10s timeout to the FMCB core.
  2. Updated code to work reliably with the PS2SDK.
  3. Added button hints to FSCK.
  4. Corrected flipped button processing (OK -> Quit) in FSCK.

                           Changelog for the installer

Changelog for v0.971:
  1. Added button legend.
  2. Once again, all files in the BOOT folder will be copied.
  3. Added a BOOT folder for the HDD (BOOT-HDD). Files in there will be copied to hdd0:__sysconf/FMCB.
  4. Removed unused file flag bits.
  5. Added new Portuguese, French and Spanish localizations.
  6. Button legend will be dynamically positioned, to cater for the varying lengths of labels in various languages.
  7. Users can now cancel at the memory card selection and installation type screens.

                                                             Known bugs

I think that I've fixed all of them by this release. :)
Known bugs:
  1. None!

                                                          Additional notes

I've spent slightly over a hundred hours working on this, and I hope that it works well.... but of course, anything could go wrong - so I have provided a memory card dumping and restoration facility within the installer.
A dump of a memory card in slot 1 will get saved as mc0.bin, and a dump of a card in slot 1 will get saved as mc1.bin.
The file will be saved to the directory where the main executable of this installer resides in.
Caution! You can only make one dump of a card from each port. Making additional dumps will overwrite the previous dump.

During development, I have sent 2 out of 3 of my cards to their graves and damaged the filesystems of all of them too. Thank goodness for the dumps that I made at the beginning of this project!
(I seriously don't know what's wrong with those damaged cards... they were hardly used and now they cannot be detected at all).

Supported installation media:
  • USB devices only

                       Warnings against potential pitfalls

!!! WARNING !!! If you make a multi-install, do not delete any of the B*EXEC-SYSTEM folders or any of the OSD*.elf files inside them!
Doing so might result in SEVERE data loss.
Do not delete uninstall.dat from the SYS-CONF folder either, or you will probably be stuck with the multi-install files forever.

Lastly, read the included README file for more details.

                                         Notes regarding the sources

The sources have been released. :) Check out the downloads section below.
Within the sources, I have created:
  1. SECRMAN, a clone of the Sony Security Manager (SECRMAN) module that has card-binding functions (SecrDownload*).
  2. SECRSIF, a clone of the Sony Security Manager SIF RPC server.
  3. MCTOOLS, a RPC server module that provided misceallenous functions for the memory cards like dumping and restoration, and filesystem manipulation.
  4. UDNL, the Updater module. Used for updating the IOP with newer modules (Which is only SECRMAN for this installer).
Hopefully, they will be useful for the homebrew community after their release.

                               Supported languages

For more information on supported languages and how support for languages can be completed, click here. A template for translating this software is provided in the downloads section of this page.


 Supported languages and their translation status

LanguageStatus
Japanese*     Unassigned
English    Completed and built-in.
French    Translated by ShaolinAssassin.
Spanish    Translated by ElPatas.   Original translation by pool7.
German    Translated by Delta_force.
Italian*    Translated by master991.
Dutch*    Translated by port187.
Portuguese    Translated by gledson999.
* Not updated for v0.97 (2016/01/09) and later.

Download & Source (via developer's official website):
ichiba.geocities.jp

PS2Indent - A PS2 model detection Tool by SP193

PlayStation 2 identification tool

Update 2016/05/21: v0.823 re-released.
Update 2016/01/04: v0.822 released.
Update 2015/08/29: v0.821 released.
Update 2015/06/21: v0.820 re-released. Corrected README file because I saw a CXD9686R.
Update 2015/05/30: v0.820 released.
Update 2014/10/19: Added a link to the PS2Ident database page.
Update 2014/10/13: v0.810R released.
Update 2013/10/14: v0.805 released.
Update 2013/08/25: v0.804 released.
Update 2013/07/26: v0.803 released.
Update 2013/07/18: v0.802 re-released - stability fix.
Update 2013/07/17: v0.802 released - labels update.
Update 2013/07/14: v0.801 released - minor bugfix.
Update 2013/07/11 03:19: Added a translation template.
Update 2013/07/11 02:09: Initial public release, with minor fix. Please re-download if you downloaded before I re-released it!

This PlayStation 2 Utility by developer SP193 is an identification tool that allows a user to dump the PS2 Console ROM chip and MECHACON NVRAM to be made. It will also gather data from the console, for research purposes.
It has the following features:
  • Dumps ROM chips (BOOT and DVD ROM) as a whole, not according to their contents (rom0, rom1, rom2 and erom)
  • Coloured user interface that is easy to use.
  • Supports dumping to memory cards and USB mass storage devices.
  • Supports multi-languages, which include the 8 supported languages by the PS2
  • Gathers data of all known parts of the PS2.
  • Attempts to automatically match the chip/part name with the version number of the part.
  • Supports all PlayStation 2 consoles, including the SCPH-10000 and SCPH-15000, and the PSX (DVR unit).
Note: Chip and mainboard identification is currently very incomplete and inaccurate, due to a lack of data. Sometimes, Sony makes hardware revisions without changing the chip implementation numbers as well, hence why chip identification may be inaccurate. The chip and version IDs are, however, accurate since they are taken directly from the hardware.
Its database, which contains the parts and mainboard data, is managed and updated with the PlayStation 2 Ident DataBase Management System (PS2IDBMS) tool. I made such a change because it wasn't possible to get a complete list of all PlayStation 2 models in existence. With PS2IDBMS, a spreadsheet containing all recorded models can be generated automatically.
Not to mention that the whole PS2Ident tool would have to be recompiled, whenever model data was added
 
Data recorded : If the database has your console's data in it, PS2Ident will attempt to determine its mainboard model based on:
ROMVER stringROM version string
Model nameThe "name" of the console's model.
EE revisionRevision of the EE chip.
FPU revisionRevision of the EE chip's FPU.
IOP revisionRevision of the IOP chip.
GS revisionRevision of the GS chip.
MECHACON revision and regionRevision and MagicGate region of the MECHACON
SPU2 revisionRevision of the sound processor.
SSBUS I/F revisionRevision of the SS-BUS I/F Controller.
Model IDUniquely identifies the console's model. Even more accurately than the model name.
Console model IDAnother (2-byte) version of the model ID. Obtained from the i.Link ID data.
EMCS IDUniquely identifies the Engineering, Manufacturing and Customer Services (EMCS) system that made the console.
M Renewal DateWhat this represents is unclear. It's something related to the MECHACON (date of firmware build or EEPROM settings update?)
ADD0x010An ID that is used by the SONY service tools to identify major revisions.
If your console is not recognized, its mainboard model will appear as "unknown". While it is true that Sony consoles might be physically similar across releases from different territories, I've decided to treat each region's release as being different because I would also want to have a complete list of existing PlayStation 2 models. With such data it is possible to determine what models Sony has released in every terrirory, and at which series did they start at.
 
How to submit new model data, starting from this release:

  1. If your console model is not recognized, its mainboard will appear as "unknown" and a new database record file in this naming convention will be generated among the dumped files: __database.bin (e.g. SCPH-10000_0500044_database.bin).
  2. Open your console, and take note of the mainboard model number. Take note of the models of all chips that were unrecognized by PS2Ident, so that we can get an updated chip model list for all components.
  3. Submit this file to me, along with the mainboard model and other missing chip models via e-mail.
  4. When recording down the model of the MECHACON chip, please take note that the model number should include its firmware version as well (e.g. CXP103049-401GG instead of just CXP1013049).
Please understand that the database record file alone is useless to me, since I need the mainboard model name to update the database with PS2IDBMS.
The model database file will be updated every week, or whenever I can commit to do so.
If your model is already recognized, the database record file will not be generated.

As for the chassis and EMCS ID (For Dragon-series units):
At the lower right-hand corner of the product information sticker that is either on the bottom or back of the unit, there will be something like "H FOXC". In this example, the letter 'H' is the chassis model, while "FOXC" stands for FOXConn (the EMCS that made the console). Please contribute this information if necessary.

Glossary/terms: Known parts of a PlayStation 2 console


EEThe Emotion Engine, which is a MIPS R5900. The "main CPU" of the PlayStation 2.
FPUThe VU0, which also acts as the 2nd coprocessor to the EE.
IOPThe I/O processor, which is a MIPS R3000A. The "sub-CPU" of the PlayStation 2. Although insignificant in power, it's actually in control of every part of the PS2, and provides access to the peripherals from the EE.
GSThe Graphics Synthesizer (aka the "GPU" of the PS2).
SPU2The Sound Processor. Also known as DEV4.
SSBUS I/FThe SS-BUS InterFace (I/F) Controller, provides an interface to the SS-BUS from the DEV9 expansion device. Also known as a "SSBUS buffer" on consoles sporting an expansion-bay.
MECHACONThe drive MECHAnics CONtroller.
DVPI'm not sure about this one, but it's a very powerful and smart processor that is connected directly to the MECHACON. Version data reported by the MECHACON includes data from the DVP as well.
Boot ROMThe ROM chip containing the default IOP modules, the OSDSYS program, PlayStation driver and the self-test facility (On the SCPH-18000 and up).
DVD ROMThe ROM chip containing the DVD player, and the Chinese font on Chinese PlayStation 2 consoles. Newer consoles may have a single chip instead of a separate boot and DVD ROM chips. The SCPH-10000 and SCPH-15000, and all TEST, TOOL and PSX (DVR unit) units do not have a DVD ROM chip. Also known as DEV1.
NVRAM/EEPROMThe Non-Volatile Memory storage that the MECHACON/DVP has, for storing settings (system, RTC and CD/DVD drive).
SPEEDThe expansion device that gets connected to the DEV9 expansion interface. May provide Ethernet support, a UART (for a dial-up modem), a DVRP, flash storage (For storing boot files), and an ATA interface.
SMAPThe PlayStation 2 Ethernet interface. Connected to the SPEED device.
Ethernet PHYThe PHYceiver device that is connected to the SMAP interface. The earliest models included a National Semiconductor DP83846A that has auto-negotiation issues with Gigabit Ethernet.
DVRPOnly found on PSX (DVR unit) consoles, the DVR Processor is a Fujitsu MB91302A that is connected to the SPEED device. It seems to be emulating the PS2's standard ATA interface and provides the DVR functionality. Contains its own firmware.
i.Link and USB interfacesThe Firewire/IEEE1394/i.Link interface and USB interfaces. Their controllers are built into the IOP. Consoles that don't have an i.Link port still have the i.Link controller, but just have no physical connections to the outside world.
AIFOn a DTL-T10000(H), the DEV9 interface is connected through the AIF. The AIF also provides a RTC and IDE controller.
MPUSee MRP.
MRP (BoardInf)The MRP is the interface between the PS2 and PC sides of a DTL-T10000(H). All DTL-T10000(H) units have a MPU 4.0 board as the MRP.
EMCS IDContains the part of the IEEE1394 EUI-64 address that uniquely identifies the console, the model ID and EMCS ID.
i.Link IDUniquely identifies the Engineering, Manufacturing and Customer Services (EMCS) system that made the console.
Model IDUniquely identifies the console's model. Even more accurately than the model name.
Console IDContains the EMCS ID, (another version of) model ID and serial number.
M Renewal DateWhat this represents is unclear. It's something related to the MECHACON (date of firmware build or EEPROM settings update?)
ADD0x010An ID that is used by the SONY service tools to identify major revisions. Originally at word 0x010 of the EEPROM, it was moved to word 0x01 for the Dragon models. It does not always correspond with the chassis models (i.e. C and D-chassis have the same ID). It can also identify the loadout of the console, like its CEX/DEX status and the OP block installed (i.e. SANYO or SONY).
Note: Slimline consoles that had the SSBUS I/F Controller integrated into the IOP will report their SSBUS I/F controllers as version 0x31 as well. Due to some controllers reporting the same version number (0x31), they will be all identified as a "CXD9611" since they are supposed to be fully compatible anyway.

LanguageStatus
Japanese*                        Unassigned
English (completed)                        Completed and built-in.
French*                        Translated by ShaolinAssassin.
Spanish (completed)                        Translated by ElPatas
German (completed)                        Translated by Delta_force.
Italian*                        Translated by master991.
Dutch*                        Translated by someone who wishes to remain anonymous.
Portuguese (completed)                        Translated by Gillbert.

* Not updated for v0.822 and newer.
 
Downloads & Source::/ichiba.geocities.jp
VIA  : http://www.psx-place.com

PS3 4.80 CFW CEX v1.00 by Team_Zer0

Bit later than expected.. but we all got a life right?
 Thx to the people for the requests!
Its nice people still follow our work.
The same for the
multiZer0 filemanagers!
4kgr9l.png

24c8wgh.png

2ly643s.png

Features:
  • 4.80-OFW Build in PUAD
  • SEN-PSN Acces + latest SEN (pkg) support
  • Added App_Home
  • Added PS3_GAME (to mount games from multiZer0 + more game support)
  • Integrated Package Manager (Thx for this idea to REBUG and FERROX)
  • Apllied patch - Lv1~Lv2 for Peek and Poke acces
  • (removed Lv2 security patch and cleared hashes)
  • Applied patch - Disable Cinavia
  • Applied patch Region free - BlueRayDisc
  • Applied patch Bypass RSOD (when updating after downgrade)
  • Installs over any CFW on CEX
  • [Updates straight over 3.55-OFW]
  • [When QA was toggled on previous install you're able to update with this pup]
  • [Added old PS3 2.60-OFW Coldboot into the pup (because i still like it (=]
  • **NEW Added Rainbow Waves to the XMB Menu
  • **NEW PS3 Coldboot Icon/Header added when booting
  • **NEW Latest 7.30 Cobra Support

MD5: 39162bf40e79e0cfaa14407553c4aa0f


Tested On:

CECH-H/J/K/L [Zer0]
CECH-21xxa [Zer0]
CECH-20xxa [Zer0]
CECH-20xxb [Zer0, Storm]
CECH-25xxa [B7U3 C50SS]

*Images got caught on vga.. so the coldboot/header will show up in full form when use hdmi.


Download:

4.80-CFW CEX-v1.00 Team_Zer0.7z 199.2 MB
https://mega.nz/#!I4kVQJZK!icI-lc_WQMwuCYOPodmAqP5xQ0ujPK35zEg0VI3nrY8 


Source : http://www.psxhax.com

Steam running on the PS4 (Video) – via Wololo


Steam running on the PS4 (Video)
Source: Wololo
This video went majorly unnoticed when it was initially published a month ago, but /talk member OsirisX pointed out earlier today that he has been able to run Steam on the PS4, with games running at reasonable framerates.
This is not SteamOS on PS4 yet, but it’s still Steam and its games running on your console.
In the video, OsirisX showcases game Bastion, running from Steam on the PS4, at a playable framerate (OsirisX states most games run fine with mid to low graphic settings).
This all works through a build of ARCH Linux. OsirisX gave the precision that he compiled and installed the 3D Drivers provided by Fail0verflow as part of their Linux PS4 project. (these drivers’ patches can be found here).
As for everything “Linux PS4” so far, in order to run this you’ll need to have a 1.76 PS4 for now, running a PS4 Jailbreak. Recent news indicate that the joy of Linux and hacks might come to PS4 3.50 in the near future, but nothing’s guaranteed at this point unless you have a 1.76 PS4.


This statement from OSirisX comes in the context of many PS4 users trying to get Ubuntu to run with hardware acceleration on the PS4. Running Linux on the PS4 has been a possibility for some time now, but there’s no “all in one” user friendly distrib yet that lets one run hardware acceleration or Steam. This might change soon. 
Follow the thread for details.

Source: YouTube & Wololo