I saw another post regarding this and was about to bump it, but then decided to make my own as not to hijack someone else's. I'm very interested in this topic though, been able to add the avatar/Kinect data without the need to force an update via USB would certainly speed things up, especially for those who offer RGH service and do many RGH consoles daily.
I'd also like to apologize for a long detailed post (and probably boring post), I only post detailed information because in the rules of this forum, it states that incorrect/bad information posted could result in infractions and I do not want to break the rules, so everything I post I check to make sure is accurate and correct to my knowledge. I can be such a bore sometimes lol, please read on though as my long boring posts usually have a point even if someone could have explained it in many fewer words, I'm a very thorough person and Im sorry if it offends. So to the topic at hand.
My current method, assuming we're using an official M$ hard drive, or a HDDHACKR made one. That was said to basically make sure the said hard drive is compatible with an un-modified Xbox 360 console. We can add the avatar/Kinect data using usual methods, which can be done easily by simply updating any clean console with that hard drive present at the time of the update, assuming that avatar/Kinect data was included in that update. This method is not always an option for those who only have one console (and that is the RGH console), so its not really a universal method and will not work for everybody.
The recommended method AFAIK is to get official update (OF SAME DASH VERSION, NO NEWER) and rename the update folder from $systemupdate to $$ystemupdate to prevent dashlaunch from blocking the update, then of course, perform the update, actually BL4K3Y has a tutorial
HERE. I will not get into that here; this post is already long enough as it is lol. This method does not always work either, I had to actually unload dashlaunch completely to allow the update to happen (with DL unloaded, the update using default $systemupdate should alert you of the available update). If you decide to unload dashlaunch BE EXTRA CAUSIOUS WHEN updating and make sure your Xbox is not connected to the net as it WILL attempt to connect to live as soon as you boot it up. So after reading all that you can see there could be considerable risk when updating or adding avatar/Kinect data to a RGH console when things dont work as expected. This is what brings me to post here about the Jrunner feature in Xebuild/Client mode Send Avatar/Kinect data. Personally Ive never got it to work, I usually dont have time to try to figure it out, I just simply revert to the above solution as to get the job done. I noticed the Send Xbox compatibility data feature too; assuming it works the same way seems very convenient and time saving also. So here it goes
Quote:
Originally Posted by
DreamZ
![View Post]()
You need to put the actual latest systempupdate folder in xebuild/dashnumber folder.
So for example 16203 would need the $systemupdate folder in jrunner/xebuild/16203
I have Dash 17150 and I have put the matching system update folder in the Xebuild/17150/ folder and when I click send it gives me a browse window. I assume it want the system update data, I select the $systemupdate folder and nothing
Quote:
Originally Posted by
Martin C
![View Post]()
Hi - I've found a bug in J-Runner which will be looked at. If I'm honest, it's more a bug with xebuild but we won't go into that.
In the meantime, you can run it from commandline from the xebuild directory:
xebuild client -e 16537\ -noenter
The backslash is important!
After reading this, then reading the Jrunner log, which states that the Jrunner version was 0.3 beta (1) and Im currently on 0.3 beta (4) I have to ask if this bug discovered has been addressed, at the same time I read that you said it could also be a Xebuild bug, so wondering if there was any news on it.
I have a Trinity RGH2 (coolrunner, I know its old) Original dash version is 16203, Current dash is 17150 and dashlaunch is 3.14, F3 is 3.0.775, latest versions AFAIK. Just to ask to make sure, for the send avatar/Kinect function to work, can I have the Xbox connected with freestyle running or does it need to be Xell or what?
I dont mean to ask what could be considered a stupid question (I dont believe in stupid questions by the way, just stupid people) lol. I just want to make sure Im approaching this correctly, I consider myself to not to be a newb at this, I do have much experience with RGH and ALWAYS use LAN to retrieve the CPU key as obviously reading from a screen and typing is for chumps, lol. So since the avatar data is sent over LAN also, I have to assume we have to have the Xbox console in a state where we can see the IP address of the unit and basically access it on Jrunner?
Thanks in advanced for any replies.
Sorry for making a novel out of a post, I just like to be thorough as possible as to get the best responses with the least amount of questions in replies about the situation at hand. Thanks again.
