5thGenRams Forums
Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
2025 Ram 1500 Limited Sub/Amp Install
- Thread starter bshelton8
- Start date
Blue Streak Ram
Active Member
- Joined
- Jan 6, 2019
- Messages
- 52
- Reaction score
- 30
- Points
- 18
- Age
- 51
By chance do you recall the wire colors for each sub coil? And are they 2 ohm coils?
1791
Ram Guru
- Joined
- Nov 9, 2023
- Messages
- 1,030
- Reaction score
- 846
- Points
- 113
- Age
- 55
i have a 2019 with the alpine so the harmon and the alpine are the same as far as i can tell from 2019-up so the bast thing to do is forget about the amp pro get a dsp and remove the factory amp totally there are 2 plug and play dsp's all the work is done under the driver seat
rockford dsr1 and the Hertz SPL Show S8 DSP i went with the rockford
rockford dsr1 and the Hertz SPL Show S8 DSP i went with the rockford
Last edited:
Blue Streak Ram
Active Member
- Joined
- Jan 6, 2019
- Messages
- 52
- Reaction score
- 30
- Points
- 18
- Age
- 51
I’m just looking to connect a sub to the factory amp for now until PAC builds a module for it. I got an audiofrog 12 that’s very sensitive so it should be fine for a while. I have two pairs at the sub. Green brown/green white and grey brown/grey white. Obviously the greys are a pair and greens are a pair, just not sure which is positive and negative.
1791
Ram Guru
- Joined
- Nov 9, 2023
- Messages
- 1,030
- Reaction score
- 846
- Points
- 113
- Age
- 55
i think you wrong it's opposite the whites are a set and the brown's are a set
Voice Coil 1 is gray/brown (+) and green/brown (-), Voice Coil 2 is gray/orange (+) and green/orange (-), and Voice Coil 3 is gray/white (+) and green/white (-)
to me it looks like, try it
gray/brown (+)
green/brown (-)
gray/white (+)
green/white (-)
darkmage1991
Active Member
- Joined
- Jul 30, 2023
- Messages
- 30
- Reaction score
- 24
- Points
- 8
- Age
- 35
i wanted to give an update on what i was able to do.
as i said in a previous post in the thread, i have an ap4-ch41 (Rev 2) and purchased the ch42 harness seperatly. pac recently released firmware (v5) for 2025+ trucks for the ap4-ch42 only. as most know, the CH42 is just the ap4-ch41 R.2 with the updated harness (APH-CH42).
i was extremely confident flashing CH42 fw to CH41 would work but... the app blocked it with a firmware/device check, being as i was pretty damn confident CH42 is just CH41 rebranded i fired up dnSpy (decompiler/editor) and patched it out( its super easy since it's .net, its basically like editing source code almost).
found 2 functions that are for firmware verification, 1 is for newer bins, other is older, i went ahead and patched both, i flashed CH42 v5 and... it works! Module responds perfectly to truck volume changes and dings all work, funnily enough it now now shows as ap4-ch42 in the pac software.
i will not share the patched exe for legal reasons and its obiously safe to say you shouldnt just download and run programs others have modified anyways =P
for others with ap4-ch41 that might want to do this in the future... either you already have one or find a used ebay one and are wanting 2025+ support, get dnspy (GitHub), right click and select "Edit C#" on both functions `validate_PUFX_File` & `Validate_MCUBOOT_File`, -> make both always return true(Validate_MCUBOOT_File might not be needed at all, it appears to be for older firmware types). then just save module(save module is just fancy for save the modified exe file) then flash the v5 CH42 fw.
**WARNiNG**: No safety checks are present anymore if you do this... wrong/malformed fw might brick the pac module. luckilly it looks like the pac module has built in dfu so recovery might be possible if this happens. but just make sure you are downloading the ch42 v5 file and that the file isnt currupted/malformed... the md5 of the fw file i got was : ba15f35fce70851e08a1f4c117933b8b just incase you wanted to make sure its not messed up before flashing.
EDIT: i should of also added, i can only confirm this works on the R2 of the ch41 module, teh r1/older one might be different internally somehow(most likely is considering the revision change).
as i said in a previous post in the thread, i have an ap4-ch41 (Rev 2) and purchased the ch42 harness seperatly. pac recently released firmware (v5) for 2025+ trucks for the ap4-ch42 only. as most know, the CH42 is just the ap4-ch41 R.2 with the updated harness (APH-CH42).
i was extremely confident flashing CH42 fw to CH41 would work but... the app blocked it with a firmware/device check, being as i was pretty damn confident CH42 is just CH41 rebranded i fired up dnSpy (decompiler/editor) and patched it out( its super easy since it's .net, its basically like editing source code almost).
found 2 functions that are for firmware verification, 1 is for newer bins, other is older, i went ahead and patched both, i flashed CH42 v5 and... it works! Module responds perfectly to truck volume changes and dings all work, funnily enough it now now shows as ap4-ch42 in the pac software.
i will not share the patched exe for legal reasons and its obiously safe to say you shouldnt just download and run programs others have modified anyways =P
for others with ap4-ch41 that might want to do this in the future... either you already have one or find a used ebay one and are wanting 2025+ support, get dnspy (GitHub), right click and select "Edit C#" on both functions `validate_PUFX_File` & `Validate_MCUBOOT_File`, -> make both always return true(Validate_MCUBOOT_File might not be needed at all, it appears to be for older firmware types). then just save module(save module is just fancy for save the modified exe file) then flash the v5 CH42 fw.
**WARNiNG**: No safety checks are present anymore if you do this... wrong/malformed fw might brick the pac module. luckilly it looks like the pac module has built in dfu so recovery might be possible if this happens. but just make sure you are downloading the ch42 v5 file and that the file isnt currupted/malformed... the md5 of the fw file i got was : ba15f35fce70851e08a1f4c117933b8b just incase you wanted to make sure its not messed up before flashing.
EDIT: i should of also added, i can only confirm this works on the R2 of the ch41 module, teh r1/older one might be different internally somehow(most likely is considering the revision change).
Attachments
Last edited:
