User User name Password  
   
Wednesday 7.5.2025 / 21:10
Search AfterDawn Forums:        In English   Suomeksi   På svenska
afterdawn.com > forums > consoles > xbox 360 - modding & hacking > some news....
Show topics
 
Forums
Forums
Some News....
  Jump to:
 
Posted Message
theridges
Suspended due to non-functional email address
_
26. August 2006 @ 23:26 _ Link to this message    Send private message to this user   
O.P.A.: Warning - Don't Use the 'birdy' Flasher on a Non-v46
>> From garyOPA on forums.xbox-scene.com:
[QUOTE]
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..
*****Updated*********
Birdy Flasherv2.2 with Xtreme v1.3 and 2.0 FIXED
>> Geremia has released a fix for the birdy flasher, to prevent non v46 drives from being bricked..
[QUOTE]
I've corrected by hand the problems in original patch.scp and reverse.scp that caused bricked drives with birdyflasher, thanks GaryOPA for pointin, anyway i've not such drives to test myself, so use at your own risk or wait OPA latest fw to come.
[/QUOTE]

This message has been edited since posting. Last time this message was edited on 26. August 2006 @ 23:27

afterdawn.com > forums > consoles > xbox 360 - modding & hacking > some news....
 

Digital video: AfterDawn.com | AfterDawn Forums
Music: MP3Lizard.com
Gaming: Blasteroids.com | Blasteroids Forums | Compare game prices
Software: Software downloads
Blogs: User profile pages
RSS feeds: AfterDawn.com News | Software updates | AfterDawn Forums
International: AfterDawn in Finnish | AfterDawn in Swedish | AfterDawn in Norwegian | download.fi
Navigate: Search | Site map
About us: About AfterDawn Ltd | Advertise on our sites | Rules, Restrictions, Legal disclaimer & Privacy policy
Contact us: Send feedback | Contact our media sales team
 
  © 1999-2025 by AfterDawn Ltd.

  IDG TechNetwork