xboxscene.org forums

OG Xbox Forums => No-Modchip Hacks (exploits) => XBE Exploits => Topic started by: MpDay on August 31, 2004, 12:27:00 PM

Title: 5659 Exploit Also Works For 5713 ?
Post by: MpDay on August 31, 2004, 12:27:00 PM

Hi,

I have modded several Xbox 1.5 dash: 5659 models, using the font exploit.
After hot swapping the harddisk, I uploaded the fonts, BusyBox Xbox Linux, raincoat with Xecuter bios, and a downgraded dash... don't know which version, but the mapname is 'xboxdashdata.1012A700'.

After rebooting, the font exploit crashed the downgraded dash and then starts BusyBox Linux, which opens a telnet client at port 23.
Connecting to the xbox, using telnet on my laptop, I have flashed the BIOS with the Xecuter bios.
Off cource, this is only possible after soldering the 3 open pins on the motherboard, in order to make the bios writeable.

Well, some of you guys will understand my story, and the workaroud.
Here's my question:

CAN I do the EXACT same trick with a 5713 Dash version Xbox??? With the EXACT same software I'm using now???

Thank you,
MP

Title: 5659 Exploit Also Works For 5713 ?
Post by: anjilslaire on August 31, 2004, 12:32:00 PM

Depends. The dash version is irrevelant (to a point). It's the kernel version. The new 1.6 box tsop is not writeable

Title: 5659 Exploit Also Works For 5713 ?
Post by: krayzie on August 31, 2004, 12:38:00 PM

you cannot downgrade the dashboard on a 5713 kernel.

Title: 5659 Exploit Also Works For 5713 ?
Post by: MpDay on August 31, 2004, 05:08:00 PM

So the 5713 kernel has this new 'protection feature' that it will first check the dashboard version, before it continues the boot procedure, right?

Damn... M$ finally came up with a 'non-modchip exploit' protection i guess.
Checking the dashboard version is very logical and easy... but can it be manipulated?

Title: 5659 Exploit Also Works For 5713 ?
Post by: eh. on August 31, 2004, 05:32:00 PM

The kernel's checking the certificate date of dashboard .xbe's and enforcing that they can be no earlier than 5659's.  (This has been circumvented by using non-dashboard .xbe's as bootstraps instead eh. ;) )