Account & help

Start with the symptom.

One change at a time. Locate the failing stage before risking local data or replacing an app.

The useful answerFirst identify the product and whether the failure is in download, Android installation, app launch, login or a specific feature. Keep the exact error and timestamp, then use the matching branch below.

Download or installation failure

Incomplete, tiny or wrong-format file: compare the complete bytes and SHA-256 with the file record. An HTML response is not an APK; renaming it does not fix the download.

Parse error or “App not installed”: check Android version, free storage and whether the same package is already installed. Use the installer decision before changing app state.

Update conflict: stop and compare package and signing continuity through the intended publisher. Do not uninstall to force an unknown update. The update guide explains the data-loss branch.

Blank screen, crash or page not loading

  1. Check whether another page loads on the same connection. If it does not, diagnose the network first.
  2. Close and reopen the intended app once, and check for a documented service notice.
  3. If a browser page requires JavaScript, enable it only for the service you intentionally opened and reload.
  4. Compare the same feature on the service’s website if that feature is offered there. A website working does not prove a native app is fixed.
  5. Record the OS version, installed build, time and exact message if the problem continues.

Clearing cache can remove temporary files; clearing app storage or uninstalling can remove local state. Read the device’s warning and confirm recovery before a destructive reset. We do not recommend a reset as the first step.

Scores, notifications or OTP

Stale score: check an innings break, rain, finished status and the latest commentary event before assuming an outage. Use the score-specific checklist.

Missing alerts: check the correct app’s notification setting, its own selected match alerts and Do Not Disturb. Read the Cricbuzz alert workflow.

OTP or sign-in error: confirm the intended account route and follow the currently shown format, timer and recovery options in the account checklist. A new APK is not a guaranteed fix for an account restriction.

Know when to stop changing things

Stop if the requested fix requires disabling device protection, sharing an OTP, paying an unofficial “release” fee, bypassing eligibility or uninstalling an app before you know how to recover its data.

A useful support report states the intended product, device, build, exact failing action, local time and timezone, error text and the checks already completed. Remove private codes, phone numbers and payment secrets from screenshots. Use the evidence template to avoid repeating failed steps.

Keep going

The next useful step.

Back to Cricbuzz matchday →
A separate destination · Commercial link

Explore the fantasy partner.

Opens a partner website. Check its current rules, age and regional eligibility. This is separate from a Cricbuzz or Dream11 login and from the Android file download.

Open fantasy partner