The first step is to convince that the engineer of amazon is facing a brick-making machine, and the software and tools he owns is basically the same as we have. At least, it is a matter of repairing bricks. So, please trust us to toss it out. : No brick can't be repaired.
The second step, download some programs and packages that may be needed first
1. Debugging tool:
Windows: fastboot.exe adb.exe usb_driver
Linux/mac: fastboot adb-linux/adb-mac
2. The system's bootstrapping and expris
Boot.img
Updaterecovery.img
Stockrecovery.img
zergRush
3. A heart that dares to learn and explore.
(All the above file attachments will be packaged and downloaded, including windows/linux/mac version)
The third step is to operate in the following situations
1. Input method installation failed: (Always stuck in the boot LOGO can not enter the system)
1) Connect the KF to your computer and install the driver to ensure that the adb shell can be used
2) After temporarily upgrading the permissions again, fix permissions for settings.db:
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) The machine will restart and it will be OK
2. One of the mistakes in the brushing process: The beautiful brushing menu has always appeared.
1) Connect the KF to your computer and install the driver to ensure that the adb shell can be used
2) Brush the original boot program directly to boot correctly:
Adb push stockrecovery.img /sbin/
Adb shell "dd if=/sbin/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery"
Adb reboot
3) The machine will restart and it will be OK
3. Fastboot operation error, or the above two methods are invalid:
Sometimes the adb shell can't be used in this case, so you need to try several methods. Please try it out in order:
Method one, empty user data, repair boot mode:
Fastboot -i 0x1949 -w
Fastboot -i 0x1949 oem idme bootmode 0x4000
Fastbooot -i 0x1949 reboot
Method two, re-write the boot image, 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 three, final method, completely re-brush the official system, repair all bricks
The second step, download some programs and packages that may be needed first
1. Debugging tool:
Windows: fastboot.exe adb.exe usb_driver
Linux/mac: fastboot adb-linux/adb-mac
2. The system's bootstrapping and expris
Boot.img
Updaterecovery.img
Stockrecovery.img
zergRush
3. A heart that dares to learn and explore.
(All the above file attachments will be packaged and downloaded, including windows/linux/mac version)
The third step is to operate in the following situations
1. Input method installation failed: (Always stuck in the boot LOGO can not enter the system)
1) Connect the KF to your computer and install the driver to ensure that the adb shell can be used
2) After temporarily upgrading the permissions again, fix permissions for settings.db:
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) The machine will restart and it will be OK
2. One of the mistakes in the brushing process: The beautiful brushing menu has always appeared.
1) Connect the KF to your computer and install the driver to ensure that the adb shell can be used
2) Brush the original boot program directly to boot correctly:
Adb push stockrecovery.img /sbin/
Adb shell "dd if=/sbin/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery"
Adb reboot
3) The machine will restart and it will be OK
3. Fastboot operation error, or the above two methods are invalid:
Sometimes the adb shell can't be used in this case, so you need to try several methods. Please try it out in order:
Method one, empty user data, repair boot mode:
Fastboot -i 0x1949 -w
Fastboot -i 0x1949 oem idme bootmode 0x4000
Fastbooot -i 0x1949 reboot
Method two, re-write the boot image, 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 three, final method, completely re-brush the official system, repair all bricks
Guangzhou Ehang Electronic Co., Ltd. , https://www.ehangmobile.com