Print

[KevlarSnake]

when i flash my ms25 with x40a.bin does it matter if i use :


'mtkflash w x40a.bin'....                 or 'mtkflash w /m x40a.bin'...?

[Sir Smoke XIII]

Flashed 2 drives now, both by using mtkflash w /sata xtrem40b.bin  I'm using a VIA6421L pci-to-sata card (cheapass gear; was like 30 euro at the local pc store) and i hexedited the keys in manually. One was already flashed (with 3.3) and the other one was a virgin MS28.

Both are running fine !

Thnx C4E for this great release !

This post has been edited by Sir Smoke XIII: Oct 15 2006, 08:16 AM

[epicurean]

Can I burn the enable0800 iso with any program or only with CloneCD and Imgburn?

Assume DVD+DL disc required.

[langnao]

QUOTE(epicurean @ Oct 15 2006, 02:47 PM)

Can I burn the enable0800 iso with any program or only with CloneCD and Imgburn?

Assume DVD+DL disc required.

Maybe it is just me, I tried Imgburn but gotten a non-working enable0800. I switched to CloneCD, everything is okay. Both software using default settings ...

[shbykty]

QUOTE(socalbluetooth @ Oct 15 2006, 07:12 AM)

Just a FYI...extermedef.xml is a xml file so you do not hex edit it to add the code. It is simply a cut and paste operation and can be done in windows notepad. I did it and xtremebootmaker worked great after that. The xml file will be in the "C:\Program Files\X-Projects" location if you want to give it a try. It really is very easy.

I did as you suggested, and saw that the file already had those lines in it.  Here is the file from notepad:

<?xml version="1.0" encoding="iso-8859-1"?>
<main Definition="3">
      <firmware md5="f6e41ce8e8adad331b05e6ada01c2eda">
        <name>Xtreme Firmware 1.0</name>
      </firmware>
      <firmware md5="8712126f29041db40bb9c7e8473360b6">
        <name>Xtreme Firmware 2.0</name>
      </firmware>
      <firmware md5="07f07e7e275379d695d150ab56e396cd">
        <name>Xtreme Firmware 3.3</name>
      </firmware>
      <firmware md5="7ED2E14B101BBF878FA783567336F695">
   <name>Xtreme 0800</name>
      </firmware>
      <firmware md5="D17E1D6913AE1D972E95A9C87C17F9ED">
   <name>Xtreme 4.0a</name>
      </firmware>
      <firmware md5="62E7CDFD2F855DC22AD4A26C65F067C2">
   <name>Xtreme 4.0b</name>
      </firmware>
    </main>

I ran bootmaker and selected the 4.0 fw so maybe it modified the code automatically?  Does that make any sense?

Still at it...

Thanks for the help!

Just wondering, maybe for now would it be easier to just go with the 3.3fw version and try to remod it to 4.0 if I manage to get that to work rather than messing with the hexediting etc... at least until someone makes an idiot proof program to flash it on...

This post has been edited by shbykty: Oct 15 2006, 09:07 AM

[tanno]

It looks like there will be more bricks piling up based on 14 pages of these kind of questions.

Guys you really shouldn't be poking around your 360, get the experts to do it.

[shbykty]

Tanno:

You're probably right, and I'll try not to poke around in it with anything dangerous, but I'm gonna flash this bitch one way or another, and short of electrocuting me, nothing is gonna stop me now, I've come too far and wasted too much time to give up.  Bricking it would be better than quiting.  If it beats me at least it was a learning experience, and I can look back and feel good that I didn't give up.  If you are an expert then give me some good advice on how to proceed.  

 (IMG:style_emoticons/default/jester.gif)

[ntloser]

QUOTE(tanno @ Oct 15 2006, 03:42 AM)

It looks like there will be more bricks piling up based on 14 pages of these kind of questions.

Guys you really shouldn't be poking around your 360, get the experts to do it.

Another Brick in the Wall LOL

we don't read no tutorials / we don't need to think on our own.
why all the dark sarcasm in the forums

.................................


HEY....leave that drive alone
or else it will end up another brick in the wall
 

oh shit I am way over tired I am going to get off the computer now...

Guys just read the tutorials flashing to version 4 is just like flashing to 3 provided you use MTKflash to extract and flash.. and use a hex editor to get your drive key into the xtreme firmware (manual)  

OH yeah thanks very much to C4eva

This post has been edited by ntloser: Oct 15 2006, 09:42 AM

[shbykty]

Exobex said to edit a single line in a batch file to point to the new .BIN - What file are you referring to?

Below is my samread batch file.  It refers to xtreme32.bin, should the x360sam.exe line be edited to point to extreme40a.bin and also the samremod.bat for those who have already flashed using that PC?  

I ask this because I was thinking about using the 3.3 firmware just so I can feel somewhat vindicated for the effort put into this process.  




@echo off
md BACKUPS
if "%1" == "" goto usage
if "%2" == "" goto usage
md BACKUPS\%2
md BACKUPS\%2\%1
if not exist BACKUPS\%2\%1\ORIG.BIN goto step1
echo ORIG.BIN for Xbox 360 s/n %1 %2 already exists - aborting!
goto end
:step1
mtkflash r /m BACKUPS\%2\%1\ORIG.BIN
x360sam BACKUPS\%2\%1\ORIG.BIN SAMSUNG\XTREME32.BIN BACKUPS\%2\%1\HACKED.BIN
if errorlevel 1 goto end
echo.
echo Now unplug the SATA cable and power-cycle the PC & DVD drive before running
echo SAMHACK.BAT %1 %2
goto end
:usage
echo Usage: %0 7-digit serial 5-digit serial
echo e.g. %0 1234567 61005
echo This will create a folder for that particular Xbox 360, read the original
echo firmware (as ORIG.BIN) and create a modified firmware (as HACKED.BIN).
echo If ORIG.BIN for that Xbox 360 already exists THE PROCESS IS ABORTED!
:end

[amexie]

ms should use the enable0800 and write there own program to flash drives to original  but they should just make an iso and put them all over the net labled as what ever game so they are just targeting pirates and not genuine people who just want to back up there original's  they could not even give a warning game starts to load then just come up saying found and error with your drive and fixed it

[rec]

Successfully flashed MS28 drive. Previously running X33.

I simply took my backed-up ORIG.BIN and ran X360SAM to create X40A.BIN.

I then wrote X40A.BIN to my Samsung using the bad-flash recovery (10 sec) method.

Booted Xbox, tested games, all running perfectly.

Thanks for another great release!

[crosseye]

any confirmation on the /m switch? I've never used it before when flashing. I've always had the command "mtkflash w x40a.bin". However, the release says use "mtkflash w /m x40a.bin". Does it matter which one you use?

[MaxEgg]

QUOTE(crosseye @ Oct 15 2006, 08:59 AM)

any confirmation on the /m switch? I've never used it before when flashing. I've always had the command "mtkflash w x40a.bin". However, the release says use "mtkflash w /m x40a.bin". Does it matter which one you use?

Its mainly for insureance.  use it anyway and you can have less fears of failure.

[crosseye]

gotcha. Thanks.

[calvin940]

QUOTE(Samy`D @ Oct 14 2006, 11:58 PM)

I still think what I said could definately be a possibility, I mean, they wouldnt be reflashing them all the time, they would reflash it once, and only if you have hacked firmware. If c4e can make a disk iso that enables reading, M$ might have a shot of doing something similar...hell, they could even d/l the one that comes with the xtreme firmware and integrate it into a gamedisc somehow, along with a program that detects which drive you have so it can reflash the firmware it wants on there. maybe itll be the standard latest 'original' firmware for you brand of drive, maybe you could reflash it after they do that, I think its certainly plausible anyway.

Reflashing it once doesn't make sense because I would just go and flash it back to 4.0 or whatever right away, so if they were to put together a reflashing strategy, it would have to be one that checks and reflashes when it is not "orig".

Possible that MS be able to make a flash routine? Absolutely.  Would they ever do it?  Corporately, I think this would never be advocated.  Lots of things are "possibile/plausible" to do, but "would" they do it? No way for the same reasons they never tried to reflash your xbox fw even though plenty of people had flashable bios.    MS, Sony, Nintendo are not going to take actions resulting in bricked consoles (regardless of how small a percentage that is (sometimes flashes go wrong, power outages happen etc).  

QUOTE(Samy`D @ Oct 15 2006, 12:10 AM)

Oh and for the record, all those posts Ive seen about people asking if you can do it manually, yes of course you can. if you changed the keys position in the firmware something bad would probably happen. That said, I dont know shit about firmware coding so it might not be the case, but I hexed in my key from my original firmware and it worked fine.

I've never used any other program except hexworkshop and mtkflash to do it...i dont know how that x360sam thing works but it sure seems like a waste of effort....

<snip>

People are inherently lazy.  They want someone else to tell them answers and do all the work for them.  If they didn't, they would make a fw file the old fashioned way using a hex editor and then also do one with x360sam deal.  They could then compare the resulting bin files using something like ultracompare to see that the bin files created either way are identical.  But, they are too lazy and want all the answers.  These are the people that will also end up bricking their drives because they aren't willing to put in the time necessary to do it right.  These are also the people that always ask "I hear flashing fw is possible to play backups.  How do I do it?" That for me is an instant ignore.  There are so many freakin posts here about all aspects of it that it is unforgiving to ask such questions when searches or browsing will give you what you need.

Cal