Forums GAMERGEN
[HOMEBREW] Devhook 0.46 est sorti
Règles du forum
Si vous remarquez un message susceptible d'aller à l'encontre des recommandations dont une partie ou la totalité du contenu ne devrait pas se trouver là, signalez-le à l'équipe de modérateurs en cliquant sur
.
________________
Toute l'équipe vous souhaite la bienvenue ! Si vous repérez d'éventuelles erreurs qui se seraient glissées dans nos contenus, n'hésitez pas à le signaler dans les commentaires.
Si vous remarquez un message susceptible d'aller à l'encontre des recommandations dont une partie ou la totalité du contenu ne devrait pas se trouver là, signalez-le à l'équipe de modérateurs en cliquant sur
.________________
Toute l'équipe vous souhaite la bienvenue ! Si vous repérez d'éventuelles erreurs qui se seraient glissées dans nos contenus, n'hésitez pas à le signaler dans les commentaires.
[HOMEBREW] Devhook 0.46 est sorti
par zaxouprout » 28 Juil 2006, 08:44
Effectivement à l'heure ou je vous ecris ce message, la nouvelle version est sorti, je vous l'ai zippé et uploader sur mon serveur ftp.
Au niveau des nouveautés il a un fichier txt qui porte comme titre : FLASHrom et l'apparition d'un nouveau fichier dans le dossier dh/kd/ qui porte le nom : umdciso_47_2000.prx . Peut-etre le patch qui permet de lancer un iso qui en fait charge le vrai umd que vous avez inserez et vous permettrent ainsi de ne plus etre obligé de redemarrer devhook pour passer du mode ISO au UMD.
Bon je test cette version et je vous dit ce que j'ai trouvé
Edit MaGiXieN: mise en ligne sur nos serveurs du logiciel.
News officelle ICI - Ce topic devient donc l'officiel
Au niveau des nouveautés il a un fichier txt qui porte comme titre : FLASHrom et l'apparition d'un nouveau fichier dans le dossier dh/kd/ qui porte le nom : umdciso_47_2000.prx . Peut-etre le patch qui permet de lancer un iso qui en fait charge le vrai umd que vous avez inserez et vous permettrent ainsi de ne plus etre obligé de redemarrer devhook pour passer du mode ISO au UMD.
Bon je test cette version et je vous dit ce que j'ai trouvé
Edit MaGiXieN: mise en ligne sur nos serveurs du logiciel.
News officelle ICI - Ce topic devient donc l'officiel
-
zaxouprout
Gamer Pro
- Messages: 122
- Inscription: 11 Nov 2010, 16:41
- Pays: France
par zaxouprout » 28 Juil 2006, 08:58
Bon C'est il y a d'énorme nouveautés :
-interface menu refaite
-nouveau systeme nommé Flashmod permet de flash la console de la ms vers flash 1 ect... (assez bizarre tant que l'on aura pas de tutos pour nous expliquer vraiment l'utilité)
-un nouvel homebrew est mis a disposition et permet de retourner en 1.50 rien quand le lancant (fini les combos HOME+start)
Malheuresement il faut que vous pensiez a ne pas supprimer le fichier se trouvant dans :
ms0:/dh/kd/reboot.bin
Il permet l'usage de cet homebrew et se trouve dans la version 0.45 donc ne le supprimé pas
C'est tous ce que j'ai pour l'instant
-interface menu refaite
-nouveau systeme nommé Flashmod permet de flash la console de la ms vers flash 1 ect... (assez bizarre tant que l'on aura pas de tutos pour nous expliquer vraiment l'utilité)
-un nouvel homebrew est mis a disposition et permet de retourner en 1.50 rien quand le lancant (fini les combos HOME+start)
Malheuresement il faut que vous pensiez a ne pas supprimer le fichier se trouvant dans :
ms0:/dh/kd/reboot.bin
Il permet l'usage de cet homebrew et se trouve dans la version 0.45 donc ne le supprimé pas
C'est tous ce que j'ai pour l'instant
-
zaxouprout
Gamer Pro
- Messages: 122
- Inscription: 11 Nov 2010, 16:41
- Pays: France
par xeo_romain » 28 Juil 2006, 09:01
Ouaip j'ai vu ca ailleurs, ca à l'air pas trop mal (pour la vitesse); pour alncer la 2.71 qui serait stockée dans le flash1...
Excellent idée et ma foi, pas tellement risqué. (recovery powaaa).
Excellent idée et ma foi, pas tellement risqué. (recovery powaaa).
-
xeo_romain
Gamer Pro
- Messages: 109
- Inscription: 25 Jan 2006, 01:00
par zaxouprout » 28 Juil 2006, 09:26
J'ai trouvé la traduc du fichier flash rom qui est en jap je vous file la traduc' pour nos amis qui parlent anglais pour les gens francais a 100% il va falloir attendre que je fasse la traduc disponible environ dans deux heures ^^
traduction Japonais->Anglais :
These are a set of Booster's considerations regarding the danger of accessing the PSP's internal FlashROM.
---------------------------------------
Structure of the PSP's Internal FlashROM
---------------------------------------
The PSP has 32 MB of internal NAND FlashROM.
This is split into three areas: IPL, IDStorage, and MASSstorage.
The IPL area is what holds the program information that is necessary to make the PSP start. If this is damages, the PSP will not start (i.e., "bricked" in the vernacular.)
It appears that the IDStorage area is where the OpenPSID, MAC address, serial number, and other such information is recorded. Not much detail is known about this area.
The MASSstorage area is where the files that are accessed as "flash0" and "flash1" are stored. There is functionality for ECC and bad block physical/logical changes, but the format differes from something like the popular SmartMedia.
Logically, it's compatible with a DOS/V HDD image, and it's split into the following four partitions under 1.50:
24560KB:'flash0:' area
4080KB:'flash1:' area
1008KB: empty, use is unknown
944KB: empty, use is unknown
---------------------------------------
The Fragile Nature of the PSP's Internal FlashROM
---------------------------------------
Accessing the internal FlashROM is prohibited from usermode programs.
On the other hand, other than file access, it's possible to read and write to the entire area from kernel mode programs using the physical driver as a medium. Furthermore, it's possible to bypass the driver and obtain direct hardware access, but it's simple to end up rendering the PSP unusable.
The maker (i.e., Sony) should have the ability to restore an unusuable (bricked) PSP, however, this method is currently unknown to ordinary users, thus not much can be done other than returning the unit to the manufacturer or having it modded.
Then, it ended up that homemade software (homebrew) kernel mode software could be run normally from a memory stick due to a weakness in FW 1.00/1.50.
Do we know what kind of danger we're exposed to by running software from unknown sources without thinking about it?
Isn't it probably better to have an environment where software that can be run normally is limited to usermode access and that programs requiring kernel mode access should be explicitly run?
By searching for the following functionality in programs that are to be executed, we can determine the possibility of virus that could destroy the FlashROM.
1. The module attributes are set to kernel mode.
2. The program is linked to the "sceMScm_driver" library.
3. The program is linked to the "LflashFatfmt" library.
4. There are keywords for "flash", "lflash", or "flashfat" present
5. The program is linked to the API for sceIoAssign/sceIoUnassign
6. The NANDFlash hardware register addresses are loaded.
---------------------------------------
The Danger Involved in Rewriting Flash0
---------------------------------------
Flash0 contains files that are required to run the PSP and XMB. No rewriting occurs during normal use.
The PSP's startup is run by the IPL program which is written to the IPL area, but it's necessary that the version is compatible with the flash0 file.
Once flash0's pspcnf_tbl.txt, pspbtcnf.txt, and the files mentioned in pspbtcnf.txt are completed, flash1's registry is checked for consistency or created from scratch, other files necessary for starting the XMB are gathered and the system can startup. If any one of these steps cannot be completed properly, the PSP won't start up.
For programs to run from memory stick, it's also necessary to have the files that are mentioned in pspbtcnf_game.txt. Without getting to this point, homebrew wouldn't run.
I'm yet to verify this, but it's thought that if you use Dark_Alex's custom firmware proof of concept "return" programs can be run even if the registry or certain files required by the XMB are not present. At this time, running devhook from flash also misappropriates this technique.
Dark Alex
My gratitude to Dark_Alex!
Ordinarily, flash0 is mounted read-only so writing is protected against, however, it is possible to re-mount from kernel mode and obtain write access.
Since flash0 is normally read-only, it's thought that as long the files necessary for running are protected, it's ok if the empty area gets used up; although this is totally a guess.
There's 9290 KB of free space in flash0 in FW 1.50.
When devhook 0.46.0000 uses the fonts and tables for 2.71, the empty space goes down to 4,624 KB.
---------------------------------------
The Danger Involved in Rewriting Flash1
---------------------------------------
Flash1 holds the registry and other settings files and is frequently written to in common usage.
Since flash1 is put in a different partition from flash0, flash0 won't be harmed even if the power is cut while accessing flash1.
However, it's possible that the registry files in flash1 can be damaged and if the situation is such that they cannot be re-created, it can become such that the FW1.50 re-initialization and restart can loop and it won't start up. If you fall into this situation:
1. Your file system ended up being broken by interrupting power during file writing.
2. Some other file filled up the space where the now destroyed registry was.
The file system was purposefully destroyed.
one of these three things probably happened.
Regarding the initialization of the registry in FW1.50, two methods have been confirmed that destroy other files on flash1 and appear not to format and so on.
When dealing with flash1, if you protect the existence of the registry files and empty space sufficiently, this won't happen.
Since the registry in flash1 is accessed quite frequently, it is dangerous to remove the ac adapter or batteries without using the power switch when the PSP is in use.
Moreover, if the FlashRom device is put into a writer-protected condition, the PSP won't run.
The empty space in flash1 at startup time in FW1.50 is 3808KB.
traduction Japonais->Anglais :
These are a set of Booster's considerations regarding the danger of accessing the PSP's internal FlashROM.
---------------------------------------
Structure of the PSP's Internal FlashROM
---------------------------------------
The PSP has 32 MB of internal NAND FlashROM.
This is split into three areas: IPL, IDStorage, and MASSstorage.
The IPL area is what holds the program information that is necessary to make the PSP start. If this is damages, the PSP will not start (i.e., "bricked" in the vernacular.)
It appears that the IDStorage area is where the OpenPSID, MAC address, serial number, and other such information is recorded. Not much detail is known about this area.
The MASSstorage area is where the files that are accessed as "flash0" and "flash1" are stored. There is functionality for ECC and bad block physical/logical changes, but the format differes from something like the popular SmartMedia.
Logically, it's compatible with a DOS/V HDD image, and it's split into the following four partitions under 1.50:
24560KB:'flash0:' area
4080KB:'flash1:' area
1008KB: empty, use is unknown
944KB: empty, use is unknown
---------------------------------------
The Fragile Nature of the PSP's Internal FlashROM
---------------------------------------
Accessing the internal FlashROM is prohibited from usermode programs.
On the other hand, other than file access, it's possible to read and write to the entire area from kernel mode programs using the physical driver as a medium. Furthermore, it's possible to bypass the driver and obtain direct hardware access, but it's simple to end up rendering the PSP unusable.
The maker (i.e., Sony) should have the ability to restore an unusuable (bricked) PSP, however, this method is currently unknown to ordinary users, thus not much can be done other than returning the unit to the manufacturer or having it modded.
Then, it ended up that homemade software (homebrew) kernel mode software could be run normally from a memory stick due to a weakness in FW 1.00/1.50.
Do we know what kind of danger we're exposed to by running software from unknown sources without thinking about it?
Isn't it probably better to have an environment where software that can be run normally is limited to usermode access and that programs requiring kernel mode access should be explicitly run?
By searching for the following functionality in programs that are to be executed, we can determine the possibility of virus that could destroy the FlashROM.
1. The module attributes are set to kernel mode.
2. The program is linked to the "sceMScm_driver" library.
3. The program is linked to the "LflashFatfmt" library.
4. There are keywords for "flash", "lflash", or "flashfat" present
5. The program is linked to the API for sceIoAssign/sceIoUnassign
6. The NANDFlash hardware register addresses are loaded.
---------------------------------------
The Danger Involved in Rewriting Flash0
---------------------------------------
Flash0 contains files that are required to run the PSP and XMB. No rewriting occurs during normal use.
The PSP's startup is run by the IPL program which is written to the IPL area, but it's necessary that the version is compatible with the flash0 file.
Once flash0's pspcnf_tbl.txt, pspbtcnf.txt, and the files mentioned in pspbtcnf.txt are completed, flash1's registry is checked for consistency or created from scratch, other files necessary for starting the XMB are gathered and the system can startup. If any one of these steps cannot be completed properly, the PSP won't start up.
For programs to run from memory stick, it's also necessary to have the files that are mentioned in pspbtcnf_game.txt. Without getting to this point, homebrew wouldn't run.
I'm yet to verify this, but it's thought that if you use Dark_Alex's custom firmware proof of concept "return" programs can be run even if the registry or certain files required by the XMB are not present. At this time, running devhook from flash also misappropriates this technique.
Dark Alex
My gratitude to Dark_Alex!
Ordinarily, flash0 is mounted read-only so writing is protected against, however, it is possible to re-mount from kernel mode and obtain write access.
Since flash0 is normally read-only, it's thought that as long the files necessary for running are protected, it's ok if the empty area gets used up; although this is totally a guess.
There's 9290 KB of free space in flash0 in FW 1.50.
When devhook 0.46.0000 uses the fonts and tables for 2.71, the empty space goes down to 4,624 KB.
---------------------------------------
The Danger Involved in Rewriting Flash1
---------------------------------------
Flash1 holds the registry and other settings files and is frequently written to in common usage.
Since flash1 is put in a different partition from flash0, flash0 won't be harmed even if the power is cut while accessing flash1.
However, it's possible that the registry files in flash1 can be damaged and if the situation is such that they cannot be re-created, it can become such that the FW1.50 re-initialization and restart can loop and it won't start up. If you fall into this situation:
1. Your file system ended up being broken by interrupting power during file writing.
2. Some other file filled up the space where the now destroyed registry was.
The file system was purposefully destroyed.
one of these three things probably happened.
Regarding the initialization of the registry in FW1.50, two methods have been confirmed that destroy other files on flash1 and appear not to format and so on.
When dealing with flash1, if you protect the existence of the registry files and empty space sufficiently, this won't happen.
Since the registry in flash1 is accessed quite frequently, it is dangerous to remove the ac adapter or batteries without using the power switch when the PSP is in use.
Moreover, if the FlashRom device is put into a writer-protected condition, the PSP won't run.
The empty space in flash1 at startup time in FW1.50 is 3808KB.
-
zaxouprout
Gamer Pro
- Messages: 122
- Inscription: 11 Nov 2010, 16:41
- Pays: France
par zaxouprout » 28 Juil 2006, 09:42
naruto93 Wrote:: 8O
lol sinon donc je devrai lettre le 2.5 pour utiliser le 2.6 , ok je fai sa des que je serai mieu reveiller
escuse moi mais je ne comprends pas ce que tu viens d'écrire
-
zaxouprout
Gamer Pro
- Messages: 122
- Inscription: 11 Nov 2010, 16:41
- Pays: France
par zaxouprout » 28 Juil 2006, 09:48
Bon j'ai recherché dans pas mal de forums anglais genre Max Consoles ect..
J'ai compris qu'en fait le fait de mettre le firmware 2.71 sur le flash de la console pourrait en fait permettre de lancer plus vite le firmware 2.71 et avec le custom firmware de dark alex et de hurleyg's, il y aurait certaines possibilités que booster se tiens bien de dire visiblement...
Veut-il nous faire souffrir mentalement???
En attentands je vous prepare un tutos en image du flahs 2.71 de ma console
J'ai compris qu'en fait le fait de mettre le firmware 2.71 sur le flash de la console pourrait en fait permettre de lancer plus vite le firmware 2.71 et avec le custom firmware de dark alex et de hurleyg's, il y aurait certaines possibilités que booster se tiens bien de dire visiblement...
Veut-il nous faire souffrir mentalement???
En attentands je vous prepare un tutos en image du flahs 2.71 de ma console
Dernière édition par naviz le 28 Juil 2006, 09:54, édité 1 fois.
-
zaxouprout
Gamer Pro
- Messages: 122
- Inscription: 11 Nov 2010, 16:41
- Pays: France
par Moa Jordan » 28 Juil 2006, 09:48
metal_death Wrote:naruto93 Wrote:: 8O
lol sinon donc je devrai lettre le 2.5 pour utiliser le 2.6 , ok je fai sa des que je serai mieu reveiller
escuse moi mais je ne comprends pas ce que tu viens d'écrire
Il confond la version de DevHook avec le firmware de la psp, la preuve, il dit "va falloir que j'installe version "X" pour y mettre la version "Y".
Si c'est ca, tu cherches un petit peu sur le site y'a un tuto pour te dire comment tu peut utiliser DevHook
@ +
Jordan
- iPhone 4 16GB Black
- iPhone 3GS 16GB Blanc
- iPhone 3G Noir
- iPhone 3GS 16GB Blanc
- iPhone 3G Noir
-
Moa Jordan
Gamer Hardcore
- Messages: 622
- Inscription: 01 Jan 2008, 00:21
- Prénom: jordan
- Pays: France
- Sexe: Homme
par Eric de Brocart » 28 Juil 2006, 09:50
mise en ligne sur news officielle.
Bon travail metal_death
Lire
http://www.pspgen.com/modules.php?name=News&file=article&sid=2121
Bon travail metal_death
Lire
http://www.pspgen.com/modules.php?name=News&file=article&sid=2121
-
Eric de Brocart
Administrateur principal
- Messages: 19780
- Inscription: 05 Juin 2005, 00:00
- Localisation: Nice
- Prénom: Eric
- Pays: FRANCE
- Sexe: Homme
par xeo_romain » 28 Juil 2006, 09:51
metal_death Wrote:Bon j'ai recherché dans pas mal de forums anglais genre Max Consoles ect..
J'ai compris qu'en fait le fait de mettre le firmware 2.71 sur le flash de la console pourrait en fait permettre de lancer plus vite le firmware 2.71 et avec le custom firmware de dark alex et de hurleyg's, il y aurait certaines possibilités que booster se tiens bien de dire visiblement...
Veut-il nous faire souffrir physiquement???
En attentands je vous prepare un tutos en image du flahs 2.71 de ma console
C'est ce que j'ai dis plus haut ;o)
-
xeo_romain
Gamer Pro
- Messages: 109
- Inscription: 25 Jan 2006, 01:00
par Moa Jordan » 28 Juil 2006, 09:54
xeo_romain Wrote:metal_death Wrote:Bon j'ai recherché dans pas mal de forums anglais genre Max Consoles ect..
J'ai compris qu'en fait le fait de mettre le firmware 2.71 sur le flash de la console pourrait en fait permettre de lancer plus vite le firmware 2.71 et avec le custom firmware de dark alex et de hurleyg's, il y aurait certaines possibilités que booster se tiens bien de dire visiblement...
Veut-il nous faire souffrir physiquement???
En attentands je vous prepare un tutos en image du flahs 2.71 de ma console
C'est ce que j'ai dis plus haut ;o)
J'ai pas vu que t'été en vacances sur ton forum à toi
Edit => Oups c'est ce soir qui part
XD 
Dernière édition par eniddeza le 28 Juil 2006, 09:58, édité 1 fois.
- iPhone 4 16GB Black
- iPhone 3GS 16GB Blanc
- iPhone 3G Noir
- iPhone 3GS 16GB Blanc
- iPhone 3G Noir
-
Moa Jordan
Gamer Hardcore
- Messages: 622
- Inscription: 01 Jan 2008, 00:21
- Prénom: jordan
- Pays: France
- Sexe: Homme
par zaxouprout » 28 Juil 2006, 09:55
Pourquoi tu dit ca ?
Non il n'a pas dit ca plus haut il a pas dit pour la vitesse de boot amélioré . Mais bon on va pas se disputer pour ca
Non il n'a pas dit ca plus haut il a pas dit pour la vitesse de boot amélioré . Mais bon on va pas se disputer pour ca
-
zaxouprout
Gamer Pro
- Messages: 122
- Inscription: 11 Nov 2010, 16:41
- Pays: France
- Forums
- L’équipe du forum • Supprimer les cookies du forum • Heures au format UTC + 1 heure [ Heure d’été ]
SitemapIndex