xboxscene.org forums

Pages: 1 ... 41 42 [43] 44 45 46

Author Topic: TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives  (Read 6224 times)

Simple Fix

  • Archived User
  • Newbie
  • *
  • Posts: 14
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #630 on: April 15, 2009, 12:41:00 AM »

QUOTE(maninjapan @ Apr 13 2009, 06:22 PM) *

Can you post pics of the msinfo32 and also of the edited hex file?


I don't know if your talking to me but I can but will that help with anything. By the "edited hex file" you mean what was edited? I just changed the last 8 bytes of the hddhackr.com program according to the readme.txt that is included with the program.

I have an older Abit KT-600 Mobo with Via 8237 SATA chipset. I am using another computer to do the flashing I am on my Laptop right now so I can't easily get the info you want. I don't see why that would be the problem as I have already flashed several LST, RST, 22UST0 BEVS type drives successfully already using this same computer and programs.

I just ordered a Sil 3114 chipset SATA PCI card and I will try that also.

If I can't get it to work with this board.

I will pay anyone $5 each to flashed my WD1200 - BEVS - 00UST0 drives for me. I have 20 of them. Thats an easy $100 for about 30 minutes of work if anyone is willing to do this.

I will expect you to put up a deposit for the drives I will be sending to you. So you must have some cash. About $700 or $35 for each drive (20 drives x $35 = $700).

I have also flashed them (not these drives others) successfully just by flashing them one by one plugging and unplugging them back in and out one after the other without rebooting. It searches the SATA Ports each time the program is ran. I will also pay anyone $20 if they can solve my problem. No BS either I have a Paypal account and can give it to you in seconds!!

This post has been edited by Simple Fix: Apr 15 2009, 07:45 AM
Logged

Simple Fix

  • Archived User
  • Newbie
  • *
  • Posts: 14
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #631 on: April 16, 2009, 02:49:00 AM »

Nevermind I will just sell them. WD1200BEVS for sale $40 each shipped!! PM if interested.
Logged

Desperados112

  • Archived User
  • Newbie
  • *
  • Posts: 1
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #632 on: April 18, 2009, 04:52:00 PM »

Hello I'm using an HP M8530F with the Nvidia Chipset and I'm having trouble getting hddhackr to see my WD1200BEVS - 00VAT0
I'm pretty sure it uses NForce 710a,720a or 730a

Here is my msinfo32

Name   NVIDIA nForce Serial ATA Controller
Manufacturer   NVIDIA Corporation
Status   OK
PNP Device ID   PCI\VEN_10DE&DEV_0AD8&SUBSYS_2A6E103C&REV_A2\3&267A616A&0&48
I/O Port   0x0000C480-0x0000C487
I/O Port   0x0000C400-0x0000C403
I/O Port   0x0000C080-0x0000C087
I/O Port   0x0000C000-0x0000C003
I/O Port   0x0000BC00-0x0000BC0F
Memory Address   0xF8D76000-0xF8D77FFF
IRQ Channel   IRQ 22
Driver   i:\windows\system32\drivers\nvgts64.sys (10.3.0.42 built by: WinDDK, 164.53 KB (168,480 bytes), 23/02/2009 3:28 PM)
   
Name   NVIDIA nForce RAID Device
Manufacturer   NVIDIA Corporation
Status   OK
PNP Device ID   SCSI\ARRAY&VEN_NVIDIA&PROD_RAID_DISK_20&REV_\4&1996D31A&0&000000
Driver   i:\windows\system32\drivers\nvrd64.sys (10.3.0.42 built by: WinDDK, 163.03 KB (166,944 bytes), 23/02/2009 3:28 PM)
   
Name   SCSI/RAID Host Controller
Manufacturer   (Standard mass storage controllers)
Status   OK
PNP Device ID   ACPI\PNPA000\4&5D18F2DF&1
I/O Port   0x0000FFA0-0x0000FFAF
IRQ Channel   IRQ 9
   
Name   A2BARJCS IDE Controller
Manufacturer   (Standard mass storage controllers)
Status   OK
PNP Device ID   ACPI\PNPA000\4&5D18F2DF&0
I/O Port   0x0000FFE0-0x0000FFEF
IRQ Channel   IRQ 9
   
Name   NVIDIA nForce RAID Controller
Manufacturer   NVIDIA Corporation
Status   OK
PNP Device ID   ACPI\NVRAID20\3&267A616A&0
I/O Port   0x000004D2-0x000004D2
Driver   i:\windows\system32\drivers\nvrd64.sys (10.3.0.42 built by: WinDDK, 163.03 KB (166,944 bytes), 23/02/2009 3:28 PM)

I extracted the Port like it was said in readme and got C4 80 C0 80. I replaced it in hex into my hddhackr so it now looks like this. I took all of my sata drives out when trying to boot from my flash drive to format the WD drive but HddHackr still won't see it. It looks like I'm stuck someone give me a hand pls and u can have this popcorn  pop.gif  . also I have a really retarded bios that won't allow me to force the disk in ide or legacy or something so I can't do that.
Logged

mk360

  • Archived User
  • Newbie
  • *
  • Posts: 1
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #633 on: April 20, 2009, 01:10:00 PM »

Hi
i have a problem  sad.gif
when i type hddhackr -f then i meet this error "information on sector 16 does not match the firmware info"

IPB Image

my original xbox hdd is seagate and new hdd is western digital 1200bevs
and my motherboard chipset is intel
please help me unsure.gif
Logged

dangal

  • Archived User
  • Newbie
  • *
  • Posts: 41
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #634 on: April 28, 2009, 02:45:00 PM »

Q. I get an error when I try to dump hddss.bin from a 120 gb HDD.
A. This version can't dump from an elite drive yet. You'll have to dump sectors 16-22 manually with a tool like winhex, save them as 'hddss.bin' and then continue like normal, with the hddhackr.


if i have a 120gb disc from a elite,i cant dump the bin!!!???
I dont understand how dump manually this sectors?????
the only way i have is found the hddss.bin in the web?
if anybody have a good bin send me a pm please!!!
Logged

dj98hd2

  • Archived User
  • Newbie
  • *
  • Posts: 1
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #635 on: May 06, 2009, 08:35:00 PM »

(IMG:style_emoticons/default/mad.gif) Hey guys, I have a IO port question, Besides painting a big red X on my computer and loading up the shotgun, I can't get this stupid Sil equiped ASUS MB computer with either of my 2 Via 6421 cards to see the BEVS drive with HDDHackr. The Sil chip will see the WD BEVS and everything looks correct until I enter "Y" to flash the firmware to make it compatable with sector 16, I get an error saying "drive not supported, make sure its a SATA WD scorpio BEVS" whch above that error it shows a WDC1200BEVS-22USTO drive. Ive tried both 6421 cards with all different drivers and the IO ports always have a  difference of "F" not "7"like they should. The drive is not bricked yet even after several different tries, but XP still see's it as a good drive even when connected to the Via card that HDDHackr won't use. ? ASUS MB's are not made by MS are they? or is it just the Sil chips that MS makes to screw with everyone.  (IMG:style_emoticons/default/huh.gif)
Logged

AbuseTheElderly

  • Archived User
  • Newbie
  • *
  • Posts: 25
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #636 on: May 13, 2009, 12:57:00 PM »

Hi, I'm using HDDHackr v 0.91 and it seems I am stuck in an endless loop.  I have seen Others with similar problems but none where solved.  When I load up hddhackr it detects my hdd no problem, when i flash it says successful.  Upon reboot none of the info on the hdd was changed,  It STILL reports as a WD!  Tried 2 PCs onboard sata and a via 6421 card in both.  Everything I try is the same result.  the Hdd works fine in windows put data on it, format it and error checked it.  I started a thread but no replys, hoping to get some help here.

Other thread ->  http://forums.xbox-scene.com/index.php?showtopic=684271

I know your busy TheSpecialist, but this seems to be the only issue that doesn't have a fix posted.

This post has been edited by AbuseTheElderly: May 13 2009, 08:00 PM
Logged

TheGlow

  • Archived User
  • Newbie
  • *
  • Posts: 45
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #637 on: May 20, 2009, 11:51:00 AM »

I tried migrating my friends data from a 20gb to a 120.
Everything seemed to work fine, I used his profile online, all was good.
When he brought it home, his main profile wasnt on the selection screen and his other profiles were.
What would cause that?
Logged

JAmerican

  • Archived User
  • Newbie
  • *
  • Posts: 30
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #638 on: May 20, 2009, 12:16:00 PM »

QUOTE(TheGlow @ May 20 2009, 12:43 PM) View Post

I tried migrating my friends data from a 20gb to a 120.
Everything seemed to work fine, I used his profile online, all was good.
When he brought it home, his main profile wasnt on the selection screen and his other profiles were.
What would cause that?


Does he have a memory unit? His profile could have been on his memory unit the whole time.
Logged

FrostyTheSnowman

  • Archived User
  • Hero Member
  • *
  • Posts: 1137
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #639 on: May 20, 2009, 12:33:00 PM »

QUOTE(TheGlow @ May 20 2009, 10:43 AM) View Post

I tried migrating my friends data from a 20gb to a 120.
Everything seemed to work fine, I used his profile online, all was good.
When he brought it home, his main profile wasnt on the selection screen and his other profiles were.
What would cause that?


Your machine has been 'exiled' by Microsoft, like one of mine. (the same thing happened to my little brother's profile when he used it on one of my 360s...)

Meaning, ANY content saved/accessed on a memory unit/HDD by your 360 will ONLY work on your 360, and no other.

So, since your machine is 'exiled' anytime you put any memory unit in your machine and access a profile, that profile will ONLY work on your machine from that point forward, which is why it doesn't show up on his machine anymore.

To confirm that your 360 has been exiled, just put his HDD back on your 360 and I can guarantee that your machine will see the profile just fine, and his won't.

I hope you have a backup of the files from his original 20GB HDD, because the files for the profile on the new 120GB HDD are now locked to your 360. sad.gif

NOTE: Microsoft 'exiling' your 360 is not a ban necessarily, more like a half-ban. Your machine will still work normally online, it just locks down your content to your specific 360.
Logged

TheGlow

  • Archived User
  • Newbie
  • *
  • Posts: 45
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #640 on: May 20, 2009, 02:44:00 PM »

Hmm, thats kind of fruity.
So to further test this if I plug my hdd into my bro in laws 360 (only 1 room away) than none of my profiles should load up either eh?

Also I guess this may be a factor but when I formatted the 120gb in my console it wouldnt let me use my friends serial so I ended up using mine. Then when I made a new save on it to get his deviceid I saw the id was the same as my new 120gb.

Actually I recall my friend saying that profile I made to make a new save didnt load either, he said he got some kind of corruption message. that bites. only odd thing ive done recently was messing around with that gamerpic injector. I guess I shouldnt let people plug into my system...
or let people I dont like login from my system.

And yea, his files are all still intact on his 20gb.
I also had all his content on my pc but I resigned them to the new deviceid.

Do you have to resign anything in this sort of scenario? I can just drag and drop the profile with the saves and theyll work? cuz I see the deviceid would be different. I thought that would make it not work...
Logged

FrostyTheSnowman

  • Archived User
  • Hero Member
  • *
  • Posts: 1137
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #641 on: May 20, 2009, 03:09:00 PM »

Well, I can't comment on the resigning (I haven't tried upgrading my HDD to a BEVS/RST, nor have I resigned anything on the 360), but yes, your profiles will not show up on your brother-in-law's 360 if your 360 is indeed 'exiled'.

My recommendation is to keep your personal 360 completely out of the loop...
Logged

TheGlow

  • Archived User
  • Newbie
  • *
  • Posts: 45
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #642 on: May 20, 2009, 03:28:00 PM »

Yea Frosty, I read up on this here
http://xorloser.com/?p=45

Althought my console id isnt on the list, yet I would guess.

Also I found something interesting. I saw in the post that in a con file, offset 6 is where my consoleid is...
I tested this against some other saves and it looks like this isnt the case for me... anymore.
I loaded up an older Street fighter 4 save from april and my console id is at offset 6, as well as 22F and 36C.
In my current sf4 save, my console id is still at 22F and 36C but I have a different id at offset 6. And ALL my saves now have this diff id on offset 6... even games I know I havent loaded up since April.
any idea what the hell that might mean?
The image of my 20gb I made before my xfer all have my real console id at offset6. weird. maybe side effect of a 120gb drive.. odd even if its the case. i wonder if some resigner I used corrupted them somehow.
but still, Ill assume this is unrelated to the exile

on a side note, what generates the deviceid?
cuz my friends 120gb had the same id as mine. will this cause any trouble for him? the only things I can think of in common were they were both formatted on my console and I used the same hddss.bin
If its the hddss.bin then I dont have to format it on his console since thats the only hddss.bin I have.
if its console linked ill have to format it with his console and copy back his goods.

This post has been edited by TheGlow: May 20 2009, 10:46 PM
Logged

TheGlow

  • Archived User
  • Newbie
  • *
  • Posts: 45
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #643 on: May 20, 2009, 03:53:00 PM »

double post, couldnt edit previous one anymore...

Im gonna go out on a limb and figure I used a somewhat public hddss.bin.
that would generate the same deviceid for anyone using that bin file.
that device id is blacklisted or some such and thats whats causing the consoleid change...

or is all this going over my head?
Logged

FrostyTheSnowman

  • Archived User
  • Hero Member
  • *
  • Posts: 1137
TheSpecialist's HDDHackr v0.91 - Adds Support for WD BEVS-RST Drives
« Reply #644 on: May 20, 2009, 04:13:00 PM »

QUOTE(TheGlow @ May 20 2009, 02:45 PM) View Post

double post, couldnt edit previous one anymore...

Im gonna go out on a limb and figure I used a somewhat public hddss.bin.
that would generate the same deviceid for anyone using that bin file.
that device id is blacklisted or some such and thats whats causing the consoleid change...

or is all this going over my head?


LOL, it might be over your head, but I doubt it, you seem pretty quick to pick up things. smile.gif

My guess is that the change in the ID is related to the HDDSS.BIN file being the same on both drives.

I would recommend just reformatting the new 120GB HDD on your friend's 360, then copying the files over from the original 20GB HDD.

I wish I could provide details on the filesystem structure with the 360 HDD, but I haven't delved into it at all... sad.gif
Logged
Pages: 1 ... 41 42 [43] 44 45 46