Device:
-
iPad 11th generation
-
Wi-Fi model
-
iPadOS 27 Beta
-
Mond Development build
Target spoof:
-
iPad Pro M4
-
ProductType: iPad16,3
Description:
When using Mond's Device Spoofing functionality on an iPad 11th generation and changing the device identity to an iPad Pro M4 (iPad16,3), Wi-Fi stops working correctly.
The iPad and Wi-Fi work normally before applying the spoof.
Steps to reproduce:
-
Start with an unmodified iPad 11th generation.
-
Confirm that Wi-Fi works normally.
-
Install and open the Development build of Mond.
-
Use Device Spoofing.
-
Change the ProductType/device identity to iPad16,3.
-
Apply the changes.
-
Reboot the device if required.
-
Test Wi-Fi.
Actual behavior:
After spoofing the device as iPad16,3, Wi-Fi becomes non-functional or otherwise fails to operate correctly.
The issue is reproducible after applying the M4 device spoof.
Expected behavior:
Changing MobileGestalt/device-identification values should not disable or break the physical Wi-Fi functionality of the iPad.
Additional testing:
I tested other MobileGestalt-related modifications, including Eligibility-related changes and other device-identification fields.
The important observation is that changing the device identity/ProductType to iPad16,3 is sufficient to reproduce the Wi-Fi problem.
This suggests that the issue may not be caused by the Eligibility modification itself, but potentially by another MobileGestalt value modified as part of the Device Spoof.
Relevant observation:
Mond separates several modification categories, including:
-
Device Spoofing
-
Subtype
-
Eligibility
-
CacheExtra
-
Internal Features
It would therefore be useful to determine exactly which MobileGestalt keys are modified when selecting iPad16,3.
In particular, I would like to know whether the M4 spoof modifies any hardware, board, Wi-Fi, networking, or platform-identification fields in addition to ProductType.
Hypothesis:
My current hypothesis is that ProductType = iPad16,3 may not be the only relevant value.
There may be a dependent MobileGestalt field, board identifier, hardware configuration value, or other device-specific property that becomes inconsistent with the actual iPad 11 hardware.
The resulting state is effectively:
Physical hardware:
iPad 11th generation
Reported device:
iPad Pro M4 / iPad16,3
If a system component uses the spoofed device identity to select a hardware-specific configuration, this could explain why Wi-Fi functionality is affected.
Version information:
I am using the Development build of Mond rather than Mond 2.2.
The Development build includes the iOS 27-related fixes, including changes related to MobileGestalt persistence and region handling.
However, the Wi-Fi issue remains when performing the iPad16,3 spoof.
Request:
Could the developers confirm:
-
Which MobileGestalt keys are modified by the iPad16,3 Device Spoof?
-
Is ProductType modified alone, or is it modified together with other hardware-identification fields?
-
Has iPad16,3 spoofing been tested on an iPad 11th generation?
-
Is any known MobileGestalt key used by the Wi-Fi subsystem affected by the spoof?
-
Is there a recommended minimal set of keys for spoofing an iPad 11th generation as an M4 iPad Pro without affecting Wi-Fi?
I can provide logs, before/after MobileGestalt dumps, and the exact set of values modified by Mond if required.
Device:
iPad 11th generation
Wi-Fi model
iPadOS 27 Beta
Mond Development build
Target spoof:
iPad Pro M4
ProductType: iPad16,3
Description:
When using Mond's Device Spoofing functionality on an iPad 11th generation and changing the device identity to an iPad Pro M4 (iPad16,3), Wi-Fi stops working correctly.
The iPad and Wi-Fi work normally before applying the spoof.
Steps to reproduce:
Start with an unmodified iPad 11th generation.
Confirm that Wi-Fi works normally.
Install and open the Development build of Mond.
Use Device Spoofing.
Change the ProductType/device identity to iPad16,3.
Apply the changes.
Reboot the device if required.
Test Wi-Fi.
Actual behavior:
After spoofing the device as iPad16,3, Wi-Fi becomes non-functional or otherwise fails to operate correctly.
The issue is reproducible after applying the M4 device spoof.
Expected behavior:
Changing MobileGestalt/device-identification values should not disable or break the physical Wi-Fi functionality of the iPad.
Additional testing:
I tested other MobileGestalt-related modifications, including Eligibility-related changes and other device-identification fields.
The important observation is that changing the device identity/ProductType to iPad16,3 is sufficient to reproduce the Wi-Fi problem.
This suggests that the issue may not be caused by the Eligibility modification itself, but potentially by another MobileGestalt value modified as part of the Device Spoof.
Relevant observation:
Mond separates several modification categories, including:
Device Spoofing
Subtype
Eligibility
CacheExtra
Internal Features
It would therefore be useful to determine exactly which MobileGestalt keys are modified when selecting iPad16,3.
In particular, I would like to know whether the M4 spoof modifies any hardware, board, Wi-Fi, networking, or platform-identification fields in addition to ProductType.
Hypothesis:
My current hypothesis is that ProductType = iPad16,3 may not be the only relevant value.
There may be a dependent MobileGestalt field, board identifier, hardware configuration value, or other device-specific property that becomes inconsistent with the actual iPad 11 hardware.
The resulting state is effectively:
Physical hardware:
iPad 11th generation
Reported device:
iPad Pro M4 / iPad16,3
If a system component uses the spoofed device identity to select a hardware-specific configuration, this could explain why Wi-Fi functionality is affected.
Version information:
I am using the Development build of Mond rather than Mond 2.2.
The Development build includes the iOS 27-related fixes, including changes related to MobileGestalt persistence and region handling.
However, the Wi-Fi issue remains when performing the iPad16,3 spoof.
Request:
Could the developers confirm:
Which MobileGestalt keys are modified by the iPad16,3 Device Spoof?
Is ProductType modified alone, or is it modified together with other hardware-identification fields?
Has iPad16,3 spoofing been tested on an iPad 11th generation?
Is any known MobileGestalt key used by the Wi-Fi subsystem affected by the spoof?
Is there a recommended minimal set of keys for spoofing an iPad 11th generation as an M4 iPad Pro without affecting Wi-Fi?
I can provide logs, before/after MobileGestalt dumps, and the exact set of values modified by Mond if required.