- Install the package to PS3
- Select a Fake signed SELF from the menu and press X to launch.
- Enjoy.

Limitations:
The SELF you are launching must be "fake signed" for it to launch, if not it will bring you back to XMB,
This is good for quick testing your development/test builds without repacking to a PKG every time.
Future support will be added for non-signed SELF/ELF's

- This tool installs BootOS, which can be used to boot Linux kernel from lv2patcher v9.
- v2.0 is made by kmeaw and kha0S.
- It allows you to install unmodified Debian Squeeze.
- Full support to installation on External Hard Drive/Pen Drive. No PS3 disk installation for now.
- All needed PS3 specific kernel modules are already pre-compiled and installed.
- PS3 vram is enabled as swap as default
- Thanks to marcan for AsbestOS, Mathieulh and graf_chokolo for default.spp trick, geohot for dev_flash mount code.
- Thanks to jbc for testing and KingDong for the icon :)
- Now it works on PS3 fat.

This tool is used on 3.55 firmwares only for installing linux proposes. Use only if you known what you are doing. Use at your own risk.

It's a clone of JaicraB's USB FIRM LOADER, with a few differences for people like me with USBs that have different numbers. Major Features: Choose what USB to use, Redirect dev_flash to usb, Redirect app_home to usb, Dump LV2 kernel and mount points.

Changelog:
2.0
- The first version had a stupid "bug" that does not allow you to use the online pass purchased. Sorry for that..

1.0
- Inital release

How to:
- Start Change_IDPS and wait for the refresh of the console

IMPORTANT NOTES:
- Change_IDPS must be started after every reboot of the console before groped access to PSN and PS-STORE (if you do not get an error: 8002A224)
- Check in the debug menu settings (it's under Network Settings), the NP Environment setting is set as np (not sp-int)
- L'IDPS is set in automatic mode (depending on your region (EU, USA, etc.).
- When the Change_IDPS is functioning properly, the LED will switch on the console from the usual green color to YELLOW

This little tool lets you make some magic in your machine.
It lets you change your MAC Address FOREVER, easy, uh?

Procedure:

a) Put a pendrive / external hdd, for example, in any usb port (app search for it).
b) Now you have 2 options:
- Dont put any file in the usb unit.In this case, the program will use a special mac address (Air Address)
- Or put a file called "mac.bin", this file will be your new mac. You need put inside in binary format
your 6 bytes of your new mac, for example, DE 11 00 11 4A DE.

c) Install app, and launch it.
d) The program will try make a backup of your old mac in the usb unit as "mac_original.bin".
Remember take it in some secure place before launch again the program or will be overwrite and you will
lose your original value, perhaps forever...i dont know.

e) Wait to the program returns to the xmb or reboot.
If not reboot auto, reboot manually the PS3, and you will see the changes forever.

f) Its all folks!

NOTES:

a) You need SS patches enabled to use it, if not perhaps you will have problems because lv1 dispatch manager
blocks your service requests.
b) If the program CANT make a backup of your old mac, led will blink in red.
c) If the program CANT change your mac, the led will remain off (if you reboot your machine its will revert to green)
d) If the program CAN make a backup or your mac led will blink green.
d) If the program CAN change your mac led will be off and later green.
e) I tested it and works as a charm, but remember that you only take your choices with your machine, not blame me
if you fuck something.
f) Its not change any value at the ram (lv1, vsh or lv2), the change is real.
g) You can change in a custom firmware, and later update a official firmware and your mac will remains changed.
h) This program will be a plugin in JFW DH 3.41

USES:

The mac change is real, its have a lot of uses, as example:

a) Make funny stupid videos of "new firmwares" without hide your mac (stupid use, but well, a lot of people is stupid and live in dark hole places...:)).
b) Make a true use avoiding that your mac can be banned, or in a legit video that your machine appear as it.
c) Spoof your mac to catch wireless conections that have mac auth list, and use this wireless connection (yeah, Chaos Air Bringer).
d) A lot of uses that your imagination can have...

You need to create a folder on the root of your USB stick called coldboot. This where you place your custom coldboot files.

Coldboot Installer can also back up you current coldboot files. It backs them up in the app’s USRDIR and to the root of USB000 if present with a .bak extention.

Warning: this app changes dev_flash files. Use at your own risk

Note: The rebug packages are provided as a mirror in case they are unavailable and for historical proposes. You should support rebug development by visiting Rebug's website and downloading from there: http://rebug.me.

- create a directory in your /dev_usb000/ called "plugins"
and put all your sprx plugins into, it should be
/dev_usb000/plugins/prx_name1.sprx
/dev_usb000/plugins/prx_name2.sprx

....
All of the sprx that are present in this folder, will be loaded at ps3 boot.

-There is no max sprx number that can be loaded, the only limit will be the memory available, this is important, if you load to many sprx, some games will refuse to load.
-SPRX will be injected into vsh process, therefore they will be runned at every moment(even during a game).
-Deank made a cool FTP server sprx, that you can load into VSH, so you have a ftp even while you're playing a game. I just patched it for CCAPI. Or use webMAN 1.44 for CCAPI,

How to install CCAPI?
-----------------------------
Just download and run this pkg on your ps3.
CCAPI_2_80_REV3_Package_dev.rarIt will tell you to reboot, and it's done. You only need to do this once.

How to uninstall CCAPI?
----------------------------
Just run again the pkg.

Is it risky?
No, in the worst case, you could need to reinstall your firmware.

Quick control console:
It's just a quick tool to use some of CCAPI functions.

2.00:
- Memory use has been reduced
- Boot time has been reduced too, at the first load it's about 20 sec, then for next boot it's now instant.
- Shoud be compatible with more fimwares now.
- DLL is now released, you can now make your own ccapi programs.

Control Fan Utility is an application that let you set the speed of the fan for your PS3 console or install a payload that runs behind games and controls the fan speed to keep the temperature under a certain reading.
The utility is intended to work on CFW CEX/DEX 3.41, 3.55, 4.21, 4.30, 4.31, 4.40, 4.41, 4.46, 4.50, 4.53, 4.55, 4.60, 4.65, 4.66, 4.70, 4.75, 4.76, 4.78, 4.80, 4.81, 4.82,4.83

Note: USB Flash Dump v1.0 is an exact copy of Glevand dump_flash only with icons changed.

INSTRUCTIONS
===========
1.install dump_flash.pkg
2.plug a usb stick with enough memory into usb001 (your ps3's first usb slot)
3.run dump_flash
4.your ps3 will black screen for about 2 min at the most for NOR based consoles then your console will beep and reboot itself back to XMB.
(dont worry just be patient let the tool work and dont power off the console for the risk of bricking).
For those of you who are using this on a NAND based conosle i have no clue how long it will take to dump so just be patient and let it work and dont power off for risk of bricking.
5.once the dumping is complete and your console has rebooted you can unplug the usb and go to your computer once at your computer open then usb folder and you will find a nice little file called flash.bin that is your consoles NOR/Nand flash (have fun)

To ensure you have a proper nor Dump it must be exactly 16.0 MB (16,777,216 bytes)

RCOs are a bunch of xml files encrypted together,
you can mod these with RCOMage and make custom strings on your xmb.
RAFs are Video files. the only one that is a raf is coldboot.raf, which is the boot logo. Can be made with ColdBoot Maker. Tutorial Here.
AC3s are of course audio files, which is the boot sound.

Homebrew train is on its way.
BACKGROUND
RCOs are a bunch of xml files encrypted together,
you can mod these with RCOMage and make custom strings on your xmb.
RAFs are Video files. the only one that is a raf is coldboot.raf, which is the boot logo. Can be made with ColdBoot Maker. Tutorial Here.
AC3s are of course audio files, which is the boot sound.

I might make a tutorial on modding RCOs for noobs if i receive some positive feedback.

CUSTOMIZE

To Customize
1. put flash drive into computer and make the folder structure of customize/modz(example F:/customize/modz)
2. put all your customized files in that folder.
3. make sure all the names of the files are the same as the orginal(case sesitive)
4. copy ES35's Customize v0.1.geohot.pkg to the root of your flash drive (example F:/)
5. put that flash drive into the ps3, and go to install pkg files.
6. install ES35's Customize v0.1.geohot.pkg
7. scroll down to ES35's Customize v0.1
8. observe the great graphics of the icon and background image, and remember to donate.
9. open it, and click install.
10. quit.

To Clean up
1. Open it, press the up and down dpad buttons to scroll to clean it up.
2. press X.
3. quit.
CLEANING DOES TAKE AROUND 30 SECONDS.

In keeping with our Red Valentines theme this month... we release another red themed app.
Tonight, in our second release we bring you a second handy app that continues our
commitment to the removal or the need for ANY dongles. A simple app that should likely
make it into everyone's PS3 tool set. An XMB application that places the PS3 into factory
service mode. Now, You can now throw away that downgrade dongle! Also, as an added bonus
we've included CEX and DEX versions of the pkg.

Psgrade was ported to all sorts of devices, even calculators ... none of those external
devices are needed any longer! You may now re-purpose them!

Usage:
------
When you run the app it will beep once and reboot if successful. Three beeps indicates a
failure, report the contents of factory.txt in this thread for help. (Factory.txt will
save to the USB flash if you put on in the right most USB port of the PS3.) At this point
you will come back up in Factory Service Mode (FSM). Place the Lv2Diag.self on the USB the
Lv2diag.self will perform its intended purpose automatically. So be aware of that feature
should you not be expecting the PS3 to boot back into the non-FSM XMB.

This app will not work on any of the "reDRM" firmwares, aka Cobra or TrueBlue CFW.

1. Install the appropriate pkg for your system; FactoryServiceMode.gnpdrm.pkg for CEX and
FactoryServiceMode.pkg for DEX. Leave the USB Flash Drive in the PS3.
2. Run the app and listen for the single beep, you should enter FSM automatically.
3. rename/copy the Lv2diag_exit.self on the root of the FLASH Drive to Lv2diag.self
Note: This release simply exits FSM. Do NOT use the RSOD Lv2Diag released earlier unless you have RSOD.
4. Place the USB Flash Drive in the right most USB port of the PS3.
5. Restart the PS3. When it boots up, you will be out of FSM.
5. Enjoy sticking it to the dongle makers in your own little way.

Information:
------------
The app detects the firmware you are running on so it should work on all the firmwares
supported by "one" previously. (3.15, 3.41, and 3.55. Basically, Ones that are lower than
3.56.) During creation of this tool, the open-source ps3toolchain, and a slightly modified
make_self were utilized. All code is original and makes use of no previously released or copyrighted
code, this Lv2diag.self is made 100% with the PSL1GHT SDK so it can be shared freely and without
concern for breaking any laws in your country. So, "no sony code inside!"

FAQ:

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.

When the program starts you will see the typical intro screen, if you choose “Yes” you will see the data from your PS3, if sounds three beeps indicates that it was not possible dump and show the error message, and if all went well sounds a beep and you are able to see the data

Automatically saves the IDPS in dev_hdd0/IDPS.bin, you must open it with a hex editor and look hexadecimal values, for example (IDPS false, I will not reveal my IDPS):

IDPSet is a tool to make CEX and DEX dump and you can permanently change your console IDPS (NAND and NOR) and change the PSID too. You just have to run IDPSet on your CFW (with eid_root_key and valid idps.bin on the root of your USB key).

It can generate a DEX and CEX dump of the current NOR/NAND that is compatible with the REBUG switch CEXDEX function. Easy to use, Windows is not needed!

In this tutorial PS3ITA will guide you with all the necessary steps to achieve the "dummy_bdemu" directly from the console. This procedure is useful to all users who use a CFW DEX (debug / test) on a console that has the blu-ray disc broken or simply for those who do not want to wear the player's lens for intensive use.

In fact, the "dummy_bdemu" is to appear on the XMB icon BD player despite the absence of the disc, increasing, therefore, the compatibility of our backups are initiated by the backup manager multiMAN.

Below is a comprehensive guide designed, documented and tested in detail on CFW 4.21 PS3ITA DEX:

Disclaimer: Attention! PS3ITA assumes no liability arising from incorrect use of these procedures and for any damage that the console could suffer. Use the procedure at your own risk!

Disclaimer 2: Warning! PS3ITA not instigates and does not support piracy in any way, the procedure is posted only to illustrate the operation of the emulator of BD player in a console for DEX then start the games legally purchased!

Part 1: Guidance on the preparation.

Console (NOR \ NAND) with any CFW DEX (the entire tutorial was tested on CFW 4.21 PS3ITA DEX)
A usb stick formatted in FAT32 with at least 3mb available
(If you prefer you can do before a disk partition using a PC, consider that this key will be connected to the console every time you want to emulate the BD player)
Last backup manager multiMAN
PKG Install_Fake_BDEmu be installed on a console with DEX cfw:

Part 2: Creating the "dummy_bdemu."

Step 1. Download the PKG Install_Fake_BDEmu
Step 2. Enter PKG just downloaded into your USB stick formatted in FAT32:
Step 3. Enter the same usb stick formatted in FAT32 into the USB port of your console and install the PKG from (XMB) -> (Game) -> (Install Package Files):
NOTE: The following steps format your usb stick formatted in FAT32 in a format recognized only by your debug console and not a PC, this will take only 3mb of total capacity, if you want to go ahead and make the first partition a disc using a PC
IMPORTANT: After the first run of PKG you should not delete it. E 'can recover formatted data on your USB stick when started for the second time ... the choice is yours!
Step 4. Choose your USB stick formatted in FAT32 (this usb stick must always remain connected to your console every time you want to emulate the BD player), put it in the far right of the console port:
Step 5. Start now PKG "Install Fake BDEmu"
Step 6. After refreshing the console you will notice that your pen drive is no longer recognized as a removable disk (procedure performed correctly) and the application "Install Fake BDEmu" has turned into "Remove Fake BDEmu (second confirmation of procedure performed correctly):
NOTE: From now on your USB stick is formatted in a format recognized only by your debug console (with certain settings) and not from a PC.
IMPORTANT: You should not delete the application "Remove Fake BDEmu" if you want to recover formatted data on your USB pen ... the choice is yours!

Part 3: Debug settings and use the emulator.

Step 1. Go to (XMB) -> (Settings) -> (Debug Settings) -> (Blu-ray Disc Access) and set "BD Emulator (USB)":
Step 2. Then go to (XMB) -> (Settings) -> (Debug Settings) -> (Transfer Rate Pacing for BD Emulator) and set "HDD Native"
Step 3. Now for the changes to turn off the console and paying particular attention to leave the usb stick into the port on the right (the one previously formatted USB stick from the "Install Fake BDEmu", see Part 2 to Step 4).
Step 4. Check that your BD player is properly emulated (XMB) -> (Game):
Try to start well, as standard procedure, a backup of your game (also from external hdd) through multiMAN ... you will notice that the backup has been successfully emulated icon of your BD player in turn also emulated above (despite the absence of a disc inserted in the drive)!

IMPORTANT:
Before you turn on the console, remember to always insert into the USB port further to the right the usb stick created to emulate the player (if inserted after power will not be recognized).
At a later time if you do not want to emulate your reader with this pen usb remember to reset it with the application "Remove Fake BDEmu" to restore any of the data originally present on the USB stick.
When you do not emulate your reader with this pen usb remember that you have altered settings 2 Debug (see Step 1 and Step 2 Part 3), check whether to restore or not.

Problems when installing game updates? JuicyFix patches the correct offset that should fix game updates/patches with certain titles using "lv2open" instead of vsh open. Run this first, then run your game that requires an update. Depending on the game it may or may not work.

Just install and execute. once executed the patch remains until next gameos reload/reboot

ps3-hacks.com description:

Problems when installing game updates? JuicyFix patches the correct offset that should fix game updates/patches with certain titles using "lv2open" instead of vsh open. Run this first, then run your game that requires an update. Depending on the game it may or may not work.

Mathieulh's advice:

Some game updates use lv2open to check the disc's param.sfo to make sure the right disc is in the drive and the check fails because psjailbreak patches only patch the vsh open, as such a lot of patches will ask to "insert" the disc if you are playing from a backup, I don't care much about backups myself but for the sake of it and because some people may actually do a legit use of them, here is the patch.

Someone actually pointed out that the check uses the same fs function than the one psjb patches (my mistake on that one) for some reason though, the sfos' title ids do not match which is what the patch I released earlier "fixes"

this will change the led color and if it is on mode on/off/blink and it will keep it on that mode also on the XMB
for example now my ps3 has green and yellow together while blinking
-----------------------------
This is a completely new version of Led Changer.
The app allows you to change the colour of your system's LEDs (the power light) and keep it also on the XMB or while playing games/homebrews.
This is NOT permanent; the first time that you turn off your PS3, the led will go back to normal
This version does NOT need any kind of external drive. all you need is a JoyPad; just it.
Now the app is Lighter (from ~1.2 Mb to ~145Kb), Faster, for all TVs (HD/SD) and Easier to use.

After the “success” of luafwii, I decided to port it to PS3 and take two parallel developments. For those who do not know LuaFPS3 LuaPlayer for PS3 is that is allows you to run homebrew lua made ​​in your ps3.

Author: the_marioga

What is Lua?
Lua is a programming language, simple and powerful, that does not require to be compiled to run it.

What can you do this lua player?
Show pictures, shapes, display text, data collected and SIXAXIS DualShock3, among other things. Very useful and powerful when programming simple video games.

The features are on file in the RAR reference.html

What changes will be in the next version?
Management functions of files and folders
ImageLoadinOne removed (obsolete)

Features:
-Texture loading (currently only supports BMP)
-Onscreen text rendering
-Controls (including sixaxis and joysticks)
-Screenshots
-All standard Lua functionality (with the exception of the OS functions)
-PC emulator that can be used to test scripts before you run on the ps3 (Linux, Mac and Windows binaries included,
if you are using the windows binary and get some missing dll messages, those dll's are in the "compat DLL's.zip" file in the emulator folder)

Update:
LuaPlayer is updated from Lua 5.1 to the last Lua version 5.2.3.

The used library for sound is Estwald's (aka Hermes) nice spu sound library.

The other great library from Hermes, tiny3d for 2D and 3D grafics is also added.

Download the player + some tiny3d samples by Hermes, ported to Lua scripts:
LuaPlayer.rar (mediafire)

PS3 LUA Player psl1ght-v2 port by 3141card

Found time to read how LUA work, more exact, how library code like a SDL interface can be added. It is very simple.

I add e.g. TTF-font support, a sys-font in the example. But I am really not interested in LUA. Maybe someone
here have time and pleasure to add things like sound (from psl1ght or SDL) and other things to the LUA Player.

- Compiled with psl1ght 2 and signed for 4.xx
- The app search for "/dev_usb000/app.lua",
- Change nothing on lib code, fix only the usual path/name probs for psl1ght vs psl1ght-v2

LuaPlayerPS3 beta 1.0 Written by jonlimle
XMB icons created by yamagushi

Current Features
-Texture loading (currently only supports BMP)
-Onscreen text rendering
-Controls (including sixaxis and joysticks)
-Screenshots
-All standard Lua functionality (with the exception of the OS functions)
-PC emulator that can be used to test scripts before you run on the ps3 (Linux, Mac and Windows binaries included,
if you are using the windows binary and get some missing dll messages, those dll's are in the "compat DLL's.zip" file in the emulator folder)

How to use
-copy everything that is in the "Copy to USB root" to the root of your USB drive
-install the pkg as you would any other pkg
-all files that you attempt to open from lua must be on your USB drive
-any scripts that you make, must be on the root of the card, and named app.lua

-when testing the scripts in the emulator, it will load app.lua in the same folder as the binary, all files that you attempt
to load should also be in that same folder

this release comes with an example app.lua which shows a few of the features of which you are currently able to do

when using the emulator, the keys are mapped in the folowing way

up = up arrow
down = down arrow
left = left arrow
right = right arrow

triangle = w
square = a
cross = s
circle = d

start = enter/return
select = quote key (")

R1 = Right shift
R2 = Right control
R3 = question mark

L1 = Left shift
L2 = Left control
L3 = z

There is currently no emulation of the joysticks or sixaxis in the emulator

if you have any questions, comments, or requests you can post them wherever you downloaded this from, or you can also find me on irc in #luaplayerps3 on irc.freenode.net

Commands
========

--GRAPHICS--
- InitGFX(width, height) this must be called before you can call any other graphics related functions, for example, if your tv was 720p you would call InitGFX(720,480)

- beginGFX() this must be called before you can begin drawing to the screen

- DrawText(x, y, text, surface) this will print text to the screen, x is the x posistion on the screen, y, is the y posistion, text is the text you want to print
and surface (see information on surface below) is the surface that you want to print the text on to, if you do not give it a surface, it will print to the main screen

- DrawCircle(x, y, size, r, g, b, alpha) this will draw a circle on the screen, x is the x posistion on the screen, y, is the y posistion, size is how many pixels wide you want the circle to be, r is the level of red for its color, g is the level of green for its color, b is the level of blue for its color, and alpha is for the
alpha :P

- BlitToScreen(surface) you must call this on every surface that you want drawn onto the main screen (see definition of surface below)

- endGFX() this must be called after you have drawn everything wanted onto the current frame

- Screenshot(filename) Saves a screenshot (bmp format) to your usb device, filename = name of file to be saved

--SURFACE--
a surface currently only holds a texture (only bmp format supported currently)
you must initialize surface by calling surface() for example ...

mySurface = surface()

you must initialize the suface before you can start using any of its methods, from here on, we will be using "mySurface" as the example for the method definitions

- mySurface:LoadIMG(bmpfile) this will load a bmp image file into "mySurface"

- mySurface:setRectPos(x, y) this will set the posistion on the screen where "mySurface" will be drawn, x is the x posistion, and y is the y posistion

- mySurface:getRes() this will return the width and height in pixels that the surface will take up, you need to call this in a way similar to...
mySurfaceWidth, mySurfaceHeight = mySurface:getRes()

--CONTROLS--
- initPads(num) you must call this before you can begin reading any keys num = the number of pads you want, 7 is reccomended

- setsixaxis(padnum, enable) you must call this before you can use any of the sixaxis functionality padnum is the pad that you want to enable/disable sixaxis on
if there is only one pad, you would use 0 for padnum, enable is weather you are wanting to enable or disable it, if enable, use 1, or 0 to disable

- up(padnum) returns true if the up button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- down(padnum) returns true if the down button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- left(padnum) returns true if the left button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- right(padnum) returns true if the right button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- triangle(padnum) returns true if the triangle button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- square(padnum) returns true if the square button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- circle(padnum) returns true if the circle button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- cross(padnum) returns true if the right button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- R1(padnum) returns true if the R1 button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- R2(padnum) returns true if the R2 button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- R3(padnum) returns true if the R3 button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- L1(padnum) returns true if the L1 button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- L2(padnum) returns true if the L2 button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- L3(padnum) returns true if the L3 button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- start(padnum) returns true if the start button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

- select(padnum) returns true if the select button is pressed, and false if it isnt, padnum is the pad which you want to check, if only one controller is connected use 0

LV2 Loader is a tool for devs to allow the quick testing of modified lv2_kernel.self by launching it from the root of dev_flash without the risk of bricking the PS3 or need for a flasher if the new kernel does not work.

The app will run on any 3.15, 3.41, 3.55 CEX or DEX firmware that has lv1 mmap and lv2 peek and poke patches. It also has udp_printf support which will return the offset of the lv2 boot path in lv1 and a little bit of info about what it is doing.

It works by searching lv1 memory for the lv2_kernel.self boot path then modifying it to point to the root of dev_flash instead. After it finishes searching and patching the path LV2 Loader will reboot lv2 gameos without rebooting lv1.

If the app has already been ran once and the user attempts to run it again before rebooting lv1 or the current lv2 kernel does not have peek and poke it will return you to the XMB.

Note: The rebug packages are provided as a mirror in case they are unavailable and for historical proposes. You should support rebug development by visiting Rebug's website and downloading from there: http://rebug.me.

LV2 Loader is a tool for devs to allow the quick testing of modified lv2_kernel.self by launching it from the root of dev_flash without the risk of bricking the PS3 or need for a flasher if the new kernel does not work.

The app will run on any 3.15, 3.41, 3.55 CEX or DEX firmware that has lv1 mmap and lv2 peek and poke patches. It also has udp_printf support which will return the offset of the lv2 boot path in lv1 and a little bit of info about what it is doing.

It works by searching lv1 memory for the lv2_kernel.self boot path then modifying it to point to the root of dev_flash instead. After it finishes searching and patching the path LV2 Loader will reboot lv2 gameos without rebooting lv1.

If the app has already been ran once and the user attempts to run it again before rebooting lv1 or the current lv2 kernel does not have peek and poke it will return you to the XMB.

PREPARATION:
Using FTP or multiMAN/file manager place your modified lv2_kernel.self into the root of dev_flash on your PS3.

HOW TO USE:
1: Install lv2_loader.pkg
2: Run LV2 Loader from XMB
3: PS3 will beep and reboot. (If you do not hear a beep it has not worked)

NOTE: As long as you do not reboot lv1 you can continue to use the new path and change the lv2_kernel.self each time if you wish.

F.A.Q:
Q: Can LV2 Loader boot DEX lv2_kernel.self?
A: YES. It will require your PS3 to be QA flagged. Don’t be fooled though. Just because you can boot the DEX lv2 kernel does not mean it will magically function like a DEX. For that to happen it will require more patching but this certainly makes the road easier to figuring it out.

Q: Can LV2 Loader boot lv2_kernel.self from a higher firmware?
A: In testing, booting a 3.56 lv2 kernel resigned for 3.55 worked without any problems. Keep in mind that amongst other things, the ps3 is still using the lower firmware’s appldr so there is no real advantage to doing this at the moment.

Q: Can this brick my PS3?
A: NO, NO, NO. The whole point of LV2 Loader is to prevent this from happening during your development of lv2 patches.

Q: Isn’t the offset for the lv2 boot path the same for all PS3?
A: NO. In testing on five different PS3 we came across seven dramaticly different offsets. Infact one of the PS3 at one stage or another in testing used four of the same offsets as the others and has now returned to the original offset from when we started.

Q: How do I reboot the PS3 without rebooting lv1 hypervisor?
A: Using glevend’s Reboot app will let you reboot the PS3 and maintain the modified lv2 boot path. As a bonus for REBUG users when changing modes with Rebug Selector the PS3 will reboot from the new path as well.

Q: As a user of REBUG firmware, if I boot the DEX lv2 kernel does that mean I am running DEX firmware on a retail PS3?
A: YES. REBUG uses the entire DEX firmware apart from 3 or 4 sprx (to allow QA flag support mainly) and uses the CEX lv2_kernel.self. Booting the DEX lv2_kernel.self will in effect, complete the set.

Enjoy.

~ Codename: REBUG

Credit and Thanks:
As always to graf and glevend for the hypervisor work.
Big thanks to Dean for the handy memory mapping tip and adding support for LV2 Loader into multiMAN at the last minute.

This application will dump all accessible LV2 memory on a
jailbroken retail PS3.

To run this app, place lv2dump_07a.pkg on a usb memory
stick. Install the pkg. Then run LV2Dump from the XMB.
It should run for approximately 20-30 seconds, then it
will exit back to the XMB. There will now be a file named
LV2.BIN in the folder /dev_hdd0/game/

You can access your dump by copying the file out with your
own code, or the FTP application.

Before attempting another dump, delete the LV2.BIN that
is in /dev_hdd0/game/ as the next dump will append to the
file if it exists.

The dump is right around 8MB - which will let you take a
look at the PS3's kernel.

For all of you out there intereseted in, or already in the process of reverse engineering the PS3, this new tool will make your life a whole lot easier! Now you can dump LV1, LV2, AND/NOR Flash and eEID from one tool! There have been methods in the past that accomplished the same goals, but certainly the ease of use and speed hindered many. Of course, none had such a beautiful user-interface either.

This application allows the mounted one of the /dev_Alejandro unit. This unit is a mirror of the /dev_flash unit, being this active one also.

The /dev_flash unit lacks permissions of writing, useful to read like towards formerly, nevertheless the new one, IF it has writing permissions.

It is for this reason, that we do not become people in charge of the evil use that can be given this application, to the used method, etc. As end users YOU ARE RESPONSIBLE FOR the USE THAT YOU DO OF THIS PROGRAM IN YOUR MACHINES!

FLASH WRITER ENABLER:
------------------------
This application allows the mounted one of the /dev_Alejandro unit. This unit is a mirror of the /dev_flash unit, being this active one also.

The /dev_flash unit lacks permissions of writing, useful to read like towards formerly, nevertheless the new one, IF it has writing permissions.

It is for this reason, that we do not become people in charge of the evil use that can be given this application, to the used method, etc. As end users YOU ARE RESPONSIBLE FOR the USE THAT YOU DO OF THIS PROGRAM IN YOUR MACHINES!

To have it in account before wanting to manipulate firmware, archives XML, etc.

Here's a small app I made in a few minutes. It's completely untested as I have no access to a PS3 until Monday and thus may not work at all, so feedback would be appreciated.

It uses the SynaPS3 library, even though it only uses 1 function from the library. No harm in self-advertisement for my (baby-stage) library?

Jaicrab's Loader was made when we still had to use peek/poke to remount directories. We now have syscall8 (hermes) and syscall35 (PL3) for remounting directories. This makes things much easier.

This loader is universal and works with both Hermes and PL3.
Create a folder called "cfw" on the root of your device and place the "dev_flash" folder inside it. Then create another folder called "cfw" INSIDE your "dev_flash" folder.

It supports CFW on your harddrive, so once you have a "finalized" build of your CFW, just throw it on hdd0 and run the app on start!

Along with mounting your dev_flash, this app will also dismount your cfw the next time you run it.*

It checks for the "cfw" folder on the following devices (in this order, meaning bottom devices take priority):

hdd0
ms
usb00x (1 through 7)

Source is of course included, and so is a compiled .pkg (hosted offsite as it is built with Sony SDK).

AsbestOS is a Linux bootloader that runs off of the PS3 Lv-2 USB exploit. It is designed to boot on PS3 systems running System Software version 3.41, though it could be adapted to earlier versions. Linux runs on the GameOS partition, thus having the same access to hardware that GameOS has.

Ok after many days of hard work and get help from every where. The new Loader is out of Beta. Has a new Name again, sorry. This time it does not require Hermes' Payload at all, you can still use it. You do require peek/poke in your payload though. And is Now $ony Free, thats right folks no more $ony SDK. it runs on PSL1GHT and ps3chain.

For some reason it does not work with Fat PS3s. i think its due that we are still on the old kernel. i will working hard to get it working with the new kernel asap. you are also required to be on firmware 3.41. other then that here is the README and link at the Bottom

To all that have donated thanks you have help me start to get my teeth fixed. i go back in two weeks for the doctors to look again. its free but the doctor is two hours away. so with funds tight, your donations help pay for gas and such. Thank yall from bottom of my heart.

And i also want to say thanks to Ceal for testing the shit out of this as fast i could pop out a new prototype she was there to test. thanks
here is the README

AsbestOS Open Loader README

== Introduction Requirements==

This a AsbestOS Linux bootloader that runs off of the PS3 Lv-2 exploit.
It is designed to boot on PS3 systems running System Software version 3.41, though it could be adapted to earlier versions. Linux runs on the GameOS partition, thus having the same access to hardware that GameOS has. This code is experimental and is intended for those who have a 16KB USB dongle and no possibility to launch asbestOS in other form. does not require you to be using Hermes' 4vB payload!!!! *It also requires you to be using Hermes' 4vB payload this is a typeo fixed here in the read me to lazy to upload again to compile is best to be using linux, as i have not tested on windows

== Building ==

The PS3DEV environment variable needs Setup

$ mkdir ~/ps3dev // I Find in my user drive i have no permison problems
$ mkdir ~/ps3dev
Add these to the end of you ~/.bashrc file

Then Read the readme under both those drives and compile how they lay out.
rember we have already set the PS3DEV and PSL1GHT vars

== Usage ==

First compile AsbestOS Loader get a compatible USB exploit mechanism.
You should also connect your PS3 and PC to a network not the internet.
(they need to be in the same broadcast domain also)

P3

Do nothing but plug into your router

PC

there is where everyone seems to have the trubble. i have created a easy setup guide for the NFS share. Read HowToNFS. if you cant do this becuase your in windows run Virtualbox with your fav linux. bridge the network cards under VM setup and then continue with the Guide.

Transfer the AsbestOSHybridLoader.pkg (that you compiled ) to the root of a thumb drive At this point if you have edit you own dtbImage.ps3.bin (marcan's kernel image included under xdata) Copy them to the root of you usb thumb drive.

Fire off the exploit device, turn on your PS3 using power followed by eject within 0.2 seconds .

Install the pkg AsbestOSHybribLoader.pkg.
OK now find the penguin and run the Program.

\

Ok the scary part the screen goes black.it....Wait for it....If you get anything at all, congratulations, Kernel is running. At this point, if you have any issues, the problem should be fairly apparent from the messages (Kernel panic NFS not mounted). If not then there could be a cupple things wrong. There has been reports that there is a issuse with SD tvs. I can not comfirm because i do not own a tv.I happen to run mine to a Monitor with a HDMI > DVI cable. There are also been reports of it not working on Phat PS3s. as im not sure about this (one friend told me it worked on his phat),

Once the PS3 is up and running and your NFS share.you should now have a Working AsbestOS. to find out more about AsbestOS got to marcan's blog http://marcansoft.com/blog/ You Can Contact me at my blog http://margatz85.blogspot.com/

And i want to say thanks to Ceal, Marcan32, KaKaRoToKS, Hermes, ooPo, AerialX, Mathieulh, Aaron (the guy who started PSL1GHT) and who ever i missed. with out any of yall i wont have been able to do what i do. Thats have fun and use my toys the way i want

MrGatz85

== ToDo ==

spell check every thing (ROFL i cant spell sorry)
Keep up with the latest kernel and patchs.( We will have HDD support soon)

This was one of the first programs for the PlayStation 3 that was created by indie game developer ThatOtherPerson. This is neither a game nor an app, but rather a simple test pkg to try out different functions on the PS3.

Its a simple but sorta nice little demo. Its in 3d (meaning polygonal not 3D TV kind of 3d) and you can move the camera with the analog sticks. It doesn't seem like anyone has posted it elsewhere so if anyone wants it you can get it here. I reused the package.conf, package.sfo and ICON0.PNG from Lachrymose's pong game so it will appear as pong in the xmb and if you have that installed it will get overwritten.

PS3Load allows you to run SELF programs (homebrew) over your wireless or wired network; it uses Wiiload, for those familiar with it and the Homebrew Channel. To use it, simply run Wiiload (download) with a .self file, and point it to your PS3's IP address.

PSL1GHT has come a long way since I started it last week as a temporary stop-gap while waiting on trap15 to work on PS3DK. It's quickly become incredibly feature-filled, and it's already possible to create full applications with it!

Two days ago, PSL1GHT received network support. Just today, PSL1GHT has received SPRX module linking support. SPRX modules are dynamic libraries already installed on your PS3; they provide all the game functionality like setting up the display, managing the controller, playing audio, etc. Now that we can use these, we get all sorts of useful functionality on the PS3! (If anyone's interested, we still could use some devs to come and help us fill in the SPRX headers and stubs)

As an example I wrote a program called PS3Load. PS3Load allows you to run SELF programs (homebrew) over your wireless or wired network; it uses Wiiload, for those familiar with it and the Homebrew Channel. To use it, simply run Wiiload (download) with a .self file, and point it to your PS3's IP address.

PS3Load is included in PSL1GHT's samples, but I've also attached a precompiled version to this post. For the ultimate fun, ps3load ps3load into ps3load so you can ps3load while you ps3load.

Nov. 1 Update: It seems that a number of people were having problems with the first pkg I created, so I've uploaded a slight bugfix.

setup is as follows:
* Grab HackMii from the 'net, unpack it and use/copy only the WIILOAD part!
* Run the WiiLoad on your PC
* Assemble the PS3LOAD.self into a Package (or wait until it is done for you!)
* Install/Run the PS3LOAD app on your PS3!
* Use Wiiload on your PC, to send and launch your other PS3's selfs!

Change log:
0.2 - 4.xx (unknown)- Repacked to work on all firmwares

0.2 - 3.55 (an0nymous)- It seems that a number of people were having problems with the first pkg I created, so I've uploaded a slight bugfix.

You can load SELF files using the net.
You can load applications from USB/ HDD devices
You can install applications to the USB or HDD devices from one .zip file
You can copy applications from USB devices to HDD
Also you can delete installed applications.

You can load .ZIP files via tcp using the network, just like the SELFs.
An “install” folder will be built into your [USB/HDD root: Homebrew] Folder and contents shadow copied to PSL145310/homebrew/install.
The”install” folder can be added manually as-well, if no network loading is to be used.
Programs will be displayed in PS3LoadX and buttons commands will be available accordingly.

1.1 - 3.55 (CondorStrike)- Only fixed the spawning issue to make it work on 3.55 CFWs
- added a new ICON0.PNG, cause I hate that PSL1GHT logo, but left the binary intact
- also added a PIC1.PNG, SND0.AT3, and PARAM.HIS.

1.1 - 3.41 (hermes)PS3loadX is my personal evolution of PSL1GHT PS3load sample, using now the Tiny3D library. I hope this version helps to you to work easily ;)

- You can load SELF files using the net.
- You can load applications from USB/ HDD devices
- You can install applications to the USB or HDD devices from one .zip file
- You can copy applications from USB devices to HDD
- Also you can delete installed applications.

NOTE:
-----
You can include this lines in your app to return to the PS3LoadX application

Sending SELF files from the net
-------------------------------
You need send it from the PC using psloadx.exe (see PSL1GHT tools)
For example from one .bat file under windows:
set PS3LOAD = tcp:192.168.2.12 // -> PS3 IP
ps3load.exe *.self
pause

Installing ZIP files
--------------------
HDD0 is selected by default. To change to USB you need plug one device.
When you send a ZIP file the app ask to you if you want really install it or not in the current device.

Select one Application
----------------------
Use LEFT/RIGHT in digital pad

PSID is your playstation's unique identifier to Sony, this program will patch the loaded PSID in memory to one of your choice. This won't permanently patch your PSID, but *MIGHT* let you fool PSN. Best way to test this is for somebody with a banned PS3 to try changing it and going online.

PSIDPatch 1.6
-------------
Updated PSIDPatch 1.6, seems there were 2 extra places in Lv-2 where your ConsoleID is stored that I didn't notice, now PSIDPatch changes them too.

Updated PSIDPatch 1.5, now it can also change the Console ID sent to PSN, although if the ID isn't valid you'll get a nice 8002A224 error.
Included a sample consoleid.txt file too.

Updated PSIDPatch 1.2 for 3.55 consoles. SELF is signed and the package is "signed".
1.2 also lets you generate a random PSID now, no need for txt files :)
Also, removed the confirmation screens.

PSID is your playstation's unique identifier to Sony, this program will patch the loaded PSID in memory to one of your choice. This won't permanently patch your PSID, but *MIGHT* let you fool PSN. Best way to test this is for somebody with a banned PS3 to try changing it and going online.

Please note that I'm not sure if PSID is what is actually used for bans! Apparently the ID used for banning is generated using the PSID, but I think that the result of this generation *MIGHT* be stored somewhere in memory. If it is, this tool is worthless for PSN until that result is found.

Made and tested on a 3.41 PS3 for 1.0, 3.55 PS3 for 1.2... Although not tested online by me!
If your using a different version and patching doesn't work properly please contact me and we'll work out a fix :)

This uses the peek and poke syscalls in order to patch your PSID. Please make sure your using a payload which uses them (http://psx-scene.com/forums/575356-post358.html for example) or a CFW that has them (kmeaw 3.55 does)

Usage:
Install package
Run PSIDPatch
Press Cross to patch PSID with a random number, or Square to patch ConsoleID.
Or.. if you want to use your own:
Create a text file called psid.txt/consoleid.txt on root of your USB
Put 32 hex characters inside (e.g. 1234567890ABCDEFFEDCBA0987654321) or 64 for ConsoleID
Open PSIDPatch, choose your USB using Up/Down arrows and press R1 to patch.

Technical Stuff:
PSID starts at 0x800000000044A18C in 3.41, 0x800000000045218C in 3.55. It is 16 bytes long.
Two identicle Console ID's exist in memory: one which is 32 bytes at 0x80000000003C2EF0 and another which is 16 bytes at 0x8000000000452174. PSN seems to use the second one, but PSIDPatch patches both.

Thanks:
Mathieulh/RichDevX - bragging about PSID stuff on twitter, if it was a private convo I never would of started this :)
user - Fixing CFWLoad code so no SCE confidential stuff is included, thanks man :D
djekl - Random PSID idea, can't believe I didn't think of that...

PSPoke is a homebrew application that allows you to view/edit the lvl2 memory on the PS3 during runtime via the pc!!

Similar to the Awesome Peek Poker, we can now apply patches to lvl2 during runtime to do various things, such as enable psn and change the ps3's psid number.

This is a network only application and you must use netcat on a linux pc to use it.

PSPoke does not allow editing of the PS3 Ram on the PS3, the idea is that you use a pc to connect via terminal.
To connect to the ps3 use netcat as follows:

nc 2002

With a bit of luck, you will see the usage guide in the terminal window.

Known Bugs*

Freeze on exit if you dont connect from a pc - PSPoke enters a blocking state while its listening for a connection, causing it to seem to lock at the black screen. To fix this, either restart the PS3, or connect to PSPoke via terminal.

Treat it as a beta ;)

Note: This homebrew application has been made with the 100% legal PSL1GHT PS3 SDK

How to REMOVE QA Flag from your PS3
============================
1. Download this QA Flag Reset.
2. Run reset_qa_flag.pkg , If you hear a beep it worked.
3. Reboot the ps3
4. QA Flag is now set to default (Off) Your PS3 is now normal again.

Source: http://www.ps3hax.net/2011/06/released-qa-flagging-tools/

How to Downgrade from 3.55 to lower versions
============================
1. Install CFW355-OTHEROS++-SPECIAL.pup (Doesn’t matter what version you are 3.41, 3.50 etc etc)
2. Install QA Flag Extra pkg
3. Run qa_flag (It will show up as this, that is fine)
4. If you hear the beeps, continue. If you don’t hear the beeps start over.
5. Reboot
6. Go into recovery menu and Update your ps3 with the firmware that you want (3.15, 3.41 etc)
7. Have it install

QuickDumpR is a tiny app that will dump the ram to the hdd in 15 seconds from launch to xmb. It uses the same code as the Awesome Peek Poker, but takes up less space in the ram, thus a less messy dump!

QuickDumpR is a tiny app that will dump the ram to the hdd in 15 seconds from launch to xmb. It uses the same code as the Awesome Peek Poker, but takes up less space in the ram, thus a less messy dump!
Instructions:

Just download it, install it and run it. Then either use Comgenie's Awesome File Manager or an FTP app to copy it off for analysis on yout PC.

It dumps the ram to the same place as Awesome Peek Poker ("/dev_hdd0/dump.bin") so thats were to look. Oh, and be sure to delete a previous dump before you dump again, it will increment to the file.

Rebug Toolbox is application designed to complete the full function of REBUG REX EDITION firmwares but is also compatible with most current 3.55->4.81 CEX/DEX CFW (some options are not available) . Besides from performing the CEX/DEX EID0 and LV2 Kernel Swapping it is also a FTP server and is packed with a bunch of other useful tools.

Note: The rebug packages are provided as a mirror in case they are unavailable and for historical proposes. You should support rebug development by visiting Rebug's website and downloading from there: http://rebug.me.

1. COBRA Payload 7.52 including
@habib's bug fix for lv1 peek support for multiMAN,
@deank's backup disc support for PS3 games
KW and @aldostools's homebrew blocker (thanks to @kokotonix for informing)

A collection of LV1 patches that can be used for better compatibility with some PS3 tools. Any combination of these patches can be applied before booting OtherOS.

DEX/CEX

* SWAP LV2 KERNEL:
Swaps between CEX and DEX LV2 Kernel. This option will only work if your Target ID is set to DEX

* REWRITE TARGET ID IN FLASH:
This option requires you have a valid NOR/NAND dump named correctly on dev_usb000. Use EXPORT FLASH TO FILE function to dump your NOR/NAND to dev_usb000 and then use c2d.exe to convert your dump to DEX.

Once you have prepared your NOR/NAND dumps place them on a USB device and connect it to dev_usb000.

Now that you have your valid dumps named properly and connected to dev_usb000 it is a simple as selecting the option and following the onscreen prompts. Takes less than 10secs once you have your dumps prepared.

* EXPORT FLASH TO FILE:
Backup your current NOR/NAND to file on dev_usb000. Takes about 45secs for NAND

UTILITIES

* TOGGLE QA:
Enable/Disable QA flag. Enable for easy downgrade and other extra features on all 3.55/4.21/4.30/4.31 CFW.

* SET GAMEOS BOOT FLAG:
Sets the GameOS boot flag. Use this if your PS3 is having trouble booting PS2 titles after running OtherOS or is accidently sending you back to OtherOS when trying to enter recovery mode.

* CREATE PACKAGES FOLDER ON PS3:
Create /dev_hdd0/packages folder or your PS3 to be used with Package Manager.

* EXPORT HYPERVISOR LV1 MEMORY:
Save LV1 memory to dev_usb000 or dev_usb006 or dev_hdd0 if usb is not found.

* EXPORT GAMEOS LV2 MEMORY:
Save LV2 memory to dev_usb000 or dev_usb006 or dev_hdd0 if usb is not found.

* EXPORT FLASH TO FILE:
Backup your current NOR/NAND to file on dev_usb000. Takes about 45secs for NAND

* CHANGE ACTIVE PS3ID:
Spoof IDPS in LV2 memory. Choose from Use EID0 or Use EID5. EID5 will spoof your original CEX IDPS allowing you to connect to PSN if your PS3 is running REBUG REX EDITION firmware in DEX mode.

QA is supported in all REBUG REX EDITIONS but at this point in time we are unable to set the QA Token from GameOS on 3.55+ firmware.

It is good practice to enable QA in 3.55 before updating to any CFW not just REBUG.

OTHEROS++ SUPPORT

OtherOS++ is supported by all REBUG REX EDITIONS and will detect your existing OtherOS HDD partition.

However none of the REBUG REX EDITIONS have emer_init.self patched (create smaller GameOS partition). We are working on a solution to this from GameOS.

In the meantime if you do want to create an OtherOS partition you have two options:

1: Use a 3.55 firmware that already has emer_init.self patched to the size you want.
2: Patch REBUG 3.55.3 REX EDITION in PS3MFW Builder

If you choose option 2 we highly recommend that you ONLY patch emer_init.self. Also the resulting PUP will only be able to be installed on 3.55 firmware as the spkg_hdr will be mismatched.

One final thing to note about OtherOS on 4.21.1 is that it function is slightly reduced at the moment due to the fact that we are not able to map memory like in 3.55 and below. The affected modules are ps3ram and ps3sbmmio.

Hopefully this problem can be addressed without having to release another firmware.

GameOS utilizes files to make the console work (I won’t give details)
These files (SELF = EXE, SPRX = DLL) are stored in /dev_flash
This tool enables to decrypt these SELF/SPRX files
Such a decrypter will only help people who know what they do
The application is not yet capable to decrypt all files (coming soon !)

12/12/10 - V0.6B - Second BETA Release
- More stability (no hangs anymore)
- Much more files can now be decrypted

GameOS utilizes files to make the console work (I won't give details)
These files (SELF = EXE, SPRX = DLL) are stored in /dev_flash
This tool enables to decrypt these SELF/SPRX files
Such a decrypter will only help people who know what they do ;-)
The application is not yet capable to decrypt all files (coming soon !)

Howto :
First, uninstall previous version
Install the .PKG provided in the archive

- Put the file you want to decrypt into :
/dev_hdd0/game/DCRY00001/USRDIR/SOURCE/
- Launch the decrypter
- Get the decrypted files from :
/dev_hdd0/game/DCRY00001/USRDIR/DESTINATION/

The current version decrypts only one file per launch
Make sure to have only one SELF/SPRX file in /SOURCE/ directory

After having to QA a few PS3 in a row. Then installing a different firmware straight after, it was time to cut out the middleman.

Toggle QA will SET/RESET the QA Flag and Token on any 3.41 or 3.55 firmware that has lv1 mmap and lv2 peek and poke patches (which is most of them).

When you run the app it first detects if the PS3 is 3.41 or 3.55. Next it will check if your firmware has any of the required lv1 patches already and only patch the hypervisor with the ones you need. After it finishes patching Toggle QA will check the status of the QA Flag and SET/RESET it accordingly. Then once the QA SET/RESET is done any lv1 patches made will be removed.

THIS SOFTWARE WRITES TO THE PS3 EEPROM – USE AT YOUR OWN RISK

Note: The rebug packages are provided as a mirror in case they are unavailable and for historical proposes. You should support rebug development by visiting Rebug's website and downloading from there: http://rebug.me.

**** THIS SOFTWARE WRITES TO THE PS3 EEPROM – USE AT YOUR OWN RISK ****

After having to QA a few PS3 in a row. Then installing a different firmware straight after, it was time to cut out the middleman.

Toggle QA will SET/RESET the QA Flag and Token on any 3.41 or 3.55 firmware that has lv1 mmap and lv2 peek and poke patches (which is most of them).

When you run the app it first detects if the PS3 is 3.41 or 3.55. Next it will check if your firmware has any of the required lv1 patches already and only patch the hypervisor with the ones you need. After it finishes patching Toggle QA will check the status of the QA Flag and SET/RESET it accordingly. Then once the QA SET/RESET is done any lv1 patches made will be removed.

HOW TO USE:
1: Install toggle_qa.pkg
2: Run Toggle QA from XMB
3: PS3 will beep and return to XMB. (If you do not hear a beep it has not worked)

NOTE: Every now and then it will hang on the lv1 patching stage. If it has not beeped and returned to the XMB after about 30secs you will need to reboot and try again.

Enjoy.

~ Codename: REBUG

Credit and Thanks:
Big thanks to graf and glevand for the hypervisor work.
Everyone involved in getting the QA Flag/Token working back many moons ago.

This program allows to simulate the dev_flash from USB. Allowing a Custom Firmware. We may modify the files of our new dev_flash (USB) as we please, without running the risk of throwing away the PS3.

It is a beta version, probably find bugs. I will continue working on it when time permits me. Remember that suffers no risk to the console. All that is changed the new dev_flash'll be doing really USB.

Here I bring the new version 0.3

Improvements:

- Code optimization.

- Fixed USB port allocation.

- Fixed black screen.

Recommendations:

- Only have a USB MASS STORAGE USB connected to load FIRM LOADER.

- UPDATE NO FIRM while in USB mode LOADER.

Thanks for reporting bugs!

Requirements:

Syscall PEEK and POKE.

Installation:

1. Copy the "FTP server" the entire contents of the / dev_flash the USB (the root).

2. Copy the JaiC_USB_FIRM_LOADER.pkg also the root of the USB.

3. Install the package.

Use:

1. Insert the USB into the PS3.

2. Run USB LOADER FIRM. After a few seconds will return to the XMB. The new firmare is loaded.

You will see that whatever you do the USB will be launched. Ideal for amending RCO, exchange modules, as you imagine.

IMPORTANT!

Do not update while in Live Firmware Mode. It will reboot, setting the original dev_flash back, and then it will update! Do not update from USB FIRMWARE LOADER!

xReg Plus is a simple app that will allow you to backup and restore your xRegistry.sys file to/from USB. Good for instantly restoring your settings and access to your save data again after a Service Mode install.

Note: The rebug packages are provided as a mirror in case they are unavailable and for historical proposes. You should support rebug development by visiting Rebug's website and downloading from there: http://rebug.me.

DISCLAMER: This software can be used to enable LEGALLY obtained DLC (downloaded content) if your console has become deactivated. It contains NO ‘Official SCE’ code and was made using open source SDK psl1ght. The responsibility IS on the end-user to use this software in accordance with his/her own country’s/region’s copyright laws.

xReg Plus is a simple app that will allow you to backup and restore your xRegistry.sys file to/from USB. Good for instantly restoring your settings and access to your save data again after a Service Mode install.

1: Press SELECT to BACKUP xRegistry.sys to root of USB000

2: Press START to RESTORE xRegistry.sys from root of USB000

Also includes Activation Reviver.

You must have a backup of your act.dat file and the exdata folder must already exist in dev_hdd0/home/00000001/ (Currently that is the only address it copies to).
How it works..

1: Place act.dat onto root of USB stick and place in USB000 (slot furthest right)