Jump to content
RealModScene

Leaderboard


Popular Content

Showing content with the highest reputation on 10/16/16 in all areas

  1. 2 points
    As I see, the problem still not resolved. So, if you still have a problems with this hosting, I can host your scripts on my hosting. Contact me, If your need my help.
  2. 1 point
    This tutorial is only for those of you who; lost all of their original and hack nand dumps + erased/corrupted the nand/flash the wrong image to the nand. If you find yourself in this situation then this tutorial will walk you step by step to make your console boot hack dash again. Take note that you won't be able to restore your console to retail ever again and you will be unable to use your dvd drive until you extract the key off of it. Things you will need; usb spi nand programmer(nand-x, jr-programmer, any will do(eMMC R/W kit for corona 4gb) J-Runner the ultimate JTAG/RGH app DOWNLOAD Extracted nand files that match you motherboard model (download below) Step 1; Recovery of cpu key and LDV's Download one of the clean extracted donor nand files according to your motherboard model and extract the containing folder to the location of your choice; Don't use these files to unban your console, first you don't have the original cpu key and second they are all from ban consoles. You have been warned! corona 4gb.rar corona 16mb.rar falcon opus.rar jasper bb.rar jasper sb.rar trinity.rar trinitynofcrt.rar xenon.rar zephyr.rar Next you need to solder/plug in your nand programmer wires onto the motherboard Open J-Runner app an click on "show working folder" button located at the bottom right Open the folder name "data" located inside /J-Runner/xeBuild/ folders Open your extracted nand files folder and copy and paste KV.bin, SMC.bin, smc_config.bin and fcrt.bin(if required) to data folder. It should look like this. In J-Runner, copy and paste this cpu key F37C0CD50B928F4E67614ACD548A4E49 in the cpu key section. Choose dashboard version according your hack type (for JTAG choose 7371 - for phat rgh1 choose 14699 - for R-JTAG choose 15574 - for phat RGH2 choose 14719 - for slim choose anything above 14719) Select your motherboard nand type. Select retail as your image type. It should look like this. In J-Runner under the Advanced tab click on Create an image without nanddump.bin Then you will be ask to enter LDV just enter any number between 1 and 80 and click ok. At this point the dummy image should be successfully created and automatically loaded in the "Load Source" section. Now with your nand programmer properly connected to both you pc and motherboard click on "Write Nand". Wait until J-Runner is finish writing the nand and select your "hack type" then click on "Create ECC" for rgh machine or "Create Xell-Reloaded" for JTAG/R-JTAG machine. Now click on "Write ECC" or "Write Xell-Reloaded" depending on your hack type. You are now ready to boot xell and recover your cpu key. Power on your console and wait for xell to boot. Once xell as booted write down your cpu key, fuseset 02 and fuseset 07 Understanding and calculating LDV's Calculating CF/CG ldv is fairly simple. Just count the number of "F" in fuseset 07 to fuseset 11. So in the example above we have a cf/cg lock down value of 2. Calculating CB LDV can be a little bit more trickier. You have to take the right-most "F" and calculate how many character it is from the left. In the example above the right-most "F" is 5 characters from the left so we have a cb lock down value of 5. Understanding CB LDV; Quote from Martin C @ TX Quote This value is NOT updated every dashboard version and is not directly reflected in any apps. However, the value can be translated to a CB/dashboard version. You cannot 'edit' your image to use a different CB for a retail NAND. It MUST match the entry as found in XeLL, otherwise it'll fail to boot. The example above is from a Jasper with a cb ldv cseq of 5 and by looking at the chart below we can determine that dashboard 7371 would be the highest version acceptable for this particular console. Step 2; Building the fake OG nand image Now back in J-Runner, enter your cpu key in the cpu key section. Select your dashboard according to your CB LDV cseq Select Retail as Image type. Select Motherboard nand type. Click on the "Advanced" tab and on "create an image without nanddump.bin" You will be ask for LDV, this is the cf/cg LDV so you enter what you have in fuseset 07 and click "ok" You have now created a fake original nand image. Even though you won't be able to boot your console with this image it would still be a good idea to keep it somewhere safe. With your new image loaded in the "Load Source" section and your cpu key in the "Cpu Key" section click on the "kv info" tab. You will noticed that the info in there are obviously not from your console. So now would be a good time, for those who can, to extract your dvd drive key and patch the key vault with the appropriate dvd key. Click on the "XB Settings" tab, click on "Advanced XeBuild Options", paste your dvd key in the "dvdkey" section, click "OK" then click the "Use Edited Options" check box. For DG16D5S and DLN10N owners; the easiest and cheapest way to make your dvd drive functional would be to install a TX LTU 2 pcb. Final Part; Building/writing your hack image Back in J-Runner, with your new fake original nand image loaded in the "Load Source" section and cpu key in the "Cpu Key" section select hack image type(Jtag - rgh - rgh2 - r-jtag), select your desired dashboard(should be the latest which is 16537 at the moment of write), select motherboard nand type. You can also edit dashlaunch and xeBuild options at this point. Click on create xeBuild image. You will see 3 or 4 warning messages poping up which will ask you if you want to delete kv.bin, smc.bin, fcrt.bin and smc_config.bin. Click yes on all of them. With your nand programmer properly connected to both your console and pc click on "Write Nand" ​ Boot your console and have fun.
  3. 1 point
    As I promise the Blur skin (Aurora 0.6b) is ready for download in December 2016. Previews: Download: Blur-version 1.0.xzp After installation, load the skin and press "Back Button" to open the menu and select the "View Settings", after that go to "Theme" and Select "Blur [x1024]" Cover Layout for better looking. For best looking disable Animate Background. Thank You for support and Liked my skin. (Updated at December 6, 2016)
  4. 1 point
    sup homies? 17502? The latest builds of XeBuild by Team xeBuild,Xebuild GUI by swizzy and DashLaunch by c0z have been released with support for the latest update by Microsoft. Check out the dl links bellow to get these great releases. http://www.realmodscene.com/index.php?/topic/6843-xebuild-117-xebuild-gui-2098-17502-kernel-support-added/ http://www.realmodscene.com/index.php?/topic/6842-dashlaunch-317-17502-kernel-support-added/
  5. 1 point
    Hi everyone! I got a jasper xbox, that someone tried to RGH1.2, but failed so i got it for cheap. After i got it i wrote the stock nand back, and removed RGH wiring, but i got an RROD after 7 seconds with the secondary error code 0022, so i checked the PLL_BYPASS area and sure enough the 10K pll bypass resistor was missing, so i replaced it with a 10K 1/4 w resistor between PLL and CPU_RST, but it still throws the same RROD. Does anyone have an idea what it could be? Maybe a dead cpu? PS: Please note that i'm sure this is not an LDV problem, becouse the stock nand worked fine, before the RGH.
  6. 1 point
    How did you create the RGloader image without a dump, as you still need the KV, SMC, SMC_Config, etc from the nand when you build RGloader. You might be able to dump the nand you have, and run it through XeBuild Gui, and recreate a working image. Does it show you your DVD key when you boot xell? if so, all is not lost.
  7. 1 point
    Update to the latest 2.0.17502.0 RGH Dash. You can use Swizzys XeBuild GUI. If you need heelp, take a look into this Guide.
  8. 1 point
    Useful Tools: Latest multiMAN eEID Root Key Dumper (3.55) eEID Root Key Dumper (4.50) Latest PPC+ Latest Showtime Latest mmTOOLS Latest reActPSN CFWs: Latest Rebug CFWs Latest Rogero CFW Latest ZER0 (HABIB) Here are the guides for installing the latest 4.xx CFWs on your PS3: If you're on OFW higher than 3.55, you CAN'T install CFW directly! You need to check if your model is old enough to be hackable (older than June 2011). If you're lucky enough and it is hackable, you can use a hardware flasher (NOR Guide | NAND Guide) to dump your 3.56+ flash, patch it and re-flash it before you can install CFW using the guides below. If your PS3 is not hackable, you CAN'T install CFW at all. Your only option would be to install an ODE to be able to run homebrew and backups. If you're already on CFW, you can always start with the 2 (optional) steps below before installing the CFW of your choice: Dump your NOR/NAND Flash: Download and install the latest version of multiMAN (CEX) from the link above, plug in a FAT32 formatted USB flash drive into the right USB port, launch multiMAN under the Game column and go to mmOS > Press O on any file > Open in HEX viewer > Press SELECT > Press START > Export GameOS LV2: Select No > Export HV LV1: Select No > Export FLASH: Select Yes This creates a backup of your NOR/NAND flash so that you can recover using a hardware flasher in case of a (highly unlikely) brick. It is recommended to do it every time you upgrade/downgrade your CFW just in case something goes wrong. Dump your eEID Root Key: This has to be done only once, while (and if) still on 3.55/4.50 CFW, just in case you want to ever switch to DEX in the future without having to downgrade back to 3.55/4.50 CFW to dump it. Download and install the correct eEID_RKDumper.pkg for your CFW version (3.55/4.50) > Unplug all USB devices > Launch eEID RKDumper under the Game column. It will black screen for 10-15 seconds, beep 3 times and reboot automatically. Now FTP to your console and retrieve your Root Key/PCK1 (48 bytes) from /dev_hdd0/tmp/eid_root_key if on 3.55 or /dev_hdd0/game/FLTZ00010/USRDIR/eid_root_key if on 4.50. Once you retrieve your Root Key, you can delete eEID RKDumper from your XMB as it is not needed anymore. Rebug 4.46.1 LITE: This CFW can only be installed on top of CEX FWs. If you're on a DEX FW, you have to convert to CEX before you can install this CFW. If you don't know what CEX/DEX is, you're most likely on a CEX FW. If you're on 3.55 or lower OFW, or a hardware flasher patched 3.56+ OFW, or any 4.46 or lower CFW, you can install Rebug 4.46.1 LITE from XMB by following the guide below: 1- Install Rebug 4.46.1 LITE from XMB: Download the latest Rebug LITE from the link above, verify the md5 hash with @DEFAULTDNB 's PPC+, rename the PUP to PS3UPDAT.PUP, put it on your FAT32 formatted flash drive in PS3UPDATE, go to System Update and Update via Storage Media. Make sure there's NO original game disk in the drive, NO game is mounted and that you DON'T Update via Internet or else you would risk installing OFW >3.55! 2- Enable QA: Go to Package Manager > Install Package Files > PS3 Hard Disk and install Rebug Toolbox. Launch it under the Game column, go to Utilities and change Toggle QA Flag to Enabled. This is to ensure easier and safer downgrading. Notes: OFW 4.55 has been released, make sure you don't accidentally update. You also need a spoofer to connect to PSN (with ban risk). Make sure you use mM 4.46.00 or higher because older versions are not compatible with this CFW. Make sure you install the Rebug Toolbox pkg included inside Package Manager because older versions are not compatible with this CFW. Make sure you use reActPSN v2.27 or higher because older versions might not be fully compatible with this CFW. Rebug 4.46.1 REX/D-REX: If you're on a CEX FW, you have to install the REX Edition. If you're on a DEX FW, you have to install the D-REX Edition. If you're on 3.55 or lower OFW, or a hardware flasher patched 3.56+ OFW, or any 4.46 or lower CFW, you can install Rebug 4.46.1 REX/D-REX from XMB by following the guide below: 1- Install Rebug 4.46.1 REX/D-REX from XMB: Download the latest Rebug REX/D-REX from the link above, verify the md5 hash with @DEFAULTDNB 's PPC+, rename the PUP to PS3UPDAT.PUP, put it on your FAT32 formatted flash drive in PS3UPDATE, go to System Update and Update via Storage Media. Make sure there's NO original game disk in the drive, NO game is mounted and that you DON'T Update via Internet or else you would risk installing OFW >3.55! 2- Enable QA: Go to Package Manager > Install Package Files > PS3 Hard Disk and install Rebug Toolbox. Launch it under the Game column, go to Utilities and change Toggle QA Flag to Enabled. This is to ensure easier and safer downgrading. Notes: OFW 4.55 has been released, make sure you don't accidentally update. You also need a spoofer to connect to PSN (with ban risk). Make sure you use mM 4.46.02 or higher because older versions are not compatible with this CFW. Make sure you install the Rebug Toolbox pkg included inside Package Manager because older versions are not compatible with this CFW. Make sure you use reActPSN v2.27 or higher because older versions might not be fully compatible with this CFW. Rogero 4.55 v1.xx: This CFW can only be installed on top of CEX FWs. If you're on a DEX FW, you have to convert to CEX before you can install this CFW. If you don't know what CEX/DEX is, you're most likely on a CEX FW. If you're on 3.55 or lower OFW, or a hardware flasher patched 3.56+ OFW, or any 4.55 or lower CFW, you can install Rogero 4.55 v1.xx from XMB by following the guide below: 1- Install Rogero 4.55 v1.xx from XMB: Download the latest Rogero CFW from the link above, verify the md5 hash with @DEFAULTDNB 's PPC+, rename the PUP to PS3UPDAT.PUP, put it on your FAT32 formatted flash drive in PS3UPDATE, go to System Update and Update via Storage Media. Make sure there's NO original game disk in the drive, NO game is mounted and that you DON'T Update via Internet or else you would risk installing OFW >3.55! Notes: This CFW is built from OFW 4.55, so it prevents accidental updates to OFW >3.55 and allows PSN access (with ban risk) without the need for a spoofer. QA is enabled by default on this CFW. Make sure you use mM 4.55.00 or higher because older versions are not compatible with this CFW. Make sure you use reActPSN v3.12 or higher because older versions might not be fully compatible with this CFW. ZER0 (HABIB) 4.55 V1.xx: [iNSTALL AT YOUR OWN RISK] This CFW can only be installed on top of CEX FWs. If you're on a DEX FW, you have to convert to CEX before you can install this CFW. If you don't know what CEX/DEX is, you're most likely on a CEX FW. If you're on 3.55 or lower OFW, or a hardware flasher patched 3.56+ OFW, or any 4.55 or lower CFW, you can install ZER0 4.55 V1.xx from XMB by following the guide below: 1- Install ZER0 4.55 V1.xx from XMB: Download the latest ZER0 CFW from the link above, verify the md5 hash with @DEFAULTDNB 's PPC+, rename the PUP to PS3UPDAT.PUP, put it on your FAT32 formatted flash drive in PS3UPDATE, go to System Update and Update via Storage Media. Make sure there's NO original game disk in the drive, NO game is mounted and that you DON'T Update via Internet or else you would risk installing OFW >3.55! Notes: This CFW is built from OFW 4.55, so it prevents accidental updates to OFW >3.55 and allows PSN access (with ban risk) without the need for a spoofer. QA is not enabled by default on this CFW. Enable QA before installation. Make sure you use mM 4.55.00 or higher because older versions are not compatible with this CFW. Make sure you use reActPSN v3.12 or higher because older versions might not be fully compatible with this CFW.
×
×
  • Create New...