Jump to content
RealModScene

Blackjack

Members
  • Content Count

    118
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Blackjack


  1. You gave me an idea :)

     

    I could do this in two ways :

    - 1st one would be to use the unused LED point from the DNA because only one is used on the latter. It depends on wich ROL model of the console.

    - 2nd one would  be to use the ISP Signal from the DNA. The problem is that my whole set up is based on it. Actually it controls my modchip Ace V1. But i could flash it with new Bistreams indeed they are Dual Nand compatible. Then it would liberate the ISP Signal and i could use it to control the +5V USB Memory.


  2. The simple way would be to put an external switch for the VCC point, basically tho, in order for a new patch to be developed we have to know which device it is registered as so we can disable it's mountpoint...

     

    Yes the simple way...I'm afraid of this...

    The simpliest way for me would be  a Xebuild Patch lol

     

    Of, you're using the USB port?

     

    I'm using an USB extended Memory but it is recognised as an Internal Memory by my Corona.

     

    NOTICE : 

     

    nointmu    - disables jasper NANDmu, trinity 4G interal USB and corona 4G mmc memory units

     

    nointmu's Xebuild Patch works because  on Trinity the memory is recognised as an internal USB memory.

    On Corona it is recognised as an internal memory


  3. Yeah, sorry... i haven't updated the code of the GUI... it's still the same, so you'll have to use the argument editor... and add -a nointmu somewhere before the last part (output.bin)

    Yes in XeBuild GUI " Disable Onboard MU " doesn't work there is an error in the log but using the argument editor -a nointmu it is solved.

    By the way I tried to use " Custom Xell " I wanted to create an image with BlackCat Xell but impossible  to create the latter...

    Thank you Swizzy for your software and your support :)


  4. Hi,

    I updated my old jtag to 2.0.16202.0 and installed Fsd 3 Rev 483 + Dashlaunch 3.06 with no problems. My Kinect works fine on NXE but not onto FSD ! There is not the small Kinect window on the right bottom corner. Sound recognition works good.

    am I the only one that's happening ? Or is it a known bug of FSD ?

    Thanks for your help and sorry for my english ( i'm french). ;)

×
×
  • Create New...