PS3 [GUIDE] Unbrick a PS3 after an unfortunate PS3Xploit flash

hi, someone can help me please?

I have a ps3 phat cecha0, I bricked it trying to install linux, but before the problem I made two backups of the nand, one with rebug toolbox, other with evilnat options, I was using evilnat 4.88.2

I`m hoping to use this tutorial to solve this, but I have some questions and I`m afraid that the situation be worse

In the files on the first post I can`t see the files to use with 4.88, can someone give a hint that what I have to do?
 
tunex said:
hi, someone can help me please?

I have a ps3 phat cecha0, I bricked it trying to install linux, but before the problem I made two backups of the nand, one with rebug toolbox, other with evilnat options, I was using evilnat 4.88.2

I`m hoping to use this tutorial to solve this, but I have some questions and I`m afraid that the situation be worse

In the files on the first post I can`t see the files to use with 4.88, can someone give a hint that what I have to do?
Click to expand...
You might be posting in the wrong thread.
This thread is about failed or inappropriate no-fsm patching, the objective being to restore the ROS regions with an official CoreOS because the jailbreak attempt failed and/or CoreOS files are "corrupted" as far as the system is concerned.
If you say you "bricked" while installing Linux (?), I doubt that restoring OFW CoreOS would solve anything... Moreover if you already have proper backups of your NAND, I don't think you should need any patch files from the OP or elsewhere.

To help you with your problem, we would first need to know how you "bricked", the term "while installing Linux" is too vague. As it is, we cannot say what needs to be fixed!
 
Last edited:
bguerville said:
You might be posting in the wrong thread.
This thread is about failed or inappropriate no-fsm patching, the objective being to restore the ROS regions with an official CoreOS because the jailbreak attempt failed and/or CoreOS files are "corrupted" as far as the system is concerned.
If you say you "bricked" while installing Linux (?), I doubt that restoring OFW CoreOS would solve anything... Moreover if you already have proper backups of your NAND, I don't think you should need any patch files from the OP or elsewhere.

To help you with your problem, we would first need to know how you "bricked", the term "while installing Linux" is too vague. As it is, we cannot say what needs to be fixed!
Click to expand...
I tryed an old petit boot based on openwrt and it bricked the ps3

I tryed to check my backup with the tool from the first post and my ROS0 and ROS1 are red, because this I posted here
 
tunex said:
I tryed an old petit boot based on openwrt and it bricked the ps3

I tryed to check my backup with the tool from the first post and my ROS0 and ROS1 are red, because this I posted here
Click to expand...
Afaik petitboot does not make any changes to CoreOS. Anyway that's still not enough information to understand the problem, never mind proposing solutions to fix it.
Did you get petitboot to load ok at first?
Then if you did, what did you do after that?
What happens now when you boot the system?

FYI
Iirc there is no native OtherOS++ support in Evilnat's 4.88.2 CFW (it must have been an oversight & Evilnat is not around to add support).
I think you need to use Rebug or other earlier CFWs go install OtherOS++ or you must unpack Evilnat's CFW, apply proper OtherOS++ patches & repack.
 
Last edited:
bguerville said:
Afaik petitboot does not make any changes to CoreOS. Anyway that's still not enough information to understand the problem, never mind proposing solutions to fix it.
Did you get petitboot to load ok at first?
Then if you did, what did you do after that?
What happens now when you boot the system?
Click to expand...

This petitboot I found in an old site, it's diferent, it opens a graphical interface that could recognize a ubuntu power-pc disck or an installation on hdd, but It was empty, I could not exit it, only access a terminal based in openwrt

I have access to a E3 flasher, but I could not restore with the backup that I made with rebug toolbox

When I try to check with PS3 Dump Checker the ROS0 And ROS1 are red and the bump is market as BAD.

I would like to recover this backup to try again with E3 flasher

This is the petit that I tried: http://jk.ozlabs.org/projects/petitboot/

I alredy tried square to load gameos, but I reboot into petit again
 
tunex said:
This petitboot I found in an old site, it's diferent, it opens a graphical interface that could recognize a ubuntu power-pc disck or an installation on hdd, but It was empty, I could not exit it, only access a terminal based in openwrt

I have access to a E3 flasher, but I could not restore with the backup that I made with rebug toolbox

When I try to check with PS3 Dump Checker the ROS0 And ROS1 are red and the bump is market as BAD.

I would like to recover this backup to try again with E3 flasher

This is the petit that I tried: http://jk.ozlabs.org/projects/petitboot/

I alredy tried square to load gameos, but I reboot into petit again
Click to expand...
That petitboot is fine, I used it myself.
What CFW did you do all this on?
Evilnat's 4.88.2?
Using what tools to enable OtherOS++?

If you are stuck in OtherOS mode, you need to go back to GameOS, you can do that using the petitboot console.
Or have you tried to soft reset (console switched off, hold power button til you get 2 beeps)?

Regarding the dump check, validate it with the last version of pyps3checker, available at github.com/PyPS3tools & post the logs.
If ever the CoreOS regions are found to be corrupted, I doubt very much that petitboot would be the culprit, are you sure you didn't apply bad patches with a hardware flasher?
 
Last edited:
it was some months ago, I don't remember all the steps

I was in evilnat 4.88.2, I don't remember if I used only the tools on evilnat menu or if I used rebug toolbox

I was able to make a downgrade one week before and installed linux with the official otheros using ubuntu 8.10, but after that I restored to evilnat and tried again to test with other distributions

This is the result:

PyPS3checker v0.11.x. Check log.
Checked file : C:\Users\rafae\Desktop\ps3\backup antes do red ribbon 20120101-001358-FLASH-NAND-FW4.84\20120101-001358-FLASH-NAND-FW4.84.NANDBIN
******* Getting flash type *******
Flash type : NAND (full dump, 256MB)
******* Getting SKU identification datas *******
idps = 0x03
metldr0 = 0xEDE0
metldr1 = 0x0EDA
bootldr0 = 0x2A37
bootldr1 = 0x2A37
bootldrsize = 0x2A3B0
Matching SKU : OK
CECHCxx (COK-002)
Minimum version 1.00
******* Getting SDK versions *******
ROS0 : 484.000
ROS1 : 482.000
******* Checking bootldr_top_region *******
001.01 bootldr0 (Top) : OK
001.02 bootldr1 (Top) : OK
001.03 bootldr Rev key (Top) : OK
001.04 bootldr Statistics (Top) : OK
001.05 bootldr (Top) 0xFF Filled Area : OK
******* Checking Header_Magic *******
002.01 Header Magic 0x00 Filled Area 0 : OK
002.02 Header Magic : OK
002.03 Header Magic 0x00 Filled Area 1 : OK
******* Checking flash_region_table *******
003.01 Flash Region Table Header : OK
003.02 asecure_loader Offset - Length : OK
003.03 asecure_loader Name : OK
003.04 eEID Offset - Length : OK
003.05 eEID Name : OK
003.06 cISD Offset - Length : OK
003.07 cISD Name : OK
003.08 cCSD Offset - Length : OK
003.09 cCSD Name : OK
003.10 trvk_prg Offset - Length : OK
003.11 trvk_prg Name : OK
003.12 trvk_pkg Offset - Length : OK
003.13 trvk_pkg Name : OK
003.14 creserved_0 Offset - Length : OK
003.15 creserved_0 Name : OK
003.16 ros Offset - Length : OK
003.17 ros Name : OK
003.18 cvtrm Offset - Length : OK
003.19 cvtrm Name : OK
003.20 Flash Region Table 0x00 Filled Area : OK
******* Checking asure_loader_region *******
004.01 asecure_loader Header : OK
004.02 metldr Offset : OK
004.03 metldr Length : OK
004.04 metldr Name : OK
004.05 metldr RevKey : OK
004.06 metldr Binary Size : OK
004.07 metldr Statistics : OK
004.08 asecure_loader 0x00 Filled Area : OK
******* Checking eEID_region *******
005.01 eEID Header : OK
005.02 EID0 Offset - Length : OK
005.03 EID1 Offset - Length : OK
005.04 EID2 Offset - Length : OK
005.05 EID3 Offset - Length : OK
005.06 EID4 Offset - Length : OK
005.07 EID5 Offset - Length : OK
005.08 EID0 IDPS0 : OK
005.09 EID0 IDPS1 : OK
005.10 EID0 Static : OK
005.11 EID2 BlockSize/Padding : OK
005.12 EID3 Static0 : OK
005.13 EID3 Static1 : OK
005.14 EID3 Static2 : OK
005.15 EID5 IDPS0 : OK
005.16 EID5 IDPS1 : OK
005.17 EID5 Static : OK
005.18 eEID Region 0xFF Filled Area : OK
005.19 eEID Statistics0 : OK
005.20 eEID Statistics1 : OK
******* Checking cISD_region *******
006.01 cISD Header : OK
006.02 cISD0 Offset - Length : OK
006.03 cISD1 Offset - Length : OK
006.04 cISD2 Offset - Length : OK
006.05 cISD0 0xFF Filled Area : OK
006.06 cISD1 IDLog Header : OK
006.07 cISD1 Semistatic 1 : OK
006.08 cISD1 Semistatic 2 : OK
006.09 cISD1 0xFF Filled Area 0 : OK
006.10 cISD1 Static : OK
006.11 cISD1 Semistatic 3 : OK
006.12 cISD1 0xFF Filled Area 1 : OK
006.13 cISD1 Statistics : OK
006.14 cISD2 : OK
006.15 cISD 0xFF Filled Area : OK
******* Checking cCSD_region *******
007.01 cCSD Header : OK
007.02 cCSD Entry Table : OK
007.03 cCSD 0xFF Filled Area : OK
******* Checking Revokation_region *******
008.00 trvk_prg Region Header : OK
008.01 trvk_prg0 SCE : OK
008.02 trvk_prg0 Hash : OK
Size = 0x2E0
MD5 = 78629D24BD721488F3A1E846938F87DF
Version = 3.55 (from PUP)
008.03 trvk_prg1 SCE : OK
008.04 trvk_prg1 Hash : OK
Size = 0x2C0
MD5 = 6866A7A6B69EE57FD4BC1EF95C5666A6
Version = 3.15 (from PUP)
008.00 trvk_pkg Region Header : OK
008.05 trvk_pkg0 SCE : OK
008.07 trvk_pkg1 SCE : OK
******* Checking Unreferenced_Area *******
008.08 unreferenced area 0xFF filled : OK
******* Checking CoreOS_region *******
009.00 ROS Header : OK
009.01 ROS0 Header : OK
009.02 ROS0 Hash : OK
Size = 0x6FFFE0
MD5 = 7972C66E5CD5FD26772E53BA8638EA89
Version = 4.84.2 REBUG D-REX
009.03 ROS1 Header : OK
009.04 ROS1 Hash : WARNING!
Size = 0x6FFFE0
MD5 = A0E9FB54223DF60212140B64BE9B2D30
Version = (unknown)
******* Checking cvtrm_region *******
010.01 cvtrm Header : OK
010.02 cvtrm Header Static 1 : OK
010.03 vtrm Magic 1 : OK
010.05 vtrm Magic 2 : OK
010.07 cvtrm 0x00 Filled Area : OK
******* Checking cell_ext_os_area *******
011.01 cell_ext_os_area Header : OK
011.02 cell_ext_os_area 0xFF Filled Area 0 : OK
011.03 cell_ext_os_area Break Section : OK
011.04 cell_ext_os_area 0xFF Filled Area 1 : OK
******* Checking bootldr_bottom_region *******
012.01 bootldr0 (Bottom) : OK
012.02 bootldr1 (Bottom) : OK
012.03 bootldr Rev key (Bottom) : OK
012.04 bootldr Statistics (Bottom) : OK
012.05 bootldr 0xFF Filled Area : OK
******* Checking datamatches *******
bootldr size : OK
per console nonce : OK
bootldr : OK
metldr size : OK
vtrm header datas : OK
vtrm : OK
******* Checking repetitions *******
Header Magic Repetition : OK
asecure_loader Repetition : OK
eEID Repetition : OK
cISD Repetition : OK
cCSD Repetition : OK
trvk_prg Repetition : OK
trvk_pkg Repetition : OK
ros Repetition : OK
cvtrm Repetition : OK
******* Additional information *******
MAC address : 00:19:C5:82:37:39
CID : 0x0002005AF06C
eCID : 01C53DD7411897180A05004000000000
board_id (part of console S/N) : 27430321
kiban_id (board barcode) : 15A600979273
******* Checks completed *******
Total number of checks = 131
Number of dangers = 0
Number of warnings = 1
Following check(s) returned a WARNING!
009.04 ROS1 Hash
All checks done in 3.22 seconds.
 
tunex said:
it was some months ago, I don't remember all the steps

I was in evilnat 4.88.2, I don't remember if I used only the tools on evilnat menu or if I used rebug toolbox

I was able to make a downgrade one week before and installed linux with the official otheros using ubuntu 8.10, but after that I restored to evilnat and tried again to test with other distributions

This is the result:

PyPS3checker v0.11.x. Check log.
Checked file : C:\Users\rafae\Desktop\ps3\backup antes do red ribbon 20120101-001358-FLASH-NAND-FW4.84\20120101-001358-FLASH-NAND-FW4.84.NANDBIN
******* Getting flash type *******
Flash type : NAND (full dump, 256MB)
******* Getting SKU identification datas *******
idps = 0x03
metldr0 = 0xEDE0
metldr1 = 0x0EDA
bootldr0 = 0x2A37
bootldr1 = 0x2A37
bootldrsize = 0x2A3B0
Matching SKU : OK
CECHCxx (COK-002)
Minimum version 1.00
******* Getting SDK versions *******
ROS0 : 484.000
ROS1 : 482.000
******* Checking bootldr_top_region *******
001.01 bootldr0 (Top) : OK
001.02 bootldr1 (Top) : OK
001.03 bootldr Rev key (Top) : OK
001.04 bootldr Statistics (Top) : OK
001.05 bootldr (Top) 0xFF Filled Area : OK
******* Checking Header_Magic *******
002.01 Header Magic 0x00 Filled Area 0 : OK
002.02 Header Magic : OK
002.03 Header Magic 0x00 Filled Area 1 : OK
******* Checking flash_region_table *******
003.01 Flash Region Table Header : OK
003.02 asecure_loader Offset - Length : OK
003.03 asecure_loader Name : OK
003.04 eEID Offset - Length : OK
003.05 eEID Name : OK
003.06 cISD Offset - Length : OK
003.07 cISD Name : OK
003.08 cCSD Offset - Length : OK
003.09 cCSD Name : OK
003.10 trvk_prg Offset - Length : OK
003.11 trvk_prg Name : OK
003.12 trvk_pkg Offset - Length : OK
003.13 trvk_pkg Name : OK
003.14 creserved_0 Offset - Length : OK
003.15 creserved_0 Name : OK
003.16 ros Offset - Length : OK
003.17 ros Name : OK
003.18 cvtrm Offset - Length : OK
003.19 cvtrm Name : OK
003.20 Flash Region Table 0x00 Filled Area : OK
******* Checking asure_loader_region *******
004.01 asecure_loader Header : OK
004.02 metldr Offset : OK
004.03 metldr Length : OK
004.04 metldr Name : OK
004.05 metldr RevKey : OK
004.06 metldr Binary Size : OK
004.07 metldr Statistics : OK
004.08 asecure_loader 0x00 Filled Area : OK
******* Checking eEID_region *******
005.01 eEID Header : OK
005.02 EID0 Offset - Length : OK
005.03 EID1 Offset - Length : OK
005.04 EID2 Offset - Length : OK
005.05 EID3 Offset - Length : OK
005.06 EID4 Offset - Length : OK
005.07 EID5 Offset - Length : OK
005.08 EID0 IDPS0 : OK
005.09 EID0 IDPS1 : OK
005.10 EID0 Static : OK
005.11 EID2 BlockSize/Padding : OK
005.12 EID3 Static0 : OK
005.13 EID3 Static1 : OK
005.14 EID3 Static2 : OK
005.15 EID5 IDPS0 : OK
005.16 EID5 IDPS1 : OK
005.17 EID5 Static : OK
005.18 eEID Region 0xFF Filled Area : OK
005.19 eEID Statistics0 : OK
005.20 eEID Statistics1 : OK
******* Checking cISD_region *******
006.01 cISD Header : OK
006.02 cISD0 Offset - Length : OK
006.03 cISD1 Offset - Length : OK
006.04 cISD2 Offset - Length : OK
006.05 cISD0 0xFF Filled Area : OK
006.06 cISD1 IDLog Header : OK
006.07 cISD1 Semistatic 1 : OK
006.08 cISD1 Semistatic 2 : OK
006.09 cISD1 0xFF Filled Area 0 : OK
006.10 cISD1 Static : OK
006.11 cISD1 Semistatic 3 : OK
006.12 cISD1 0xFF Filled Area 1 : OK
006.13 cISD1 Statistics : OK
006.14 cISD2 : OK
006.15 cISD 0xFF Filled Area : OK
******* Checking cCSD_region *******
007.01 cCSD Header : OK
007.02 cCSD Entry Table : OK
007.03 cCSD 0xFF Filled Area : OK
******* Checking Revokation_region *******
008.00 trvk_prg Region Header : OK
008.01 trvk_prg0 SCE : OK
008.02 trvk_prg0 Hash : OK
Size = 0x2E0
MD5 = 78629D24BD721488F3A1E846938F87DF
Version = 3.55 (from PUP)
008.03 trvk_prg1 SCE : OK
008.04 trvk_prg1 Hash : OK
Size = 0x2C0
MD5 = 6866A7A6B69EE57FD4BC1EF95C5666A6
Version = 3.15 (from PUP)
008.00 trvk_pkg Region Header : OK
008.05 trvk_pkg0 SCE : OK
008.07 trvk_pkg1 SCE : OK
******* Checking Unreferenced_Area *******
008.08 unreferenced area 0xFF filled : OK
******* Checking CoreOS_region *******
009.00 ROS Header : OK
009.01 ROS0 Header : OK
009.02 ROS0 Hash : OK
Size = 0x6FFFE0
MD5 = 7972C66E5CD5FD26772E53BA8638EA89
Version = 4.84.2 REBUG D-REX
009.03 ROS1 Header : OK
009.04 ROS1 Hash : WARNING!
Size = 0x6FFFE0
MD5 = A0E9FB54223DF60212140B64BE9B2D30
Version = (unknown)
******* Checking cvtrm_region *******
010.01 cvtrm Header : OK
010.02 cvtrm Header Static 1 : OK
010.03 vtrm Magic 1 : OK
010.05 vtrm Magic 2 : OK
010.07 cvtrm 0x00 Filled Area : OK
******* Checking cell_ext_os_area *******
011.01 cell_ext_os_area Header : OK
011.02 cell_ext_os_area 0xFF Filled Area 0 : OK
011.03 cell_ext_os_area Break Section : OK
011.04 cell_ext_os_area 0xFF Filled Area 1 : OK
******* Checking bootldr_bottom_region *******
012.01 bootldr0 (Bottom) : OK
012.02 bootldr1 (Bottom) : OK
012.03 bootldr Rev key (Bottom) : OK
012.04 bootldr Statistics (Bottom) : OK
012.05 bootldr 0xFF Filled Area : OK
******* Checking datamatches *******
bootldr size : OK
per console nonce : OK
bootldr : OK
metldr size : OK
vtrm header datas : OK
vtrm : OK
******* Checking repetitions *******
Header Magic Repetition : OK
asecure_loader Repetition : OK
eEID Repetition : OK
cISD Repetition : OK
cCSD Repetition : OK
trvk_prg Repetition : OK
trvk_pkg Repetition : OK
ros Repetition : OK
cvtrm Repetition : OK
******* Additional information *******
MAC address : 00:19:C5:82:37:39
CID : 0x0002005AF06C
eCID : 01C53DD7411897180A05004000000000
board_id (part of console S/N) : 27430321
kiban_id (board barcode) : 15A600979273
******* Checks completed *******
Total number of checks = 131
Number of dangers = 0
Number of warnings = 1
Following check(s) returned a WARNING!
009.04 ROS1 Hash
All checks done in 3.22 seconds.
Click to expand...
Like I said, Evilnat 4.88.2 was reported to lack OtherOS support.

The logs you posted show just one warning which imho can safely be ignored.
The active ROS region's CoreOS (ROS0) is valid & the fact that the ROS1 CoreOS type cannot be identified (the version was 4.82, it was the CFW that was installed just before you updated to Rebug REX 4.84.2) should not be a problem.
Imho this dump is good.

Btw your console is a nand model, you cannot use a E3 flasher, those are for NOR only, with NAND you should use a Teensy.
 
bguerville said:
Like I said, Evilnat 4.88.2 was reported to lack OtherOS support.

The logs you posted show just one warning which imho can safely be ignored.
The active ROS region's CoreOS (ROS0) is valid & the fact that the ROS1 CoreOS type cannot be identified (the version was 4.82, it was the CFW that was installed just before you updated to Rebug REX 4.84.2) should not be a problem.
Imho this dump is good.

Btw your console is a nand model, you cannot use a E3 flasher, those are for NOR only, with NAND you should use a Teensy.
Click to expand...
do you know where can I buy one? there's a specific model?
 
tunex said:
do you know where can I buy one? there's a specific model?
Click to expand...
Afaik the manufacturer (pjrc.com) discontinued the model you need, Teensy 2.0++, a few months ago so you will have to search online.
It should be around 20 bucks.
Unfortunately, with the board, you will also need expensive tsop nand clips otherwise you will need to do all the soldering.

Btw note that your dump was done with Rebug D-REX 4.84.2 which probably means the active ROS 0 CoreOS is DEX.

If ever you are to flash your NAND (which so far in this convo is still not really proven to be the problem), remember to make 2 or 3 validated (with pyps3checker) full nand dumps with the Teensy before you do anything else as you cannot reuse your previous backup dumps as they are.
You will have to frankenstein a file from the backups + a valid Teensy dump + the no-fsm CoreOS file for 4.88 available at github.com/PyPS3tools. Post the logs of the Teensy dump & seek our help to create that frankie file when you are ready.
 
bguerville said:
Afaik the manufacturer (pjrc.com) discontinued the model you need, Teensy 2.0++, a few months ago so you will have to search online.
It should be around 20 bucks.
Unfortunately, with the board, you will also need expensive tsop nand clips otherwise you will need to do all the soldering.

Btw note that your dump was done with Rebug D-REX 4.84.2 which probably means the active ROS 0 CoreOS is DEX.

If ever you are to flash your NAND (which so far in this convo is still not really proven to be the problem), remember to make 2 or 3 validated (with pyps3checker) full nand dumps with the Teensy before you do anything else as you cannot reuse your previous backup dumps as they are.
You will have to frankenstein a file from the backups + a valid Teensy dump + the no-fsm CoreOS file for 4.88 available at github.com/PyPS3tools. Post the logs of the Teensy dump & seek our help to create that frankie file when you are ready.
Click to expand...

I also have the dump.hex from your tool before make the cfw install, can it help in any way?
 
tunex said:
I also have the dump.hex from your tool before make the cfw install, can it help in any way?
Click to expand...
I don't think so but you should keep it safe nonetheless, the frankie file is the last thing that needs done before patching, there is no point working on this as long as you don't have a dump of the Flash memory in its current state & if you cannot start the console or reset it with the power button sequence, the only way to get a current dump is to install a Teensy.
 
tunex said:
Only more question please, with this two things I can try to restore the nand?
https://store.modchip59.com/produit/teensy2ps3-adapter/
https://store.modchip59.com/produit/teensy-2-at90usb1286/

You said that you used that petit too, do you know any way to go back to gameos from the terminal or any other thing? If there`s a way to "unstuck"?
Click to expand...
Iirc there are 2 ways.

1. In petitboot you should use the square gamepad button or delete/backspace on usb keyboard to boot into GameOS.
I don't remember what command you should use in the alt-f1 text console.

2. you can reset the default boot options by turning the ps3 off then pressing the console power button until you hear one set of beeps, then a second set of beeps & releasing the button.
The console should boot to GameOS by default after that.

Btw it's normal to get nothing on screen with the petitboot GUI if no bootable partition can be found on internal hdd or USB.
 
Last edited:
bguerville said:
Iirc there are 2 ways.

1. In petitboot you should use the square gamepad button or delete/backspace on usb keyboard to boot into GameOS.
I don't remember what command you should use in the alt-f1 text console.

2. you can reset the default boot options by turning the ps3 off then pressing the console power button until you hear one set of beeps, then a second set of beeps & releasing the button.
The console should boot to GameOS by default after that.
Click to expand...
already did it, without result, I cant even access that recovery menu holding power
 
tunex said:
already did it, without result, I cant even access that recovery menu holding power
Click to expand...
Code: 
... 
case TwinEventKeyDown:

		switch(event->u.key.key) {

		/* Gross hack for video modes, need something better ! */

		case KEY_0:

			pboot_vmode_change = 0; /* auto */

			pboot_quit();

			return TWIN_TRUE;

		case KEY_1:

			pboot_vmode_change = 3; /* 720p */

			pboot_quit();

			return TWIN_TRUE;

		case KEY_2:

			pboot_vmode_change = 4; /* 1080i */

			pboot_quit();

			return TWIN_TRUE;

		case KEY_3:

			pboot_vmode_change = 5; /* 1080p */

			pboot_quit();

			return TWIN_TRUE;

 

		/* Another gross hack for booting back to gameos */

		case KEY_BACKSPACE:

		case KEY_DELETE:

			pboot_message("booting to GameOS...");

			system(BOOT_GAMEOS_BIN);

		}


...
As you can see in the source code excerpt above, pressing the keyboard keys:

0/1/2/3 change the video mode.
and
delete/backspace boot GameOS from the petitboot GUI screen.
 
bguerville said:
Code: 
...
case TwinEventKeyDown:

        switch(event->u.key.key) {

        /* Gross hack for video modes, need something better ! */

        case KEY_0:

            pboot_vmode_change = 0; /* auto */

            pboot_quit();

            return TWIN_TRUE;

        case KEY_1:

            pboot_vmode_change = 3; /* 720p */

            pboot_quit();

            return TWIN_TRUE;

        case KEY_2:

            pboot_vmode_change = 4; /* 1080i */

            pboot_quit();

            return TWIN_TRUE;

        case KEY_3:

            pboot_vmode_change = 5; /* 1080p */

            pboot_quit();

            return TWIN_TRUE;

 

        /* Another gross hack for booting back to gameos */

        case KEY_BACKSPACE:

        case KEY_DELETE:

            pboot_message("booting to GameOS...");

            system(BOOT_GAMEOS_BIN);

        }


...
As you can see in the source code excerpt above, pressing the keyboard keys:

0/1/2/3 change the video mode.
and
delete/backspace boot GameOS from the petitboot GUI screen.
Click to expand...
Yes I saw that, mas it not working, so I tought that I could do something in terminal
 
tunex said:
Yes I saw that, mas it not working, so I tought that I could do something in terminal
Click to expand...
Well the terminal should be a Linux bash or something along those lines therefore what the petitboot GUI does to boot to GameOS ie execute "system(GAMEOSBIN)" should be doable too.
In C the system() function is used to execute a command in the terminal so if you execute the "GAMEOSBIN" file directly in the terminal, it should in theory do the same thing, you could look in the source for the exact path stored in the GAMEOSBIN variable & try to execute it in the terminal.
 
Does this method works for a PS3 Slim without NOR dump? I tried installing CFW on a CECH-3011A model only following said steps for installation and I didn't create a dump, so I bricked it. Should I have hope on fixing it or should I give up? The console has no sentimental value since I bought it at a flea market for $10USD not too long ago.
 
DesGeek said:
Does this method works for a PS3 Slim without NOR dump? I tried installing CFW on a CECH-3011A model only following said steps for installation and I didn't create a dump, so I bricked it. Should I have hope on fixing it or should I give up? The console has no sentimental value since I bought it at a flea market for $10USD not too long ago.
Click to expand...
you would need a hardware flasher to make a dump. then you can repair it.
 
You must log in or register to reply here.

Similar threads

Back
Top