Topic: Phoenix On 5530 : Work (Read 657 times)

Chicken Scratch Boy · « **Reply #15 on:** March 15, 2004, 07:22:00 AM »

damn, you guys at guex are awesome, maybe we can get a little cross forum communication going (babel fish sucks at dynamic adresses, so...) perhaps a ppf patch (applyable via ppf-xbox) might work for this type of patch, btw, arnt eeproms legal to move freely, i mean people sell them on the BST forum, so if they were illegal, i'm sure HSD woul dhave put a stop to it a LOOOONG time ago... maybe if you take a eeprom with zeroed keys, you can patch it up withthe correct per xbox data via live info, i'm just thinking, if your newb enough not to check the mfg date when you buy an xbox, you might not be too good at hexing...

Xboxhakur_band · « **Reply #16 on:** March 15, 2004, 08:30:00 AM »

This finding supports my theory from 2 1/2 months ago...
http://forums.maxcon...d=5286#post5286

According to the docs at xbox-linux, disabling debug mode would mean more difficult repairs and manufacturing. Because of that doc, I never actually believed that debug mode had been disabled in newer kernels.
By changing the EEPROM, u r changing the checksum, which "should" force the kernel into debug mode. It may even be enough to simply change the checksum data.

At this point, I would only do this if u have a mod-chip. Until we get more confirmation that it's safe, I'd be very careful.

PC_Arcade · « **Reply #17 on:** March 15, 2004, 09:59:00 AM »

I would (I've got both versions of the flasher), but I'm not 100% sure what to do with them??!!

clogicgmather · « **Reply #18 on:** March 15, 2004, 10:28:00 AM »

same here, happy to try it, got a 5530 kernel and a bootchip if i get into trouble if some clearer instructions were available.
Ive got a file called EEprom_Flasher_Audio_Hack.rar, do i need anything else?

krayzie · « **Reply #19 on:** March 15, 2004, 11:08:00 AM »

This is some awesome news guys. I hope this brings lots of further development on this subject.
Btw wouldn't it be possible to integrate some eeprom patcher within the bootprocess of pbl that will just adjust it temprorarily and change it back when the new bios is loaded.

Grospolina · « **Reply #20 on:** March 15, 2004, 11:36:00 AM »

krayzie, it's not a good idea to write to EEPROM all the time. If power is lost while it's writing (it's not as fast as writing to RAM), then the data could be corrupted and it might kill the box. Also, EEPROM only supports a limited number of writes (typically 10 000 or 100 000 write cycles). After that, it could get worn out. Although it may take a long, long time to get that high, it's still not a great idea to do it.

PC_Arcade · « **Reply #21 on:** March 15, 2004, 11:49:00 AM »

shodanjr_gr · « **Reply #22 on:** March 15, 2004, 12:00:00 PM »

krayzie · « **Reply #23 on:** March 15, 2004, 01:55:00 PM »

Chicken Scratch Boy · « **Reply #24 on:** March 15, 2004, 02:44:00 PM »

yeah krayzie, ava had this problem bunch of people lost thier eeproms, and needed to patch a cromwell... mxm seems to have gotten it down, though

any way, i think that a back, up patch, flash whould work, but i dont know if yoshiro can do this? perhaps someone can relay the idea to him?

krayzie · « **Reply #25 on:** March 15, 2004, 08:04:00 PM »

If now only anyone found out what stops the dashboad of the new 5713 kernel from being downgraded. Couldn't that be an eeprom related problem as well? Well guess that might to much good new in these few days.
Also anyone knows about the mechinstaller fonts that didn't work on the 5530 kernel. Wouldn't it be possible that they work with this eeprom fix. Maybe it was having similar problems.

clogicgmather · « **Reply #26 on:** March 16, 2004, 12:57:00 AM »

o.k im trying to implement this hack, i have the rar named EEprom_Flasher_Audio_Hack. I have some questions.

To extract the eprom do i have to get config magic running without my chip switched on? (ie signed config magic xbe to the audio hack) can i run it with my xbit chip on?

Assuming i do then have my eeprom.bin file i then stick it in with the Eeprom.exe, Patcher_Eeprom_Yosh.bat and image.bin

What are these files doing? does image.bin contain the patch code and some sort of new eeprom file is produced as a result of running patcher_eeprom_yosh.bat

Assuming it does produce some modified eeprom, i just flash this back with config magic and all is fine and dandy?

and finally will this allow me to use the hacked mech assault fonts?

Ive got a mate whos fully french/english speaking, was gonna hook up with him this evening to see if any of the posts on guex provide some answers, will post any translations we make as well.

Guy

legueux · « **Reply #27 on:** March 16, 2004, 02:38:00 AM »

Please, until we release a complete solution (we're working hard on actually) you must be very prudent because we don't want to be responsible if someone crash his Xbox.

The first solution (hexa edit + patcher) is not validated, Yoshihiro have just exposed the solution.

We are trying to make an easy solution to patch Eeprom and we must make a lot of tests before to release something.

krayzie · « **Reply #28 on:** March 16, 2004, 05:09:00 AM »

I'm sure the patchin of the eeprom leaves the hdd key alone.

Chicken Scratch Boy · « **Reply #29 on:** March 16, 2004, 05:32:00 AM »

rofl, if we took blank eeproms from liveinfo and filled them in, whould it work? cause i assume that they dont have the 5530 patch in them...

Author Topic: Phoenix On 5530 : Work (Read 657 times)