Professional Documents
Culture Documents
Sign In Sign Up
Search...
Home Activity Store Support Leaderboard
1 2 3 4 5 NEXT Page 1 of 5
This recovery is fully working with goodies such as repeatable keys and adb sideload support. Use volume keys to navigate
menus and power button to select. Internal sdcard is handled differently on Open C and Kis 3 so this recovery only supports
external sdcard.
Do not use this recovery to flash official updates from ZTE website! You need to repack them for ClockWorkMod or use the stock
recovery to install.
How to make clean ROM dump/backup of your device (before you root or install CWM):(recommended)
1. Download and install ZTE USB drivers (windows) or setup udev rules (linux)
2. Download and install Android SDK tools and platform-tools to get adb and fastboot
3. Download recovery-cwm60xx-kis3.img recovery image and rename it to recovery.img
4. Create a new directory somewhere and copy adb(.exe), fastboot(.exe) and recovery.img into it
5. Enable USB debugging on your device (Firefox OS - Settings -> Device information -> More Information -> Developer -> Remote
Debugging --- Android - Settings->Developer options -> Android debugging)
6. Plug in your device via USB cable and install drivers if necessary
7. Open terminal window as an administrator (windows) or execute adb commands with sudo (linux)
8. Change into the directory you've created and execute following commands in terminal window (boots into recovery instead of
flashing it)
9. select backup & restore -> backup (Seriously, always backup your device before you install anything!)
10. Boot into ClockWorkMod by pressing volume up while powering on or using 'adb reboot recovery'
11. Select backup & restore -> backup (Seriously, always backup your device before you install anything!)
Sources for the recovery are available in my github. You can compile it yourself using CM11 source tree.
Like my work?
ClockWorkMod 6.0.5.1
14.8. changelog:
initial release
Members
3,952
4,651 posts
Previous builds:
Location: Finland
Twitter: @konstatuomio
recovery-cwm6050-kis3.img
http://konstakang.com/devices/kis3/CWM
md5:2333a51e306976dc4dbacf0856a3b915
Edited January 8, 2017 by KonstaT
Moderator Team
147
3,685 posts
Location: northampton
Devices: Crackling Ham
Armani wt88047
Twitter: @philipnwright
got round it by booting cwm recovery by adb, installing cm11 and then rebooting to bootloader and flashing cwm
Moderator Team
147
3,685 posts
Location: northampton
Devices: Crackling Ham
Armani wt88047
Twitter: @philipnwright
Members
0
1 post
C:\a>fastboot reboot
rebooting...
C:\a>
and then when i press the power and the volume up it takes me to the old fastboot menu and not the
ClockWorkMod Recovery
menu
please advice...
C:\a>fastboot reboot
rebooting...
C:\a>
and then when i press the power and the volume up it takes me to the old fastboot menu and not the
ClockWorkMod
Recovery menu
please advice...
By old fastboot, I take you mean the stock recovery? Bootloader mode just stays on the splash screen and you'll have fastboot
access.
Have you flashed ZTE updates to your device? It means that you'll likely have a script (/system/etc/install-recovery.sh) that will
replace your recovery with the stock one during a reboot.
Boot the recovery without installing it (fastboot boot recovery-cwm60xx-kis3.img) and make a backup of your stock ROM like
instructed. When you select 'reboot' to boot out of recovery it should ask two questions. Something about root (you can ignore
that) and then a warning about your custom recovery being overwritten. Select the option to prevent that. You should be able to
flash it to the recovery partition so that it will stick after that.
Great to see KonstaT working on Kis 3. I had a Blade and I've used many of his great roms. Thanks for everything KonstaT! : )
I've tried to install CWM on my Smart A16 (from Portugal). I'm on windows 8.1. I've followed this guide and installed everything
needed, but when I execute "adb reboot bootloader", the phone turns black, and then when I execute "fastboot boot
Members recovery-cwm6050-kis3.img", it keep on waiting for the devide. I've notice that when I run the first comand, on device
management, the phone get's like it lost the drivers or something like that, it show "android device" or something like that - can't
5 remember now - with an exclamation port. Since that's happening to me, I can't install CMW. Can someone help? What am I
43 posts
doing wrong, did I misse something?
Devices: ZTE Blade Gen 2
(Sapo a5)
Thanks again and keep up your amazing work Konstat! : )
Kind regards!
Members
3,952
Convertido de web en PDF a http://www.htmlapdf.com con el api html a pdf
4,651 posts
Location: Finland Hi!
Twitter: @konstatuomio
Great to see KonstaT working on Kis 3. I had a Blade and I've used many of his great roms. Thanks for everything KonstaT! :
)
I've tried to install CWM on my Smart A16 (from Portugal). I'm on windows 8.1. I've followed this guide and installed
everything needed, but when I execute "adb reboot bootloader", the phone turns black, and then when I execute "fastboot
boot recovery-cwm6050-kis3.img", it keep on waiting for the devide. I've notice that when I run the first comand, on device
management, the phone get's like it lost the drivers or something like that, it show "android device" or something like that -
can't remember now - with an exclamation port. Since that's happening to me, I can't install CMW. Can someone help? What
am I doing wrong, did I misse something?
Kind regards!
Yeah, it's a driver issue. I still can't believe how winblows can have such major issues with this. Fastboot is a generic Google
mode (USB\VID_18D1&PID_D00D), it's not even something that you'd need a vendor specific driver. There's people with the same
issue on my Blade III CWM thread and also few versions of fastboot drivers posted there. Also Google search for 'windows 8
fastboot driver' will give you plenty of results.
Take care!
The handset is an Open C from Ebay and I've installed theEU_FFOS+to+Android.zip rom.
Members
My computer is Windows 7 64 bit and I have Android SDK installed plus the ZTE handset USB drivers.
0
22 posts
Devices: Lenovo A830
ADB shows the phone if I list devices but when I run the command to reboot to bootloader the phone switches off and the windows
Twitter: @yorksims
gong sounds to show it's dissconected but then the gong sounds again rapidly 3 or 4 times and the phone stays switched off.
Any ideas?
Members
5
43 posts
Devices: ZTE Blade Gen 2
Convertido de web en PDF a http://www.htmlapdf.com con el api html a pdf
(Sapo a5)
I have what is probably a very simple problem that has me pulling my hair out at the moment so any advice would be great.
The handset is an Open C from Ebay and I've installed theEU_FFOS+to+Android.zip rom.
My computer is Windows 7 64 bit and I have Android SDK installed plus the ZTE handset USB drivers.
ADB shows the phone if I list devices but when I run the command to reboot to bootloader the phone switches off and the
windows gong sounds to show it's dissconected but then the gong sounds again rapidly 3 or 4 times and the phone stays
switched off.
Any ideas?
yorksims, watch the video above, do the same things on win 7 - the disable signature thing - and download and install the adb
driver that is on video description. Hope it works - it did for me, I had the same problem, but on win 8.1.
Members
3,952
Convertido de web en PDF a http://www.htmlapdf.com con el api html a pdf
4,651 posts
Location: Finland I have what is probably a very simple problem that has me pulling my hair out at the moment so any advice would be great.
Twitter: @konstatuomio
The handset is an Open C from Ebay and I've installed theEU_FFOS+to+Android.zip rom.
My computer is Windows 7 64 bit and I have Android SDK installed plus the ZTE handset USB drivers.
ADB shows the phone if I list devices but when I run the command to reboot to bootloader the phone
switches off and the windows gong sounds to show it's dissconected but then the gong sounds again rapidly 3
or 4 times and the phone stays switched off.
Any ideas?
It doesn't switch off. There's just no visual confirmation that you've booted to bootloader mode. On Firefox OS bootloader, it just
stays on the splash image. On Android bootloader, it stays on a blank screen. This is when you should execute fastboot
commands. E.g. you can 'fastboot devices' to see that you can access your device. If not, you likely need to install some fastboot
drivers (see above).
I had suspected a driver issue but my device manager showed no missing drivers and a ZTE adb driver installed so I wrongly
assumed that it would work.
Convertido de web en PDF a http://www.htmlapdf.com con el api html a pdf
However,for some strange reason,when I uninstalled the ZTE adb driver and installed the one shown in the video then everything
worked.
Members
To make sure everything was working properly as I went along I used the commands
0
22 posts
Devices: Lenovo A830
Twitter: @yorksims
adb devices
fastboot devices
and with the new driver installed fastboot showed the device and I could continue to boot into the new recovery to make a backup
then go through the process again to flash it.I then flashed Super SU and one of the trimmed down versions of Gapps and now
have one very cheap (£38.99) Kitkat phone to use for work.
I do also have a small confession to make though that may save others some grief,don't do what I did and blindly copy and paste
the fastboot commands from the OP and then wonder why fastboot can't find the recovery file.
I spent another half hour scratching my head before realising that the command in the OP refers to cwm60xx but of course the
image file is cwm6050 so once I'd put right that schoolboy error that I'd made,all was good.
Members
0
4 posts
Members
3,952
4,651 posts
Location: Finland
Twitter: @konstatuomio
It doesn't switch off. There's just no visual confirmation that you've booted to bootloader mode. On Firefox OS bootloader, it
just stays on the splash image. On Android bootloader, it stays on a blank screen. This is when you should execute fastboot
commands. E.g. you can 'fastboot devices' to see that you can access your device. If not, you likely need to install some
fastboot drivers (see above).
Members
0
4 posts
Members
0
2 posts
Devices: ZTE V790
But when I try to enter into Recovery Mode, there is only green robot logo, no any menu. So I switched to version 6.0.3.3
Installing update...
Error in /sdcard/cm-11-20140914-UNOFFICIAL-KonstaKANG-kis3.zip (Status 0).
Installation aborted.
And what you makes you think you should be able to flash any of my builds to a V790? It's a completely different device!
Members ZTE V790 aka ZTE Kis aka ZTE Open is a msm7x27a device and it's codename is roamer2.
3,952
4,651 posts This is for ZTE Kis 3 aka ZTE Open C which has a msm8610 chipset.
Location: Finland
Twitter: @konstatuomio
Is Kis III and Kis 3 are different devices? Many people think they arethe same
Members
0
2 posts
Devices: ZTE V790
Is Kis III and Kis 3 are different devices? Many people think they arethe same
Members There's probably about a dozen marketing names/variants of that device (like there is for this device as well). MoDaCo has a
3,952 separate forum section for your device.
4,651 posts http://www.modaco.com/forum/708-zte-kis-orange-dublin/
Location: Finland
Twitter: @konstatuomio
Members
0
3 posts
Devices: ZTE Kiss3, ZTE
Open C
Sure, if you choose to install separate Google apps package (you don't have to if you don't want to).
Then some Android 101. Concept of root (having administrative access) is something related to running an operating system.
You don't need to root your device to install a custom recovery (CWM, TWRP), you only need to have an 'unlocked' bootloader that
Members is accessible with fastboot (which all of these ZTE devices already have). You don't need to root your device to install a custom
3,952
ROM (e.g. CM11), you only need to use a custom recovery to install (consider it an OS of it's own). CM11 itself has root access
4,651 posts
Location: Finland
built in.
Twitter: @konstatuomio
Members
0
3 posts
Devices: ZTE Kiss3, ZTE
Open C
help me ?? :(
Members
0
9 posts
Devices: ZTE V811W
1 2 3 4 5 NEXT Page 1 of 5
GO TO TOPIC LISTING
ZTE General Discussion
Theme Contact Us