gavin_darkglider

Aurora works with a database, so generally speaking it is a bad idea to try to downgrade, without starting with a fresh install. As for the fixes for ConnectX, you are speaking about, in the latest version, they dont fix the plugin, just made it so if the xex wasnt in the plugins folder the option doesnt show up in the options meny. On top of that, the other fix that was added was the option to unload connectX. Personally, if you ask me compared to NetISO, connectX isnt even worth wasting the time, but we havnt released that to the general public yet, due to it not being complete server side, and there needs to be connection error handling. That being said, with NetISO, the games load 1000X faster than they do with ConnectX, and you dont have to extract iso files. It also works with GOD format, which is nice as well, and when using it, you can rip the game from the iso to your hard drive, as well, which gets rid of the need to extract to install as well. Long story short, the issues with connectX will never be fixed, as it is just a patched plugin for a devkit. We have no control over the inner workings of the plugin, so we cant update it to work with the latest SMB protocols. Basically you are forced to use SMB protocols from 2002 on your server for it to connect, and those are flawed. Just my 2 cents.

Passed upstream to devs.

You might be able to glitch it into booting freeboot, but that mightbe iffy. you should be able to patch the image to work with a devkit, but I dont have those patches, or the time to try and figure that out. If I was interested in this, I would ask 15432, who managed to get freeboot to boot on the winchester using a devkit cpu. He/She might be able to point you in the right direction.

I believe felida looked into this, and couldnt get it to work. I myself dont do skins, so he is the one to ask.

I have no access to approve accounts. I can do covers, but not accounts.

The winbond patches are also included with J-Runner, so that is probably the easiest option if the updserv option is out of your hands. That being said, starting the dashlaunch installer, with the updserv option enabled, and while that is running on the xbox, open a command line where xebuild is located, and type xebuild update -f <dashversion> It should update the kernel, and if you put the $SystemUpdate folder in the xebuild/<dashversion>/ folder, then it will automatically update the avatar data as well. Obviously for this to work, you need to be on the same network, but most people only have one. lol.

Use the xebuild updserv option, and it will use the SMC included in the nand image you already have flashed, instead of trying to patch it fresh. You could also use the updflash.bin file instead, and get the same results. Xebuild dumps the required files that need patched, and if they are already patched, will inject them into the next image, instead of trying to patch them again. Hince all the problems I had with my R-JTAG not working with the glitch patching, as the patch for that in j-runner was used instead, so it failed to patch the SMC.

Chances are it is the stealth plugin being loaded by dashlaunch that is causing the problems. That being said, we do not support stealth here, and because you are using it, this thread is now closed, and you will get no more support with this issue. Edit: lol, I locked my own thread. Oops.....

I never got in with the trainer devs like you, because cheating wasnt really that interesting to me. lol. So, I will take your word for it. I cant think of a reason why this would be happening unless there is a plugin confilct somewhere. There is always the possibility that the users that are experiencing these issues are on an older dash version, and that could be causing problems as well.

For what it is worth, I have seen a lot of computers, and game systems get those lines, and 99.9% of the time, it is a hardware related issue, not software. Unfortunatly, there are no real hardware stress tests for the xbox, but if there were I would say run one on the video card, and see how it reacts.

I am not sure why you would need to do that. Have you tried to unload nova first? it was always recommended since 0.3b, when trainers were introduced into aurora, that you unload all plugins(Dashlaunch included) before running aurora trainers, due to the fact the plugins could interact with the trainer engine, and cause unwanted problems, like what you are experienceing now.

You go to modules, and unload the nova plugin.

Your Image is broken, but chances are, that you need the XUI Tool extensions for aurora, which came in with 0.7b. you can find them here: http://phoenix.xboxunity.net/downloads/AuroraElements (XUI Extensions).rar Instructions can be found at phoenix.xboxunity.net at the end of the post for aurora 0.7b not 0.7b.1 hotfix(So, the end of the second post on the page.)

Sorry, was meaning to give more information, not single you out. lol. I was going to remove the quote, once I finished, but was in a bit of a rush at the time. lol.

This isnt possible without those adapters, because the console doesnt accept non authenticated controllers, and it doesnt have drivers for other non xbox controllers. So, the adapter will copy the code from a working controller, and then will use the xbox controller usb communication standard to translate the codes. There have been devices made for just specific devices, but that was mainly for keyboard and mouse. https://team-xecuter.com/xfrag/ This was before the CronuxMax line, which will do that and more.

I think I might still have the script that was used to test this function somewhere..... let me look into what I have laying around in the old hdd, and I will get back to you.... After looking at what I still have from testing 0.7b, I dont have any test lua files that use that function, so I am in the dark on that as well. I will drop a line to the devs to see if I can get them to update the API.

It sounds like the updater didnt unload the plugin, try unloading the plugin, and see if it updates.

First, if you were such a bad ass programmer, you would have figured this much out by now. Second, if you want any information on how those files are used, dissassemble the xex with IDA Pro. From there you have the whole blueprint for the game engine, which will tell you more than a hex editor, or any of us on this forum. The only reason skyrim has mods like this on the 360 is because the game came out on the PC with a homebrew mod options. Since it is the same game, compiled for a different CPU, modders already know what is up with the files. If you could find a PC version of the game, and you can find tools to do this for that version of the games, and then might be able to take what you learn there and apply it to the 360 version. Personally for what you are trying to do, a Nintendo Switch, with LayeredFS(CFW Option), would be a better option, as it is designed primarilly for this sort of application. Unfortunatly the xbox doesnt do this. On top of that some game developers pre-compile assets(Hince why we needed the aurora asset editor) into d3d maps, because it is faster than loading an image file, and having the console convert it into a d3d map to load. Once again this is a development choice, and every developer is different about how they write code. I have seen many code implementations that are all different, but essentially do the same thing over the years. This applies to all programmes, so until you step through the dissassembled XEX, and spend way more time then you want looking at that code, you wont have the first idea of what to do.

Making a small block image wont work. The best option is to install a dual nand solution, with a 16mb nand. the demon works nicely for this, but those are getting harder to find these days. there are other options that will get you where you want to be, but not nearly as easy.

here is the relative commit from retroarch to add support for aurora's launch data. https://github.com/Swizzy/RetroArch/commit/f3f527ba206ea2b6d803b758d1d53372d81df24c I am not going to do the work on this, as I do not have time to. but that is where I would start.

If you can find the code, it shouldnt be that hard to add, but I do not have that code, so I cannot try it.

You are welcome.

You can skip the update. What version does it report running?

I dont see any problems either. I know I have had issues if I didnt unplug the console after writing the nand, but this is usually when writing 16mb nands with a hardware flasher, mainly because the SMC doesnt reload, after nand write. Chances are though, that you are experiencing the Read only issue with the 4GB MMC nands in corona big block consoles, and the only way to fix that is to remove the nand that is there, install a new 16 mb nand, and move a bunch of resistors, Then once that is done, you need to create a new 16mb image using the files you have. Lucky for you this doesnt hurt retail, as Microsoft doesnt look for nand swaps usually, so you could also convert your retail image if you wanted as well. All that being said, it is not an easy repair, so I would find someone to do it for you, if you arent comfortable with that.

Please dont thread hijack, also, 0.8 has hardly been started, so it will be a while.