2

My OnePlus One phone got stuck in a boot loop over night without, as far as I know, a specific reason to do so (no new update was installed). Before this it was running perfectly fine. The phone was running the stock CM.

The phone boots and shows the Cyanogen Mod Ready logo and then restarts (Android version 6.0.1, Cyanogen version 13.1.2).

I tried numerous things so far Booting in safe mode, wiping the caches and a factory reset (as suggested on the boot loop info page) all did not solve the problem.

Using ADB sideload to push and flash a zip of the ROM from the computer did not work. Yet no error was returned.

Furthermore, flashing the ROM with fastboot, as described here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 did not resolve the boot loop. Also here, no errors were returned when flashing the individual files.

I'm not sure what other options I could still explore.

  • The phone was plugged in when it happened? – esQmo_ Nov 3 '16 at 16:02
  • The phone was at the moment charging through the power outlet. – invalid_id Nov 3 '16 at 17:41
  • So this leads me to think that there is something with the eMMC. I think it might be a hardware problem due to short-circuit – esQmo_ Nov 3 '16 at 17:51
  • I was already suspecting a hardware issue, but afaik there is no way to check it. Also, if it would be the eMMC shouldn't the flashing return an error when I overwrite a file? Thank you for your help so far – invalid_id Nov 3 '16 at 17:56
  • You're welcome. Since I'm not good in hardwares, I can't tell you exactly what is causing the issue. But let's return on software side, did you flash the Cyanogen OS Fastboot Images as described in the link you provided? – esQmo_ Nov 3 '16 at 19:17
0

After contacting OnePlus they set up a remote session. During this session they also flashed the phone using their own files. This, however, did not solve the problem.

The phone was still under waranty so they arranged it to be send for repair. They found the motherboard to be faulty, which has been replaced and the phone works perfectly fine again.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.