[Galaxy S 4 Q&A, Help & Troubleshooting] EliYakov:
URGENT HELP NEEDED

SEE FULL PHONE SPECS AT BOTTOM OF POST, which I have managed to claw together in the last 24 hours ... I am giving you guys as much info as possible, so you know what I have done, tried, what has failed & what has worked; Even if only partially! Rather more info & you guys can skim, versus too little info!

Dearest Distinguished Fellow Geeks, Friends, Developers & GOD's a La Tech!

I'm @ my wits end & bloody terrified right now

(And if you read the background on me below, you will realize that it must take a calamity of EPIC proportions to get me remotely upset & additionally, I have never EVER before been so clueless in terms of something IT related & therefore, this is the first time in my whole life that I am posting to a forum)

- if I'm blatantly honest wif ya all & PRAY someone can help me or guide me 2 help!

I could be a developer myself, as one of my god given talents, happens to be a qualified advanced & senior tech specialist, BUT NOT much of Unix, Linux & I have barely been learning on Android, for the equivalent of a YEAR, as a newish convert from iPhone - That said, I have NOT & WOULD not take a step, without first researching at least half a dozen reported user experiences and/or answered/RESOLVED technical user replies & their explicit advice, followed with my own weighing of the Pro's & Con's FOR ME, based on my personal & business needs (I weigh Pro's & Con's old school style; on a block of A4 Lined Paper & if I establish a RISK @ or OVER 60%, in terms of Android/Linux/Unix, I would NOT change a thing, before making a novice mistake, such as this appears to be!

NO Android expert, but I am equally NOT naive! I only moved to Android from iOS at S3, however, I did manage to Root my current "S4" via code & managed to do it without much difficulty ... The REAL problem began last night, when a new app I downloaded which was meant to show me WHY I was suddenly getting ERROR msg after ERROR msg that I had no more internal space (That I would not get new SMS, that hell was about to freeze over and so on) & that with EVERY APP that can be on an SD card, on mine, and having only the essentials on the Internal, so as to keep the internal components running optimized at all times. I am meticulous about maintenance & permissions repairs.

First, some background about me, to help you understand my level of expertise - My technical field of expertise is a combination of self taught, work/career related trained or post secondary schooling certifications, for example WIN/DOS (Graduate of half a dozen MCSE etc Certifications, with no less than 98% Average) - Thereafter, I naturally gravitated career-wise to the PC-Hardware side - I learned on the fledgling ancestors of todays Internet, before the internet took off (& whilst I am no longer working due to substantial disability, I have managed to keep my IT skills sharp as Needles) first, in my early mid-teens @ Canada's then most technologically advanced Internet Provider, Bell Sympatico, thereafter promoted up technically to Bell Nexxia for Corporate Internet & High Level Resolutions, never before seen at the time, which then lead to me being headhunted & promotion to Global Crossing & being privileged to be a part of IT history, by being a part of their backbone; For those unfamiliar, GC was the BIGGEST & at that time MAIN company responsible for laying the Fibre under the Oceans we use to do EVERYTHING we do today! Later, I worked for Dell & was specially trained & Dell Certifications @ Stage 4 Tech Level (Highest Dell internal "Dell-On-Call" Expert level tech, at the time I was employed there) ... I am a child of the Internet & Computer Age at 34 years of age & my first memories, are not of when I first walked or spoke one of the trilingual languages I was simultaneously raised with, but rather of sitting on my dad's lap, as he feverishly worked on his then, over $50,000 expensive, room sized computing outfit, which kickstarted a lifelong & ongoing fascination with ALL things IT. At home I always had a Mac alongside my PC & became famous for being the first person in the world to program & allow a Mac to dual boot into Windows - A story that was extensively covered by the media at the time, as MS & Apple were NOWHERE near what I had achieved & anticipated the same result "hopefully" within a year. I became one of the main consultants to BOTH to create what became known to the world as "Bootcamp" & was privileged beyond belief to meet my idols, Steve Jobs, Bill Gates, Captain Crunch & Wos! Today, I still have my dual boot MacBookPro sitting next to my PC, despite Windows having ALWAYS run better on Apple's hardware, than ANY competitor PC hardware maker I have EVER tested or used! Hacking software & making it work with hardware outside the concept of their makers, was ALWAYS my biggest ambition; Essentially, discovering how things work and/or don't - Learning by trial & error, if you will & that has always been my motto & thus far, it has only enriched my technical capabilities! ...

... That is; Until last night & today! ...

So I was suddenly forced to select & place my faith with a highly rated App from the Play Store (Unknown APP Developers was NOT yet checked, as mentioned in more detail below) - Sadly, I cannot tell you which APP it was, cause suddenly the action it recommended & took me to a system crash, followed with seemingly endless Bootloop. I essentially can't get past the boot screen UNLESS I do a Reboot Recovery via ADB, with the phone connected to the PC via USB, then a wipe of the Cache & data wipe/factory reset. INTERESTINGLY, I have managed to duplicate this OFTEN, after the restart following successful Cache Wipe & Factory Reset, the phone boots to the SysUI as it did when I unboxed! That is NO PROBLEM! I have duplicated this result so often, because I have naturally tried every other technical option, known to mankind, before my last resort, this POST! INTERESTING as well, PERHAPS, is that I cannot seem to use ANY route, of the MANY, via Volume Up & Down, Home & Power to get to EITHER Recovery OR to Safe Mode! I have ONLY been able to use the buttons within Recovery AFTER a recommended Win App instructed the phone to "Reboot Recovery" - I then get the droid guy with the red exclamation mark & to get to the options, after trying all sorts, I discovered that I had to hit the Power ON/OFF briefly to have the options list show up! - Then with the use of the Volume Down button to Scroll, down, through the options AND Volume UP held longer selects the option highlighted in Recover Mode, leading for example to the Data Wipe/Factory Reset option & the foreign looking (Seeing it for the first time, I thought my phone was fawked for sure if "NO" was appearing in the list of options THAT MANY TIMES) list of "NO" options with a "YES" option & further warning beside it! - I cannot explain to myself WHY the phone will not seemingly go into Recovery manually, with any number of button press options alone & I reckon I have tried every combination of options, I managed to find on the net, YET as soon as the phone is commanded into Reboot Recovery via ADB Win App, the buttons work after the phone gets to the, CLEARLY distraught Droid laying on his side! When I try to boot WITHOUT USB into Recovery it either flashes the display and/or Boot Logo, over & over until I release and/or even makes a clicking or clock tick-like sound, combined with an endless boot logo, until I force a shutdown via EITHER holding the POWER ON/OFF button for about 10 seconds, which leads to the endless Boot Logo OR the combo of Home button & Power ON/OFF, which to the best of my recollection flashes the display ON & OFF, until released, then endless Boot Logo. I had a similar problem with my S3 after it had a fatal drop from my hand, caused by a temporary paralysis of an extremity, which is one of many side effects/symptoms of my Illness/Disability & happens without warning, HOWEVER, in the case of the S3, it would Boot Logo for a bit, then reboot itself & repeat & there was NO WAY to stop it doing that until the battery died, or was physically removed by me. So this time around, I am quite literally delighted that it will AT LEAST go into Recovery via ADB & USB & then the use of the buttons when inside & that it WILL stay powered OFF, unlike my S3 fatality. Just to be clear, my current phone has not even been left to bounce around a protective enclosure within a small pouch, NEVER-MIND a drop!

This APP I downloaded 24 hours ago was "designed" to reveal ALL internal files that IT (The APP) considered to be bloatware and/or obsolete files, clogging the internal side ... It led me straight to one file, which stood out to me, like no other, because I live in Germany & speak German. Here we have a load of so-called APPS named either "Mediatheken" or "Mediathek" or "Mediatheke" & they are VERY popular Digital Options or Features - The variants arise in German, depending on how one is describing it & how many one is speaking of! A "Mediathek" singular, is ONE way of saying, what we refer to as "Media Center" & "Medien" the other way of saying "Media" CANNOT be used in this context, because "Medien" in German is reserved ONLY for describing the traditional "media" or press NOT Media Files etc. Whereas saying "Mediatheken" or "Mediatheke" is the English equivalent of "MEDIA CENTER" with greater than one, in content & IMPLIES a tangible digital file or FILES! To define it is easier! It is nothing more than an APP or APPS, made by individual German TV networks, giving the user the ability to stream any program after it's airing (Similar to Netflix or another provider I use here, called Watchever, which allows the user to download ANYTHING for offline viewing, which is in addition to Music Streaming services which I am a client of & use on my mobile as much as I use them on my traditional computer. Those services, Ampya & Spotify, ALSO allow "offline" downloading of music, which is then logically (Or so I thought anyway) downloaded to the Internal Storage - To make the whole thing even more complex, I unboxed & setup the phone in German first & used my offline Music & offline video Mediatheken WITHOUT an SD Card until I realized, space was becoming a "life or death" situation. That would mean, theoretically, that ANY say series, movie or music I downloaded to the German Language setup phone, stored internally before I got the SD Card & it would be logical, that the created folder for the said media, would be called MEDIA which is Mediatheke in German. I changed the sys language from German to English when I successfully rooted it, well over 2 months ago now & DID NOT/forgot to switch back to German ... So whilst my phone was literally terrorizing me to uninstall ANYTHING on the internal side, via a peppering of errors I couldn't OK fast enough to be able to simultaneously get rid of ANYTHING APP wise, that is unable to be stored on the SD Card. The concept was, get rid of the NON-ESSENTIAL apps stored internally to calm the phone down & then proceed to find a solution to track down, easily, what was causing this sudden space crunch! The irony is; 95% of ALL the apps on my phone, were capable of being run & stored on the SD CARD; Meaning there was clearly more than just 2 or 3 APPS I had to quickly dump, but obviously, in my mind, there had to be STUFF on the internal side, media, that was left undiscovered by me or which were NOT auto synced to DropBox or my Google Drive. As it turned out, initially, I was correct in assuming that there was obviously **** on the internal side, which I had long forgotten about & adding an APP here or there, which HAD TO BE installed & run internally such as, one example, Facebook, plus the forgotten media, had now led to the Space Crunch! I went folder to folder to locate the media I had looked at, was sent or received BEFORE my Micro-SD Card upgrade & uploaded them all to my DropBox & Google Sync, so as to have 2 backups. BUT, even after having deleted a good 100 pictures & audio files, there was still SOMETHING I was clearly missing in terms of space usage, versus the size of the APPS now on the Internal side & their total space. Which is when I began looking for an APP to hunt down bigger files in bulk & in my panic, the app recommended I ditch a file I was named "Mediatheke or Mediatheken" - A file I thought was loaded with crap from all these various "mediathekes" due to its size; That, I thought, not only made perfect sense (after discovering all the other media pre SD Card, forgotten about & causing the Space issues) but HAD TO BE THE "ROOT" - no pun intended - of ALL EVIL! It deleted the file without so much as a warning that said file was being shared by other APPS or systems, NEVER-MIND WARNING ME of what would come next! The phone suddenly crashed & rebooted only to reach the Boot Logo & remain there, illuminating the logo just as it normally would, but without proceeding! Since the first Reboot Recovery, Cache Wipe & Factory Restore & the phone would do EVERYTHING as expected, again & AGAIN, until it finished booting & had loaded the stock SysUI & the pretty diagrams of what each thing does, which was & remains the goal, ONLY, within 10 seconds MAX I get the same Error in Grey "Unfortunately the System UI has" stopped/quit/failed/crashed" - I cannot recall, because of my illness, which if the 4 it said & BEFORE I could even hit OK or do ANYTHING at all, it auto shuts down & returns to the non-stop Boot Logo.

At first I thought I was dealing with a simply/slight corruption or error (Perhaps because of the Cache Wipe) that would surely allow me to proceed someway or another, to resolve the problem & in the course of my following non-stop research to resolve, I deduce that the corruption or error is 100% the ONLY thing causing the SystemUI to fail, thus MUST BE related to the deleted file. I was correct, it would appear! This APP had me delete something big in size, related to the SystemUI, namely Mediatek" - The difference is ONE SINGLE CHARACTER, namely the missing "H" which would have made it "Mediathek" & instead has caused me an unprecedented, epic nightmare, unlike any nightmare I have ever had, seen or heard of in my 3 decades of IT induced life! What followed has had me part terrified to death, part dumbfoundead, part mystified, part livid that such a colossal error or mistake can be allowed to proceed, without even the slightest regard for the integrity of the carefully cared for by myself, Operating System & has now ultimately left me resigned to the gut wrenching feeling of utter helplessness/hopelessness ever since ... The ERROR came in a heartbeat/blink of the eye after the file was deleted, WITHOUT any warning the file MIGHT be essential to or even shared by the system/OS or other applications FORGET a warning that I would be deleting a file that MUST be kept, was recommended to be kept or had to be kept; FULL-STOP! As soon as the error notification pops up, the phone literally reboots itself right back to square one & stays there, until I force a power cut via a long hold of the Power ON/OFF button OR by physically removing the battery, as a NUMBER of threads from you guys have instructed other's to do, in the case of Bootloops. Even more remarkable, is the fact that during the endless Boot Logo, I can attach my phone to my Windows or OSX Mavericks, at ANYTIME, without any difficulty or say lag & command it to Wipe Data or Reboot or Reboot in Recovery & after a clearing of the Cache & a Factory Reset or vice versa, tried in countless different variations & times, the phone DOES reboot & goes back to the factory ROM, YET, as soon as it shows the newly restored UI, the System UI error comes, knocking the phone back to endless Boot Logo. Also interesting; My phone doesn't seem to want to go into Safe Mode either!

To add insult to injury, I realized only in the last 24 hours that my phone is NOT a Samsung S4, rather a S4 clone (Make = Shengda - All retrievable specs I have managed to get, below, since "Shengda" doesn't seem to have it's ROM's available for an emergency, or a decent website either! I am FURIOUS that this phone seemed so good at having convinced me that it was a Samsung S4; Even the various Device ID apps I have had; Perfect example, in order to do the ROOT, the phone was identified as nothing other than a Samsung! ONLY the ADB console on my Win revealed its maker was NOT Samsung at all, but a "China phone") that looks identical to the S5, except with extra's like a Dual SIM, which was the major selling point at the time I bought it! I thought nothing other than it being a modified or supped up Samsung S4, with a S5 size screen, back last November when I bought it & no one knew that it would turn out to look virtually identical to the current S5. It was billed as a Samsung S4 "modified to higher specs & added features" like the battery, apparently the same power of the S5 batteries & 2 of them to boot: Each a much higher mAh than the S4 offered & on par with the soon to be released S5. To be frank, the phone has been a DREAM; Until NOW! I have never had an issue with it! On the contrary, I have continually had better results with IT, than Samsungs new S5 is promising ahead of it's German release next month, to give & NOT to be compared with the S4, the alternative at the time! WHO WOULDN'T HAVE BOUGHT THIS PHONE, is the only question I can pose, even now, still!

I am now at such a stage of despair, that I have long gone into "DO ANYTHING MODE" to bring my beautiful phone back to life! In my desperate search I found a website, NeedRom.com (which has MANY shout out's to XDA btw) & interestingly they have NO MENTION of Shengda BUT when I did a cross search of the EXACT ROM I have, via the Build ID, it returned a ROM from another maker I have NEVER heard of before called "Star"! I don't know a thing about how to get a working/stock ROM or "custom rom" onto the phone, with which I would hope to be able to re-install to a similar functionality that I had before. That is where I place my hope in your wonderful & endless talents! However, in the meantime, judging by the Build ID, being numerically, exactly identical to the one that was originally what I believe is called the "stock ROM" which doesn't want to reset itself to how I got it ... if my guesstimation that the clone maker "Star's" Android Build = identical to the "Shengda" one I started with, that would tell me that it MUST be highly compatible with my phone & hardware, therefore could be the EASY resolve!!!???

What makes me worry is that it REMAINS from a different maker & my lack of knowledge vis-a-vis ROM's and/or how to install/flash a Custom ROM's, plus add to that, without having some APP being placed on a phone, which is not working in that capacity YET, makes me pause, because I simply do NOT want to take a stab in the dark! I am willing to take any ROM that will work, BUT, I am sure you will respect the fact that I want to know exactly what I am to do, step by step, including where to get the necessary tools, the ROM itself & how to apply them all successfully! I know that I can Apply from ADB, or SD Card in the Recovery I can get to via USB, but I'm still confused as to how the rest works & at the least, would need help or a point in the right direction to learn how to do this successfully, no matter the time or resources required! On top of that, I DO have Odin but ZERO knowledge on how it works, which settings I would check/NOT check & what wants to be done to make the "flash" fully successful. I know that I am patient & learn VERY easily, IF I am given the right material guides or help!

Another point of confusion for an Android user of my capability, or lack thereof, is that users, along with developers seem split on whether to use Odin or perhaps Heimdall on OSX, which some say is apparently much superior & less risky (Not that my phone's risk could be any greater right now - In my opinion, my phone might be what is referred to as a "soft brick" based upon my newly attained knowledge of the last 24 hours, or it wouldn't load the OS, Restore to Factory ROM, only to fail because of the System UI!) - On top of that Needrom.com has a totally different method to get the ROM onto the phone, which of course only adds to my confusion; Which is the better or BEST way, for the phone & for me! I downloaded the exact build I spent hours hunting down, unzipped the Flasher Tools, but since the "Instructions to install the ROM" seems to have been written by a non-English speaker, or worse (Translated from some language via Google Translate & copied & pasted) as the "definitive guide" to follow to successfully flash this ROM on my phone; Essentially the instructions are so garbled & unclear to this native English speaker, that I am reluctant/worried to do it to begin with, before I give ya all the chance to help me, perhaps with steps I have missed out or which did not present themselves; My disability unfortunately affects my concentration, so if something is not as CLEAR & straight forward as you guys ARE, then I could cause yet MORE damage than has already been caused! Despite my newfound knowledge that one can apparently "unbrick" - Something that I learned a few short minutes ago & which gives me hope that my case is not as hopeless as it would be, IF I were still an iPhone user!

Guessing, with reference to IT, is FUN as a geek, I'll admit it, shamelessly, but NOT when it's the only phone I have & WILL BE ABLE TO AFFORD FOR A LONG TIME, with no chance of a contract phone or anything of the sort, because I am disabled & therefore also poor! This phone enabled me to monitor my over dozen different medications, medication doses, refill times, reminders ... It enables me to program my WELL above average NEED to see DR after DR, Specialist after Specialist & do so, without great effort, nor worry that my own Neurological Disorder, will cause me to become sicker than I already am! This phone is my medical Bible! Without it; I would be FULLY unable to manage half of what this disability forces me to live with & I PRAY to God that someone may have enough patience, understanding & love, to help me restore what is an indispensable medical asset & my ONLY means of contact with the outside world. That's LIFE, when you get struck down with the worst Pain Condition known to man or DR & my phone has been the lifeline, I cannot live without. The damage caused so far has caused uncontrollable pain attacks & pain no other person can contemplate; Yet I KNOW that the thought alone, that this is unresolvable, would do far worse damage, than anyone can possibly fathom!

So I am praying that you wonderful users & developers will be able to help ... I turned to you FIRST because I marvelled & bow before you, at the success rate of the half a million posts & threads I have read since the meltdown started, before even coming to the detailed conclusion that I am at now, contained herein, all on my own!

Please feel free to email me directly at D.W.Doneit1@Gmail.com

May God Bless & Protect You All,

Sent with LOVE, Kindness & Admiration for you ALL! Heroes & GODS of Technology!

Thank you so very kindly!!!

Eli in Berlin

Manufacturer = Shengda

Model = GT-I9500 and inside behind the battery it says Model I9500 L

Android Version = 4.2.1

(Would LOVE to upgrade to the newest version if I have to start from scratch anyway, again, here I am not fully clear on what is involved)

Rooted - YES

Last Setting for DEV = USB DEBUGGING ACTIVE & allow unknown apps (Normally inactive for security reasons but turned on because I sent Framaroot to the phone before I deleted this "Mediatek" file to verify my Root settings)

Build ID = GT-I9500-20130904-093234

Board ID = K29W

Chipset Platform = MT89_K29W according to SRS ADB Toolbox --- YET ---

the phone specs AND multiple other owners report their/this phone being mt6589 - MORE CONFUSION

Android version	4.2.1; eng.scm.1372296033; SDK17

CPU	4 cores; ARMv7 Processor rev 2 (v7l) MT89_K29W; Max: 1209,0 MHz; Min: 497,2 MHz

GPU	PowerVR SGX 544MP; Imagination Technologies; OpenGL ES-CM 1.1; OpenGL ES 2.0 build 1.9@2204701

Flash	4 GB (3.589 GB actual); 4 GB (3.693 GB actual)

Phone	GSM, Dual SIM; Net: HSPA

WiFi	wlan_mt6628; IEEE 802.11 b/g/n; MediaTek MT6628; AP Mode

USB Host	No

SD Version:	1.1 5

KERNEL: Linux version 3.4.5 (user@linux-user) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jun 27 09:20:03 CST 2013

CODENAME: REL

Mainboard: K29W

BRAND: Samsung

CPU_ABI: armeabi-v7a

CPU_ABI2: armeabi

DEVICE: K29W

DISPLAY: GT-I9500 20130627-092201

FINGERPRINT: Samsung/K29W/K29W:4.2.1/JOP40D/1372296033:user/test-keys

HARDWARE: mt6589

ID: JOP40D

TAGS: test-keys

Processor	: ARMv7 Processor rev 2 (v7l)

processor	: 0

BogoMIPS	: 2439.94

processor	: 1

BogoMIPS	: 2447.96

Features	: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt

CPU implementer	: 0x41

CPU architecture: 7

CPU variant	: 0x0

CPU part	: 0xc07

CPU revision	: 2

Hardware	: MT6589

Revision	: 0000

FINALLY, the Build Properties I got from SpecDevice.com

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=JOP40D

ro.build.display.id=GT-I9500 20130627-092201

ro.build.version.incremental=eng.scm.1372296033

ro.custom.build.version=1372296033

ro.build.version.sdk=17

ro.build.version.codename=REL

ro.build.version.release=4.2.1

ro.build.date=Thu Jun 27 09:22:01 CST 2013

ro.build.date.utc=1372296121

ro.build.type=user

ro.build.user=scm

ro.build.host=vanzo63

ro.build.tags=test-keys

ro.product.model=GT-I9500

ro.product.brand=Samsung

ro.product.name=K29W

ro.product.device=K29W

ro.product.board=K29W

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=SHENGDA

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=MT89_K29W

# ro.build.product is obsolete; use ro.product.device

ro.build.product=K29W

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=K29W-user 4.2.1 JOP40D eng.scm.1372296033 test-keys

ro.build.fingerprint=Samsung/K29W/K29W:4.2.1/JOP40D/1372296033:user/test-keys

ro.build.flavor=mt89_k29w_s8041_shengda_jb2_sw_mul

ro.build.characteristics=default

# end build properties

# begin mediatek build properties

ro.mediatek.version.release=ALPS.JB2.MP.V1.3

ro.mediatek.platform=MT6589

ro.mediatek.chip_ver=S01

ro.mediatek.version.branch=ALPS.JB2.MP

ro.mediatek.version.sdk=1

# end mediatek build properties

#

# system.prop for generic sdk

#

rild.libpath=/system/lib/mtk-ril.so

rild.libargs=-d /dev/ttyC0

# MTK, Infinity, 20090720 {

wifi.interface=wlan0

# MTK, Infinity, 20090720 }

# MTK, mtk03034, 20101210 {

ro.mediatek.wlan.wsc=1

# MTK, mtk03034 20101210}

# MTK, mtk03034, 20110318 {

ro.mediatek.wlan.p2p=1

# MTK, mtk03034 20110318}

# MTK, mtk03034, 20101213 {

mediatek.wlan.ctia=0

# MTK, mtk03034 20101213}

#

wifi.tethering.interface=ap0

#

ro.opengles.version=131072

wifi.direct.interface=p2p0

dalvik.vm.heapgrowthlimit=128m

dalvik.vm.heapsize=256m

# USB MTP WHQL

ro.sys.usb.mtp.whql.enable=0

# Power off opt in IPO

sys.ipo.pwrdncap=2

ro.sys.usb.storage.type=mtp,mass_storage

# USB BICR function

ro.sys.usb.bicr=yes

# USB Charge only function

ro.sys.usb.charging.only=yes

# audio

ro.camera.sound.forced=0

ro.audio.silent=0

ro.zygote.preload.enable=0

#

# ADDITIONAL_BUILD_PROPERTIES

#

ril.specific.sm_cause=0

gps.solution.combo.chip=1

ril.external.md=0

fmradio.driver.chip=3

ro.sf.hwrotation=0

ril.current.share_modem=2

launcherplus.allappsgrid=2d

launcher2.allappsgrid=3d_20

curlockscreen=1

ro.mediatek.gemini_support=true

persist.radio.fd.counter=15

persist.radio.fd.off.counter=5

persist.radio.fd.r8.counter=15

persist.radio.fd.off.r8.counter=5

persist.mtk.wcn.combo.chipid=-1

drm.service.enabled=true

fmradio.driver.enable=1

ril.first.md=1

ril.flightmode.poweroffMD=1

ril.telephony.mode=1

ril.radiooff.poweroffMD=0

dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt

mediatek.wlan.chip=MT6628

mediatek.wlan.module.postfix=_mt6628

ro.config.notification_sound=OnTheHunt.ogg

ro.config.alarm_alert=Alarm_Classic.ogg

ro.config.ringtone=Backroad.ogg

qemu.hw.mainkeys=1

ro.init.screen_brightness=240

net.bt.name=Android

dalvik.vm.stack-trace-file=/data/anr/traces.txt

# begin adupsfota properties

ro.adups.fota.oem=Vanzo

ro.adups.fota.device=GT-I9500

ro.adups.fota.version=GT-I9500 20130627-092201

# begin adupsfota properties

debug.sf.hw=1

persist.sys.ui.hw=1

windowsmgr.max_events_per_sec=120

wifi.supplicant_scan_interval=300​