Printable View
You'll get the FW details from 360 Flash Tool, however I believe we need to decode the extracted fcrt.bin (if you have one of course - if you don't, you may not need to).
I've not attempted a DVD recovery on a Slim yet so have no experience in the matter.
this is pretty cool thanks martin c
Martin C, you wrote in the OP that it's not possible to use XNandHealer with a dash after 12625.
One of my consoles got flagged while connected to Live (foolish AP2.5 brainfart) and subsequently banned the end of August. Then it was fortunately involved in the unban wave of September and able to go back online, but it was still corrupting profiles and gamesaves, therefore it was still flagged. This is a Microsoft refurbished non-HDMI console from 09/09 so there is no way I have (or can get) the CPU key from it.
At the time it was unbanned, it had dash 13599 on it and I went ahead and dumped the Nand and ran it through XNandHealer. I figured if Microsoft had unbanned it then there was a good chance the flags that caused the ban were removed from their servers. They just didn't remove the flag from the console when it was unbanned. After running it through XNandHealer and removing the flags (there were 3 places in the secdata.bin that needed fixing), I flashed it back and it no longer corrupts profiles or gamesaves and is used on Live regularly.
So, my question is, how was I able to successfully remove the flags using XNandHealer on a 13599 kernel if it's supposedly been blocked by encryption?
I'm not trying to cause an argument or anything. But, if there's something being missed in all of this, then it should be found out.
Ok - lets get some terminology sorted first.
Without the CPU key, you CANNOT edit secdata.bin. You were not removing any flags anywhere. Secdata bin can be created a number of times in different locations (previous versions are referred to if the current one becomes corrupted), therefore xnandhealer / findsecdata looks through the NAND and discovers locations whereby previous versions are stored. This is the problem for most consoles, since the new format of secdata.bin introduced in 13146 (poss even 12625) with LDV being stored is normally the only one they have AFTER the corruption has already taken place so the secdata.bin mapping which was previously there is incompatible with the new style.
Your situation is fairly unique - not many people here have been unbanned by MS. More than likely when MS unbanned the console a new secdata.bin was created with valid values and therefore findsecdata had a newer file table to read from with valid entries. It doesn't manually edit anything as I said before, as it doesn't have the ability.
I'm assuming that if you made the changes under 13599 that you were able to update to 13604 without issue? If so, then what I've said above is accurate as far as my understanding goes.
For 99% of the people using this guide, they will only have a clean secdata.bin copy from before LDV was applied to the file and these are now invalid.
Where can i find a tutorial on how to dump the nand and get cpu key on a 13604?
This is a very well done guide Martin C, great job.
If it's an HDMI console, RGH it.Quote:
Originally Posted by realrat
If it's not, you can't unless you had the CPU key previously.
thx for the info
how do i know if its flaged on the server?
i checked my console with Xval said failed AP25 Chalange so can i clear it?
or is it to late i can still sigh into xbox live for now.
It all depends when you got the flag...you could clear it and take your chance and connect to LIVE you got a 50/50 chanceQuote:
Originally Posted by coolshrimp
Edit:
Just re-read your post..you have connected to LIVE since the flag so you will be registered on the server side as having Faied AP25