[ Update 2 ] Cfw 4.40 Miralatijera Disponible

[the-green]

Merci lexou06, ceci complique encore les choses mais t'as un petite erreur !!

impossible d’installer un CFW 4.30 sur une console ayant un CFW 4.31 !! il faut un downgrader spécifique crée pour ça !

Le CFW MLT du hacker espagnol est un CFW 4.31, pas un 4.30 donc le CFW de Rogero ne passera pas dessus !! c'est pour ça qu'il faudra tenter d’installer un CFW 4.40 via le recovery( si ce dernier est toujours accessible) sinon c'est la galère !!

les CFW 4.40 sont faites à la base de l'OFW 4.40 et donc fonctionnent la dessus sans ce patch LV2 no check

pesro, j'ai pu installer le Rogero 4.30 sur le CFW 4.21 Rebug REX

j'ai pu facilement installer le CFW Rebug 4.30.1 REX directement depuis le XMB sur le CFW Roegro 4.30 v2.04...ça marche tant que la base du CFW est un OFW du même version ou plus

[lexou06]

oups oui ofw superieur a celi de rogero je sais bien

un cfw 4.40 no check j'en ai 1 de dispo pas encore mis en ligne par Rogero (je l'ai depuis 2 jours en test) ca devrait aller ,je peux pas lui filer non plus tu comprendds pourquoi ... ; je comprends ce que tu dis lol c'est la gestion du qaflasgs qui posent probleme sur ces cfw en 4.40 ,autant sur celui de Mirela que d'autres ( on va eviter celui de sgk pas un dev plutot du 'bricolage" dangeureux ...) c'est pour ca que j'ai proposé le rogero en 4.30 puisque le seul avec un patche Lv1

[pazara]

bonjour

non pas d’accès aux xmb

pas d'accès aux recovery système

console en mode factory mais impossible a drowngarder led vert clignote pendant une heure et toujour rien sa avec plussieur firnware ofw ou cfw

les seul fichier que j'ai peut récupérer c'est sa avant tout c'est problème

Avec CoreMultiTool v2.7.0

dumpDevflash /204544 ko /199mo

dumpDevflash2 /16384 ko /16mo

dumpDevflash3 /512 ko / 512ko

lv2dump /8192 ko / 8mo

nanddump /245504 ko / 239mo

Ps3lowlevelram /262144 ko / 259mo

mon modelle de ps3 et

02-27430373-3832361-

cechg04 3-275-774-01

date code 7C

comment je peut utiliser c'est fichier pour récupérer la console ps3

Modifié le 27 mars 2013 par pazara

[the-green]

oui certes il a le LV2 no check mais il ne passera pas !! du moins pas sans flasher hardware, il faut au préalable downgrader vers le 3.55

la solution c'est de remonter encore plus vers un CFW 4.40

[the-green]

Je ne sais pas comment l'utiliser mais essaye avec l'outil de Jaicrab MAD v3 mais je ne crois pas qu'il va marcher sur la version 4.31 !!

bref, ta solution c'est le flasher hardware !! espérant que ta nand est toujours intacte !!

[pazara]

BONJOUR

merci a vous tous

ps3

revenue a la vie

merci

Modifié le 27 mars 2013 par pazara

[the-green]

bullshits !!

c'est quoi cette histoire !!! c'est fini l'age des fakes sur la scène PS3

[lexou06]

lol la blague

[lexou06]

regarde ca c'est pour bientot par contre >>http://img94.imageshack.us/img94/1411/capturesoy.png

[pazara]

MERCI A TOUS je vous explique comment j'ai fait pour réparer la ps3

1 installation sur usb dossier pre3_01 jaicrab

merci a the-green

2 installation sur usb dossier ps3/upgrade mettre à la racine le fichier advanced.cfg , puis renommez le Lv2Diag.self à egea.self, créez le répertoire suivant PS3/UPGRADE/egea.self.

3 a la racine de usb mette vos dump ou nor allumer la ps3 attendre quelle s'etient tout seul allumer la ps3 pour aller en mode recovery et voila le mode apparaît et la ps3 ne s'éteint plus installation firmware ect tout marche pour moi

encore un grand merci a tous

[pazara]

bonjour a tous je viens de récupérer une ps3

elle s'allume mais en mode av je tombe sur un écran bleu

et en mode hdmi sur un écran rouge mais pas inscription

rien d’écrit que une image rouge je veux passer en mode recovery et la toujours écran rouge sens rien d’inscrire avez vous déjà vue sa et pouvez vous me dire si vous avez une solution

c'est ps3 était en cfw la personne a voulue installer un cfw d'une team que je ne connait pas voici l"e non

PS3UPDATCdEX-4.40.1-CFW_by_SGK

résultat sa ps3 et bloquer j'ai tester de mettre downgrader mais rien la ps3 reste allumer et rien se passe

[the-green]

Un autre update des CFW de ce hacker espagnol !

Update 2:
Startup animation as PS1 PSX full

• ReActPSN fixed (without copying or look or view of Rogero)
• Rif
  license bypass, ie now the console will not care that the content is
  purchased or not, meaning that on a console without rif's not act.dat or
  milk should boot all content without complaining (PS2 classics for
  example) but that will give blackscreen fix that patching the ps2netemu
  to use a static klic
• And a new way that I have called Dcex, basically recharge the system mode WITHOUT changing eid dex or do

to move it to the paraphernalia dex so if you ought to have enabled qa
flags are nothing more ... all in a safe and have our kind of debugger
to debug games and riding games manager network without any Works well within the pack

[deaphroat]

Merci mais c'est lourd l'espagnol

J'ai fait un changelog comme j'ai pu

[the-green]

D'après ce qu'on dit sur ce nouveau CFW, il permet de lancer les DLC sans aucune modification/ajout de type reactPSN !! ce qui représente une avancée majeure.

Jusqu'à maintenant, je n'ai ai trouvé aucun PUP préparé à partir des patchs de MiralTijera, si qq un a un lien vers le bon PUP qu'il me le passe via MP svp ! merci d'avance.

[deaphroat]

J'ai voulu mettre à jour les download j'ai pas tout trouve

C'est vraiment compliqué l'espagnole...

Légalement j'ai pas encore réussi à lancer mon jeu. Je testerais avec son custom et je te dirais.

[ARACHETOUS]

essaye un downgrader, essaye rogero 4.30 2.05

et sinon

essaye de lui passer un custom firmware de même niveau en factory (vu que la tu est en 4.31, ben il te reste ou le 4.40 de l'espagnol, ou le 4.31 arch (les 2 sont plus ou moins dangereux )...

Salut,

je suis désolé mais pas de danger avec mon CFW, aucun brick ressencé et téléchargé environ 3000 fois donc ça prouve ça stabilité. Après pour ceux qui est du CFW de l'espagnole, je sais pas.

Le seule qui est un danger pour les console c'est le SGK comme vous avez pu le constater sur un autre topic de votre site qui rapporte un brick et il n'est pas le seule d'ailleurs.

A bon entendeur,

++

[sephirothff]

hmmm, je vois d'un mauvais oeil ce genre de patch permettant d'installé n'importe quoi niveau contenu psn sans l'avoir payé...

[deaphroat]

UPDATE 3

Warning, this update if it is best instalais instaléis first previous ...

I copy and paste the post of Estwald because of what you put on I have nothing more to add ....

Estwald wrote:

First of all, Miralatijera me that if they "saw" made ​​public the Core in its name and the rest is of my own by collaborating

On the other hand, the uniqueness of this, is that just your CFW offers the ability to launch applications in the background and these things, show that when the CFW provide useful ideas and instead locked away, are offered the possibility the dev, they can do things and are more likely to do so. In contrast, others, think that by taking out a CFW automatically have to give support ... it will be no [poraki] : O you try hard enough and you provide the info or you worry your porting (I mean Iris Manager), as did Miralatijera (in 4.31 gave us all the information he could and at 4.40, made the port it, and I then managed some little things: well if you do things), because if not directly rule and I stand so quiet [burla2] .

And with that, let the matter:

The Core

The core novelty presents how the possibility of launching an application in the background, which is called "sm.self" and installed in root / dev_flash, which has advantages and disadvantages:

Disadvantages:

- If the application in the background hangs the system, obviously, the system will not advance from that point. So the flag is provided removesm to remove, but obviously, if someone puts nosearch flag, the result would be a semibrick (have to reinstall CFW). So careful with this.

- Access to the system is limited to exports of syscalls and basically liblv2.

- That the application is in the background, does not mean you do not eat resources, obviously

Advantages:

- The ability to control the temperature and fan without affecting other processes directly or maintaining "awake" USB devices tend to fall asleep, it seems a good start. The application runs on a separate plane to vsh.self, PSX emulator or PS3 game (obviously on the PS2 emulator, at least natively on the FATs, the LV2 ceases to exist and our application dies) and processes not stop LV2 how true alternatives.

The System Manager

The System Manager is how I called the application that will run in the background, basically consists of three separate parts:

1) The main: The main loop is enclosed in a 1 ms in duration to receive commands via address 0x450 of LV2 with which to configure the application (you can set the thread priorities, changing temperature tables, and mode time device activation and get some additional information)

2) FanCtrl_Thread: basically, this thread does the same as the payload that I developed for Fan Control Utility (Incidentally, the application has been updated to the 1.5 to work with this without problems )

hilo_utilidad-control-fan-utility-v1-5-cfw-cex-3-41-3-55-4-21-4-30-4-31-and-4-40_1893851

The advantage is that unlike the payload, this does not affect directly the processes, so that should not happen reporting problems some users of the application. Basically, this is how I would have liked me to do from the beginning, but until now, there was no way.

Added a small payload that is housed in the direction of LV2 0xF70, like Fan Control Utility, but only to protect the syscalls sm_shutdown and provide compatibility with the previous system, so that it can be integrated in Iris Manager support.

3) UsbWakeup_Thread: This thread has 3 running modes and basically deals with "wake up" USB devices that tend to "sleep" for lack of use, causing problems in games.

The wake mode is to write in a file called "nosleep" we can create in root of the device (no matter that has length 0, just exists or not) for the SM know or not to use units. By default, it does every minute, but you can program steps of 10 seconds (2560 seconds maximum, to which we must add two seconds for the indicator).

USB storage devices, can be divided into hard drives and flash memory devices that are not as convenient to be writing all the time. This is the reason that is delegated to the user to create "nosleep". Indeed, in some games, you must set BD Emu and that makes the USB pass renamed as / dev_bdvd, which also supported.

The three modes are: 0 -> disabled, 1 -> enabled for a single device and 2 -> enabled for all devices (this is the default)

Default operation (autonomous)

Just load the SM, the settings are:

- Temperature control / fan Fan Control Utility equivalent asset.

- Wakeup writing on all devices, including / dev_bdvd (if a USB device allow writing) on, proceeding to write 1 time every minute or so. Obviously, writing only affects those devices with the file "nosleep" (elsewhere, could detect read access as much)

The LEDs indicate the following:

- Yellow Led Fixed: temperature below 70 degrees
- Led yellow / green flashing temperature above or equal to 70 degrees
- Led red / yellow / green flashing temperature above or equal to 75 degrees

- Green LED remained two seconds every 10: led activity

- Leds off for two seconds: indicate a write access to USB device. This is important to know, because we should not unplug a USB device in a deed, obviously (we wait for the LED to turn off and unplug a few seconds later)

External Control Support

Fan Control Utility 1.5:

hilo_utilidad-control-fan-utility-v1-5-cfw-cex-3-41-3-55-4-21-4-30-4-31-and-4-40_1893851

And soon, Iris Manager:
hilo_aplicacion-iris-manager-v2-36p_1862716_s820

Installation and Use

If you have the flag "nosearch" active, unset. Copy the Core (sys_init_osd.self) and root sm.self in a pendrive and expects the restarts (for many, to install the core and then to install the system manager)

If you want to uninstall sm.self then adds the flag "removesm"

If you want to prevent a USB device "sleep" create a file "nosleep" in root of the device (whether measured 0 bytes)

UPDATE 4

another update from Estwald:-D

What's new:

- There have been some corrections of time to avoid excessive delays when changing the mode of operation for the Fan and USB Wakeup.

- Priorities have been reduced to a minimum to try and stop the System Manager as little as possible to other processes running and only use their downtime.

- Added the ability to change a priority and update time main () (this used to be able to tinker with things, if necessary, but in principle it should count as is)

Installation:

- If you already have the previous version, simply copy sm.self in USB root, put it in USB000 (closest to the reader) and reboot.

- If you have the core 3.2.0 following the instructions, replaces the old sm.self by the new

Uninstalling:

- Copy the folder "flags" is inside the RAR to the device and restart with it plugged in USB000

USB Wakeup:

- Create a file called "nosleep" (no extension, which I already see it coming XD ) In root of the device you wish that every so often, are accessed by writing to keep alert

-------------------------------------

Psmaniaco wrote: Estwald a question, in your Iris Manager I think you added the temperatures of Cell and RSX right?
Are the temperatures of the sensors you mentioned further back?
A greeting.

If

put another application in the background

Yes and no. For starters, you can only be accessed through syscalls or liblv2 exportable functions in PSL1GHT. Make them the idea that this is pre-vsh.self and operates completely autonomously. Also, you need a series of special construction flags or not work (which I include in the Makefile to scetool).

If not done well, the best thing you can get, is to ignore your application XD

By the way and for that matter, if you delete the sm.self you can do it directly (root is / dev_flash and just mount it in writing) or otherwise, add the flag "removesm" to do it for the core you: no need to remove the core.

And by the way, a recommendation mine: NEVER put no root any files that could be copied by the core unless it is that what you want: if you put a vsh.self in root, for example, automatically copies and going to care if it's a different version. So very careful with that, it can cause a semibrick XD