• Sign Up! To view all forums and unlock additional cool features

    Welcome to the #1 Explorer ST Forum and Explorer ST community dedicated to Explorer ST owners and enthusiasts. Register for an account, it's free and it's easy, so don't hesitate to join the Explorer ST Forum today!


Fullscreen Android Auto/CarPlay Mod Is Here for Sync3 10P Screen!! [FMods Team 10 Pees]

Messages
31
Reactions
13
Points
2
Location
Dominican Republic
Vehicle
Ford Explorer ST 2021
#41
Update to beta2... but i forgot to look in the config file. How do i make config changes after upgrading to beta 2?
And the technical notes:
  • In order to install this beta, you will need to format your flash drive with either exFAT or FAT32. NTFS USB drives will not work and will give cryptic patch failure errors.
  • You will need to be on FMods Tools version 2.9. Update that first if you haven't already!
  • If you're upgrading from an alpha build of this mod, please edit your autoinstall.sh file to set RESTORE=1 and PATCH=1. Note that you will need to have your backup files handy and in the appropriate backup directory. (You did keep them in a safe place, right?)
Open autoinstall.sh with notepad
 

Cdubya

1000 Post Club
Messages
1,781
Reactions
894
Points
262
Location
NE Ohio
Vehicle
2020 Explorer ST
#42
Restored to stock using the alpha USB with restore=1. Then put in the Beta2 USB. Hash errors prevent the patch.

Here's the log:
DEV Fix for +10inchP Full AA CP screen v1.0 - Developed by Team 10 Pees
Not backing up Home.qml - hash mismatch.
Not backing up Root.qml - hash mismatch.
Not backing up MM_DioService - hash mismatch.
Not backing up MM_GalService - hash mismatch.
Not backing up mm_cfgbuilder - hash mismatch.
ERROR: Patch file dry run failed to apply.
Please ensure you are on Sync 3 Build 3.4.23188.
Check USB logs for extra information.
Please remove the USB stick to reboot.


I'm back to the old screen :(
 

Last edited:
Messages
3
Reactions
1
Points
2
Location
Canada
#43
Restored to stock using the alpha USB with restore=1. Then put in the Beta2 USB. Hash errors prevent the patch.

Here's the log:
DEV Fix for +10inchP Full AA CP screen v1.0 - Developed by Team 10 Pees
Not backing up Home.qml - hash mismatch.
Not backing up Root.qml - hash mismatch.
Not backing up MM_DioService - hash mismatch.
Not backing up MM_GalService - hash mismatch.
Not backing up mm_cfgbuilder - hash mismatch.
ERROR: Patch file dry run failed to apply.
Please ensure you are on Sync 3 Build 3.4.23188.
Check USB logs for extra information.
Please remove the USB stick to reboot.


I'm back to the old screen :(

Mine did the same thing, I just ended up reloading Alpha and sticking with that for now.
 

Cdubya

1000 Post Club
Messages
1,781
Reactions
894
Points
262
Location
NE Ohio
Vehicle
2020 Explorer ST
#44
Mine did the same thing, I just ended up reloading Alpha and sticking with that for now.
Good thinking...alpha is better than stock
I really wanted to try 30fps instead of 60fps. I don't mind the menu bars.
 

OP
I
Messages
17
Reactions
21
Points
2
Location
United States
Vehicle
21 ST
Thread Starter #45
Restored to stock using the alpha USB with restore=1. Then put in the Beta2 USB. Hash errors prevent the patch.

Here's the log:
DEV Fix for +10inchP Full AA CP screen v1.0 - Developed by Team 10 Pees
Not backing up Home.qml - hash mismatch.
Not backing up Root.qml - hash mismatch.
Not backing up MM_DioService - hash mismatch.
Not backing up MM_GalService - hash mismatch.
Not backing up mm_cfgbuilder - hash mismatch.
ERROR: Patch file dry run failed to apply.
Please ensure you are on Sync 3 Build 3.4.23188.
Check USB logs for extra information.
Please remove the USB stick to reboot.


I'm back to the old screen :(
The instructions on the forum are to take your backup files on the USB made by the alpha during original install (those are the stock ford files) and then place them into the backup folder on a beta2 USB stick before installing. Set restore=1 on beta two autoinstall.sh, set your menu bar settings in config.sh and then run beta2 install. The beta2 installer will restore the original files to stock first, then patch them with new beta2 improvements. I tried that process to go from alpha to beta when we released the new beta and it worked exactly as I just described.
 

Cdubya

1000 Post Club
Messages
1,781
Reactions
894
Points
262
Location
NE Ohio
Vehicle
2020 Explorer ST
#46
The instructions on the forum are to take your backup files on the USB made by the alpha during original install (those are the stock ford files) and then place them into the backup folder on a beta2 USB stick before installing. Set restore=1 on beta two autoinstall.sh, set your menu bar settings in config.sh and then run beta2 install. The beta2 installer will restore the original files to stock first, then patch them with new beta2 improvements. I tried that process to go from alpha to beta when we released the new beta and it worked exactly as I just described.
I did exactly that, trust me. There were three back up files that i placed in the beta2 backup folder. the hash errors still resulted so i thought maybe the stock files didn't restore. then used the alpha usb to restore only. confirmed stock carplay, then tried beta2 again with just patch. same hash errors...
 

Messages
3
Reactions
1
Points
2
Location
Canada
#47
The instructions on the forum are to take your backup files on the USB made by the alpha during original install (those are the stock ford files) and then place them into the backup folder on a beta2 USB stick before installing. Set restore=1 on beta two autoinstall.sh, set your menu bar settings in config.sh and then run beta2 install. The beta2 installer will restore the original files to stock first, then patch them with new beta2 improvements. I tried that process to go from alpha to beta when we released the new beta and it worked exactly as I just described.
That's exactly what I did and it still didn't work
 

Messages
35
Reactions
18
Points
2
Location
So Cal
#48
I want to do this mod but not being fluent in techno-speak makes me hesitant. I think I'll wait till it's less complicated.
 

OP
I
Messages
17
Reactions
21
Points
2
Location
United States
Vehicle
21 ST
Thread Starter #50
I did exactly that, trust me. There were three back up files that i placed in the beta2 backup folder. the hash errors still resulted so i thought maybe the stock files didn't restore. then used the alpha usb to restore only. confirmed stock carplay, then tried beta2 again with just patch. same hash errors...
That's exactly what I did and it still didn't work
We are looking into this... Going from alpha to beta worked for us so something else is definitely going on with the hash check code then. Hopefully we can get this fixed in the next beta release.
 

Messages
2
Reactions
4
Points
2
Location
California
Vehicle
2021 Ford Explorer ST
#51
Hi, the person looking into this here. We do hash validation two times during the install process: first during the backup step, and then again right before a clean install. This helps us ensure that we aren't potentially writing data into a non-SYNC 3.4.23188 file (as such a modification would cause very hard-to-debug crashes).

The hash mismatch error reported above is more of a warning than an actual error, and happens during the backup phase. If it's reported, it means that (a) the backup files are not stored on the USB, and (b) that the installer has detected that the files currently installee aren't stock. To anyone having this issue, can you please check that you have files in your SyncMyMod/files/other/backup/+10inchP directory?

The actual issue hanging up the install is "ERROR: Patch file dry run failed to apply", which means that our test patch attempt fails. This generally happens in Home.qml and/or Root.qml, as we don't currently have a solid mechanism to un-patch the file (and you can't patch over an already-patched file).

If the files aren't present there, the RESTORE operation will fail silently due to another bug that I'm fixing for beta3 (that otherwise shouldn't cause any issues, just no logging in this case). Put your backup files into that specific directory, and everything should hopefully work. I'm also going to specifically work on a case to detect if the mod was already installed to just allow you to change settings since that appears to be a relatively common use case.

On a more personal note, I apologize for the difficulties we're having with the installer. I'm still new to the entire "mod packaging" thing and am really learning as I'm going. While I am absolutely testing things on actual hardware, my testing tends to be done in a controlled environment and things can be missed because I know how things are supposed to work.
 

Last edited:

Cdubya

1000 Post Club
Messages
1,781
Reactions
894
Points
262
Location
NE Ohio
Vehicle
2020 Explorer ST
#52
Hi, the person looking into this here. We do hash validation two times during the install process: first during the backup step, and then again right before a clean install. This helps us ensure that we aren't potentially writing data into a non-SYNC 3.4.23188 file (as such a modification would cause very hard-to-debug crashes).

The hash mismatch error reported above is more of a warning than an actual error, and happens during the backup phase. If it's reported, it means that (a) the backup files are not stored on the USB, and (b) that the installer has detected that the files currently installee aren't stock. To anyone having this issue, can you please check that you have files in your SyncMyMod/files/other/backup/+10inchP directory?

The actual issue hanging up the install is "ERROR: Patch file dry run failed to apply", which means that our test patch attempt fails. This generally happens in Home.qml and/or Root.qml, as we don't currently have a solid mechanism to un-patch the file (and you can't patch over an already-patched file).

If the files aren't present there, the RESTORE operation will fail silently due to another bug that I'm fixing for beta3 (that otherwise shouldn't cause any issues, just no logging in this case). Put your backup files into that specific directory, and everything should hopefully work. I'm also going to specifically work on a case to detect if the mod was already installed to just allow you to change settings since that appears to be a relatively common use case.

On a more personal note, I apologize for the difficulties we're having with the installer. I'm still new to the entire "mod packaging" thing and am really learning as I'm going. While I am absolutely testing things on actual hardware, my testing tends to be done in a controlled environment and things can be missed because I know how things are supposed to work.
Thanks for the help. Unfortunately the log file I posted is not the original one i tried with Beta2 usb after transferring the backup files (3) to it and using restore=1, backup=1. if memory serves, it had multiple faiked hash tests and did not restore. I then used the alpha Usb to restore=1 and that seemed to go without issues and stock carplay is the result. The log i posted is the result of the beta2 usb with just patch=1. I wish i kept the log file at each attempt but my only backup is the original alpha2 usb after initial install.
 

Messages
1,241
Reactions
777
Points
162
Location
East Freetown, MA
Vehicle
2020 Explorer ST, Silver Spruce Metalic
#53
How long does it take to get the email to sign up? It's been three days since I signed up and still have not received an email. What should I do?
 

Messages
31
Reactions
13
Points
2
Location
Dominican Republic
Vehicle
Ford Explorer ST 2021
#54
How long does it take to get the email to sign up? It's been three days since I signed up and still have not received an email. What should I do?
Check Spam folder
 

Messages
148
Reactions
34
Points
27
Location
Bridgewater, New Jersey
Vehicle
2022 Ford Explorer ST
#55
Hi, the person looking into this here. We do hash validation two times during the install process: first during the backup step, and then again right before a clean install. This helps us ensure that we aren't potentially writing data into a non-SYNC 3.4.23188 file (as such a modification would cause very hard-to-debug crashes).

The hash mismatch error reported above is more of a warning than an actual error, and happens during the backup phase. If it's reported, it means that (a) the backup files are not stored on the USB, and (b) that the installer has detected that the files currently installee aren't stock. To anyone having this issue, can you please check that you have files in your SyncMyMod/files/other/backup/+10inchP directory?

The actual issue hanging up the install is "ERROR: Patch file dry run failed to apply", which means that our test patch attempt fails. This generally happens in Home.qml and/or Root.qml, as we don't currently have a solid mechanism to un-patch the file (and you can't patch over an already-patched file).

If the files aren't present there, the RESTORE operation will fail silently due to another bug that I'm fixing for beta3 (that otherwise shouldn't cause any issues, just no logging in this case). Put your backup files into that specific directory, and everything should hopefully work. I'm also going to specifically work on a case to detect if the mod was already installed to just allow you to change settings since that appears to be a relatively common use case.

On a more personal note, I apologize for the difficulties we're having with the installer. I'm still new to the entire "mod packaging" thing and am really learning as I'm going. While I am absolutely testing things on actual hardware, my testing tends to be done in a controlled environment and things can be missed because I know how things are supposed to work.
dude you guys are killing it !!! anyone who thinks there wont be little issues that will need to be ironed out are nuts. It will take alittle time to get it all worked out . Thanks also to the guys installing all of kt to test run it and check for issues. I know almost nothing about computers so I have to wait alittle while u ntil I find some help in New Jersey . But in the meantime, all you guys working on this KNOW there are 1000's of people waiting and extremely thankful!!!
 

Chamorro85

Active Member
Messages
547
Reactions
255
Points
52
Location
Round Lake, IL USA
Vehicle
'21 Explorer ST
#56
How long does it take to get the email to sign up? It's been three days since I signed up and still have not received an email. What should I do?
Deff check spam. Got mine right away but spam folder hid it for a day since I didn't think to check there.
 



Top