PS4 Controller not sync

[claudyu07]

hi guys . i've a situation here .
PS 4 turns on but the controller won't sync.
Safe mode working perfect usb only.
i have tried reset controller , factory reset ps4 , system update , rebuild database ... nothing worked .
Antenna is properly connected on the mainboard.
Any ideas? thanks

[diif]

Re: PS4 Controller not sync

Massive long threads over on the PlayStation Forums with the same issue.

The short of it, you need access to another controller to find out if it's the console or controller causing the problem.

[claudyu07]

Re: PS4 Controller not sync

Massive long threads over on the PlayStation Forums with the same issue.

The short of it, you need access to another controller to find out if it's the console or controller causing the problem.

Controller connects fine over bluetooth to my android phone and can use it

[stj]

Re: PS4 Controller not sync

got a warranty on the console?

[dj_ricoh]

Re: PS4 Controller not sync

and normal with usb no?

[claudyu07]

Re: PS4 Controller not sync

no warranty .
@dj_ricoh ps4 only works on bluetooth.
Usb only working in safe mode.

[newtothis]

Re: PS4 Controller not sync

For anyone reading this -

Need to flash the NOR chip - Bluetooth section of the firmware goes corrupt

[stj]

Re: PS4 Controller not sync

how big is the dump?

[newtothis]

Re: PS4 Controller not sync

32,768 kb

If the .bin is extracted it is in the file - C0020001.bin section that goes bad

I use HxD to copy the data from a working C0020001 and replace the entire section in the original .bin file

[stj]

Re: PS4 Controller not sync

can you upload it for others who may not have access to a working console when they need it please.

[newtothis]

Re: PS4 Controller not sync

Can do - I will write up a tutorial on how to do it too

[stj]

Re: PS4 Controller not sync

nice

[newtothis]

Re: PS4 Controller not sync

WIP - Currently writing it up....


As promised a tutorial on how to remedy the PS4 controller not syncing except via USB in safe mode.

There are 2 issues that can cause this

1) The Wifi/BT board has seen its last days and needs replacing - The Wifi/BT board is a BGA connection type but the pads are large enough to just use your iron to flow solder to each pad before flowing to the board

2) The NOR chip has gone corrupt and will require the dump to be repaired and reflashed

We will cover how to reflash the NOR in this guide using a raspberry PI 3

Equipment needed :

• Raspberry PI 3 (with an 8GB SD card)
• Female to Female jumper cables
• SOIC16 to DIP16 300mil wide adapter
• RJ45 network cable (For PI network connection)
• Hot air rework station/Iron and consumables (Flux/Solder etc)

Software needed :

• Raspbian (http://downloads.raspberrypi.org/raspbian_latest)
• Win32 Disk Imager (http://sourceforge.net/projects/win3...atest/download)
• Putty (http://the.earth.li/~sgtatham/putty/.../x86/putty.exe)
• Hxd Editor (https://mh-nexus.de/en/downloads.php?product=HxD)
• WinSCP (https://winscp.net/eng/download.php)
• Working Wifi/BT dump (https://mega.nz/#!5dAxFTZL!GVuxziYAU...-7-0Ik7VB5PCe0)

Firstly lets install Raspbian to the Raspberry PI:

1. Start up Win32 Disk Imager and in "Image File" select the decompressed Raspbian .IMG file
   
2. In "Device" select the location of the SD card
   
3. Select "Write"

After the writing is complete put the SD card into the Raspberry PI and power it up using the USB cable.

Remote connection shell to the Raspberry PI:

Plug the RJ45 into the Raspberry PI and after a minute check your router connections to find the IP of the Raspberry PI.

1. Start up Putty
   
2. In "Host Name" put the IP of the Raspberry PI
   
3. Select "SSH"
   
4. Select "Open"
   
5. In the login fields put "pi" as the username and "raspberry" as the password
   
6. Insert the following commands line by line
   

sudo -s
cd /bin
wget http://jaicrab.org/Ps4/Tools/JAISPI/jaispi
chmod +x jaispi
echo "#blacklist spi-bcm2708" > /etc/modprobe.d/raspi-blacklist.conf
echo "blacklist i2c-bcm2708" >> /etc/modprobe.d/raspi-blacklist.conf
reboot

Installation is complete. By Putty you can access the Raspberry Pi. To run the command jaispi you need to be root (sudo-s).

Before we do this we now need to wire up our SOIC16 adapter to our PI:

The following reference images are color coded for the connections from the SOIC adapter (or the chip if soldered direct) to the PI interface pins :

PI Pinout:---------------------------------------------------------------------------------SOIC16 Pinout:

----------------------------------------------------------------------

Full connection information table:

Removing the NOR:

Now we have the PI setup and ready to go it's time to remove the NOR from the PS4 mainboard, The chipset in question is MX25L25635FMI-10G and is found here :



Flux the chip up and use your Hot Air Station to heat and remove the chip.

Clean up the pad area on the board with braid ready for reinstallation - Now depending on your preferences of either using Hot Air to reattach or using your iron either pre-tin the pads or not - Whatever suits you best

Checking the connections for the NOR to the PI:

Making sure you orient the NOR correctly using the above Diagrams/Tables insert the NOR into the SOIC adapter.

Start up Putty if its not already running and login to your PI

Set yourself as Root with:

sudo -s

Use the command below to check read access to the NOR:

jaispi -i /dev/spidev0.0

Jaispi should report back with

JaiSpi v1.0
ID: 0xC22019 MX25L25635

If you get an an "Unknown" message please check your wiring and possibly give your NOR a clean with IPA to remove any flux that could hinder continuity.

Next we want to take a read dump of the NOR with:

jaispi -r corruptedno1.bin /dev/spidev0.0

It is best to take 3 dumps then verify each one using against the NOR, To do this use the above code and alter the name "corruptednor1.bin" by a number increment for each one.

So you should end up with 3 dumps with the names :

corruptednor1.bin
corruptednor2.bin
corruptednor3.bin


Next we verify each dump by using the command:

jaispi -v corruptednor1.bin /dev/spidev0.0

Do this for each dump you took by changing the name of the file - If it says any of them have differences then again check your connections.

Obtaining the dumps from the Raspberry PI:

To obtain the dump files from the raspberry PI we will want to remote connect using WinSCP

1. Install WinSCP
2. In "Hostname" input the Raspberry PI IP
3. Use the same credentials as Putty (Above) to log into the PI
4. On the right you should now see your dump files, Right click one and select "Download"

Extracting the .bin dump file:

1. Using PS4_AC1D_Flash-Tool.exe click "Extract"
2. Next to "NOR Dump" click "Open" and select your dump file
3. Click "Save" and select a destination for your extraction
4. Click "Extract Now!"

Using HxD to check for corruption:

1. Open HxD
2. Select "File" "Open" and select file "C0020001.bin" that you just extracted using Ac1d Tools
3. Again select "Open" and select the provided working .bin from the "Working Wifi/BT DUmp" file you downloaded from the above links (Make sure it is from the correct board revision that is printed on your motherboard EG:SAA-001)
4. Press "CTRL+K" to open up a compare window in HxD and select "OK"
5. If HxD shows differences in the files then the file is corrupt

Repairing the corruption using HxD:

1. Close the corrupted window in HxD and leave the working example open
2. Select "File" "Open" and open your original unextracted .bin dump file
3. Navigate to the address in your unextracted dump file that is associated with your mainboard version (The text file accompanying the working example will tell you what address to goto (For EG : SAA-001 board will be at address x144200)
4. From this point you should see a lot of FF FF FF FF < This is the corruption
5. From the working example file "C0020001.bin" right click and "select all" then right click "Copy"
6. At the bottom of the HxD window you will see "Length" - Take not of the value
7. In your unextracted "corruptednor1.bin" select and drag from the beginning of line x144200 until the "length" selection matches the previous one you took note of.
8. Once you have matched the length selection right click and select "Paste Write"
9. Click "File" "Save"

Flashing the NOR back:

1. Rename your repaired .bin file to "workingnor.bin" then move it back onto the Raspberry PI using WinSCP
2. In Putty use the following command to flash the file back to the chip

jaispi -p workingnor.bin /dev/spidev0.0

Once the process is complete you should see:

JaiSpi v1.0
ID: 0xC22019 MX25L25635
Starting...
0x02000000 -> 8192 Sectors written
Done!

Next verify again by using:

jaispi -v workingnor.bin /dev/spidev0.0

You should now be greeted with:

ID: 0xC22019 MX25L25635
Checking...
0x02000000 -> 0 Different sectors
Done!

If all is well solder your NOR back onto your PS4 Mainboard and enjoy gaming once again