Jtag Help On A Jasper 512

[style2bboy]

o i have done the following

1# Dump 2 nands !

2# compare Good !

3# Inject KV and Confing to xbr!

4# WRITE XBR

and then i soldered the jumper and the Diode
once i turn on the xbox it powers up but i don't get no video or NO Error.......
i Have flash like 5 times now and flashed back to the back up nand dump1 and work fine but no luck with the xbr.bin??

i have used 360 flash tool and The CB is 6723 on a jasper 512
 i have Flashed Xell it is called jasper-6723-hack-for-256mb-512mb.bin i boot up the xbox but once again thing i pushed the eject too no luck !!

i have also tried to Erase the nands i did this >>>> nandpro.exe usb: -e512 1000

i was told that doing this won't effect the XBR flash since i well be erasing from block 1000
but NOP!!!!! did not work i booted up the xbox i got the Christmas lights so i Injecting just the KV and The config to the xbox and just got nothing just like last time!! just the green power light comes on

well what else should i do now?? uhh.gif

[ReverseAffect]

recheck your 2 diode connections.....check them with a meter..if your not getting xell/xellous ,that be the issue
did you have any badblocks?

[style2bboy]

NO Bad Blocks......and i have use 3 different NEW set's of 2 diode's

also i have tried 3 different style of JTAG Connections

>>>>>http://img145.imageshack.us/img145/7457/reversejatg.jpg

>>>>>http://boxxdr.com/boxxdr_jtag.jpg

But no luck i well tell you when i had the xbox power on be for i jtag it i was not able to see or format the default memory on the onboard memory of the xbox???

[muller1000]

Well, if you have done everything by the book your jasper may not be exploitable. I would double check your cb version via hex editor. I made that mistake only once. What is the manufacture date on the console? After June may have patched 7371 kernel.

[ReverseAffect]

the Op stated this,
i have used 360 flash tool and The CB is 6723 on a jasper 512
 i have Flashed Xell it is called jasper-6723-hack-for-256mb-512mb.bin i boot up the xbox but once again thing i pushed the eject too no luck !!


what was the commands you used for injecting jasper6723hackfor256mb512mb.bin?
your kv and your config?
if anything pass me your good nand copy to have a look at it...

[muller1000]

I would get back to stock dash & only use jtag tool by cool shrimp 1.74 to redump nand and write xell. If that comes up with christmas lights then cb needs to checked again with hex editor or check diodes. When I used 360 dump tool it gave exploitable cb but when checked manually with hex editor the cb was in fact patched.
At 00008400, if it starts with "43 42 1A 5E", this mean that you have an unexploitable jasper and the CB is 6750.
 
The only two programs needed are Jtag tool by cool shrimp 1.74 to write xell and freeboot and 360 flash dump to get cpu key. There should be no problems if soldering and correct positioning of diodes and jumper wires are correct. I still use nand compare to triple check my dumps.

[ReverseAffect]

I would get back to stock dash & only use jtag tool by cool shrimp 1.74 to redump nand and write xell. If that comes up with christmas lights then cb needs to checked again with hex editor or check diodes. When I used 360 dump tool it gave exploitable cb but when checked manually with hex editor the cb was in fact patched.
At 00008400, if it starts with "43 42 1A 5E", this mean that you have an unexploitable jasper and the CB is 6750.
 
The only two programs needed are Jtag tool by cool shrimp 1.74 to write xell and freeboot and 360 flash dump to get cpu key. There should be no problems if soldering and correct positioning of diodes and jumper wires are correct. I still use nand compare to triple check my dumps.

yep had the same issue on a 16mb jasper with the cb 6723 360 flash tool showed 6750 only...
so just to be on the safe side ,muller1000 is right...stick with the hex edit to see the cb
also i find out autohacker works like a charm seeing the cb in secs at startup...

[muller1000]

Also like to share something else & a warning to others. When I was dealing with that 512 I also came a cross a hazardous buggy program. I was using nandpro20c windows Gui at the time and was taking good dumps and writing back ok when out of nowhere I started to get bad block errors when verifying after write. I thought ok got 5 good dumps but and every time I wrote them back with nandpro20c it did the same thing.

I thought it was my nand and spent 2 days with no luck. I then started to come to a realisation it may be the program and to my horror everytime I opened a clean orig nand it would end up being corrupt. All my good nands were F&*cked up.The only thing that saved my 512 from being a paper weight was that I had one and only good dump in my recycle bin & luckly I didn't use nandpro20c windows GUI. So I deleted that program and just use cool shrimp freeboot program as stated previously.  

This may of only happened to me but thought I should share that if people are currently using it and getting bad block errors & not being able to recover back to stock dash with their original dumps when previously everything was working just fine ..

[ReverseAffect]

so what are you using now?
nandpro20b or nandpro20e?

[muller1000]

Sorry it was the nandflasher 360 for windows version 1 by Trancy that uses nandpro. That program may have a serious bug. I was doing everything manually  but got lazy and tried nandflasher 360 but end up being disastrous.  I now only use jtag tool by cool shrimp 1.74 to redump nand and write xell. As I can just use the  read/ write feature via usb without any issues.

[ReverseAffect]

needs to be moved to tech support...

[style2bboy]

Wow Thanks for all the post 

im using the new Autohacker V2.1..... the V2.1 now well tell you have you have a
Jtagable that was one of the update on autoHacker said by the maker

I have checked manually with Hex workshop hex editor 6 and at 00008400 i have (43 42 1A 43) is that good?

the command i used for Xell >>> C:\Nandpro20b\nandpro.exe usb: -w512 jasper_6723_hack_for_256mb_512mb.bin 0
name of file is >> jasper_6723_hack_for_256mb_512mb.bin

im using NandPro20b

[style2bboy]

i Have used jtag tool coolshrimp i read the nand and i got

Error 210 Reading Block 6932
Error 210 Reading Block 7EB9

so i used 360 Flash tool V0.94 and it does not show no Bad BlockS???

but the dumps do match 100% .......what else can i use to see if i have bad blocks or what can i do?   

[style2bboy]

you think by erase the NAND at first? All of it? BB's does it tend to have issues regarding the filesystem of the NAND (the "MU" part of it) and the user sometimes should i Erase  the whole NAND, write XBR, and never use the MU again.

If the original dump works, the JTAG Should work, too Right if done properly. should i do a complete erase of your NAND, write XBR again???