Post by: Xbox-Scene on August 05, 2006, 01:09:00 PM
| Ryanmp31 released a new version of the Toshiba-Samsung TS-H943 firmware USB-stick package, now using Commodore4eva's TS-H943 Xtreme v2.0 FW: Quote
Download: n/a (might be illegal under DMCA/EUCD) News-Source: xboxhacker.net |
Post by: Textbook on August 05, 2006, 12:26:00 PM
QUOTE(Xbox-Scene @ Aug 5 2006, 03:16 PM) 
Second of all, instead of writing the orig.bin to a new file, in hopes of getting the flasher out quick, I took that part out as well and now the program just overwrites your orig.bin with the correct values to make it the xtreme20.bin (although the name remains orig.bin.
(IMG:style_emoticons/default/mad.gif)
Why? So...you're completely overwriting their original firmware? So now, if something goes wrong, you're completely screwed, because there is no ORIG backup. This just doesn't make sense to me. Not only that, but he makes your "custom" Xtreme20.bin file named orig.bin. How confusing is that going to be trying to help people? This isn't helping people at all, it is overwriting their original firmware backup with the xtreme20 and naming that orig. For people that brick their drives using this, it's going to be alot of work to get them fixed. Use the manual way people!
Post by: nephilim on August 05, 2006, 12:48:00 PM
it repaird now and if your wondering how i fixed it i done the old way
i opend the drive up and removed the bios chip on the drive and reprog it direct
(buy the way i tryed a direct prog of this firmware before restoring my back up result dead drive)
here how i done it
used a smd hot air station the epoxy round the chip aint heat proof lol it just breaks up
removed the chip used a willem programer to reprog the 39sf020a
used my original flash unbricked my drive
but as i say folk dont have the tools like that so take care on what your doing
cos bricking a drive is all too easy
Post by: jtom617 on August 05, 2006, 01:06:00 PM
The xtreme firmware v2.0 is great though. But i will stick to just flashing it normally with mtkflash.. (IMG:style_emoticons/default/pop.gif)
Post by: Textbook on August 05, 2006, 01:36:00 PM
QUOTE(nephilim @ Aug 5 2006, 02:55 PM)
i used this firmware it bricked my drive i think there is a bug in it
it repaird now and if your wondering how i fixed it i done the old way
i opend the drive up and removed the bios chip on the drive and reprog it direct
(buy the way i tryed a direct prog of this firmware before restoring my back up result dead drive)
here how i done it
used a smd hot air station the epoxy round the chip aint heat proof lol it just breaks up
removed the chip used a willem programer to reprog the 39sf020a
used my original flash unbricked my drive
but as i say folk dont have the tools like that so take care on what your doing
cos bricking a drive is all too easy
There is evidence to back up my claim.
QUOTE(jtom617 @ Aug 5 2006, 03:13 PM)
This autoflashing business is a complete nightmare.
The xtreme firmware v2.0 is great though. But i will stick to just flashing it normally with mtkflash.. (IMG:style_emoticons/default/pop.gif)
And a supporter. Need we say anything else? Don't use the autoflasher!
Post by: KUNFUCHOPSTICKS on August 05, 2006, 01:50:00 PM
http://forums.xbox-scene.com/index.php?showtopic=536923
but i guess this is offical
Post by: garyopa on August 05, 2006, 03:23:00 PM
v1.0 was bad, very often reading nothing but >FF's, and then programming the
Samsung with the Xtreme firmware, never checking the read file, or anything.
v2.0 is even worse, not even storing a backup. Ugh!
I had way too many BRICKs here from users using this program, and the worse
is with and all >FF's backup, the dvd-key is lost making two nice bricks one the
motherboard, and two the dvd drive, only thing can be done is save the dvd drive
by selling it to someone else and programming it with their dvd-key for their x360
system.
Please Please Please if you are going to use this auto-flasher, please please please
stop the batch progress and check the orig.bin file yourself manually.
Oh'dear Oh'dear. This program needs some serious noob-proofing.
Post by: proger on August 05, 2006, 04:09:00 PM
I know you could brick less drives then this guy has! (IMG:style_emoticons/default/smile.gif)
This could almost classify as a Xbox 360 virus. (IMG:style_emoticons/default/tongue.gif)
This post has been edited by proger: Aug 5 2006, 11:11 PM
Post by: jtom617 on August 05, 2006, 04:45:00 PM
QUOTE(proger @ Aug 5 2006, 11:16 PM)
LOL, true that! worse than over heating... (IMG:style_emoticons/default/laugh.gif)
Post by: Fluxburn on August 05, 2006, 09:38:00 PM
>>>> Nm lol, it doesn't make a backup first. Haha use mkflash and make a backup, then I guess you can try this program if you feel lucky. Why is this even released if it is that horrible?
This post has been edited by Fluxburn: Aug 6 2006, 04:40 AM
Post by: billyrainbow on August 05, 2006, 10:16:00 PM
Post by: Textbook on August 06, 2006, 01:11:00 AM
QUOTE(billyrainbow @ Aug 6 2006, 12:23 AM)
Just as Auto Flasher v2.0 is released C4E releases Xtreme v3 with media stealth capabilities!
Great job C4E, release a new firmware rendering the autoflasher useless. Please Ryanmp31, don't make another one. It's already easy enough with MTKFlash.
Post by: Be_Vigilant on August 06, 2006, 03:58:00 AM
The old version of autoflasher worked PERFECTLY on my samsung.
And yes I did check the orig.bin b4 flashing !
--
Hopefully a new autoflasher will come out to support the v3 FW (IMG:style_emoticons/default/laugh.gif)
Post by: cnotemd on August 06, 2006, 05:48:00 AM
Post by: rhem on August 06, 2006, 08:57:00 AM
What's The Easiest Way To Flash My 360 Without Opening It Up, That Is Pretty Stable?
Thanx