Thanks, I'll do that when my Nand-X arrive, shipped out 5/28 and it's still not here yet!
installed nand-x now 360 wont turn on
- Thread starter biggnutz
- Start date
hi here are some photos of jtag tool n nad compare
[ame]http://rapidshare.com/files/395512509/1.bmp.html[/ame]
[ame]http://rapidshare.com/files/395512696/2.bmp.html[/ame]
let me know what u think
[ame]http://rapidshare.com/files/395512509/1.bmp.html[/ame]
[ame]http://rapidshare.com/files/395512696/2.bmp.html[/ame]
let me know what u think
Well...As far as my intuition about your problem goes, I really really think that there is some problem with your JTAG part. Because with your original NAND, your 360 is working fine, while with Xell, it does not work, so this rules out any problem with reading or writing to your NAND.
So, either your JTAG QSB has some problem with it, or your connections aren't right, or you forgot to change the JTAG from OFF to ON and only kept changing the resistor values
.thanks i think ur right ill make a jtag hack with a diode whats the best tutorial u think to do this pls.
1. Couldn't you attach the images in your post? That way, they are much easier for everyone to view.
2. You should post a screenshot of Degraded too, because if even if you dump your nand 3 times and all of them have bad blocks at exactly the same place, NAND Compare won't tell you that there are bad bloacks on your nand. While, Degraded tells you whether your nand dump has bad blocks or not.
3. You should also post a screenshot with your nand opened in 360 Flash Dump Tool.
4. As far as JTAG Tool goes, the settings seem correct for your Xbox360. But there is nothing else of interest there.
The diodes are already present in the cables provided with Nand-X for the JTAG part. Just make it 100% sure that both the cables of JTAG and the QSB are perfectly in contact with the points of solder with the motherboard and RoL(in your case). Also make sure that the JTAG connection is active when you install and run Xell. It is a common mistake that people just change the resistor setting on the JTAG QSB while the JTAG switch is OFF, and thus their Xell doesn't boot.
So, go easy and calmly solder those points and make sure everything is perfectly done. Don't rush, and do everything systematically. I believe that if everything goes fine, which I hope it does...Your Xbox360 will work fine even when you install Xell.
Last edited:
Ubergeek
Xecuter Groupie
Absolutely correct. That's just what I said. I just can't understand that he already has installed the JTAG part 2 times. He couldn't have made the same mistake twice while installing it...Or could he ???
Well, you are correct. But which image in the last post of biggnutz do you think is worth 1000 words ?
Last edited:
@ biggnutz
Do you maybe have a Jasper with a CB version 6712?
If so, check my post here:
http://team-xecuter.com/forums/showpost.php?p=277252&postcount=22
I had the same problem - soldered the Jasper, read the NAND, wrote Xell and then - NOTHING.
Box didn't power up (no button worked), only worked again after reflashing the original NAND.
I think there may be a bug in JTAG Tool for this CB version of Jasper.
Because if you flash Xell manually with NANDPro with the right Xell-Image everything works fine.
Give it a try...
Do you maybe have a Jasper with a CB version 6712?
If so, check my post here:
http://team-xecuter.com/forums/showpost.php?p=277252&postcount=22
I had the same problem - soldered the Jasper, read the NAND, wrote Xell and then - NOTHING.
Box didn't power up (no button worked), only worked again after reflashing the original NAND.
I think there may be a bug in JTAG Tool for this CB version of Jasper.
Because if you flash Xell manually with NANDPro with the right Xell-Image everything works fine.
Give it a try...
Hey guys, If I update my kernel to 7371, will it fix the bad block on the nand? I have the old dashboard kernel 6645.
You didn't tell which MB you have. Because if you the 256MB or 512MB version of Jasper, there is >90% chance that there will bad blocks on it, and updating your console won't fix them.
But still, it is recommended to update to 7371 before Jtagging because freeboot may have compatibility problems with any kernel other than 7371. So, you should atleast update to 7371 and then dump your NAND. If there are bad blocks on it, you should try XNAND Healer or Bad Block Remapper to fix them.
U could be right ill give it a go makes sense.it does say on the tutorial (- Xbox 360
with kernel version 7371 or lower(Some 7371 and 7363 consoles may not work if they have the patched CB Console manufature date of 6-1-09 and later ) n mine is 09 model. ill try n do it manualy without jtag tool.
with kernel version 7371 or lower(Some 7371 and 7363 consoles may not work if they have the patched CB Console manufature date of 6-1-09 and later ) n mine is 09 model. ill try n do it manualy without jtag tool.
Opus...Interesting. Anyways, still update your kernel to 7371 and then dump your NAND. Then post your results. After that, we will see what we can do. OK ?
Is it always recommended to update to kernel 7371 no matter what motherboard type I have? I have a jasper with 7363 from June. There is a chance, its possible to JTAG it right?
BGAMods
VIP Member
june 2009 is the cut off date i believe so itll be close. its always recommended to update to 7371 as thats what freeboot is built on. the best thing is to dump the nand as its the only way to be sure that its exploitable. good luck mate i hope it is.