well then i think we are due for another dash update then or one of there patches....
i assume by now they are aware of this issue....
it's doing the same on my legit 9199 consoles..... 

a pic be nice...make it easier...

take a pic...lol

this is due to Efuses(LDV values)im sure being blown in the CPU when we do these dash updates..
lot of our errors are coming from users with donors or just no info on there nand(corrupted read and show no errors)
and also user error on the respect of knowing how to place it/inject/flash it, but something happens within this time.
pc's glitch in a nanosec we don't see it and most programs have a timeout value along with the hardware making the user think there correct info being transferred...

so they have to match the paths in the CPU area where the info has been locked forever(blown Efuse)..
with a corrupted nand...not easy to do
when the Efuse is blown it's like a maze shutting down electronic info paths and rerouting them...(LDV values).

i am at the era of this is true and now i am looking for the dead locked pathways seeing whats on the other side
and does it need the info that's locked still to make the connection to where it is going or does it just shut down,
 the path and keep us from going into the SB,GPU or cache for the system to open back up(with no information to do this just opening a simple path(nothing to unlock just start your connection from where the fuse path was locked)...
anyways that's my thing

as far as i know it's takes sampling through 360flashtool to find the right values to reconstruct a orig nand...

I don't imagine the upper bold writing being applied to the re-booters.
all i ever see in the boot loader sections are LDV 1 1 0 or 1 0 1 (fuseset)

course i can be going about this all wrong or half right...
so far thanks to all involved and the new 1.94 flashtool it's been working...

it's is only for a region change to play different country's games....
and now that can be done with all the software out ...
but it was cool to see it boot from NTSC to PAL or PAL to NTSC or other regions...

you can try the wiring on top and run 1 DB1f1(FT1U2) point through the south bridge hole...
also if that board is warped in any manor it can cause and error....(re-flow/re-heat the GPU).
do you have the stock clamps on? with the hex screws on the bottom?
do you have the xclamp fix and the bolts/screw heads or to many washers on the bottom,
causing it to bow up when screwing down the mobo?


3 main reasons why it would cause E79 are,
1) corrupt kv(not your issue)...
2) one of the diode wires loosing connection or shorting out through the tape when pressure is applied on the mobo(all it takes is 1 small pinhole) after screwed down to the frame...
3) one of the solder balls loosing contact under the GPU area (due to being warped just a tad)
this could be from to many heatups outside the main frame with a small warped board,so now it's mended (works) but as soon as the screws pull the mobo down it breaks that connection on the GPU( I had over 20 boards do this) some showed signs of this because of the fan speed altering when pressing on the mobo(only on some)...

the kv.bin won't even load up in bincrypt(weird)

and yes he has to go through and try different ldv values....

not really ...i am going to email support though.....

you wrote,
I've tried hooking up an original (non-HDDHACKR'd) drive to the end of the cable and it doesn't recognize it either -- so it doesn't have to do with how the drive is made


well yes, because of this unit(i have the blue one with disk) only sees Xformat or nothing(as of now)..
now if it was possable for any 2.5 sata to work ,then it be a whole different story...M$ won't make there money ...lol
Only in a jtagged unit will any 2.5 sata drive been seen, in the stock casing(port) for format and workability ....

that's why i posted what i posted 50e

i will be looking into this to...but i always used the pc so...

what i meant is did you just have the disk and then a off brand hd rewader...but i take it you have the official disk and cable hookup(usb)...
so then with this new dash 9199.stock boxes can not do it through the box...did you write m$ or look on there site about this?

but mistakenly click "format"...
well then that's there problem ain't it...understanding anything simple is simple and the pc way is the best way......
remember they have to learn the right way(this is how the world works)...not the whatever lame way there messing up with...

no you can't use freeboot or xbr# to make it a liget console....that's a stupid question
if you took the time out to read the forums...you would know you can't do this........
2 hours for a 40 min nand right on a 16mb nand is all it takes to flash back the orig nand.
 then go update the dash if you want a legit box,but what a waist of a jtagged unit after that ..

Blade007 wrote,
I have read several posts around the net and seem to get the impression you have to move resistors and use 16Mb XD card as the USB card writers cant raw write correctly to a 256Mb card. People have also said that you should be able to switch to the xd card and flash via USB SPI as it see's the XD card as the nand when switched so would it be able to write a 256Mb nand image to the card via this method so you dont have to use a 16Mb and swith resistors so the onboard nand becomes un-usable


not in this lifetime...this is why you have to move the resistors and use a 16mb xd..
still problems with the 64mb(for 256mb-512mb) one though so it won't be released at anytime soon...

or ST-6KO2D733 bigger one center leg cut.....

you can replace it with a (PH62)BCP51 (2T751)smaller one 3 leg...
or J210G or WJD210 bigger one center leg cut.....
which one....
3 leg small or 2 leg larger one...let me know if your in the states ....
more or less they just through anything in there that varied ....
I checked all my 35 mobos...

relient_k you gave me 4 nand copy's...
1)....orig corrupted like a mofo due to the lpt's wiring it looks like it....
2)....small corruption ...different CB from others..
3)....looks like freeboot but messed up cb and ldv values
4) freeboot and totaly messed up cb values with a 6bl of 12.8?<not right..

I don't have 1 solid nand or cb or ldv value......
be straight so we can fix this....
that copy i sent you to try hasn't the config.bin,it's just to see if you get a boot up....
if your going to blow smoke up my ass i am done with you....(sorry i don't have time to play around)..
was this a ban unit and you messing around?
was this a totally corrupt problem reading the nand(to many block errors i see on orig2)and you send me patched up donors?

yes that is it...and well worth it ...in the future you can also get other adapters for stuff...
also ask if its a 5.0E the newest, it's hard to tell ....and the price range is ok ...just the shipping time is 3 weeks...
watch hong kong shippers there taking up to 1 month because of customs......try to stick with Shanghai, China because of prices and 1-3 weeks shipping time...USA sellers will rape you on this item...

i also think that you can do this with a InFeCtuS 2 with the 30 wire hook up...

collions,
did you swap over the nands or the nand info for the working cpu...and did you make sure you didn't overheat a Electrolytic Capacitor(s)
by the cpu in the process or the caps on the bottom of the mobo
(under the cpu)

ok,
but if that was the case then 360flash tool would of loaded it being a full 16mb nand.....
anyways just pass it on and we will see...

jesus dude...i can see if this was a 256 or 512 but you f***ed up a 16 mb dump....40 mins to read the whole 16mb off lpt or 4-6 mins off SPI usb...you couldn't wait to do that....wow
anyways if you think you have a good version of kv and whatever pass me over your 2 nand dumps and the kv...
i see what i can do...

and you didn't flash xellous into the orig nand and then lpt it over to the computer did you?