Jump to content
RealModScene

Swizzy

Members
 View Profile  See their activity

  • Content Count

    10457

  • Joined

  • Last visited

  • Days Won

    353

Posts posted by Swizzy

  1. Posted

    what i need to recompile the mupen with toolchain?have some tutorial for make thias or i need wait the developer of mupen recompile?

    i can recompile it for you a little later maybe... you'll need linux and maybe even edit some of the code...

    I can not update the console with new xell from usb. Xell stops at :fat Mount udo0 (Trinity mainboard)

    Try rebuilding your nand and updating XeLL that way using Simple 360 NAND Flasher instead ;)

  2. Posted

    without memory usb it does not happen, I have an external hd but it gets turned off when using xell, I swapped the usb device and stopped the problem of red screen could run free60 xbox360 ubuntu10.10 but mupen after the xell do reading. elf the screen is black I'll send the video via pm because it has cpukey will be that the screen is turning black because my television is those old tube and mupen does not support the low resolution of the tv?the xmplayer_0.0.1 give black screen

     

    only free60 xbox360 ubuntu10.10 is working 

    Posted Image

    The reason you only get black screen when trying to boot mupen64 is because it doesn't support Corona unless you recompile it using the new (updated) libxenon toolchain

     

    I wonder if it could be the USB's File System, Would NTFS or FAT make any difference?

    Edit: misspelled FAT..(LMFAO)

    No, it makes no difference because XeLL don't support NTFS at this time, i've been working on squeezing that in... but... it's not very easy (the NTFS lib is HUGE and it's not easy to find what can be disabled safely without breaking everything)

     

    Just did the update changing xell.ggggg.bin (or whatever it was named) (for RGH's) renamed it to updxell.bin and it successfully updates, after reboot I run xell from DVD button and it shows it as version 0.993, when I try to boot mupen64 though it gives the seg fault and this stack dump:

    Posted Image

    this stack dump tells me that your USB drive falls down to the "lazy formatter" thingy, i've fixed this bug in XeLL, however... the bug is also present in most homebrew that uses usb devices...

    https://github.com/Free60Project/xell/commit/0a15d0abfaa365a4c0b024b58fd69732932bbdd6#L0R337 <--- the 2 lines here is the fix :)

  5. Posted

    I'm relativly new to all of this, and was wondering if this update should be done (for stability etc..) to my already hacked console, or if this is only for hacking a clean console.  Sorry if this is a really dumb question. :(

    It doesn't make your console boot any better or so... it does however fix some bugs in XeLL, if you ever use that (highly unlikely as most ppl don't really use it much) there's little to no reason to update just because it's out...The new xeBuild GUI, J-Runner, AutoGG etc. will all use the new XeLL Reloaded from now on ;)
    • Like 1

  6. Posted

    :wallbash:

    Video works from XellLaunch, however... reading the NAND doesn't... (MMC coronas) other consoles work just fine... this also means that nothing from the NAND can be used by XeLL, including getting your real MAC Address 

    For those of us not fully in the circle of power users... does this offer anything for users without the Corona motherboard?  For instance, I have a phat console (Jasper).  Is this something I should be concerned about getting?  Does it do anything for me?  In the reply about Nintendo64, you mention something about stuff needing to be recompiled.. does that mean future releases that would require compiling in this new libxenon thing be only functional if you have this new version of Xell?  I'm really just concerned about re-opening my xbox and doing more work to it since it's working so well now.

    Well, it improves USB drive support, which is great... it also handles badblocks better....The recompilation i spoke of is only related to Corona video ;)

  7. Posted

    So this means , We can now play n64 emulator for coronas ? How do i install this please ? Thank you

    It doesn't automatically mean you can use any Libxenon homebrew, they need to be re-compiled with the new libxenon toolchain...How to install it? well, read the readme and you shall know... ;) otherwise, wait for an updated xeBuild GUI, J-Runner, AutoGG or whatever, they will all have this ;)

  8. Posted

    If you dumped before writing (like you should have) just rebuild using the correct key and reflash it using etheir xell (if that still boots) or using hardware flasher like NAND-X or similar

    Otherwise just use xeBuild GUI with the key you built with to extract kv etc. put them in the data directory (all decrypted variants of them without the name part that says if it's encrypted or decrypted (kv.bin, smc.bin, smc_config.bin)) then just build with the correct key...

    • Like 1

  9. Posted

    A quick update: In order for the CPUKey extraction to actually work you'll need to have Dashlaunch 3.01 or newer installed, any older dashlaunch version is incompatible (cOz added the feature i use with this version)

    i dont have a hard flasher and dont want to go buy one if it goes wrong. It is a beta. I learned from the ps3 scene to sit back and watch first.

    It's beta yes, but the read/write code for the nand has been tested for a very long time, i haven't heard of anyone having any major issues (the issues reported to me has been caused by faulty usb memories, which isn't really related to my tool in the first place)The reason i released it as a beta is because of the new features that haven't been tested for hours... i've done some tests, but not every single possible way... the features that make it a BETA:CPUKey extraction - Not tested a whole lot, but... it should work perfectly fine as it's afaik the same as the function which Team FSD have in F3, and the same that should be in the Dashlaunch installer (which also requires Dashlaunch 3.01 or newer in order to work)Automode - Well, it's for pre-defined commands, it might fail at some point, it shouldn't do that... but... i haven't really tested it out a shitload, just made sure that it runs the command expected...

  10. Posted

    great ! is this work with wireless or we should use a lan cable between xbox and pc ?

    It'll work with any networking connection you might have, wireless, wired doesn't matter... i'm working together with BlakCat right now to add some security to it so that it's safe to use, most won't even notice it since most of the time the transfer of the NAND goes fine, but... for the times that the transfer for whatever reason fails (say your cable sucks ballz or your wireless connection drops in the middle of the transfer, and comes back up losing data or whatever) Simple 360 NAND Flasher won't write anything (because it'd obviously be a bad thing to write a bad image ;)

    • Like 1
×
×
  • Create New...