Jump to content

Kyle2100

Senior Member
  • Posts

    452
  • Joined

  • Last visited

Posts posted by Kyle2100

  1. As we receive tons of email asking us for more info and release date, here is a quick update on our product status.

    After a few days delay due to Chinese New Year, we have finally received our prototype boards, as can be expected from any development cycle, we have experienced a few issues with reliability of our entry point, we will work on refining our method and keep you posted, stay tuned for more exciting news and videos in the coming weeks.

    We are sorry for the delay, but we are also sure all Switch owners will be delighted by our product. It is worth the wait!

    NEWS RELEASED ON FEBRUARY 15th

  2. IMPORTANT: A 2.0 update has been released 
    Official support for v1.0 in this thread has come to an end.

    There has been alot of development going on around the PS3 since the discoveries of thePS3Xploit (webkit exploit) on 4.81 OFW, first we seen the IDPS dumper (4.81/2 OFWreleased with some big news & hope to come along with it, like a Flash Writer (downgrader) for OFW, so if you have been reluctant to buy a Hardware Flasher such as the E3 Flasher and bust open your PS3, but have been wanting to get your PS3 FAT(PHAT) Console and your Downgradable PS3 SLIM Models (up to & including 25xx models with minimum installable version <= 3.56) on Custom Firmware, then here is your chance with a 100% SOFTWARE SOLUTION thanks to the work of PS3Xploit Team ( @bguerville@esc0rtd3w & W)along with contributions from new team member @habib to help expedite this release. Essentially what this Software Solution does is write a patch to the CoreOS (on NOR/NAND Chip) and when the PS3 Console is then rebooted you can install a Custom Firmware directly, So downgrading back to 3.55 is not required in the process, rather "Direct OFW to CFW patching" is done to allow for Custom Firmware Installation. Since this exploit is executed from 4.82 OFW, you can only install to a 4.82 CFW, HOWEVER if you wish to use an earlier firmware such as REBUG 4.81 for example, once on 4.82 CFW you must TOGGLE QA using a toggle tool, which allows CFW user's to freely switch CFW version from past and present. Read more about this in the Frequently Asked Question (FAQ) and more info in the details provided:



    UPDATE - View Public Warning 
    BfEBwXb.jpg


    Flash Writer Compatible with these PS3 Models:
    Supports FAT ModelsCECHAxx/Bxx/Cxx/Exx/Gxx/Hxx/Jxx/Kxx/Lxx/Mxx/Pxx/Qxx
    Supports SLIM Models 2xxx (minver 3.56 or lower ONLY, check with >>> minverchk.pup - SEE FAQ TAB for USAGE )

     
    •  
      PS3 OFW 4.82 NAND/NOR FLASH WRITER v1.0
      ***** IMPORTANT DETAILS BELOW -- AVOIDING A BRICK *****

      WARNING: USE THE PROVIDED flsh.hex AS IS. DON'T PATCH IT OR MODIFY IT OR YOU WILL BRICK *****
      • Verify flsh.hex file on a flash drive and in the far right USB slot!
        • 4.82 flsh.hex MD5: 8E156C99101BF36EC3EDB832982AE46D
      • DO NOT USE ON CFW (Custom Firmware) (Only Supports OFW)
      • DO NOT USE ON PS3 Models 3xxx/4xxx (aka SuperSlims / Late Slim modelsyou will brick those console. 
      • USE ONLY ON 4.82 OFW


      PLEASE READ FIRST:
      • It's essential not to flood the browser memory with junk before running the exploit. The reason for this is that due to javascript core memory usage limitations we are scanning several times a small range of browser memory (a few Mb) to find some essential data in RAM, if the memory is flooded then the range to scan becomes much larger & the probabilities that our data is found in the smaller range decrease dramatically..
      • So in short, never use the browser or set a homepage you cancel before running the exploit!
      • If you need to, set the homepage to 'blank', close the browser then reopen it to start the flash writer.

      v1.0.0 - Initial Release
      • Supports Direct OFW to CFW patching for All Phat and 2xxx Slim (minver 3.56 Dec 2010 and lower)
      • the NOR/NAND writer will just copy 3Mb of CoreOS data to both ros0 & ros1 in the flash memory.
      • There is only one version released for 4.82. The same hex patch file can be used on nor & nand.
      • It's as safe as possible, with a check for usb device & patch file making the exploit hang instead of corrupting flash if file is not found.
      • In case of corruption (extremely rare but could always happen), it's only a partial brick because no per console info ever gets erased so a hardware flasher could still be used if ever a recovery reboot was impossible.
      Usage Tips:
      1) Try using a LAN connection or a solid WiFi connection during exploitation. A weak signal can cause problems.
      2) If the exploit takes more than 5 minutes to work, reload page, browser, or restart console and try again.
      3) If you are using a LAN connection and experience network issues, make sure all cables to router are in working order.

      Steps:
      1. Setup a small Web server on pc or smartphone. A custom miniweb application (from: https://sourceforge.net/projects/miniweb/files/) with small changes to the JaveScript, and supplied to host files if you would like to use it. Don't come to us for explanations about how to run a http server though. Google it.

      2. Extract the files from release to your http server root folder.
      2a- To use the miniweb.exe server, it is necessary to create a folder: htdocs
      2b- The files *.html and *.js included in the zip files should be copied/moved to htdocs
      3. Copy the "flsh.hex" file from release folder to root of flash drive.

      4. Put a FAT32 USB key in port closest to BD Drive (/dev_usb000).

      5. DOUBLE-CHECK your flash drive on XMB to make sure it shows up under Music, Photos, Videos, etc.

      6. Open the PS3 browser File Address window, write the IP address of your server (and the port if not 80) & press the Start button.

      7. Select the appropriate button for your console and wait for PS3 to power down. DO NOT STOP THE PROCESS ONCE STARTED!!

      8. Once PS3 has powered down, reboot console and install CFW matching OFW version. If installing through XMB does not work, boot to recovery and install.

    Downloads:
    UPDATE (JAN 2017) 
    VERSION 2.0 HAS BEEN RELEASED & NOW EVEN EASIER TO USE) >>> LINK <<<



    Courtesy of Team PS3Xploit:
    W (Javascript, Research & Testing)
    @esc0rtd3w (Debugging, Research & Testing)
    @habib (ROP & Debugging)
    @bguerville (ROP/Javascript & Debugging)
     
    Last edited: Jan 28, 2018
     
  3. 4 hours ago, joeajjan said:

    How to fix it when i enter a match the game freezes and lags alot is there any fix for that i don’t think that my phone doesn’t support this game i played before without any problem but now i don’t know what happened any help is appreciated

    What game 

  4. Required Items.

    • Jailbroken iDevice on iOS <=11.1.2
    • An sftp or on device file manager (Cyber Duck, FilzaJailed, Winscp, etc.)
    • Terminal Client
    • The latest version of bfinject: https://github.com/S...aga/sacmunCrack
    • To just sign apps use signer.sh - signer.sh

    Instructions

    [hide]1. If you are on Electra, reboot your device and re-jailbrake with the "Tweaks" option turned OFF. For LiberiOS, just run the jailbreak.IMG_0381.png

    1. Once jailbroken, create a new folder somewhere on your device called "bfinject" using one of the previously mentioned sftp or file managers. (I made my folder in /var/mobile/Documents/bfinject). You can do this with CyberDuck, or if you're using terminal, in your location type 
      mkdir bfinject
      
    2. Screen_Shot_2018_01_30_at_1_29_07_PM.png
    3. Download and move the bfinject.tar into the bfinject folder, wherever it is located on your iDevice.
    4. Screen_Shot_2018_01_30_at_1_30_25_PM.png                                                                  
    5. Using a Terminal client, ssh into your iDevice with
      ssh root@ipaddress
       and log in with your password. alpine is the default password to log in, unless you have changed it which is highly recommended.
    6. cd into the bfinject folder. For me that command will be
      cd /var/mobile/Documents/bfinject
      
    7. Run 
      tar xvf bfinject.tar

      to unpack the contents

    8.  Screen_Shot_2018_01_30_at_1_35_02_PM.png

    9. Now your bfinject folder should look like this, and if it is then you are ready for action.                                                                                                

    10. Screen_Shot_2018_01_30_at_8_38_41_PM.png

    11. Run the app that you want to crack, I will be using Reddit as an example

    12. Once your app is up an running, run

      bash bfinject -P app.app -l dylibs/bfdecrypt.dylib 

      Screen_Shot_2018_01_30_at_9_13_58_PM.png

    13. The app should start being cracked now. First you will see a floating UIView with "Decrypted" printed, followed by this screen.IMG_0382.png

    14. Now you have two options. You can set up a server by pressing "Yes" or you can do it another way. I have tried using the netcat server way but it didn't work for me, so I will show you an alternative way. Run the command (Still on your iDevice)

      find /var/mobile/Containers/Data/Application/ -name decrypted-app.ipa

      Screen_Shot_2018_01_30_at_8_59_26_PM.png

    15. As shown below, you will be presented the file location of the decrypted .ipa, and you can then transfer it from you iDevice on to your Mac/PC into your .ipa stash in preparation for Appsync to finally be published :). Make sure to delete the decrypted-app.ipa on your iDevice so that if you crack new apps you won't be confused by different cracked apps.

    16. Screen_Shot_2018_01_30_at_9_27_31_PM.png[\hide]

    • Like 1
    • Informative 1
  5. 1 minute ago, ozzeme said:

    Rename the main .deb file will cause issues?

    Didn’t rename,  I mistyped when I was doing it but didn’t install anyways.  It was just an example 

  6. 13 hours ago, Big Meechy said:

    Hey Kyle appreciate the guide but it’s way to vague, can you send screenshots of the step by step process? I did everything the same way you wrote it and no dice.

    Updated 

  7. 13 hours ago, Big Meechy said:

    Hey Kyle appreciate the guide but it’s way to vague, can you send screenshots of the step by step process? I did everything the same way you wrote it and no dice.

    Yes give me a bit 

    18 hours ago, fcelani said:

    Where am I supposed to write the 4th step? On filza?

    Once u hit install a terminal window will pop up and u type it.  Yes filza 

  8. Requirements :

    filza escaped 

    jailbroken phone/iPad 

    the .deb u want to install 

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    HOW TO INSTALL:

    1. Download the .deb 

    2. Place the deb into a folder you can get to easily with filza escaped 

    “I will be placing mine in /var/mobile/Containers/Data

     

     

    3.  Once copied to the folder you want click on the deb and hit install.

    https://imgur.com/gallery/04Udf

    ”it will fail and that’s ok”

    should look like this: https://imgur.com/gallery/VNKdf

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    4.  Now type this 

    su root 

     

    Cd /var/mobile/Containers/Data

     

    Hit Enter 

    https://imgur.com/gallery/mHIix

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Then Type: 

    dpkg -i “then deb name”

    examp: dpkg -i example.deb

    https://imgur.com/gallery/sKB4B

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

     

    after your type the deb name  hit enter and it should be installed, respring and enjoy

     

     

     

     

     

     

     

    • Like 4
    • Thanks 3
×
  • Create New...

Important Information

We would like to place cookies on your device to help make this website better. The website cannot give you the best user experience without cookies. You can accept or decline our cookies. You may also adjust your cookie settings. Privacy Policy - Guidelines