The above video goes away if you are a member and logged in, so log in now!
Did you grab the latest version of Brandon Wilson's App (0.06.0001)? You made sure to use KIOSK341.8xv as the stage 1 payload right? Make sure you have no stage 2 selected.
Originally Posted by desi tmac91
Let me know if it works.
You said you were on 3.21.. There isn't a payload for that firmware I believe. You'd have to update to 3.41, and I don't know how to do that on a demo PS3.
Originally Posted by desi tmac91
It might be that you are on FW 3.21 and you need to set FW compat under options to that same version. Problem is finding and Appvar that is appropriate.
I know there is one FWC315, could anyone maybe share onefor 301? Or maybe point me in the right direction.
ps. I just love these godly threads with up to date info. epic
I just fixed the 10-23-2010 KakaRoto Payloads. I needed a break from Fallout: New Vegas.. lol
They were working, but I was missing a couple. I added them back in.
Also, a slight name change has happened. I will be referring the Kiosk payloads as:
KIDEFxxx.8xv- Default Kiosk Payload
KIDEVxxx.8xv- DEV Kiosk Payload
KIPATxxx.8xv- Patched Kiosk Payload
Sorry for any inconvienence. With so many payloads coming out, I am trying to get a naming scheme down that will be easy to distinguish one from another. I only can have up to 8 characters in an .8xv file, so I have little room to experiment.
I also updated my compileLINUX.sh script and my compileWINDOWS.bat batch file. It now supports automated compiling of Patched Payloads and Kiosk Payloads. Check it out!
Where did you find a 3.15 kiosk compatible payload?
Originally Posted by thisisme
OK, all of these changes have me confused a bit. I'm wondering what the dump_elfs payloads do for one thing. Ah, so we're going with PAT for the prefix. I was thinking that or NUS for no_unauth_syscall but I think PAT is easier for people to understand. What I was going to do was put K at the end of the kiosk ones, since technically it's just a different firmware (that way if he adds debug units later, we can just put D at the end). That sort of limits us to 4 characters max for the name part, but, that should be alright, assuming the number of payloads doesn't continue to double Anyway, I was thinking that would keep them grouped based on functionality.
Last edited by Kratos77; 10-24-2010 at 06:13 PM.
im not familiar with kiosk versions. Im trying to locate an Appvar that i can use under options "FW Compat". I can only find one for 3.15 "FWC315" or am i missing something?
Originally Posted by remainnameless
Fallout las vegas is a curse, its almost impossible to stop playing.
Great... I didn't even think of DEBUG versions.. lol. I think I agree with your style of naming scheme. I'll make the appropriate changes here in a few. For the meantime, I'm going to do debug payloads as DEBxxx.8xv for non-kiosk consoles and KIDEBxxx.8xv for debug kiosk (if they even exist). If there are any more opthoins available, it will have to change.
Originally Posted by Kratos77
He's had the dump_elfs support for the last couple of payloads. He also has dump_lvl2 and shellcode_panic. I think the latter 2 are for trying to find the USB descriptors for older firmwares. I never knew what the dump_elfs was for. I'll take a look here in a bit and see if I can figure it out.
Thanks for the input Kratos. It's really appreciated.
hey guys im kinda confused
i dont know which PL3 to use if i want to play MOH on 3.41 using open manager 1.17.2
can someone please help?
Use the DEF341.8xv. I haven't tried it with a 3.42+ game though. Let us know if it works.
Originally Posted by th3riddler
Ah, but wouldn't names like DEBDEF315 or KIDEBPAT341 be too long? This is all pure speculation of course at this point, but DEF315D or PAT341DK would work. I'm using DUMP for the dump_elfs ones atm. Guess I'd have to shorten that to DMP should the dump ones prove useful, and a debugging kiosk be discovered (I really don't think they make those, though).