• RIL (mobile network, SMS & data) - dual-SIM (V811W)
• Wifi
• Audio (playback/input/routing/headphones/etc)
• Bluetooth
• Camera (photos, camcorder & panorama)
• FM radio
• GPS
• Hardware acceleration and OpenGL rendering
• Hardware video decoding & encoding
• SD card
• USB-storage (on external sdcard) & adb
• USB-tethering
• Wifi-tethering
• Touchscreen/multi-touch
• Sensors
• LEDs

• ???

• Device
• Kernel
• Proprietaries
• legaCyMod

• CyanogenMod team & everyone who's been working on CM11

Like my work?

Do not mirror my builds! Please post a link to this page instead.

lineage-13.0-20170205-UNOFFICIAL-KonstaKANG-kis3.zip
http://konstakang.com/devices/kis3/CM13

Google apps:
The Open Gapps Project

Working:

• RIL (mobile network, SMS & data)
• Wifi
• Audio (playback/input/routing/headphones/etc)
• Bluetooth
• Camera (photos, camcorder & panorama)
• FM radio
• GPS
• Hardware acceleration and OpenGL rendering
• Hardware video decoding & encoding
• SD card
• USB-storage (on external sdcard) & adb
• USB-tethering
• Wifi-tethering
• Touchscreen/multi-touch
• Sensors
• LEDs

Not working:

• ???

Important!!! If you’re using my open sourced work as a part of your project, be fair and give proper credits, and contribute back by keeping your project open source as well. I've put countless hours of my spare time into this project and I deserve at least this (I'm not getting paid to do this). Free and open source doesn't mean without respect!

Sources:

• Device
• Kernel
• Proprietaries

Thanks:

• CyanogenMod/LineageOS team & everyone who's been working on CM13

Like my work?

I'm Algerian and not an english speaker so sorry for my english,

I bought two years ago a ZTE Kis 3 from swisscom in Switzerland. I never used the phone a lot until last September when I needed it. I was using CyanogenMod Android 5.1 the phone was working properly until it started to slowly defect because the volume buttons stopped working. Last week, several applications were spitting up. I donated reset the phone from the settings as I have often done. However the problem persisted and I made the mistake of suppressing the rom by recovery. The phone didn't turn on anymore and stayed on the boot but thanks to the adb I managed to restart it in recovery since the volume keys don't work anymore and I flashed the last version of lineageOs (android 7.1) for ZTE Kis 3 available on your site with the last corresponding gapps. But unfortunately from the phone does not start anymore and stays on the lineageOs boot. The phone is no longer detected by the ADB even though I changed the wire. And the only solution I found on the internet is to use the SP Flash Tool but I can't find the ZTE Kis 3 ScatterFile anywhere.

So I'm asking you if you would have it and if you would have a solution to my problem knowing that I need the phone and I can't buy another one.

Thank you in advance

Build quality & display
When it comes to size, the Mini is only slightly smaller than the Axon 7. In fact, the size difference is hard to notice unless you actually put both phones side by side. The Mini measures 5.8 by 2.8 by 0.3 inches and weighs 5.4 ounces, making it just a bit smaller and lighter than the Axon 7 (6.0 by 3.0 by 0.3 inches, 6.2 ounces), but not nearly as small as the more genuinely miniaturized Sony Xperia X.

The phone hasn't undergone any major changes in design, either. You get the same metal unibody build available in gray or gold, the same gentlyback, and the same button and port placement. a volume rocker and power button on the right side, a USB-C charging port on the bottom, a 3.5mm audio jack up top, and a SIM/microSD card slot on the left (which worked with a 256GB card). The back is home to a responsive fingerprint scanner set below the camera sensor.

The Axon 7 Mini's 1,920-by-1,080, 5.2-inch AMOLED display is smaller, and less sharp, than the 5.5-inch Quad HD panel on its larger sibling. It has 423 pixels per inch, compared with 538ppi on the Axon 7. That said, many other phones in this size range like the 5-inch Google Pixel, and the 5.5-inch Moto G4 also have 1080p panels. The Mini benefits from rich colors, great viewing angles, and a maximum brightness that's easy to see outdoors.

Performance
The phone is powered by Qualcomm Snapdragon 617 processor. It's a midrange chipset, nowhere near as powerful as the Snapdragon 820 you get the larger device. There's also less RAM, 3GB instead of 4GB. Unsurprisingly, this results in significantly lower benchmark results. The Mini scores 46,859 on AnTuTu, which measures overall system performance, which is a lot lower than the Axon 7's 141,989. It's on par with other midrange phones like the Snapdragon 617-powered G4 (46,260) and the Snapdragon 430-powered X2 (43,984).

That said, performance is still fairly smooth. While we encountered some stuttering when running lots of apps in the background, it wasn't any worse than you'll encounter on most midrange phones. A software update pushed out during testing seems to reduce many instances of sluggishness. The phone also handles games like Asphalt 8 and GTA: San Andreas without any difficulty.

Camera quality
Camera performance on the Mini's 16-megapixel rear sensor is solid, but it isn't particularly noteworthy. The phone takes good shots outdoors under brightly lit conditions, but compared with the 20-megapixel sensor on the Axon 7, it doesn't capture as much detail. In a shootout with the Axon 7 (in default Auto HDR mode), we noticed more instances of noise, a slower autofocus, slower shutter speeds, and notably worse low-light performance. The 8-megapixel front sensor is and still takes good selfies and video.

Youtube Review

Connectivity
2G: GSM 850/900/1800/1900MHz
3G: WCDMA 850/900/1700/1900/2100MHz
4G: FDD-LTE B1/B2/B3/B4/B5/B7/B8/B12/B17/B19/B20 TDD-LTE B38/B40/B41

For more information please visit ZTE Axon 7 Mini.

Thank you :)

can anyone pls help me. im trying to figure out how to connect to my blade s7 to install bootloader and recovery.

i stupidly flashed my recovery and boot with the wrong image.been struggling for 4 days

thanx in advance.

  

• RIL (mobile network, SMS & data)
• Wifi
• Audio (playback/input/routing/headphones/etc)
• Bluetooth
• Camera (photos, camcorder & panorama)
• FM radio
• GPS
• Hardware acceleration and OpenGL rendering
• Hardware video decoding & encoding
• SD card
• USB-storage (on external sdcard) & adb
• USB-tethering
• Wifi-tethering
• Touchscreen/multi-touch
• Sensors
• LEDs

• ???

• dual-SIM (V811W) not supported

• Device
• Kernel
• Proprietaries

Thanks:

• CyanogenMod team & everyone who's been working on CM12.1

Like my work?

It has Android version 6.0.1 Qualcomm snapdragon processor.

Help, please.

https://www.clangsm.com/forum/uploads/monthly_04_2017/post-614791-1493523708.jpg

Requests and suggestions are always welcome, any support will be very much appreciated.
And be generous in Liking and Appreciating. .

Disclaimer: This is a preliminary build of MIUI v5, there's still a lot of bugs. It's not meant to be your daily driver. I am not responsible for any damage to your device.

ChangeLog:
04.08.16

- First boot

08.08.16

- Single sim fix

--------------------------------------------------------------------------------------------------
Working:
=> Wifi
=> MIUI features ( except themes )
=> GPS ??
=> Bluetooth ??
=> Camera
=> Audio
=> SD Card
=> USB Storage
=> Touchscreen
=> Sensors
=> LED - Need reconfigure

=> RIL ( Single Sim )

--------------------------------------------------------------------------------------------------

--------------------------------------------------------------------------------------------------
Known Bugs:
=> Phone apps FC
=> Themes Manager not working
=> RIL not working ( Dual Sim )

--------------------------------------------------------------------------------------------------

Install Procedure:
=> Reboot in recovery
=> Wipe data/factory reset
=> Flash rom
=> Flash SuperSU - If you want to have root access
=> Reboot System
=> First boot takes some time, so be patient.
=> Enjoy

--------------------------------------------------------------------------------------------------

Download ROM - 08.08.16
https://www.mediafire.com/?v0b4bksh506exr0

SuperSU-v2.46
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip

--------------------------------------------------------------------------------------------------

Credits:
CM 11 by @KonstaT
MIUI v5 by zlaja84

ROM OS Version: V5
Version Code = 3

Version Information
Status: Alpha

Tips:
Flashing Recommendation
must do a clean install.

--- = SRS One-Click-Root v5.1 =

16:30:09 - Starting ADB Server ..
16:30:16 - Manufacturer: ZTE
16:30:16 - Model: ZTE BLADE A512
16:30:17 - Android Version: 6.0.1
16:30:17 - Build ID: VDF-A512B01-PT_MR03b
16:30:17 - Board ID: MSM8917
16:30:17 - Chipset Platform: msm8937
16:30:17 - Getting OffSets ..: error: only position independent executables (PIE) are supported. (False)
16:30:18 - Query Server for Best Method .. Found Rootkit: 8

---- = Start Rooting Process .. Please Wait = ----

16:30:19 [+] Testing exploit: root8 (please wait ..)
16:30:21 [+] Remounting / system Filesystem as R / W ..
16:30:21 [+] Installing SU Binary ...
16:30:22 [+] Installing SuperUser APK ...
16:30:23 [+] Remounting / system Filesystem as R / O ..

16:30:28 [+] Rooting Complete!

It gives indication that it gets root but it does not stay.

Another program that supposedly works is this one spoken in this video:

Https://www.youtube.com/watch?v=w_U_pjwE_3Q

Program: http://kidapso.com/autorootdl I can not test because I can not download even responding to the proposed surveys.

If you know of any solutions, share. Thank you

Build ID: VDF-A512B01-PT_MR03b

I would like to have my edited device files double checked. So I can be confident in building the custom recovery.

I have installed a linux mint VM.I believe I have correctly setup the build environment. I have successfully built a few kernels and roms for a different device.

I started by repo syncing CM11 and ran extract-files.sh. This gave me a device folder zte/n817..

I looked at Boardconfig.mk and their seemed to be some errors I marked in red

This is the original unedited Boardconfig.mk

[HIDE]

USE_CAMERA_STUB := true

# inherit from the proprietary version
-include vendor/zte/n817/BoardConfigVendor.mk

TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := unknown
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_VARIANT := cortex-a7
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true

TARGET_BOOTLOADER_BOARD_NAME := n817

BOARD_KERNEL_CMDLINE := androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37
BOARD_KERNEL_BASE := 0x00000000
BOARD_KERNEL_PAGESIZE := 2048

# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072

TARGET_PREBUILT_KERNEL := device/zte/n817/kernel

BOARD_HAS_NO_SELECT_BUTTON := true
[/HIDE]

This is my Boardconfig.mk I edited. Changes marked in red

[HIDE]

USE_CAMERA_STUB := true

# inherit from the proprietary version
-include vendor/zte/n817/BoardConfigVendor.mk

TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := msm8610
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_VARIANT := cortex-a7
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true

TARGET_BOOTLOADER_BOARD_NAME := n817

BOARD_KERNEL_CMDLINE := androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37

BOARD_KERNEL_BASE := 0x00000000 - Don't know what to put here

BOARD_KERNEL_PAGESIZE := 2048

# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 16777216
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 16777216
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1291845632
BOARD_USERDATAIMAGE_PARTITION_SIZE := 1862270976
BOARD_FLASH_BLOCK_SIZE := 131072

TARGET_PREBUILT_KERNEL := device/zte/n817/kernel

BOARD_HAS_NO_SELECT_BUTTON := true

[/HIDE]

The ZTE n817 Quest does not have mtd. So I ran adb shell and cat /proc/partitions and ls -al /dev/block/platform/msm_sdcc.1/by-name also mount and df commands.
I then used  dd if=/dev/block/mmcblk0** of=/sd card/***.img  to dump the phones whole image and each partition separately.

Looking at all these outputs I put this together.

[HIDE]
#blocks ----  by-name      ----        partitions          ----               size
8192 ----     DDR ->    ----        /dev/block/mmcblk0p2
8192  ----    aboot ->    ----      /dev/block/mmcblk0p15
16384  ----   boot ->     ----      /dev/block/mmcblk0p17      ----  16384 x  1024     =     16777216
311296 ----   cache ->   ----       /dev/block/mmcblk0p22
40960  ----   carrier ->  ----      /dev/block/mmcblk0p23
8192  ----    dbi ->      ----      /dev/block/mmcblk0p5
8192   ----   fsc ->     ----       /dev/block/mmcblk0p11
8192   ----   fsg ->     ----       /dev/block/mmcblk0p12
8192   ----   misc ->    ----       /dev/block/mmcblk0p21
131072 ----   modem ->    ----      /dev/block/mmcblk0p16
8192   ----   modemst1 ->  ----     /dev/block/mmcblk0p13
8192  ----    modemst2 ->  ----     /dev/block/mmcblk0p14
8192   ----   pad ->    ----        /dev/block/mmcblk0p9
32768  ----   persist ->   ----     /dev/block/mmcblk0p8
16384  ----   recovery ->  ----     /dev/block/mmcblk0p18      ----     16384 x 1024   =  16777216
8192  ----    rpm ->    ----        /dev/block/mmcblk0p3
8192   ----   sbl1 ->    ----       /dev/block/mmcblk0p1
16384  ----   splash -> ----        /dev/block/mmcblk0p19
8192   ----   ssd ->   ----         /dev/block/mmcblk0p10
1261568 ----  system ->  ----       /dev/block/mmcblk0p24       ----  1261568 x 1024  =    1291845632
8192  ----    tombstones ->  ----   /dev/block/mmcblk0p20
8192  ----    tz ->   ----          /dev/block/mmcblk0p4
1818624 ----  userdata ->  ----     /dev/block/mmcblk0p25       ----    1818624 x 1024  = 1862270976
8192  ----    ztecfg ->  ----       /dev/block/mmcblk0p7
8192  ----    ztelk ->    ----      /dev/block/mmcblk0p6

=======================================================================
=======================================================================

Filesystem                              Size     Used     Free   Blksize
/dev                                   198.8M   132.0K   198.6M   4096
/sys/fs/cgroup                         198.8M    12.0K   198.7M   4096
/mnt/asec                              198.8M     0.0K   198.8M   4096
/mnt/obb                               198.8M     0.0K   198.8M   4096
/system                                  1.2G   780.7M   430.1M   4096
/data                                    1.7G   642.1M     1.1G   4096
/cache                                 299.0M     5.8M   293.2M   4096
/persist                                31.5M     4.1M    27.4M   4096
/carrier                                39.4M     4.0M    35.3M   4096
/firmware                               64.0M    41.0M    23.0M   16384
/mnt/shell/emulated                      1.7G   642.1M     1.1G   4096
/storage/emulated/legacy                 1.7G   642.1M     1.1G   4096
/storage/emulated                      198.8M     0.0K   198.8M   4096
/mnt/media_rw/sdcard1                   29.8G     9.7G    20.1G   8192
/storage/sdcard1                        29.8G     9.7G    20.1G   8192
/storage/emulated/0                      1.7G   642.1M     1.1G   4096
/storage/emulated/0/Android/obb          1.7G   642.1M     1.1G   4096
/storage/emulated/legacy                 1.7G   642.1M     1.1G   4096
/storage/emulated/legacy/Android/obb     1.7G   642.1M     1.1G   4096

[/HIDE]

This is the cm.mk

[HIDE]
## Specify phone tech before including full_phone
$(call inherit-product, vendor/cm/config/gsm.mk)

# Release name
PRODUCT_RELEASE_NAME := n817

# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_phone.mk)

# Inherit device configuration
$(call inherit-product, device/zte/n817/device_n817.mk)

## Device identifier. This must come after all inclusions
PRODUCT_DEVICE := n817
PRODUCT_NAME := cm_n817
PRODUCT_BRAND := zte
PRODUCT_MODEL := n817
PRODUCT_MANUFACTURER := zte
[/HIDE]

 -- but I'm not sure it is right. Because the ZTE n817 Quest is identified as
[HIDE]
ro.product.model=N817
ro.product.brand=ZTE
ro.product.name=ZTE_WELLINGTON
ro.product.device=wellington
ro.product.board=wellington
ro.build.description=ZTE_WELLINGTON-user 4.4.4 KTU84P 20150821.163315.3491 release-keys
ro.build.fingerprint=ZTE/ZTE_WELLINGTON/wellington:4.4.4/KTU84P/20150821.163315.3491:user/release-keys
ro.build.characteristics=cdma
from device/zte/wellington/system.prop

[/HIDE]

This is the device_n817.mk

[HIDE]
$(call inherit-product, $(SRC_TARGET_DIR)/product/languages_full.mk)

# The gps config appropriate for this device
$(call inherit-product, device/common/gps/gps_us_supl.mk)

$(call inherit-product-if-exists, vendor/zte/n817/n817-vendor.mk)

DEVICE_PACKAGE_OVERLAYS += device/zte/n817/overlay

LOCAL_PATH := device/zte/n817
ifeq ($(TARGET_PREBUILT_KERNEL),)
    LOCAL_KERNEL := $(LOCAL_PATH)/kernel
else
    LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL)
endif

PRODUCT_COPY_FILES += \
    $(LOCAL_KERNEL):kernel

$(call inherit-product, build/target/product/full.mk)

PRODUCT_BUILD_PROP_OVERRIDES += BUILD_UTC_DATE=0
PRODUCT_NAME := full_n817
PRODUCT_DEVICE := n817
[/HIDE]

The AndroidProducts.mk

[HIDE]
PRODUCT_MAKEFILES := \
    $(LOCAL_DIR)/device_n817.mk
[/HIDE]

This is AndroidBoard.mk

[HIDE]
LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

ALL_PREBUILT += $(INSTALLED_KERNEL_TARGET)

# include the non-open-source counterpart to this file
-include vendor/zte/n817/AndroidBoardVendor.mk
[/HIDE]

This is the original unedited recovery.fstab I got using extract-files.sh

[HIDE]
# mount point    fstype    device        [device2]

/boot       mtd         boot
/cache      yaffs2      cache
/data       yaffs2      userdata
/misc       mtd         misc
/recovery   mtd         recovery
/sdcard     vfat        /dev/block/mmcblk0p1        /dev/block/mmcblk0
/system     yaffs2      system
/sd-ext     ext4        /dev/block/mmcblk0p2
[/HIDE]

Do I need to sync a clockworkmod recovery in the CM11 tree and replace android_bootable_recovery or android_bootable_recovery-cm ¿?

The phones vendor Proprietary Blobs have not been extracted yet. I didn't get the vendor files when I ran extract-files.sh.. I'm not finding the right way to extract the phones vendor files. I keep find different or conflicting instructions.

Is there any tips or advice you would give me in helping me build the custom recovery ¿¿

Thank you for helping me with this

thanks to Sattarvoybek from 4pda we've got a working TWRP for the S7!!!

Install it by dd if=/sdcard/recovery.img of=/dev/block/bootdevice/by-name/recovery

(only if u've got root! ;) )

https://4pda.ru/forum/index.php?showtopic=697227&st=340

Download: https://drive.google.com/open?id=0B4Ya5mT9NhjqUUZyVTFDT18xQlU

I have 2 problems and I need your help and advices.

I've a french ZTE Open C with the cm13 of KonstaT.

My IMEI is 0. Is it possible to restore it? Or mask it? I don't have a backup of my stock rom and I know it's illegal to change it but it's already changed.

I can only connect to Edge and I have the good APN. Is it related? How can I fix this?

Should I try to flash my stock ROM? Is it a baseband problem?

Have a good day

So today when I saw it person, I went to go through recovery menu, but I couldn't go up, only down, and up volume was "stuck". So when I opened phone, I saw a broken volume up switch. Is there any way for me to pull contacts from the phone? Is there any way to get out of recovery? Because it looks like phone thinks I'm holding volume up and power and goes straight to recovery mode

After tearing my hair out and going slightly nuts on those 4 days. I finely figured out the syntax of the cmd structure for this tablet. I now have the tablet talking to my laptop in the bootloader mode. If I try to download a img file and flash it to the tablet. The tablet just sat there and did nothing. Now the tablet will flash on it's screen after reading the img. That the img has the wrong keys and so on and reject the img . The correct sequence for this tablet is, in recovery mode choose "apply update from ADB". Then in Windows terminal type "adb sideload <and the file name>". It has to be SIDELOAD not DOWNLOAD, that's the key to the cmd sequence in this tablet. And "adb reboot bootloader" does nothing. The reboot bootloader has to be done by power button + volume down button. At lease now I made some progress on this tablet after 4 days work. A good thing in that it is a good inside project on these cold snowing days. Now I just need to find the right recovery-CWM image file for this tablet.    Konsta the tablet rejects the "recovery-cwm6051-kis3.img" file of yours.  Could you please tell me were I can download the right recovery-CWM file.  This sideload cmd sequence sure through me for a loop. Since I started using Android phones I had to learn a new OP system. I have been a Windows tech for many years. I have successfully rooted 3 phones and 2 tablets that I have owned over the years. I only hard bricked 1 phone.

Steve

Important. Prerequisites!!! You need to install Android KitKat on your Open C first (e.g. EU_FFOS+to+Android.zip will do). You also need to have this ClockWorkMod or this TWRP recovery installed.

Do not mirror my builds! Please post a link to this page instead.

cm-12.1-YOG3C-KonstaKANG-kis3.zip (yes, you need to use this exact CM12.1 build as a base)
http://konstakang.com/devices/kis3/SailfishOS
md5:23593b90fb7be93a7e14aec6a3a95f68

sailfishos-kis3-release-2.0.0.10-20160123-alpha2.zip
http://konstakang.com/devices/kis3/SailfishOS
md5:bf5ac7346ed5e08e32c884fd0022409c

Working:

• Audio
• Bluetooth
• Camera (photos & camcorder)
• Display
• GPS
• Headphones (run 'systemctl restart ohmd.service' as root after each reboot)
• Media decoding/encoding with gstreamer codecs
• RIL (voice calls, SMS & mobile data)
• Sensors
• SD card
• Touchscreen
• USB storage (MTP only - choose 'PC connection' mode from settings)
• USB-tethering
• Vibrate
• Wifi
• Wifi-tethering

Partially working:

• FM radio - not hooked to UI yet - command line guide in this post

Not working:

• and more...

Issues:

• Display auto-brightness is enabled by default on first boot so display is very dark on devices that don't have an ambient light sensor ('Settings -> System -> Display -> Adjust automatically' to disable)
• Display brightness setting allows decreasing brightness below 'minimum' which powers off the panel completely (don't do it ;))
• Proximity sensor disabled for now -  wasn't working(?) and would cause display to switch (and stay) off during calls
• There is some kind boot time race condition with systemd services and device fails to boot to Sailfish OS sometimes and reboots itself instead (remove battery, wait for stars to align better and try again :P)

Sources:

• mer-hybris
• mer-hybris-kis3

Thanks:

• Jolla
• Sailfish OS HADK (Hardware Adaptation Development Kit)
• sledges, mal- & people at #sailfishos-porters

Like my work?