Logic-Sunrise : actualités, téléchargements, releases, dossiers et tutoriaux

Suite à une interview accordée par theverge.com, Phil Molyneux annonce officiellement que la PS4 lira bien les films au format 4K, disponibles via leur future plate-forme de téléchargement. Pour information, la PS4 sera équipée d'HDMI 1.4b, qui permet la diffusion de contenu d'une telle résolution (4096px par 2160px), mais avec certaines limites. Il est par exemple impossible avec cette version d'HDMI de monter au dessus de 30 images seconde dans cette résolution. C'est pourquoi la lecture est possible pour des films, mais pas pour les jeux ou la 3D. Les consoles même next next gen ne seront de toute façon pas assez puissantes pour une telle puissance de calcul.

L'autre annonce vient de la taille des fichiers. Toujours selon Phil, les films pourraient atteindre 100Gb en poids, ce qui peut représenter une semaine de téléchargement pour une connection ADSL classique. Le soucis du 4K est visiblement son avance sur le temps, les téléviseurs n'étant même pas encore équipés de norme correcte HDMI, et son remplaçant (l'HDMI 2 ?) n'est pas encore annoncé.

Né d'une forte demande de la communauté, BwE NOR Validator est destiné à confirmer la validité de dumps NOR pour par la suite les patcher en firmware 3.55. Ce projet a été démarré il y a peine deux semaines et se trouve être plutôt ambitieux car mettre au point un programme performant de vérification de dumps PS3 n'est pas aisé. Le développeur australien qui en est à l'origine, BwE, semble pourtant avoir réussi son pari.

Les anciennes versions donnaient en effet plutôt de bons résultats mais l'amélioration ne s'arrête pas pour autant. Une nouvelle version 1.08 vient d'être mise en ligne, ajoutant ainsi de nouvelles vérifications et corrigeant inévitablement à ce stade du projet des bugs. Seules les NOR sont actuellement supportées, les NAND seront prises en charge dans un autre programme.
 
Gardez toutefois en tête qu'aucune application ne permet pas de valider avec un taux d'erreur nul un dump ! BwE NOR Validator peut donc vous indiquer qu'un dump est valide alors qu'il ne l'est pas, ou inversement. La meilleure solution restera dans tous les cas de faire les vérifications à la main avant de flasher un dump qui pourrait être invalide. Pour cela, aidez-vous de cette page du PS3Devwiki.
 
Utilisation :
 

- Place your .bin/s in the same folder as the validator.

- Run the validator and press Start.

- A console will appear asking you to select your dump (if you have more than one in the folder).

- Make your selection and or select if you watch to patch it (either in its current byte orientation or the opposite).

- Wait patiently.

- Press Enter at the end to launch the output. 

Changelog :

- 1.08 - 29/02/2013 : added timeout for version check + added 16bit corrupt sequence check + fixed long outputs + fixed metldr ident bug + changed some warning/danger results + changed 00/ff results
- 1.06 - 27/02/2013 : fixed bug when handling old coreos versions + fixed .self md5 list
- 1.05 - 25/02/2013 : added approx 220 more validations + changed statistic ranges + latest version check + fixes to metldr/bootldr
- 1.02 - 22/02/2013 : more md5's & authid checks + changed some results.
- 1.01 - 16/02/2013 : authid check bugfix
- 1.00 - 15/02/2013 : first public release

Télécharger BwE NOR Validator 1.08

Les mises à jour de Multiman s'égrènent inexorablement et l'infatigable Dean nous fait profiter aujourd'hui de la version 04.20.01 de son fer de lance : le populaire Multiman. Ce loader, désormais devenu un incontournable pour les possesseurs de PS3 hackées, a pour fonction principale de vous permettre de lancer vos backups de jeux PS3. Il présente une compatibilité avec un large éventail de titres, pour ne pas dire tous. Leur affichage dans l'homebrew est très soigné et esthétique et surtout peut se faire de différentes façons. Vous pourrez ainsi choisir entre un style coverflow à la WiiFlow ou encore un style plus simpliste sous forme de liste.
 
Outre tout cela, Multiman est doté de nombreuses autres fonctions. Un explorateur de fichiers pour réaliser des transferts de fichiers entre disques durs est disponible ainsi qu'un client FTP pour permettre des copies grâce au protocole FTP. Enfin, Multiman, c'est aussi le lancement de tous les formats de vidéo grâce à son association au lecteur vidéo Showtime, la possibilité de profiter des jeux "rétros" mais aussi des jeux PS1 à l'aide des émulateurs intégrés, et bien plus encore !
 
Cette version de Multiman est une version UPDATE. Aussi, il est nécessaire que vous ayez préalablement installé les versions BASE ou FULL de Multiman 04.20.00.
 
Mises à jour de la version 04.20.03 :
 

multiMAN 04.20.03 update is available online and in the WEB column.

multiMAN ver 04.20.03 UPD (20130303).zip (7.97MB)
Download multiMAN ver 04.20.03 UPD (20130303).zip from Sendspace.com - send big files the easy way

* Added DynaRec support: New option in Settings "Enable DYNAREC"
* DYNAREC support for 3.55CEX/DEX, 4.21CEX/DEX, 4.30CEX/DEX, 4.31CEX
* Fixed few minor issues in 4x2 and 8x4 modes (refreshing the game title when insert/ejecting a PS3 game disc)
* Fixed a very rare bug in mmOS when icon names/texts are getting corrupted

=============================================

* You can install it on any mM supported firmware (3.55CEX/DEX, 4.21CEX/DEX, 4.30CEX/DEX, 4.31CEX)
* The configuration file is USRDIR/CF.ini
* Comes with bios and all paths set properly where the default ROM path is /dev_hdd0/PSXISO
* EBOOT.BIN calls RELOAD.SELF so you can boot PS3SX directly from multiMAN
* It has VERY POOR compatibility but shows that dynarec is working on all firmwares.

You can enable DynaRec in mM's settings and directly load PS3SX from mM's GAME column. Thanks to aldostools for the cover. Developers can use this dynarec option in mM if they wish to test their apps in this environment.

The implementation in mM is different than IngPereira's approach, because it doesn't use the 0x700000 area for the payload and the patches, there are no issues with PKG files and works on all firmwares. Still the kammy data for the hvsc redirections is used, but dynarec's usage is greatly simplified by an "On/Off" option in mM.

Après Gears of War Judgement, ou d'autres gros titres, c'est au tour du très attendu Tomb Raider dont l'incontournable vedette est Lara Croft, d'être leaké sur le net avec 10 jours d'avance. Plusieurs noms de releases sont disponibles comme Tomb.Raider.PAL-NTSC.XBOX360-P2P ou tr-p2p, mais la source vient visiblement des réseaux P2P plutôt que de gros groupes de la scène.

Bien évidemment, nous vous rappelons que la demande et la publication de liens pour la télécharger ne sont pas tolérées sur Logic Sunrise.

LS vous recommande fortement de ne pas jouer en ligne avant la date de sortie pour éviter tout risque de ban !
 

BlaKCat propose sa nouvelle version d'AutoGG : 0.8.8, et pas n'importe laquelle : il est désormais possible à partir de n'importe quelle console, même les Corona V2, 3 ou 4, de mettre à jour votre dash en un simple clic ! Cette version apporte le support de la mise à jour de Microsoft 16203.

Il vous faudra pour cela une console JTAG ou RGH, une connexion LAN, AutoGG 0.8.8 et enfin FSD. D'un simple clic sur un bouton, votre nand va donc se mettre à jour dans sa dernière version de manière automatique. Plus besoin de passer par un dump de nand et un patch manuel.
 

- New Dash 16203
- New Xebuild 1.07
- New DashLaunch 3.07
- Option de Erase Corona 4g Nand
- Code Improved.

Télécharger AutoGG 0.8.8

Alors que DeanK travaille d'arrache pied sur son manager, MultiMan, Estwald (Hermes) & D_Skywalk de leur côté ont bien décidé d'améliorer le manager à la base développé par Hermes : Iris Manager. Certes moins complet que MultiMan à l'heure actuelle, Iris Manager s'améliore tout de même plutôt rapidement.

Au menu de cette mise à jour, on retrouve la correction de bugs, l'affectation de nouvelles fonctions à quelques touches, l'ajout de libnet et d'autres changements.

- New payload v8 syscall eliminating the syscall 36 and used instead to 8 redirections. The syscall 8 works in a hidden in applications, thus respecting the other use that gives the syscall 8 in certain firmwares (LV1 Peek)
- Added Multiman method for disc-less from / APP_HOME (thanks for commenting DeanK how it works). This increases the compatibility.
- Added patched explore_plugin.sprx method to launch the games from road / dev_bdvd when selecting / app_home/PS3_GAME. This method connects when “No Controller BDVD” and requires that each CFW patched module (see explore_plugin_notes.txt within patch_tools_libfs_exploreplugin.rar). Grid is a game thus far.
- Fixed all (fucking) problems and other productions, as authentication based disks using CFW 3.41, 3.55, 4.21 and 4.31 (yes, I’ve been to them all)
- Now HDD0 mounts are safer, both for the method how it can be accessed only “/ dev_bdvd” in reading.
- Added ability to restart by pressing TRIANGLE on the main screen
- Iris Manager now works in two ways, thinking about those who have BDVD operational unit and the voiceless.
- New homelaunc1 (must install because the former will not work)
- This is a summary of the disk operating modes:

Available options:

Requires Disco:

- With controller, disk not only asks “Yes” if no blocking routes / APP_HOME. This may prevent it from interfering with games.
- No Controller: obviously hard but never require it to “No” will be provided / APP_HOME (some games with trophies bug report, if this option is set to no). For riding HDD0 is protected.

*********
* 2.09 *
*********
- Fixed: Changed the option word « videomode » to the correct one « avregion » my bad…
- Updated: Now using xeBuild 1.07
- Updated: Now using Dashlaunch 3.07
- Updated: Now building 2.0.16203.0

V3.07
- added 16203
- hopefully all cpu/dvd keys will display fully in installer now
- fix description spelling error (F/C)

Dash Launch 3.07
----------------

Known Issues:
----------------

- *** WARNING ***
One of the testers observed a console reaching out to live despite liveblock only
when fakelive or autofake was enabled. If you intend a keyvault to not get banned,
do not use it on a glitch/jtag machine!
- Autologin popup blob does not display properly... live with it.

Currently the project is missing the following supported translations:
Japanese, Korean, Chinese Simplified, Chinese traditional

Currently supplied translations:
English, French, Portugese, Russian, Spanish, German, Italian, Polish

The skin pack includes the sources used to skin dash launch as well as the
string files if anyone wishes to create a translation to one of the above
languages (inlcuding English, as I know my explanations are not always easy to
understand.) Also included is a c# based editor for the string files to assist
in translation.

External fonts, background image and skins may be used by this,
simply place skin.xzp and/or font.ttf and/or background.png (1020x720) beside
default.xex. If neither location has a font file supplied the system font
on flash will be used.

Welcome to The Next Level

****
at time of this writing, this is ONLY compatible with RETAIL kernel versions:
jtag : 9199, 12611, 12625, 13146, 13599, 13604, 14699, 14717, 14719, 15574, 16197, 16202
glitch : 13599, 13604, 14699, 14717, 14719, 15574, 16197, 16202
glitch2: 14717, 14719, 15574, 16197, 16202
****

================================================================================
Overview - what it does
================================================================================
- It will launch a XeX or CON file from the path you specified in launch.ini
as long as it's valid
- Depending on the button you hold when the xbox is trying to load the NXE, it
will divert to the xex/con tied to that button or return to default as
defined in launch.ini
- At boot time it is possible to subvert default item and/or NXE loading, but
you must wait until the controller syncs to do so
- Depending which button is held when closing miniblade in NXE (use Y button to
close, release then hold a QL button) it will quick launch a CON or XEX
from your ini file
- allows one to patch kernel/xam at bootup with a freeBOOT patch style bin file
from usb or hdd (in that order) must be in root of the device and be named
"kxam.patch" and be no larger than 0x4000 bytes. Again, kxam.patch binary
format is the same as a compiled freeboot patch bin, but uses real virtual
addresses rather than offsets - as of 2.22 the first 32bit value must instead
be the version of the kernel the patches apply to
- with the included patch set, launch.xex acts as a helper to detect when
xbox1 emulator loads, allowing memory unlock patch and xbox1 emulator
to function together

================================================================================
Installation
================================================================================
- have the required hacked kernel version installed on the console

- get the installer to a place where you can run it, and do so. Follow onscreen
instructions if any. The installer will prompt you if it needs to update the
kernel/hv patches and will give you an opportunity to configure stuff.

- edit the options, and dont forget to save them somewhere if you want them to
be applied next boot. Don't forget to set configapp to the installer, so
you can go to it any time via miniblades' system settings (hold RB to go to
real system settings)

- the back button is your friend if you are wondering what button to push

================================================================================
Updaters and Avatars
================================================================================
- this version of dash launch contains an update blocker that is enabled by
default. There are two ways around this if you wish to install the bits and
pieces used by the dash for kinect and avatars
1 - place the updater that matches this version on removable media, and
rename the folder from $SystemUpdate to $$ystemUpdate
----OR----
2 - place an ini where dash launch can find it and set the noupdater option
to false - noupdater = false
Updates seem to work best if memory stick is inserted while in official dash
****
NOTE that some games WILL prompt you to update the console if avatars are
not installed, this doesn't mean they have an update to actually put in, it
just means it needs avatar/kinect bins/resources to run
****

================================================================================
LIVEblocker
================================================================================
- if you are like me, and keep your consoles off the net then this option is
for you. It's capable of blocking the resolution of the LIVE specific
servers and does so by default, with an additional option in the ini file
it will attempt to block access to all MS servers. The default option is
set up to block only LIVE servers, which still allows programs like FSD to
access covers and such. The blocks lists are:

weak:
^xemacs.xboxlive.com$
^xeas.xboxlive.com$
^xetgs.xboxlive.com$
^xexds.xboxlive.com$
^piflc.xboxlive.com$
^siflc.xboxlive.com$
^msac.xboxlive.com$
^xlink.xboxlive.com$
^xuacs.xboxlive.com$
^sts.xboxlive.com$
^xam.xboxlive.com$
^notice.xbox.com$
^macs.xbox.com$
^rad.msn.com$
passport.net$

strong:
xboxlive.com$
xbox.com$
nsatc.net$
microsoft.com$
passport.net$
bing.net$
msn.com$

where:
somedomain.com$ = ends with somedomain.com
^somesub.somedomain = starts with somesub.somedomain
^somesub.somedomain.com$ = is exactly somesub.somedomain.com

================================================================================
Important - going to NXE
================================================================================
- if you need to go back to NXE and have default item set in ini, HOLD RB while
exiting game via miniblade or exit using one of the miniblade options like
family settings

================================================================================
INI notes
================================================================================
-it's possible to have multiple ini files, priority is as they appear in the list
(** it is NOT recommended to launch USB con/xex from hdd ini **)
the first one found on the devices in that order will be the one used at boot.
-see http://code.jellycan.com/simpleini/ for more info on the ini parser

================================================================================
autoswap option functionality
================================================================================
GOD ie1:
disk1 = Hdd:\Content\0000000000000000\01234567\00004000\01234567890123456789;
will have 01234567890123456789.data folder beside it
disk2 = Hdd:\Content\0000000000000000\01234567\00004000\98765432109876543210;
will have 98765432109876543210.data folder beside it
EXTRACTED ie:
disk1 = Hdd:\games\somegame\disk1\default.xex;
disk2 = Hdd:\games\somegame\disk2\default.xex;
- GOD/NXE disk rips on the same media in the same folder will automatically
be found with no special naming convention
- EXTRACTED games with the naming above for each disk with the disk# folders all in
the same folder on the same media will be found without an ini file
- swapping between disks contained on different media is not supported

================================================================================
Caveats
================================================================================
The work herein is presented as-is, any risk is solely the end users
responsibility. While all of us are sorry when unforseen things happen, not
every situation or mistake can be accounted for before they have been
spotted. Please use responsibly.

xeBuild 1.07
============


Introduction:
=============
xeBuild is a command line system image builder for JTAG, glitch, and clean images.
Run the xeBuild program with no (or incorrect) args to see it's useage info.


What's New:
===========
- minor bug fixes
- add 16203


Current Limitations:
====================
- STAY THE HELL OFF LIVE! Nuff said, we're not you're mum.


How To Use:
===========
- See individual folders for lists of files to provide
- if desired provide replacement cpu and 1bl keys in text files
- open a command window in the xeBuild directory
- on the command line type, for example:

example - if you provided keys in appropriate text files

xeBuild.exe -t glitch -c falcon -d myfalcon myfalconout.bin

-t glitch = build a glitch type image
-c falcon = use falcon bl and patch set
-d myfalcon = a folder is present called "myfalcon" with per machine files, this uses it
myfalconout.bin = the file that will be produced

- type xeBuild.exe -? for command line info


Example:
========
-take original console dump, put it in mytrinity folder as nanddump.bin
-set CPU key and 1BL key in ini file, verify LDV from nanddump.bin matches console fuses
if not set cfldv in ini file
-build (xeBuild.exe -t glitch -d mytrinity -f 13599), flash and hopefully life is good


.ini files:
===========
Just a word on the format... the ini parser is not very robust, the files need
to be plain ASCII, everything after a ; on a line is ignored, and spaces are
not acceptable (they get removed).

Things like CPU key and 1BL key, if present in the per box ini file need not be
placed anywhere else.


Optional Patches:
=================
Various optional patches are included for use with the -a option, they are:
nofcrt - removes fcrt.bin requirement on some drives
nohdd - disables detection of internal SATA HDD
nohdmiwait - HDMI consoles will no longer wait or EXX screen when video is not ready
nomu - disables detection of jasper big block NAND mu
notrinmu - disables detection of trinity 4G internal USB module


Note:
=====
- DON'T USE THIS UNLESS YOU KNOW FOR SURE THAT YOU NEED IT! Using an incorrect
controller config can result in problems remapping bad blocks (even manually.)
If you have a 16M jasper, an additional build type has been added
'jaspersb', by default the image will be built for jasper with big block
controller (config 00023010), use this alternate switch to build for small
block controller (config 01198010.)


Multi build/options example:
============================
when you specify -f 13599 on the command line:
13599\filelist.ini
is parsed instead of data\filelist.ini

Also the bin directory is used from
13599\bin\
instead of
bin\
allowing anyone to create multiple builds without multiple instances or
rebuilds/hex edits/hacks of the main app.

The example provided is the last version of 13599 patch set from dash launch and
other files to build freeboot 13599

example use:
------------
xeBuild -f 13599 -d myfalcon x13599out.bin

-f 13599 : use .\13599\filelist.ini, and .\13599\ for firmware files, .\13599\bin\ for patches
-d myfalcon : use .\myfalcon for per build files (cpu key, keyvault, security files, ini etc.)
x13599out.bin: override auto generated name and produce .\x13599out.bin as the final NAND image

note, if -d ***** is not specified it will still use the original /data and /bin dirs


Devkit image building:
======================
This feature is currently considered Beta/Work In Progess.

A new image target type was added, "-t devkit" which builds 64M flash images for devkits. Currently untested,
building with a 00 filled CPU key will create a zeropaired devkit image that may allow one to boot a software
bricked devkit that one does not know the CPU key for and recover it to an operational state. By powering on
the console with such an image present, with a recovery DVD in the drive, the recovery software should be able
to create a new keyvault, re-pair the DVD drive to the new keyvault, and allow normal operation once complete.

Normal devkit image building when one does know their CPU key and thus has security files and keyvault should
work as expected.

Building devkit for glitch/jtag is also possible using the standard -t glitch/jtag methods. Sample ini
have been provided with this release, but will not work unless patches and files are supplied. Note that devkit
is not our focus, but was relatively easy and straight forward option to supply for those that wish to make
use of it.


jasperbigffs:
=============
Those who use large block NAND are now able to nearly double the size of the system file area
with this option with no apparent ill effects. Normally this option wouldn't be needed, but if one
wanted to experiment with more files in flash, or one was building a devkit image for a devkit with
a big block flash, this option is required.

support:
========
If you've found a bug or have a suggestion, please comment at
http://www.realmodsc...rum/15-xebuild/ (english)
http://homebrew-conn...x.php?board=8.0 (english/french)

Credits:
========
Without ikari this would not have been possible, thanks!
__ ____ ___ ___ _____
/ _|_ __ ___ ___| __ ) / _ \ / _ \_ _|
| |_| '__/ _ \/ _ \ _ \| | | | | | || |
| _| | | __/ __/ |_) | |_| | |_| || |
|_| |_| \___|\___|____/ \___/ \___/ |_|
[v0.08 - inspired by ikari]
R.I.P.
No this isn't freeboot, it is a clone and has always been since the last
release of ibuild.

Thanks and greetz to everyone who has contributed to hacking this
wonderful machine. Thanks to the engineers and countless others who made
the machine what it is... we only wish they had listened and RROD was
not a problem. If we were to list everyone here, there would be no time
left to play on the machine!

Thanks Team Xecuter for the Corona 4G! Thanks to JuggaHax, dayton360mods,
glitch360team and all other contributors for helping find a way to make Corona 4G golden!

Thanks to Free60, LibXenon.org, Redline99 and Tuxuser for providing xell builds <3

Thanks to Swizzy for making the official GUI front end for xeBuild, for always
adding the new stuff we shovel at him and never once complaining.

Big thanks to the folks at #freeboot on efnet for the tireless
hours of help you all give freely. Thanks to the testers who tirelessly
made sure stuff worked. Thanks to rgloader for doing the work yourselves,
there *is* no spoon, just a glitch in the matrix.

Don't believe what random people *cough* write on forums ..

So if someone buys a PlayStation 4 game, I asked, you're not going to stop them reselling it?

"Aaaah," was Yoshida's initial answer, but seemingly only because he'd forgotten his line. "So what was our official answer to our internal question?" he asked his Japanese PR advisor. The advisor stepped in but didn't seem to answer clearly, at least to my ears. Yoshida then took control again firmly:

"So, used games can play on PS4. How is that?"

I said I thought that was fine.