The reasons of flashing TV box or smart TV becomes brick:

1. Failed to install the input method, mainly caused by the incorrect file permissions -"Settings. db";

2. Operation error in the process of flashing ;

3. Fastboot is used.

Believe it or not, professional engineers have basically the same software and tools that we have for a bricked device. So believe what we've come up with: no brick is beyond repair.

● Failed to install the input method: because the operating system of android originates from Linux, the control of permissions is very strict, and the system startup stage is started by using the system user.

After we upload the file, the system user actually has no access to our file.As a result, system users cannot read settings.db and are stuck in the boot LOGO together.

● Operation error in the process of flashing:in fact, the most dangerous operation, is often the easiest, flashing itself is not easy to make mistakes, if this process goes wrong, you can turn on the device to flash constantly.

● Fastboot cannot be restored after using: fastboot is the user can use the lowest level of the modification tool, at present all the operations can be completed without fastboot, it is strongly recommended not to use fastboot for the operation such as flashing.

The feature of fastboot is powerful function, but almost every change will lead to a change in the underlying system, that is, if you do not know what you are doing, do not use fastboot.

After understanding the cause, then solve it step by step:

Failed to install the input method :(cannot be entered into the system because LOGO has been stuck in the boot)

(1)connect the KF to the laptop, install the drive, make sure the adb shell is available

(2)repair settings.db's permissions after temporarily raising the permissions again

   adb zergRush /data/local/tmp/.
　　adb shell "chmod 777 /data/local/tmp/zergRush"
　　adb shell "./data/local/tmp/zergRush"
　　adb wait-for-device
　　adb shell "chown system.sytem /data/data/com.android.providers.settings/databases/settings.db"
　　adb shell "chmod 660 /data/data/com.android.providers.settings/databases/settings.db"
　　adb reboot

(3) Restart the dervice and you will find that everything is OK.

One of the errors: the flashing menu keeps appearing

(1)connect the KF to the laptop, install the drive, make sure the adb shell is available

(2) directly flashing back the original bootstrap program to correctly guide:

   adb shell "dd if=/sbin/
   stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery"
　　adb reboot

(3) Restart the dervice and you will find that everything is OK.

Fastboot goes wrong, or the above methods are invalid:

Sometimes adb shell is no longer available in this case, so you need to try a variety of methods. Please try them one by one:

Method 1: clear user data and repair boot mode:

 　 fastboot -i 0x1949 -w 
　　fastboot -i 0x1949 oem idme bootmode 0x4000
　　fastbooot -i 0x1949 reboot

Method 2: re-write the boot image and repair the boot mode:

　  fastboot -i 0x1949 boot boot.img
　　fastboot -i 0x1949 -w 
　　fastboot -i 0x1949 oem idme bootmode 0x4000
　　fastbooot -i 0x1949 reboot

Method 3: the final method, completely reflash the official system, repair all the bricks.

Conclusion

If your smart TV or Android TV box became brick, please analyze the cause first, then solve it step by step. But the most important thing is flashing is risky, it requires careful consideration first.