A buddy of mines just got a chance to install my x3 modchip along with 80 gb HD into my Halo SE Xbox. Everything was fine until we tried to boot it up. When we did this, the power button flashed orange, nothing was on the screen, and the box turned off and on three times or so. He put his xecuter 2.6 in my box and it worked fine, so he put my chip in his and it did the same thing(flashing lights and so). Does that mean the chip is bad? I bought it from system-mods about a month ago and just had time to put it in and looking at their return policy doesn't look like they'll take it back, so I hope its not a bad chip. Please help! Is there anything else I can do to see if the chip is good? Thanks Folks
X3 Problem
- Thread starter Speeder
- Start date
Martin C
VIP Member
What banks did you set the X3 to boot from?
have you tried all the banks?
What BIOS is on the 2.6 you tried??
Martin
have you tried all the banks?
What BIOS is on the 2.6 you tried??
Martin
NAND-X , Dumping NAND & Jtagging - A few Questions.
Just been reading up on subject of NAND and Jtagging for about and hour and half now. I still have a few questions that I can't find answers to and would appreciate it if someone on here could answer them for me!
First all of all I'm pretty sure I will be purchasing the Xecuter NAND-X to perform this as this seems like the most up to date, easiest and safest method. And using CoolShrimp's Jtag tool.
1. I have a Jasper Arcade with 2.0.7 Dashboard (MFR yyyy-mm-dd 2009-08-11) What are the chances of it being 'Jtaggable'
2. No matter what motherboard or dashboard, every NAND is DUMPABLE, correct?
3. Is it possible to write 'Xell' to all versions of motherboards & dashboards?
4. Assuming the answer to Q2 is TRUE and Q3 is FALSE. Can I use the NAND-X to dump the NAND and check the CPU key using a windows based program rather than checking it through booting the console? I think this would be very useful for those console which have lost their DVD key.
Thanks alot.
Just been reading up on subject of NAND and Jtagging for about and hour and half now. I still have a few questions that I can't find answers to and would appreciate it if someone on here could answer them for me!
First all of all I'm pretty sure I will be purchasing the Xecuter NAND-X to perform this as this seems like the most up to date, easiest and safest method. And using CoolShrimp's Jtag tool.
1. I have a Jasper Arcade with 2.0.7 Dashboard (MFR yyyy-mm-dd 2009-08-11) What are the chances of it being 'Jtaggable'
2. No matter what motherboard or dashboard, every NAND is DUMPABLE, correct?
3. Is it possible to write 'Xell' to all versions of motherboards & dashboards?
4. Assuming the answer to Q2 is TRUE and Q3 is FALSE. Can I use the NAND-X to dump the NAND and check the CPU key using a windows based program rather than checking it through booting the console? I think this would be very useful for those console which have lost their DVD key.
Thanks alot.
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
1. slim to none
2. Yes just cant write on non expoitable
3. no
4. no
1. slim to none
2. Yes just cant write on non expoitable
3. no
4. no
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
After dumping the NAND image (correct term?) can the image not be opened in a windows based program to display the key etc?
I'm thinking this would be a worthwhile tool to use on motherboards which have lost the DVD key by extracting the NAND and copying down the key from it.
After dumping the NAND image (correct term?) can the image not be opened in a windows based program to display the key etc?
I'm thinking this would be a worthwhile tool to use on motherboards which have lost the DVD key by extracting the NAND and copying down the key from it.
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
2.Yes you can read any NAND on any board, and you can write it any of them but even if you try to write XBR/Freeboot to a motherboard with 8955 or higher the jtag will not work since the efuses in the CPU are burnt thus blocking the jtag.
3. Yeah you can write whatever you want to any nand just don't expect the Xell to work on a console that cant be jtagged so anything higher than 7371 is not jtaggable.
4. No you can't because the CPU key is the one used to encrypt the NAND image therefore you need to write Xell onto a jtaggable console then boot it, and see the CPU key, then you can use 360 flash tool and open the NAND image and decrypt the nand using the CPU key of the console which will reveal the dvd key.
Also, to me the NAND-X is a overpriced tool. If you are handy with a soldering iron you can easily do it with 3 wires and 2 diodes the jtag wiring and the nand read wiring you can find like homemade usb nand readers for less.
1. I don't know what you mean by 2.0.7. Tell me the regular dashboard numbers like 9199, 8955 or whatever. You can only jtag consoles that have 7371 dashboard or below.Farly said:
2.Yes you can read any NAND on any board, and you can write it any of them but even if you try to write XBR/Freeboot to a motherboard with 8955 or higher the jtag will not work since the efuses in the CPU are burnt thus blocking the jtag.
3. Yeah you can write whatever you want to any nand just don't expect the Xell to work on a console that cant be jtagged so anything higher than 7371 is not jtaggable.
4. No you can't because the CPU key is the one used to encrypt the NAND image therefore you need to write Xell onto a jtaggable console then boot it, and see the CPU key, then you can use 360 flash tool and open the NAND image and decrypt the nand using the CPU key of the console which will reveal the dvd key.
Also, to me the NAND-X is a overpriced tool. If you are handy with a soldering iron you can easily do it with 3 wires and 2 diodes the jtag wiring and the nand read wiring you can find like homemade usb nand readers for less.
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
No, the CPU Key and DVD key are different. But they only tie together cause the CPU key decrypts the nand. If you decrypt the nand you can put any dvd key you like all zeros whatever floats your boat. Just gotta inject that into the nand image then save it and flash it back to the xbox.
No, the CPU Key and DVD key are different. But they only tie together cause the CPU key decrypts the nand. If you decrypt the nand you can put any dvd key you like all zeros whatever floats your boat. Just gotta inject that into the nand image then save it and flash it back to the xbox.
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
I wouldn't hold my breath. The xbox 360 and the new xbox 360 S are software identical. The reason the jtag exploit works on some xbox 360s is the fact that Microsoft slipped up in their dashboards for a bit. It first emerged as the king kong exploit where people noticed they could change some unsigned shaders. Then, this king kong exploit grew into the jtag exploit. Now, once you update a console to anything higher than 7371 then the efuses of the cpu get burnt therefore blocking the jtag exploit. Now, since all xbox 360 s come with probably either 9199 or 8955 then there is no way to even attempt to jtag it. I'm unsure whether how you'd even go about wiring it. Hell, I don't even know how to read the nand on the xbox 360 s.
I wouldn't hold my breath. The xbox 360 and the new xbox 360 S are software identical. The reason the jtag exploit works on some xbox 360s is the fact that Microsoft slipped up in their dashboards for a bit. It first emerged as the king kong exploit where people noticed they could change some unsigned shaders. Then, this king kong exploit grew into the jtag exploit. Now, once you update a console to anything higher than 7371 then the efuses of the cpu get burnt therefore blocking the jtag exploit. Now, since all xbox 360 s come with probably either 9199 or 8955 then there is no way to even attempt to jtag it. I'm unsure whether how you'd even go about wiring it. Hell, I don't even know how to read the nand on the xbox 360 s.
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
Suppose, although nobody knew how to do the first Xbox 360 console when that came out. They'll figure out how to the NAND of the new console eventually, just give it a bit of time.Smkface said:
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
Yeah, sooner or later they will figure that part out. But, there isn't much to you know gain from that. I mean you read the nand, it's nothing new in there. Haha.
Yeah, sooner or later they will figure that part out. But, there isn't much to you know gain from that. I mean you read the nand, it's nothing new in there. Haha.
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
smkface, I am pretty sure you cant write to the nand period. As you know the 7371 dash above blows efuse to what enables you to write to the nand thus writing xell to see cpu key.
smkface, I am pretty sure you cant write to the nand period. As you know the 7371 dash above blows efuse to what enables you to write to the nand thus writing xell to see cpu key.
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
Well marshamods you're wrong. You can write and read nand on any console. How did people uncripple their HDD usage when they were banned? That's because they read their nand off their 8955 dashboard consoles and modified it so it removes all the secdata and wrote it back to the nand. If you don't believe me go solder lpt connections to the newest original xbox 360 and find out for yourself.
Go ahead and read this tutorial if you don't believe me it tells you how to go about the uncrippling. Read the bold and it never says that you can uncripple 7371 and below nands.
http://forums.xbox-scene.com/index.php?showtopic=697231
Also, the burning of efuses prevents you from running the jtag hack NOT reading and writing to the nand. You can write xell/xbr/freeboot to a unjtaggable console if you wish but it just simply will not boot.
marshamods said:
Well marshamods you're wrong. You can write and read nand on any console. How did people uncripple their HDD usage when they were banned? That's because they read their nand off their 8955 dashboard consoles and modified it so it removes all the secdata and wrote it back to the nand. If you don't believe me go solder lpt connections to the newest original xbox 360 and find out for yourself.
Go ahead and read this tutorial if you don't believe me it tells you how to go about the uncrippling. Read the bold and it never says that you can uncripple 7371 and below nands.
http://forums.xbox-scene.com/index.php?showtopic=697231
Also, the burning of efuses prevents you from running the jtag hack NOT reading and writing to the nand. You can write xell/xbr/freeboot to a unjtaggable console if you wish but it just simply will not boot.
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
I jtagged it and dumped anidentical Nand.
Are there any tutorials around that show you how to inject a new DVD key in the Nand?
Oh and just to let you know I dont know the CPU key
as its a 8955 version dash
Thanks
SMKface I have a console with Dashboard Version 2.0.8955 and I think it has the wrong dvd in it along with the wrong DVD key.Smkface said:
I jtagged it and dumped anidentical Nand.
Are there any tutorials around that show you how to inject a new DVD key in the Nand?
Oh and just to let you know I dont know the CPU key
as its a 8955 version dashThanks
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
Thanks for correcting me smkface. I know a little bit more now.Smkface said:
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
Um, did you really just ask me that? I just explained it a couple of posts ago. YOU CANNOT JTAG A CONSOLE WITH ANYTHING HIGHER THAN 7371! You did not jtag that console you simply dumped a nand. You can do that on any console. You won't get a dvd key for it since you can't get the CPU key to decrypt the nand, because you can't run Xell on the xbox to get the CPU key because you have a dashboard higher than 7371. ITS IMPOSSIBLE TO GET A LOST DVD KEY FROM A CONSOLE WHOSE DASHBOARD IS HIGHER THAN 7371. So you have a expensive dvd player on your hands at this moment.hackerjoe said:SMKface I have a console with Dashboard Version 2.0.8955 and I think it has the wrong dvd in it along with the wrong DVD key.Smkface said:
I jtagged it and dumped anidentical Nand.
Are there any tutorials around that show you how to inject a new DVD key in the Nand?
Oh and just to let you know I dont know the CPU key
Thanks
Re: NAND-X , Dumping NAND & Jtagging - A few Questions.
how do i find out what number my dashboard is? call me a noob if you want but idk where to find itt.
how do i find out what number my dashboard is? call me a noob if you want but idk where to find itt.