Jump to content


Photo

X360sam 0.4


  • Please log in to reply
61 replies to this topic

#46 foaley77

foaley77

    X-S X-perience

  • Members
  • PipPip
  • 446 posts
  • Location:Australia
  • Xbox Version:v1.1
  • 360 version:v1 (xenon)

Posted 14 September 2006 - 10:32 AM

going to try this

Edited by foaley77, 14 September 2006 - 10:34 AM.


#47 foaley77

foaley77

    X-S X-perience

  • Members
  • PipPip
  • 446 posts
  • Location:Australia
  • Xbox Version:v1.1
  • 360 version:v1 (xenon)

Posted 14 September 2006 - 10:58 AM

Why is it when I use this program the original firmware is only 128 k? I have enough room on the floppy


#48 Textbook

Textbook

    X-S Hacker

  • Last Chance
  • PipPipPipPipPipPip
  • 2,552 posts
  • Location:Near Flint, Michigan
  • Interests:Xbox and Computers
  • Xbox Version:v1.0
  • 360 version:v1 (xenon)

Posted 14 September 2006 - 12:48 PM

QUOTE(foaley77 @ Sep 14 2006, 06:05 AM) View Post

Why is it when I use this program the original firmware is only 128 k? I have enough room on the floppy


You're probably dumping an IDE drive's firmware.

#49 foaley77

foaley77

    X-S X-perience

  • Members
  • PipPip
  • 446 posts
  • Location:Australia
  • Xbox Version:v1.1
  • 360 version:v1 (xenon)

Posted 14 September 2006 - 12:53 PM

QUOTE(Textbook @ Sep 14 2006, 09:25 PM) View Post

You're probably dumping an IDE drive's firmware.


its doing this with mtkflash way as well how can i fix it?


#50 Nerry

Nerry

    X-S Young Member

  • Members
  • Pip
  • 30 posts

Posted 18 September 2006 - 01:27 AM

problem i'm having is that after entering the samread command, it will create the origin.bat file and be 512k.. yet it aborts when it finds out it isn't 256k

#51 Textbook

Textbook

    X-S Hacker

  • Last Chance
  • PipPipPipPipPipPip
  • 2,552 posts
  • Location:Near Flint, Michigan
  • Interests:Xbox and Computers
  • Xbox Version:v1.0
  • 360 version:v1 (xenon)

Posted 18 September 2006 - 02:24 AM

QUOTE(Nerry @ Sep 17 2006, 08:34 PM) View Post

problem i'm having is that after entering the samread command, it will create the origin.bat file and be 512k.. yet it aborts when it finds out it isn't 256k


Are you sure you're not dumping another drive's firmware? Try disconnecting all other IDE devices by physically unplugging them to make sure. It should definitely be 256k.

#52 Nerry

Nerry

    X-S Young Member

  • Members
  • Pip
  • 30 posts

Posted 18 September 2006 - 02:40 AM

my IDE connections are Hard drive & CD rom
and i'm using a boot disc too

any suggestions knowing this info?

#53 RiPpN-N-TrIppN

RiPpN-N-TrIppN

    X-S X-perience

  • Members
  • PipPip
  • 448 posts
  • Xbox Version:v1.1
  • 360 version:v1 (xenon)

Posted 18 September 2006 - 03:03 AM

sounds like you are dumping the FW from another drive
D/C every thing apart from what you need
i used a USB card to flash mine so i only had my xbox dvd connected every thing else i D/C
so if your using a boot cd only have that drive and your xbox one connected
rember your trying to dump from the SATA not the IDE
the FW for the 360 dvd is 256k
if your getting some thing diffrent your dumping the wrong drive


#54 Nerry

Nerry

    X-S Young Member

  • Members
  • Pip
  • 30 posts

Posted 18 September 2006 - 04:12 AM

Well i can't boot from CD, since i have to have my hard drive connected to access x360sam

I can't boot from the USB drive, since for some reason "USB-HDD", "USB-CDROM", "USB-FDD", and "USB-ZIP" are all selectable in my bios for bootsequence, yet none of those are my USB flash drive

any other suggestions?

#55 Nerry

Nerry

    X-S Young Member

  • Members
  • Pip
  • 30 posts

Posted 18 September 2006 - 05:38 AM

Also, what's the preferable combo for doing this?

ex. cdrom (boot) + hard drive (read/write)
usb (boot/read/write)
floppy disc (boot/read/write)


i might be able to get something other than anything involving USB

#56 zanzini

zanzini

    X-S Member

  • Members
  • Pip
  • 83 posts

Posted 26 September 2006 - 08:37 PM

I have an Intel ICH5 Chipset and am using the NTFS DOS CD for the SAM360. Im trying to back up the original .BIN but I keep getting MKDIR failed for 'backups'.

Can anyone please advise me what I may be doing wrong, ive disconnected all unused drives so all I have is my oroginal C: (Hard Drive), a D: (which I presume is my DVD Rom for booting the disk) and the A: whcih I presume is my Samsung Drive.

Should I be typing the C:\SAMREAD 5240406 12345 from the C: or the A: or does in not matter?!

Either way it doesnt work and im starting to feel like im a bit thick!

QUOTE(zanzini @ Sep 26 2006, 08:37 PM) View Post

I have an Intel ICH5 Chipset and am using the NTFS DOS CD for the SAM360. Im trying to back up the original .BIN but I keep getting MKDIR failed for 'backups'.

Can anyone please advise me what I may be doing wrong, ive disconnected all unused drives so all I have is my oroginal C: (Hard Drive), a D: (which I presume is my DVD Rom for booting the disk) and the A: whcih I presume is my Samsung Drive.

Should I be typing the C:\SAMREAD 5240406 12345 from the C: or the A: or does in not matter?!

Either way it doesnt work and im starting to feel like im a bit thick!


Just as a follow up im still getting A: even when the 360 isnt powered up, ahould there be a directory in the A:? as im getting directories for A: C: and D: although the D: only has COMMAND COM in it.

#57 Textbook

Textbook

    X-S Hacker

  • Last Chance
  • PipPipPipPipPipPip
  • 2,552 posts
  • Location:Near Flint, Michigan
  • Interests:Xbox and Computers
  • Xbox Version:v1.0
  • 360 version:v1 (xenon)

Posted 26 September 2006 - 09:55 PM

You use whatever your NTFS hard drive was mounted as. Most likely C: (or D:). Use whatever one was giving you the MKDIR failed, because that is completely normal. It is trying to make a folder and you already have it, so it says "Failed" because it's already there. Don't worry about it it's normal. After that though, it should run MTKFlash. That's where you select your SATA and read the original firmware.

#58 zanzini

zanzini

    X-S Member

  • Members
  • Pip
  • 83 posts

Posted 27 September 2006 - 12:20 PM

This is the message im getting now

MKDIR Failed
MTK Flash by Josepph Lin
WTU 1998 (ver1.83c)
PORT: 170, MASTER/SLAVE: G0

#59 Textbook

Textbook

    X-S Hacker

  • Last Chance
  • PipPipPipPipPipPip
  • 2,552 posts
  • Location:Near Flint, Michigan
  • Interests:Xbox and Computers
  • Xbox Version:v1.0
  • 360 version:v1 (xenon)

Posted 27 September 2006 - 02:46 PM

Is your Samsung MS25 or MS28? There are special instructions for MS28 drives.

eXOBeX, I thought of a good "check" for X360SAM. I've already talked to one person who somehow had a bad original dump of the firmware (all FF's) but was the correct size, so the process continued and it ended up putting FF FF FF FF FF FF FF FF into his xtreme firmware and flashing his drive. No good firmware backup, no more DVD drive in that 360.

A good check would be to check the key range area and make sure it isn't all FF's or 00's. flash78 had a program called keygen.exe that was basically like KDX from DOS, just printed out the drive key on screen.

#60 BastardSon

BastardSon

    X-S Enthusiast

  • Members
  • 10 posts
  • Location:Metro Detroit
  • Xbox Version:v1.6
  • 360 version:v1 (xenon)

Posted 17 October 2006 - 04:28 PM

QUOTE(Textbook @ Sep 27 2006, 02:53 PM) View Post

eXOBeX, I thought of a good "check" for X360SAM. I've already talked to one person who somehow had a bad original dump of the firmware (all FF's) but was the correct size, so the process continued and it ended up putting FF FF FF FF FF FF FF FF into his xtreme firmware and flashing his drive. No good firmware backup, no more DVD drive in that 360.

A good check would be to check the key range area and make sure it isn't all FF's or 00's. flash78 had a program called keygen.exe that was basically like KDX from DOS, just printed out the drive key on screen.


This is so true, 2 VERY important things that you MUST to do BEFORE you EVER patch or modify your orig.bin is to verify the filesize and then VERIFY the file has a valid key.

I know someone who also bricked his drive because his extracted orig.bin was only 48k. Assuming that all files should be 256k, If X360SAM could verify the filesize and abort before patching, i think alot of bricked drives could be saved. Maybe there is a dos command we can just add to the existing batch files to check for this.

I also like the keygen.exe v0.46 app becuase it displays the key in dos and dumps it to a text file. But the file has a dpmi problem when run outside of XP and is useless on a bootdisk. But it does show the same key as the current tools like 360FWToolbox. If X360SAM could display the key and then prompt to continue or
abort would be perfect.

If anyone knows how to get the dpmi working on a boot disk, please show the configuation and what files are needed. I download the files but it still didnt work right for me.

I'm not bad mouthing X360SAM, i think its a great tool. I just think these 2 features can make it an even better tool. I know you could still have a 256k file and be shown a bad key, but at least the user might have a chance to save the drive from becoming a brick.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users