Homebrew-Connection.org

Please login or register.

Login with username, password and session length
Advanced search  

News:

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Life4Beers

Pages: [1]
1
General Development / Skylander Figuriene Mod / Hack For all Console GUI
« on: 21 November 2012 à 11:49:37 »

Warning - Always Back up your Original Skylander read
Quote
How to use Skylander Editor

Before I get into how to use the Skylander editor I think it is worth clearing up some information about it.

This tool will NOT:

    Let you crack the game. It only works with legitimate Skylanders you have purchased and will not let you change one character type to another. It also won’t let you unlock areas you have not paid for.
    It may not work with Xbox portals – the code says this support is experimental. The author did not have an XBOX portal to test with but the code needed was inserted.
    It has another known bug. If you have never played with a Skylander it will say the data checksums are invalid – this is because new Skylanders don’t have checksums. This is fixed by putting the skylander on the portal while playing the game, this writes the checksums to the figure and it can then be edited or backed up.

This tool will:

    Let you back up your Skylanders for when a save goes wrong.
    Let you restore a character from a backup file.
    Let you experiment with different upgrade paths.
    If you are hardcore you can read the file specifications and use this to develop more advanced tools to change hats or change other Skylander attributes.

Here is how use the Skylander Editor v2 tool:

    If you haven’t played the online version of Skylanders you need to install the portal driver. In the bin directory run the file called spyrowebportaldriver.exe to install the portal drivers or download it by creating an account at universe.skylanders.com.
    The program works from a DOS command window. Type Editor.exe. This will give you a list of available commands.
    Place a figure on the portal that is connected to the computer.
    The command ‘Editor.exe r Figure.bak’ will back up your figurine to a file called Figure.bak in the same folder as the editor. You can use whatever name you want for the file but naming them after the figure makes the most sense.
    The command ‘Editor u Figure.bak’ will upgrade the skylander to max money and stats from heroic challenges.
    The command ‘Editor.exe w Figure.bak’ will write the modified(or unmodified) backup of your skylander from the backup file.



Download Link : Skylander GUI Download

Life4Beers

2
Hardware & Technical / Nintendo Wii U Teardown
« on: 21 November 2012 à 11:20:16 »
The Wii U is available in two versions: the basic and deluxe kits. The basic kit comes in white, while the deluxe is black. Both are glossy. The deluxe console gives you 32GB of on-board storage (eMMC NAND) vs. 8GB for the standard model. The deluxe kit also includes a stand and cradle for the Wii U tablet GamePad as well as a stand for the console itself.

















You can read more at the source


Source News : ANANDTECH

Life4Beers

3
PS3 News / SDAT Creator by oakhead69
« on: 16 November 2012 à 14:12:53 »
Oakhead69 one of the latest Developers to join PSX-Scene Developers Team has released a handy PC application called the "SDAT Creator". This tool will create a V3 SDAT file from decrypted data. Instructions are also include on how to decrypt V4 SDATs on a 4.xx CFW PS3. This program is also useful for modifying the contents of SDAT file for language conversions. The source code is provided in the download below.

Instructions:

Quote
•   You first need to decrypt the original V4 SDAT file.
•   You can use extttdpk coded by asmodean asmodean's reverse engineering page - news and updates to decrypt it.
•   This needs to be done on a PS3 with >3.56. e.g 4.21.
•       There are compiled versions of this on the web for example
•   You need to modify the file decrsdat.lst with a list of SDATs to be decrypted e.g.

Quote
Code:
# input_file output_file
/dev_hdd0/model_shader_pack.SDAT /dev_hdd0/model_shader_pack.dat

Quote
There is code available that can decode V3 SDATs on the PC, but we can not decode the V4 SDATs as we do not have the EDATKEY1 that has a SHA-1 of 6ECDFEC0A11890C1F2A689062D3EFE562317B2FB. Once we have this key V4 SDATscan be decrypted on a PC.

This program is also useful for modifying the contents of SDAT file for language conversions etc. I know that this has been requested by people in the past. Now we can do it.

To use the SDAT Creator:

1) Provide the decrypted data as input to the SDAT creator.
2) Specify the output SDAT file.
3) Optionally provide the original V4 SDAT file and it will then use the hashes etc from this file otherwise it just uses some default values..
4) Press the 'Create SDAT' button and that's it.

The code I have provided is based on KDSBest's C# port of the Java code written by JuanNadie. Any keys used in the code are already publicly available on the internet.

Most of the information I used to create this program was gained from this post NPDRM Self algorithm.
Big thanks to JuanNadie, KDSBest and others that posted on this thread.

I have used it to create successful patches for
Test Drive: Ferrari Racing Legends (BLUS30842)
Ice Age 4: Continental Drift (BLES01686).

For Sports Champions 2.BCES01598 there are other issues with the EBOOT.BIN that I can not fix.
For Air Conflicts Pacific Carriers.BLES01604 the V3 SDAT files to not work even on 4.21. I think this is because they contain elf files and V3 SDATs do not support executable content.
Men.In.Black.Alien.Crisis.BLES01549. This should work but it has a 4gig+ sdat file, but I have tested my creator can handle files of this size.
Disney.Epic.Mickey.2.The.Power.of.Two I have noticed that this has sdat files but I have not had any time to look at them.


Life4Beer



4
PS3 News / Sony Gearing Up To Issue The Ban Hammer - CFW Users Beware!
« on: 14 November 2012 à 07:21:21 »
The PlayStation 3 scene should have expected this. Various reports suggest that anyone using custom firmware and using PSN/SEN will be banned. Even those using fck PSN or other means of bypassing access to PSN/SEN can be included in the ban wave. I for one have never used online access on my custom firmware PS3, so it would be interesting to see how far the ban hammer reaches. If you are one of the unlucky ones you will be met with error code 8002A231. Please inform fellow CFW users should you encounter this.

Translation from Japan's Playstation Website
Quote
Patronage of our PlayStation ® 3 you use, thank you.

Recent PlayStation ® malicious software used in the 3 cases occurred.
Use of illegal software is PlayStation ® 3 system software license agreement, the PlayStation ® Network terms of use, the Sony Entertainment Network terms of use violation.
Violations found PlayStation ® will be exempt from providing services such as warranty and repair of three.
If PlayStation ® 3, if using a rogue software, immediately stop using them, please delete. If you are using illegal software, future PlayStation ® 3 PlayStation ® may be no longer connected to the Network and Sony Entertainment Network.

Online community management and other healthy perspective, PlayStation ® even if observed violating the Network terms of use and terms of Sony Entertainment Network, or international laws, PlayStation ® may be no longer connected to the Network and Sony Entertainment Network.

We appreciate your understanding and cooperation.


Source News : Playstation Japan

Life4Beers

5
PS3 News / ErmaC 4.30 CFW v1.3 Available & Updated
« on: 13 November 2012 à 08:57:58 »
HDMadness has released another version of this CFW based on 4.30 for the PS3, this time removing the annoying Demo Mode notice, improved stability and more!

For those who have taken the leap to custom firmware above 3.55 might want to take a look at this. Dubbed the next Kmeaw of 4.30 CFW, or 4.21 with 4.30 spoofs, this custom firmware might be the next gen of firmware with the most game compatibility. Well that is what most comments via the sources below suggest. Even with the previous statements this firmware is not without bugs. Such bugs include the elusive XMB grouping bug. I bring this info to you without actually testing it myself. So those avid psx-scene members that are willing to give us some feedback would be appreciated. Mod on! Game on! and advance!

ErmaC 4.30 CFW v1.3:
Quote

•   More Stable than any other 4.30 CFW out there (Tested with numerous PS3, slim and phat models)
•   Can run games with the latest updates signed with Keys up to 4.30 without any patching needed
•   PSN enabled
•   Cinavia protection disabled
•   No "Demo Mode", XMB fully optimized so you can have the best performance with your console
 






Source News : PS3 Crunch

Life4Beers

6
PS3 News / Rebug CFW 4.21 XMB MOD v0.4 XMB
« on: 13 November 2012 à 03:52:22 »
Developer IcEmAn2012, known for his IcE-rX Media Manager and XMB CFW MOD for XMBM+ mods, is back again. This time around he brings a mod to Rebugs CFW 4.21 XMB.  This project, a work in progress, includes modded XMB categories such as images, video & homebrew and more. Also around the corner is version 1.0 and an upcoming video of this Rebug XMB Mod.

Rebug CFW 4.21 XMB MOD v0.4 XMB FEATURES:

Quote
•   Images
•   Video
•   Homebrew
•   Games
•   Install
•   Netzwerk-Einstellungen/Spieldaten-Dienstprogramm
•   info

Install Package Installer under category is divided into 7 system folder:
•   PS3 Hard Drive (internal)
•   Install Homebrew (Tools)
•   Install XMB BOOT PKG
•   Install PSN Content
•   Install PS1 PSN Content
•   Install PKG patches / updates
•   Install PKG Content

Install category for IcE-RX Media Manager modified (XMBM +) app/home/PS3_GAME / -> Launch Application (emulation) Homebrew category for app / tool PKGs Package Installer has been translated










Source News : IceMan Modz



Life4Beers

7
Developer $n!pR has updated PKG ToolKit GUI to support naehrwert’s scetool which allows you to encrypt and decrypt ELF and SELF files. This application needs Microsoft .NET Framework 4 to run.
Quote from developer this is my GUI for the signing tools from geohot. I might expand it to include other tools later. Tested working with the couple apps I made so hopefully it works just as good for anyone else who wants to try it

Quote
Changelog:
- [Version 1.40]
- Added AllUnpkg tool.
- Can now decrypt retail and debug packages.
- Option of creating debug or retail packages.
- Changed how log output is handled.
- Autodetect Title ID of PKG.





Source News : PS3HAX

Life4Beers

8
Hardware & Technical / Downgradable PS3 Models trimmed down charts
« on: 10 November 2012 à 15:56:19 »
Downgradable PS3 Models

Don’t know if your PS3 is downgradable, what’s the lowest firmware it can go or how to find what model you have? Then check this article out.
So with the explosion of the PlayStation 3 scene there have been a plethora of questions pertaining to the PS3 and downgrading. So with that in mind I gathered all the information together in one convenient post that will help you find out the answers!

FAQ

Q.) Can CFW be installed on 4.xx OFW?
A.) NO, you need to DOWNGRADE to 3.55 Firmware. when DEVS FIND A WAY FOR IT TO BE INSTALLED ON A HIGHER FW IT’LL BE ANNOUNCED, PATIENCE.

Q.) Can i Software Downgrade from 4.xx OFW?
A.) NO, THE ONLY WAY RIGHT NOW IS TO use a Hardware Flasher, (E3, Progskeet ECT) IT CAN BE COMPLICATED SO BE CAREFUL.

Q.) Can i brick my PS3 installing a 4.xx CFW?
A.) Yes, bricking CAN OCCUR WHEN ALTERING A CONSOLE OTHER THAN INTENDED. USERS ARE REPORTING BRICKS, IF YOU ATTEMPT READ CAREFULLY AND TAKE YOUR TIME.

Q.) Can i brick my PS3 by downgrading?
A.) YES you can, HOWEVER SOME BRICKS CAN BE REVERSED. IF YOU BRICK YOUR CONSOLE IN ANY WAY, YOU ARE RESPONSIBLE.
How to find a PS3′s Model Number

To locate the model of your PlayStation 3, look on the back of the system and locate the bar code sticker. Underneath the bar code you will see the 11-digit serial number followed by a model number which begins with “CECH”. You can also find the model number by looking on the box. It can be found by looking on the top of the box (the side where the handle is located) and is printed below the contents of whats inside the box

You can download pdf file for Downgradable PS3 Models trimmed down charts  and other information






Life4Beer

9
Software / MinVerChk - Determine Minimum Downgrade Firmware Check Tool
« on: 10 November 2012 à 14:57:22 »
Determine the base firmware of your PS3 with a few steps and images.

The first thing you have to do is:

- A PS3.
- MinVerChk
- USB flash drive


1 - Transfer the MinVerChk file to a USB flash drive, as if it were an upgrade (e.g. x:/PS3/UPDATE/PS3UPDAT.PUP).
2 - Insert the USB flash drive into the PS3.
3 - Install the update from XMB (This will fail and display the Firmware Base).


after running the tool if it says your base firmware is 3.55 or below then you can downgrade, in order to downgrade you will need to buy a hardware flasher such as the e3 flasher or Progskeet.

MinVerChk File



Dummies Guide



10
Software / W11Modder v1.0beta AiO firmware 3.0 up to 4.3
« on: 09 November 2012 à 22:15:56 »
The Australian developer OzchipsDev who also release x360RGH GUI has today release his new soft mod AiO W11Modder GUI, The GUI enables you to mod your nintendo wii firmware from 3.0 to 4.3. The GUI also enables you to include hackmii bundle and other packages like WiiFlow, GX Loader, Pimp My Wii & and many other packaes.

Quote
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
(¯`·.¸¸.·´¯`·.¸¸.-> W11Modder GUI 1.0 beta – By Ozchips Development <-.¸¸.·´¯`·.¸¸.·´¯)
 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
****************
 * Requirements *
 ****************
 
- Microsoft .NET Framework 4.0 or later
 - SD card 2GB
 - internet connection
 
****************
 * What it does *
 ****************
 
***********
 * Credits *
 ***********
 
Thanks :
 
- Thanks to Giantpune for wilbrand
 - Razkar for his great Homebrew-connection channels www.homebrew-connection.org
 - All Developers for there apps bundles
 - All beta testers and anyone else I have forgotten
 - A Special thanks to HDCM for all his kind words on my app also being a total tool – keep finger typing your command prompts mate….. Loser!
 
while the rest of the world & Big Scene Members enjoys the simplicity of GUI’s…….
 
Ozchips Development – Since 1996
 www.ozchips.net




Life4Beers

11
Following up on my previous update, today the developer decided to take his PS3 Resigner Script even further and came up with something he is very excited about - he present to you CFW 4.xx+ F.A.R. Script v0.5b (F.A.R. standing for "Full Auto Resigner" ^^).
 
Changes since previous Resigner Script:
 
Automatically unpacks, resigns, finds/adds "Content and Title ID" to package.conf and repacks .pkg files (Just drag and drop your .pkg file on the "CFW 4.xx+F.A.R. Script (Drag Here).bat")
 Automatically detects if the input file is an EBOOT.BIN and is able resign DISC and NPDRM EBOOT.BIN's (Drag and drop the EBOOT.BIN on the .bat and select DISC or NPDRM at the prompt)
 Automatically makes a .BAK (backup) of your original EBOOT in it's source folder.
 

 


Source: PS3 News

Life4Beer

12
Tutorials/Guides / Xbox 360 Error Codes Guide
« on: 30 October 2012 à 09:40:43 »
    THIS ERROR CODE GUIDE

    As it states it is only rough guide and it may contain errors
     
    --==ERROR Codes==--
     If there is a problem with the Xbox360 The LEDs in the ring of light will flash in a particular pattern. The pattern itself leads some insight to the problem. Certain patterns will lead to numbered error codes which will provide further insight to the problem. The numbered error codes are described below their corresponding LED code.
     
    =============================
     Manufacture Mode
     Sections 1, 2, 3, and 4 are flashing red and green
     

    =============================
     
    THINGS TO TRY
     
    •If you attempted the JTAG hack restore your original NAND image
     •Reflow Southbridge
     
    =============================
     
    Console displays no Red lights. But outputs no audio or video.
     

    THINGS TO TRY
     •Reflow the GPU and HANA Chips
     

    =============================
     
    Sections 1, 2, 3, and 4 are flashing red
     - The AV cable cannot be detected
     
    THINGS TO TRY
     •Make sure that the AV cable is correctly connected to the Xbox 360 console.
     •Disconnect the AV cable from the Xbox 360 console, and then reconnect the AV cable to the Xbox 360 console.
     •If the four flashing red lights continue to flash, try wiping the metal area of the AV pack with a dry cloth. The metal area is the end that plugs into the console. Wipe the metal area thoroughly, and then try the AV Pack again.
     •If the AV cable is correctly connected but the four red lights are still flashing, substitute a different AV cable if you have one available.
     
    =============================
     
    Sections 1, 3, and 4 are flashing red
     - General Hardware Failure
     

    Check the secondary Error Code per the instructions in the section below
     
    THINGS TO TRY
     

    •Try restarting the console.
     •If restarting the console does not resolve the behavior, follow these steps:
     •Turn the console off.
     •Unplug all the power and AV cables from the console.
     •Unplug the power cord from the wall socket.
     •Firmly reconnect all the cables.
     •Turn on the console.
     
    * If these steps do not resolve the behavior, turn the console off, remove the hard drive, and then turn on the console. If the 3x Red LED error light is no longer displayed, turn the console off, re-attach the hard drive, and then turn on the console.
     * Also examine the lights on the power supply. When you turn on the console, the power supply light should illuminate green even if the three lights on the RoL flash red.
     
    =============================
     
    Sections 1, and 3 are flashing red
     - Overheating
     
    Alternatively Overheating can be cause by the console locking up or "freezing" after a set amount of time. Lockups that occur at a specific point in a game are generally problems with the game itself and not caused by overheating.
     
    THINGS TO TRY
     
    •Let the Xbox 360 console cool.
     •Note You may have to wait several hours for the console to cool enough. Do not turn on the console when the console is hot.
     •Verify that the console has sufficient ventilation and that the fan is operating. For more information about ventilation, see the "More Information" section.
     
    PREVENTION SUGGESTIONS
     To try to prevent this problem, use the following precautions:
     
    •Do not block any ventilation openings on the Xbox 360 console.
     •Do not put the Xbox 360 console on a bed, on a sofa, or on any other soft surface that may block ventilation openings.
     •Do not put the Xbox 360 console in a confined space, such as a bookcase, a rack, or a stereo cabinet, unless the space is well-ventilated.
     •Do not put the Xbox 360 console near any heat source, such as a radiator, a heat register, a stove, or an amplifier.
     
    DO NOT EVER PUT YOUR CONSOLE IN THE FREEZER OR OUT IN COLD WEATHER
     Some people think that doing this might help "fix" an overheating console, in fact doing so could cause even bigger problems. Electronic devices like your console are made to function at and around room temperature, extreme cold temperatures can often cause just as many problems as extreme warm temperatures (such as overheating). Also if the console is located in a dramatically cold area while running, the difference in temperature between the hot console and cold air can create condensation which in turn will short out your console making the situation far worse. Condensation will happen more quickly if your console is overheating due to the greater difference in temperature. In short... DON'T DO IT.
     
    A more aggressive Solution to overheating is to improve the cooling system of the console. The best solution is to replace the thermal compound. If you attempt this you do so at your own risk. If you're console is still under warranty it is recommended that you contact MS for a replacement before attempting to fix it yourself.
     
    =============================
     
    Section 4 is flashing red
     - Hardware Failure
     
    The Specific Type of hardware failure can be determined by the error code displayed on the screen.
     If the screen is blank or you would like additional information follow the instructions for determining the secondary error code in the section below
     E11. Its when you have both heatsinks off the xbox 360 and you try to run it.
     
    E64 - This error occurs if something goes wrong while flashing the drive or installing a modchip.A sign for it is that the dvd-drive doesnt eject the tray anymore. DVD drive timed out during reset. It can also be caused by a faulty DVD power or SATA cables(edsondario & Fios89)
     

    E65 - This error occurs if something goes wrong while flashing the drive or installing a modchip. A sign for it is that the dvd-drive can still be flashed and read out. According to XBH: DVD drive is not DMA configured
     
    E66 - This error occurs when you replace the dvd-drive and forget to spoof it with the correct version string of the drive you replaced....
     
    E67 - This error occurs when your harddrive is defective, it might still work sometimes....Hard drive timed out during reset. There is also a small chance that it is a cold joint under the Southbridge causing problems with the I/O of the HDD.
     
    E68 - This error occurs when your harddrive is defective, it might still work sometimes.... It can also happen because of a bad eeprom or a wrong security sector.It can also be a problem with the internal connection of the harddrive to the mainboard...According to XBH: Hard drive not DMA configured
     
    E69 - This error occurs when your harddrives security sector is unreadable, if you have played around with that make sure to have the correct security sector on the drive. However it could also just be defective and trigger the error because of that.
     
    E70 - HDD Error (Corrupt Filesystem/partitions) or Hard drive not found
     
    E71 - This error is related to a failed dashboard update, can also be NAND related if you have an Infectus chip. It can also often be caused by a cold joint under the Southbridge(if it wasnt caused by an update). According to XBH: Error within Xam
     
    E72 - This error is related to a loose pin or a not existent NAND chip, can also happen if you flashed it badly with an Infectus chip and/or the NAND is dead. According to XBH: Error within Xam
     
    E73 - This error is caused by a cold solder joint under the Southbridge or the ethernet chip.In rare cases it can also be triggered by a cold joint under the GPU on one of the lines that run to the Southbridge chip. And missing parts(caps, resistors...) under the Southbridge can trigger this error as well.
     
    E74 - This error is caused by a cold solder joint under the GPU, (H)ANA-chip or in between. Mostly it is one of the outer solder balls on the side facing the (H)ANA chip so a shim increases the chanced of success quite a bit. Can also be a component that is missing or damaged so look for missing parts near the GPU and the (H)ANA chip.
     
    E75 - This error is related to the network chip, might be power related or so.This can happen while installing and NME 2. In general it sounds like a cold solder joint somewhere there.However it can also be a Hitachi DVD-drive that is not connected... According to XBH: Couldn't read ethernet phy vendor/wrong ethernet vendor
     
    E76 - This error is caused by a dead network chip.This can happen when a lightning hits your house and the network chip is under high voltage. According to XBH: Couldn't complete ethernet reset
     
    E77 - This error is caused by a dead network chip. It can occur when your house gets hit in a thunderstorm. According to XBH: phy request is already processing/ reading reg failed/ Failed to write reg
     
    E78 - AsicId check failed
     
    E79 - This error occurs when your harddrive is defective, it might still work sometimes....
     There is also a small chance that it is a cold joint under the Southbridge causing problems with the I/O of the HDD. It can also be related to wiring the diodes while JTAGGING. Couldn't start xam.xex
     
    E80 - Wrong LDV version in NAND Flash. You have the new dashboard update but not the resistor R3T6, follow known fixes to see how to resolve the problem.
     
    =============================
     
    --==SECONDARY ERROR CODES==-
     The specific type of hardware failure can be determined by a "hidden" error code
     


    1.Turn the xbox 360 on, and wait till the 3 red lights are flashing.
     2.Press and hold the sync up button (the small white one), while holding that button press the eject button.
     3.The LEDs will now blink the first number in the code (as described below).
     4.Release the eject button and press it again.
     5.The LEDs will now blink the second number of the code.
     6.Release the eject button and press it again.
     7.The LEDs will now blink the third number of the code.
     8.Release the eject button and press it again.
     9.The LEDs will now blink the forth number of the code.
     10.Release the eject button and press it again.
     11.The LEDs will go back to the 3 red flashing lights.
     

    You should be able to determine the difference between the 3 flashing lights and the error code lights by the rate in which they flash.
     
    Here is how you interpret the LEDs to get the code number:
     
    * All four lights flashing - 0
     * One light flashing - 1
     * Two Lights flashing - 2
     * Three lights flashing - 3
     
    0000 - The Xbox doesnt know whats wrong it freezes after showing the first digit(0) of the error code.Might be a cold solder joint somewhere under the GPU as someone fixed it with the X-Clamp replacement, might also be scaler or Southbridge related since this is where the error code is calculated...
     
    0001 - power supply problem
     
    0002 - Network Interface problem
     
    0003 - Power problem could be the PSU could be the GPU/CPU, somehow the console isn't getting clean power from the power supply.
     

    0010 - There is a problem with the Southbridge Chip usually dealing with how it connects to the mainboard (cold solder joint/bridged solder joints)
     
    0011 - CPU over heating - If you are receiving this error after disassembling your console make sure to all 8 of the heatsinc screws are tightened securely to the board/heatsink holes.
     
    0012 - GPU over heating
     
    0013 - RAM over heating
     
    0020 - This error is caused by a bridged solder joint under CPU, GPU or one of the RAM bricks.
     This effect can also be caused by tin whiskers leading to shorts and if the GPU was taken off the mainboard this error will also show up.
     It can also be power related(the CPU/GPU or RAM isnt getting enough power). Can also be a component that is missing or damaged so look for missing and bridged parts near the GPU.
     If the console was jtagged and the resistors and cables are still connected it will show 0020, the parallel port can stay as long as no PC is connected.
     
    0021 - This can be caused by two completely different things either:
     A. DVD Drive Time out - Can be caused by problems with a firmware flash. This is also speculated to sometime be caused by a problem with the southbridge chipset on the motherboard based on how it connects to the DVD drive.
     B. GPU error, generally caused by a poor connection to the mainboard (cold solder joints/bridged solder joints) See error 102 for more information
     
    0022 - CPU error, generally caused by a poor connection to the mainboard (cold solder joints/bridged solder joints). This can also be triggered by an error with the TSOP.
     
    0023 - This error is unknown but assumed to be a short either under Southbridge and (H)ANA chip or in between these.Look for 0021 and 0022 and reflow the Southbridge-> HANA chip area, the X-Clamp Fix might help as well.
     
    0030 - Problem with temperature control sensor
     
    0031 - This error is caused by a faulty/cracked RAM brick, however it can also be caused when the heatsink is shorting out a resistor or like a bad solder joint under the GPU. Also caused by the Southbridge if not properly soldered to motherboard or if it experiences a power short. Can be caused by a backwards power cord or faulty power cord to dvd player.
     
    0032 - Might be temp sensor related, check out 0030
     
    0033 - Might be temp sensor related, check out 0030
     
    0100 - There is a problem with the Southbridge Chip usually dealing with how it connects to the mainboard (cold solder joint/bridged solder joints)
     
    0101 - This error is caused by bridged solder joints under the USB ports or a defective USB device that is connected to it.
     
    0102 - Error in the "Digital Backbone" (CPU/GPU/RAM), this is usually caused by a cold solder joint between the GPU and the mainboard.
     There are two theories to fixing this one deals with the "X" clamps that hold down the chips. The other involves re-Heating the chips. DO NOT attempt either of these if your console is still under warranty. If your console is still under warranty return it to the store where it was purchased or call MS to have it replaced.
     
0103 GPU Error this is usually caused by bridged solder points where the GPU connects to the mainboard. see error 0102 for more detailed information
 
0110 - Ram error, this is caused by a cold or bridged solder joint on one of the Ram chips.
 

0200 - This error is caused by a Cold Joint in the GPU/RAM area similiar to 0102 good results could be achieved with flushing alcohol under the chips, reflowing them and afterwards applying an X-Clamp Fix.
 
0201- The error is very rare but it is somehow GPU/RAM related, two people could fix it with the Improved X-Clamp replacement, one had to remove his washers from the RAM in order to get it to work. Check the references for more information.
 
0220- This error is unknown but is assumed to be caused by missing resistors, probably on GPU.
 
0222- This error is unknown but someone managed to fix it using the X-Clamp replacement.
 
0232- "The DVD Drive overheats. This error can be caused by the disconnecting of the DVD Drive. This is usually not the case."(Unconfirmed)
 
1000 - Kernel can't be launched/signature in NAND Flash chip is broken! It could be possible after bad update. http://forums.xbox-s...p;#entry4156375
 
1001 - DVD Drive Error, either incorrect firmware or DVD Time out.
 
1002 - (not yet known)
 
1003 - Hard Drive Error... It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it
 
1010 - Hard Drive Error, Can be caused buy a corrupt or missing eProm. See also E68 above
 
1011 - This error occurs when your harddrives security sector is unreadable, if you have played around with that make sure to have the correct security sector on the drive....
 
1012 - HDD Error (Corrupt Filesystem/partitions) or Hard drive not found
 
1013 - This error is related to a failed dashboard update, can also be NAND related if you have an Infectus chip. It can also often be caused by a cold joint under the Southbridge(if it wasnt caused by an update).
 
1020 - NAND issue (loose pin/ bad flash)
 
1021 - This error is caused by a cold solder joint under the Southbridge or the ethernet chip.In rare cases it can also be triggered by a cold joint under the GPU on one of the lines that run to the Southbridge chip.
 
1022 - There is high chance it's a scaler chip problem (the "ANA" or "HANA" chip near the AV cable connection) it can also be caused by a faulty AV cable so check that first. In some cases it is a problem with the GPU and may be repairable by doing the x-clamp replacement (see error 0102)
 
1023 - DVD drive not connected, connect DVD drive to boot
 
1030 - This error deals with the Ethernet port's controller chip, a dead chip may not cause the error but removing the Ethernet controller chip does, it may also be caused by other Ethernet related problems.
 
1031 - This error is caused by a dead network chip.
 
1032 - AsicId check failed
 
1033 - it could be cpu/gpu related or it could be psu related, not much info is known for sure. If you installed the JTAG hack on your console it may be related to the wiring being installed poorly.
 ...
 
1444 and up There is no "4" in the error codes four lights is a "0" go back and check your code again.
 
=============================
 
--==Console Reset Codes==--
 
Clear All Installed Game Updates and Console Cache
 •Go to the "system" blade
 •Select "memory"
 •Press Y on the HD symbol
 •Press X,X, Left Bumper, Right Bumper, X,X
 •A message will appear saying: "Do you want to perform maintenance on your Xbox 360 storage devices?"
 •Select Yes
 
Clear Any Failed system updates that cause the console to error.
 •With the console off, press and hold the sync up button (the small white one)
 •While holding the sync button press the power button to turn on the console
 •Continue to hold the sync button until the Console has booted up completely.
 •During the boot process the console should clear any failed updates, allowing you to use it normally.
 
=============================
 

13
Hardware & Technical / Rogero CEX-4.21 CFW v1.00 Free for All
« on: 25 October 2012 à 10:57:46 »
This was posted by Rogero a link is also supplied from the original forum taken from
http://www.tortuga-cove.com/forums/viewtopic.php?f=127&t=3636
Quote
After Testing with some bricked Slim consoles ( from updating to CFW4.21 ) with different friends and testers around the world,
I can confirm that Bricked consoles can be recovered back to CFW3.55 even if you didn't have a NOR Dump/Backup .


Requirements are:
1- a Hardware Flasher so you can read/write to the PS3 NOR flash
2- A Dongle with PSgrade payload (any old jailbreak dongle + PSGrade hex will do) used to Enter Factory Service Mode (FSM)
3- Rogero CEX3.55 v3.7 PUP

for more details about Recovering from the Brick please check this new thread ----> Brick-Recovery Procedure from CFW4.21 back to CFW3.55

Note:
- I didn't receive any Brick report from any FAT PS3 that updated to CFW4.21, so it seems FAT consoles are not being affected by the bug.

- Apparently only the last downgradable Slim models are affected (CECH-25xx with Datecode 1A and base FW version = 3.50)

- I Also know that there are also few Slims that bricked with model CECH-20xx but 90% of the reports were model
(CECH-25xx with Datecode 1A and base FW version = 3.50).

- The Brick may be caused by the boot-loaders not being written correctly into the NOR during the Update process.

Please note also that all the above info may not be 100% accurate,
things are still being worked on so nothing is confirmed at all and I don't promise anything about an updated CFW.





ATTENTION:

1- This CFW doesn't have LV1 checks disabled and can't be installed on Downgraded PS3 consoles unless you have Dehashed/Reset Syscon Properly (if you're not sure about your PS3, Dehash it anyway to avoid any risk) Link ----> Dehashing Tutorial


2- Always make a NOR/Nand dump using multiMAN or memdump before installing this CFW to have a recovery backup in case of any bricks.
Having a valid NOR/Nand dump is an essential step before upgrading, because you will always have a way to recover (using hardware flashers) when you have a valid dump.
** A Hardware Flasher alone without a valid dump cannot fix your bricked PS3 **


3- The QA flag must be always Enabled on your PS3 for safer upgrading/downgrading operations. Link ----> toggle_qa.pkg


4- Always use the Recovery Menu while installing this CFW to avoid possible bricks (XMB update works, but Recovery Menu is safer).


5- TrueBlue CFW users must update back to OFW3.55 before installing this CFW to avoid possible bricks.


6- Please Check the MD5 of the downloaded PUP file before installing this CFW to avoid possible bricks. Many users who reported about bricks have had a different PUP MD5 checksum probably due to the large download rate on the download links/servers. If your PUP MD5 didn't match this MD5 : 418b6d659ba7201b04247618929e73ff Please re-download the file.



Links removed until the weird bricking issues are resolved...


MD5: 418b6d659ba7201b04247618929e73ff

Size : 192 MB (201,814,594 bytes)

v1.00 Info
- This is a 4.21CFW spoofed to version 4.25 to allow SEN access
- It can be used as a normal System Update from any 3.55 OFW/CFW/MFW
- It was tested using a hardware flasher and no bricks or any problems at all were encountered
- It can run games signed with Keys up to version 4.21 without any Eboot/Sprx patching needed
- Games must be loaded from Disc Icon (with Original game in BD) and not from app_home
- Current 3.55 homebrew application can't be loaded on this CFW, applications must be re-signed properly.

- Downgrading back to 3.55 is always possible using the following steps :
- Download the 4.25 downgrader PUP ---> 4.25 Downgrader Size 176MB (184,595,263 bytes) MD5: 49d80e07fc1f5ca1b0840e02e94635db
- Rename the downloaded file to "PS3UPDAT.PUP" and put it on your USB in: "USB\PS3\UPDATE\PS3UPDAT.PUP"
- While on Rogero CFW4.21, go to System Update from XMB and install the 4.25 downgrader CFW.
- Once installed, now put "Rogero CEX-3.55 CFW V3.7" on your USB in: "USB\PS3\UPDATE\PS3UPDAT.PUP" ---> Rogero CEX-3.55 CFW V3.7.PUP
- Start the PS3 into Recovery Menu and install "Rogero CEX-3.55 CFW V3.7" (from Recovery Menu, this is important)
- Once the install is finished, you're now back on Rogero CFW3.55 v3.7 (from here it's better to dehash again before installing any other OFW/CFW 3.55)

Credits to eussNL and the PS3DevWiki for the valuable and always up-to-date source of information.
Credits to Deank for his continuous efforts on Multiman and many other PS3 tools/fixes.


You need to already be on 3.55 to install this. Installing from any firmware other than 3.55 will simply not work

Life4Beers

Pages: [1]
emails