PS3 [DEV} PS3MFW Builder MOD

[littlebalup]

As I mentioned, I have also mimatches on the lv1 keys. Not only the curve type, but the public key too:

 

[sandungas]

Good work finding errors @littlebalup
That one for lv1ldr seems to be messed up with other firmware versions
http://www.psdevwiki.com/ps3/Keys#Lv1ldr

 

[haxxxen]

@littlebalup
thank you very much for finding these errors on keys and also the problem with the global options. though, with the keys it is not my fault, cause i just have taken them from other builds and just added the later ones.

i have looked now myself on the keys and noticed there are several differences to scetool keyset.

and about self_-/iso_rebuilder, self_rebuilder is only made for flash files and lv1/lv2 kernels. all other coreos files (including lv0 and its loaders) are isolated modules and have to be resigned with iso_rebuilder (if so, and which does not work for regular flash files btw)

when modifying cfws, you better choose scetool, since most developers have signed the files with it and when scetool was used before, you cannot resign the files with self_-/iso_rebuilder.

edit
just remembered, it's weird, but i haven't got these brick issues myself, since i have made a test with 4.81 dualboot fw myself, when ofw was released. i always make this test on ofw to see if patches do still match.

 

[Omage]

How to use ps3mfw-builder for ofw dex 4.81?
My english is not good, many options do not understand
Have a detailed tutorial?
http://www.psx-place.com/threads/tu...rsonalized-cfw-mfw-with-ps3-mfw-builder.2079/
Follow this link tutorial OK?

 

[haxxxen]

How to use ps3mfw-builder for ofw dex 4.81?
My english is not good, many options do not understand
Have a detailed tutorial?
http://www.psx-place.com/threads/tu...rsonalized-cfw-mfw-with-ps3-mfw-builder.2079/
Follow this link tutorial OK?

this is not about mfwbuilder, but well...

sorry, but i still had no time nor interest to add dex payloads/patches to mfwbuilder. there are still some other things and this will consume much time. for now, you have to do it manually and maybe @Joonie can give you more details on dex payloads

 

[littlebalup]

@littlebalup
thank you very much for finding these errors on keys and also the problem with the global options. though, with the keys it is not my fault, cause i just have taken them from other builds and just added the later ones.

i have looked now myself on the keys and noticed there are several differences to scetool keyset.

and about self_-/iso_rebuilder, self_rebuilder is only made for flash files and lv1/lv2 kernels. all other coreos files (including lv0 and its loaders) are isolated modules and have to be resigned with iso_rebuilder (if so, and which does not work for regular flash files btw)

when modifying cfws, you better choose scetool, since most developers have signed the files with it and when scetool was used before, you cannot resign the files with self_-/iso_rebuilder.

edit
just remembered, it's weird, but i haven't got these brick issues myself, since i have made a test with 4.81 dualboot fw myself, when ofw was released. i always make this test on ofw to see if patches do still match.

No it's not your fault. The mistakes in keys seems to be there since a while. And are in the original PS3MFW builder.

Strange and weird you had no brick using iso_rebuilder to resign lv0 with those keys. Maybe you used iso_rebuilder for the isolated modules (isolated modules keys are ok) and scetool for the lv0 ? (ref to my "Test 5" : http://www.psx-place.com/threads/ps3mfw-builder-mod.1888/page-4#post-80898). But, as your task use iso_rebuilder for both lv0 and modules, you should not.
So, maybe I'm crazzy...

 

[subsonix]

Can any body help me with creating a linux partition with ps3mfw builder? Im not to sure what option to use? Can any one post screen shots? Im gunna be using my ps3 as a dedicated linux server.

 

[subsonix]

I keep getting this error.
FATAL ERROR: Could not unpkg file: dev_flash_000.tar.aa.2012_06_30_064328: child killed. segmentation violation. Any one care to help. I just want to have a partition to put red rib linux on hdd. USB is slow.

 

[pinky]

I keep getting this error.
FATAL ERROR: Could not unpkg file: dev_flash_000.tar.aa.2012_06_30_064328: child killed. segmentation violation. Any one care to help. I just want to have a partition to put red rib linux on hdd. USB is slow.

might not have the right keys or the right privileges. for the former, I think the keys file(s) is on a github; for the latter, try running mfw on the desktop.

edit: two more ideas: try running the app as administrator. also, make sure you link to the keys folder on the main menu of the app. it should be over to the right of the app, away from the patches section, in settings.

 

[JumpSuit]

Can this be fixed for PS3 MFW Builder? I can't patch to OtherOS++ for lv1: https://cdn.discordapp.com/attachments/186510351192424448/509573333067628564/unknown.png
it is seearching for lv1.self.ELF when it is lv1.self.SELF, I think that is the problem...?

 

[pinky]

Can this be fixed for PS3 MFW Builder? I can't patch to OtherOS++ for lv1: https://cdn.discordapp.com/attachments/186510351192424448/509573333067628564/unknown.png
it is seearching for lv1.self.ELF when it is lv1.self.SELF, I think that is the problem...?

which pup are you using? it will error like that if you try applying a patch that already exists. as for the name, one (perhaps more) app's naming convention is to stick elf at the end of the .self. I was thinking it was scetool that did it without adding a file name of your own. I think ps3tools does this too or at least it did, perhaps using the same app. I can't remember the app in question to be sure. I've never personally applied that patch, just spit ballin'.

 

[Louay]

@habib @Joonie @Alexander @littlebalup
try those as @littlebalup did 2 years ago

Using OFW 4.85 pup as base.
Keys up to date (keys copied of 4.81 and renamed to 4.85 and 9.99).
tools used(SCEtool, iso_rebuilder,self_rebuilder,unself)
2 lv0tool version (one with extract option ,other with -option export)
Applying ECDSA patches to isoldr and spu_pkg_rvk_verifier

Test 1 (using only SCEtool) :
- Decrypted lv0 with : SCEtool
- Extracted loaders from lv0.elf with lv0tool
- Decrypted isoldr.self and spu_pkg_rvk_verifier.self with : SCEtool
- Applyed patches to isoldr.elf and spu_pkg_rvk_verifier.elf.
- Resigned isoldr.elf and spu_pkg_rvk_verifier.elf with : SCEtool
- Imported loaders to lv0.elf with lv0tool.
- Resigned lv0.elf with : SCEtool
Result : BRICK!

Test 2 :
- Decrypted lv0 with : SCEtool
- Extracted loaders from lv0.elf with lv0tool
- Decrypted isoldr.self and spu_pkg_rvk_verifier.self with : SCEtool
- Applyed patches to isoldr.elf and spu_pkg_rvk_verifier.elf.
- Resigned isoldr.elf and spu_pkg_rvk_verifier.elf with : iso_rebuilder
- Imported loaders to lv0.elf with lv0tool.
- Resigned lv0.elf with : iso_rebuilder
Result : BRICK!

Test 3:
- Decrypted lv0 with : SCEtool
- Extracted loaders from lv0.elf with lv0tool
- Decrypted isoldr.self and spu_pkg_rvk_verifier.self with : unself
- Applyed patches to isoldr.elf and spu_pkg_rvk_verifier.elf.
- Resigned isoldr.elf and spu_pkg_rvk_verifier.elf with : iso_rebuilder
- Imported loaders to lv0.elf with lv0tool.
- Resigned lv0.elf with : iso_rebuilder
Result : BRICK!

Test 4 (using only unself and iso_rebuilder) :
- Decrypted lv0 with : unself
- Extracted loaders from lv0.elf with lv0tool
- Decrypted isoldr.self and spu_pkg_rvk_verifier.self with : unself
- Applyed patches to isoldr.elf and spu_pkg_rvk_verifier.elf.
- Resigned isoldr.elf and spu_pkg_rvk_verifier.elf with : iso_rebuilder
- Imported loaders to lv0.elf with lv0tool.
- Resigned lv0.elf with : iso_rebuilder
Result : BRICK!

Test 5 (using scetool for lv0 only) :
- Decrypted lv0 with : SCEtool
- Extracted loaders from lv0.elf with lv0tool
- Decrypted isoldr.self and spu_pkg_rvk_verifier.self with : unself
- Applyed patches to isoldr.elf and spu_pkg_rvk_verifier.elf.
- Resigned isoldr.elf and spu_pkg_rvk_verifier.elf with : iso_rebuilder
- Imported loaders to lv0.elf with lv0tool.
- Resigned lv0.elf with : SCEtool
Result : BRICK!

Test 6 (using self_rebuilder for lv0 only) :
- Decrypted lv0 with : unself
- Extracted loaders from lv0.elf with lv0tool
- Decrypted isoldr.self and spu_pkg_rvk_verifier.self with : unself
- Applyed patches to isoldr.elf and spu_pkg_rvk_verifier.elf.
- Resigned isoldr.elf and spu_pkg_rvk_verifier.elf with : iso_rebuilder
- Imported loaders to lv0.elf with lv0tool.
- Resigned lv0.elf with : self_rebuilder
Result : BRICK!

any help ,propostion?

EDIT : there is 2 scetool exe (private build) with 314KB that i use for those six test and now i test with scetool (public build ) that have 122KB and it works Dualboot FW boots normaly and install CFW (overflow cfw)

 

[SpyroMancer]

What kind of settings do i have to use, to make a standard cex cfw, with this mod? I've searched various releases of mfw builder, and each one is different. But for my understanding, this is the most corrected one? I want to make my own mfw for personal use. cex, no cobra.

 

[pinky]

What kind of settings do i have to use, to make a standard cex cfw, with this mod? I've searched various releases of mfw builder, and each one is different. But for my understanding, this is the most corrected one? I want to make my own mfw for personal use. cex, no cobra.

I'd say this is the one to use, yes. I'd strongly advise you have a flasher on hand in case something goes wrong.

 

[SpyroMancer]

So, is it possible for some insturctions on how to build a standard mfw, using this version? For latest FWs.

It would be awesome, thank you.

 

[pinky]

So, is it possible for some insturctions on how to build a standard mfw, using this version? For latest FWs.

It would be awesome, thank you.

you don't necessarily need to build one from scratch. you can taken any ofw or cfw and build from that. for example, you can take rebug 4.86 lite, and build a no bd from it. or add any touches you like.

 

[SpyroMancer]

you don't necessarily need to build one from scratch. you can taken any ofw or cfw and build from that. for example, you can take rebug 4.86 lite, and build a no bd from it. or add any touches you like.

Sure, but it would also be nice to have the info available for everyone.

 

[pinky]

Sure, but it would also be nice to have the info available for everyone.

I seem to recall a mfw tutorial somewhere, but I can't remember where. I know @Bobby_Downgrades made some youtube videos showing how to make a cfw. it's broken into several parts. can't recall if he's doing it manually or using mfw.

 

[SpyroMancer]

I seem to recall a mfw tutorial somewhere, but I can't remember where. I know @Bobby_Downgrades made some youtube videos showing how to make a cfw. it's broken into several parts. can't recall if he's doing it manually or using mfw.

Bobby is doing it manual, there is a tutorial here, but not for this build. Tried the same settings with this one, but didn't work. Settings have different categories and/or names. Anyway... maybe @haxxxen can help

 

[pinky]

Bobby is doing it manual, there is a tutorial here, but not for this build. Tried the same settings with this one, but didn't work. Settings have different categories and/or names. Anyway... maybe @haxxxen can help

I'd strongly recommend a flasher of some sort before installing a mfw. dunno what you mean by didn't work. did you get an error building the mfw? I recommend building it on your desktop where you have more privileges by default. that could cause it to error if users don't have full privileges. not having the keys in the right format can also cause it to error or not linking to them.