- Dec 2, 2009
I tried just flashing just the ota zip but it wouldn't boot past the splash screen for some reason and it wouldn't logcat either. Is there a way to see if my storage is corruptWell there is no need to fastboot flash boot.img / system.img if you later on flashing the OTA. TO be sure that everything is clean, I would do the following steps:
- fastboot erase boot
- fastboot erase system (-w if you would like to erase userdata, too)
- fastboot flash recovery (latest TWRP, if not already installed)
- fastboot reboot recovery
- flash latest OTA
- flash gapps
@AndDiSa the os is running fine it just seems to think there's no storage@gavster26 Not that I am aware of ...
Are you in a bootloop? In that case the first thing I would try is wiping data. If this does not help either you could try to boot to recovery by pressing the vol- button only and then in recovery have a look at /proc/last_kmsg probably there you can find a hint what's wrong during boot.
That's not actually a bug, that's default AOSP behavior. My Nexus 5 (running MM straight from Google) behaves like that. I don't really like it either, but it is what it is. Your other MM device must have overridden it somehow. I do think there is an Xposed module that can change that behavior.A minor bug I found: reducing the notification sound level to zero forces the "Do not disturb"-mode on, that doesn't happen on my other Android 6 device.