Print

[bubbles2578]

This is my first post so Hi to everybody.

This might be a silly question but here goes.
Ive done 7 NAND Dumps and managed to get the 5th and 7th to be identical.

I basically just want confirming if I need to get 2 consecutive dumps identical or can I accept the 5th and 7th dumps?

Cheers

[cabb360]

2 or 3 identical dumps don't matter what order u dump as long as they match.  I sugest backing a few more up u Neva know lol

This post has been edited by cabb360: Apr 22 2010, 11:56 AM

[thwack]

If it's a 16mb NAND - check them in Degraded before flashing anything back to the NAND - see if there's bad blocks that aren't reallocated, as if you do not do this, you risk giving yourself a major headache.....

[bubbles2578]

Ive managed to get 4 nand dumps all identical. All 4 have the same 3 bad blocks (error 250). I ran these through degraded and they initially wouldnt work but then i changed the date using a hex editor and degraded now reads them. the Cb is exploitable. But it comes up with the 3 bad blocks that it saw during the dump. It also says that these bad blocks were found at another location (the end of the file 0x3fd, 0x3fe and 0x3ff).

Ive read on 1 tut that these are ok and I dont need to do anything to them, but on another it says that I need to relocate them. Any ideas whats the best thing to do?

While I was debating whether or no to relocate the bad blocks I decided to put xell onto the nand so that I could get the CPU key. (I did this because from what I have read on the tuts that you dont use the dumped nand with xell you only write it over the top, (first 50 blocks 00-4f))(The bad blocks seen in degraded were above 0x145, so shouldnt affect it). BUT, ive got the dreaded e79 error. Everywhere I read it says that the main cause of this is that the jtag points arent done correctly. Ive double and tripple checked these and they are fine. I didnt use a link between pins 4 & 7, I used a 100ohm resitor. Would it be worth me trying to connect a 330ohm or even a 470ohm resistor in place of this 100ohm as I have heard this can help?

another question I have is, do I need to inject the Kv into xell? I havent read anywhere that you do, im just curious.

cheers

This post has been edited by bubbles2578: Apr 23 2010, 09:40 AM

[bubbles2578]

Sorry for the double post, couldnt seem to edit the original.

The bad blocks in my original nand were 145, 14B and 1F7.
These were shown in nandpro when reading the nand and in degraded.
Any ideas?

Cheers

[thwack]

The blocks are fine - they are physical bad blocks on the NAND - I'd recommend using Xellous rather than Xell, as Xellous can remap for you when installing XBR - as for FreeBoot, you'll need to remap those blocks manually.

As a simple test, install Xellous into XBR, and flash the lot over tho your NAND - that way, at least you'll have a starting point to tell if your wiring is a bit off.

Either way, those blocks will still need reallocation.

[bubbles2578]

Ive decide im going to insert xellous into xbr like you said.

Here is the picture of my degraded.

(IMG:http://img690.imageshack.us/img690/7420/degradedb.jpg)


I think I know how to install xellous into xbr
but how do I go about reallocation of the blocks so that I can write xbr?

cheers

[cabb360]

https://docs.google....O...zMjY4&hl=en

use this method to flashing best way it will deal with bad blocks while flashing. Just get xellous installed and u good to go

[bubbles2578]

Thanks for the reply and the info, but the link that you posted is for installing using Linux and I am using windows.

[cabb360]

First of all l2read that tut is for running nix on the 360 and u use putty to remote and flash extract NAND Putty is a windows progam that allows to to ssh to 360 after u get debian running on the 360.

Dl all the things u need from the usaul places
install xellous
burn debian to DVD boot up 360 with eject or wired controller into xell pop in DVD while blue screen then let the magic begin.

[bubbles2578]

Ive put XBR onto the NAND and i still get the same problem. E79 error. Ive checked all my connections with jtag, and tried again, no difference. I removed the jtag and re-installed it. Same problem. So I put my original nand back on. Powered up and my original dashboard worked.

Then I realised that I hadnt removed the jtag. I thought the original dashboard wouldnt work if the jtag was in place. If this is true then there is definetley something wrong with the jtag connections. But ive double and tripple checked these, using a multimeter checking with various alternatives on the mobo and they are all connected fine.

Im using IN4148 Diodes. Would it be better to use the BAT41 Doides because Ive read in some places that these have a better success rate?

Cheers

[cabb360]

Jtag wires always stay. Can't boot xbr without em did u remove jtags wires after flashing if so that's ur e79 error

[bubbles2578]

when i installed xbr the jtag wires were still attached. but because it didnt work i put my original nand dump onto the 360. The original nand dump worked fine and the original dashboard loaded up. I then realised that the jtag wires were still attached, which confused me, because I thought that the original dashboard wouldnot work with the jtag wires still attached.

Could someone confirm this for me?

With the jtag wires im using the IN4148 diodes, is it better to use the BAT41 Diodes because ive heard these can be more successful?

Cheers

[bubbles2578]

Ive now managed to get xell working. The solder points on my jtag were fine but the wire connecting the diode to one of the jtag points was dry jointed.

I then injected xellous into xell and mangaed to connect to the 360 using a network cable. I then placed the xbr.bin for my motherboard on a flashdrive and it updated the nand automatically. but when i rebooted the 360 the dashboard started to load and then i got an E71 error.

So im just working on reflashing the nand again to see what happens.

ill let you all know if and when it works

cheers

[bubbles2578]

Right Then.
First of all sorry for the tripple post but i didnt have the option to edit for some reason.

Secondly

I reflashed XBR onto the 360 using xellous and I decide to watch it do it this time. I have read that when you use xellous to write XBR it remaps all the bad blocks for you. But when I was watching xellous write xbr I noticed that when it came to the bad blocks (I have 3 in all), it wrote all 3 bad blocks to the same alternate location. So after it had finished writing I tested it, and I got E71 again.

So I decided to remap XBR myself using nandpro, then I injected the KV into the xbr and used nandpro to write it. Worked first time.

Thanks to everyone who helped on this forum and to the authors of the numerous tutorials I used.

Ive now got a Jtaged 360.

I dont think I did anything wrong while writng XBR through xellous. I renamed it to the correct filename. put in the root of my mem stick and booted the 360 into xellous and it saw the mem stick and started to write the file.
Anybody have any ideas as to why this didn't work for me. The only reason Im asking is if there is an update to XBR I want to be able to use xellous to update it insted of having to go through the whole process of connecting it up to my lpt port.

Just one more question what is the best direction to go in now?

cheers