Bad Glitch image flash :(

[MOCAMBO]

So I used nand healear 0.72 and everything was smooth with booting xell and what not, but when I went to flash the glitch image, I was getting massive amount of error 202 when flashing the blocks.

Now I'm trying to erase by flash, but now I get the usb interface device not found error

What do I do?

I have my original nands, 4 all good no bad blocks or anything.

 

[dirtyscout]

what mobo is it and are you trying to flash the ecc or the ggbuild ? if your trying the ggbuild use rawflash from xell

 

[MOCAMBO]

I'm doing it on a trinity mobo on the new 14699 dash.

What do you mean use rawflash from xell? What do I exactly do? I keep getting the usb interface not found message when I try to do anything with nandpro or nandhealer.

 

[dirtyscout]

try building your image with multi build found here. http://team-xecuter.com/forums/showthread.php?t=74059

rawflash will let you install a nand image from xell google rawflash v4 i think it is.. so once you find rawflash put the file and your hacked nand image on a usb and push eject to boot

edit... heres link to rawflash http://libxenon.org/index.php?topic=212.0

 

[MOCAMBO]

No I dont think you understand.

Nandpro cannot find the usb interface when I have my nand x connected to my trinity mobo AND I cannot boot into xell anymore either.

The greenlight on the CR does not flash green anymore either.

 

[dirtyscout]

post pics of your install sounds like a wiring issue.

 

[MOCAMBO]

post pics of your install sounds like a wiring issue.

Ok I'll post some pics but, if it was a wiring issue, wouldn't I have had problems booting into xell?

 

[WestCoastConsoles]

If you can boot to xell take your image and throw it on a usb stick under the name nandflash.bin also throw in xenon.elf this is your rawflash file. it will then write the image to the console through xell.

Check your nand soldering touch every point up they can break and cause this issue.

 

[MOCAMBO]

If you can boot to xell take your image and throw it on a usb stick under the name nandflash.bin also throw in xenon.elf this is your rawflash file. it will then write the image to the console through xell.

Check your nand soldering touch every point up they can break and cause this issue.

No.....

I COULD boot into XELL BEFORE I flashed the Glitch image.

AFTER I flashed the Glitch Image

I can't boot into Xell nor can I read the nand anymore as it gives me the looking for usb interface error.

 

[MOCAMBO]

Ok so I went through the bad recover flash slim thread and checked to see if 3.3v is going through my R1D5 pad. Is it worth doing the 5v mod so I can write the nand again?

 

[comcraft]

I created guide for this yesterday as i had some consoles with this issue.

Its in Slovak tho, so hoping google translate can make it understandable:

90% its soldering, but the 10% is corruptly flashed NAND. And NandHealer isnt supporting latest Multibuilder, thats probably why you got corrupt image flash on first place. If soldering is fine, thats your issue

http://translate.google.sk/translat...boxzone.sk/viewtopic.php?f=61&t=26416&act=url

Regards,

L.

 

[tingedace]

Hi, I'm sure this is a wiring issue as it happened to me although was on a phat.
I took all the wires off and started again from scratch and then everything was fine.

Xnandhealer 0.72 does support the latest multibuilder 0.7 (14699 dash) and should build an identical image to that of multibuilder.

 

[ishockin]

You might have to supply power to the NAND since you flashed such a bad image

 

[MOCAMBO]

Ok here are the pics, if I was to re-do all the wiring, would it solve my issue? Or would I have to supply power to the nand regardless?

 

[MOCAMBO]

Would adding 5v as shown in the image below help me write/read the nand again?

 

[Martin C]

Between booting XeLL and going to rewrite the new image, did you move the console at all?

 

[MOCAMBO]

Between booting XeLL and going to rewrite the new image, did you move the console at all?

After booting Xell and rewriting the new image, I didn't more the console at all. Maybe a slight nudge while I was connecting the NAND-x cables, but nothing else. I didn't pick it up or anything like that.

Edit:

This is a breakdown of how the image flashing process went exactly.

**Both 360 and Nand-x had power the whole time

1. Clicks write glitch image bin to 360
2. Asks me to verify which interface I'm using
3. Check usb, turns out I had mixed up my blue and green wires to nand -x so it gave me an error first
4. Swap the wires, recognizes perfectly.
5. Clicks write glitch image bin and starts writing, and basically for EVERY single block until 03xx onwards, it was giving me a bad flash error 202, like every single line/block.
6. Xell does not boot anymore, I can't read the nand or anything, CR greenlight does not flash anymore either.

 

[Martin C]

are you 100% sure you have ALL connections plugged in the right way on ALL parts of the kit (taking into account you already managed to plug them in the wrong way once already) ?

 

[Beejeex]

I know this is my first post. i read alot. I had that one time. bad flash thing. i removed the power from the box for about 5-10 mins and tried to reflash. Then the flash worked for me. I also disconnect the nandx from the pc not from the box.

Bee.

 

[frazzeld]

Have you got a short between points B and E