Factory service mode ps3 что это
Besides the normal "retail" bootmode there are several other modes the console can boot or halt in:
Fan test [ edit ]
The "fan test" mode allows to clean out the dust inside the PS3. When the PS3 boots in this mode the fan starts spinning in opposite direction and at 100% speed for a few time. Is reported to work for PS3 Models CECHG and newer, as shown in this table
- How to enable fan test mode
- Turn power switch to the OFF position (at the back of PS3 Fat), or disconnect the main power cable (at the back of PS3 Slim and SuperSlim)
- Press and hold button in the Switch board
- Turn power switch to the ON position (at the back of PS3 Fat), or connect the main power cable (at the back of PS3 Slim and SuperSlim)
- The PS3 boots doing a lot of noise from the fan (dont panic, is normal and doesnt last for much time), at this point you can release the button
Other special modes [ edit ]
The following requires the power switch in the back to be on:
1: beeps means beeps within a sort succession and exclude all previous ones and the power-on beep
sysmgr_ss.fself [ edit ]
requiring one will error out but not freeze (Tested on FAT NOR model CECHP01)
Other special modes [ edit ]
The following requires the power switch in the back to be on:
1: beeps means beeps within a sort succession and exclude all previous ones and the power-on beep
Solid Red [ edit ]
Solid Red - Powered Standby mode
Level-2 Kernel [ edit ]
It will allow to run an Application mounted via:
BSOD [ edit ]
Blue Screen of Death] error msg "Settings information is corrupted. Press the X button to repair and restore default settings."
- Failure at the configuration stage. Suspects: Harddrive/NAND VFlash areas content: Registry files on FAT16 partition (/dev_flash2 on NAND), VSH files on UFS2 partition (/dev_flash on NAND).
-
bad : Easy fixable by following instructions or using Recovery integrity fail : Seen when using Spoofedindex.dat/version.txt without patching VSH.self too (e.g. RogeroV3 -> solved in RogeroV3.1)
- also seen with VSH panic related to CEX2DEX/TargetID mismatches
- How to enable fan test mode
- Turn power switch to the OFF position (at the back of PS3 Fat), or disconnect the main power cable (at the back of PS3 Slim and SuperSlim)
- Press and hold button in the Switch board
- Turn power switch to the ON position (at the back of PS3 Fat), or connect the main power cable (at the back of PS3 Slim and SuperSlim)
- The PS3 boots doing a lot of noise from the fan (dont panic, is normal and doesnt last for much time), at this point you can release the button
Solid Blue [ edit ]
Solid Blue - Disc present in Bluray Drive
Rebug Toolbox [ edit ]
Select Option "Toggle Product Mode" under "Utilities" column.
- Allows remarry-ing of the Blu-Ray drive
- Blu-Ray DRL CRL fixing
- Downgrading of System Software
Flashing Blue [ edit ]
Flashing Blue - Disc inserted in / being ejected from Bluray Drive
JIG / Factory Service Mode / manufacturer [ edit ]
- The PS3 can enter a special "Service Mode". When it does (and can boot harddrive/dev_flash) the bottom right hand corner of the screen has a red translucent rectangle with the words "Playstation 3. Factory/Service Mode" inside of the rectangle. When the PS3 is off, plugging a special "JIG" in the USB port (and then pressing Eject immediately after pressing the Power button), the PS3 is triggered into Service Mode when it boots up. This special mode then accepts firmware code loaded in from the USB port (PS3UPDAT.PUP), and allows reflashing the firmware chip, or running programs from a USB drive.
- When on Factory Service Mode you cannot access the browser or leave the mode without an exit self and the console needs to be compatible with the exit self
JIG / Factory Service Mode / manufacturer [ edit ]
- The PS3 can enter a special "Service Mode". When it does (and can boot harddrive/dev_flash) the bottom right hand corner of the screen has a red translucent rectangle with the words "Playstation 3. Factory/Service Mode" inside of the rectangle. When the PS3 is off, plugging a special "JIG" in the USB port (and then pressing Eject immediately after pressing the Power button), the PS3 is triggered into Service Mode when it boots up. This special mode then accepts firmware code loaded in from the USB port (PS3UPDAT.PUP), and allows reflashing the firmware chip, or running programs from a USB drive.
- When on Factory Service Mode you cannot access the browser or leave the mode without an exit self and the console needs to be compatible with the exit self
NLOD [ edit ]
NLOD - No Led of Death
- Failure in the hardware_init stage. Suspects: Power disconnected, switch off, Power Supply, 12V fuses
- Misc: Faulty Ribbon Cable
Solid Blue [ edit ]
Solid Blue - Disc present in Bluray Drive
Solid Red [ edit ]
Solid Red - Powered Standby mode
ss_server2.fself [ edit ]
on all games and software (Games requiring an HDD will error out unless there is one in the drive)
Linux [ edit ]
1st step – Generating a challenge
- ps3dm_usb_dongle_auth /dev/ps3dmproxy gen_challenge
2nd step – Generating a valid response for a challenge
You need a dongle id. Valid range for dongle IDs is 0×0000 – 0xffff. So choose one, doesn’t matter which one, but some are revoked .
- ps3dm_usb_dongle_auth /dev/ps3dmproxy gen_resp 0xBABE “here is a challenge like this 0xXX 0xXX … of size 20 bytes”
3rd step – Verifying response (Enabling “Product Mode”)
- ps3dm_usb_dongle_auth /dev/ps3dmproxy verify_resp 0xBABE
“here is the response from step 2 like this 0xXX 0xXX … of size 20 bytes”
Solid Green [ edit ]
Solid Green - Powered On.
Level-1 Hypervisor [ edit ]
Different acting in Level-1 Hypervisor
BSOD [ edit ]
Blue Screen of Death] error msg "Settings information is corrupted. Press the X button to repair and restore default settings."
- Failure at the configuration stage. Suspects: Harddrive/NAND VFlash areas content: Registry files on FAT16 partition (/dev_flash2 on NAND), VSH files on UFS2 partition (/dev_flash on NAND).
-
bad : Easy fixable by following instructions or using Recovery integrity fail : Seen when using Spoofedindex.dat/version.txt without patching VSH.self too (e.g. RogeroV3 -> solved in RogeroV3.1)
- also seen with VSH panic related to CEX2DEX/TargetID mismatches
- Рестарт LV2
- Вся информация о процессе прописывается в лог файле.
- Добавлена проверка peek/poke с информацией об ошибках в логе.
- Добавлена проверка hvcall 114 с информацией об ошибках в логе.
- Теперь файл Lv2diag_exit.self копируется на dev_usb000 (необходимо его переименовать в Lv2diag.self, чтобы использовать).
- Failure in the hardware_init stage. Suspects: Power disconnected, switch off, Power Supply, 12V fuses
- Misc: Faulty Ribbon Cable
- Failure in the hardware_init stage. Suspects: RSX, CELL BE, XDR Ram, GDDR Vram, Syscon, South Bridge , Starship2 (if NAND SKU), NAND/NOR Flash, Power Supply, Fuses, Regulators, Cooling/Fan
- Failure at the firmware stage. Suspects: Harddrive content: Firmware files on UFS2 partition.
- On my bricked slim (CECH-2501B) the first sequence of 4 is: green red green red.
- On my working slim (CECH-2101B) the first sequence is: red red red red.
- On my other working slim (CECH-3001A) the first sequence is: red red red red.
- On all three consoles the next 3 sequence's, are all red.
- Failure in the hardware_init stage. Suspects: RSX, CELL BE, XDR Ram, GDDR Vram, Syscon, South Bridge , Starship2 (if NAND SKU), NAND/NOR Flash, Power Supply, Fuses, Regulators, Cooling/Fan
- On my bricked slim (CECH-2501B) the first sequence of 4 is: green red green red.
- On my working slim (CECH-2101B) the first sequence is: red red red red.
- On my other working slim (CECH-3001A) the first sequence is: red red red red.
- On all three consoles the next 3 sequence's, are all red.
- Failure at the firmware stage. Suspects: Harddrive content: Firmware files on UFS2 partition.
- Failure in the loaders stage. Suspects: Flash content: CoreOS files, inproper lv0ldr - pre VSH.
- When the PS3 is off
- plugging a special "JIG" in the most right USB port (closest to the Blu-Ray Drive)
- then pressing Eject immediately after pressing the Power button
- Failure in the loaders stage. Suspects: Flash content: CoreOS files, inproper lv0ldr - pre VSH.
If there is no hardware failure, reinstalling a proper firmware in Recovery Menu would likely fix it, some times requiring resetting/revalidating using the Recovery Menu suboptions.
НЕЛЬЗЯ ИСПОЛЬЗОВАТЬ НА НЕПРОШИВАЙКАХ!
Q: Can I use this with the RSOD fix self you released earlier?
A: You should only use the RSOD fix Lv2Diag.self to repair a RSOD PS3. Use the suplied Lv2diag.self packaged with this release to simply get out of service mode.Q: I'm having problems. help.
A: Post the contents of the factory.txt, which is stored on the root of the USB flash drive where you put Lv2Diag.self, along with a detailed explanation and we will try to help you out. Without the contents of the factory.txt file. we will not be able to help.Q: Why didn't you just name the release .self file Lv2diag.self and save us a step?
A: We intend to release more fun tools for you at some point, this just helps you keep them straight from the start.Q: It doesn't beep a single time for me, it beeps 3 times and goes back to the XMB. Can you help?
A: We attempted to fixed this in the v.2 version of the app, ensure you have that one installed. If you do have that installed. Run the app a second time, without shutting down or restarting the PS3.Q: I see this, "ERROR: failed to read EPROM", in the factory.txt error log. Can you help?
A: You likely heard 3 beeps. We attempted to fixed this in the v.2 version of the app, ensure you have that one installed. If you do have that installed. Run the app a second time, without shutting down or restarting the PS3.Q: I see this, "ERROR: SS EPROM read error returned: 1, product_mode: 0", in the factory.txt error log. Can you help?
A: You likely heard 3 beeps. We attempted to fixed this in the v.2 version of the app, ensure you have that one installed. If you do have that installed. Run the app a second time, without shutting down or restarting the PS3.Q: I see this, "ERROR: LV1 mmap hvcall 114 not available:", in the factory.txt error log. Can you help?
A: You likey have OFW (With Original PSJB Dongle even) or a reDRM Firmware. You will need to switch to a MFW to get this application to work.Q: I see this, "ERROR: LV2 poke syscall not available:", in the factory.txt error log. Can you help?
A: You likey have OFW (With Original PSJB Dongle even) or a reDRM Firmware. You will need to switch to a MFW to get this application to work.Q: I get a 80010505 error in factory.txt on the USB drive sometimes. HELP.
A: We noticed this on one Phat CECHG system in testing. but could not replicate it on other PS3's and it only occured after the initial run from a power on of the PS3. In this case, every time we ran it a second time the application worked with out fail. Try again and post the factory.txt if the problem persists.Q: Could you have made this just a little easier to use?
A: Nope! ;-)FactoryServiceMode.gnpdrm.pkg - для CEX.
FactoryServiceMode.pkg - для DEX.Homebrew позволяющее ввести PS3 в Factory Service Mode!
6041
Без необходимости в донгле!НЕЛЬЗЯ ИСПОЛЬЗОВАТЬ НА НЕПРОШИВАЙКАХ!
Информация о FSM:
Рестарт LV2
Вся информация о процессе прописывается в лог файле.
Добавлена проверка peek/poke с информацией об ошибках в логе.
Добавлена проверка hvcall 114 с информацией об ошибках в логе.
Теперь файл Lv2diag_exit.self копируется на dev_usb000 (необходимо его переименовать в Lv2diag.self, чтобы использовать).Q: Can I use this with the RSOD fix self you released earlier?
A: You should only use the RSOD fix Lv2Diag.self to repair a RSOD PS3. Use the suplied Lv2diag.self packaged with this release to simply get out of service mode.Q: I'm having problems. help.
A: Post the contents of the factory.txt, which is stored on the root of the USB flash drive where you put Lv2Diag.self, along with a detailed explanation and we will try to help you out. Without the contents of the factory.txt file. we will not be able to help.Q: Why didn't you just name the release .self file Lv2diag.self and save us a step?
A: We intend to release more fun tools for you at some point, this just helps you keep them straight from the start.Q: It doesn't beep a single time for me, it beeps 3 times and goes back to the XMB. Can you help?
A: We attempted to fixed this in the v.2 version of the app, ensure you have that one installed. If you do have that installed. Run the app a second time, without shutting down or restarting the PS3.Q: I see this, "ERROR: failed to read EPROM", in the factory.txt error log. Can you help?
A: You likely heard 3 beeps. We attempted to fixed this in the v.2 version of the app, ensure you have that one installed. If you do have that installed. Run the app a second time, without shutting down or restarting the PS3.Q: I see this, "ERROR: SS EPROM read error returned: 1, product_mode: 0", in the factory.txt error log. Can you help?
A: You likely heard 3 beeps. We attempted to fixed this in the v.2 version of the app, ensure you have that one installed. If you do have that installed. Run the app a second time, without shutting down or restarting the PS3.Q: I see this, "ERROR: LV1 mmap hvcall 114 not available:", in the factory.txt error log. Can you help?
A: You likey have OFW (With Original PSJB Dongle even) or a reDRM Firmware. You will need to switch to a MFW to get this application to work.Q: I see this, "ERROR: LV2 poke syscall not available:", in the factory.txt error log. Can you help?
A: You likey have OFW (With Original PSJB Dongle even) or a reDRM Firmware. You will need to switch to a MFW to get this application to work.Q: I get a 80010505 error in factory.txt on the USB drive sometimes. HELP.
A: We noticed this on one Phat CECHG system in testing. but could not replicate it on other PS3's and it only occured after the initial run from a power on of the PS3. In this case, every time we ran it a second time the application worked with out fail. Try again and post the factory.txt if the problem persists.Q: Could you have made this just a little easier to use?
A: Nope! ;-)FactoryServiceMode.gnpdrm.pkg - для CEX.
FactoryServiceMode.pkg - для DEX.akela1979, у меня сейчас слим 250гб прошивка 3.41 использую юсб ключ на пейлоаде гермес4б - если поставлю данную програмку то шаманство с вкл/выкл приставки больше не потребуеться? и будетли работать мультимен без самого донгла, потому что если без донгла запускать он пишет бд эмулятор не найден - а с ключем все нормально работает.
The Playstation 3 Console can enter a special "Service Mode". When it does so, the bottom right hand corner of the screen has a red translucent rectangle with the words "Playstation 3. Factory/Service Mode" inside of the rectangle.
To enter, it is needed setting Offset 0x48C07 on the System Controller EEPROM to value: 0x00 or 0xFE,
at least something beside 0xFF (inactive). This can usually be done via a special hardware logic dongle, or the Factory Service Mode Tool.Game OS [ edit ]
Game OS Applications will be granted to access following Level-2 Kernel Syscalls:
Besides the normal "retail" bootmode there are several other modes the console can boot or halt in:
Solid Green [ edit ]
Solid Green - Powered On.
Errors on boot [ edit ]
Error output in order of appearance and likely suspects:
NLOD [ edit ]
NLOD - No Led of Death
YLOD [ edit ]
YLOD - Yellow Led of Death (Flashes Green, Yellow then Red)
If you ground out tristate on a (?NOR only?) console with YLOD, it would GLOD instead if it is caused by bad flash (or content of flash). This makes it an easy way to check if the YLOD is flash caused (most common) or RSX caused (second most common).
RSOD [ edit ]
Red Screen Of Death error msg "serious error has occurred"
Seen with cvtrm errors : RSOD Fix
LED Diag Mode [ edit ]
I have found what I think is a diag mode that displays error codes using the power button light, kind of like what an OBD-1 ECU on a car would do. To activate it you have to do a fan test and wait until after the ps3 powers off(this much I am sure of) then you have to press eject and then power rapidly many times in succession also try holding eject and pressing power. Once you enter this mode the power light will flash yellow for about 1 second then the status of 4 component's(which ones I don't know) within the ps3 will be displayed by the power light blinking 4 times for each 4 component's. Then the yellow light blinks again letting you know the cycle has started again.
So it seems that red=good and green=bad. Also I removed the Blu-ray drive on my bricked slim and the codes did not change. sorry I don't know more about this.
I have now bricked the CECH-2101B and it also displays green red green red as the first sequence of 4
Anyone with a ylod console please post their symptoms and result of this test
Probably Green = 1, while red = 0. So you get 16 bits.
Blu-ray drive is not a core part of the system, it will boot without it just fine.
Cannot seem to get led diag to work on CECHA fats, don't know what FW version (because requiring fan test , available only for Models CECHG and higher?).
YLOD [ edit ]
YLOD - Yellow Led of Death (Flashes Green, Yellow then Red)
If you ground out tristate on a (?NOR only?) console with YLOD, it would GLOD instead if it is caused by bad flash (or content of flash). This makes it an easy way to check if the YLOD is flash caused (most common) or RSX caused (second most common).
GLOD [ edit ]
GLOD - Flashing Green Led of Death (or when nothing is bad: PS3 is powering off)
Factory Service Mode Tool [ edit ]
FactoryServiceMode Tool v0.2 (Only on modified Playstation System Software 3.55 and lower) allows you to enter Factory Service Mode without any Dongle and just through GameOS XMB.
Flashing Blue [ edit ]
Flashing Blue - Disc inserted in / being ejected from Bluray Drive
LED Diag Mode [ edit ]
I have found what I think is a diag mode that displays error codes using the power button light, kind of like what an OBD-1 ECU on a car would do. To activate it you have to do a fan test and wait until after the ps3 powers off(this much I am sure of) then you have to press eject and then power rapidly many times in succession also try holding eject and pressing power. Once you enter this mode the power light will flash yellow for about 1 second then the status of 4 component's(which ones I don't know) within the ps3 will be displayed by the power light blinking 4 times for each 4 component's. Then the yellow light blinks again letting you know the cycle has started again.
So it seems that red=good and green=bad. Also I removed the Blu-ray drive on my bricked slim and the codes did not change. sorry I don't know more about this.
I have now bricked the CECH-2101B and it also displays green red green red as the first sequence of 4
Anyone with a ylod console please post their symptoms and result of this test
Probably Green = 1, while red = 0. So you get 16 bits.
Blu-ray drive is not a core part of the system, it will boot without it just fine.
Cannot seem to get led diag to work on CECHA fats, don't know what FW version (because requiring fan test , available only for Models CECHG and higher?).
RSOD [ edit ]
Red Screen Of Death error msg "serious error has occurred"
Seen with cvtrm errors : RSOD Fix
Errors on boot [ edit ]
Error output in order of appearance and likely suspects:
ss_server1 [ edit ]
of functions already listed here such as Downgrading/BD Remarry/CRL Files etc. but also lets the ps3 use ps2_netemu.self)
RLOD [ edit ]
RLOD - Flashing Red Led of Death
Seen in combination with poweroff when downgrading below metldr/bootldr capability
GLOD [ edit ]
GLOD - Flashing Green Led of Death (or when nothing is bad: PS3 is powering off)
Dongle [ edit ]
The PlayStation 3 is triggered into Service Mode when it boots up.
RLOD [ edit ]
RLOD - Flashing Red Led of Death
Seen in combination with poweroff when downgrading below metldr/bootldr capability
Читайте также:
If there is no hardware failure, reinstalling a proper firmware in Recovery Menu would likely fix it, some times requiring resetting/revalidating using the Recovery Menu suboptions.
Fan test [ edit ]
The "fan test" mode allows to clean out the dust inside the PS3. When the PS3 boots in this mode the fan starts spinning in opposite direction and at 100% speed for a few time. Is reported to work for PS3 Models CECHG and newer, as shown in this table