[DEV][ROM][17.11.] CyanogenMod 11 (Android 4.4.4) for ZTE Open C / Kis 3

[Guest arifvox]

this work for V815W?

[Guest minipower]

I have a ZTE Quest N817 which has the MSM8610 CPU. I believe these phones have the same MSM8610 CPU and are similar
ZTE Open C / Kis 3 (Beeline Smart2, Moche/MEO Smart A16, ZTE V811W, ZTE V811, Skinny V811, Optus Hop Smart, ZTE Blade M

Do you think it would it be possible for me to use this recovery and rom on the ZTE Quest N817 ¿

I also have the SPC for the phone. All I have been able to do is backup the efs, but was unable to backup some of the folders because they are still locked, even tho I entered the SPC into the box. Does anyone know how to root by using the SPC ¿

The rom is missing the SU binary from the data folder. The phone does not have fastboot enabled. It does have FTM mode and I am also able to get the phone into what I think is called Bootloader mode (Holding volume up/down and power. which turns the phone on with a blank black screen) So I am unable to remount to read write with ADB

I believe the Bootloader is also locked. Is it possible to use the Open C tool to unlock the Bootloader ¿

Here is the specs of the ZTE Quest N817 off http://specdevice.com

General Specifications

[HIDE]Manufacturer    ZTE
Model    N817
Android version    4.4.4; 20150821.163315.3491; SDK19
CPU    2 cores; Qualcomm MSM8610 msm8610; Max: 1190.4 MHz; Min: 300.0 MHz
Display    800 x 480; DPI: 240; Evaluated Size: 3.9"
Touch screen    Multitouch 2 points
GPU    Adreno (TM) 305; Qualcomm; OpenGL ES-CM 1.1; OpenGL ES 3.0 [email protected] [email protected] LNXBUILD_AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1.04.04.03.048.063+PATCH[ES]_msm8610_LNX.LA.3.5.1_RB1__release_ENGG (CL@)
RAM    425 MB
Flash    4 GB (3.641 GB actual); 32 GB (31.250 GB actual) (see memory map tab)
Communications
Phone    CDMA; Net: EVDO_A
WiFi    wlan; IEEE 802.11 b/g/n; Qualcomm 8610 Snapdragon 200; AP Mode
USB Host    Yes
Bluetooth    Bluetooth 4.0
GPS    Yes
Advanced Features
Front camera    Photo: 1.9 MP; Max: 1600x1200; Video: 0.9 MP; Max: 1280x720; Focus: fixed; No flash
Back camera    No
Sensors    msg22xx-proximity (MStar); range: 0...5; resolution: 5 (100%); power: 0.1mA;
    kxtj9-accel (Kionix); range: 0...19.6; resolution: 0.01 (0.051%); power: 0.2mA;
Vibrator    Yes
Supported languages    166; Afrikaans; Aghem; Akan; Amharic; Arabic; Assamese; Asu; Azerbaijani; Basaa; Belarusian; Bemba; Bena; Bulgarian; Bambara; Bengali; Tibetan; Breton; Bodo; Bosnian; Catalan; Chiga; Cherokee; Czech; Welsh; Danish; Taita; German; Zarma; Duala; Jola-Fonyi; Dzongkha; Embu; Ewe; Greek; English; Esperanto; Spanish; Estonian; Basque; Ewondo; Persian; Fulah; Finnish; Filipino; Faroese; French; Irish; Galician; Swiss German; Gujarati; Gusii; Manx; Hausa; Hawaiian; Hebrew; Hindi; Croatian; Hungarian; Armenian; Indonesian; Igbo; Sichuan Yi; Icelandic; Italian; Japanese; Ngomba; Machame; Georgian; Kabyle; Kamba; Makonde; Kabuverdianu; Koyra Chiini; Kikuyu; Kazakh; Kalaallisut; Kalenjin; Khmer; Kannada; Korean; Konkani; Kashmiri; Shambala; Bafia; Cornish; Langi; Ganda; Lingala; Lao; Lithuanian; Luba-Katanga; Luo; Luyia; Latvian; Masai; Meru; Morisyen; Malagasy; Makhuwa-Meetto; Meta'; Macedonian; Malayalam; Mongolian; Marathi; Malay; Maltese; Mundang; Burmese; Nama; Norwegian; North Ndebele; Nepali; Dutch; Kwasio; Norwegian; Nuer; Nyankole; Oromo; Oriya; Punjabi; Polish; Pashto; Portuguese; Romansh; Rundi; Romanian; Rombo; Russian; Kinyarwanda; Rwa; Samburu; Sangu; Sena; Koyraboro Senni; Sango; Tachelhit; Sinhala; Slovak; Slovenian; Shona; Somali; Albanian; Serbian; Swedish; Swahili; Congo Swahili; Tamil; Telugu; Teso; Thai; Tigrinya; Tongan; Turkish; Tasawaq; Central Atlas Tamazight; Ukrainian; Urdu; Uzbek; Vai; Vietnamese; Vunjo; Soga; Yangben; Yoruba; Chinese; Zulu
Battery    Technology: Li-ion; Voltage: 3653
FM radio    FM Radio[/HIDE]

 

Build.prop
[HIDE]# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KTU84P
ro.build.display.id=N817V1.0.0B04
ro.build.version.incremental=20150821.163315.3491
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=Fri Aug 21 16:34:56 CST 2015
ro.build.date.utc=1440146096
ro.build.type=user
ro.build.user=xuzhenxuan
ro.build.host=ztesuper25
ro.build.tags=release-keys
ro.product.model=N817
ro.product.brand=ZTE
ro.product.name=ZTE_WELLINGTON
ro.product.device=wellington
ro.product.board=wellington
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=ZTE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8610
# ro.build.product is obsolete; use ro.product.device
ro.build.product=wellington
# Do not try to parse ro.build.description or .fingerprint
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
# end build properties
#
# from device/zte/wellington/system.prop
#
#
# system.prop for msm8610
#
# Use reference RIL for initial bringup
#rild.libpath=/system/lib/libreference-ril.so
rild.libpath=/vendor/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
persist.radio.msgtunnel.start=false
persist.radio.atfwd.start=true
# Start in cdma mode
ro.telephony.default_network=4
#
# system props for the cne module
#
persist.cne.feature=1
# Skip /sys/power/wait_for_fb_* nodes and
# force FB to be always on
debug.sf.fb_always_on=1
debug.composition.type=dyn
debug.gralloc.map_fb_memory=0
debug.hwc.dynThreshold=1.5
dalvik.vm.heapsize=36m
dev.pm.dyn_samplingrate=1
ro.hdmi.enable=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
media.aac_51_output_enabled=true
#37491 is decimal sum of supported codecs in AAL
#codecs: AVI AC3 ASF AAC QCP DTS 3G2 MP2TS
mm.enable.qcom_parser=37491
# VIDC: debug_levels
# 1:ERROR 2:HIGH 4:LOW 0:NOlogs 7:AllLogs
vidc.debug.level=1
#
# system props for widevine
#
persist.gralloc.cp.level3=1
#
# system props for the data modules
#
ro.use_data_netmgrd=true
#system props for time-services
persist.timed.enable=true
#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
#
# System props for telephony
# System prop to turn on CdmaLTEPhone always
#telephony.lteOnCdmaDevice=1
# simulate sdcard on /data/media
#
persist.fuse_sdcard=true
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=none
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=true
# Reduce Background apps limit
# System property for cabl
ro.qualcomm.cabl=0
# system prop for NFC DT
ro.nfc.port=I2C
#
#DASH video streaming
#Specify max allowed resolution/bandwidth for representations
#Set allowed avsync window during playback
#
persist.dash.max.rep.resolution=1280*720
persist.dash.max.rep.bandwidth=4000000
persist.dash.avsync.window.msec=100
tunnel.audio.encode = false
#use VERY_HIGH_QUALITY for audio resampler
af.resampler.quality=4
#Buffer size in kbytes for compress offload playback
audio.offload.buffer.size.kb=32
#8x10 does not support tunnel av playback
#this prop should be set to false all the time
av.offload.enable=false
#enable voice path for PCM VoIP by default
use.voice.path.for.pcm.voip=true
#
#System property for FM transmitter
#
ro.fm.transmitter=false
#enable dsp gapless mode by default
audio.offload.gapless.enabled=true
#additional max allowed background services on bootup
persist.added_boot_bgservices=4
#property to force camera shutter sound on speaker
ro.camera.sound.forced=1
# tongcd add
ro.sys.fw.bg_apps_limit=16
ro.config.low_ram=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.camera.tintless=enable
persist.radio.en_wifi_lte=false
ro.com.google.clientidbase=android-zte
ro.com.google.clientidbase.yt=android-sprint-mvno-us
ro.com.google.clientidbase.am=android-sprint-mvno-us
ro.build.baseband_version=N817B01
ro.emode.delete.tests=auxmic,led
persist.radio.use_nv_for_ehrpd=true
ro.emode.flashtest=false
ro.build.pri.version=5
ro.build.sw_internal_version=N817V1.0.0B09
ro.emode.fm=1
ro.emode.keytest=home,back,menu
persist.radio.apm_sim_not_pwdn=0
ro.emmc=1
ro.streaming.ua.prof=http://www.zte.com.cn/mobile/uaprof/N817.xml
ro.com.google.clientidbase.ms=android-sprint-mvno-us
drm.service.enabled=true
persist.radio.mode_pref_nv10=1
persist.radio.apm_mdm_not_pwdn=1
ro.config.suppress_ipv6=false
ro.browser.home.page=http://www.google.com/m?client=ms-hms-sprint-us&channel=portal
ro.cnap.oic=0
ro.cnap.yh=0
ro.cnap.configstatus=-1
ro.setupwizard.launchtype=0
ro.home.operator.carrierid=Chameleon
persist.product.reseller.name=Chameleon
ro.cdma.home.operator.numeric=310000
ro.cdma.home.operator.alpha=Chameleon
ro.config.multimode_cdma=false
persist.carrier.selected_id=SPRINT
persist.carrier.activated_id=SPRINT
persist.sys.usb.sprint=enable
persist.sys.usb.menu=enable
persist.sys.usb.config=mtp
ro.config.alarm_alert=Dawn_of_the_jungle.ogg
ro.config.notification_sound=Crisp.ogg
ro.config.ringtone=Orion.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
persist.sys.logkit.ctrlcode=0
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.vendor.extension_library=/vendor/lib/libqc-opt.so
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.4_r6
ro.com.google.clientidbase.gmm=android-zte
persist.radio.add_power_save=1
ro.telephony.default_network=4
ro.adb.secure=1
persist.sys.ztelog.enable=0
persist.sys.ssr.restart_level=3
persist.radio.adb_log_on=1
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=1
ro.qc.sdk.izat.service_mask=0x1
persist.gps.qc_nlp_in_use=1
persist.loc.nlp_name=com.qualcomm.services.location
ro.gps.agps_provider=1
ro.pip.gated=0[/HIDE]

Memory Map
[HIDE]RAM: 425 MB

System RAM: 136.000MB
System RAM: 273.000MB
System RAM: 16.000MB

Flash: 4 GB (3.641 GB actual)

zram0: 0.063 GB
mmcblk0: 3.641 GB[/HIDE]

 

 

[Guest KonstaT]

12 hours ago, minipower said:

I have a ZTE Quest N817 which has the MSM8610 CPU. I believe these phones have the same MSM8610 CPU and are similar
ZTE Open C / Kis 3 (Beeline Smart2, Moche/MEO Smart A16, ZTE V811W, ZTE V811, Skinny V811, Optus Hop Smart, ZTE Blade M

Do you think it would it be possible for me to use this recovery and rom on the ZTE Quest N817 ¿

I also have the SPC for the phone. All I have been able to do is backup the efs, but was unable to backup some of the folders because they are still locked, even tho I entered the SPC into the box. Does anyone know how to root by using the SPC ¿

The rom is missing the SU binary from the data folder. The phone does not have fastboot enabled. It does have FTM mode and I am also able to get the phone into what I think is called Bootloader mode (Holding volume up/down and power. which turns the phone on with a blank black screen) So I am unable to remount to read write with ADB

I believe the Bootloader is also locked. Is it possible to use the Open C tool to unlock the Bootloader ¿

It's still a completely different device with completely different hardware. Don't expect anything you find here to work on your device and you most definitely shouldn't use Open C Windows flasher.

Never even heard of SPC (Service Programming Code?) before this. Apparently it's some CDMA thing.

Use 'adb reboot bootloader' to boot to bootloader. Make sure you've installed required drivers (or check udev rules on linux) and see if you have fastboot access. Pressing both vol up/down when powering on will likely boot to qdloader (Qualcomm service mode you need with QPST).

It's running an old (and most likely unpatched) Android version. Popular one-click root tools will have no problem with that.

[Guest minipower]

High Konsta T.. Thanks for taking the time to reply. Do you mind if I dig a little deeper in that mind of yours ¿

I was afraid the phones were to different. From reading and tinkering, the phone does not have fastboot or adb in recovery mode. When I type adb reboot bootloader the phone does not go into bootloader but restarts like normal to the home screen.

Maybe its something I'm not doing or doing wrong, but when I hold the vol up/down and power buttons, it does go into qdloader mode but abruptly reboots the phone to the home screen when I plug in the USB or if I have the USB plugged in when I boot into qdloader. I am able to see the device manager load ZTE Diagnostics Interface port DFU drivers for the phone in qdloader mode before the phone reboots. Do you Think if I force install qualcomm HS-USB driver it will stop the phone from rebooting.

 

No luck with any of the one-click tools. I read others have not been able to get any of the one-click tools to complete.

If I understand it right. Since android has ditched Mass Storage and moved to MTP, I would not be able to mount the phones file system with programs like ext2fsd, which would allow me to -force-write to a Read Only Partition.

 

I did download the kernel from opensourcezte and have an VM android build environment. I really do not know how to program anything except for my remote control, microwave and sound system lol.. But I was able to stumble my way through building some custom rom's for my unsupported p4vzw tablet, Thanks to google fu and shear determination.

Would you be able to point me to a layman's write up to build a kernel with an unlocked bootloader ( I believe the bootloader would be built with the kernel -- right? ) If i'm able to do that, I think I should be able to build a custom recovery at the same time. Of course I can only do that after making or editing a device tree. With the phone not rooted I would not be able to use any of the cyanogenmod scripts to pull the files from the phone.. Right?

[Guest KonstaT]

15 hours ago, minipower said:

I was afraid the phones were to different. From reading and tinkering, the phone does not have fastboot or adb in recovery mode. When I type adb reboot bootloader the phone does not go into bootloader but restarts like normal to the home screen.

Fastboot and adb are two completely different things and never work at the same time. Fastboot is a protocol used to communicate with device when booted in bootloader mode. ADB needs device side service running (adbd) and is used when booted in Android/recovery. Stock recoveries never have adb enabled besides for flashing firmware updates (adb sideload).

Some carrier branded ZTE devices are known to be locked down. Locked/crippled bootloader and even system write protection on some devices.

15 hours ago, minipower said:

Maybe its something I'm not doing or doing wrong, but when I hold the vol up/down and power buttons, it does go into qdloader mode but abruptly reboots the phone to the home screen when I plug in the USB or if I have the USB plugged in when I boot into qdloader. I am able to see the device manager load ZTE Diagnostics Interface port DFU drivers for the phone in qdloader mode before the phone reboots. Do you Think if I force install qualcomm HS-USB driver it will stop the phone from rebooting.

Installing USB drivers on your computer won't affect this in any way. On some devices you can power off, press both vol up/down keys, and connect USB cable to boot to qdloader.

15 hours ago, minipower said:

If I understand it right. Since android has ditched Mass Storage and moved to MTP, I would not be able to mount the phones file system with programs like ext2fsd, which would allow me to -force-write to a Read Only Partition.

Never even heard anyone to do anything like that. You've never been able to access Android system partitions whether you were using MTP, PTP, or UMS. initramfs is packed with kernel in boot.img and you can't edit that without unpacking/repacking boot image.

15 hours ago, minipower said:

Would you be able to point me to a layman's write up to build a kernel with an unlocked bootloader ( I believe the bootloader would be built with the kernel -- right? ) If i'm able to do that, I think I should be able to build a custom recovery at the same time. Of course I can only do that after making or editing a device tree. With the phone not rooted I would not be able to use any of the cyanogenmod scripts to pull the files from the phone.. Right?

Bootloader is not built with the kernel. There is no source code available to build one (qcom's lk bootloader is open source but we don't know the modifications vendors make). Flashing a 'bad' bootloader is the surest way to permanently brick a device so people don't usually experiment with things like that. There's no point in building anything if there's no way you can get it flashed/booted on your device.

Edited August 19, 2016 by KonstaT

[Guest minipower]

Thank you for answering those for me.

No luck with the qloader mode. Every time QPST connect's with the phone, it reboots. I see I mixed up bootloader with boot.img.

Using a program like ext2fsd, I hoped it could be mounted like a usb hard drive, no luck tho.

I'll keep trying and will JTAG this thing if I have too. First I'll try building a custom recovery.

I don't want to keep taking thread this off topic. Again thank you for clearing up the questions.

 

Edited August 20, 2016 by minipower
missing t

[Guest cesardp27]

Hello, I have installed on my phone ZTE Open C version 12 CyanogenMod (Lollipop 5.0) and want to install version 11 (Kit Kat 4.4.4) but when I perform wipe data and factory reset and then give it to install the ROM me indicates that he can not install, there is a step I'm missing? and of course the gapps not install them. thanks for your support

[Guest KonstaT]

2 hours ago, cesardp27 said:

Hello, I have installed on my phone ZTE Open C version 12 CyanogenMod (Lollipop 5.0) and want to install version 11 (Kit Kat 4.4.4) but when I perform wipe data and factory reset and then give it to install the ROM me indicates that he can not install, there is a step I'm missing? and of course the gapps not install them. thanks for your support

There's installation instructions in the third post of this thread as always.

What is the error message?

[Guest cesardp27]

Sorry I can't find the third post

[Guest KonstaT]

55 minutes ago, cesardp27 said:

Sorry I can't find the third post

LOL. :D Even every 3-year-old can count to three. There's first post, second post, then *drumroll* third post.

How to install:

1. boot into ClockWorkMod
2. backup and restore -> backup (create a nandroid backup of your current ROM)
3. mounts and storage -> format /system
4. wipe data and factory reset
5. install cm-11-xxxxxxxx-KonstaKANG-kis3.zip
6. install gapps-kk-xxxxxxxx-signed.zip
7. reboot now

Edited August 29, 2016 by KonstaT

[Guest cesardp27]

Many Thanks.... testing

[Guest ToniBl4ck]

Hi, nice rom, but it cannot find my dual-sim card, my device is v811w

[Guest KonstaT]

2 hours ago, ToniBl4ck said:

Hi, nice rom, but it cannot find my dual-sim card, my device is v811w

FAQ, third post of this thread!

[Guest ToniBl4ck]

thanks so much, its work!

[Guest JuniorJPDJ]

Hi, why when i start cm11 it automatically unmounts my sdcard, the same when i click to mount it or put it in, it's being mounted, and then automatically unmounted

[Guest KonstaT]

9 hours ago, JuniorJPDJ said:

Hi, why when i start cm11 it automatically unmounts my sdcard, the same when i click to mount it or put it in, it's being mounted, and then automatically unmounted

Never heard of such issue. Corrupt sdcard?

How about crabbing a logcat so we don't have to guess...

Edited December 17, 2016 by KonstaT

[Guest JuniorJPDJ]

3 hours ago, KonstaT said:

Never heard of such issue. Corrupt sdcard?

How about crabbing a logcat so we don't have guess...

Never mind, actually sdcard died in my eyes...

[Guest JuniorJPDJ]

I want to compile entire ROM, I saw repositories in your first post, what I need to compile, in which order and how to make it flashable zip?

[Guest KonstaT]

14 minutes ago, JuniorJPDJ said:

I want to compile entire ROM, I saw repositories in your first post, what I need to compile, in which order and how to make it flashable zip?

There's a complete 'how to build' guide in the third post of this tread. Build system will spit out a recovery flashable zip.

[Guest JuniorJPDJ]

15 minutes ago, KonstaT said:

There's a complete 'how to build' guide in the third post of this tread. Build system will spit out a recovery flashable zip.

K, I'm a bit blind, sorry.
Actually there was similar "how to build" in device tree at your github, but it looked to me too little complicated, I had to ask...

What I need to change in source to make internal SD mount in /storage/sdcard0 (and ofc external sd as sdcard1)?

I've kis3, not open c

[Guest KonstaT]

15 minutes ago, JuniorJPDJ said:

K, I'm a bit blind, sorry.
Actually there was similar "how to build" in device tree at your github, but it looked to me too little complicated, I had to ask...

What I need to change in source to make internal SD mount in /storage/sdcard0 (and ofc external sd as sdcard1)?

I've kis3, not open c

Revert https://github.com/KonstaT/android_device_zte_kis3/commit/3217d2ba21bd8e0804e9268cb0570aefb86cfe16.

Also see this as reference. https://source.android.com/devices/storage/config-example.html

[Guest JuniorJPDJ]

May I also ask you, which partition exactly am I looking for?
I can't see any not mounted big partition in fdisk -l /dev/block/mmcblk0

Edited December 17, 2016 by JuniorJPDJ

[Guest KonstaT]

25 minutes ago, JuniorJPDJ said:

May I also ask you, which partition exactly am I looking for?
I can't see any not mounted big partition in fdisk -l /dev/block/mmcblk0

Internal sdcard is emulated on /data partition (/data/media) on Kis3 partition layout. Open C partition layout has physical partition.

You also need to create a custom recovery image (CWM or TWRP) that won't wipe your internal sdcard when factory resetting...

Edited December 17, 2016 by KonstaT

[Guest JuniorJPDJ]

Thank you very much for help, own build is working great ;)

EDIT: omg, thats huuge
 

Quote

juniorjpdj@trusty:~$ du -sh cm11-kis
67G    cm11-kis

 

Edited December 18, 2016 by JuniorJPDJ

[Guest KonstaT]

57 minutes ago, JuniorJPDJ said:

Thank you very much for help, own build is working great ;)

EDIT: omg, thats huuge

Well done!

Out directory probably counts almost half of that. When you have Android source x 7 on your HDD you'll need to learn some tricks how to save space (repo/git --reference, removing toolchains and other projects you don't need from the manifest, etc). ;)

Edited December 18, 2016 by KonstaT