Discussion in 'Xbox 360 Guides' started by InsaneNutter, Dec 31, 2011.
I've quadruple double tripleduple checked it. It's not the key.... any other ideas?
Are you using your original nand dump or the one from your console at the moment?
I did it with original nand dump that the guy who sold me the JTAG gave me. But I'll try recovering the nand like your tutorial says.
Well seems like the nand that came with my jtag is useless, thanks again to your method everything went fine. Now I only gotta learn how to get those new gen games on my hdd.
Its not useless, its always a good idea to keep the orig dump as you never know when you might need it. With the new hacked image builders now your current nand works better and solves a lot of problems as you have found.
thanks nutter, I used this on my old xenon jtag and it worked like a charm!
thank you for the guide
I've updated the jtag and reinstalled dashlaunch (2.32 from 2.29) and updated FSD to 2.2 (from 2.0) but now I have a slight problem some or all of XBLA games give errors such as cant save, cant save profile or cant access HDD. I've tried retails games and they seem to work just fine. Any idea whats up?
I am stumped
EDIT: found out that this is profile related. looks like my main profile got corrupted or maybe new dash does not like that I changed some achievements with Profile_Editor_2.5. Since the same xbla work on a different offline profile. Also maybe cause thats a live profile. playing around with this
EDIT2: restored a backup of profile everything is as should be
Something that has always puzzled me about these tutorials, they never make any mention of the aud_clamp thing, which unless I've been misinformed is important, isn't it? I've been told that if your jtag uses the aud_clamp line instead of the other (don't know what its called) you have to choose that option in the software that builds your new file. I never see this mentioned in the tutorials, and the only guess I can make is that by reading your existing nand the tool already knows this?
Anyway, to give some context, my jtag was done by someone else out of town, and I've meant to update it several times but always put it off due to fear, not fully understanding, etc. I'm here now to finally just do it, if I mess up oh well I mess up . I just wanted to get that aud_clamp question out of the way before I follow this tutorial. Thanks .
EDIT: What is the difference between reading your current nand and using the original nand? I've seen instructions that say you need your original nand (I have it from the person that did my jtag) while guides like this say to read the current nand from the xbox.
Yup the reason i dont mention it is that we are taking the smc and the configuration unique to your console from your existing nand. So you have no need to mess about with stuff like that, if your console works now it should work all been well after you have updated it. In my opinion that is the safest way of upgrading.
Your current nand has your smc and current configuration in, your orig nand is how the console was before it was hacked. So if you have it wired up using the aud-clamp way you would need to apply the changes for this manually.
EDIT: I figured it out, thanks for the help.
Can you explain this in more detail please. What exactly do you mean when you say for aud-clamp I need to apply changes manually? Is it just switch in xeBuild?
BTW, just to see if the steps would work, I went through this tutorial last night, just didn't flash the new nand. Everything went as the guide says it should.
Thanks For a Very detailed Post.
Thanks very much for such a detailed guide. I've just been following this on a JTAG'd Jasper console I've dug out to give to a friend. Unfortunately I've not done anything with it for over a year so I'm a little out of the loop on what to do.
I've completed the guide all the way through but am getting an error in NAND Flasher saying: Error: This image is not compatible with your XBOX 360 model.
NAND Flasher 360 tells me I've got a Falcon (v3.0) which I remember being right, CB: 5770 and a 16MB NAND, I can't remember if this is right or not.
The updflash.bin log file has this in:
SMC checksum: c507f5ba
unknown SMC found, type: Jasper v4.1(2.03)
jtag hack found in smc.bin!
I'm assuming the unknown SMC may have something to do with the problem I'm seeing??
Can anyone offer any help please?
It looks like your trying to build an image for a Jasper when in fact your console is a Falcon, try building an image for a Falcon and see if that helps.
Oh my god I can't believe that's what it was! Thank you very much and sorry for wasting your time. No wonder I couldn't find people having the same problem. Duh!
lol no problem, sometimes its the most simple of things that get over looked! Glad you got it working anyway
Finally found a detailed post on how to update.
But I screwed up. I followed the guide. I got an error when trying to write the nand. something along the lines of "Unable to finish writting" I restarted the xbox and got a e71 error then after that I got a e79 error. I could still boot into xell. Is there anything I can do to fix this without opening the xbox?
Presuming you have Xellious you can put your updflash.bin on a USB stick and boot in to Xell, it should flash your new nand for you.
If you only have Xell you would need to boot in to Linux and try and flash your nand from there.
Thanks insane. But my Xellious won't pick up my usb anymore.
Originally I used rawflash. I inserted xenon.elf along with nandflash (nand that was dumped) into the root of the usb and it rewrote the nand. But now it won't pick up the usb. Is there anything I'm doing wrong?
I also tried loading updlfash.bin but it still doesn't pick it up
Try just having your updflash.bin on the USB stick, try formatting the USB memory stick agaion with the FAT32 file system and see if its picked up.
If not try another stick, ive heard Xellious can be fussy.
Thanks for the quick reply. Tried both nands. Original nand that I backed up before writing the new nand that I built. Sill got the e79 error.
It gets as far as loading the xbox logo then screen scrambles and goes into the error screen. Anything else I can do?
I checked out degrader 1.1 and apparently only had 1 bad block
Separate names with a comma.