Search the Community
Showing results for tags 'r-jtag'.
Found 2 results
-
? Hey guys.. What a bad day. My previous 360 Phat (Fffffalcon board) bummed out on my, so I bought another working board for a few bucks. After I removed the complete R-JTAG with all QSB's and reinstalled it into the new Jasper board, I couldn't get it to glitch (POST79 LOAD_XAM each time although XELL should not get to 79). Some time later I decided to wire the AUD_CLAMP manually using the 2 x 1N4148 diodes and an optional resistor method, as the little QSB suffer previous damage. As soon as I did that I started getting RRODs each time I try to boot XELL. I triple check everything and found that I accidentally soldered the AUD_CLAMP wire to Q2N3 instead of Q2N1 ? Do you guys think I fried it? Gettin 0022 RROD with each try AND with the whole R-JTAG disconnected ?☹️? EDIT: Error 0022 not 0010 sorry
-
So I went away for a few days and let my younger brother use my fairly new R-Jtag Falcon, anyways when I got home he told me he opened up Dashlaunch to try and install homebrew, something came up about DL being incompatible with something and I guess he hit install anyways, It's been starting up to the MS dash ever since. The first thing I did was boot the console with the diskdrive and it booted Xell but I don't know where to go from here, I used a disc I have for xex menu and it did nothing as well, I've been referred to two options to resolving this but not sure which approach is better suited to take, one was to create a new nand, where the other was to simply change my launch.ini file. Can anyone help me with figuring out the best option and how to go about doing it or even show me a guide to do it. Thanks.
