Hermes AsbestOS Payload

[remainnameless]

Hey guys,

I stumbled across this while on elotrolado. Sorry for the babelfish translate, I don't know Spanish.

Here I let the AsbestOS loader:

Version homebrew worked under psl1ght already compiled:

http://mods.elotrolado.net/~hermes/p...ad_v4_apps.rar

version not psl1ght:

http://mods.elotrolado.net/~hermes/p...oad_hermes.rar

In order to compile asbestos.bin (that is included) it is needed compilers PS3, such as those that or ifcaro has precompiled (that is what I have used I) or those that generates ps3toolchain.

to asbestos_loader, is an application prototype that must be compiled and so you already know: you can use basic the sources of open to manager, you clear all the PPU_SRCS less main.cpp and you add syscall8.c, you put of TARGET asbestOS.elf, you clear all the PPU_LDLIBS and you leave emptinesses VPSHADER_SRCS and FPSHADER_SRCS.

The EBOOT.BIN that is generated next to the sources, can be sent from app_home when igniting the console, if in pendrive you add a folder in root “PS3_GAME”, inside you put the ICON0.PNG and valid PARAM.SFO (that you can adapt so that puts asbestOS and those things), you create a folder “USRDIR” and inside you put the EBOOT.BIN.

Also it can become of the following way: you create the folder inside “homebrew” in root of pendrive and another one of name “AsbestOS”, where you copy the EBOOT.BIN and the ICON0.PNG

In root of pendrive it is needed asbestos.bin (that are in the folder “asbestos_bin” of rar) and dtbImage-20101020.bin, kernel of Linux that you can unload here of http://marcansoft.com/transf/dtbImage-20101020.bin

With that you would have to see the pinguinos and all that: it is not possible to be gone beyond unless you can form servant TFTP, etc, but as concept sample, is worth.

The shipper uses the generic route “/dev_usb” reason why he does not agree that there are other devices FAT connected to the console.

PS: Please, that the people who do not know of these things, abstain to take part: Linux in PS3 at the moment, is but a curiosity that another thing, because it is in diapers. This that I put here is not but that a curiosity for some and others, perhaps it is a route easy of work to develop kernel in a device that in principle, is not preparation for it.

Greetings

News Source: PSGROOVE Payload Custom (V4B) (102 de 119) @ ElOtroLado.net

I'll have a TI-84+ port here in a few!

EDIT: (Quick and Dirty Tutorial)
To make this work, you need these 2 files:
Payload_4_apps- http://mods.elotrolado.net/~hermes/p...ad_v4_apps.rar
DTB Image- http://marcansoft.com/transf/dtbImage-20101020.bin

After you have extracted DTB Image, copy the kernel (dtbImage-20101020.bin) to the root of your flash drive.

Then extract Payload_4_Apps. Create a folder called "HOMEBREW" on the root of the flash drive, and a folder called "ASBESTOS" inside of it. Then copy "EBOOT.bin" and "ICON0.PNG" from "payload_4_apps > homebrew > AsbestOS" to the "HOMEBREW > ASBESTOS " folder on your flash drive.

Load up Hermes' payload and run Open Manager. Go to the Homebrew launcher (Press START) and launch AsbestOS.

There you go. It's not much right now, but if you set up a TFTP server you can run a lot of Terminal commands.

[naughtydog]

Two things

1. Hermes never left (which is a good thing)

2. This will start a fight in ps3 scene between hermes and kakaroto <--- Im sure this is in .rar and not git though all i care about is having both of them in ps3 scene and not on each others neck

[Skeetys]

Really couldn't care less about KaKaRoLo... He might be good for the scene, but attacking others is just bs and his attempt to cover for himself made him look even worse.

[MangoScango]

So what exactly does this do? The translation sucks. It looks like it replaces Stage 2 of AsbestOS with a homebrew app? I can't really tell...

[omegatron]

competition creates improvement, so hopefully these guys will try to out do each other and we will benifit

[MRDOCA]

kakarots already flaming on twiter.

[Ozz465]

competition creates improvement,

This ...

[AugustSKY]

i lol'd

[JonahUK]

From the readme

This code is adapted to launch using syscall 8 from my psgroove payload variant.

This code is experimental and is intended for those who have a 16KB USB dongle and no possibility to launch asbestOS in other form

You can get an experimental compiled kernel from http://marcansoft.com/transf/dtbImage-20101020.bin or build one (see marcan README)

How it works:

At first, you need to read asbestos.bin and kernel code (i.e from one application. I include a prototype- example in "asbestos_loader" directory
to load the files from USB devices)

asbestos.bin is allocated in 80000000007FD000 address (LV2 area) (my payload is loaded at 80000000007FF000, remember you)

To work, you must test if syscall 8 is working with this function:

if(sys8_enable(0ULL)<0) goto error;

You can copy asbestos.bin to LV2 so:

// copy asbestOS
sys8_memcpy(0x80000000007FD000ULL, (uint64_t) asbestos_mem, (uint64_t) asbestos_len);

And run it passing the allocated kernel memry and the size:

// run asbestOS
sys8_call(0x80000000007FD000ULL, (uint64_t) kernel_len, (uint64_t) kernel_mem);

Internally it disables interrupt for PPE thread 0, patch the decrementer interrupt (0x800000000000900) and waits to capture thread 1 in an internal loop
mean this interrupt (_thread1_wait in start.S). Thread 1 changes the mode from virtual to real mode, disable interrupts and waits a signal from thread 0
(_thread1_release!=0)

In LV2 virtual address starts at 0x8000000000000000 but in real mode it starts at 0

From thread 0, the Linux kernel is moved from 'kernel_mem' to 0x800000000010000 (DEST_H<<16 in start.S) because you must enter in real mode and you loses
the virtual address focus. In theory, you have 0x7FD000-0x10000= 0x7ED000, 8310784 bytes for Linux kernel (remember you asbestos.bin is allocated in
0x7ED000.)

When Linux kernel is copied it proceed to change thread 0 to the real mode, call lv2_cleanup(), move the Linux kernel from 0x10000 (DEST_H<<16) to 0x0
using kload() releases thread 1 (it go to 0x100 address, reading _thread1_vector value) and thread 0 go to the same address, 0x100

Remember you this code is experimental and may be, it has some mistakes: I have done what i could

NOTE: Patch for decrementer Interrupt is based in 3.41 firmware (start.S line 35), but surely it works in all

Cheers,
JonahUK

[joneSi]

Cleaned it up:

I am putting the AsbestOS loader here:

Homebrew version worked under psl1ght already compiled:

http://mods.elotrolado.net/~hermes/p...ad_v4_apps.rar

version not compiled with psl1ght:

http://mods.elotrolado.net/~hermes/p...oad_hermes.rar

In order to compile asbestos.bin (that is included) a PS3 compiler is needed, such as those that or ifcaro has precompiled (that is what I have used I) or those that generates ps3toolchain.

asbestos_loader, is an application prototype that must be compiled with what you already know [edit:the sony sdk]. you can use basic the sources of open to manager, you clear all the PPU_SRCS less main.cpp and you add syscall8.c, you put of TARGET asbestOS.elf, you clear all the PPU_LDLIBS and you leave empty VPSHADER_SRCS and FPSHADER_SRCS.

The EBOOT.BIN that is generated next to the sources, can be sent from app_home when igniting the console, if in pendrive you add a folder in root “PS3_GAME”, inside you put the ICON0.PNG and valid PARAM.SFO (you can adapt that so that it puts asbestOS and those things wherever), you create a folder “USRDIR” and inside there you put the EBOOT.BIN.

Also it can also be made in the following way: you create the folder inside “homebrew” in root of a pendrive and another one named “AsbestOS”, where you copy the EBOOT.BIN and the ICON0.PNG

In root of the pendrive needs asbestos.bin (that are in the folder “asbestos_bin” of rar) and dtbImage-20101020.bin, kernel of Linux that you can unload here of http://marcansoft.com/transf/dtbImage-20101020.bin

With this you should be able to see the penguins and whatever: you can't go further with this unless you configure a TFTP server, etc, this is a proof of concept, ok.

The 'charger' [not sure what he means here] uses the generic route “/dev_usb” reason which is why it does not like it when there are other FAT devices connected to the console.

PS: Please, do not tinker with this if you don't know what you are doing. Linux on PS3 at the moment, is more of a curiosity than anything else, because Linux on PS3 is still in 'diapers'. I put it here because it is a curiosity for some and others. Perhaps it is easy work to develop kernel for a device in principle, it is not ready for it now.

Greetings