Jump to content


Photo

What Modchip Is?


  • Please log in to reply
16 replies to this topic

#1 JackFive

JackFive

    X-S Enthusiast

  • Members
  • 12 posts

Posted 07 September 2009 - 10:35 AM

Hi, I would know my modchip. Anyone can tell me what kind of model is?

The photo:
http://img44.imagesh...i/49921660.jpg/
http://img513.images...i/65329986.jpg/
http://img35.imagesh...i/36153439.jpg/

I start the mod whit a power's pressure of 3-4 sec.
When the Xbox starts, appear the word Xecuter2 under the word XBOX.

My XBOX is V.1.1

Whit X-wizard 3.1 Plus I have taken this information:

Xbox Bios Checker 5.0:
Chip Type: LPC based (SST49LF020)
Bios: Xecuter2 4977
Bios MD5 Hash: F51878CA4506080394428173B62AB1EA

I have taken the bios (with a backup of EvoX) and controlled with XBtool 1.0.23a:
The MD5 is: 0x92987e26edd5833921c9b0e539ea091e
Also in the evox.ini there is this hash in the "Current = ..."

I tried to flash the bios (because I installed 320Gb Hard Disk) but I can't. I tried to flash with "x2 4981.06",0xca25c9b3721da8c96c4770515dbcda07 but nothing.
In particular remains the word Erasing for much time but it does succeed nothing.

Can you help me! Thanks a lot.

Edited by JackFive, 07 September 2009 - 10:39 AM.


#2 JackFive

JackFive

    X-S Enthusiast

  • Members
  • 12 posts

Posted 07 September 2009 - 03:30 PM

I tried to flash the bios with the Dashboard Avalaunch and the program FlashX 1.2.

When I open the program FlashX, appear a error
No X2 found or chip protected!

How I unprotected the chip?

#3 Heimdall

Heimdall

    X-S Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 5,749 posts
  • Location:UK
  • Xbox Version:v1.4
  • 360 version:v4.0 (jasper)

Posted 07 September 2009 - 04:27 PM

It's not an Xecuter2 chip, so FlashX won't work. The "Xecuter 2" shown under the Xbox logo is from the X2.4977 BIOS, not from the chip.

I don't recognise the mod, but as the flash chip is an SST 49LF020 make sure your evox.ini contains the line:

Flash = 0xbf61,"SST 49LF020",0x40000

#4 JackFive

JackFive

    X-S Enthusiast

  • Members
  • 12 posts

Posted 07 September 2009 - 05:13 PM

QUOTE(Heimdall @ Sep 7 2009, 05:27 PM) View Post

make sure your evox.ini contains the line:

Flash = 0xbf61,"SST 49LF020",0x40000


Yes contains it.
Now i don't know what am I doing. I bought this xbox 2 years ago and there was that Bios yet.

#5 Alex548

Alex548

    X-S Knowledgebase

  • Head Moderators
  • PipPipPipPipPipPipPipPip
  • 4,411 posts
  • Gender:Male
  • Location:Your mom's house
  • Xbox Version:v1.0
  • 360 version:v1 (xenon)

Posted 07 September 2009 - 10:15 PM

Edit your new BIOS to your liking, then reflash using the EvolutionX dashboard.

From the looks of it, you'll be using a 256k BIOS.

#6 JackFive

JackFive

    X-S Enthusiast

  • Members
  • 12 posts

Posted 07 September 2009 - 10:57 PM

This is my evox.ini
CODE

[Misc]

AutoLaunchGames    = No
AutoLaunchDVD    = No
DVDPlayer    = "f:\apps\default.xbe"
AutoLaunchAudio    = No
#AudioPlayer    = "c:\xboxdash.xbe"
MSDashBoard    = "c:\xboxdash.xbe"
UseFDrive    = Yes
UseGDrive    = Yes
SkinName    = Original
#SkinName    = RuDeDuDe2
UseItems    = No
ScreenSaver    = 5
Fahrenheit    = No
ShadeLevel    = 90
EnableSMART    = Yes
HDD_Temp_ID    = 194
ChameleonLed    = 15
TSR_Type    = 0
IGR        = No
GameRegion    = 0

[Network]

SetupNetwork    = Yes
StaticIP    = Yes
Ip        = 192.168.0.3
Subnetmask    = 255.255.255.0
Defaultgateway    = 192.168.0.1
DNS1        = 213.205.32.70
DNS2        = 213.205.36.70
SetupDelay    = 0
SkipIfNoLink    = No

[Clock]

JumpToMsDash    = No
JumpIfNoLink    = Yes
Use24        = Yes
SwapDate    = No
SNTP_Server    = 0.0.0.0

[FTP]

Enable        = Yes
Password    = xbox

[Telnet]

Enable        = Yes

[RDTOOLS]

Enable        = Yes
Name        = XBOX_V1.0

[BIOS]

ROM        = "X2 4977",0x92987e26edd5833921c9b0e539ea091e
ROM        = "X2 4981.06",0xca25c9b3721da8c96c4770515dbcda07
#
Flash        = 0xbf61,"SST - 49LF020",0x40000
Current        = 0x92987e26edd5833921c9b0e539ea091e

[Skin_Original]

#
# <Time>   =
# <IP>     =
# <Name>
# <Version>
# <CD>
# <BIOSVer>
# <KernelVer>
# <RDName>
# <SpaceC>
# <SpaceE>
# <SpaceF>
# <SpaceX>
# <SpaceY>
# <SpaceZ>
#
Text    =       30,37,0.5,0x000000,0,"<Time>"
Text    =       28,39,0.5,0x808080,0,"<Time>"
Text    =       620,420,0.5,0x000000,1,"<Name> V<Version>"
Text    =       618,422,0.5,0x808080,1,"<Name> V<Version>"
Text    =       620,37,0.5,0x000000,1,"<CD>"
Text    =       618,39,0.5,0x808080,1,"<CD>"
Text    =       30,420,0.5,0x000000,0,"RD Name : <RDName>"
Text    =       28,422,0.5,0x808080,0,"RD Name : <RDName>"
LogoType=    0

[Menu]

Section "Root"
{
    Item "Launch DVD",ID_Launch_DVD
    Item "Trainers",ID_trainer
    Item "MS Dashboard",ID_MS_Dash
    Item "Reboot",ID_Quick_Reboot
#    Item "Power Cycle",ID_Full_Reboot
    Item "Power Off",ID_Power_Off
#    Item "Lock Harddisk",@210
#    Item "Unlock Harddisk",@211
    Section "System Utils"
    {
        Item "Settings",ID_Settings
        Item "Flash BIOS",ID_Flash_Bios
        Item "Backup",ID_Backup
        Item "Skins",ID_Skins
    }
    Section  "Launch Menu"
    {
        Section "Games"
        {
            AutoAddItem "e:\games\"
            AutoAddItem "f:\games\"
            SortAll
        }
        Section "Apps"
        {
            AutoAddItem "e:\apps\"
            AutoAddItem "f:\apps\"
            SortAll
        }
    }
}

[Action_10]

LogFile          = "f:\lock.log"
Info "This function will lock your XBOX Harddisk"
Warning "You will now lock your XBOX harddisk and will be able"
Warning "to boot from an original XBOX bios"
#
hddlockenable

[Action_11]

LogFile          = "f:\unlock.log"
Info "This function will unlock your XBOX Harddisk"
Warning "You will now unlock your XBOX harddisk and will not be able"
Warning "to boot from an original XBOX bios"
#


1. I tried to flash the bios using the tools of EvolutionX Build 3935, but the flash is still to "Erase" .

2. I tried to flash the bios using the program XFlash Build 2 (not FlashX 1.2), this is the final report:
Checking Flash ID
Flash Manufacturer = bf
Flash Device code = 61
Started ERASE Cycle, takes 5-10 Seconds
Starting Programming
Starting ProgramDevice() - Flash VerifyFailure at address ff00007d
Aborting ProgramDevice() - Wrote 14, Read 0d
Programming Failed!!

#7 JackFive

JackFive

    X-S Enthusiast

  • Members
  • 12 posts

Posted 08 September 2009 - 11:25 AM

Would you want any information about xbox for help me?

I think there is a protection in the chip, but how I remove it?

However I use the 256Kb bios yet.

#8 Heimdall

Heimdall

    X-S Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 5,749 posts
  • Location:UK
  • Xbox Version:v1.4
  • 360 version:v4.0 (jasper)

Posted 08 September 2009 - 11:42 AM

I'd guess that your chip is broken:

QUOTE
Starting ProgramDevice() - Flash VerifyFailure at address ff00007d


If Evox won't flash it, and XFlash won't flash it, then you're probably out of luck. It might be worth trying a Raincoat flasher like Eurasia 1.3, just for completeness.

#9 JackFive

JackFive

    X-S Enthusiast

  • Members
  • 12 posts

Posted 08 September 2009 - 12:32 PM

QUOTE(Heimdall @ Sep 8 2009, 12:42 PM) View Post

I'd guess that your chip is broken:
If Evox won't flash it, and XFlash won't flash it, then you're probably out of luck. It might be worth trying a Raincoat flasher like Eurasia 1.3, just for completeness.


Also the Eurasia 1.3 report an ERASE ERROR sad.gif

But isn't there a possibility of a write-protection? This is my last hope!
However there aren't switch in the chip that can remove the protection sad.gif

Edited by JackFive, 08 September 2009 - 12:50 PM.


#10 Heimdall

Heimdall

    X-S Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 5,749 posts
  • Location:UK
  • Xbox Version:v1.4
  • 360 version:v4.0 (jasper)

Posted 08 September 2009 - 02:05 PM

If it was write protected you'd get an error saying "flash unwriteable" or something similar.

As it seems to be unflashable, the easiest way for you to get LBA48 support would be to use Phoenix BIOS Loader (PBL) to load a different BIOS. Have a look at metoo-m8plus-v1.4.1.zip (from the usual places).

To use it, edit the PBL BIOS ROM (Metoo-M8plus_16-06.bin) with evtool, and change the name of the first dash to something other than evoxdash.xbe - unleashx.xbe would be a good choice. Rename the PBL default.xbe to evoxdash.xbe. Then, rename your current dashboard unleashx.xbe, and replace your current dashboard with PBL evoxdash.xbe, boot.cfg, and your edited Metoo-M8plus_16-06.bin.

Once you get it working you can experiment with other Boot From Media (BFM) BIOSes - there's a load of them available at the usual places. I'd recommend iND-BIOS.5003.

BUT, before you start, make sure you can boot a rescue disc, like Frosty's Rescue Disc, so that if you misconfigure PBL or the BIOS you can still recover. smile.gif

#11 JackFive

JackFive

    X-S Enthusiast

  • Members
  • 12 posts

Posted 08 September 2009 - 03:53 PM

Sorry but I don't understand this instruction. Tell me if these are correct:

1. I open evtool and edit Metoo-M8plus_16-06.bin
2. In particular I must change the name of the first dash (evoxdash.xbe) to unleashx.xbe
3. I rename the PBL default.xbe to evoxdash.xbe
4. I rename my current dashboard (evoxdash.xbe that is in the C of XBOX) to unleashx.xbe
5. I move PBL evoxdash.xbe, boot.cfg, and my edited Metoo-M8plus_16-06.bin to the C of XBOX

And now?

#12 Heimdall

Heimdall

    X-S Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 5,749 posts
  • Location:UK
  • Xbox Version:v1.4
  • 360 version:v4.0 (jasper)

Posted 08 September 2009 - 04:05 PM

That's correct. Once you've done that you can reboot the Xbox.

If you want to test it first, here's an alternative process:

1. Open evtool and edit Metoo-M8plus_16-06.bin
2. Change the name of the first dash (evoxdash.xbe) to unleashx.xbe
3. Rename the PBL default.xbe to evoxdash.xbe
4. Copy the current dashboard (evoxdash.xbe that is in the C of XBOX) to C:\unleashx.xbe
5. Move PBL evoxdash.xbe, boot.cfg, and the edited Metoo-M8plus_16-06.bin to C:\temp\ on the Xbox
6. Use file manager to launch C:\temp\evoxdash.xbe

Once it works:
7. Move PBL evoxdash.xbe, boot.cfg, and the edited Metoo-M8plus_16-06.bin to C:\ on the Xbox

#13 JackFive

JackFive

    X-S Enthusiast

  • Members
  • 12 posts

Posted 08 September 2009 - 04:29 PM

Ok the Xbox starts and when I go to the Settings I have:

Bios Version: X2 4977
Kernel Version: 1.00.5838.01 (before it was 1.00.4977.01)

Ok now? There is other modification to do?

#14 Heimdall

Heimdall

    X-S Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 5,749 posts
  • Location:UK
  • Xbox Version:v1.4
  • 360 version:v4.0 (jasper)

Posted 08 September 2009 - 04:42 PM

I think that's done - your Xbox is now running Evox M8+ as its BIOS. You should now be able to set up your 320GB disk. Once the disk is set up with Slayers, use XBPartitioner 1.1 to format the disk, to make sure you get the right cluster sizes on the F/G partitions.

#15 JackFive

JackFive

    X-S Enthusiast

  • Members
  • 12 posts

Posted 08 September 2009 - 04:55 PM

QUOTE(Heimdall @ Sep 8 2009, 05:42 PM) View Post

I think that's done - your Xbox is now running Evox M8+ as its BIOS. You should now be able to set up your 320GB disk. Once the disk is set up with Slayers, use XBPartitioner 1.1 to format the disk, to make sure you get the right cluster sizes on the F/G partitions.


Yesss, RUN perfectly!!

Thanks a lot Heimdall beerchug.gif beerchug.gif

OMG it's fantastic, thanks thanks thanks




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users