Zum Inhalt springen

Hallo, Gast
Du musst dich registrieren bevor du auf unserer Seite Beiträge schreiben kannst.

Benutzername
  

Passwort
  





Durchsuche Foren

(Erweiterte Suche)

Foren-Statistiken
» Mitglieder: 56,835
» Neuestes Mitglied: JamesOvege
» Foren-Themen: 29,883
» Foren-Beiträge: 205,642

Komplettstatistiken

Benutzer Online
Momentan sind 531 Benutzer online
» 0 Mitglieder
» 530 Gäste
Applebot

Aktive Themen
Kinect 2.0: Beim Spielen ...
Forum: XBOne User News
Letzter Beitrag: 1win_lot
Gestern, 22:38
» Antworten: 18
» Ansichten: 972
Xbox 360 slim mfr 13-08-2...
Forum: XB360 Themes
Letzter Beitrag: Flori90
02.11.2026, 00:59
» Antworten: 2
» Ansichten: 5,962
Weiß jemand, welche Tätig...
Forum: Allgemeines
Letzter Beitrag: geral
01.11.2026, 05:28
» Antworten: 2
» Ansichten: 179
Hat jemand gute Erfahrung...
Forum: Allgemeines
Letzter Beitrag: geral
01.11.2026, 05:20
» Antworten: 2
» Ansichten: 95
Neue Spiele für die Konso...
Forum: XBOne News
Letzter Beitrag: Flori90
30.10.2026, 21:14
» Antworten: 9
» Ansichten: 6,096
Sind Moderatoren aktiv
Forum: Glückwünsche & Uservorstellungen
Letzter Beitrag: Flori90
30.10.2026, 06:50
» Antworten: 2
» Ansichten: 152
The Bradford Exchange
Forum: Glückwünsche & Uservorstellungen
Letzter Beitrag: Flori90
30.10.2026, 00:57
» Antworten: 2
» Ansichten: 715
Lohnt sich die ps5 pro ?
Forum: Xbox Series X/S – Konsole & Einrichtung
Letzter Beitrag: Flori90
30.10.2026, 00:41
» Antworten: 0
» Ansichten: 109
Game Over...... :-(
Forum: Board News
Letzter Beitrag: Flori90
30.10.2026, 00:21
» Antworten: 9
» Ansichten: 13,910
Home Video Editing
Forum: The Funny Side of Life
Letzter Beitrag: gigiwu
18.06.2023, 09:29
» Antworten: 14
» Ansichten: 995

 
  Brennen geht nicht - HILFE !!!
Geschrieben von: Jaskiniowiec - 28.08.2011, 16:25 - Forum: Fragen zu Brennern & Rohlingen - Antworten (7)

Kann keine DVD brennen!
Habe Brenner NEC DVD RW ND-3530A, benutze ImgBurn, Rohlinge Verbatim DVD+R DL.
Habe schon 4 DVDs verbrannt. Gebrannt wurde mit 2,4X und bei 6% werden diese Fehler gezeigt:
http://img263.imageshack.us/img263/8233/brennen.png
http://img33.imageshack.us/img33/9673/brennen2.jpg
http://img822.imageshack.us/img822/8720/brennen3.jpg
Kann es sein, dass mein Brenner zu alt oder nicht geeignet ist?

Drucke diesen Beitrag

  DVD's werden mit Xecuter PCB nicht erkannt
Geschrieben von: Milan82 - 28.08.2011, 16:13 - Forum: Fragen zur XB360 Konsole - Antworten (14)

hi,

ein eigentlich korrekt eingebautes xecuter pcb im 0272er-laufwerk liest keine spiele. habe eine slim, das alte pcb auf stock geflashed, dann dash aufs neuste upgedated, dann xecuter pcb eingebaut und dann auf lt 1.91 geflashed. wobei ich die xecuter platine geflashed habe, wo sie noch nicht im laufwerk verbaut war.

nun folgendes: nachdem ich die xecuter pcb verbaut habe und ich ein spiel einlege, surrt das laufwerk kurz und dann steht im xbox menü nur "lade öffnen", obwohl ein spiel drin ist. eigentlich müsste das ein defekt am laser sein. aber der laser hat vorher tadellos funktioniert und beim einbau wurde er nicht beschädigt.

muss ich vielleicht das laufwerk noch mal flashen, wo jetzt die xecuter eingebaut ist? beim jf ist auch kein fehler zu sehen..

danke euch schon mal Smile

Drucke diesen Beitrag

  XBOX 360 SPINT BITTE HELFT MIR
Geschrieben von: electrostar40 - 28.08.2011, 14:47 - Forum: Sonstige Fragen rund um die XB360 Hardware - Antworten (11)

hallo bin neu hier also keine erfarung im forum wollte mal wiesen wie ich die probleme von meine xbox beheben kann oder was das ist also jetz komm ich zur sache

1.die xbox hängt sich wehrend dem spielen auf und gefriert also stand bild
2.die xbox wird sehr heiß also CPU und GPU habe auch schon frische wärmeleitpaste drauf aber bringt trotzdem nichts
3.lüfter ist sehr langsam also geschwindigkeit ist nicht so wie sie sein soll
4.die xbox ging vor der neuen System aktualisierung ging sie ohne probleme seit der System aktualisierung spiend die xbox total rum hatte auch schon 8 mal ROD aber dann hab ich sie aus gemacht und dann ging sie wieder Huh sogar den fehler E74 hatte sie auch schon dann habe ich die xbox ausgemacht und dann ging sie wieder Huh was sehr komisch ist

bitte um schnelle hilfe

Drucke diesen Beitrag

  Reset Glitch Hack
Geschrieben von: xXRobinhoXx - 28.08.2011, 13:51 - Forum: Other Tools - Keine Antworten

Zitat:**********************************
* The Xbox 360 reset glitch hack *
**********************************

Introduction / some important facts
===================================

tmbinc said it himself, software based approaches of running unsigned code on the 360 mostly don't work, it was designed to be secure from a software point of view.

The processor starts running code from ROM (1bl) , which then starts loading a RSA signed and RC4 crypted piece of code from NAND (CB).

CB then initialises the processor security engine, its task will be to do real time encryption and hash check of physical DRAM memory. From what we found, it's using AES128 for crypto and strong (Toeplitz ?) hashing. The crypto is different each boot because it is seeded at least from:
- A hash of the entire fuseset.
- The timebase counter value.
- A truly random value that comes from the hardware random number generator the processor embeds. on fats, that RNG could be electronically deactivated, but there's a check for "apparent randomness" (merely a count of 1 bits) in CB, it just waits for a seemingly proper random number.

CB can then run some kind of simple bytecode based software engine whose task will mainly be to initialise DRAM, CB can then load the next bootloader (CD) from NAND into it, and run it.

Basically, CD will load a base kernel from NAND, patch it and run it.

That kernel contains a small privileged piece of code (hypervisor), when the console runs, this is the only code that would have enough rights to run unsigned code.
In kernel versions 4532/4548, a critical flaw in it appeared, and all known 360 hacks needed to run one of those kernels and exploit that flaw to run unsigned code.
On current 360s, CD contains a hash of those 2 kernels and will stop the boot process if you try to load them.
The hypervisor is a relatively small piece of code to check for flaws and apparently no newer ones has any flaws that could allow running unsigned code.

On the other hand, tmbinc said the 360 wasn't designed to withstand certain hardware attacks such as the timing attack and "glitching".

Glitching here is basically the process of triggering processor bugs by electronical means.

This is the way we used to be able to run unsigned code.

The reset glitch in a few words
===============================

We found that by sending a tiny reset pulse to the processor while it is slowed down does not reset it but instead changes the way the code runs, it seems it's very efficient at making bootloaders memcmp functions always return "no differences". memcmp is often used to check the next bootloader SHA hash against a stored one, allowing it to run if they are the same. So we can put a bootloader that would fail hash check in NAND, glitch the previous one and that bootloader will run, allowing almost any code to run.

Details for the fat hack
========================

On fats, the bootloader we glitch is CB, so we can run the CD we want.

cjak found that by asserting the CPU_PLL_BYPASS signal, the CPU clock is slowed down a lot, there's a test point on the motherboard that's a fraction of CPU speed, it's 200Mhz when the dash runs, 66.6Mhz when the console boots, and 520Khz when that signal is asserted.

So it goes like that:
- We assert CPU_PLL_BYPASS around POST code 36 (hex).
- We wait for POST 39 start (POST 39 is the memcmp between stored hash and image hash), and start a counter.
- When that counter has reached a precise value (it's often around 62% of entire POST 39 length), we send a 100ns pulse on CPU_RESET.
- We wait some time and then we deassert CPU_PLL_BYPASS.
- The cpu speed goes back to normal, and with a bit of luck, instead of getting POST error AD, the boot process continues and CB runs our custom CD.

The NAND contains a zero-paired CB, our payload in a custom CD, and a modified SMC image.
A glitch being unreliable by nature, we use a modified SMC image that reboots infinitely (ie stock images reboot 5 times and then go RROD) until the console has booted properly.
In most cases, the glitch succeeds in less than 30 seconds from power on that way.

Details for the slim hack
=========================

The bootloader we glitch is CB_A, so we can run the CB_B we want.

On slims, we weren't able to find a motherboard track for CPU_PLL_BYPASS.
Our first idea was to remove the 27Mhz master 360 crystal and generate our own clock instead but it was a difficult modification and it didn't yield good results.
We then looked for other ways to slow the CPU clock down and found that the HANA chip had configurable PLL registers for the 100Mhz clock that feeds CPU and GPU differential pairs.
Apparently those registers are written by the SMC through an I2C bus.
I2C bus can be freely accessed, it's even available on a header (J2C3).
So the HANA chip will now become our weapon of choice to slow the CPU down (sorry tmbinc, you can't always be right, it isn't boring and it does sit on an interesting bus Wink

So it goes like that:
- We send an i2c command to the HANA to slow down the CPU at POST code D8 .
- We wait for POST DA start (POST DA is the memcmp between stored hash and image hash), and start a counter.
- When that counter has reached a precise value, we send a 20ns pulse on CPU_RESET.
- We wait some time and then we send an i2c command to the HANA to restore regular CPU clock.
- The cpu speed goes back to normal, and with a bit of luck, instead of getting POST error F2, the boot process continues and CB_A runs our custom CB_B.

When CB_B starts, DRAM isn't initialised so we chose to only apply a few patches to it so that it can run any CD, the patches are:
- Always activate zero-paired mode, so that we can use a modified SMC image.
- Don't decrypt CD, instead expect a plaintext CD in NAND.
- Don't stop the boot process if CD hash isn't good.

CB_B is RC4 crypted, the key comes from the CPU key, so how do we patch CB_B without knowing the CPU key?
RC4 is basically:
crypted = plaintext xor pseudo-random-keystream
So if we know plaintext and crypted, we can get the keystream, and with the keystream, we can encrypt our own code. It goes like that:
guessed-pseudo-random-keystream = crypted xor plaintext
new-crypted = guessed-pseudo-random-keystream xor plaintext-patch
You could think there's a chicken and egg problem, how did we get plaintext in the first place?
Easy: we had plaintext CBs from fat consoles, and we thought the first few bytes of code would be the same as the new CB_B, so we could encrypt a tiny piece of code to dump the CPU key and decrypt CB_B!

The NAND contains CB_A, a patched CB_B, our payload in a custom plaintext CD, and a modified SMC image.
The SMC image is modified to have infinite reboot, and to prevent it from periodically sending I2C commands while we send ours.

Now, maybe you haven't realised yet, but CB_A contains no checks on revocation fuses, so it's an unpatchable hack !

Caveats
=======

Nothing is ever perfect, so there are a few caveats to that hack:
- Even in the glitch we found is pretty reliable (25% success rate per try on average), it can take up to a few minutes to boot to unsigned code.
- That success rate seems to depend on something like the hash of the modified bootloader we want to run (CD for fats and CB_B for slims).
- It requires precise and fast hardware to be able to send the reset pulse.

Our current implementation
==========================

We used a Xilinx CoolRunner II CPLD (xc2c64a) board, because it's fast, precise, updatable, cheap and can work with 2 different voltage levels at the same time.
We use the 48Mhz standby clock from the 360 for the glitch counter. For the slim hack, the counter even runs at 96Mhz (incremented on rising and falling edges of clock)
The cpld code is written in VHDL.
We need it to be aware of the current POST code, our first implementations used the whole 8 bits POST port for this, but we are now able to detect the changes of only 1 POST bit, making wiring easier.

Conclusion
==========

We tried not to include any MS copyrighted code in the released hack tools.
The purpose of this hack is to run Xell and other free software, I (GliGli) did NOT do it to promote piracy or anything related, I just want to be able to do whatever I want with the hardware I bought, including running my own native code on it.

Credits
=======

GliGli, Tiros: Reverse engineering and hack development.
cOz: Reverse engineering, beta testing.
Razkar, tuxuser: beta testing.
cjak, Redline99, SeventhSon, tmbinc, anyone I forgot... : Prior reverse engineering and/or hacking work on the 360.


.rar   reset_glitch_hack_v1.0.rar (Größe: 2.56 MB / Downloads: 82)

Drucke diesen Beitrag

  Reset Glitch Hack [UPDATE#1)
Geschrieben von: xXRobinhoXx - 28.08.2011, 13:49 - Forum: XB360 User News - Antworten (77)

Zitat:**********************************
* The Xbox 360 reset glitch hack *
**********************************

Introduction / some important facts
===================================

tmbinc said it himself, software based approaches of running unsigned code on the 360 mostly don't work, it was designed to be secure from a software point of view.

The processor starts running code from ROM (1bl) , which then starts loading a RSA signed and RC4 crypted piece of code from NAND (CB).

CB then initialises the processor security engine, its task will be to do real time encryption and hash check of physical DRAM memory. From what we found, it's using AES128 for crypto and strong (Toeplitz ?) hashing. The crypto is different each boot because it is seeded at least from:
- A hash of the entire fuseset.
- The timebase counter value.
- A truly random value that comes from the hardware random number generator the processor embeds. on fats, that RNG could be electronically deactivated, but there's a check for "apparent randomness" (merely a count of 1 bits) in CB, it just waits for a seemingly proper random number.

CB can then run some kind of simple bytecode based software engine whose task will mainly be to initialise DRAM, CB can then load the next bootloader (CD) from NAND into it, and run it.

Basically, CD will load a base kernel from NAND, patch it and run it.

That kernel contains a small privileged piece of code (hypervisor), when the console runs, this is the only code that would have enough rights to run unsigned code.
In kernel versions 4532/4548, a critical flaw in it appeared, and all known 360 hacks needed to run one of those kernels and exploit that flaw to run unsigned code.
On current 360s, CD contains a hash of those 2 kernels and will stop the boot process if you try to load them.
The hypervisor is a relatively small piece of code to check for flaws and apparently no newer ones has any flaws that could allow running unsigned code.

On the other hand, tmbinc said the 360 wasn't designed to withstand certain hardware attacks such as the timing attack and "glitching".

Glitching here is basically the process of triggering processor bugs by electronical means.

This is the way we used to be able to run unsigned code.

The reset glitch in a few words
===============================

We found that by sending a tiny reset pulse to the processor while it is slowed down does not reset it but instead changes the way the code runs, it seems it's very efficient at making bootloaders memcmp functions always return "no differences". memcmp is often used to check the next bootloader SHA hash against a stored one, allowing it to run if they are the same. So we can put a bootloader that would fail hash check in NAND, glitch the previous one and that bootloader will run, allowing almost any code to run.

Details for the fat hack
========================

On fats, the bootloader we glitch is CB, so we can run the CD we want.

cjak found that by asserting the CPU_PLL_BYPASS signal, the CPU clock is slowed down a lot, there's a test point on the motherboard that's a fraction of CPU speed, it's 200Mhz when the dash runs, 66.6Mhz when the console boots, and 520Khz when that signal is asserted.

So it goes like that:
- We assert CPU_PLL_BYPASS around POST code 36 (hex).
- We wait for POST 39 start (POST 39 is the memcmp between stored hash and image hash), and start a counter.
- When that counter has reached a precise value (it's often around 62% of entire POST 39 length), we send a 100ns pulse on CPU_RESET.
- We wait some time and then we deassert CPU_PLL_BYPASS.
- The cpu speed goes back to normal, and with a bit of luck, instead of getting POST error AD, the boot process continues and CB runs our custom CD.

The NAND contains a zero-paired CB, our payload in a custom CD, and a modified SMC image.
A glitch being unreliable by nature, we use a modified SMC image that reboots infinitely (ie stock images reboot 5 times and then go RROD) until the console has booted properly.
In most cases, the glitch succeeds in less than 30 seconds from power on that way.

Details for the slim hack
=========================

The bootloader we glitch is CB_A, so we can run the CB_B we want.

On slims, we weren't able to find a motherboard track for CPU_PLL_BYPASS.
Our first idea was to remove the 27Mhz master 360 crystal and generate our own clock instead but it was a difficult modification and it didn't yield good results.
We then looked for other ways to slow the CPU clock down and found that the HANA chip had configurable PLL registers for the 100Mhz clock that feeds CPU and GPU differential pairs.
Apparently those registers are written by the SMC through an I2C bus.
I2C bus can be freely accessed, it's even available on a header (J2C3).
So the HANA chip will now become our weapon of choice to slow the CPU down (sorry tmbinc, you can't always be right, it isn't boring and it does sit on an interesting bus Wink

So it goes like that:
- We send an i2c command to the HANA to slow down the CPU at POST code D8 .
- We wait for POST DA start (POST DA is the memcmp between stored hash and image hash), and start a counter.
- When that counter has reached a precise value, we send a 20ns pulse on CPU_RESET.
- We wait some time and then we send an i2c command to the HANA to restore regular CPU clock.
- The cpu speed goes back to normal, and with a bit of luck, instead of getting POST error F2, the boot process continues and CB_A runs our custom CB_B.

When CB_B starts, DRAM isn't initialised so we chose to only apply a few patches to it so that it can run any CD, the patches are:
- Always activate zero-paired mode, so that we can use a modified SMC image.
- Don't decrypt CD, instead expect a plaintext CD in NAND.
- Don't stop the boot process if CD hash isn't good.

CB_B is RC4 crypted, the key comes from the CPU key, so how do we patch CB_B without knowing the CPU key?
RC4 is basically:
crypted = plaintext xor pseudo-random-keystream
So if we know plaintext and crypted, we can get the keystream, and with the keystream, we can encrypt our own code. It goes like that:
guessed-pseudo-random-keystream = crypted xor plaintext
new-crypted = guessed-pseudo-random-keystream xor plaintext-patch
You could think there's a chicken and egg problem, how did we get plaintext in the first place?
Easy: we had plaintext CBs from fat consoles, and we thought the first few bytes of code would be the same as the new CB_B, so we could encrypt a tiny piece of code to dump the CPU key and decrypt CB_B!

The NAND contains CB_A, a patched CB_B, our payload in a custom plaintext CD, and a modified SMC image.
The SMC image is modified to have infinite reboot, and to prevent it from periodically sending I2C commands while we send ours.

Now, maybe you haven't realised yet, but CB_A contains no checks on revocation fuses, so it's an unpatchable hack !

Caveats
=======

Nothing is ever perfect, so there are a few caveats to that hack:
- Even in the glitch we found is pretty reliable (25% success rate per try on average), it can take up to a few minutes to boot to unsigned code.
- That success rate seems to depend on something like the hash of the modified bootloader we want to run (CD for fats and CB_B for slims).
- It requires precise and fast hardware to be able to send the reset pulse.

Our current implementation
==========================

We used a Xilinx CoolRunner II CPLD (xc2c64a) board, because it's fast, precise, updatable, cheap and can work with 2 different voltage levels at the same time.
We use the 48Mhz standby clock from the 360 for the glitch counter. For the slim hack, the counter even runs at 96Mhz (incremented on rising and falling edges of clock)
The cpld code is written in VHDL.
We need it to be aware of the current POST code, our first implementations used the whole 8 bits POST port for this, but we are now able to detect the changes of only 1 POST bit, making wiring easier.

Conclusion
==========

We tried not to include any MS copyrighted code in the released hack tools.
The purpose of this hack is to run Xell and other free software, I (GliGli) did NOT do it to promote piracy or anything related, I just want to be able to do whatever I want with the hardware I bought, including running my own native code on it.

Credits
=======

GliGli, Tiros: Reverse engineering and hack development.
cOz: Reverse engineering, beta testing.
Razkar, tuxuser: beta testing.
cjak, Redline99, SeventhSon, tmbinc, anyone I forgot... : Prior reverse engineering and/or hacking work on the 360.

UPDATE BY SCALEO:

Der Hack funktioniert nicht (und wird auch niemals) mit Xenon-Mainboards! (Aber solche Krücken interessiert ja so oder so niemanden. Wink)

Quelle: http://www.xboxhacker.org/index.php?topi...#msg126144

Das ganze ist eine Art "JTAG" Hack für die Xbox 360 FAT und S Konsolen, es gibt dazu auch schon ein Video

[video]http://www.youtube.com/watch?v=JyYdL4L6vwE[/video]

Das Paket kann man sich gleich im Download Bereich downloaden.

Edit: Hier der Link

Reset Glitch Hack

Drucke diesen Beitrag

  Xbox 360 und Internet Browser
Geschrieben von: 20sin09 - 28.08.2011, 12:49 - Forum: Fragen zur XB360 Konsole - Antworten (4)

Hallo
ich hab ne Xbox 360 Elite 120gb und möchte damit gerne ins internet gehen also auf eBay oder so.
Ich habe 12 Monate Xbox Live Gold und kann auch in Facebook abe ich will ein Brwoser um auf andere Seiten zu gehen
Das Media Center läuft bei mir aber ich weiß nicht wie das mit dem Browser da geht hab es schon mehrfach versucht OHNE erfolg -.-
Ich hoffe ihr könnt mir helfen

Die box ist nicht geflasht

Drucke diesen Beitrag

  Deus Ex Human Revolution - Konsole friert bei Update ein... Statuscode...
Geschrieben von: Manhunt - 28.08.2011, 12:15 - Forum: Fragen zu XB360 Patches & Updates - Antworten (8)

Hallo Leute,
wie der Titel schon sagt ist meine Konsole beim Update eingefroren. Sad
Aktuell bringt sie mir den Statuscode: 3151-335A-B800-0F00-C000-0013

Find dazu nix bei MS ausser das ich den Service kontaktieren soll.
Die Konsole war mal bei MS zur Reperatur und das Liteon Ver. 7... wurde zuletzt auf die LT_plus v1.1 geflasht.

Besteht noch Hoffnung das wieder hinzubiegen? Key etc. alles noch vorhanden von den letzten 2 Flashvorgängen.
Danke für eure Hilfe...

Drucke diesen Beitrag

  nach flash öffnet Laufwerk nicht mehr
Geschrieben von: benno69 - 28.08.2011, 10:47 - Forum: Fragen zum Flashen - Philips / Lite-On - Antworten (19)

Hi
Ich wollte meine Xbox auf orginal flashen und dann das Systemupdate 13146 installieren, jetzt haz Jungleflasher es zwar gelöscht aber die orginal kommt in Dosflash nicht richtig drauf,
Er zeigte zwar im Dosflash an das er die bänke beschreibt, aber die Schublade geht anschließend nicht auf, im Jungleflasher wird sie auch nicht erkannt.
Gleichzeitiges starten der Konsole und Win XP ging auch nicht,dann wurde meine Festplatte nicht gefunden oder windows stürzte vorher ab,erst win xp starten und dann Konsole ging.
Unter Dosflash kommt auch meisten die meldung " Unknow flash typ".
Es ist ein Liteon 83850 C July 2009 dann habe noch ein ERsatzlaufwerk 74850C vom September 2008 das funktioniert noch, jetzt wollte ich da aber nicht auch noch was riskieren, dann andere müßte
doch wieder zum leben erweckt werden können oder ?

Drucke diesen Beitrag

  Updaten ? für neue Games nötig ?
Geschrieben von: Shadowbane - 28.08.2011, 09:27 - Forum: Fragen zum Flashen - Philips / Lite-On - Antworten (3)

Hallo, was ich nicht verstehe ist folgendes:

Meine Xbox 360 Dicke hat die LT+ 1.61 drauf und die Firmenware SystemUpdate12611 von welchem Datum die ist weiß ich nicht

jdnfalls ist da schon für kinec en paar vorbereitungen drin was ich nicht nutze und brauche

Was mich wundert, weil alle hier wegen AP 25 was schreiben , bei mir laufen die ganzen spiele ohne probs wie z.B AC Broth.., NFS Shift 2, CoD Black Ops

Das sind die neusten Games die ich besitze die ja diesen Check haben sollen, Noch zu sagen Meine Console is Offline und ich Spiele damit auch nur Offline

laufen da jetzt die ganz neuen Games noch wie Deus Ex usw. oder muss ich jetzt auch wieder Flashen ? Braucht man das ganze nur um Online zu gehen ?

Klärt mich mal einer bitte auf

Danke mfg. Daniel

Drucke diesen Beitrag

  Zwei Spiele problem im FSD2.0
Geschrieben von: skorpion-23 - 28.08.2011, 08:09 - Forum: Sonstige Fragen zur Homebrew - Antworten (1)

Morgen
Ich habe auf meiner JTAG-Box zwei Spiele auf der Festplatte kopiert, folgende Spiele:


Red Dead Redemption

Red Dead Redemption Undead Nightmare


So steht es auch im Filemanager vom FSD2.0 drin.


Aber im Freestyledash unter XBox games steht 2x Red Dead Redemtion drin
und das gleiche Logo es geht aber nur ein Red Dead Redemption und das
andere geht nicht. Gehe ich über XEXMENÜ rein gehen beide spiele, haben aber das gleiche Logo.Kann man das ändern,das Logo?

Drucke diesen Beitrag