Did you accidentally lift a pad somewhere, and yeah pics would be good. That spark concerns me though. I hope its nothing more than a lifted pad or trace.
jasper coolrunner not booting
- Thread starter windstorm
- Start date
no, i will take pictures, there was some glue on i think pins 2 pins, they are beside each other, i touched the knife on both at the same time by accident, when the power was in, the first time it sparked, the second time it turned the 360 on
---------- Post added at 06:03 ---------- Previous post was at 06:03 ----------
ya i had it plugged in, i will remember to mark them
---------- Post added at 06:03 ---------- Previous post was at 06:03 ----------
ya i had it plugged in, i will remember to mark them
if it sparked the first time why the f**k did you do it a second time ???
If you have messed it up you only have yourself to blame mate. This should be a lesson to others for sure . You can`t expect to go into your xbox with such stupidity and expect it to come out the other end working , it drives me nuts . What you should have done is spend a couple days READING so you knew what to do before you took the case off . Not screw it up and then start posting your mess ups.
Crazy !
If you have messed it up you only have yourself to blame mate. This should be a lesson to others for sure . You can`t expect to go into your xbox with such stupidity and expect it to come out the other end working , it drives me nuts . What you should have done is spend a couple days READING so you knew what to do before you took the case off . Not screw it up and then start posting your mess ups.
Crazy !
Last edited:
it was a very tiny spark i didn't think it sparked,, the second time i wrote the nand and i found it was booting, i thought maybe it was the tiny bit of glue on the pin headers, i started to remove it, and i noticed the 360 turned on
It doesnt really matter how small the spark was . if there was a spark then there was a short .
. One of the GOLDEN RULES in fact GOLDEN RULE NUMBER 1 is ALWYS unplug your board before touching it with something metal because if you dont you will kill it as you have probably just found out . A finger is more than enough to get hot glue off .
ok bollocking over now i`ll try and be helpful .
What are you using to write the nand (nandpro or jtag tool ? ). What size is the nand file you are trying to write ?
. One of the GOLDEN RULES in fact GOLDEN RULE NUMBER 1 is ALWYS unplug your board before touching it with something metal because if you dont you will kill it as you have probably just found out . A finger is more than enough to get hot glue off .
ok bollocking over now i`ll try and be helpful .
What are you using to write the nand (nandpro or jtag tool ? ). What size is the nand file you are trying to write ?
Last edited:
ya i learned my lessen after that, but it was too small to get my fingers in and i thought i had it unplugged
OK . Personally and it is just a personal opinion , i dont like it . I prefer to use nandpro as i know exactley what im doing with that . Especially for a big block jasper as you only need the first 64 meg of the nand not the whole 256 or 512 . I`m assuming when you dumped the nand it dumped a 16 meg file ? This is going to be your problem once we get the thing booting to xell again . If you have only got a 16 meg dump then you are going to have to use a donor nand to get this up and running and inject your KV into it .
Last edited:
i dumped a 16,256,512, a i did a few of the 16's, it was booting xell everytime, when i wrote it to the nand, but now it doesn't
seanr28
VIP Member
- Mar 7, 2004
- 1,203
- 0
When you say you flashed the whole image is that where it is left now?? If so re-flash the ecc file using +w command, try booting xell again.
The fact that it still powers on after a quick short is obviously a good thing, so at the minute your problems would apear to be with your freeboot image
I take it that your correct size image is able to be read in 360 flash tool?
The fact that it still powers on after a quick short is obviously a good thing, so at the minute your problems would apear to be with your freeboot image
I take it that your correct size image is able to be read in 360 flash tool?
he`s using jtag tool sean
If i were you I would flash the 256 dump back to the console and see if it boots to nxe dash before you try and make a free boot image if its a 256 , it would be useful if you knew exactley which one it was , you can do that with nandpro .
Get nandpro installed and i`ll send you come commands to try
If i were you I would flash the 256 dump back to the console and see if it boots to nxe dash before you try and make a free boot image if its a 256 , it would be useful if you knew exactley which one it was , you can do that with nandpro .
Get nandpro installed and i`ll send you come commands to try
Last edited:
seanr28
VIP Member
- Mar 7, 2004
- 1,203
- 0