Bootloop after Marshmallow Update

Well that file is for going back from Open OS, not from Marshmallow.

Try this link:

1 Like

So downgrade is not possible (Can’t install older package over newer build). Hope that factory reset to marshmallow will get me out of the boot loop.

I am having a boot loop too.:frowning:
It’s even impossible on the balcony (3°C) to upgrade it.

Did some of you maybe disable the Google App in Lollipop? That is one very reliable way to end up in a bootloop when upgrading to Marshmallow. I had to learn that the hard way during the beta test…

3 Likes

Yes, I disabled it. Didn’t know I need it.

A post was merged into an existing topic: Can you feel it coming OTA tonight? - THIS UPDATE IS NOT OFFICIAL!

Update:

  • Still no successful upgrade, but I wanted to ask if somebody else (that is suffering the bootloops) also gets a red LED on the last ~20 apps being optimized (this seems to have nothing to do with battery charge, since I’ve been getting this with charging cable and without cable but with more than 30% battery right afterwards)
  • Also, as somebody else noted, the amount of apps being optimized varies all the time. It started with 79, stayed like that (optimizing to completion) for maybe 20 loops, then it decreased to 10, increased to 40 and finally increased to 90, where it has been the last couple of loops.

An update to the update:

  • After blood, sweat and tears, I got to manually flash the OTA file via ADB sideload (the sdcard would not be recognized in recovery mode). The process concluded with the “Install from ADB complete.” text but a system reboot brought me back to the bootloop.

Does this mean that, in theory, the image is now correctly installed and the only thing not allowing the phone to startup is the overheating?

Cheers,
Suckelo

I tried exactly the same, but i don’t think it’s the overheating, if you observe the bootloop via
adb logcat *:E
you can see that there are a lot errors concerning app optimization.

I hope that a factory reset will help.

I charged the phone the whole night and the issue persists. Trying to get into the recovery I only get “no command” open-chested andy.

When you see “no command” screen, press again Power and VolumeUp, then leave Volume Up, then Power. Now you can see the recovery menu.

i wondered how i got there last time fiddling around with the combination without paying attention. thanks.
wiping cache…
retrying…
optimizing 33 apps…done
reboot.
optimizing 111 apps…if this doesnt work, the os gets the hammer and a full reset. …done.

ok here goes…shit.
hammertime.

1 Like

Will you write if/when you do it? I don’t think I can trust myself to wipe the whole phone and then realising it was for nothing.
I’m trying again after wiping the cache partition

1 Like

cache did nothing. If i remember correctly google introduced a new JIT runtime to marshmallow and this may or may not be the reason the apps could not be optimized.

wiping it helped to get it to launch, though. but everything not backed up is lost.

Yeah cache wiping did nothing.

Are you saying that you did a “restore to factory settings”, the update finished correctly and now you have a functioning phone with marshmallow?

I guess I’ll have to do it too :sweat:

yes. and keeping it cool during opimization does nothing when the runtimes are incompatible.
Even if you keep it in the fridge, the optimizer can’t handle it.

1 Like

Cooling the Phone doesn’t appear to do anything, so I wanted to try the other option (the recovery mode). But really have no clue what to do after opening the recovery mode. It looks as though I need to be a lot more interested and experienced with computers and software than I actually am (or would like to be).
Am I right, or just overlooking something simple?

Check 1), then 2) and then 3)

  1. Dictionary Entry: Recovery Mode
  2. https://support.fairphone.com/hc/en-us/articles/201654943
  3. https://support.fairphone.com/hc/en-us/articles/207914363-Manually-install-Fairphone-OS-for-the-Fairphone-2

That should bring you up to date.

That’s also what we have observed so far - it seems to be a common problem to phones shipped with the Google Mobile Services.
We did not find another root cause, but please report anything else.

Unfortunately, this is not recoverable - and you will have to wipe the data.

2 Likes

@borjan / @ChuckMorris
Do you happen to know if reactivating the deactivated Google apps (and updating them to current version) before starting the Marshmallow update will help?

1 Like