Print

[tonytone55]

just to give an update from yesterday. i was able to fix my friends drive. i noticed that if i tried to use the disc again and the 360 was not on in the initial read stage nothing happened, as soon as i turned it on there were letters that would flicker which told me that the drive was still working and could connect to my comp. i gave dosflash a try and it worked. (with lots of hiccups) THANK XBOX SCENE for the help. i wasn't able to update him to 1.51, i put his old 1.41 on to make sure it worked. now that that is all done i went to update to 1.51 and now my comp just hangs at the ram test and finds my hdds. cant get into the bios, nothing and wont load windows. so after all that, my friends box is the same as i started and i have a comp that doesn't do anything. all in all i accomplished nothing. great day words of advice. be careful about your power and connections with this disc. Otherwise you will spend a day fixing something you shouldn't have had to.

[1hotjob]

I just flashed 3 drives today and none of the files were backed up. I used the 1.52 disk. I noticed after looking around that the 360 mod disk was booting to C:. I looked on the disk trying to find an autoexec or config file but couldn't find anything. 1.51 backed up files to my HD, so I thought nothing of doing these and then found the problem.

I sent one off, but the others I will re-read to get a back up of them.

Is there a way I can change this?

Is there a way you can write 1.53 to have it load to X or Z drive?

Edit: After thinking about this, I don't see how it worked in the first place. If the original firmware wasn't saved to the C:\Samfiles, where did it find the file to create the modded firmware? It gets crazier the more I think of it.

I also looked in the one folder on the C:\Samfiles and it was empty. I guess the 1.51 didn't save the files there. Does it matter that my HD is a SATA drive?

Love the software though. I just need to get my bugs worked out.

[jinn]

QUOTE(1hotjob @ Mar 29 2009, 06:55 PM)

I just flashed 3 drives today and none of the files were backed up. I used the 1.52 disk. I noticed after looking around that the 360 mod disk was booting to C:. I looked on the disk trying to find an autoexec or config file but couldn't find anything. 1.51 backed up files to my HD, so I thought nothing of doing these and then found the problem.

I sent one off, but the others I will re-read to get a back up of them.

Is there a way I can change this?

Is there a way you can write 1.53 to have it load to X or Z drive?

Edit: After thinking about this, I don't see how it worked in the first place. If the original firmware wasn't saved to the C:\Samfiles, where did it find the file to create the modded firmware? It gets crazier the more I think of it.

I also looked in the one folder on the C:\Samfiles and it was empty. I guess the 1.51 didn't save the files there. Does it matter that my HD is a SATA drive?

Love the software though. I just need to get my bugs worked out.

Name the back up folder 1 or A and the oring and itreme will be there.
Then rename it in windows

[1hotjob]

I am going to reconnect the drives and try it again. I would really like a back up of the original firmware.

[FrostyTheSnowman]

QUOTE(1hotjob @ Mar 29 2009, 11:04 PM)

I am going to reconnect the drives and try it again. I would really like a back up of the original firmware.

Make sure your backup folder name is less than 8 characters in length or that can happen. (empty folders)

Also, there is not many changes between v1.51 and v1.52, v1.52 was just released to fix the issues some users were having. If v1.51 worked better for you, then you can always stick with that one, as the actual firmware is the same in both releases.

Also, to clear up the whole C: thing:

1. This disc uses a 'fake' C: drive to do it's work (only while the disc is running)
2. Your real NTFS/FAT/FAT32 HDD is actually mounted as the D: drive (only while the disc is running)
3. All files are backed up to the D: drive in the 'SAMFILES' 'LONFILES' or 'BENFILES' folders

The scripts are telling you that your files are being saved to C: when in reality they are being saved to your real HDD (D:)

The scripts only say C: for backup because that is what you see your real HDD as in Windows.

[techmob]

how does spoofing work with this disc?

my drive is a BenQ spoofed as a different Benq version, will this disc auto detect and spoof it for me?

can someone clarify thanks

[wulfie]

QUOTE(Fear345 @ Mar 30 2009, 05:01 AM)

Will this work with a hitachi 78fk spoofed to a ms25 ? if so any tips i need to know ?

I've got a sammy spoofed as liteon in my jasper and it worked just fine.  Just follow directions as they appear on your pc when you load this disc

[Fear345]

QUOTE(wulfie @ Mar 30 2009, 03:46 PM)

I've got a sammy spoofed as liteon in my jasper and it worked just fine.  Just follow directions as they appear on your pc when you load this disc

So being an Hitachi drive and they not being able to be done in dos makes no difference once spoofed ?

[1hotjob]

QUOTE

Make sure your backup folder name is less than 8 characters in length or that can happen. (empty folders)

I think that is the root of my problem. I was naming the folders with the serial number of the Xbox, 12 numbers. Not thinking of the 8.3 limitations of dos. It has been too long since I have worked with DOS files.

It would be helpful for those in the future using your disk if you put that in the line where you ask for a folder name. If it is in there, I read it so fast that I skipped it. Maybe a red font warning more than 8 characters will result in the backup files not being saved.

Now it is time to try to make the serial port. I bought a set up with a USB to serial.

[luckout]

Why am I getting "error reading from drive d: dos area: general failure"?

[techmob]

just used this for the first time, and it dumped and flashed no problems

thanks alot

[FrostyTheSnowman]

QUOTE(1hotjob @ Mar 30 2009, 11:01 AM)

I think that is the root of my problem. I was naming the folders with the serial number of the Xbox, 12 numbers. Not thinking of the 8.3 limitations of dos. It has been too long since I have worked with DOS files.

It would be helpful for those in the future using your disk if you put that in the line where you ask for a folder name. If it is in there, I read it so fast that I skipped it. Maybe a red font warning more than 8 characters will result in the backup files not being saved.

Now it is time to try to make the serial port. I bought a set up with a USB to serial.

I'm pretty sure there is a warning line right above the prompt, but it's just normal white text so I wouldn't be surprised if people were missing it. Is it possible to change the color of text in a DOS batch script?

But yeah, my disc will still mod your drive successfully even if an invalid backup directory is specified, it uses a fail-safe script that backs up your ORIG.BIN file to a RAMDISK so that it can still successfully modify your 360 drive regardless of the backup directory's name.

QUOTE(whey8tor @ Mar 30 2009, 01:30 PM)

I dunno if any of you had this problem with v1.52 i can read my benq drive it reads all banks from 0-3 and finishes. but when it asks me if the firmware dump was successful and I type Y it just hangs there....... is there any way around it?

Are you sure you are using v1.52 and not v1.51?

v1.51 commonly had that problem...

[1hotjob]

QUOTE

Is it possible to change the color of text in a DOS batch script?

This may help. Please don't go all crazy with the backgrounds!

[keywiz]

Hi,

I have an xecuter connectivity kit v2, can i use it with the 360 modification disc v1.52?

Thanks

keywiz

[whey8tor]

I re downloaded and burned the iso just to make sure it was v1.52 and still hangs after reading.