82w ago - Following up on the MA BD Tool v0.8 for PS3 JFW DH 3.56 MA CFW, today JaicraB has updated the previous PS3 Preloader Advance 2 to version 3 followed by bugfix 3.1 alongside a guide by Chekco via DemonHades below.
To quote, roughly translated: Hi all, as many know, when it published the JFW 3.56 MA-DH commented on the possibility of creating a virtual flasher to downgrade to 3.55 or less, well today is a fact that possibility so from now no one is "prisoner of MA", however it is a dangerous process, it is recommended to keep things clear and know what we are doing responsible are misuse said this. Let's begin:
The first is dump the data vital to our PS3, Aegean and we will use a configuration file download from the link below the pre3 (jaicrab.blogspot.com.es) and put in the root of the pen Archivo advanced.cfg, then rename the Lv2Diag.self to egea.self, create the following directory PS3/UPGRADE/egea.self.
Connecting to the USB port on the right and hope while reading the data from our ps3 "the process are between 3/5 minutes depending on the pen", when finished we will create the Backuprflash.bin. There are flash drives that are not compatible with egea, if we see that the ps3 starts normally change pendrive...
Good, the configuration file that will do is dump the rflash and flash1, flash2, flash3 once the reading process will turn off the ps3 and begins one of the most dangerous steps, we now have to patch the rflash with 3.55 core_os not chek, patch is recommended to follow the tutorials to dowgrades with physical flasher, but if you look confused or not know how. To be continued...
JaiCraB, to create preloader 3 and include the MAD.
Varicela test this tool and give me a PS3 and which I used for this tool and other future purposes.
Kike for sacrificing your PS3.
Checko, to try all options.
Demonhades by atosigarme to do it.
M * D ** for the knowledge transmitted.
Black, to add the improvement of Service Mode
Sorry for my bad English
PS3 Preloader Advance 3 by JaicraB
I decided to make improvements to the previous Advance Preloader 2. A major improvement is the virtual controller (MAD). Can directly manipulate the NOR or NAND memories of our consoles without having a physical developer. This leads to a high risk of running out of console.
A bad patch and you would be required to settle a physical developer. It has been tested successfully in several models. This does not mean that there is any model that fails. I hope you will heap up head. I am not responsible for any damage. Another use is to make copies of data unique to each console.
This tool has been developed for systems and lower JFW 3.55 3.56 MA. It requires no external libraries. It works even without the dev_flash in the system. It can be launched as Lv2Diag.self, as in JFW EGEA MA SELF 3.56 or releasing from any FileManager that supports it. May soon be published as PKG.
1. Copy of rflash:
For systems with NOR (16MB) and NAND (256MB) (no bootloader). Available two ways to copy. The first 16MB, 256MB or whole (for NAND) The process takes 50 sec (16MB NOR), 15 sec (16MB NAND), 1 min (256MB NAND). In rflash entire system is stored on the PS3. There we find:
Bootloader (NOR models only)
It will create a file called "Backuprflash.bin" in the USB000.
2. Restoring the rflash (MAD):
This step is dangerous, a bad change in the original can cause rflash BRICK. A bad usage can only be repaired only with physical developer. Also available in two modes (16MB, 256MB). Designed primarily for downgrading systems with "JFW MA" and for systems with problems downgrader. Has option to restore only different sectors. (Experimental). The process can take NOR, auque See not work on USB not quench. The "rflash" must be copied to the USB as "rflash.bin" But this safe to do so ... Do not!
3. Copy and Restore "/ dev_flashX"
To safely handle the file system used in GameOS. It will create a file called "Backupflash1.bin", "Backupflash2.bin", "Backupflash3.bin" USB000 depending on the number of dev_flash chosen. You can mount that image in your PC so you can change and then restore it. It is also useful when the system downgrade option 2 "Restoring rflash" and change your firmware with the file system. To restore is to copy the image of the "dev_flash" USB000 named the "flashX.bin".
4. Dump LV2, LV1
It is an extra unimportant. You just have to be installed in the system SC 6, 7, 11 for the process. The file created will be named on USB000 "DumpLv2.bin", "DumpLv1.bin".
5. Service Mode
We can enter / exit the service mode. To enter service mode from the pre3 need patched systems with LV1.
6. Out mode
When you finish the processes indicated in advance.cfg can do is shut down or reboot the system.
The tool will locate the file "advance.cfg" in "/ dev_usb000/advance.cfg" (Port closer to the reader) You can do all the actions triggered sequentially. That is, you can program the rflash and dev_flash at a time, out of service mode and reboot. In the configuration file is detailed the activation of each action. Flashing green LED means you are working.
Where it is that Red is complete. Writing in NOR models will seem to be blocked. But the led usb flash every 20 seconds so slightly. Do not put out until you do one or put the red LED.
JFW 3.56 downgrade MA:
The process will be detailed demonhades.org community.
Easy change version:
With well patched the rflash (CoreOS not check) with their respective "dev_flashX" can be changed in a matter of 4 minutes (NAND) of any firmware using this tool. Will address the issue soon on demonhades.org
Chickenpox test this tool and give me a PS3 and which I used for this purpose and other future purposes.
Kike for sacrificing your PS3.
Checko, to test all future tutorials opciones.Y use of that tool.
Demonhades by atosigarme to do it.
M * D ** for the knowledge transmitted.
Black, to add the improvement of Service Mode.
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