Hello I have a Geprc Cinelog25 v2 that I purchased a few months ago. I tried to fly the cinewhoop this morning but the quad refused to liftoff the ground. I had a light crash into the carpet the night before but didnt think much of it. Motor number 2 will spin up after arming but it starts to spin after the other 3 motors. I checked ESC config and the configurator can find the firmware on all but the number 2 motor. I tried flashing that motor ESC but a get a error 206, something about a page layout. The AIO is on BF4.5 I tried 2 different versions of BF configurator with no luck.

I was going to order as new motor for it but I am concerned its the AIO not the motor. Would the motor still spin up if it was bad? If the motor is bad, what in the motor would cause failure? I am no expert but it seems to me that there isnt much that can go bad with a motor. When it spins up the motor sounds normal. Is it more likely something is bad on the AIO?I was thinking on flashing the AIO firmware to a earlier version but not sure if that would help.

Any ideas how to proceed?

Thanks for your time 
FlybyJames

Swap motors.. see if the issue follows the motor.. if it does .. it’s the motor.. if it stays at the motor location .. it’s the esc.
I would start with removing the props, connect to betaflight.. power up each motor individually with keeping your hand on the drone body so you can “feel” as well as “hear” each motor..

Ok thanks very much I will give that a go.

https://youtu.be/qtvrG4ilWgk?si=eM4l-laSS3H5d8BE

Thanks for the awesome suggestions. The solution to the problem was not covered in his video but was still informative. JB always has good stuff and I learned something today. The fix was flashing the firmware on ESC #2, the esc configurator would originally not see any firmware on motor 2 and I was getting a #206 page layout error when I tried to flash that firmware. There is a option to disable that layout function in the configurator. When disabled the firmware flashed without issue. The Cinelog is now back in the air. Still uncertain why this happened and ultimately I fear it will be a ongoing issue with this AIO. 

Thanks for the help
FlybyJames