IRIEZ,
why did you wait until the 24 page of this thread to tell us that version 5.1 is privately being tested? if people knew that, they would have wisely NOT wasted their time updating and re-opening their fagile XBOX360 shells. I of course did NOT take this update--and will NOT.
This means v5.0a/b is already obsolete...
The comments from C4eva were very clear on this point..he stated a new update would be released shortly..in others don't waste your time using v5.0a/b.
In this game the
EARLY BIRD does not get the worm...he often gets crushed..patince is the order of the day when new firmware is released...people sould NOT rush out and use it until its been in the stream for a few months and survived a few rounds of XBL updates.
I wonder what potential damage that Blaster 360 is going to do if people improperly use it..
I can already see the million threads on how its bricked their HDD (corrupted its partion etc) or DVD flash memory..the yhave stated publically it was loaded with all sorts of bugs..I read Team Execture reports and it does not leave me with a comfortable feeling...i suspect it will take them few generations before they work out ALL the bugs..just like the PS2 AND xbox360...EARLY BIRD GENERATIONS ARE ALWAYS BUGGY--I would advise being careful using it until its been out a few months at least..don't be Guinee pig for new hardware.
I will offer a safer and cheaper solution below to that blaster360...TEXTBOOK tutorial.
BTW,
here is a good lesson and comparison for what we are going thru with these new firmware updates:
testers of Dishwork satellite TV AUTOROLL scripts recently understand EXACTLY what I am saying...there might be a few of you guys who test Dish...and I'm sure you have been thru thru ALL the wars with dynamic code card updates and card loop attacks.
to me playing around with firmware is similar to testing Dish sat TV cards...and what I'm surprised most about is how little has been developed in flashing the onboard flash memory TSOPs via JTAG trapping programs--i.e the BIOS..that is probbaly an area that needs quick attention before it is too late...somewhere in calander year 2007 MS could brick these consoles easily in 2 seconds flat.
but I don't want to digress too much from the topic at hand...just wanted to offer a comparison that is topical.
I repeat again, I suggest everyone wait until this firmware is tested for at least several more weeks then and the ripping tools get updated and we monitor closely how the game patches from XBL affect it....
its the updates that we need to worry about...there have been many e66 and e79 reports that can't be fully identified as to the real cause.
Does Error 66 ring a bell?
That should have been warning shot across the bow...only now are there easy tools to fix it...another one was released tonight.
my suggestion is wait , be patient and allow ONLY a small % of testers to play with it....I suggest to C4Ev he be more careful releasing these things for public consumption especially if he anticipates more immediate upates are right around the corner...this is a RADICAL update not just a minor one.
its wonderful his contribution,
but caution is advised...even the best coders with perfect track records get nailed hard..just ask Penga the guru of Dishnetwork hacking scripts; make a long story short Dishnetwork found a major exploitbale hole in one of his popular scripts 2 weeks ago and killed a very very very large % (tens of thousand of hacked sat TV cards)..it was called "BLACK TUESDAY" and it marks as the largest and major ECM eventin history against what was considered the safests autoroll script on the market.
stay with v4.2b for now, its tested to work with current XBL updates..so if you dont update they can't easily kill you..at least until they force a stream update...which BTW they can easily...but we can se that comming.
we need to start logging these XBL streamd updates...is anyone doing that?
incidently,
i don't agree at all wit what IRIEZ, says no one in this thread is having any success ripping and burning XBOX1 backups (which is what this update is all about in the first place)...despite his claims that he spoke to (10) ten friends who have no problems...I don't see them adding their suggestions; therefore its unconfirmed and hollow should NOT be taken as truth.
all of what I siad was true..we agree to disagree.
until we can do at least 10 XBOX1 games start to finish that run perfectly its is NOT a working solution..and we have what apears a ways to still go...both in firmware and tools
all I see is bold statements that it works, but it DOES NOT--certainly with NOT enough consitancy to justify its implementation.
after 27 pages of asking for advice on how to do it, I think that alone is proof enough.
this is a cmobination of problems: firmware is still in beta testing and has bugs, ripping tools need updating and different hardware DVD drvives (MS25 vs. MS28) are reporting different results when backups are burned with exact same procedures...so its a combination of problems.
this is NOT a flash and go update.
also somones asked how do they reflash without opening up the XBOX360 each time ( I mentioned this above)..well I will share with you the TEXTBOOK procedure with my additional modifications:
I do it excatly as he sugegsted, but I use a Dremel tool to trim the inner casing metallic shell (the area between the memory card sockets) to allow the female SATA cable to pass thur the casing shell without it being pinched or the plastic bezel on the outside being trimmed..just pass it thru the front of one of th memory card slots...very easy to do....and a DREMEL tool is cheaper than that $70--Blaster360, whch still is in beta testing and hasalot bigs in it.
buy this for $5 with free shipping with PAYPAL (coupon: PAYPALFREE) and install it:
http://www.newegg.co...N82E16812206003pics:
http://www.360mods.n...ls/album=3.htmlif you do this mod you wont have to spend $70 on that expensive blaster 360 which is uneccesary..this is how to do it.
if you feel my attidude is wrong or arrogant, then good, I got my point across and it might give someone pause to wait and be more cautious until more is known about this firmware release and beta testing is finished.
you guys are playing Russian Roulette with these firmware updates.
walk blindly into an update and you'll brick your console one day..I have seen this happen many times over the years..when new toys are released...and the MODs have to be even more cautious as well.
i don't see enough caution being used here.
Author
Topic: Xtreme firmware 5.0A and 5.0B for TS-H943 (Read 1787 times)