Startseite - ModControl.Com - GermanysNr1MultiConsoleSceneSource

PS3: mmCM v04.00.01 / multiMAN Cobra Manager v04.00.01

Geschrieben: 26.01.2012 um 17:20 von hitman43

Das Cobra USB Team hat den mmCM / multiMAN Cobra Manager aktualisiert.
Die neuste Version des multiMAN enthält ein neuen Displaymode.
Außerdem wurde in dieser Version der Support zum laden von PS3, DVD und Blu-ray ISO Files übers Netzwerk vorbereitet.
Screenshots vom neuen Displaymode findet Ihr im Anhang.

Zitat:

Cobra Update: 04.00.01

* Added new display mode (Board 5x4x5), replacing the oldest "Game list (plain)" mode
"Board" display mode shows ICON0.PNG game images by default.

You can use covers by changing the option "XMMB Game Icon Swap" in Settings
http://img834.imageshack.us/img834/5719/psv00x.jpg
http://img842.imageshack.us/img842/458/psv01x.jpg
http://img835.imageshack.us/img835/9405/psv1x.jpg

* Improved File Manager visuals when used in SD resolution (480p/576p)
* Fixed an issue, which prevented operation on CFW/MFW 3.41 when Cobra USB is not used
* Added support for showing PSN titles in all display modes from internal/external HDD (PSN titles cannot be loaded and you have to put empty RELOAD.SELF in game's USRDIR folder to make it show!) (requested)
* Added lastGAME2 and bdRESET applications
* Added 11 new themes to the theme download section (total of 14 now)
* Updated 15 language files
* Added separate background images for Board and XBDM display modes (PSVBG.JPG and XBDBG.JPG)
* Updated mmCM Original Theme (includes new images PSVBG.JPG, XBDBG.JPG, PBOX0.PNG, PBOX1.PNG)
* Preparations to support loading of network PS3, DVD and Blu-ray ISO files
* Preparations to support firmware version spoofer (auto-spoofing to latest official FW or to user-defined fixed version)

Required Cobra USB update will be announced when network ISO and firmware spoof support is available

More info on http://www.cobra-usb.com

Download: mmCM ver 04.00.01 BASE (20120126).rar
Quelle: http://www.cobra-usb.com/

Views: 84 | Anhänge: 3

PS3: Showtime v3.4

Geschrieben: 24.01.2012 um 14:47 von hitman43

Homebrewcoder Andreas Öman alias LonelyCoder hat das Showtime v3.4 Update für PlayStation 3 Konsolen mit Jailbreak bzw. CFW veröffentlicht.
Nachfolgend die Changelogs und Releasenotes mit den Änderungen.
Die Downloads findet Ihr im Dateianhang.

Zitat:

Today marks the release of Showtime 3.4. For a list of most of the important bug fixes and features added, see the 3.4 page.

Download the release from github.

Note: It seems Showtime still suffers from out of memory conditions now and then but I've not been able to pinpoint the exact cause of those issues. A few things were implemented just prior to the 3.4 release in order to mitigate the low memory problems.

With that said I though I could write something about what's been done this year and where Showtime is going.

... (History and Future) ...

Tomorrow I will be leaving on a six week vacation and during that period I won't do any PS3 related development (as I don't have the console with me). I might do some general Showtime stuff though. I've no idea what that will be though... I guess I'll find out.

So with no further ado,
Thank you for the past year. Talk to you all soon again.

Features:

Zitat:

Feature #348: please add support for EGL / OpenGL|ES
Feature #417: Mark files that has been played
Feature #518: Samba streaming
Feature #640: MP4 codec support
Feature #690: resuming playback from where left off
Feature #707: Detect track flags in .MKV container
Feature #710: Subtitle adjustment.
Feature #775: mkv track names display
Feature #784: Plugins: Cache remote (HTTP) image files
Feature #802: Plugins: settings.createComboBox like in showtime settings

Fixes:

Zitat:

Bug #216: Image navigator - missing rotation of previews
Bug #448: Photo - Doesn't display .jpg over 900ko
Bug #478: new version can't play 1080p movies
Bug #628: Clock is 1 hour off.
Bug #716: Video list disappears permanently
Bug #717: The clock displaying is not right
Bug #718: italic subtitles display
Bug #719: Subtitles in mkv file are still on even though in settings they are off
Bug #720: Rar Split files is broken
Bug #721: L5.0/5.1 MKV no video playback
Bug #724: 3 Video Files splitted but Showtime Shows 1 Video in the Directory
Bug #726: Subtitle BUG (Overlapping)
Bug #729: .MP4 Container problem (and possible .MKV improvement suggestion)
Bug #731: Subtitles in rar split files
Bug #732: Subtitle position.
Bug #739: SMB (Samba) Network Issue
Bug #740: Bookmarks: Selecting photo image and appera fodler image?
Bug #746: SMB (Samaba) Video Playback Issues
Bug #748: MKV 5.1 igh level ( Debug Option to write a txt when it says CPU to slow )
Bug #750: high quality mkv (+20gb)
Bug #757: Samba Playback Video Speed-Ups Slow-Downs
Bug #760: Memory leak when playing large/long movies
Bug #771: No video shown when playing this movie sample
Bug #773: Idee to eliminate the Memory Problem on MKV!!!
Bug #776: Http Client Hangs
Bug #779: Plugins: Message with a lot of charaters block
Bug #781: Plugins: Read local xml files
Bug #782: Plugins: Read files from SMB path
Bug #790: Plugins: showtime freeze when reading rtmp
Bug #794: .OGM Container playback issues [PS3]
Bug #796: Audio track bug
Bug #806: Video titles do not flow under cover art image?
Bug #810: AC3 mono track does not work.
Bug #834: FLV PLAYBACK BUG
Bug #836: More than 1 Subtitle per movie.
Bug #842: Possible bug with AVC codec Baseline@L1.3. (on PS3).

Quelle: https://www.lonelycoder.com/redmine/news/31

Views: 74 | Anhänge: 3

Wii: Bolt Thrower v0.62

Geschrieben: 23.01.2012 um 18:48 von hitman43

Titmouse hat seinen Shooter Bolt Thrower für homebrewtaugliche Nintendo Wii Konsolen aktualisiert.

Zitat:

Version 0.62 is now released - Fixed music playback stopping in 0.61 after loading screen, needing next tune to be clicked to restart the tune.

Bolt Thrower is currently single player Space Shoot 'Em Up. It’s still work in progress and updates will happen whenever I can find the spare time. Every effort is being made to detach game data from the code, being 'data driven' anyone can change the look or functionality of the game. So I've exposed the data through a XML configuration file rather than lock the data into the code. Please submit your ideas, bug reports or anything else via the discussion page if you wish to help in any way.

previous version comments

Version 0.61 is now released (available from the games auto update only at the moment) - try the Dpad up button to recall mines (mines are Dpad down) I’ll add more notes here about 0.61 bit later when I have some spare time.

Quelle: BoltThrower - WiiBrew via - Afficher le sujet - [Wii] Bolt Thrower v0.62

Views: 76 | Anhänge: 1

Xbox 360: Freedom Manager v3.0

Geschrieben: 19.01.2012 um 15:58 von hitman43

Das Matrix Team hat den Freedom Manager v3.0 veröffentlicht. Die neuste Version der Software erlaubt es die LTPlus v3.0 nun auch auf die Freedom PCB´s zu flashen um so unter anderem das "Silver Bullet" Feature der LT+ 3.0 nutzen zu können.
Mittels LT+ 3.0 ist es möglich alle XGD3 und AP2.5 Spiele mittels Topology Data Patches in der ISO problemlos auf der Xbox 360 abzuspielen.
Bedenkt vor dem Erwerb der Platine bitte, dass die Matrix Freedom PCB nur mit Xbox 360 SLIM LiteON DG-16D4S Laufwerken (0272, 0225, 0401 & 1071) funktioniert.

Zitat:

The Freedom Manager V3.0 compatible with LT+ 3.0 has been released.

To use it simply unzip it, run it, and press “WRITE IXTREME FW”, the Manager will take care of all.

That’s as easy as it comes when using the Freedom PCB

.

Matrix Freedom PCB kaufen bei: CodeXecution.Com
Quelle: The MATRiX Team - Home of the matrixglitcher360 and matrix nand programmer

Views: 302 | Anhänge: 1 | Antworten: 2

PS3: KaKaRoTo - PS3 FW 4.00 HEN in absehbarer Zeit!

Geschrieben: 19.01.2012 um 15:50 von hitman43

Homebrewcoder und Hacker KaKaRoTo hat auf seinem Blog einen erfreulichen Eintrag verfaßt.
KaKaRoTo und 10 weitere Entwickler arbeiten mit Hochdruck an einer Möglichkeit Homebrewsoftware auch unter der neusten PS3 Firmware 4.00 auszuführen.
Es werden keine Peek&Poke Syscalls supported, das heißt, Backup Manager werden vorerst nicht laufen.
Der PS3 4.00 HEN besteht insgesamt aus 3 Teilen, zwei davon sind bereits fertiggestellt, der dritte Part ist zu 60-70% einsatzbereit.
Einen Releasetermin des PS3 4.00 HEN gibt es noch nicht, allerdings die Info, das Mathieulh ein Lügner ist und wie viele bereits erwartet haben keine einzige Information für einen PS3 Systemhack parat hatte.

Zitat:

Here’s a “quick” status update on the 4.00 HEN (Homebrew ENabler) for PS3.
Following my clarifications from almost 2 months ago here, there has been a lot of progress. We have not been slacking off, we’re a group of about 10 developers working together for the last 2 months, for sometimes 15 hours everyday in order to bring back homebrew support to the latest version of the PS3.
There are three major parts to the HEN, first, getting the packages to install on the PS3, that part is done, completed, tested, debugged, etc.. the second part is to get the apps to run, that one still has major issues… the last part is something I will not discuss for now (it’s a surprise) but it’s about 60% to 70% done (and it has nothing to do with peek&poke and has nothing to do with backup managers or anything like that. This is and will stay a piracy-free solution for the PS3).
Now, running apps is the biggest challenge that we’ve been working on for the past 2 months. As some of you know, if you’ve been following me on Twitter, we originally had hoped for Mathieulh to give us the “npdrm hash algorithm” that was necessary to run the apps, but he was reluctant, he kept doing his usual whore so people would kiss his feet (or something else) so he’d feel good about himself. But in the end, he said that he refuses to give us the needed “npdrm hash algorithm” to make it work… So what I initially thought would be “this will be released next week” ended up taking a lot more time than expected, and we’re still nowhere near ready to make it work.
Mathieulh kept tossing his usual “riddles” which he thinks are “very helpful for those who have a brain”, and which pisses off anyone who actually does… so he told us that the solution to all our problems was to look in appldr of the 3.56 firmware.. and that it was something lv1 was sending appldr which made the “hash check” verified or not… so we spent one month and a lot of sweat and after killing a few of our brain cells out of exhaustion, we finally concluded that it was all bullshit. After one month of reading assembly code and checking and double-checking our results, we finally were able to confirm that that hash algorithm was NOT in the 3.56 firmware like he told us (at all).
He said that it was an AES OMAC hash, but after tracking all the uses of the OMAC functions in appldr, we found that it was not used for the “hash”… he then said “oh, I meant HMAC“, so we do that again and again come up with the same conclusion, then we’re sure it’s not in appldr, and then he says “ah no, it’s in lv1“.. have a look for yourself to what he decided to write : Talk:KaKaRoTo Kind of ´Jailbreak´ - PS3 Development Wiki
That happened after the huge twitter fight I had with him for being his usual arrogant ass and claiming that he “shared” something (For your information, the code that he shared was not his own, I have proof of that too (can’t show you the proof because even if I don’t respect him, I gave him my word to not share what he gave me, and I respect my word) since he forgot to remove the name of the original developer from one of the files… also it was completely useless and was not used at all, just made me waste a day reading the crappy undocumented code. So why is he still trying to force his “advice” through these riddles even after we had that fight? Well to sabotage us and make us lose all those months of hard work!
So anyways, we had all accepted that Mathieulh was full of shit (we knew before, but we gave him the benefit of the doubt) and decided to continue working without considering any of his useless riddles. So we then tried to exploit/decrypt the 3.60+ firmware in order to get the algorithm from there.
Now, a few more weeks later, we finally have succeeded in fully understanding that missing piece from the “npdrm hash algorithm”, and here it is for everyone’s pleasure with some prerequisite explanation :
A game on the PS3 is an executable file in a format called a “SELF“file (kind of like .exe on windows), those “self” files are cryptographically signed and encrypted.. For PSN games (games that do not run from a bluray disc), they need to have an additional security layer called “NPDRM”. So a “npdrm self” is basically an executable that is encrypted and signed, then re-encrypetd again with some additional information. On 3.55 and lower, we were able to encrypt and sign our own self files so they would look like original (made by sony) “npdrm self” files, and the PS3 would run them without problem. However, it wasn’t really like an original file.. a real NPDRM self file had some additional information that the PS3 simply ignored, it did not check for that information, so we could put anything in it, and it worked. Since the 3.60 version, the PS3 now also validates this additional information, so it can now differentiate between NPDRM self files created by sony and the ones that we create ourselves for homebrew. That’s the “npdrm hash algorithm” that we have been trying to figure out, because once we can duplicate that information in the proper manner, then the PS3 will again think that those files are authentic and will let us play them.
Another important point to explain, I said a few times that the files are “signed”.. this means that there is an “ECDSA signature” in the file which the PS3 can verify. The ECDSA signature is something that allows the PS3 to verify if the file has been modified or not.. it is easy to validate the signature, but impossible to create one without having access to the “private keys” (think of it like a real signature, you can see your dad’s signature and recognize it, but you can’t sign it exactly like him, and you can recognize if your brother tried to forge his signature). So how were we able to sign the self files that were properly authenticated on 3.55? That’s because this “ECDSA signature” is just a very complicated mathematical equation (my head still hurts trying to fully understand it, but I might blog about it in the future and try to explain it in simple terms if people are interested), and one very important part of this mathematical equation is that you need to use a random number to generate the signature, but Sony had failed and used the same number every time.. by doing that, it was easy to just find the private key (which allows us to forge perfectly the signature) by doing some mathematical equation on it. So to summarize, a “signed file” is a file which is digitally signed with an “ECDSA signature” that cannot be forged, unless you have the “private key” for it, which is impossible to obtain usually, but we were able to obtain it because Sony failed in implementing it properly.
Now, back on topic.. so what is this missing “npdrm hash algorithm” that we need? well it turns out that the “npdrm self” has a second signature, so it’s a “encrypted and signed self file” with an additional layer of security (the NPDRM layer) which re-encrypts it and re-signs it again. That second signature was not verified in 3.55 and is now verified since the 3.60 version of the PS3 firmware.
One important thing to note is that Sony did NOT make the same mistake with this signature, they always used a random number, so it it technically impossible to figure out the private key for it. To be more exact, this is the exact same case as the .pkg packages you install on the PS3, you need to patch the firmware (making it cfw) so that those .pkg files can be installed, and that’s because the .pkg files are signed with an ECDSA signature for which no one was able to get the private key. That’s why we call them “pseudo-retail packages” or “unsigned packages”.
The signature on the NPDRM self file uses the exact same ECDSA curve and the same key as the one used in PS3 .pkg files, so no one has (or could have) the private key for it. What this means is that, even though we finally figured out the missing piece and we now know how the NPDRM self is built, we simply cannot duplicate it.
The reason we wasted 2 months on this is because Mathieulh lied by saying that he can do it.. remember when the 4.0 was out and I said “I can confirm that my method still works” then he also confirmed that his “npdrm hash algorithm” still works too? well he didn’t do anything to confirm, he just lied about it because there is no way that he could have verified it because he doesn’t have the private key.
I said I will provide proof of the lies that Mathieulh gave us, so here they are : he said it’s in 3.56, that was a lie, he said it’s an AES OMAC, that was a lie, he said it’s an HMAC, that was a lie, he said it’s in appldr, that was a lie, he said it’s in lv1, that was a lie, he said that he can do it, that was a lie, he said that “it takes one hour to figure it out if you have a brain”, that was a lie, he said that he verified it to work on 4.0, that was a lie, he said that he had the algorithm/keys, that was a lie, he said that once we know the algorithm used, we can reproduce it, that was a lie, he kept referring to it as “the hash”, that was wrong. The proof ? It’s an ECDSA signature, it’s not a hash (two very different terms for different things), it was verified by vsh.self, it was not in lv2, or lv1, or appldr, and the private key is unaccessible, so there is no way he could build his own npdrm self files. Now you know the real reason why he refused to “share” what he had.. it’s because he didn’t have it…
So why do all this? was it because his arrogance didn’t allow him to admit not knowing something? or was it because he wanted to make us lose all this time? To me, it looks like pure sabotage, it was misleading information to steer us away from the real part of the code that holds the solution…. That is of course, if we are kind enough to assume that he knew what/where it was in the first place. In the end, he wasn’t smart enough to only lie about things that we could not verify.. now we know (we always knew, but now we have proof to back it) that he’s a liar, and I do not think that anyone will believe his lies anymore.

Enough talking about liars and drama queens, back to the 4.0 HEN solution… so what next? well, we now know that we can’t sign the file, so we can’t run our apps on 3.60+ (it can work on 3.56 though). What we will do is look for a different way, a completely new exploit that would allow the files we install to actual run on the PS3. We will also be looking for possible “signature collisions” and for that we will need the help of the community, hopefully there is a collision (same random number used twice) which will allow us to calculate the private key, and if that happens, then we can move forward with a release.
When will the “jailbreak” be released? If I knew, I’d tell you, but I don’t know.. I would have said in last november, then december, then before christmas, then before new year, etc… but as you can see, it’s impossible to predict what we will find.. we might get lucky and have it ready in a couple of days, or we may not and it will not be ready for another couple of months.. so all you need to do is : BE PATIENT (and please stop asking me about an estimated release date)!
I would like to thank the team who helped on this task for all this time and who never got discouraged, and I’d like to thank an anonymous contributor who recently joined us and who was instrumental in figuring it all out. We all believe that freedom starts with knowledge, and that knowledge should be open and available to all, that is why we are sharing this information with the world. We got the confirmation (by finding the public key used and verifying the signatures) yesterday and since sharing this information will not help Sony in any way to block our efforts in a future release, we have decided to share it with you. We believe in transparency, we believe in openness, we believe in a free world, and we want you to be part of it.
If you want to know more about this ECDSA signature algorithm, read this interesting paper that explains it in detail, and you can also watch Team Fail0verflow’s CCC presentation that first explained Sony’s mistake in their implementation, which made custom firmwares possible.

Thanks for reading,
KaKaRoTo

Zitat:

We are now sure at 100% (with proof) that the @Mathieulh bastard has been lying to us and on purpose misleading us to sabotage the release..

Zitat:

and @Mathieulh didn't want to "share" "his" "npdrm hash algo" because he doesn't know it, and we now for sure that he lied and don't have it

Quelle: Status update on the PS3 4.0 HEN

Views: 615 | Antworten: 4

PS3: Team AC1D - Doch nur Dummgelaber!

Geschrieben: 17.01.2012 um 17:44 von hitman43

Als erstes zwei Dinge vorweg, der True Blue Dongle ist aus unserer Sicht kein Hammer, wir werden das Ding hier nicht bewerben oder irgendwelche EBOOT´s anbieten damit Eure Kopien (unerheblich ob Ihr sie selbst gesichert habt) abspielen könnt.
Fakt ist aber, das der True Blue Dongle momentan die einzige Möglichkeit ist um neuere Spiele (Firmware 3.6+ Games) auf einer homebrewtauglichen PS3 (CFW 3.55) abzuspielen.
Andere Lösungen gibt es nicht. Um so erstaunlicher war gestern der Hoffnungsschimmer für einige als Team AC1D großmaulig (wohl via MonkeyDesk.At, ist wohl die Quelle für diese News) ankündigte, das der True Blue Dongle nichts weiter als Abzocke ist.
Fakt ist, jeder muss wissen ob er Geld für "Raubkopierfeautres" ausgeben will.
Fakt ist auch, das Team AC1D einwenig XML Editing am PS3 XMB vorgenommen haben, sprich von Denen kam nichts besonders auch wenn sie besondere Leute in ihrem Statement grüßen.
Fakt ist, es gibt keine CFW, kein sinnvolles Programm noch irgendeinen Hack für die PS3 der von Team AC1D stammt (die Redirections von DevFlash Files zum USB Stick kamen auch nicht von Denen

).
Von True Blue hingegen kam zumindest eine CFW und ein Dongle der, auch wenn die meisten Features nicht mehr bringen als andere Lösungen, zumindest auch die neusten bzw. aktuellere Games auf der PS3 abspielen kann.
Team AC1D muss also abliefern, das werden sie vermutlich aber nicht..
Die traurige Realität bleibt, der True Blue ist im Moment die einzige Lösung um neuere Games und Homebrewsoftware auf der PS3 abzuspielen.

Zitat:

Recently we have been made aware of several announcements made on various forums from people who seek to trivialise the capabilities of True Blue and claim that functionality such as playing 3.6+ games can easily be reproduced on regular custom firmware (CFW).

In each and every case, the announcements amount to nothing more than baseless accusations and disinformation - these people are intentionally spreading information they know to be incorrect in an attempt to create confusion. A lot of effort and research has gone into the creation of True Blue, which has allowed us to take our position as the ONLY team producing any real results, providing solid support and benefits for our customers. For all the people who have claimed that what True Blue does is trivial and can be easily duplicated, there has been absolutely nothing that has come from any of these peopole, they have simply been all talk and have delivered nothing of real value.

The proof is in the result and at the end of the day, with all the claims that have been made by other groups, the fact remains that the True Blue team are the only ones who have actually delivered.

Offizielle Webseite: True Blue - play 3.6+ games on your jailbroken PS3
Quelle: http://www.ps3crunch.net

Views: 573 | Antworten: 8

Xbox 360: x360Glitchip angeblich bald Corona kompatibel?

Geschrieben: 17.01.2012 um 17:24 von hitman43

*UPDATE*:

Wie von uns vor einigen Tagen schon etwas "aggressiver" formuliert, x360glitchip ist garnichts, lest selbst:

Von Tiros (NANDPro sollten alle kennen, auch die die über meine Wortwahl gejammert haben

)

Zitat:

I call shenanigans on x360glitch chip. Everyone grab a broom

Having an onboard osc. does nothing at all to change the cpu clock speed on the fly.
The clk is only used for timing the glitch pulse, and thats only a PART of what needs to be done.
Apparently the creators of this device dont even fully understand how the hack works

Quelle: http://www.xboxhacker.org/index.php?...3120#msg133120

Von Blackaddr (unter anderem der AUD_CLAMP Fix):

Zitat:

Indeed. In addition, the nonsense these (not just x360Glitchip) developers are spouting about their products improved boot times and such is ridiculous. Most of them are just copycatting whatever the 'flavour-of-the-day' alternate cap/wire gauge/loop is on the forums, almost none bring any value-add to the table.

There are some big hints about what needs to be done to glitch a Corona on this board, but somehow I doubt these guys even understand the information available to them. STBY_CLK is used because you need *some* clock at a reasonably fast frequency. I create my own clock on my FPGA board simply because I can, but as Tiros pointed out, I still need to use either CPU_PLL_BYPASS or change the HANA clock in order to change the CPU's clock.

On the bright side, the useless oscillator is eating into their profits since people will quickly realize paying more for this is stupid.

Quelle: http://www.xboxhacker.org/index.php?...3123#msg133123

*UPDATE ENDE*

Zuerst, Maximus bzw. sein Maximus Stinger Glitcher ist ebenfalls in der Lage mit nur 6 Kabeln, also ohne CLK_STBY in der Slim zu funktionieren. XAIO wurde angekündigt.
Das Marketinggelaber ala andere bauen nur vom x360Glitchip nach ist also mal wieder völliger Quatsch.
Zu dem waren die Testmuster vom x360Glitchip eher enttäuschend.
Ob die neue Version des Chips (1.4) endlich mal gut in Slim Konsolen läuft bleibt also abzuwarten, die Frage ob der neue x360Glitchip v2 dies bewerkstelligen kann ist also aufgrund der miesen Vorgängerhardware auch noch ungewiss.
Fakt ist, das viel viel Gelaber von den Franzosen an der Tagesordnung steht und viele Marketingversprechen auch bei anderen Produkten nicht eingehalten wurden.
Nunja, schaut Euch das Video an, ich glaub viele von Euch würden eher den TX Cool Runner, Squirt360, XAIO, Matrix II oder Maximus Stinger nehmen als den x360Glitchip v2 der hoffentlich nicht aussieht als hätte man den Chip selbst in der Garage zusammengebastelt wie es beim v1.2 der Fall war.
Zu den News. Der neue x360Glitchip soll eventuell ab Februar in
Xbox 360 Konsolen mit Corona Mainboards funktionieren.
Vermutlich wird auf einen angepassten Code für das Mainboard gewartet, was die angebliche Innovation komplett in Frage stellt.
Aber gut, lest bzw. seht selbst, gezeigt wurde natürlich ein Trinity Mainboard.
Mich persönlich haut es nicht um!

Zitat:

While other teams are content to copy and / or do only the smart money with them to bring anything more and / or make announcements

announce nothing, the team brings you the first x360Glitchip chip global Corona Ready.

As you know, the corona (new version of Slim motherboard after Trinity) were no longer compatible Glitch after the withdrawal

HANA chip used in the timing via the point CLK_STBY.

The x360Glitchip v2 is the first global chip no longer requiring that point, and becomes Corona Ready.

Of course, it will be an update of build.py Glitch hack to support the new corona of CB, CB 13121.

Other features of the v2 will be made soon, because it does not stop there. :-)

Here's a video of a x360Glitchip v1.4, modified for Corona Ready, a Trinity.

You will notice the absence of point B (This is no longer useful), and impressive boot time. (10s, 15s, 12s and 7s).

Quelle: x360Glitchip vous apporte la compatibilité Corona

Views: 584 | Antworten: 10

PS Vita: PlayStation Vita Firmware v1.52 released!

Geschrieben: 17.01.2012 um 14:12 von hitman43

Das Trauerspiel von unnötigen Firmwareupdates auf einer Sony Konsole scheint sich nun auch auf der Vita fortzusetzen.
Die Systemaktualisierung 1.52 für die PS Vita bringt neben einer verbesserten Systemstabilität (angeblich soll ein Fix für der Erkennung von SIM Karten im 3G Netz eingebunden worden sein) nämlich keine nennenswerten Funktionen mit sich.
Mal abwarten was Sony noch aus der Vita rausholt!

Zitat:

System software version 1.52 for PlayStation ® Vita Update

From January 16, 2012, began to update the system software version 1.52.

To become available and some features of the PlayStation ® Network features, updates the system software of PS Vita (Update) is required. PS Vita also system software, by updating, adding and security can be enhanced many features. Please use the update to the latest version.

The main features in system software update version 1.52
The software system has improved the operational stability.

Quelle: All the latest news, information, and file downloads from the Sony Playstation/PsOne,PS3/PS2/PSP/PS VITA Scenes! - PS Vita Firmware 1.52 Released via All the latest news, information, and file downloads from the Sony Playstation/PsOne,PS3/PS2/PSP/PS VITA Scenes! - PS Vita Firmware 1.52 Released

Views: 127 | Antworten: 1

Letzte Forenthemen

	Thema	Infos	Letzter Beitrag
	Xenonblade Cronicles läuft... Forum: Offizielles WODE Forum	1126 Views: 18 Antworten:	Heute, 01:09 von Jones23
	Wii: Homebrewchannel,USB Loader GX... Forum: Software Tutorials	215394 Views: 1089 Antworten:	Heute, 00:58 von Jones23
	4.3E mit HBC 1.0.8 IOS58... Forum: Software (allgemein)	5039 Views: 29 Antworten:	Heute, 00:57 von Jones23
	suche x360 spieler für xlink Forum: Offtopic / Funny Things	19 Views: 0 Antworten:	Gestern, 22:57 von winfreund
	Kommende xgd3 Games Forum: Offizielles xk3y Forum	159 Views: 5 Antworten:	Gestern, 21:49 von Ryo_Hazuki
	ISO/XK3Y Forum: Offizielles xk3y Forum	79 Views: 4 Antworten:	Gestern, 21:41 von Ryo_Hazuki
	Gears of War 3 "Disk konnte... Forum: Xbox 360 - Backuptalk	2256 Views: 23 Antworten:	Gestern, 21:20 von winfreund
[ Neue Beiträge \| Heutige Beiträge ]