Un Flasheur En .xex

[val532]

Salut,

Alors qui va se lancé et créer un petit homebrew pour dumpé et flashé depuis la console ?

En .xex ou .elf bien sur.

[darkmaster60]

J'y ai pensé, ça serait quand même bien un petit Firmware-Dumper

[Pink Floyd]

je sors ma boule de crystal....

[Yelrac]

En elf ça doit être fesable mais en xex sachant que la flash est utilisé en même temps j'ai des doutes que ce soit possible...

je sors ma boule de crystal....

t'en a qu'une???

-->[]

[Pink Floyd]

En elf ça doit être fesable mais en xex sachant que la flash est utilisé en même temps j'ai des doutes que ce soit possible...

je sors ma boule de crystal....

t'en a qu'une???

-->[]

c'est fAIsable que tu reviennes pas ?

Modifié 24 décembre 2009 par Pink Floyd

[Yelrac]

rien d'autre à dire...

edit: en plus ta phrase, ce n'est pas du français...

Modifié 24 décembre 2009 par Yelrac

[Pink Floyd]

c'est une figure de style, nuance

bref...

Modifié 24 décembre 2009 par Pink Floyd

[val532]

Bon en tous cas qui veut si collé ?

[BestPig]

Comme il a été dit, je ne pense pas que cela soit vraiment possible puisque le dashboard est utilisé et donc en constante modification.

[darkmaster60]

Bah juste une lecture du firmware, ça serait déjà un bon début

Perso, compter pas sur moi, j'suis une tanche .. =/

[Shakin]

Salut,

Faut voir le fonctionnement de la console, si lorsque l'on lance une application il est possible de travailler sur certaines choses ou pas.

@+

[val532]

Une version .elf qui se lance depuis le xell.

[BestPig]

Une version .elf qui se lance depuis le xell.

Oui la à mon avis c'est possible.

[80Y]

uniquement l'elf est possible depuis le Xell. Une fois le kernel lancé sur la console il n'autorise pas ce genre d'action depuis un XEX (flash, dump) du moins je crois, à confirmer

Modifié 28 décembre 2009 par 80Y

[TheTool]

salut,

tout est possible, pour preuve, le systeme d'update de la 360,

reste a savoir comment il fonctionne

Ludo

[BestPig]

Une maj qui installerai directement xbr, pourquoi pas , puisque que l'on peut lancer du code non signé, mais bon comme la nand est entirement réecrite pour xbr, a mon avis c'est plus probable que quelqu'un sort quelque chose qui le fait avec xell, que avec un update de 360 xD.

[Quentin67]

et puis avec le xell sa doit être plus simple a faire que avec le dash surtout que je sais pas si la console va aimé qu'a un moment il y est plus rien sur la rom du lecteur

[kogami]

Oui en effet le xell est plus approprié pour un flash de la nand, tout peux être stocké en ram sans devoir utilisé la nand comme mémoire.

[BestPig]

Dans le code source de xell, on dirait que y'a des fonctions sympa .

void readsector(unsigned char *data, int sector, int raw){	int status;	sfcx_writereg(STATUS, sfcx_readreg(STATUS));	sfcx_writereg(ADDRESS, sector);		sfcx_writereg(COMMAND, raw ? 3 : 2);	while ((status = sfcx_readreg(STATUS))&1); 	if (status != 0x200)	{		if (status & 0x40)			printf(" * Bad block found at %08x\n", sector);		else if (status & 0x1c)			printf(" * (corrected) ECC error %08x: %08x\n", sector, status);		else if (!raw && (status & 0x800))			printf(" * illegal logical block %08x (status: %08x)\n", sector, status);		else			printf(" * Unknown error at %08x: %08x. Please worry.\n", sector, status);	}	sfcx_writereg(ADDRESS, 0);	int i;	for (i = 0; i < 0x210; i+=4)	{		sfcx_writereg(COMMAND, 0);		*(int*)(data + i) = bswap_32(sfcx_readreg(DATA));	}}void flash_erase(int address){	sfcx_writereg(0, sfcx_readreg(0) | 8);	sfcx_writereg(STATUS, 0xFF);	sfcx_writereg(ADDRESS, address);	while (sfcx_readreg(STATUS) & 1);	sfcx_writereg(COMMAND, 0xAA);	sfcx_writereg(COMMAND, 0x55);	while (sfcx_readreg(STATUS) & 1);	sfcx_writereg(COMMAND, 0x5);	while (sfcx_readreg(STATUS) & 1);	int status = sfcx_readreg(STATUS);	if (status != 0x200)		printf("[%08x]", status);	sfcx_writereg(STATUS, 0xFF);	sfcx_writereg(0, sfcx_readreg(0) & ~8);}void write_page(int address, unsigned char *data){	sfcx_writereg(STATUS, 0xFF);	sfcx_writereg(0, sfcx_readreg(0) | 8);	sfcx_writereg(ADDRESS, 0);	int i;	for (i = 0; i < 0x210; i+=4)	{		sfcx_writereg(DATA, bswap_32(*(int*)(data + i)));		sfcx_writereg(COMMAND, 1);	}	sfcx_writereg(ADDRESS, address);	sfcx_writereg(COMMAND, 0x55);	while (sfcx_readreg(STATUS) & 1);	sfcx_writereg(COMMAND, 0xAA);	while (sfcx_readreg(STATUS) & 1);	sfcx_writereg(COMMAND, 0x4);	while (sfcx_readreg(STATUS) & 1);	int status = sfcx_readreg(STATUS);	if (status != 0x200)		printf("[%08x]", status);	sfcx_writereg(0, sfcx_readreg(0) & ~8);}

EDIT : Ces fonctions sont appeler dans :void update_xell_flash(void *xell_address, u32 file_size) {C'est pour update xell, il écrit bien dans la nand, si xell est capable de s'autoupdater dans la nand, je voit pas pourquoi ça serait impossible de mettre XBR comme ça.

Modifié 28 décembre 2009 par BestPig

[Yoshihiro]

Salut Voila C'est sortie

Flash360 v1.0 By Redline992010-01-15Place in the root dir of a usb drive:updslot0.bin - Xell			 (Address 0x0C0000 max length 0x040000 bytes, no metadata)updslot1.bin - Rebooter		 (Address 0x100000 max length 0x140000 bytes, no metadata)updpatch.bin - Rebooter Patches (Address 0x194000 max length 0x004000 bytes, no metadata)updflash.bin - Nand Image File  (this must include the metadata or aka spare/ecc bytes)	Must be the full nand with exceptions for consoles with a built in Memory Unit.		Flash360 will scan the bad block reservation area of the file to be flashed.	If it finds blocks that have been remapped then it sets the writing mode	to write the file as-is.  If it determines that no blocks have been remapped	then it sets its write mode to relocate any blocks as it goes along.		The block relocator logic will only apply to the Flash partition. This means that it	will not try to relocate any block from the built in Memory Unit (if available). 	A simple check of the KV will be done if the choice to not copy it from the current	nand is selected.  Flash360 cannot currently get the CPU key to completely verify	the KV before writing. If it detects a difference in the first page it will	warn you before proceeding.	If Flash360 is ran from a HDD, USB or MU, saving the current nand image will be available.The raw dumped nand file will be saved to "D:\flashdmp.bin". (same dir as xex)For consoles with built in MU:You can select to save the entire nand or only the Flash partition (66 MiB).This also means you can write just Flash partition (66 MiB) to the nand.When writing the Flash you can select to keep the current Keyvault and Config blocks. This is the recommended way to flash XBRebooter, straight from the release package.If any writing to the nand is done do not return to the dash or bring up the guide.An auto shutdown mechanism is in place by backing out of the main menu.  The power plug should be removed to allow for a complete reinitialization of console.Notes:It is up to the user to verify the validity of the file(s) to be flashed.Flashing the nand is risky, I hope it works well for everyone, if problems ariseI will do my best to address them.  There are still many items I would liketo do/add to this app, so it will be a work in progress.When using this app do not do anything that will interrupt it. Do not use the big center guide button on the controller. Do not have the dash doing anything in the background. Remember what this application is doing is replacing the contents on the nand without the rest of the system knowing about it.There is also a new Xell I have created with many of these features plus some newones that should be nice.  Time didnt permit releasing it though.Thanks:To kreet and angerwound for looking over my code and fixing many noob mistakes. :)And especially to all the gracious people who helped test!Greets:r0wdy, tiros, MODFREAKz, schtrom, xorloser, tmbinc, seventhson, angerwound, kreet, lantus,Skorchir, D-BlooD, momdad, skitzo, Cr4zi3, Sonic-Iso, stk50, Yoshihiro, Arakon and Alley. Team Greets:XBRebooter, XeDev, Jungle, HyperX, Avalaunch, Xecuter, MS Interactive Entertainment Business Department

[imedox]

Salut Voila C'est sortie

Flash360 v1.0 By Redline99 2010-01-15  Place in the root dir of a usb drive: updslot0.bin - Xell			 (Address 0x0C0000 max length 0x040000 bytes, no metadata) updslot1.bin - Rebooter		 (Address 0x100000 max length 0x140000 bytes, no metadata) updpatch.bin - Rebooter Patches (Address 0x194000 max length 0x004000 bytes, no metadata)  updflash.bin - Nand Image File  (this must include the metadata or aka spare/ecc bytes)	 Must be the full nand with exceptions for consoles with a built in Memory Unit.	 	 Flash360 will scan the bad block reservation area of the file to be flashed.	 If it finds blocks that have been remapped then it sets the writing mode	 to write the file as-is.  If it determines that no blocks have been remapped	 then it sets its write mode to relocate any blocks as it goes along.	 	 The block relocator logic will only apply to the Flash partition. This means that it	 will not try to relocate any block from the built in Memory Unit (if available).  	 A simple check of the KV will be done if the choice to not copy it from the current	 nand is selected.  Flash360 cannot currently get the CPU key to completely verify	 the KV before writing. If it detects a difference in the first page it will	 warn you before proceeding.	   If Flash360 is ran from a HDD, USB or MU, saving the current nand image will be available. The raw dumped nand file will be saved to "D:\flashdmp.bin". (same dir as xex)  For consoles with built in MU: You can select to save the entire nand or only the Flash partition (66 MiB). This also means you can write just Flash partition (66 MiB) to the nand.  When writing the Flash you can select to keep the current Keyvault and Config blocks.  This is the recommended way to flash XBRebooter, straight from the release package.  If any writing to the nand is done do not return to the dash or bring up the guide. An auto shutdown mechanism is in place by backing out of the main menu.    The power plug should be removed to allow for a complete reinitialization of console.  Notes: It is up to the user to verify the validity of the file(s) to be flashed.  Flashing the nand is risky, I hope it works well for everyone, if problems arise I will do my best to address them.  There are still many items I would like to do/add to this app, so it will be a work in progress.  When using this app do not do anything that will interrupt it. Do not use the  big center guide button on the controller. Do not have the dash doing anything in  the background. Remember what this application is doing is replacing the contents on  the nand without the rest of the system knowing about it.  There is also a new Xell I have created with many of these features plus some new ones that should be nice.  Time didnt permit releasing it though.  Thanks: To kreet and angerwound for looking over my code and fixing many noob mistakes. :) And especially to all the gracious people who helped test!  Greets: r0wdy, tiros, MODFREAKz, schtrom, xorloser, tmbinc, seventhson, angerwound, kreet, lantus, Skorchir, D-BlooD, momdad, skitzo, Cr4zi3, Sonic-Iso, stk50, Yoshihiro, Arakon and Alley.   Team Greets: XBRebooter, XeDev, Jungle, HyperX, Avalaunch, Xecuter,  MS Interactive Entertainment Business Department

enfin le xex test sur jasper 256 ça marche nikell Merci @Redline99.

Modifié 16 janvier 2010 par imedox