Hello,
Although I'm newly registered user here I know about this place a long time ago, reading it through and through almost every day now. First of all I would like to THANKS to all the Xecuter Team for their work and products which is simply fantastic. Big thanks goes also to everyone from first line support for their help and knowledge! I bought several products made by Xecuter in the past, starting from their X360 opening tool, through CK3 Lite, CK3 Pro with Probe and finally NAND-X with few QSB JTAG kits. Although I had some troubles while using them, I allways succeed at the end because I always found the same issue that users had here and that were always solved by your excellent guides/answers.
Now I have JTAG'd three consoles for me and friend. His was Xenon and Falcon, mine was Falcon. His both consoles went great (using QSB and in case of Falcon using JTAG Kit #2). For my Falcon I used JTAG Kit #5 and I succeed as well (had E79 problem but after some reading I solved it by setting the resistor to 470 Ohm). Freeboot and FSD working just fine on all of them now.
I decided to bought one more console for me and him (just for backup). I found two candidates so I spent some money and tried to JTAG them. Unfortunately, one of them, JASPER 512M from August 2009 with Dashboard 7363 is not JTAGable (CB=6750). Well, sh*t happens. The second one is Falcon, CB=5770, same as my first one, so I did the same work. Again I choosed QSB method and JTAG Kit #5 for some reason (looks better, I do not like wiring and there is no possibility to remove motherboard from the case without unsoldering yellow wire from the ROL panel).
I have to say that all the solder work has been done by my colleague from work since I am not able to solder. From my point of view their job is excellent (I can post some photos later if needed). Well, I did the same work like with my first Falcon and Freeboot is successfuly installed. Following is the problem:
I noticed that when I turn OFF the console it won't turn OFF my wireless controller (holding Guide button -> Turn OFF the console). Upper left light from the quadrant on the controller stays ON. In this state, turning ON the console using this controller is not possible. Turning ON the console using power button went into 3 RRoD, subcode 0020. I tried repeatedly turning the console OFF and ON using the power button, same situation. When I removed the battery from the Wireless Controller and wait a while, then I am able to turn the console ON and Freeboot is working as it should. I put the controller ON, can use it with no problem, unless I put the console OFF. Then the situation repeats.
I tried again to disassemble whole console, soften the MB, GPU and CPU screws a little, at the end removed motherboard from the case, tried the resistor parameters on JTAG Kit #5 to all positions (0-330-470), nothing has help. So I tried to write my original NAND back to see if this could help. After writing it I put both switches on JTAG Kit #5 to position OFF and in this state my Falcon won't power up at all (using standard power button). Then I moved ON/OFF switch on JTAG Kit #5 to position ON, tried different resistor parameters and in this state the console boot up well and I have back my original dashboard 7371 (when I think about it, what is the reason to have two switches on JTAG Kit #5 that could be set to position OFF?). OK, but when I put my wireless controller ON, synchronize it with the console and try to turn the console OFF (again using Guide button on the controller), it again turns OFF console only and controller stays ON. In this state, when I turn the console ON using standard power button, I am getting 3 RRoD like in the situation above (have not tried to check subcode but I suppose it is the same 0020 like before). Again, I can boot up normaly only when I took away batteries from my controller, wait a while and then pressing power button on the console.
At this stage I am out of any idea and strongly believe that there is something that could help me (hoping nothing has blew up on my console).
My appologies for such long post but I wanted to say "THANKS" somehow and tried to describe the problem as detailed as possible. And please, excuse my english.
Thank you.
Although I'm newly registered user here I know about this place a long time ago, reading it through and through almost every day now. First of all I would like to THANKS to all the Xecuter Team for their work and products which is simply fantastic. Big thanks goes also to everyone from first line support for their help and knowledge! I bought several products made by Xecuter in the past, starting from their X360 opening tool, through CK3 Lite, CK3 Pro with Probe and finally NAND-X with few QSB JTAG kits. Although I had some troubles while using them, I allways succeed at the end because I always found the same issue that users had here and that were always solved by your excellent guides/answers.
Now I have JTAG'd three consoles for me and friend. His was Xenon and Falcon, mine was Falcon. His both consoles went great (using QSB and in case of Falcon using JTAG Kit #2). For my Falcon I used JTAG Kit #5 and I succeed as well (had E79 problem but after some reading I solved it by setting the resistor to 470 Ohm). Freeboot and FSD working just fine on all of them now.
I decided to bought one more console for me and him (just for backup). I found two candidates so I spent some money and tried to JTAG them. Unfortunately, one of them, JASPER 512M from August 2009 with Dashboard 7363 is not JTAGable (CB=6750). Well, sh*t happens. The second one is Falcon, CB=5770, same as my first one, so I did the same work. Again I choosed QSB method and JTAG Kit #5 for some reason (looks better, I do not like wiring and there is no possibility to remove motherboard from the case without unsoldering yellow wire from the ROL panel).
I have to say that all the solder work has been done by my colleague from work since I am not able to solder. From my point of view their job is excellent (I can post some photos later if needed). Well, I did the same work like with my first Falcon and Freeboot is successfuly installed. Following is the problem:
I noticed that when I turn OFF the console it won't turn OFF my wireless controller (holding Guide button -> Turn OFF the console). Upper left light from the quadrant on the controller stays ON. In this state, turning ON the console using this controller is not possible. Turning ON the console using power button went into 3 RRoD, subcode 0020. I tried repeatedly turning the console OFF and ON using the power button, same situation. When I removed the battery from the Wireless Controller and wait a while, then I am able to turn the console ON and Freeboot is working as it should. I put the controller ON, can use it with no problem, unless I put the console OFF. Then the situation repeats.
I tried again to disassemble whole console, soften the MB, GPU and CPU screws a little, at the end removed motherboard from the case, tried the resistor parameters on JTAG Kit #5 to all positions (0-330-470), nothing has help. So I tried to write my original NAND back to see if this could help. After writing it I put both switches on JTAG Kit #5 to position OFF and in this state my Falcon won't power up at all (using standard power button). Then I moved ON/OFF switch on JTAG Kit #5 to position ON, tried different resistor parameters and in this state the console boot up well and I have back my original dashboard 7371 (when I think about it, what is the reason to have two switches on JTAG Kit #5 that could be set to position OFF?). OK, but when I put my wireless controller ON, synchronize it with the console and try to turn the console OFF (again using Guide button on the controller), it again turns OFF console only and controller stays ON. In this state, when I turn the console ON using standard power button, I am getting 3 RRoD like in the situation above (have not tried to check subcode but I suppose it is the same 0020 like before). Again, I can boot up normaly only when I took away batteries from my controller, wait a while and then pressing power button on the console.
At this stage I am out of any idea and strongly believe that there is something that could help me (hoping nothing has blew up on my console).
My appologies for such long post but I wanted to say "THANKS" somehow and tried to describe the problem as detailed as possible. And please, excuse my english.
Thank you.
Last edited: