Jump to content


News Editor
  • Content count

  • Donations

  • Joined

  • Last visited

  • Days Won


zapptheman last won the day on August 1

zapptheman had the most liked content!


About zapptheman

  • User Group: News Editor

  • Title: New Programer

  • Post Count: 362

  • Post Ratio: 0.29

  • Total Rep: 255

  • Member Of The Days Won: 27

  • Joined: 03/22/2015

  • Been With Us For: 1245 Days

  • Last Activity:

  • Currently:


Contact Methods

Profile Information

  • Gender
    Not Telling
  • Location
    _a hood near you
  • Consoles I Own
    PS Vita
    Xbox 360
    Xbox One
    Nintendo DS
    Wii U

Recent Profile Visitors

3,190 profile views
  1. Yeah. This ps4 has lots of weird issues, previous owner tried to fix the BD drive which had the white thing that kept falling out inside, he completely cooked it man. He damaged the daughterboard (cut some traces which you can see in the images provided) and somehow, wireless does not work. The controller has to be in direct line of sight, less than 30 cm away from the ps4 or it will not connect, and of course the power and eject buttons now working lol. Lucky its just my 4.05 testbench. Terrible though. I don't know how he managed it
  2. But would the ribbon cable also affect the power button thats on the mainboard?
  3. Same issue with both power and eject button. If i touch the pad directly, it does not work 90% of the time. If i use the button, same thing, wont work 90% of the time. The other 10% is when the PS4 gets into a Mood and decided it wants to let the buttons work, and then they work for a bit and then stop again after a while. I can also confirm that the issue persists even when i swap logic boards to the new one
  4. Hi guys. Welcome to my first Raspberry Pi Tutorial. As usual, i have a video below showing how to achieve a simple installation and set up the OS to work how you want it to work. Below i will have some written instructions you can follow feel free to ask any questions you may have below. Video: Written Tutorial: What you will need: - Pi Kit - Wifi Dongle - Fan - Camera - Enclosure - Micro SD card (4GB or more) Optional Extras if you are adding the Alarm System: - Siren - 12V Power Supply - Relay - Wire - Jumper leads Downloads: - MotioneyeOS Image - Imaging tool for SD card - Putty (if you are adding extra buttons and features) WARNING! Before we continue, I am not responsible for anything you do which may damage any of your hardware, or cause you to loose any files/folders on your computer if you are not careful. Step 1 - You need to purchase the Pi and components to get this running. Step 2 - Download the appropriate downloads for the project\ Step 3 - Format your SD card to Fat 32 (insert into your PC and right click on it --> format --> Fat32 Step 4 - open Win32DiskImager and install it Step 5 - Open installed Win32DiskImager Step 6 - Click on the folder icon next to the drive letter and seek to the .img file you downloaded. Should be named something like "motioneyeos-raspberrypi3-dev20180712.img" Step 7 - Select the drive you want to install to (make sure this is your SD card otherwise you may wipe the wrong thing). Then click write, followed by Yes to continue. Step 8 - Once complete, safely eject the SD card and insert into your raspberry Pi. Step 9 - Connect your Pi to a USB keyboard, Ethernet, HDMI, and plug in the power cord to boot for the first time. If all worked well you should see a red light on your Pi, followed by a blinking green light. (if you don't see the green light blinking, check to see if there is any output on your screen, if not, you probably did not format the SD card correctly.) Step 10 - If the Pi booted successfully, you should see a terminal on screen. You should be able to login by typing 'Admin' as the username, and leave the Password blank, this should work. (if not, please let me know so i can try help you, you may be on a different version of the OS) Step 11 - If booted without any issues, you should now be able to access the lovely GUI webpage through your browser. You will need to find out the IP address of the PI, you can do this through your router, or with phone apps such as fing Step 12 - Once you know the IP address of your Pi, Enter it into your web browser of choice, and you should see the Lovely GUI pop up. Step 13 - Plug in your cameras via USB (i recommend using no more than 2 as the Pi may not be powerful enough to run them depending on the applications you are using them in) Step 14 - click on the 3 horizontal bars on the top left, then click the 'Add Camera Button' you can add the cameras here. Step 15 - Go through the settings and tweek them for your use. Step 16 - Set a Static IP so your Pi doesn't randomly change addresses on you Step 17 - That's it! if you are just setting up the simple version, you are done! Congrats!!! If you would like to know some more advanced things, stick around for more. Advanced: Step 18 - If you would like to receive email notifications whenever your camera senses motion, simply enable Motion Detection This can be enabled through the Motion Detection Menu. Step 19 - It is recommended to set up an email account which belongs to your PI with Gmail, and make sure it has been enabled to accept insecure sessions. Step 20 - You will need to put in the following details for Motion Notifications Email Addresses: <write your email address which you want the notifications sent to> SMTP Server: smtp.gmail.com SMTP Port: 587 SMTP Account: <Write the email address you created for your Pi to use> SMTP Password: <Write the password for the email address above here so the OS can access the account> From Address: <it is recommended you use the same address as the SMTP Account> Use TLD: "ON" Attached Pictures Time Span: <You will need to play with this time as it will be dependent on your internet speed, i would recommend putting it as low as you can before it starts sending emails without images. This is the time the device will wait for images to be uploaded before sending the email (i use 40) Step 21: Profit? That's it for the tutorial so far! I will be adding more info later about setting up the siren and switches for it. Once my video is up I will release the Write up detailing how i did it Hope you guys enjoyed. If i helped, please feel free to leave a like so i know you are interested in seeing more tutorials like this XD Let me know if there is anything you need help with or you think i could have improved on. Thumbnail:
  5. Hey mate, sorry for the late reply. Been a bit busy.. My work bench is currently a mess and i don't have room to take apart my PS4 XD But here is an image of the logic board i removed from the ps4 when i replaced it with a new one for some testing. The button on this works intermittently too. If you look carefully, you can also see where the previous owner cut the tracers on this logic board. Thanks for any help bud
  6. @BwE Hey mate, good to see you back! Kinda off topic, but would you by any chance know anything about why the power and eject buttons have stopped working on my ps4? they will randomly work for periods of time and then stop again. Might be a long shot but what the hell
  7. zapptheman

    i need a program to edit .pkg ps4 game

    I could make one but it's pretty straight forward. You need the FPKG tools @cfwprophet patched and you need to know the Password for the fpkg you are extracting. If its 32 0's then enter that as the password and away you go. Else, well you might just need to ask the person who released it what their PW is. The code to extract is as follows.... I see not many people have posted this around so hopfully it helps (put this into a batch file) To unpack pkg files with a passcode (full unpack): Make sure to replace the values for "Your_Package_Name" with the actual name of the PKG you are extracting orbis-pub-cmd.exe img_extract --passcode "00000000000000000000000000000000" in\your_package_name.pkg out\ Pause To unpack without a passcode (Partial unpack, will not be able to repack): Make sure to replace the values for "Your_Package_Name" with the actual name of the PKG you are extracting orbis-pub-cmd.exe img_extract --no_passcode in\your_package_name.pkg out\ Pause Keep in mind, you will need to create in "in" and "out" folders in the directory you are running this batch file from
  8. zapptheman

    The Winner Of The ESP8266 Wi-Fi Board For PS4 Is

    Congrats everyone! A very kind gesture from Greg! This is why this is the best forum!
  9. zapptheman

    [Tutorial] Advanced ★Debug Settings for PS4 on 4.05

    Sorry mate i am not sure how to do this, you might need to see what other people have done to fix this.
  10. I guess that's one way to go about it. Still would worry me too much XD
  11. Yeah it's pretty wild man XD i'm just waiting for the CFW's to develop more. I don't think i will be using the autorcm method. Seems too dangerous. Will also be waiting for devs to find a way to access online functions without ban hammer. Unless Nintendo makes online paid. Then who cares XD
  12. XD FSM is the most stable way to go about it but i don't think cfw is up to scratch yet. Apart from Xecuters... (which you need to pay for)
  13. Everything as long as it is the old revision of hardware. You can use the FSM jig and run CFW. Be warned the CFW is not yet finished
  14. zapptheman

    Win A ESP8266 Wi-Fi Board For PS4

    *Bump* We are looking for more entries. Tell your friends to enter for a chance to win one of these delux ESP8266 Wi-Fi Boards for ease of access with all your jailbreak hosting needs.
  15. This is likely because your PS4 has cached the website and is no longer attempting to pull it off the ESP chip. Do a connection test to make sure it is still connecting to the ESP chip, If not, you will need to reconnect it (might require a reflash if you cant do this from the ps4) If it is connected, then try loading the exploit by going through the web browser instead, go to the same link that you would go to when you open the user guide (just open user guide and write down the link and then write it into the normal browser) this will hopefully clear the cache. Test the hen payload and wait for it to say "You're all set" then click ok and the back button to take you back to to main exploit host menu and then test that the hen worked by looking to see if debug settings are present. If this worked, immediately shut down the PS4 or reboot it and then next time you go to user guide it should work a charm!