Nothing Phone 2 I’m writing this as a frustrated Nothing Phone 2 user who has been left with a completely non-functional WiFi after the OS 4.0 update (Build: Pong-B4.0-251226-1110).Timeline of the Issue😃ecember 2025: Updated to Nothing OS 4.0 - WiFi issues started immediatelyJanuary 2026: Received another patch update - Instead of fixing the problem, WiFi got WORSEPast 2 days: WiFi won’t turn on AT ALL - completely deadWhat I’ve Already Tried (EVERYTHING):
✓ Factory Reset - NO EFFECT
✓ Reset Network Settings multiple times - FAILED
✓ Safe Mode - WiFi still dead
✓ Wiped cache partition - NO IMPROVEMENT
✓ Power off for 24+ hours - DIDN’T HELP
✓ Removed all apps - STILL BROKEN
✓ Multiple restarts and reboots - USELESSCurrent Situation:
My phone is essentially UNUSABLE. I cannot:Connect to home/work WiFiDownload apps or updatesUse WiFi callingProperly sync my dataWork efficiently (forced to use expensive mobile data)This is NOT a minor bug - this is a CRITICAL system failure that renders the device defective.What Nothing Needs to Do IMMEDIATELY:Acknowledge this critical bug publicly - Stop ignoring users in the community �Release an emergency hotfix - This has been ongoing for over a MONTH with no official fixProvide a rollback option to OS 3.0 - Allow users to downgrade without voiding warrantyCompensate affected users - We paid for a working smartphone, not a broken oneTransparent communication - Give us a timeline for the fix, not silenceTo Other Affected Users:
If you’re experiencing the same issue, please comment and upvote. Nothing needs to see how widespread this problem is.To Nothing Team:
You paused the OS 4.0 rollout in December 2025 because of bugs �, but many of us already got the broken update. Where is our fix? Where is the accountability?A smartphone without working WiFi is NOT a smartphone. This is unacceptable.Phone Details:Model: Nothing Phone 2Build: Pong-B4.0-251226-1110Issue: WiFi toggle completely dead, won’t turn onStatus: ALL troubleshooting methods failed#NothingPhone2 #NothingOS4 #WiFiBug #CriticalIssue