Hey there.

So... you use an ad blocker. That's cool. Sometimes we do too.

But without ad revenue, we wouldn't even be here. And we might not be here much longer.

Please disable your ad blocker and click to continue.

Page 2 of 2 First 12
  1. #11
    deank Guest

    [Register or Login to view code]

    No success...

    I tried a lot of different things but always get an error (0x8001002B).

    * ERROR_KERNEL_I/O_ERROR: 0x8001002B

    If I use non-existing port I get 0x80010002.

    If I apply the firmware patches to lv2 from waninkoko's source my PS3 locks...

    It will be nice if there was an explanation what these kernel pokes do:

    [Register or Login to view code]

    I tried

    [Register or Login to view code]

    [Register or Login to view code]

    [Register or Login to view code]

    Try to unmount first with syscall 838... still no go

    [Register or Login to view code]


    I compared my original level2 kernel with the patches posted above:

    [Register or Login to view code]

    I don't have an asm/disasm to check the opcodes, but it will be much appreciated if anyone can find more info on this.


  2. #12
    barrybarryk Guest
    The GameOS probably throws a logic error trying to mount a UDF as write not protected, as it's expecting all udf discs to be optical media.

    Try it with the write protect mode flag as 1 instead of 0.

  3. #13
    deank Guest
    I'll give it a try... I managed to 'block' all my USB ports by setting them to UDF by poking some values in the kernel table of connected devices... Tried to format the hdd as exFAT and to mount it as EFAT but that didn't work either (error 0x80010037)...

    Nope... still error 80010037... I formatted the disc as udf 2.50... I can't even get it working with regular FAT32 USB... trying to unmount it (works) and then to mount it back (doesn't work - error 8001002b).

    I'll dump my lv2 and check the mount table for the BD rom and then will try to copy it to a usb mount table.

    Edit: Some progress... I found out what one of the poke data means: pokeq( 0x800000000019282CULL, 0x63BD06664BFFD67DULL ); compared to original :63 BD 00 2B 4B FF D6 7D

    This one patches the kernel to return XXXX0666 error, instead of the real one (like in my case 8001002B).

    I changed it to 0000. I managed to unmount /dev_usb000 and mount it back... that's something.

    I mounted my USB stick as /dev_bdvd and /dev_bdvd appeared in the root folder (without having original BD disc inserted)


Page 2 of 2 First 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Log in