QJ.net Game Discussion - PSP, Xbox, Wii, PS3, PSP Homebrew, and PSP Guides

**niko86** · 08-08-2008, 04:39 AM

Just a quick question really. What calls on pspbtdnf.bin to load?

The reason i ask is i'm trying to modify the DCv6 install, so i can load 4.01m33 without using DCv6. But while still only having one instance of DCv6 on my stick.

Jaxrir worked out a method for that by having 2 copies of DC6 folder renaming one to 401. Then you can replace the resurrection.prx in one of them with resurrection.elf with the extension changed to .prx which boots 4.01m33 like time machine would. Only problem is that means having 4.01m33 time machine, DCv6 and the 401.pbp thats 60mb, or more.

I traced, copied and renamed then patched files so i have 2 ways to boot DCv6 from 2 ipl.bin files. One ipl.bin the other ipx.bin. I've noticed pspbtdnf.bin and pspbtdnf_02.bin are the only files to reference to resurrection.prx.

I know its lame just doing a few hex changes here and there, and its not like im looking to release this as if its something i've made. It's mainly just out of curiosity and its giving me a little project which is helping me understand how a psp's firmware works.

**vodkkaa** · 08-08-2008, 04:50 AM

the *.bin files are the boot tables read by the ipl.

**niko86** · 08-08-2008, 05:09 AM

Quote:

Originally Posted by vodkkaa

the *.bin files are the boot tables read by the ipl.

What i've noticed the ipl.bin references to ipl_01.bin and ipl_02.bin which then reference to like you say the boot tables. But they only refer to the pspbtcnf.bin tables. pspbtdnf.bin refers to resurrection.prx which is why i'm trying to find the file which references or loads pspbtdnf.bin.

pspbtcnf seems to be where the path stops and pspbtdnf is where it ends. i'm looking for the middle. And pspbtcnf.bin seems to be encrypted i used freeplay's newCNFedit program, but i just get garbled .txt file so the decryption must be different. So i can't check pspbtcnf.bin.

Any ideas or should i just give up?

**vodkkaa** · 08-08-2008, 06:23 AM

Im not sure but I assume each .bin in the kd folder corresponds these different boot modes: xmb load, game, update, pops, and np9660. the 01g and 02g refer to phat or slim respectively. I would guess that the .bin that references resurection.prx is the updater boot table. I would assume this is called from the pspbtconf.bin and not the ipl as the IPl is not executed every time you switch modes (game, updater, pops, vsh, or np9660)

**niko86** · 08-08-2008, 06:32 AM

Ahh i see that explains the 2 varients of the same bin files. Decompressing/decrypting is the problem now, as freeplays program seems to not work on this file. Or even my 4.01m33 firmware pspbtcnf, i doubt i can make something to do that but i'll have a search round see if i can find more info to help me thanks vodkkaa

**JaX3RiR** · 08-11-2008, 04:31 AM

Another problem here would be that we cannot use the official pspbtcnf.bin (lol) and PRXDecrypter cannot decrypt the pspbtcnf.bin for some reason (failed, unk. tag 0x4C9414F0).

Dark-Alex himself said that M33 firmwares do not use the pspbtcnf.bin.. But I can't figure out what else is loading pspbtdnf.bin.

08-08-2008, 04:39 AM	#1
niko86 Join Date: May 2008 Location: Hartlepool, England Posts: 357 Trader Feedback: 0	pspbtdnf.bin Just a quick question really. What calls on pspbtdnf.bin to load? The reason i ask is i'm trying to modify the DCv6 install, so i can load 4.01m33 without using DCv6. But while still only having one instance of DCv6 on my stick. Jaxrir worked out a method for that by having 2 copies of DC6 folder renaming one to 401. Then you can replace the resurrection.prx in one of them with resurrection.elf with the extension changed to .prx which boots 4.01m33 like time machine would. Only problem is that means having 4.01m33 time machine, DCv6 and the 401.pbp thats 60mb, or more. I traced, copied and renamed then patched files so i have 2 ways to boot DCv6 from 2 ipl.bin files. One ipl.bin the other ipx.bin. I've noticed pspbtdnf.bin and pspbtdnf_02.bin are the only files to reference to resurrection.prx. I know its lame just doing a few hex changes here and there, and its not like im looking to release this as if its something i've made. It's mainly just out of curiosity and its giving me a little project which is helping me understand how a psp's firmware works.

08-08-2008, 06:23 AM	#4
vodkkaa Join Date: Apr 2007 Posts: 886 Trader Feedback: 0	Im not sure but I assume each .bin in the kd folder corresponds these different boot modes: xmb load, game, update, pops, and np9660. the 01g and 02g refer to phat or slim respectively. I would guess that the .bin that references resurection.prx is the updater boot table. I would assume this is called from the pspbtconf.bin and not the ipl as the IPl is not executed every time you switch modes (game, updater, pops, vsh, or np9660) Last edited by vodkkaa; 08-08-2008 at 06:33 AM..

08-11-2008, 04:31 AM	#6
JaX3RiR Enter Custom Title JaX3RiR Join Date: Nov 2007 Real First Name: Janne Location: Finland Just Played: GTA IV Posts: 844 Trader Feedback: 0	Another problem here would be that we cannot use the official pspbtcnf.bin (lol) and PRXDecrypter cannot decrypt the pspbtcnf.bin for some reason (failed, unk. tag 0x4C9414F0). Dark-Alex himself said that M33 firmwares do not use the pspbtcnf.bin.. But I can't figure out what else is loading pspbtdnf.bin. __________________ http://card.mygamercard.net/nxe/JaX3RiR.png

08-08-2008, 04:50 AM	#2
vodkkaa Join Date: Apr 2007 Posts: 886 Trader Feedback: 0	the *.bin files are the boot tables read by the ipl.

08-08-2008, 06:32 AM	#5
niko86 Join Date: May 2008 Location: Hartlepool, England Posts: 357 Trader Feedback: 0	Ahh i see that explains the 2 varients of the same bin files. Decompressing/decrypting is the problem now, as freeplays program seems to not work on this file. Or even my 4.01m33 firmware pspbtcnf, i doubt i can make something to do that but i'll have a search round see if i can find more info to help me thanks vodkkaa