Search the Community
Showing results for tags '17502'.
Found 2 results
I've successfully gotten xell to pop up and wrote down the key. Entered the key in JRunner with nandumb1.bin in the source then clicked the xecbuild to create the modded dash and I get a error box that says im missing ini's. Now, to further explain. I'm not connected to the internet. Reason why is because JRunner crashes instantly when the internet turns on. I downloaded the core pack from TX and run as Admin. Sooooo because I have this problem I downloaded the dash 17502 from the internet and extract to the xbuild folder. So now 17502 appears in the add dash drop down box in JRunner. The reason why I'm running 17502 is because my other console I made has it and it runs great for me. I'm very familiar with it and don't like change. I'm kind of kicking myself because I know I should had updated it first. I have successfully put the original dash back and it works great. Tried updating through USB to the newest dash and get a update error. The modchip is installed. But maybe it's a bad update. So I'm gonna try and redownload the newest update tomorrow and see if that works. Dunno if the chip being hooked to the console will be a problem. Whats the deal with the missing ini's? Anybody know a easy fix?
Hi all, So from what I can see, tydye81 is the only one left working on RGLoader right now, and is a very busy individual. In his most recent README: He encourages people to decompile RGBuild and build it again with support for new kernels and that it should be a relatively simple process. I was able to use ILSpy (a .NET reflector) to decompile the C# code for both RGBuild.exe and RGBuildLauncher.exe, edit it to fix some small compile-time errors generated most likely by ILSpy, and run the program in Visual Studio. After I got that working, I could only find dash/kernel versions hard coded into the program as the check boxes in RGBuildLauncher.exe. I assumed from this that RGBuildLauncher.exe just generates good arguments for RGBuild.exe based on what you put into RGBuildLauncher.exe, so all I did was add a checkbox for 17502. I was able to find the SE.17489.bin image on the forums   and have found a recommendation from a user that has RGBuild working on 17502 to use the same files from the 17489 filesystems to build the 17502 image and to spoof the kernel . If spoofing doesn't work, (it looks like it didn't work for this guy) I will need an SE.17502.bin from a devkit, and nothing really shows up for me when searching for that. So, at this point, do we just need to wait for someone to publicly release their 17502 devkit filesystems? Or is there a way we can build a 17502 RGBuilder image with the files available now?