xboxscene.org forums

Author Topic: Error- Could Not Open Virtual Nand Device File  (Read 31 times)

SHADOWSTRIKE1

  • Archived User
  • Newbie
  • *
  • Posts: 36
Error- Could Not Open Virtual Nand Device File
« on: September 02, 2010, 07:40:00 PM »

Hey guys.  Jtagging this Xbox has been a wild ride.  I've run into problems at every single possible step.  Allow me to fill you in-

I finally got my Jtag up and running, and it was going fine for a couple days, but then magically I got the E79 error.  I have done absolutely everything to fix it.  I have resoldered my entire JTag wiring about 5 times.  I've tried many different switching diodes.  I tried putting a 330 ohm resistor on my jumper wire.  I've reflashed tons of times.  I've cleaned out my entire fan.  I've ran it without any HDD or USB plugged in.  I've tried holding in the sync button and turning it on.  I've tried holding in the disk tray and turning it on via eject button.  Still E79.  Finally, after reflashing to original NAND, and then reflashing that to my FreeBoot image, I got it kinda working.  By kinda, I mean Xell would boot up fine, but if I ever turned the system on via the power button, all I would get was a black screen.  Even weirder, when I turned off the system, my wired controller would still have the 4 lights on.  After tinkering for a bit, I got it to boot finally.  So I turned it off, and turned it back on.  Guess what?  E79.  

So I reflashed back to original NAND, and I've been trying to follow this guide-
Noob Friendly Jtag Tutorial

I figured from there I could update to FreeBoot via USB.  The only problem was, is that I get to the step where I have to use CMD to write my KV1.bin to my free60.bin, and I get the following message-

"Could not open Virtual Nand Device File: free60.bin
Can not continue"

I've tried to do this on 3 different computers, and I've tried using both nandpro20b and nandpro20e.  Same thing.  I am using the Xenon free60 .bin.  Something I did notice is that the free60.bin file is only 1,320 kb, but the included readme file said that that was ok.

Please, any help would be greatly apperciated.  I've seriously tried everything to fix this.  I purchased a translucent black "Ghost Case" to put my 360 in once it's finished... but it's just sitting there mocking me as I cannot finish this system (IMG:style_emoticons/default/sad.gif).  If nothing else, could I trust someone and send them my kv1.bin and my free60.bin files and have them write them for me?  I dont know about the risk of this.  I'm not sure how special your kv is, but whatever.  Again, I am using a Xenon mobo.  

P.S.-  Do I have to have all the screws in when I test my system?  Like, I have the top of the case off so I can tinker with it, but I was just hoping that none of the screws ground out the mobo or something.  I can take pics if you guys would like.
Logged

dennisv9

  • Archived User
  • Full Member
  • *
  • Posts: 102
Error- Could Not Open Virtual Nand Device File
« Reply #1 on: September 03, 2010, 03:14:00 PM »

"Could not open Virtual Nand Device File: free60.bin Can not continue" ==> use nandpro20B (yes, BBBBBBB). that one works; i had the same problem. used my old nandpro20b version; and worked like a charm.

another way to go about is to first flash free60.bin with the supplied command (' nandpro lpt: -w16 free60.bin 0 '); after which you flash your keyvault directly into your nand (nandpro lpt: -w16 kv1.bin 1 1).

the result is the same, it doesn´t matter if you inject your keyvault into the free60.bin and then write it into you nand. or you write them individually to your nand. off course write your kv.bin as last!!!!

kv.bin is useless to others without your cpu key to decrypt the information, at least as far as i know.

you don´t need to put any screws in to test, just mainboard and some cooling. that is how i do it. it is completely out of the case. only a motherboard and some fans on the cpu and gpu.
Logged