Phone Does not Boot After OTA from 4.0.5 to 4.0.6

Question

Phone Does not Boot After OTA from 4.0.5 to 4.0.6

Closed this issue 8 years ago · 7 comments

OTAed from 4.0.5. Gets stuck at CM boot animation. Can not do adb logcat either (error message is : read: unexpected length.)

Answer 1 · 2016-08-11T18:16:27.000Z

Clean flash is OK. @saintsantos Can you flash 4.0.5 and let it OTA to 4.0.6 and see if the problem exists?

Answer 2 · 2016-08-12T05:00:16.000Z

Tried build a new platform (4.0.7) that only has phonelab/cm-13.0/develop branch. OTA from 4.0.5 to 4.0.7 does not work either. Same symptoms and same error message.

I suspect something is wrong in updating the boot image. Also, I did not see patch for /system/bin/kmsgd, which is supposed to be in the OTA package.

Answer 3 · 2016-08-12T14:33:05.000Z

We added the patch yesterday. Pull device/moto/shamu and you should be good. Was also took Scott's device from 4.0.5 and adb sideloaded the ota and his device booted fine and there doesn't seem to be any issue.

Answer 4 · 2016-08-12T14:33:34.000Z

shaseley commented 8 years ago

Answer 5 · 2016-08-12T16:58:42.000Z

I did not see any new changes in device/moto/shamu. The last commit was from ef1dc at 8/11 1 pm.

Answer 6 · 2016-08-13T00:46:53.000Z

OTA 4.0.7 -> 4.0.8 works.

Answer 7 · 2016-08-15T00:41:04.000Z

Fixed by setting SELinux to permissive mode in recovery kernel.