The above video goes away if you are a member and logged in, so log in now!
I had this problem too, turns out make_self_npdrm doesn't sign properly on windows, when I tried it on linux and it worked fine.
I don't think that hex editor is working correctly. It is not finding "/dev_bdvd" in the EBOOT.BIN. Secondly, why say "Works great.", when it didn't work for you? If you get a blackscreen, then I don't think it's working. Unless SAW doesn't work with EBOOT.BIN replacement.
Originally Posted by jumper2009
Also, how could you say "SAW booted..." when it didn't boot?
I think I might switch editors. I am using the HexEditor plugin for Notepad++. Maybe I shouldn't, lol. Time to go a Google'n!
Thanks, I will try this. I didn't think that would be the issue, but maybe my Windows build of ps3tools isn't updated.
Originally Posted by villadelfia
If u cant find dev_bdvd,then u cant edit something! Will not work. An Example of that is Force Unleashed 2... So simple. Before i used this editor i got the 800blabla Error. But know it starts but hangs on the BlackScreen.
if your getting that 80010007 error it's cause the EBOOT size didnt come out the size of the original EBOOT, if you want to fix it, just add hex padding to the patched EBOOT, till it's the same as the original, if you do this, make sure your hex addresses are the same, along with the headers.
I've same issue here... package installs fine but when start the game, return this 80010007 error code.
Thanks for that bit of information. The Hex editor provided in an earlier post was fine, I'm sure. I somehow got EBOOT.BINs mixed up. I don't know how. I jumped to conclusions and I apologize to the one who provided it.
Originally Posted by 8-bit
I'll do some research on adding padding to a file. Should be able to find something.
Edit: There's my problem. My brain must be mush. I need sleep. I opened the EBOOT.BIN and not the EBOOT.ELF. lol, my mistake.
Edit: Can you explain what you mean by "Hex padding". There is nothing in my book that sounds like that. (And Google is of no use)
Edit: Also, if this is needed to be done, then why do I not see this in guides anywhere? I don't hear all the people making working pkg's talk about doing anything advanced.
Last edited by Troop116rules; 01-12-2011 at 01:04 AM.
HEX WORKSHOP V5 –
HEX WORKSHOP V5 WORKS GREAT!!
I had the same error when using Hex-Editor MX* Replaced the EBOOT.BIN after that was fixed via FTP**
NFSHP Going*** Going for V1.01 Update and will fix EBOOT I'll let all know the results sooon!
i've do that right now but the error still the same.
Originally Posted by 8-bit
Make sure your being case sensitive when typing in things in cmd
Originally Posted by tiochico27
Of course i did but error still there.
Originally Posted by consume
I've made a test, and the new EBOOT.BIN couldn't be unself again, i can't extract the ELF file from that. Wich means that "make_self_npdrm" process is not working how desired, i think.
Sorry for my bad english