Really? I thought it was caused by too-long wires...
http://gbatemp.net/threads/nand-flash-dump-3ds-xl.350668/page-7
Post #126
There is one, i didn't have patience to find the other trough
Really? I thought it was caused by too-long wires...
http://gbatemp.net/threads/nand-flash-dump-3ds-xl.350668/page-7
Post #126
There is one, i didn't have patience to find the other trough
http://gbatemp.net/threads/nand-flash-dump-3ds-xl.350668/page-7
Post #126
There is one, i didn't have patience to find the other trough
yeah i thought that guy just got unlucky with soldering or something? who knows, but we can't say for certain that writing to the flash too much bricks your 3ds. (unless their is enough evidence)Seems as though he just read the NAND? After reading it he attempted to boot into the 3DS' Menu and it wouldn't boot up.
yeah i thought that guy just got unlucky with soldering or something? who knows, but we can't say for certain that writing to the flash too much bricks your 3ds. (unless their is enough evidence)
vini9157, can you find the other one? when you have the patience i tried to see but i couldn't find it, maybe i missed it
don't worrysy but its 14 pages
yeah like, i was under the impression accessing nand is what you are limited to do if something/most things are bricked. like ps3, you need to use a flasher. kindle, you need to use a flasher, i guess it is the same for many things, you just need to have access to the nand, and as long as you do that you are fine.likely just a solder fuck up. people really shouldn't open their electronics and solder shit if they don't have the skills.
not that this is a hard solder job... especially on a 3DS XL. i did it half asleep at 2 am at night almost in the dark...
that rewriting the nand would damage it is of course ridiculous, it is rewritten by the 3DS itself continuously throughout using it!
the toshiba nand is likely rated for usage in the order of millions of rewrite cycles...
why is it that windows always wants to format my 3dsxl as it does not recognize its format? its just that no one else seems to come across this, ive atempted this over a couple of weeks now and still no luck, ive even change sd card readers and went out and brought more appropriate wire and redid and rechecked.... one thing i have noticed is under windows disk management it does say drive H unknown 950MBs...
I was thinking of wiring a micro USB port into one of the corners currently used for a strap. Then using some epoxy to hold it in place.
Then I would use a micro USB sync cable to connect it to an SD adapter, to my PC. Any thoughts?
likely just a solder fuck up. people really shouldn't open their electronics and solder shit if they don't have the skills.
not that this is a hard solder job... especially on a 3DS XL. i did it half asleep at 2 am at night almost in the dark...
that rewriting the nand would damage it is of course ridiculous, it is rewritten by the 3DS itself continuously throughout using it!
the toshiba nand is likely rated for usage in the order of millions of rewrite cycles...
remember software routines have some sort of anti-brick routines. (crc checks, if true one write, next page, if false, skip and mirror faulty page).
Compared to writing a huge block of data at once 1:1, that fails suddenly can corrupt the whole crc'd page (n:1), thus bricked that area onwards (bad crc).
I think the point is, if there is a bad block, even with a valid dump, you will just keep trying to write to that, and screwing up the whole thing as no remapping takes place. Where as with software (3ds updating), the bad block would be remapped to the reserved area and all would be fine. Least that's how I read it.
Same used to happen with the 360, before the software that flashed a hacked nand image was updated to handle it automatically, you had to remap bad blocks manually before flashing. If you didn't and the block was in a critical area=brick.
You still have to remap bad blocks in the image now,when you are writing via hardware flasher, although the software that prepares the image remaps the blocks for you these days.
ah this really makes sense, thanksI think the point is, if there is a bad block, even with a valid dump, you will just keep trying to write to that, and screwing up the whole thing as no remapping takes place. Where as with software (3ds updating), the bad block would be remapped to the reserved area and all would be fine. Least that's how I read it.
but permanently brick? or just that you cannot flash back the dump it 'needs' until you fix the blocks etc, which we are not able to do yet.So yes, writing directly right now, depends entirely on the 3DS's NAND micro controller. A small fucked up bit, and a poorly handled "healthy" recovery sector, dirty line (bad solder), small electrical noise, etc could brick your NAND.
yup. same with new 4gb xbox'es. all remapping handled by controller. you can't see any bad blocks in your dump.To my knowledge, an emmc nand is having it's own controller cpu on board, just like a sd card is having one. If a block became bad, that controller will map it to another location of the internal flash memory area.