QUOTE(sdeens2009 @ Nov 4 2010, 05:11 AM)
I found the real truth and answer in another Euorpean forum that already received the Kinect dash two weeks ago before the US officially received at its final non-beta level: 12611.
They too were evaluating this new Kinect dash at earlier levels prior to 12611 (beta Kinect dash) and its apparently very sensitive to the presence of any "non-MICROSOFT" USB key or thumbstick in the consoles USB ports during the kernel upgrade process. It actually slows it down too considerably.
This is EXACTLY why that fellow at top of page: REDNAS was getting E71 after flashing and testing with the Kinect kernel was updated; and his E71 went away ONLY after he immediately removed the offending USB stick. He was very lucky it didn't go RROD. This new kernel is very sensitive to certain types of USB sticks.
This kernel may NOT like NON-Microsoft USB thumbsticks in the USB port during the Kinect upgrade process; apparently there is a check for them and its creating a bad side effect that can slow down or corrupt the kernel update process to 12611. This is a very big two stage upgrade btw which is unlike 8599 and 9199 which were not that big. This may not effect all USB sticks, but its creating some sort of bottleneck during the upgrade which might be leading to the nand firmware corruption.
This in turn may trigger RROD after you shut it down electrically and the SMR and all capacitors discharge for at least 90 seconds. This is why it will work until you shut it down.
I spoke to some others on-line and a few went RROD if they had a cheapo USB thumstick in the the front port, so I am not alone on this observation. This is what led me to find the Europeans whom already knew about it.
You have to remove the non Mircosoft USB thumbstick first before taking the Kinect dash upgrde to 12611 or you risk brick: RROD which may not be purged by another X-clamp replacement. The nand firmware is subtly corrupted during the upgrade process and the nand (i.e BGA probably will need to be removed and reflashed back to 9199 kernel manually) and possibly start all over again.
There may a way to purge the corrupted firmware short of a chip removal ( tried all the gimmics I can think of)
So, I am interested in any and all suggestions short of BGA removal, since I don't have any blank fimrware/nand chips and reballing the removed orginal is too much of an adventure. I have the UP-2007 programmer with EBGA adapater so I can reflash a new blank one and install it myself. Done this hundred of times, but reballing is too hard IMHO. and besides I donlt know if the BGA had any locked OTP registers that need to be set manually.
This USB stick fiasco is EXACTLY what I observed last night, becasue I forgot to mention I had a non-authorized cheapo USB Magnovox thumbstick in the front port of my Falcon when I took 12611 dash, that I never removed during the Kinect dash upgrade; I guess it is checking for it and since it does not meet the quality control criteria laid forth by MS it seems to cause an temporary interruption during the kernel upgrade process (that is why it seemed extremely slow to me) and this in turn is the initial trigger.
I hope you guys remember that "waring message" from MS that specifically warns us NOT to use or format non-authorized USB thunmbsticks? Well this is the accidental payback...BRICK--RROD or E71 during upgrades...accidental bricking RROD.
Incidently, you guys who said my Falcon was an inneveitabe RROD were not using your common sense; use Google next time to see what other sites in Europe are noticing since they often get these new kernels before US..this is not just an isolated case. It has extra cooling fans and its temps were monitored closely. This Falcon was my best and coolest running console.
I had another Falcon and Zephyr both former RROD that I did the X-clamp on and they both took perfectly the kernel 16611, but I wisely removed my Magnavox USB thumbstick. I wont make that mistake twice. and the 12611 kernel upgrade process was literally more than twice as fast. That was the first clue that I knew they would survive it. They work fine now 24 hours later.
In some consoles, if you remove the troublesome USB thumstick/key the RROD goes away but not all consoles will fully recover. I need to dig deeper into seeing which consoles are most sensitive to being hard bricked; but the Falcons seem very senstive to it.
This was first observed two weeks ago in England with some of the beta Kinect dash kernels and they found out yesterday that even the latest 12611 is still triiggering sometimes RROD in some consoles if a non authroized cheapo USB stick is plugged into the front USB port (like my cheapo Magnavox USB stick). not 100% sure about that back USB port.
Heads up guys and get that cheapo "NON-MS" USB stick out or you risk RROD on your Falcon or at the very least E71 during a Kinect 12611 upgrade process if your testing LT1.1
SORRY, MY FRIEND...
You are ABSOLUTELY WRONG!!!
Your falcon died cause all falcons die!
At least, and if you have RROD, check out your error code, and see where is the problem that caused it.
I know LOTS OF PPL that UPDATED via USB STICK (NON MS)
And NO ONE HAD THAT PROBLEM!!!
QUOTE(nuttyrich @ Nov 4 2010, 06:08 AM)
Sdeens is onto something.
I consider myself lucky because I had my sansdisk usb drive in.
I downloaded the new dash upon rebooting it no longer read my usb drive and said it must be configured for the xbox 360 (something along that sort).
It basically formatted my usb stick.. and erased everything I had on there.
The USB stick can now be used as a 512 meg memory stick (Microsoft formats it and then reserves 512 to be used as a memory card. (I've never seen this before).
The rest can can be used as a regular usb stick.
Please take out your usb stick if you have one in there while updating, I consider myself lucky not getting an error but notice usb stick is used a different way now.
Hopes this helps someone.!
That was cause your usb stick was NOT FORMATTED in FAT 32.
Thats all...
i updated 3 consoles with a non MS usb stick, and i had no error in none of the 3 ones!
Author
Topic: Test Results For Current Fw On Final Kinnect Dash - Post Here! (Read 986 times)