Playing with the actual processors and programming them to behave the way you wanted isn’t as easy as you think it is. Those who have been cross compiling ROMS by themselves or those who dare to flash custom ROMS into their phone would definitely know the extent of the efforts required for developing ROMS, apps for your android device.
It’s very usual that you mess up with your phone while flashing ROMS or configuring kernel etc. Here are some tips to quickly recover from such situations. I’ll be listing down more as I go on learning new ones.
Phone stuck at start up logo:
- This situation is called boot-loop where while executing instructions one by one, your phones stuck in between and can’t proceed until it gets results from current task and that current task never gives results and it loops there forever. In such case, go to recovery ( search for “How to boot <your device model name” to recovery>” and wipe data, dalvik and cache partitions. In the process, you might loose all your internal data but that’s the only quick solution to get out of it. Basically you hard reset your phone.
Phone not turning ON just notification light blinks:
- There could be two reasons for this. Either your phone is completely lost the battery charge, in that case you keep it for charging and wait for it to come back on.
- If you keep it for charging and even after few ours of charging, if it still blinks notification light with no signs of turning ON the screen, congratulations, you have broken your phone and can’t really do anything about it. You can put it in showcase though.
fastboot.exe devices doesn’t show up any device :
- while flashing you might need help from fastboot command to flash the stock firmware. Lot of times fastboot devices command doesn’t show any of the connected device. In such cases there could be two reasons for this to happen.
- first, you might need to reinstall your device drivers or check if your device as fastboot drivers. Download them and install.
- Else, for some OEMS, there is an extension to fastboot command like “fastboot -i 0x2b4c” for Lenovo phones. Check if your OEM has any of such extensions. Use that with fastboot. It should definitely solve the issue.
- Third reason , you might need to turn on usb debugging from Developer options in your android phone. Here’s how you do it –> How to turn ON usb debugging in android.
Phone not turning ON, boots into recovery:
- If after flashing, your phone doesn’t turn ON, if it boot again and again into recovery, the easiest solution is to flash recovery again. It’s the recovery partition which usually gets messed up and that’s why your phone boots into recovery. Re-flashing recovery should always solve the problem.
Stay tuned. This is just part 1. I’ll be posting more soon.
Let me know your difficulties and FAQ in the comment section below. Feel free to mail me your detailed problems at email@example.com or you can start discussing at FAQ section “FAQ“.
Have a good day :-). Peace !!!