O.P.A.: Warning - Don't Use the 'birdy' Flasher on a Non-v46

Date: Saturday, August 26 @ 21:50:36 UTC
Topic: Xbox 360

Been so busy working on Media Stealth, I was not watching other people's work, as my packages are good enough for me.
But I also run a repair business on the side, and after getting a ton of Hitachi's in the mail, all due to flashing with the "Birdy" flashing program, as people were in a rush to get the new Media Detect and were getting trigger-happy waiting for my next release.
I decided to look into the problem with the "Birdy Flasher" and "Bricked" drives.

Here is the problem:
In the script file there is labels to point to the various sections of flashing code. Remember each firmware build has different offsets and ram address for the hacks.
The Birdy script works great for v46 drives (as that is his model on his x360 system). But users with v59 and other drives were reporting "bricked" drives.

Here is why:
After detecting the version of drive by dumping the firmware, the system then starts the flash progress with the following script:

This is taken from the (V59) area:
***********************************************************
:Flash59
// ---- Flash --

status(flashing firmware)
EnCrypt

:fl461

status(flash 9003e000 Master checksum)
Flash(9003e000,1000)

iftrue
goto(fl462)
endif

YNMessage(Error by flash 9003e000 Master checksum retry ?)

IfTrue
goto(fl461)
endif
exit

:fl592
**********************************************************

It is clear as the ink on the paper, the problem is the flashing never gets to the (FL592) line, as the labels above are all pointing to the V46 code!
Ugh!. The problem is even worse, all the sections other than V46 all have the same labelling error. They all point to the V46 code after the first line.

To FIX the problem if you wish to use the Birdy flasher, then just edit the script file and change the three 46 numbers for your drive to the right ##.

If you already used the Birdy flasher, and now have a BRICKed drive.
I am very sorry, you will need to get a replacement drive or send the drive to a repair shop which can correctly remove the flash chip and externally reprogram it using your hopefully saved "backup" file...

That's all for now folks.... I will be releasing my own package soon with all the latest goodies, like "Media Detect v2", "Stealth Firmware", etc..



This article comes from 360-HQ.COM:
https://www.360-hq.com

The URL for this story is:
https://www.360-hq.com/article987.html