102w ago - This holiday weekend Spanish PlayStation 3 developer JaicraB has released PS3 Preloader Advance, a rewritten LV2Diag.self that allows restoring the Dev_Flash.bin file (to fix semi-bricked PS3 consoles) and has been tested on JFW DH CFW although it should work on all Custom Firmware he states.
To quote, roughly translated: Already available the tool to reset any "/ dev_flash". It is but a program that runs without external modules.
Why we find it being unable to load basic libraries housed in the "/ dev_flash" we must use direct syscalls to the kernel. The compilation is clean STUB external modules, hence it only takes a few KB ...
The function is to load the file "/ dev_usb000/flash1.bin" and write in RAW mode to the "/ dev_flash". But not before mounting the "/ dev_flash" Write mode.
It's simple but effective. There are dangers of bricks, but backup mistake or left unfinished for various reasons.
In principle works in all FIRMS, but mainly is designed to JFW-DH356MA by semibricks problems and instead of HDD when the system stored inside the "/ dev_flash".
But you have backups you can ask of anyone with the same firm or even removing it from the pup and mounting it on a FAT system. Its use is simple.
In Factory Mode to rename the "Preloader Advance.self" a "Lv2Diag.self" and copy it to USB.
Within the USB copy at the root of the flash backup named "flash0.bin"
Connect the USB into the port nearest the reader, and on the system. The LED blinks green. It means that restoring the flash.
When the process is shut down. Check the log it creates on the USB to be sure.
It only plays out of the factory mode with the "Lv2Diag.self" step2 flowing through the network.
For more information use and addressed to: www.demonhades.org
MxxxS, My great teacher
Lara, to change and let me sleep at night tinkering...
Demonhades by bud
And the community of demons.
Happy Holidays to all.
PS3 Preloader Advance 2
Bring Preloader version 2 of the Advance.
Configuration file to select the actions.
Restore all flashes.
Make backups of all the flashes.
Optimization of the code.
Auto-Exit Service mode.
Be in Service Mode.
Copy and advance.cfg Lv2Diag.self-in USB
Modify the file to taste advance.cfg
Insert the usb backups according to the advance.cfg
Switch with USB-introduced into the nearest port to the reader.
CORE- While this well and allow access to the Service mode, this utility will recover all the flash. The change of HDD in a 3.56 version is not a problem on systems with NOR memories. No need to do an UPDATE THROUGH. Good luck!
Good friends demons, the wait has been tedious and frustrating, so jaicrab wants us this gift to the community to wish a Merry Christmas to all those you had a semibrick with the installation of the JMB or a bad installation in the flash.
1. Prepare our dongle to put it in service mode (I used my amazebreak, but it any other apparatus to use the downgrader payload). Then enter the port and do the combo usb000 power and eject, will turn itself off the PS3.
2. Download the JFW-DH 3.56 MA 1.2.1 Service Pack
3. Download of demonisos.net and rename it to flash0.bin
4. Place in the root of the pendrive (flash0.bin), and also put in the root renamed the advance preloader Lv2Diag.self
5. Introduce the stick in the port usb000 (closest to the reader) and turn on the console.
6. The LED will blink green while working on the restoration, when finished will go out alone.
7. For get into the root end of the usb Lv2Diag.self used to exit the service mode (finalized).
8. Ya again have our PS3 alive with the JFW-DH 3.56 MA.
No more, now you can have it back running the PS3 and not afraid to mess up, this system is tested in fat60 (I have bricked mine) and I have it again making war, is valid for any model although format the hdd.
And without further, 1saludo departed JaiCraB MERRY CHRISTMAS and all the demons DemonHades and friends
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!
very very nice... really thinking about changing to irismanager.... i think deank could do this a long time ago in multiman... but hes with teamcobra... so he want to make money... NOW he have to do it...
mm is great... it can do alot of stuff... but i really only use it for ftp, filemanager and to create xmb mount pkgs via last game...
i think its no problem to find a alternative ftp and filemanager... there are homebrew stuff for this... so the only important reason for me to use mm is to create xmb mount pkgs via load last game pkg...
if iris manager would have a function like last game... i would change really quick!!!! because i like it simple! and most of futures in mm are useless for me!!
next big thing i hope will be psp backups via irismanager... i really like this dude!!
btw is load last game working with irismanager??? i didnt tested yet!?
Following up on his revisions, today Spanish PlayStation 3 developer Estwald has updated the Iris Manager PS3 game backup manager to version 1.50 followed by v1.50.1, v1.50.2, v1.50.5, v1.50.6, v1.51, v1.52, v1.52.1, and v1.53 with the changes detailed below.
To quote, roughly translated: Well, if you do not mind, I go up and this and that people will test: your upload yours and let me know when (that can be downloaded without using git!) And I add anything new at no cost to you (if you want to take an eye for entertainment, do it ).
I've gotten notes, anyway (I played the payloads also, by the way, to add code if LV2 patches fail because the instruction cache, as seems to be happening at 3.55 in the case of black screen)
Ability to run PSX ISO
IMPORTANT extract psx iso.txt:
As added PSX isos for Iris Manager 1.50 +
Create a folder in root PSXGAMES or USB HDD
Put the PSX game folder inside. The folder name is used as the name of the game in Iris Manager.
The PSX games should be files. Bin or. Img (or. BIN,. IMG) contend sectors of 2352 bytes. You can get from 1-8 files "iso"
Iris Manager takes the isos in alphanumeric order. When you throw a game with multiple isos you can rotate the screen in order
the last moment.
You can put a cover.jpg file (maximum size 1024 x 1024 pixels)
PSX config is saved in the game folder.
Iris Manager mounts USB / BDVD and HDD0 in that order of preference to change the hard disk virtually. If a device can be mounted
It is used to simulate EJECT / PUT.
If a game has two or more discs when the game asks for a disk change, unplug and plug the USB device or disc ejects and hits CD / DVD / BR to change the "iso" (to be ax when your "ejecta" LED flashes green when you put a "new" medium green LED does not blink). The method is rotating so when using the latest iso it will change to the first iso)
NOTE: You can use a BR disc without problems PSX Emu patched. It is not necessary to eject the disc to play.
The configuration of each game is saved in your contacts, while the PSX game disc, is taken as reference for the games you have not saved the configuraracion there.
As I discuss the order they are taken multiple ISOS is alphanumeric (will 1.bin 2.bin Disc 1 and Disc 2 as)
When demos to run, if there are several, are presented with a screen that shows the order of the iso, but that makes pressing CIRCLE rotate upwards (so for example, if we are playing disc 2, you can select Start)
As I comment if you can mount a USB device is taken as "eject" first, otherwise a possible CD / DVD / BR that can be mounted and ultimately the HDD (so you can not eject). This makes it possible that if we have a game on the internal PSX with a pendrive connected and we disconnect and connect back to be changed from "ISO"
Changing ISO can only be done if the game is awaiting it and calling the appropriate function. This is because if "eject" (although no pendrive see activity in the eye) the green led flashes console. To get him back update the counter rotating.
Internally the emulator supports 8 virtual files are rotated. Iris Manager assigns all consecutively. If a game had 3 albums would be allocated as follows: 1,2,3,1,2,3,1,2 by what we see in the following sequence instead of the three would go to 1.
Although you can change discs should not tinker needlessly with that: a game may hang, so Use it only when necessary
Note that the first version of the emulator: if a game does not work but you have the assurance that if it works from ps1_emu CDROM (not the net), you tell me if I can watch it.
Indeed, in PSX options, choosing emulator is unnecessary for ISOS: ya know that you need to run (another thing that is not )
Estwald updated Iris Manager to version 1.50.1 to solve a permission issue in the FTP Server.
Estwald updated again to version 1.50.2 to fix a problem with the settings for PSX ISO
Ability to run PSX ISO (since 1.50.0)
Merged with code from D_Skywalk
Fixed small bugs (the FTP bug was fixed in 1.50.1)
Added option to copy PSX games from USB to HDD and viceversa.
MC now is cached on internal HDD and updated on the original folder returning to Iris Manager
Added option to list games per category using R2 (first all, then each category)
Fixed issue where BR drive was disappearing.
Fixed problem with a poke that could affect 3.55.
v1.51 (232014 via elotrolado.net/hilo_3-55-4-30-iris-manager-v1-38_1842936_s520#p1731460966):
Added support for 4.21 DEX
Removed "PSX unsupported" message when a PSX "ISO" is launched (syscall 8 is required to make it work; LV1 patches are not needed)
New version of the PSX emulator V2 (ps1_emu_patched2.self, do not rename it)
Added support for .ISO and .MDF (alcohol) formats for PSX images.
Images in MODE1/2048, MODE2/2336 and MODE2/2448 (CD-XA) are also supported.
All the images of the same game must be in the same format.
Added check of free space on HDD, when copying games
If size of game is larger than free space on internal HDD + 1GB, the copy is aborted
If size of game is larger than free space on external USB + 1MB, the copy is aborted
BD-EMU does not mount the HDD by default (now there are 2 options: old behavior and the default)
Some parts of the code have been touched (if some hangs occurs on start up)
The patcher tools have been unified in the same rar file
Restored the missing "mkdir" function that caused the error accessing language.ini