This mean bug hit us twice, so that it might be helpful do document it in order to help other persons with the same problems.
Symptoms:
According to various investigations (see links below) the system thinks that the Setup Wizard is still running. This bug presumably was introduced with some Android version (Oct 2015), came to the Moto G, and when the bug was removed, the Moto G did not get the corrected OS version.
When does the Problem appear?
There are strong indications that the problem always occurs whenever the device runs out of (flash) memory. Note that our device did not have an SD when the problem appeared.
How can one heal the device?
There have been some recommendations how to repair the phone (see links below):
What did really help?
In fact all methods 1 .. 4 failed, because no adb connection could be established (see Topic 5. of the symptoms), and the Setup Wizard got to an endless loop when I started it via Nova Launcher. So finally I used the Recovery system to reset the device.
If anybody ran into the same trap or has a better solution, please tell!
See also:
http://ift.tt/2cC10aB
http://ift.tt/2cC0byy
http://ift.tt/1Vb6kTL
http://ift.tt/2cC1xJH
http://ift.tt/2cC0Ujl
Symptoms:
- Home button does no longer work.
- Notifications do not work (as consequence, data transfer via USB cable is impossible).
- Quick settings do not work.
- Factory reset does not work.
- Developer mode cannot be enabled (as a consequence, no adb connection possible).
- Automatic orientation disabled after every reboot.
- Mobile data enabled (!) after every reboot (very funny if you pay 0,23 EUR per megabyte and do not notice...)
- When changing volume using the physical keys, the device sometimes reboots.
According to various investigations (see links below) the system thinks that the Setup Wizard is still running. This bug presumably was introduced with some Android version (Oct 2015), came to the Moto G, and when the bug was removed, the Moto G did not get the corrected OS version.
When does the Problem appear?
There are strong indications that the problem always occurs whenever the device runs out of (flash) memory. Note that our device did not have an SD when the problem appeared.
How can one heal the device?
There have been some recommendations how to repair the phone (see links below):
- Change User
- Run the SetupWizardTestActivity via adb
- Run some additional command (see below) via adb.
- Run the SetupWizardTestActivity via Nova Launcher.
- Factory reset via Recovery.
What did really help?
In fact all methods 1 .. 4 failed, because no adb connection could be established (see Topic 5. of the symptoms), and the Setup Wizard got to an endless loop when I started it via Nova Launcher. So finally I used the Recovery system to reset the device.
If anybody ran into the same trap or has a better solution, please tell!
See also:
http://ift.tt/2cC10aB
http://ift.tt/2cC0byy
http://ift.tt/1Vb6kTL
http://ift.tt/2cC1xJH
http://ift.tt/2cC0Ujl
from xda-developers http://ift.tt/2cCkgbf
via IFTTT
No comments:
Post a Comment