How do you do it with an X3? Is it possible? I know you can save it over to the Admin folder on the C drive, but once its there can you restore it to the xbox? Sorry if this is a dumb question...
Changing EEPROM
- Thread starter Naka
- Start date
Bring in the pro's JTAG
EDIT! soldered everything even better im able to write the orig.bin and it comes back identical. going to update this once i get a good write of xbr or xell.
i flashed the orig nand back to the xbox. 360 boots up just fine. it seems anyone having this problem with e79 have something wrong with the jtag connections. im so sure i got a good connection =/ im using the diodes on the pins 3 and 4 and over where the jumper wire goes. well personally i think thats the best jumper wire ive ever done! it looks so nice and neat. im guessing my problem should be simple to fix. is there any other pin connections i can use for the jtag? an alternate pin out schematic would rock! im sure there's one out there so if you can find it let me know.
also im going to try the 3 330 ohm resistors after i flash one more time with xbr.
My only problem is getting a good write and to boot the xbox
I can build the file for xbr but i cant open it in degrade once im done. idk if anyone can. however i only get error 79 and a single red light flashing. i get 3 red rings once i power on with ejecting dvd drive.
Ive gone through different tests and trial and errors. this is the fastest it goes to error 79 with just the kv in the xbr instead of both kv and config.
this all may have something to do with me flashing it while the dvd and rf board (ring of lights) was unplugged. but i wanted to see if it would still work.
xell will not work at all.
My only explanation is im not getting a good write to the nand. ive had my bios on the pc at EPP and at 278mh or something like that last part ill check again and update because im going to up the mh by 100.
it may give a stronger write. it may make things mess up worse. who knows trial and error. once im done i will write a xenon trial and error tut.
I can say is once i wrote the image to the nand xbr and with kv and config injected at the same time once i dumped the box after i checked it in comparison with total commander there are 6 differences. and every time i dump it and compare. there is always 6 differences. whether it be a bad write file that i dumped in comparison with a good xbr kv+config its the same 6 differences. but they are completely different at the same time. some reason im getting 6 errors while writing at the same place however it only writes just a bit each time i assume.
This is just a note here but, after unplugging the power and leaving it off for a few seconds.
(till the amber light on the power brick goes out) and plug it back in i sometimes get no screen or longer waiting times before a single red flashing light and error 79. sometimes 3 red lights. but it depends on what i just wrote to the nand.)
This would be much easier on finding the problem and solving if it didn't take 45 mins each dump and write. the write may take longer im not really timing anymore they both feel like forever.
As for solder points. everything is perfect except for one thing. because i forced myself to check weather the diodes on the jtag hack pin-out were backwards
(they weren't and they were soldered perfect) i accidentally pulled one off.
This wasn't easy as i was trying to remove some heat shrink tubing off the diode because i couldn't see its black line accommodating the accidental yank lol, was me pulling out the copper ring on the surface. there's not much for me to solder to now.. but i have it connected *the diode is basically in the hole now soldered down*
Now it just seems to boot faster into error 79 making me think its not my writing anymore because i chose to write with the xbr file and only the kv injected.
im going to do one more read/dump of the nand to check if the xbr+kv i created on the pc is identical to the one i flashed to the nand.
UPDATE* i re soldered everything! i put each wire in the hole of the connection. soldered them on top and bottom of the MoBo i booted up and it still gave 1 red light error 79
so it wasn't my jtag. its completely the write. it may be the computer im using. but i don't understand why because i could get 10 reads/dumps in a row and they would all be identical. im going to do that read one more time compare then if it is bad again im going to write back the orig.bin and see if it boots. if not. then i know its my pc not able to write correctly.
i have a question though.
if i didn't have the original dump. would it be possible to get the cpu key if i could get xell to load and create a new image. i saw some people talking about it. anyone able tohelp because ive read in many forums of this same problem. mostly with falcon boards a few have my same problem. we all may have something in common however and if i can figure what that is then there is a solution possibly.
my specs for others to read and hopefully get something out of it.
xenon v1 (pre nxe) dashboard
CB Version 1903 LDV 0
CD Version 1888
CF (0) Version 2858 LDV 0
CF (1) Version 4552 LDV 1
PC specs
Windows XP Professional Version 2002 service pack 2
intell (R)
Pentium (R) 4 CPU 2.00 GHz
1.99 GHz 512 MB of ram
it will not flash ny xbox360 dvd drives. Ive only tried Hitachi and Toshiba on it.
both freeze and lock up.
degraded 1.1 shows no bad blocks in nand dumps.
commander compared several dumps and they were all identical in different orders 1 and 2 - 2 and 3 - 3 and 1
Cable is roughly 18 inches in length 5 100 ohm resistors 1/2 watt
if anyone knows if its possible for a write error to occurs when the cable is at this length and 100 ohm 1/2 watt resistors are in place, speak up! maybe removing them would help? or adding 1/4 watt 100 ohm resistors could help.
i flashed the nand with kv and config patched xbr while the r6t3 resistor was off and read/dumped the orig.bin while it was on.
I would like to know if that could cause the dumps and writes to be different. because i don't remember if i dumped the nand once more after removal of the resistor efuse.
tell me some common problems and symptoms of your 360 not working after a flash.
what pc even.
pictures below show a screenshot of the 360 the wiring,
flashtool with the orig.bin file
EDIT! soldered everything even better im able to write the orig.bin and it comes back identical. going to update this once i get a good write of xbr or xell.
i flashed the orig nand back to the xbox. 360 boots up just fine. it seems anyone having this problem with e79 have something wrong with the jtag connections. im so sure i got a good connection =/ im using the diodes on the pins 3 and 4 and over where the jumper wire goes. well personally i think thats the best jumper wire ive ever done! it looks so nice and neat. im guessing my problem should be simple to fix. is there any other pin connections i can use for the jtag? an alternate pin out schematic would rock! im sure there's one out there so if you can find it let me know.
also im going to try the 3 330 ohm resistors after i flash one more time with xbr.
My only problem is getting a good write and to boot the xbox
I can build the file for xbr but i cant open it in degrade once im done. idk if anyone can. however i only get error 79 and a single red light flashing. i get 3 red rings once i power on with ejecting dvd drive.
Ive gone through different tests and trial and errors. this is the fastest it goes to error 79 with just the kv in the xbr instead of both kv and config.
this all may have something to do with me flashing it while the dvd and rf board (ring of lights) was unplugged. but i wanted to see if it would still work.
xell will not work at all.
My only explanation is im not getting a good write to the nand. ive had my bios on the pc at EPP and at 278mh or something like that last part ill check again and update because im going to up the mh by 100.
it may give a stronger write. it may make things mess up worse. who knows trial and error. once im done i will write a xenon trial and error tut.
I can say is once i wrote the image to the nand xbr and with kv and config injected at the same time once i dumped the box after i checked it in comparison with total commander there are 6 differences. and every time i dump it and compare. there is always 6 differences. whether it be a bad write file that i dumped in comparison with a good xbr kv+config its the same 6 differences. but they are completely different at the same time. some reason im getting 6 errors while writing at the same place however it only writes just a bit each time i assume.
This is just a note here but, after unplugging the power and leaving it off for a few seconds.
(till the amber light on the power brick goes out) and plug it back in i sometimes get no screen or longer waiting times before a single red flashing light and error 79. sometimes 3 red lights. but it depends on what i just wrote to the nand.)
This would be much easier on finding the problem and solving if it didn't take 45 mins each dump and write. the write may take longer im not really timing anymore they both feel like forever.
As for solder points. everything is perfect except for one thing. because i forced myself to check weather the diodes on the jtag hack pin-out were backwards
(they weren't and they were soldered perfect) i accidentally pulled one off.
This wasn't easy as i was trying to remove some heat shrink tubing off the diode because i couldn't see its black line accommodating the accidental yank lol, was me pulling out the copper ring on the surface. there's not much for me to solder to now.. but i have it connected *the diode is basically in the hole now soldered down*
Now it just seems to boot faster into error 79 making me think its not my writing anymore because i chose to write with the xbr file and only the kv injected.
im going to do one more read/dump of the nand to check if the xbr+kv i created on the pc is identical to the one i flashed to the nand.
UPDATE* i re soldered everything! i put each wire in the hole of the connection. soldered them on top and bottom of the MoBo i booted up and it still gave 1 red light error 79
so it wasn't my jtag. its completely the write. it may be the computer im using. but i don't understand why because i could get 10 reads/dumps in a row and they would all be identical. im going to do that read one more time compare then if it is bad again im going to write back the orig.bin and see if it boots. if not. then i know its my pc not able to write correctly.
i have a question though.
if i didn't have the original dump. would it be possible to get the cpu key if i could get xell to load and create a new image. i saw some people talking about it. anyone able tohelp because ive read in many forums of this same problem. mostly with falcon boards a few have my same problem. we all may have something in common however and if i can figure what that is then there is a solution possibly.
my specs for others to read and hopefully get something out of it.
xenon v1 (pre nxe) dashboard
CB Version 1903 LDV 0
CD Version 1888
CF (0) Version 2858 LDV 0
CF (1) Version 4552 LDV 1
PC specs
Windows XP Professional Version 2002 service pack 2
intell (R)
Pentium (R) 4 CPU 2.00 GHz
1.99 GHz 512 MB of ram
it will not flash ny xbox360 dvd drives. Ive only tried Hitachi and Toshiba on it.
both freeze and lock up.
degraded 1.1 shows no bad blocks in nand dumps.
commander compared several dumps and they were all identical in different orders 1 and 2 - 2 and 3 - 3 and 1
Cable is roughly 18 inches in length 5 100 ohm resistors 1/2 watt
if anyone knows if its possible for a write error to occurs when the cable is at this length and 100 ohm 1/2 watt resistors are in place, speak up! maybe removing them would help? or adding 1/4 watt 100 ohm resistors could help.
i flashed the nand with kv and config patched xbr while the r6t3 resistor was off and read/dumped the orig.bin while it was on.
I would like to know if that could cause the dumps and writes to be different. because i don't remember if i dumped the nand once more after removal of the resistor efuse.
tell me some common problems and symptoms of your 360 not working after a flash.
what pc even.
pictures below show a screenshot of the 360 the wiring,
flashtool with the orig.bin file
Re: Bring in the pro's JTAG
have you used the diode or resistor method because if you have done the resistor one according to the pics u are a resistor missing
you wont be able to open xbr.bin in degraded
if you extract your raw kv and raw config and put into the xbr.bin then flash the xbr.bin if done correctly it will boot with a nxe dash the way to test if it was successful is plug a wired (or plug n charge controller) into the rear usb port and press the guide button if it starts going through with a bluescreen loading linux (xell) then wait until it finishes and it will show your cpu and dvd key at the end the you can put that into the keys section in 360 flash tool if it loads linux then you have the hacked dash if you have red lights when starting up then something went wrong but as long as u have your original dump you can always flash it back but check them resistors heres a pic of how it should be
have you used the diode or resistor method because if you have done the resistor one according to the pics u are a resistor missing
you wont be able to open xbr.bin in degraded
if you extract your raw kv and raw config and put into the xbr.bin then flash the xbr.bin if done correctly it will boot with a nxe dash the way to test if it was successful is plug a wired (or plug n charge controller) into the rear usb port and press the guide button if it starts going through with a bluescreen loading linux (xell) then wait until it finishes and it will show your cpu and dvd key at the end the you can put that into the keys section in 360 flash tool if it loads linux then you have the hacked dash if you have red lights when starting up then something went wrong but as long as u have your original dump you can always flash it back but check them resistors heres a pic of how it should be
Re: Bring in the pro's JTAG
if you are missing that 1 resistor it wont boot into the dash
where i circled in red is what i am on about on your pic there is only 2 u have to have the three for it to boot these have nothing to do with reading/writing the nand just the booting
oh and take the resistors off the lpt cable they are hardly ever needed and a lot of the time stop it working properly
if you are missing that 1 resistor it wont boot into the dash
where i circled in red is what i am on about on your pic there is only 2 u have to have the three for it to boot these have nothing to do with reading/writing the nand just the booting
oh and take the resistors off the lpt cable they are hardly ever needed and a lot of the time stop it working properly
Re: Bring in the pro's JTAG
thats because im using the diode jtag hack. it only calls for 2 because where the 3rd resistor goes is actually not needed there. you could solder that resistor to the pins 7 and 4 on J2D2 but a resistor isint needed so a simple wire or jumper would work. ive read if im using the diodes to add a resistor to the spot i edited in this pic. and those 2 resistors being diodes.
like this
thats because im using the diode jtag hack. it only calls for 2 because where the 3rd resistor goes is actually not needed there. you could solder that resistor to the pins 7 and 4 on J2D2 but a resistor isint needed so a simple wire or jumper would work. ive read if im using the diodes to add a resistor to the spot i edited in this pic. and those 2 resistors being diodes.
like this
Re: Bring in the pro's JTAG
i think im just gonna do the old way. with the 3 330 ohm resistors. ill try it with the330 ohm on number 4 pin and 7. if that doesn't work. ill try the old fashion way on J1F1 with all 3 330 ohm resistors.
i think im just gonna do the old way. with the 3 330 ohm resistors. ill try it with the330 ohm on number 4 pin and 7. if that doesn't work. ill try the old fashion way on J1F1 with all 3 330 ohm resistors.
Re: Bring in the pro's JTAG
i tried the diode way on 3 xboxes could never get it to work so i went with the old way and worked straight away also a lot of people have problems with the resistors on the db25 plug
think i might do it all over again on another box and take pics along the way for a tutorial
i tried the diode way on 3 xboxes could never get it to work so i went with the old way and worked straight away also a lot of people have problems with the resistors on the db25 plug
think i might do it all over again on another box and take pics along the way for a tutorial
Re: Bring in the pro's JTAG
well i never get read errors and i can write to my nand with the orig.bin so that means my jtag needs to be3wired the 330 ohm way. brb this should take 3 mins to wire up. lol
well i never get read errors and i can write to my nand with the orig.bin so that means my jtag needs to be3wired the 330 ohm way. brb this should take 3 mins to wire up. lol
Re: Bring in the pro's JTAG
ok its all wired up. im dumping reading the nnd of the orig one more time. allthough i have this weird thing happend to me. after i fashed the box back to the orig.bin... everything was fine. iread the nand to see if i could get an identicle read as the first and to all the oher nand dumps i did. i had a read error while doing so and it was error reading block 209 yet.. the dump and the orig was completly the same in total commander. they both were identicle.. maybe nandpro didn't have any error it just thought it did somehow?
-----------------------------------------------------------------------
the error is near the end. anyway here is a log of what i did.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -r16 xbr1.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
Testing LPT device address:0278
Testing LPT device address:03BC
Could not detect a flash controller!
Can not continue << forgot to plug in th cable XD
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -r16 xbr1.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Reading
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe nand3.bin: -r16rawkv1.bin 1 1
NandPro v2.0b by Tiros
Using Virtual Nand Device File: nand3.bin
Starting Block:0x000001
Ending Block:0x0003FF
Reading
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe nand3.bin: -r16 rawkv1.bin 1 1
NandPro v2.0b by Tiros
Using Virtual Nand Device File: nand3.bin
Starting Block:0x000001
Ending Block:0x000001
Reading
0001
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe nand3.bin: -r16 rawconfig1.bin 3de 2
NandPro v2.0b by Tiros
Using Virtual Nand Device File: nand3.bin
Starting Block:0x0003DE
Ending Block:0x0003DF
Reading
03DF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe XBR2.bin: -w16 rawkv.bin 1 1
NandPro v2.0b by Tiros
Using Virtual Nand Device File: XBR2.bin
Starting Block:0x000001
Ending Block:0x000001
Writing
File: rawkv.bin FileLen:4200 Blocks:1
0001
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe XBR2.bin: -w16 rawconfig.bin 3de 2
NandPro v2.0b by Tiros
Using Virtual Nand Device File: XBR2.bin
Starting Block:0x0003DE
Ending Block:0x0003DF
Writing
File: rawconfig.bin FileLen:8400 Blocks:2
03DF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe
NandPro v2.0b by Tiros
Useage:
NandPro dev: -r# Filename (HexStartBlock HexBlockCount) ->Read
NandPro dev: -w# Filename (HexStartBlock HexBlockCount) ->Write
NandPro dev: -e# (HexStartBlock HexBlockCount) ->Erase
dev: is hardware interface usb: or lpt:
dev: can also be a filename:, to be used as a 'Virtual Nand Device'
# is nand size (16, 64, 256, 512) in MegaBytes
(Optional) block ranges, defaults to entire device
-r# Reads saving file RAW (with ECC)
-R# Reads saving file without ECC
-w# Writes RAW (with ECC) file
+W# Write while ADDING ECC from file without ECC
+w# Write while FIXING ECC from RAW (with ECC) file
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 XBR2.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
File: XBR2.bin FileLen:1080000 Blocks:400
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -r16 xbr2.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Reading
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe XBR3.bin: -w16 rawkv.bin 1 1
NandPro v2.0b by Tiros
Using Virtual Nand Device File: XBR3.bin
Starting Block:0x000001
Ending Block:0x000001
Writing
File: rawkv.bin FileLen:4200 Blocks:1
0001
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe
NandPro v2.0b by Tiros
Useage:
NandPro dev: -r# Filename (HexStartBlock HexBlockCount) ->Read
NandPro dev: -w# Filename (HexStartBlock HexBlockCount) ->Write
NandPro dev: -e# (HexStartBlock HexBlockCount) ->Erase
dev: is hardware interface usb: or lpt:
dev: can also be a filename:, to be used as a 'Virtual Nand Device'
# is nand size (16, 64, 256, 512) in MegaBytes
(Optional) block ranges, defaults to entire device
-r# Reads saving file RAW (with ECC)
-R# Reads saving file without ECC
-w# Writes RAW (with ECC) file
+W# Write while ADDING ECC from file without ECC
+w# Write while FIXING ECC from RAW (with ECC) file
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -e16
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Erasing
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 xell.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
File: xell.bin FileLen:14a000 Blocks:50
004F
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -e16
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Erasing
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 XBR3.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
File: XBR3.bin FileLen:1080000 Blocks:400
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -r16 XBRKV.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Reading
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 nand1.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
File: nand1.bin FileLen:1080000 Blocks:400
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -r16 nand4.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Reading
Error: 204 reading block 209 <<< there Is the error yet the dump was identical to the orig.bin file in total commander
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 xell .bin << accidental space
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
Couldn't open xell for read
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 xell.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
File: xell.bin FileLen:14a000 Blocks:50
004F
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 nand1.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
File: nand1.bin FileLen:1080000 Blocks:400
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 nand1.bin
im also done wiring the 330 ohm resistors. my next post WILL BE A SUCCESSFUL FLASH OR ELSE ILL BLOW UP MY PC WITH MY HOME MADE ROCKET LAUNCHER MADE FROM A PAPERCLIP, PIECE OF PAPER AND SOME STRING!!!
ok its all wired up. im dumping reading the nnd of the orig one more time. allthough i have this weird thing happend to me. after i fashed the box back to the orig.bin... everything was fine. iread the nand to see if i could get an identicle read as the first and to all the oher nand dumps i did. i had a read error while doing so and it was error reading block 209 yet.. the dump and the orig was completly the same in total commander. they both were identicle.. maybe nandpro didn't have any error it just thought it did somehow?
-----------------------------------------------------------------------
the error is near the end. anyway here is a log of what i did.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -r16 xbr1.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
Testing LPT device address:0278
Testing LPT device address:03BC
Could not detect a flash controller!
Can not continue << forgot to plug in th cable XD
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -r16 xbr1.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Reading
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe nand3.bin: -r16rawkv1.bin 1 1
NandPro v2.0b by Tiros
Using Virtual Nand Device File: nand3.bin
Starting Block:0x000001
Ending Block:0x0003FF
Reading
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe nand3.bin: -r16 rawkv1.bin 1 1
NandPro v2.0b by Tiros
Using Virtual Nand Device File: nand3.bin
Starting Block:0x000001
Ending Block:0x000001
Reading
0001
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe nand3.bin: -r16 rawconfig1.bin 3de 2
NandPro v2.0b by Tiros
Using Virtual Nand Device File: nand3.bin
Starting Block:0x0003DE
Ending Block:0x0003DF
Reading
03DF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe XBR2.bin: -w16 rawkv.bin 1 1
NandPro v2.0b by Tiros
Using Virtual Nand Device File: XBR2.bin
Starting Block:0x000001
Ending Block:0x000001
Writing
File: rawkv.bin FileLen:4200 Blocks:1
0001
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe XBR2.bin: -w16 rawconfig.bin 3de 2
NandPro v2.0b by Tiros
Using Virtual Nand Device File: XBR2.bin
Starting Block:0x0003DE
Ending Block:0x0003DF
Writing
File: rawconfig.bin FileLen:8400 Blocks:2
03DF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe
NandPro v2.0b by Tiros
Useage:
NandPro dev: -r# Filename (HexStartBlock HexBlockCount) ->Read
NandPro dev: -w# Filename (HexStartBlock HexBlockCount) ->Write
NandPro dev: -e# (HexStartBlock HexBlockCount) ->Erase
dev: is hardware interface usb: or lpt:
dev: can also be a filename:, to be used as a 'Virtual Nand Device'
# is nand size (16, 64, 256, 512) in MegaBytes
(Optional) block ranges, defaults to entire device
-r# Reads saving file RAW (with ECC)
-R# Reads saving file without ECC
-w# Writes RAW (with ECC) file
+W# Write while ADDING ECC from file without ECC
+w# Write while FIXING ECC from RAW (with ECC) file
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 XBR2.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
File: XBR2.bin FileLen:1080000 Blocks:400
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -r16 xbr2.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Reading
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe XBR3.bin: -w16 rawkv.bin 1 1
NandPro v2.0b by Tiros
Using Virtual Nand Device File: XBR3.bin
Starting Block:0x000001
Ending Block:0x000001
Writing
File: rawkv.bin FileLen:4200 Blocks:1
0001
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe
NandPro v2.0b by Tiros
Useage:
NandPro dev: -r# Filename (HexStartBlock HexBlockCount) ->Read
NandPro dev: -w# Filename (HexStartBlock HexBlockCount) ->Write
NandPro dev: -e# (HexStartBlock HexBlockCount) ->Erase
dev: is hardware interface usb: or lpt:
dev: can also be a filename:, to be used as a 'Virtual Nand Device'
# is nand size (16, 64, 256, 512) in MegaBytes
(Optional) block ranges, defaults to entire device
-r# Reads saving file RAW (with ECC)
-R# Reads saving file without ECC
-w# Writes RAW (with ECC) file
+W# Write while ADDING ECC from file without ECC
+w# Write while FIXING ECC from RAW (with ECC) file
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -e16
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Erasing
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 xell.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
File: xell.bin FileLen:14a000 Blocks:50
004F
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -e16
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Erasing
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 XBR3.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
File: XBR3.bin FileLen:1080000 Blocks:400
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -r16 XBRKV.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Reading
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 nand1.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
File: nand1.bin FileLen:1080000 Blocks:400
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -r16 nand4.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Reading
Error: 204 reading block 209 <<< there Is the error yet the dump was identical to the orig.bin file in total commander
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 xell .bin << accidental space
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
Couldn't open xell for read
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 xell.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
File: xell.bin FileLen:14a000 Blocks:50
004F
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 nand1.bin
NandPro v2.0b by Tiros
Testing LPT device address:0378
FlashConfig:01198010
Using LPT device at address:0378
Starting Block:0x000000
Ending Block:0x0003FF
Writing
File: nand1.bin FileLen:1080000 Blocks:400
03FF
C:\Documents and Settings\Kyle>C:\Nandpro20b\nandpro.exe lpt: -w16 nand1.bin
im also done wiring the 330 ohm resistors. my next post WILL BE A SUCCESSFUL FLASH OR ELSE ILL BLOW UP MY PC WITH MY HOME MADE ROCKET LAUNCHER MADE FROM A PAPERCLIP, PIECE OF PAPER AND SOME STRING!!!
Re: Bring in the pro's JTAG
just a question about above what are you flashing in the pic below if its xell and not xbreboot then thats whats going wrong
you need the file XBR_Xenon_8955_3 from xbins
xell has to be compiled
just a question about above what are you flashing in the pic below if its xell and not xbreboot then thats whats going wrong
you need the file XBR_Xenon_8955_3 from xbins
xell has to be compiled
Re: Bring in the pro's JTAG
err. maybe thats why xell will not work. but xbr works. the 330ohm resistors worked fine. i would have gotten it to work with the diods but the only problem was i had a couple pins mixed up and did not notice it.
im working on dev files right now. i think ive found a way to create your own gamerpics. and use them! like edit them in photoshop then just add to the HDD. i already created 1. its not signed to any account but when i go to click on it and to change my picture on the xbox it wont select it. i believe thats not a problem because it does the same with gamerpics from gamerpic injector.
im just about to try and use an account id with it to sign it to the account. should work.
err. maybe thats why xell will not work. but xbr works. the 330ohm resistors worked fine. i would have gotten it to work with the diods but the only problem was i had a couple pins mixed up and did not notice it.
im working on dev files right now. i think ive found a way to create your own gamerpics. and use them! like edit them in photoshop then just add to the HDD. i already created 1. its not signed to any account but when i go to click on it and to change my picture on the xbox it wont select it. i believe thats not a problem because it does the same with gamerpics from gamerpic injector.
im just about to try and use an account id with it to sign it to the account. should work.
Re: Bring in the pro's JTAG
i had the 2 diode method on my system and i did a prestine job at soldering all the wires and no boot. i switched to the 3 330ohm method(but i used 270ohm radio shack was out of 330ohm) and it booted right up no problems. it went from e79 to working fine with just 3 resistors and some time.
i had the 2 diode method on my system and i did a prestine job at soldering all the wires and no boot. i switched to the 3 330ohm method(but i used 270ohm radio shack was out of 330ohm) and it booted right up no problems. it went from e79 to working fine with just 3 resistors and some time.
Re: Bring in the pro's JTAG
id really like to know why the hell someone decided to think that the diodes were better than the resistors.. it seems they dont work for everyone. while the resistors are 100% SURE.
i could have saved so much time really with my jtag.. the next one ill do with resistors.
theone420 said:
id really like to know why the hell someone decided to think that the diodes were better than the resistors.. it seems they dont work for everyone. while the resistors are 100% SURE.
i could have saved so much time really with my jtag.. the next one ill do with resistors.
Re: Bring in the pro's JTAG
i am in the process of doing a few tutorials for absolute noobs for various jtag and homebrew stuff and will probably post them here and my own site
i am in the process of doing a few tutorials for absolute noobs for various jtag and homebrew stuff and will probably post them here and my own site
Re: Bring in the pro's JTAG
No TMbinc etc,now they are the pros,we are just handy with an iron and FOLLOWING INSTRUCTIONS!K3thunder said: