How To Fix Your Infocus Device After Update Crash

Some users often brick their devices whenever they attempt using Infocus inbuilt device firmware update. I cannot explain why this happens or it’s cause, but I can help you fix your device with such problem as this.

Using any of the methods I’ll be sharing in this article could erase all the data on your device. So, I think you should be expecting that if there’s a chance of reviving your bricked device.

Let’s get started already!

Method #1

  • Try accessing your device stock recovery (try pressing vol up + power button, if  this doesn’t work on your device us vol down + power button).
  • If you successfully boot into recovery mode, wipe/erase your device data and cache, then reboot.

Method #2

  • Install fastboot/adb drivers for your device on your pc. If you don’t know how, click here.
  • Now boot your Infocus device into fastboot mode by pressing Volume Down + Power button at the same time.
  • Once it’s in fastboot mode, connect the device to PC
  • Now, while holding down Shift button on your PC, right-click on the folder containing your fastboot/adb files and select Open command window here.
  • In command window, type the following commands followed by Enter button after each command line
  • fastboot devices

    This is just to verify that your device has been properly connected in fastboot mode. It should display your device serial number.

    fastboot erase userdata

    fastboot erase cache 

    Ignore this command if you get any error message.

    fastboot reboot 

    • Disconnect the device from PC and allow it to boot completely.
    If any of these doesn’t fix your device, you will have to flash your device with a completely fresh stock firmware. To download your device specific firmware flash file, click here.


    47 Responses to “How To Fix Your Infocus Device After Update Crash”
    1. bharath gollapudi February 25, 2016
    2. Collins Edim February 28, 2016
    3. Ramesh Aravindh March 6, 2016
    4. Collins Edim March 6, 2016
    5. Ramesh Aravindh March 6, 2016
    6. Collins Edim March 6, 2016
    7. Ramesh Aravindh March 6, 2016
    8. Collins Edim March 6, 2016
    9. Ramesh Aravindh March 7, 2016
    10. Collins Edim March 7, 2016
    11. Ramesh Aravindh March 7, 2016
    12. Ramesh Aravindh March 7, 2016
    13. Collins Edim March 7, 2016
    14. Ramesh Aravindh March 8, 2016
    15. Collins Edim March 8, 2016
    16. Ramesh Aravindh March 8, 2016
    17. Collins Edim March 8, 2016
    18. Ramesh Aravindh March 9, 2016
    19. Collins Edim March 9, 2016
    20. suvajit karmakar March 9, 2016
    21. suvajit karmakar March 9, 2016
    22. Collins Edim March 12, 2016
    23. Shubham Vishwakarma March 21, 2016
    24. Anonymous August 2, 2016
    25. Collins Edim August 2, 2016
    26. Anonymous August 2, 2016
    27. Collins Edim August 2, 2016
    28. Collins Edim August 3, 2016
    29. Anonymous August 3, 2016
    30. Collins Edim August 3, 2016
    31. smeeth August 3, 2016
    32. Collins Edim August 3, 2016
    33. Anonymous August 5, 2016
    34. Sunit Das August 10, 2016
    35. Collins Edim August 10, 2016
    36. Sunit Das August 10, 2016
    37. Collins Edim August 10, 2016
    38. Sunit Das August 11, 2016
    39. Vikas Gautam September 26, 2016
    40. Vanessa Hontiveros October 5, 2016
    41. Collins Edim October 5, 2016
    42. Vanessa Hontiveros October 5, 2016
    43. Collins Edim October 5, 2016
    44. Vanessa Hontiveros October 5, 2016
    45. Collins Edim October 5, 2016

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    0
    Connecting
    Please wait...
    Send a message

    Sorry, we aren't online at the moment. Leave a message.

    Your name
    * Email
    * Describe your issue
    Login now

    Need more help? Save time by starting your support request online.

    Your name
    * Email
    * Describe your issue
    We're online!
    Feedback

    Help us help you better! Feel free to leave us any additional feedback.

    How do you rate our support?