hahaha .....you`re funny ...whos fault is it you didnt compare nands ? Its definitely not TX`s is it . (i dont work from them BTW i`m just a user of their excellent products ) Because you didnt do that you cannot definitively say that it`s defective and neither can TX . Had you compared nands and found it to be faulty before soldering you would have got a replacement without issue, because you didnt you soldered it in and thats your fault !
I think I have a problem
- Thread starter Techrev
- Start date
Ok, so what? It seems I made the same mistake their quality assurance team made. Hindsight is always 20/20. Yes, comparing the nands - in hindsight - would have saved me a lot of time and effort. However, this doesn't change the fact that they sent me a defective product in the first place. For something like this, a warranty like that is nearly useless. Their pre test instructions, if I remember right, didn't even recommend comparing nands. Usually, a write and read test will be enough to know that it's functional. It's not hard to tell, from the symptoms of the problem I have, that the problem isn't with a soldering mistake, and it was shipped out like that. The testing I did proves it. I'm sorry, but please stick to your own business, and unless you have information that can actually help my situation, keep off my thread.
---------- Post added at 17:40 ---------- Previous post was at 17:35 ----------
And, for your information, I have purchased a lot of their other products and not had an issue with them. They have all been great, and functioned as they should - if not better. This is the first time I've had a problem with anything they have sent me, and part of the reason I'm a little upset right now. Yes, they make great products, but in the event that there does happen to be a problem with one, it seems that you are left out in the cold. I'm glad that it hasn't seemed to have happened to you yet? But, maybe if it did, you wouldn't be so quick to open your mouth where it's not appreciated.
---------- Post added at 17:46 ---------- Previous post was at 17:40 ----------
Hell, the Jasper I tried to put that Demon in is currently back together and RGH2 glitching an average of less than 30 seconds (I haven't bothered to try to get it faster - I'm lazy), on a Coolrunner Rev. A that I got the minute they became available.
---------- Post added at 17:40 ---------- Previous post was at 17:35 ----------
And, for your information, I have purchased a lot of their other products and not had an issue with them. They have all been great, and functioned as they should - if not better. This is the first time I've had a problem with anything they have sent me, and part of the reason I'm a little upset right now. Yes, they make great products, but in the event that there does happen to be a problem with one, it seems that you are left out in the cold. I'm glad that it hasn't seemed to have happened to you yet? But, maybe if it did, you wouldn't be so quick to open your mouth where it's not appreciated.
---------- Post added at 17:46 ---------- Previous post was at 17:40 ----------
Hell, the Jasper I tried to put that Demon in is currently back together and RGH2 glitching an average of less than 30 seconds (I haven't bothered to try to get it faster - I'm lazy), on a Coolrunner Rev. A that I got the minute they became available.
Dicko316
VIP Member
Take some good clear hi res pics of the demon, make sure all contacts are cleaned up with solder wick first.
Then write a known good nand.bin to the demon again, then read it back, compare both nands, and post logs of the compare and the Writes and reads of the demon nand.
It is possible the demon nand has bad blocks, you mentioned in a previous post about a point where you had 2 bad blocks, this could of been NORMAL. Bad blocks can happen.
Then write a known good nand.bin to the demon again, then read it back, compare both nands, and post logs of the compare and the Writes and reads of the demon nand.
It is possible the demon nand has bad blocks, you mentioned in a previous post about a point where you had 2 bad blocks, this could of been NORMAL. Bad blocks can happen.
No, I get the same behavior when it wrote to the demon as when it wrote to the 360 nand. Random bad blocks. Using the ext usb or the micro usb (Never with the xbox power on, and only writing to the demon, but the behavior was the same). It really does look like it's the usb controller. I will clean it up though (It's pretty clean atm), and try again. The instructions only tell us to do a read and a write, I used the demon toolbox to do that. J-Runner is the tool that automatically did the compare. Also, the instructions say that damaging the Demon by improper soldering will lose warranty, not soldering itself. TX can try to say that I damaged it by soldering it in order to try and get out of replacing it under warranty, but the behavior it's displaying isn't due to bad soldering. Also, they weren't bad blocks, they were compare mismatches between two reads. The number of mismatches were random. I will clean the board up totally, and make sure it's totally clean, and try again though. Can't hurt. I have emailed the company that I purchased it from and am trying to go about it that way, but it's the weekend, so I will not hear from them until tomorrow.
---------- Post added at 18:00 ---------- Previous post was at 17:59 ----------
I'm sorry, I said random bad blocks again, but in every case, they are not bad blocks but bad read compares.
---------- Post added at 18:01 ---------- Previous post was at 18:00 ----------
It's when I tell it to read the nand 2 times, then compare both dumps to see if they are the same.
---------- Post added at 18:02 ---------- Previous post was at 18:01 ----------
Also, the number of bad compares varied, and the blocks also varied, from read to read.
---------- Post added at 18:00 ---------- Previous post was at 17:59 ----------
I'm sorry, I said random bad blocks again, but in every case, they are not bad blocks but bad read compares.
---------- Post added at 18:01 ---------- Previous post was at 18:00 ----------
It's when I tell it to read the nand 2 times, then compare both dumps to see if they are the same.
---------- Post added at 18:02 ---------- Previous post was at 18:01 ----------
Also, the number of bad compares varied, and the blocks also varied, from read to read.
Like d**ko said take some Hi Res pics as the ones you posted are poor quality making your soldering look very poor hence why we think it's a wiring problem
These products are tested for thousands of hours not just mass produced and untested. Chances are you are at fault not the product
These products are tested for thousands of hours not just mass produced and untested. Chances are you are at fault not the product
Last edited:
Also, I know that the write wasn't functioning properly because flashing the rom to the xbox cause the xbox to not be able to power up at all. I would push the button, and it would just stay black. After I reflashed the xbox using the nand-x and the other connector I installed for it, the xbox was able to power on and boot again. So, it's not a situation where the write is working correctly, but the reads are faulty. It seems to be a problem in the usb controller on the demon. I don't know. I will do what you asked though.
---------- Post added at 18:06 ---------- Previous post was at 18:05 ----------
Yeah, I was having a hell of a time with the camera and getting it to take good photos :/, you can't see jack. All the connections I tested with a multi meter as well. I will try to get better ones.
---------- Post added at 18:12 ---------- Previous post was at 18:06 ----------
I have to do all my work under magnifying glasses, you know? I'll try to do better with the camera. Later tonight.
---------- Post added at 18:06 ---------- Previous post was at 18:05 ----------
Yeah, I was having a hell of a time with the camera and getting it to take good photos :/, you can't see jack. All the connections I tested with a multi meter as well. I will try to get better ones.
---------- Post added at 18:12 ---------- Previous post was at 18:06 ----------
I have to do all my work under magnifying glasses, you know? I'll try to do better with the camera. Later tonight.
Dicko316
VIP Member
Thats not what you said here mate.
2 bad blocks is possible on the demon nand.
I/we cannot help you get this sorted, if you give inconsistant feedback.
I'n not trying to cause an argument here, just stating a fact.
I, honestly, don't have a problem if I am at fault. Just, I don't think I am. I will clean it up, test it again. If I had seen a solder bridge in my testing, failed any continuity test, etc, I wouldn't be pitching a fit :/. I'm the first one to say, hey, I spilled a little solder onto a solder pad on my first qsb point :/. Just, it was the solder pad attached to the point, and shouldn't have had any effect on anything. Nothing bridged. Reads and Writes worked fine, looked great, appeared successful. Until I compared 2 reads.
---------- Post added at 18:20 ---------- Previous post was at 18:17 ----------
@d**ko Yes, I was excited and wrote that incorrectly. My second test, immediately following that came back with around 15 comparison errors. Also, I said bad blocks, when I meant bad compares. If it was bad blocks, I know, that is easy to accommodate
. If they were consistant, and in the same place, it could also be worked with. So, I am sorry for my incorrect terminology. But, if you read all my posts, you can see that my description of the problem is the same. Random numbers of bad compares on 2 consecutive reads. Whether it's the xbox nand, the demon nand, or the demon nand through the micro usb port.
---------- Post added at 18:22 ---------- Previous post was at 18:20 ----------
Also note, that I did not get a single read or write fail. The only failures I got were when I tried to compare 2 successful reads. I'm sure the writes were bad too, for the reasons mentioned before.
---------- Post added at 18:20 ---------- Previous post was at 18:17 ----------
@d**ko Yes, I was excited and wrote that incorrectly. My second test, immediately following that came back with around 15 comparison errors. Also, I said bad blocks, when I meant bad compares. If it was bad blocks, I know, that is easy to accommodate
. If they were consistant, and in the same place, it could also be worked with. So, I am sorry for my incorrect terminology. But, if you read all my posts, you can see that my description of the problem is the same. Random numbers of bad compares on 2 consecutive reads. Whether it's the xbox nand, the demon nand, or the demon nand through the micro usb port.---------- Post added at 18:22 ---------- Previous post was at 18:20 ----------
Also note, that I did not get a single read or write fail. The only failures I got were when I tried to compare 2 successful reads. I'm sure the writes were bad too, for the reasons mentioned before.
Some things came up, and I haven't been able to get the time to take photos, I will do it tomorrow.
no surprise there then
There is definitely a bridge there . I know because i did the same thing to mine . They are a bitch to get unbridges . Use lots of flux and some goot wick and go super carefully to get all the solder off . It effects the demon nand because they are both connected to the same place on the mobo so if one is shorted they both will be . basically the demon solders one nand on top of the other and allows you to switch between the two. just go easy and you`ll get there
Last edited:
No, no bridges, and they weren't bad blocks, but bad read compares (I wrote that wrong). I did not get one bad block, and every read and write was successful. Just when I compared the dumps from 2 reads was there a problem. The next test I got 15 or 20 again, it was just a random weirdness that I only got 2 that time. I took the board out, same thing, continuity tested all the connections, and no bridges.
But, all of that is written in this thread. The next thing I have to do is clean it up as much as possible, test it again, and take pictures. If it clears up, I'll be happy as heck, but since all the continuity checks show there are no bridges I would be very surprised. I just need to get the time to do it, I have a lot going on right now. Hopefully I can today :/.
---------- Post added at 12:51 ---------- Previous post was at 12:48 ----------
People keep picking on that one statement, sigh. I shouldn't have posted it, I was just excited because I thought I saw an improvement, but it wasn't. Please, bad compares on 2 SUCCESSFUL reads is a totally different thing. They were not bad blocks.
---------- Post added at 12:55 ---------- Previous post was at 12:51 ----------
The symptoms are this: Any read or write is always successful. No matter how I do it. XBox, Demon, ext usb or micro usb. Always. And, always, when I do 2 consecutive reads, there are a random number of random compared blocks that fail the comparison. They do not report the same result. This has been the behavior from the beginning. It didn't change. Just, at one point in my troubleshooting, it seemed to improve - but it really didn't. It was just a random occurrence that that time I happened to get 2, other times it was 6 or 20 or 15 or whatever. A random number. I just got excited because I thought it was an improvement. It was not.
---------- Post added at 12:58 ---------- Previous post was at 12:55 ----------
When I clean the board up completely, again, I will make 100% sure - again - that there are no bridges. My hope is that I'm wrong, always, I want this part to work... However, I don't think so.
But, all of that is written in this thread. The next thing I have to do is clean it up as much as possible, test it again, and take pictures. If it clears up, I'll be happy as heck, but since all the continuity checks show there are no bridges I would be very surprised. I just need to get the time to do it, I have a lot going on right now. Hopefully I can today :/.
---------- Post added at 12:51 ---------- Previous post was at 12:48 ----------
People keep picking on that one statement, sigh. I shouldn't have posted it, I was just excited because I thought I saw an improvement, but it wasn't. Please, bad compares on 2 SUCCESSFUL reads is a totally different thing. They were not bad blocks.
---------- Post added at 12:55 ---------- Previous post was at 12:51 ----------
The symptoms are this: Any read or write is always successful. No matter how I do it. XBox, Demon, ext usb or micro usb. Always. And, always, when I do 2 consecutive reads, there are a random number of random compared blocks that fail the comparison. They do not report the same result. This has been the behavior from the beginning. It didn't change. Just, at one point in my troubleshooting, it seemed to improve - but it really didn't. It was just a random occurrence that that time I happened to get 2, other times it was 6 or 20 or 15 or whatever. A random number. I just got excited because I thought it was an improvement. It was not.
---------- Post added at 12:58 ---------- Previous post was at 12:55 ----------
When I clean the board up completely, again, I will make 100% sure - again - that there are no bridges. My hope is that I'm wrong, always, I want this part to work... However, I don't think so.