Database Info

Generic tablet stuck on boot (Alldaymall tablet)

Hello,
I have a generic chinese tablet running Android 4.1.1, stuck on boot. I can get into recovery mode and I did a factory reset. But it is still stuck. I am not sure what to do at this point. I can't find a factory image so I can push it using adb.
please help!
AllDayMall adm-tp001
**Edit**
If anybody has the same tablet can you please pull the /system folder and post it for me. Thanks in advance!
I narrowed it down I was able to get the build.prop from the device using adb. Now I am looking for the original build so I can push it back on the device
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=sun5i
ro.revision=41275
ro.factorytest=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=JRO03C
ro.build.display.id=nuclear_evb-eng 4.1.1 JRO03C 20130628 test-keys
ro.build.version.incremental=20130628
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Jun 28 17:10:22 CST 2013
ro.build.date.utc=1372410622
ro.build.type=eng
ro.build.user=android6
ro.build.host=Linux2
ro.build.tags=test-keys
ro.product.model=SoftwinerEvb
ro.product.brand=softwinners
ro.product.name=nuclear_evb
ro.product.device=nuclear-evb
ro.product.board=nuclear
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exDroid
ro.build.product=nuclear-evb
ro.build.description=nuclear_evb-eng 4.1.1 JRO03C 20130628 test-keys
ro.build.fingerprint=softwinners/nuclear_evb/nuclear- evb:4.1.1/JRO03C/20130628:eng/test-keys
ro.build.characteristics=tablet
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapsize=48m
ro.kernel.android.checkjni=0
persist.sys.timezone=Europe/London
persist.sys.language=en
persist.sys.country=US
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
debug.egl.hw=1
ro.opengles.version=131072
rild.libargs=-d/dev/ttyUSB2
rild.libpath=/system/lib/libsoftwinner-ril.so
keyguard.no_require_sim=true
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
persist.service.adb.enable=0
hwui.render_dirty_regions=false
ro.property.tabletUI=true
ro.property.copySystem=false
ro.udisk.lable=NUCLEAR
ro.product.firmware=v0.4rc3
eken.board.platform=exDroid
eken.hardware=sun5i
eken.hardware.screen.size=7
eken.hardware.screen.res=800x480
eken.build.version.release=4.1.1
eken.build.version.sdk=16
eken.product.model=A73
eken.product.device=nuclear-evb
eken.product.name=nuclear_evb
eken.product.manufacturer=eken
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
init.svc.adbd=running
Click to expand...
Click to collapse

laithabbas0 said:
Hello,
I have a generic chinese tablet running Android 4.1.1, stuck on boot. I can get into recovery mode and I did a factory reset. But it is still stuck. I am not sure what to do at this point. I can't find a factory image so I can push it using adb.
please help!
AllDayMall adm-tp001
**Edit**
If anybody has the same tablet can you please pull the /system folder and post it for me. Thanks in advance!
I narrowed it down I was able to get the build.prop from the device using adb. Now I am looking for the original build so I can push it back on the device
Click to expand...
Click to collapse
I have the 4.0 ICS version... Not sure if that will help. Let me know.

I have the same tablet, it boots fine, but has a big red DEMO on it so I decided to flash it, the firmware is nuclear_evb-eng 4.1.1 JRO03C 20130628 test-keys (you can check that on your Android's System Info screen).
I'll try to flash it and if I succeed, I'll report back or open a new thread with instructions for doing so because I think I was very lucky to find a stock ROM for this one and would like to share my goods with this great board.
Sorry to bump this as well, it may help someone.

Did you try to install fresh rom?

[ROM][RECOVERY] Star/Alps U9501 Both MTK6589 and MTK6582

STAR / ALPS U9501 Both MTK6589 and MTK6582
WARNING: Please make sure your phone is the exact same model & specification before flashing anything to your phone. Just because it looks the same does not mean it is the same phone. There are many many phones of this type with different hardware such as camera's, screen's & different RAM sizes and ROM sizes of which many are faked!! If in doubt do not flash anything.
YOU HAVE BEEN WARNED​​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

First things first Read this entire post before you do anything!!
Backup Backup!​
I cannot stress enough the importance of getting a full backup of your phone's stock ROM before you begin flashing tweaking or anything else Generally there is no, zero, none, manufacturer support for these devices so unless the seller made a full backup of your device you are screwed if something goes wrong :crying: SO getting a backup should be your very first step.
As said earlier there are many many variations of this phone I am sure with all kind's of different hardware configurations such as CPU, RAM, ROM, CAMERA and SCREENS so it's important to get your phones factory ROM Backed Up the most important things are the uboot.img boot.img it's also a good idea to have a stock recovery.img :good: The uboot and boot.img are what contains your phones specific hardware configuration such as the list above so providing you maintain your stock uboot and boot.img you will always be able to get these things working correctly. :highfive:
Caution: Not all is as it may seem I purchased two phones from different sellers on ebay both phones claimed to be the exact same specification MTK6589 1GB RAM 8GB ROM 720 x1280 screen res.
When the phones arrived they looked identical and I was very impressed with the general quality and the quick, smooth & responsive ROM.
So I set about getting them both rooted.
MTK Droid tools reported one phone as MTK6582 so after backing up and rooting I looked through the rom and found a script called "agold_cheat_evaluating_software.xml" This script fools all benchmark testing softwares into reporting any MTK6582 and even an MTK6572 device to be reported as an MTK6589 with a CPU frequency of 1.2ghz the rom also affects mobileuncle. This just demonstrates that you must proceed with caution
I was in middle of writing a tut to show Noob's how to best achieve a full backup when I came across this most excellent Tutorial by @rnovino on pinoyscreencast.net. :highfive: http://pinoyscreencast.net/get-stock-rom-romdump-mediatek-mt6582-via-mtk-droid-root-tools/
Please follow his instructions according to your true CPU type the MTK6589 is in the video and some extra steps are required for the MTK6582 version which he explains in post :victory: I thank him for saving me so much time and effort :laugh:
He has also linked and listed the tools and drivers required
MTK Droid tools will show the true CPU you have in your phone so a massive thanks to @Rula1 for his awesome work on this tool Please hit his thanks button. Here
Posting on this thread:​
Please do not QUOTE large posts in full :crying: only QUOTE the relevant part and delete the rest. Use The Hide button when posting large amounts Code or text if someone has requested it. As one guy said on xda after someone quoted a large TUT “Dude you owe me a new mouse wheel” LOL
Thanks:​
Use the Thanks button if someone has helped you. :highfive:
Manners:​
Being British most of us are polite and I expect you to be too. My Mother always said “son remember manners cost nothing but they will get you a long way in life”. :angel:
Helping yourselves:​
Please try to help yourself as much as you can. Google Search is your Best Friend so please use it in the first instance. :highfive: I will do my best to help where I can but I am no top developer so try not to get too techy on me. I will try to explain things in plain English for the less experienced and experienced to understand.

TWRP V2.5.0 Recovery for MTK6589​
Well I finally managed to manually port TWRP to our phone :victory:
The main problem was a standard port of TWRP would always exceed the recovery partition size no matter how I tried. The kernel of our phone is rather large at 4.2mb and this combined with the TWRP files would always come out too large. :crying:
I was about to give up on ever having TWRP again when I spotted this recompiled version of TWRP on the lenovo ru forum. Here So thanks and credit to the guy who recompiled TWRP to give me those few extra mb's to allow me to squeeze TWRP on to our phone. :highfive: I still had to edit a few images but it now works. :victory: :victory: :victory:
IMPORTANT:​
Before you flash this double check the file size against your stock recovery.img or recovery partition size. Highlight recovery/right click/properties/details and check the actual size's
If the twrp recovery is larger than the "stock" recovery.img or recovery partition it will kill your sim slots They will not be displayed or detected!! If it's smaller then your good to go
There is also included in the download MY factory recovery CWM recovery build.prop file and two boot.img's one factory one patched for root
You are responsible for flashing so you do so at your own risk and I will not be responsible for any damage or bricks.​
Download HERE​
TWRP V2.5.0 Recovery for MTK6582​
Well I finally managed to manually port TWRP to our phone :victory:
The main problem was a standard port of TWRP would always exceed the recovery partition size no matter how I tried. The kernel of our phone is rather large at 4.2mb and this combined with the TWRP files would always come out too large. :crying:
I was about to give up on ever having TWRP again when I spotted this recompiled version of TWRP on the lenovo ru forum. Here So thanks and credit to the guy who recompiled TWRP to give me those few extra mb's to allow me to squeeze TWRP on to our phone. :highfive: I still had to edit a few images but it now works. :victory: :victory: :victory:
IMPORTANT:​
Before you flash this double check the file size against your stock recovery.img or recovery partition size. Highlight recovery/right click/properties/details and check the actual size's
If the twrp recovery is larger than the "stock" recovery.img or recovery partition it will kill your sim slots They will not be displayed or detected!! If it's smaller then your good to go
There is also included in the download MY factory recovery CWM recovery build.prop file and two boot.img's one factory one patched for root
You are responsible for flashing so you do so at your own risk and I will not be responsible for any damage or bricks.​
Download: HERE​
Stock Firmware (Roms)​
MTK6582 Version
Restore files only SpFlashtool required.
Download Here
MTK6589 Version
MTK6589: SP Flash tool Required Phone.info Here
Code:
Hardware : MT6589
Model : 06v20_v89_gq3009hd
Build number : 06v20_v89_gq3009hd_20131024
Build date UTC : 20131023-220102
Android v : 4.2.2
Baseband v: MOLY.WR8.W1248.MD.WG.MP.V6.P9, 2013/07/09 20:18
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Thu Oct 24 05:57:20 CST 2013
Uboot build v : ----- should be root shell
LCD Driver IC : 1-LT050ANKP029A
installed .apk (APP) List​
Code:
C:\Users\Dell\Desktop\MtkDroidTools>adb shell pm list packages
package:Agold.com
package:agold.weatherwidget
package:android
package:com.agold.AgoldFactoryTest
package:com.agold.launcher.wallpaper
package:com.agold.launcher.wallpaperlock
package:com.androguide.ryuinferno.universal.init.d.support
package:com.android.SuspendWindow
package:com.android.backupconfirm
package:com.android.browser
package:com.android.calculator2
package:com.android.calendar
package:com.android.cellbroadcastreceiver
package:com.android.certinstaller
package:com.android.contacts
package:com.android.defcontainer
package:com.android.deskclock
package:com.android.dreams.basic
package:com.android.dreams.phototable
package:com.android.email
package:com.android.exchange
package:com.android.facelock
package:com.android.flashlightnotification
package:com.android.galaxy4
package:com.android.gallery3d
package:com.android.htmlviewer
package:com.android.inputmethod.latin
package:com.android.keychain
package:com.android.launcher
package:com.android.location.fused
package:com.android.magicsmoke
package:com.android.mms
package:com.android.music
package:com.android.musicfx
package:com.android.musicvis
package:com.android.noisefield
package:com.android.packageinstaller
package:com.android.phasebeam
package:com.android.phone
package:com.android.protips
package:com.android.providers.applications
package:com.android.providers.calendar
package:com.android.providers.contacts
package:com.android.providers.downloads
package:com.android.providers.downloads.ui
package:com.android.providers.drm
package:com.android.providers.media
package:com.android.providers.settings
package:com.android.providers.telephony
package:com.android.providers.userdictionary
package:com.android.provision
package:com.android.settings
package:com.android.sharedstoragebackup
package:com.android.simmelock
package:com.android.soundrecorder
package:com.android.stk
package:com.android.systemui
package:com.android.vending
package:com.android.videoeditor
package:com.android.vpndialogs
package:com.android.wallpaper
package:com.android.wallpaper.holospiral
package:com.android.wallpaper.livepicker
package:com.buak.Link2SD
package:com.dataviz.docstogo
package:com.devices114
package:com.devices118
package:com.estrongs.android.pop
package:com.example.amaboyapp
package:com.gameloft.android.ANMP.GloftDMHM
package:com.google.android.apps.maps
package:com.google.android.apps.uploader
package:com.google.android.backup
package:com.google.android.ears
package:com.google.android.feedback
package:com.google.android.gm
package:com.google.android.gms
package:com.google.android.googlequicksearchbox
package:com.google.android.gsf
package:com.google.android.gsf.login
package:com.google.android.inputmethod.latin
package:com.google.android.inputmethod.latin.dictionarypack
package:com.google.android.location
package:com.google.android.marvin.talkback
package:com.google.android.onetimeinitializer
package:com.google.android.partnersetup
package:com.google.android.syncadapters.bookmarks
package:com.google.android.syncadapters.calendar
package:com.google.android.syncadapters.contacts
package:com.google.android.talk
package:com.google.android.tts
package:com.google.android.voicesearch
package:com.mediatek
package:com.mediatek.CellConnService
package:com.mediatek.DataUsageLockScreenClient
package:com.mediatek.FMRadio
package:com.mediatek.StkSelection
package:com.mediatek.appguide.plugin
package:com.mediatek.appwidget.weather
package:com.mediatek.appwidget.worldclock
package:com.mediatek.apst.target
package:com.mediatek.atci.service
package:com.mediatek.batterywarning
package:com.mediatek.bluetooth
package:com.mediatek.calendarimporter
package:com.mediatek.connectivity
package:com.mediatek.datatransfer
package:com.mediatek.engineermode
package:com.mediatek.filemanager
package:com.mediatek.lbs.em
package:com.mediatek.mtklogger
package:com.mediatek.notebook
package:com.mediatek.omacp
package:com.mediatek.oobe
package:com.mediatek.schpwronoff
package:com.mediatek.smsreg
package:com.mediatek.systemupdate
package:com.mediatek.systemupdate.sysoper
package:com.mediatek.theme.mint
package:com.mediatek.theme.mocha
package:com.mediatek.theme.raspberry
package:com.mediatek.thermalmanager
package:com.mediatek.todos
package:com.mediatek.videofavorites
package:com.mediatek.videoplayer
package:com.mediatek.vlw
package:com.mediatek.voicecommand
package:com.mediatek.voiceunlock
package:com.mediatek.weather
package:com.mediatek.weather3dwidget
package:com.mediatek.ygps
package:com.mobileuncle.toolbox
package:com.projectmkmassags
package:com.svox.pico
package:com.uucun4470.android.cms
package:com.zte.mobile.MushroomDay
package:eu.chainfire.supersu
C:\Users\Dell\Desktop\MtkDroidTools>adb devices
Agold .apk makes lots of system mods so until this is fully investigated proceed with caution!!
The ROM is smooth and stable with everything working on my device as it should. :good:
Power consumption is very good too under normal use :good:
Below is a file called projectConfig.mk which I believe is run at startup but I have not had chance to fully investigate this. Notice all the cheats that can be activated although they seem not be activated in this rom I think "Agold_Empty" THIS IS A LONG LIST so I have had to upload as an attachment PS: The Rom has superuser but will require the patched boot and a patched recovery of your choice to stay rooted which are included in the download.
com.mobileuncle.toolbox should be removed and replaced with the uptodate version on playstore which now supports our phone more fully ​
ConfigProject.mk.txt Download​
Download: HERE
Hints and Tips​
Get Artistic and Make Your Own one of a kind Wallpapers easy noob friendly Here

Hi! I am glad to see this thread!
Just so you know, I found 4 ROMs for that phones on a Rusian forum, and as far as I can see there seems to be two version of that phone...
3 of the ROMs where OEM original ROMs but different releases. The guy who posted those said that only 2 of the three are functionnal on his phone. I tried all ROMs, and in my case, the only one that works is the one that didn't work for him.
My phone is identified as a MTK Model No.: ES-4 (on the back behind the battery). That that mean that it is not a real U9501?

jy_P said:
Just so you know, I found 4 ROMs for that phones on a Rusian forum, and as far as I can see there seems to be two version of that phone...
3 of the ROMs where OEM original ROMs but different releases. The guy who posted those said that only 2 of the three are functionnal on his phone. I tried all ROMs, and in my case, the only one that works is the one that didn't work for him.
My phone is identified as a MTK Model No.: ES-4 (on the back behind the battery). That that mean that it is not a real U9501?
Click to expand...
Click to collapse
Yes I think there could be many many differnt types.
Can you pull the build.prop file from /system of the original stock rom and paste the text as CODE Then HIDE?
This will give us a better idea as to the true model identification :fingers-crossed:
I am going to work now so will take a little time to reply.
This is my build.prop to compare.
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JOP40D
ro.build.display.id=06v20_v89_gq3009hd_20131024
ro.build.version.incremental=eng.root.1382565471
ro.custom.build.version=1382565471
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=2013年 10月 24日 星期四 06:01:02 CST
ro.build.date.utc=1382565662
ro.build.type=user
ro.build.user=root
ro.build.host=bahe3-desktop
ro.build.tags=test-keys
ro.product.model=06v20_v89_gq3009hd
ro.product.brand=alps
ro.product.name=06v20_v89_gq3009hd
ro.product.device=06v20_v89_gq3009hd
ro.product.board=06v20_v89_gq3009hd
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=06v20_v89_gq3009hd
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=e2006v20_v89_gq3009hd-user 4.2.1 JOP40D eng.root.1382565471 test-keys
ro.build.fingerprint=alps/06v20_v89_gq3009hd/06v20_v89_gq3009hd:4.2.1/JOP40D/1382565471:user/test-keys
ro.build.flavor=
persist.sys.timezone=
ro.build.characteristics=default
ro.build.bluetooth.name=
ro.build.wifi.ssid=
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.JB2.MP.V1.2
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.local.all.language=en_US,fr_FR,it_IT,es_ES,de_DE,nl_NL,cs_CZ,pl_PL,ja_JP,zh_TW,zh_CN,ru_RU,ko_KR,nb_NO,es_US,da_DK,el_GR,tr_TR,pt_PT,pt_BR,rm_CH,sv_SE,bg_BG,ca_ES,en_GB,fi_FI,hi_IN,hr_HR,hu_HU,in_ID,iw_IL,lt_LT,lv_LV,ro_RO,sk_SK,sl_SI,sr_RS,uk_UA,vi_VN,tl_PH,ar_EG,fa_IR,th_TH,sw_TZ,ms_MY,af_ZA,zu_ZA,am_ET,km_KH,my_MM,ur_PK,bn_IN
ro.config.notification_sound=Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.ringtone=S_Over_the_horizon.ogg
ro.hnd.analog.audio.max=172
ro.hed.analog.audio.max=148
ro.calll.nor.mic=148
ro.calll.hed.mic=152
ro.idle.nor.mic=192
ro.idle.hed.mic=192
ro.calll.hnd.mic=192
ro.idle.hnd.mic=192
ro.def.bt.in.vol=0x500
ro.def.bt.out.vol=0x2000
ro.def.volume.music=10
ro.def.volume.ring=6
ro.def.volume.voice.calll=6
ro.def.volume.system=6
ro.def.volume.alarm=6
ro.def.volume.notification=6
ro.def.volume.fm=11
ro.def.volume.matv=6
ro.def.volume.dtmf=6
ro.def.volume.system.enforced=6
ro.def.volume.bluetooth.sco=6
ro.def.volume.volume.tts=6
ro.nor.sph.vol=69,81,93,105,114,122,130
ro.hed.sph.vol=76,88,100,112,124,136,148
ro.hnd.sph.vol=79,91,103,115,127,139,155
ro.hed.media.vol=112,136,160,184,208,232,255
ro.hnd.media.vol=104,128,152,176,200,224,248
ro.hnd.tv.vol=112,136,160,184,208,232,255
ro.hed.tv.vol=0,32,64,62,128,160,192
ro.hnd.fm.vol=112,136,160,184,208,232,255
ro.hed.fm.vol=16,80,112,144,176,208,240
ro.nor.key.vol=108,132,156,180,204,228,252
ro.hed.key.vol=108,132,156,180,204,228,252
ro.hnd.key.vol=108,132,156,180,204,228,252
ro.hnd.ring.vol=136,160,184,204,220,236,255
ro.hed.ring.vol=136,160,184,204,220,236,255
ro.def.android.keyboard=en_US
ro.def.android.keyboard1=EMPTY
ro.all.keyboard=en_US,en_GB,ar,bn,cs,de,de_qwerty,es,fr,fr_CA,fr_CH,hi,hu,it,nb,nl,pt,ru,tr,th,el,ur,vi,fa,ms,pt_PT,in_ID,ro,en_PH,iw,pt_BR,zz_qwerty,km_KH,my_MM,fr_qwertz
ro.current.keyboard=en_US,en_GB,ar,cs,de,el,es,fa,fr,fr_CA,hi,hu,it,iw,nl,pt_BR,ro,ru,th,tr,vi,zz_qwerty,bn,en_PH,in_ID,ms,ur,km_KH,my_MM,de_qwerty,fr_qwertz
ro.local.def.language0=EMPTY
ro.local.def.language1=EMPTY
ro.local.def.language2=EMPTY
ro.local.def.language3=EMPTY
ro.def.camera.flash=off
ro.def.camera.zsd=off
ro.def.camera.face=off
ro.def.camera.pic.size.main=4864x2736
ro.def.camera.pic.size.sub=3840x2160
ro.def.camera.exposure.main=0
ro.def.camera.exposure.sub=0
ro.def.camera.antiband.main=auto
ro.def.camera.antiband.sub=50hz
ro.def.camera.bright.main=middle
ro.def.camera.bright.sub=middle
ro.gprs.switch=no
ro.keyboard.vibrate.value=0
ro.build.shutdown.animation=no
ro.build.time.format=12
ro.build.date.format=yyyy-MMM-d-EE
ro.auto.time.update=no
ro.auto.timezone.update=no
ro.build.default.scrbrightness=160
ro.build.max.scrbrightness=255
ro.default.inputmethod=AGOLD_EMPTY
ro.default.gps.switch=null
ro.install.nonmarket.switch=no
ro.gravity.rotation=yes
ro.build.livewp=AGOLD_EMPTY
ro.screenoff.timout=60000
ro.closescreen.timeout=6000
ro.overleap.lockscr=no
ro.build.ipo.setting=yes
ro.alarm.snooze.time=5
ro.alarm.silence.time=5
ro.wifi.notification=no
ro.wifi.sleepmode=0
ro.powerkey.function=0
ro.install.location=2
ro.build.staticwp=com.agold.launcher.wallpaper/wallpaper_default
ro.build.keyboard.touchaudio=yes
ro.build.touch.sound=no
ro.lockscreen.sound=yes
ro.touch.vibrator.feed=yes
ro.build.fontsize=AGOLD_EMPTY
ro.default.fontsize=100
ro.audioprofile.more=no
or.build.vibratorvol=0
or.build.vibratortime=0
or.button.ledvalue=4
ro.browser.homepage=AGOLD_EMPTY
ro.nosignal.hideicons=yes
ro.show.navigationbar=no
or.build.serialname=0123456789ABCDEFG
ro.phone.min.num.match=7
ro.build.autobrightness=no
ro.roaming.reminder=-1
ro.wifimac.tonvram=2
ro.acc.alps.calibration=acc,alps
ro.transition.animation=1
ro.firstboot.date=2013,3,1
ro.enable.internet.call=no
ro.sip.receiver.call=no
ro.default.battery.switch=no
ro.build.audivregain.spk=1285
ro.hallwindow.visible=yes
AP
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse

Hi!
Here is my build.prop
But just so you know, this is not the original one. I flashed my phone already with a few ROMs that I got from that Rusian site. So this ROM is one of the ROM that are supposed to be the stock ROM, but I can tell that the content of the build.prop isn't the same as the original ROM since I don't see the same details in the "About" menu.
I should have made a backup of the original ROM, unfortunately, I didn't. Too late now.
If you want the ROMs let me know, I can send all of them to you.
They are the "stock" version from May, July and September. I also have another ROM that is supposed to be a port of the N9500 which seems to be pretty much the same thing but with different background color in the menus and missing background pictures. So the following build.prop is from that July ROM.
My front camera isn't working, but it never did even with the stock ROM.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JOP40D
ro.build.display.id=06v20_v89_gq3009hd_20130702
ro.build.version.incremental=eng.root.1372750620
ro.custom.build.version=1372750620
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.1
ro.build.date=2013年 07月 02日 星期二 15:39:53 CST
ro.build.date.utc=1372750793
ro.build.type=user
ro.build.user=root
ro.build.host=bahe3-desktop
ro.build.tags=test-keys
ro.product.model=06v20_v89_gq3009hd
ro.product.brand=alps
ro.product.name=06v20_v89_gq3009hd
ro.product.device=06v20_v89_gq3009hd
ro.product.board=06v20_v89_gq3009hd
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=06v20_v89_gq3009hd
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=e2006v20_v89_gq3009hd-user 4.2.1 JOP40D eng.root.1372750620 test-keys
ro.build.fingerprint=alps/06v20_v89_gq3009hd/06v20_v89_gq3009hd:4.2.1/JOP40D/1372750620:user/test-keys
ro.build.flavor=
persist.sys.timezone=
ro.build.characteristics=default
ro.build.bluetooth.name=
ro.build.wifi.ssid=
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.JB2.MP.V1.2
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.local.all.language=en_US,fr_FR,it_IT,es_ES,de_DE,nl_NL,cs_CZ,pl_PL,ja_JP,zh_TW,zh_CN,ru_RU,ko_KR,nb_NO,es_US,da_DK,el_GR,tr_TR,pt_PT,pt_BR,rm_CH,sv_SE,bg_BG,ca_ES,en_GB,fi_FI,hi_IN,hr_HR,hu_HU,in_ID,iw_IL,lt_LT,lv_LV,ro_RO,sk_SK,sl_SI,sr_RS,uk_UA,vi_VN,tl_PH,ar_EG,fa_IR,th_TH,sw_TZ,ms_MY,af_ZA,zu_ZA,am_ET,km_KH,my_MM,ur_PK,bn_IN
ro.config.notification_sound=Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.ringtone=S_Over_the_horizon.ogg
ro.hnd.analog.audio.max=172
ro.hed.analog.audio.max=148
ro.calll.nor.mic=148
ro.calll.hed.mic=152
ro.idle.nor.mic=192
ro.idle.hed.mic=192
ro.calll.hnd.mic=192
ro.idle.hnd.mic=192
ro.def.bt.in.vol=0x500
ro.def.bt.out.vol=0x2000
ro.def.volume.music=10
ro.def.volume.ring=6
ro.def.volume.voice.calll=6
ro.def.volume.system=6
ro.def.volume.alarm=6
ro.def.volume.notification=6
ro.def.volume.fm=11
ro.def.volume.matv=6
ro.def.volume.dtmf=6
ro.def.volume.system.enforced=6
ro.def.volume.bluetooth.sco=6
ro.def.volume.volume.tts=6
ro.nor.sph.vol=69,81,93,105,117,129,140
ro.hed.sph.vol=76,88,100,112,124,136,148
ro.hnd.sph.vol=79,91,103,115,127,139,155
ro.hed.media.vol=112,136,160,184,208,232,255
ro.hnd.media.vol=104,128,152,176,200,224,248
ro.hnd.tv.vol=112,136,160,184,208,232,255
ro.hed.tv.vol=0,32,64,62,128,160,192
ro.hnd.fm.vol=112,136,160,184,208,232,255
ro.hed.fm.vol=16,80,112,144,176,208,240
ro.nor.key.vol=108,132,156,180,204,228,252
ro.hed.key.vol=108,132,156,180,204,228,252
ro.hnd.key.vol=108,132,156,180,204,228,252
ro.hnd.ring.vol=136,160,184,204,220,236,255
ro.hed.ring.vol=136,160,184,204,220,236,255
ro.def.android.keyboard=en_US
ro.def.android.keyboard1=EMPTY
ro.all.keyboard=en_US,en_GB,ar,bn,cs,de,de_qwerty,es,fr,fr_CA,fr_CH,hi,hu,it,nb,nl,pt,ru,tr,th,el,ur,vi,fa,ms,pt_PT,in_ID,ro,en_PH,iw,pt_BR,zz_qwerty,km_KH,my_MM,fr_qwertz
ro.current.keyboard=en_US,en_GB,ar,cs,de,el,es,fa,fr,fr_CA,hi,hu,it,iw,nl,pt_BR,ro,ru,th,tr,vi,zz_qwerty,bn,en_PH,in_ID,ms,ur,km_KH,my_MM,de_qwerty,fr_qwertz
ro.local.def.language0=EMPTY
ro.local.def.language1=EMPTY
ro.local.def.language2=EMPTY
ro.local.def.language3=EMPTY
ro.def.camera.flash=off
ro.def.camera.zsd=off
ro.def.camera.face=off
ro.def.camera.pic.size.main=3264x2448
ro.def.camera.pic.size.sub=2048x1536
ro.def.camera.exposure.main=0
ro.def.camera.exposure.sub=0
ro.def.camera.antiband.main=auto
ro.def.camera.antiband.sub=50hz
ro.def.camera.bright.main=middle
ro.def.camera.bright.sub=middle
ro.gprs.switch=no
ro.keyboard.vibrate.value=0
ro.build.shutdown.animation=no
ro.build.time.format=12
ro.build.date.format=yyyy-MMM-d-EE
ro.auto.time.update=no
ro.auto.timezone.update=no
ro.build.default.scrbrightness=160
ro.build.max.scrbrightness=255
ro.default.inputmethod=AGOLD_EMPTY
ro.default.gps.switch=null
ro.install.nonmarket.switch=no
ro.gravity.rotation=yes
ro.build.livewp=AGOLD_EMPTY
ro.screenoff.timout=60000
ro.closescreen.timeout=6000
ro.overleap.lockscr=no
ro.build.ipo.setting=yes
ro.alarm.snooze.time=5
ro.alarm.silence.time=5
ro.wifi.notification=no
ro.wifi.sleepmode=0
ro.powerkey.function=0
ro.install.location=2
ro.build.staticwp=com.agold.launcher.wallpaper/wallpaper_default
ro.build.keyboard.touchaudio=yes
ro.build.touch.sound=no
ro.lockscreen.sound=yes
ro.touch.vibrator.feed=yes
ro.build.fontsize=AGOLD_EMPTY
ro.default.fontsize=100
ro.audioprofile.more=no
or.build.vibratorvol=0
or.build.vibratortime=0
or.button.ledvalue=4
ro.browser.homepage=AGOLD_EMPTY
ro.nosignal.hideicons=yes
ro.show.navigationbar=no
or.build.serialname=0123456789ABCDEFG
ro.phone.min.num.match=7
ro.build.autobrightness=no
ro.roaming.reminder=-1
ro.wifimac.tonvram=2
ro.acc.alps.calibration=acc,alps
ro.transition.animation=1
ro.firstboot.date=2013,3,1
ro.enable.internet.call=no
ro.sip.receiver.call=no
ro.default.battery.switch=no
ro.build.audivregain.spk=1285
ro.hallwindow.visible=no
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
---------- Post added at 01:17 PM ---------- Previous post was at 01:14 PM ----------
And many thanks in advance for working on this! I have been looking for a ROM for a long time!

jy_P said:
Hi!
Here is my build.prop
But just so you know, this is not the original one. I flashed my phone already with a few ROMs that I got from that Rusian site. So this ROM is one of the ROM that are supposed to be the stock ROM, but I can tell that the content of the build.prop isn't the same as the original ROM since I don't see the same details in the "About" menu.
I should have made a backup of the original ROM, unfortunately, I didn't. Too late now.
[/COLOR]And many thanks in advance for working on this! I have been looking for a ROM for a long time!
Click to expand...
Click to collapse
Hi bro,
Well from the build.prop I would say our phones are the same It's a real shame and brave you didn't get a backup first before you flashed a new rom. ( Not recommended to others :laugh: )
Did you flash the boot.img too or just system ? If you have the stock boot.img there is a build.prop in there too which will show the true id of your phone. :fingers-crossed:
Get @michfood awesome boot & recovery repack utility for windows V2. Here Unpack to desktop. Then copy your boot.img to the folder then drag and drop it on to the MTK unpack.bat It will make a "boot" folder and in there you can find the contents of your boot.img look in rmdisk folder for your build.prop
As you can see from my build.prop my phones build date is October so slightly newer than the one's you have but please feel free to upload them some place to share. Recomend https://mega.co.nz it's FREE :good: plus you get 50gb storage and you dont get loads of popups and false download links also no need for spliting larger files as some of these JB backups can hit 1gb without trying
I will be uploading and posting my stuff tomorrow and some tut's etc etc for the newcomers. So please stay tuned
Thanks for the Thanks btw. Just hit the thanks button if I helped
Regards bigrammy.

I am uploading the ROMs that I have... Do you want the link(s) as PM? It will take about 24h... My upload is slow.
I am not sure if I still have my original boot image. I might have it, but when I tried the MTK_Unpack, it generated a folder with a bunch of files and folder, but there is no build.prop.
I don't have a Linux OS on hand... Do you want my boot.img that might still be the original one?

jy_P said:
I am uploading the ROMs that I have... Do you want the link(s) as PM? It will take about 24h... My upload is slow.
I am not sure if I still have my original boot image. I might have it, but when I tried the MTK_Unpack, it generated a folder with a bunch of files and folder, but there is no build.prop.
I don't have a Linux OS on hand... Do you want my boot.img that might still be the original one?
Click to expand...
Click to collapse
Hi, Sure you can post the ROM links here if you like :good:
Just try include as much info as you can about each of them maybe you could just pull the build.prop for each so people can check it to see if it matches up with there phones.
Also put a disclaimer saying people flash them at there own risk.
As for boot.img well sorry bro my mistake build.prop is in the factory recovery.img which you probably flashed over. I have been porting recoverys to these phones so I was getting confused as I have unpacked and repacked so many latley Same method applies If you still have the recovery.img. Most I have looked at have a build.prop of some descriptiton some are short version and some are full lengthen.
I use windows too so nothing I do will be in linux.
:cool

USE AT YOUR OWN RISK!
There are risks when flashing devices. If any one of those ROMs isn’t working, just try flashing another one… I am not responsible if you take the risk and break your phone. But note that I flashed them all and my phone is still working
You will find 4 ROMs there https://mega.co.nz/#F!opQn2ARB!YRwITQGXB-EmlVX4KBDqfA
I found all these ROMs as is on the web.
The next 3 comes from a Russian Forums and they are identified as stock ROMs (different releases May, July and September).
The guy that posted those said only the July didn’t work for him. In my case, only the July works. Flash with SP Flash Tool.
06v20_v89_gq3009hd_130529
06v20_v89_gq3009hd_130702
06v20_v89_gq3009hd_130907
This one was identified as a port from the N9500. I tried it, it worked on my phone but other than menu back ground color, it seems to see the same ROM at the user stand point. I have some minor issues with all the ROMs I tried and they are the same on every ROMs (occasional problem connecting Skype, google play that won’t update after some time). This one is a CWR backup. So you need to restore it from CWR and do a Factory reset.
StarU9501FromN9500Original
THOSE ROMs ARE ALL HAVING CHINESSE BLOATWARE, clean it after flashing using MTKDroidTools V2.51
Final note, I don’t see why anyone would need any of these ROMs. The two that I tried aren’t perfect. But if you really need a ROM, this is better than nothing I guess. Make a backup of your phone first with MTKDroidTools (I should have too). We rather need a better ROM. I hope we’ll get one.
If you need to ROOT your original ROM or any of these ones, I did it using UnLockRoot (but I had to run it a few times and skip the reboot step at some point… No more details, good luck). You can install CWR on the original ROM or any of these ones using MTKDroidTools.
Again, I am not responsible if something goes wrong. You do it at your own risks.
If you have question regarding MTKDroidTools, SP Flash Tool or UnLockRoot, ask Google. I found it all, you should be able too! 
bigrammy: You will also find there a boot image that could be either the same as the N9500 port or the original one that I had on my phone… I don’t know anymore but it seems to be the one from the N9500 ported ROM.
Click on thanks if that helps!

jy_P said:
Click on thanks if that helps!
Click to expand...
Click to collapse
Thanks for the time and effort in making this post bro :highfive:

Can you post your ROM too since it is more recent than mine?
Thanks!

jy_P said:
Can you post your ROM too since it is more recent than mine?
Thanks!
Click to expand...
Click to collapse
Added to post #3 Here as requested.

Any bloat were? Rooted? Known bugs? Any plans for alternative or custom Rom?
Envoyé de mon 06v20_v89_gq3009hd en utilisant Tapatalk
---------- Post added at 11:23 PM ---------- Previous post was at 11:07 PM ----------
... And thank you too!
Envoyé de mon 06v20_v89_gq3009hd en utilisant Tapatalk

jy_P said:
Any bloat were? Rooted? Known bugs? Any plans for alternative or custom Rom?
Envoyé de mon 06v20_v89_gq3009hd en utilisant Tapatalk
---------- Post added at 11:23 PM ---------- Previous post was at 11:07 PM ----------
... And thank you too!
Envoyé de mon 06v20_v89_gq3009hd en utilisant Tapatalk
Click to expand...
Click to collapse
Post updated with as much info as I have :silly: Rom has superuser but will require patched boot and patched recovery of your choice to stay rooted all included.
com.mobileuncle.toolbox should be removed and replaced with the uptodate version on playstore

bigrammy said:
Post updated with as much info as I have :silly: Rom has superuser but will require patched boot and patched recovery of your choice to stay rooted all included.
com.mobileuncle.toolbox should be removed and replaced with the uptodate version on playstore
Click to expand...
Click to collapse
Thanks
So we can flash it directly with the patched boot and recovery right?
What is the Phone.info? Who does SP Flash tool needs it?

...I couldn't wait so I tried it. It doesn't work. As for May, and September ROMs, I only get a black screens with some strange faded vertical lines. So I restored my previous backup (July ROM).

jy_P said:
...I couldn't wait so I tried it. It doesn't work. As for May, and September ROMs, I only get a black screens with some strange faded vertical lines. So I restored my previous backup (July ROM).
Click to expand...
Click to collapse
Hi,
What doesn't work the rom or the flash via flash tool
phone.info is just for information you need Notepad++ to read it.
Try Flash the rom with the patched boot.img and the system.img only. :fingers-crossed:
After the flash boot to recovery first volume + power and do a full wipe data cache dalvik cache then boot to system

bigrammy said:
Hi,
What doesn't work the rom or the flash via flash tool
phone.info is just for information you need Notepad++ to read it.
Try Flash the rom with the patched boot.img and the system.img only. :fingers-crossed:
After the flash boot to recovery first volume + power and do a full wipe data cache dalvik cache then boot to system
Click to expand...
Click to collapse
The flashing worked. The phone display doesn't work after reboot. I can't even go into recovery.
I tried flashing only the SYSTEM and the BOOT as you asked me, and ...it WORKED!!! :good:
I beleive that all the ROMs I had weir 4.2.1. I am finally having a 4.2.2!
THANKS!
My front camera is still not working though, but that might be an hardware problem with my phone.

jy_P said:
The flashing worked. The phone display doesn't work after reboot. I can't even go into recovery.
I tried flashing only the SYSTEM and the BOOT as you asked me, and ...it WORKED!!! :good:
THANKS!
My front camera is still not working though, but that might be an hardware problem with my phone.
Click to expand...
Click to collapse
:highfive:

[DUMP][4.4.2] - I535VRUDNE1-Dump / Dev Discussion ONLY!

First of all if you are NOT a developer please do not post in this thread. This will be the one and only time I am stringent in my request. If you want to thank me or anyone who works on this project then just hit the Thanks button.
Also, Developer is just a title given by XDA. There are many developers out there without the XDA anointed title. If you are one then please feel fee to join the discussion if can contribute anything of value!
Here is how I got this dump...
I built an unmodified Stock NC1 ROM from Odin TAR. I then applied patch from hre: [Update Zip] Kitkat 4.4 update.
I removed all the SBL's and the aboot from the patch as well as neutered the stock recovery image so they would not flash to the device
Dump will not boot. We (Beanstown106, Open1Your1Eyes1, Invlisiblek) think it may be firmware / kernel related as I tried on a MF1 based device with unlocked bootloader.
Here is the Build.Prop pulled while in reccovery
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=KOT49H.I535VRUDNE1
ro.build.version.incremental=I535VRUDNE1
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Tue May 20 00:16:48 KST 2014
ro.build.date.utc=1400512608
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWDD5809
ro.build.tags=release-keys
ro.product.model=SCH-I535
ro.product.brand=Verizon
ro.product.name=d2vzw
ro.product.device=d2vzw
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=d2vzw
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=d2vzw-user 4.4.2 KOT49H I535VRUDNE1 release-keys
ro.build.fingerprint=Verizon/d2vzw/d2vzw:4.4.2/KOT49H/I535VRUDNE1:user/release-keys
ro.build.characteristics=verizon
# Samsung Specific Properties
ro.build.PDA=I535VRUDNE1
ro.build.hidden_ver=I535VRUDNE1
ro.build.changelist=1542239
ro.product_ship=true
ro.chipname=MSM8960
persist.sys.storage_preload=1
ro.build.knox.container=
# end build properties
#
# from device/samsung/d2vzw/system.prop
#
#
# system.prop for surf
#
# Evolution RIL (8xxx)
rild.libpath=/system/lib/libsec-ril.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
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
persist.hwc.mdpcomp.enable=true
debug.compbypass.enable=1
debug.hwui.render_dirty_regions=true
dalvik.vm.heapsize=36m
debug.enable.wl_log=1
debug.mdpcomp.maxlayer=3
#
# system props for the cne module
#
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.feature=0
#
# System prop for Tvout/HDMI
#
persist.sys.camera.connect=0
persist.sys.videomode=0
ro.hdmi.enable=true
lpa.decode=true
lpa.use-stagefright=true
audio.offload.disable=1
#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
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
#
# system props for call volume steps
#
ro.config.vc_call_vol_steps=7
# System prop to select audio resampler quality
af.resampler.quality=255
# System prop to select MPQAudioPlayer by default on mpq8064
mpq.audio.decode=true
#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
#
# system property for Bluetooth Handsfree Profile version
#
ro.bluetooth.hfp.ver=1.6
#
#system prop for Bluetooth hci transport
ro.qualcomm.bt.hci_transport=smd
#
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0
#system prop for switching gps driver to qmi
persist.gps.qmienabled=true
# System property for cabl
ro.qualcomm.cabl=1
#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true
#
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.hwui.text_cache_width=2048
#
# Supports warmboot capabilities
#
ro.warmboot.capability=1
ro.sf.lcd_density=320
# System property for Default touch key light duration - commented out since default is 1500
#ro.button_key_light=6000
# System property for HDMI/WFD
persist.sys.camera.connect=0
persist.sys.camera.transform=0
persist.sys.videomode=0
# Use CDMALTE Phone
telephony.lteOnCdmaDevice=1
# Enable time services daemon
persist.timed.enable=true
# Keep SIM state on LPM mode
persist.radio.apm_sim_not_pwdn=1
# Don't wait the card state for RADIO POWER request
persist.radio.no_wait_for_card=1
# For sys info indication
persist.radio.add_power_save=1
# Snapshot Setting
persist.radio.snapshot_enabled=1
persist.radio.snapshot_timer=22
# Control EONS (true = EONS enabled, false = EONS disabled)
persist.eons.enabled=false
# Data modules
ro.use_data_netmgrd=false
# Use CP SE13 Table
persist.radio.use_se_table_only=1
# Default ECCList
ro.ril.ecclist=911,#911,*911
# Support Global Mode (Global Mode project)
ro.config.multimode_cdma=1
ro.telephony.default_network=10
# Restore delay of the default network - 30 mins (VZW)
android.telephony.apn-restore=1800000
# Restore delay of VZW Apps APN - 1 min (VZW)
vzw.telephony.appsapn-restore=60000
# Use data service state for signal display (Except SPR / USC / BST / VMU / CRI CS devices. PS ONLY devices use this property)
ro.config.combined_signal=true
# Retry Timer (VZW)
ro.gsm.data_retry_config=max_retries=infinite,5000,5000,60000,120000,480000,900000
# system property for vmware hypervisor running
vmware.hypervisor.running=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.vendor.extension_library=/vendor/lib/libqc-opt.so
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=1m
dalvik.vm.heapmaxfree=4m
ro.build.scafe=americano
ro.build.scafe.syrup=sugar
ro.build.scafe.size=short
ro.hdcp2.rx=tz
ro.sec.fle.encryption=true
ro.secwvk=144
ro.securestorage.knox=true
ro.monkey=0
ro.config.ringtone=Verizon_Airwaves_1.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Over_the_horizon_Acoustic.ogg
ro.error.receiver.default=com.samsung.receiver.error
ro.setupwizard.mode=OPTIONAL
ro.com.google.apphider=off
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.yt=android-verizon
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=4.4.2_r2
ro.HorizontalVVM=true
persist.sys.dalvik.vm.lib=libdvm.so
ro.kernel.qemu=0
ro.build.selinux=1
ro.config.knox=v30
ro.config.tima=1
ro.config.timaversion=2.0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=0
ro.qc.sdk.izat.service_mask=0x0
persist.gps.qc_nlp_in_use=1
ro.gps.agps_provider=1
You can download the dump (/system and boot.img) from HERE: http://goo.im/devs/scrosler/vzw-sgs3//I535VRUDNE1-Dump.7z
If you can help figure out the non boot then great! Join in.
Once again this is for people that want to contribute to the development of 4.4.2 on UNLOCKED devices.
Please no Thank you Posts, no ETA Posts, etc....
I just want to get this ***** running!
-Scott

Here are my findings thus far (not encouraging)
1. With stock Kernel it just flashes Samsung image then goes totally black.
2. With a ML1 Compiled Kernel it flashes Samsung image then goes to the SGS3 logo and goes no further.
3. Tried a Sprint Kernel and results were same as data point 1.

I wouldn't dare flash the SBL chain, but I can't help but wonder if the RPM/TZ partitions are safe or even work. Wasn't there a case a few months ago where updating firmware was being enforced for newer d2vzw/d2lte builds since things were unstable otherwise?
Btw, GPL request for I535VRUDNE1/I535OYUDNE1 kernel and wifi source submitted. I don't expect it to help much if Sprint isn't booting, but somebody needs to keep Samsung compliant.
They always forget with Verizon. Quite stunning given how quickly they upload Sprint source, usually before OTA.

Have you talked to cnexus? I remember on the sprint side with the nd8 update there were issues regarding the firmware. Users there had to jump through hoops to update firmware before flashing any custom nd8 roms...
Sent from my SCH-I535 using xda premium

Macrodroid said:
Have you talked to cnexus? I remember on the sprint side with the nd8 update there were issues regarding the firmware. Users there had to jump through hoops to update firmware before flashing any custom nd8 roms...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
agree with you Macrodroid, early I got an idea to replace the ramdisk of stock 4.3 with 4.4.2(sprint) and 4.1(verizon) ramdisk by modify safestrap!
ended with no boot stuck on black screen, updated to 4.4.2 and sprint 4.4.2 booted in safestrap slot.
I think the old bootchain not compatable with kitkat.
will test the dumb later, @scrosler you can test the sprint ND8 rom it booted with safestrap.
screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

We don't want to use SafeStrap even if unlocked devices can make use of it. Besides, you already have the latest firmware and bootloaders.
If we can manage it, we'd like a native boot with an unlocked bootchain.

I found the USC KitKat D3 Kernel source. Going to try that!

That did nothing.
They need to release the source code, plain and simple. That will be a tremendous help

LLStarks said:
We don't want to use SafeStrap even if unlocked devices can make use of it. Besides, you already have the latest firmware and bootloaders.
If we can manage it, we'd like a native boot with an unlocked bootchain.
Click to expand...
Click to collapse
Yes but you need bootable rom on locked device to make sure your tests not gone with the winds.

mohammad.afaneh said:
Yes but you need bootable rom on locked device to make sure your tests not gone with the winds.
Click to expand...
Click to collapse
I know this will worked on locked devices. The goal is to get it to work on Unlocked devices.
If updated to a locked device I could have a ROM out in 15 minutes. I like the challenge of the unlocked device.

Moved to Android Development.
Have you tried either of these combinations?
1) 4.3 source kernel (with source built DTB) and 4.4 ramdisk?
2) Extracted zImage with 4.3 ramdisk?
You might be able to generate new dtb using Sprint or USCC kk source.
Any access into adb, even if you move it up in init?

garwynn said:
Moved to Android Development.
Have you tried either of these combinations?
1) 4.3 source kernel (with source built DTB) and 4.4 ramdisk?
2) Extracted zImage with 4.3 ramdisk?
You might be able to generate new dtb using Sprint or USCC kk source.
Any access into adb, even if you move it up in init?
Click to expand...
Click to collapse
Hmmm... Number 2 seems like a good idea!
Gonna give that a spin tonight.

scrosler said:
That did nothing.
They need to release the source code, plain and simple. That will be a tremendous help
Click to expand...
Click to collapse
try this out https://www.dropbox.com/s/e8jilbv0ii9ngb3/d2-3.4.zip
its not flashable but throw it in any kernel
I found the vzw flags in the sprint kernel drop, so I chopped up a m2_vzw defconfig and compiled a vzw kernel from sprint source
edit - If somebody that is stock rooted on 4.4.2 can pull config.gz from /proc we can get the official m2_vzw config from there which would allow us to compile that with sprint source (which is the same as vzw, but if there is a more up to date like maybe USC, we can use it)

zachf714 said:
try this out https://www.dropbox.com/s/e8jilbv0ii9ngb3/d2-3.4.zip
its not flashable but throw it in any kernel
I found the vzw flags in the sprint kernel drop, so I chopped up a m2_vzw defconfig and compiled a vzw kernel from sprint source
edit - If somebody that is stock rooted on 4.4.2 can pull config.gz from /proc we can get the official m2_vzw config from there which would allow us to compile that with sprint source (which is the same as vzw, but if there is a more up to date like maybe USC, we can use it)
Click to expand...
Click to collapse
I'll try that tonight as well but I do believe you can not longer get config.gz from /rpoc. I thought that changed on later Android 4.3+ builds. Certainly could be wrong on that.

scrosler said:
I'll try that tonight as well but I do believe you can not longer get config.gz from /rpoc. I thought that changed on later Android 4.3+ builds. Certainly could be wrong on that.
Click to expand...
Click to collapse
OK cool, I know I can still pull it on my phone on AOKP 4.4.4 but touchwiz could be a completely different beast being that AOSP based code is more open security wise

zachf714 said:
OK cool, I know I can still pull it on my phone on AOKP 4.4.4 but touchwiz could be a completely different beast being that AOSP based code is more open security wise
Click to expand...
Click to collapse
Yeah, On pure AOSP or Nexus devices its done differently...
Here is one example: http://forum.xda-developers.com/showpost.php?p=43930020&postcount=46
I will still try to poke around. If I can at least get ADB its a start!

scrosler said:
Yeah, On pure AOSP or Nexus devices its done differently...
Here is one example: http://forum.xda-developers.com/showpost.php?p=43930020&postcount=46
I will still try to poke around. If I can at least get ADB its a start!
Click to expand...
Click to collapse
Im going to see what I can do with the kernel, nate told me he saw a Cert.pem file in the ramdisk which is different from 4.3 but that could just have do with 3.4.x kernel base. It is redicilous that we are almost a week in and Samsung has yet to meet GPL compliance

I found where the certificate is being loaded in init

zachf714 said:
I found where the certificate is being loaded in init
Click to expand...
Click to collapse
Interesting. I would then have to assume the certs have changed? And the theory of using old ram disk may possibly be affective because its looking for old certs and not new? Or maybe just try swapping init binary?
I was also wondering if grabbing the newest hlos-bin (as I have seen sel linux stuff in there as well (its just a zip file)) would help at all. Meaning having matching RamDisk and HLOS (radio).
What do you think?
Im still stuck at work so I cannot try anything.

scrosler said:
Interesting. I would then have to assume the certs have changed? And the theory of using old ram disk may possibly be affective because its looking for old certs and not new? Or maybe just try swapping init binary?
I was also wondering if grabbing the newest hlos-bin (as I have seen sel linux stuff in there as well (its just a zip file)) would help at all. Meaning having matching RamDisk and HLOS (radio).
What do you think?
Im still stuck at work so I cannot try anything.
Click to expand...
Click to collapse
That might work, but we would need to update the init.*.sh sctipts to load the new ril blobs and maybe also to load the 3.4.x kernel. I need to get the NC1 ramdisk down locally and look at it. I was thinking maybe setting selinux to permissive or just disabling it could maybe be worth a shot but thats just a shot in the dark.
edit - here is a boot.img with the old init in it

[Q]Help & Assistance needed [Laime L2+]

Hi, I have a Laime L2+ MTK6589T Quad core 4.0.3, can't boot in to fastboot, can only reach recovery mode, as it keeps bootlooping, it loads to the boot screen say "Laime" and that's it, which leads me to think a corrupt boot, went ahead and wiped the cached etc. , is there an "update.zip" I can get from somewhere or I'm willing to make it myself as tbh i've had enough of my phones turning in to expensive paperweights
Also when I got the phone it didn't include any form of OTA firmware upgrading & there was no play store, if there's any way to include this that would be helpful.
Sorry for being a pain in the arse and asking so much for a first post :silly:

Anyone???

TheOMFG said:
Anyone???
Click to expand...
Click to collapse
www.needrom.com/download/laime-l2-sc8825-2/
1. download rom
2. download upgrade file
3. go into upgrade application
4. select pac file
Start!
@TheOMFG

techrefresh said:
wwwneedromcom/download/laime-l2-sc8825-2/
1. download rom
2. download upgrade file
3. go into upgrade application
4. select pac file
Start!
@TheOMFG
Click to expand...
Click to collapse
The phone does not boot in to fastboot mode, only recovery is there any way I can apply the rom as an update in recovery mode?, if so do need to compile a zip from what the "Upgrade application" downloaded???
I put the .pac file in and my phone never restarted and by the looks of it, no files were flashed to my device so I pulled all the files from the temp folder that it downloads to, here's what I've got:
boot.img
cache.img
DSP_DM_G2.bin
fdl1.bin
fdl2.bin
laime.bmp
nvitem.bin
recovery.img
SC8800G_sc8825_modem_vlx_6825.bin
SC8825.xml
system_2.img
u-boot.bin
u-boot-spl-16k.bin
userdata.img
vmjaluna_6825.image
WVGA_logo_256_t6_guangxin_180.bmp(1)
Where do I go from here?

????

http://specdevice.com/showspec.php?id=a7cb-ae42-ce49-2af60033c587
KERNEL: Linux version 3.0.8 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Wed Aug 13 11:51:42 CST 2014
CODENAME: REL
Mainboard: sp8825c2
BRAND: L200
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: s9_1602
DISPLAY: T6GUANGXIN1602_4.3L035_CN_140813
FINGERPRINT: T6_6825C_SC2330B_GUANGXIN_4.3_L035_CN_16+2_RC_140813
HARDWARE: sc8825
ID: IML74K
TAGS: test-keys
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.version.incremental=140
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.date=Wed Aug 13 11:49:03 CST 2014
ro.build.date.utc=1407901743
ro.build.type=user
ro.build.user=jenkins
ro.build.host=relserver1
ro.build.tags=test-keys
ro.build.version.release=4.0.3
ro.product.model=L200
ro.product.brand=L200
ro.product.name=s9_1602
ro.product.device=s9_1602
ro.product.board=sp8825c2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=L200
ro.wifi.channels=
ro.board.platform=sc8825
# ro.build.product is obsolete; use ro.product.device
ro.build.product=s9_1602
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=s9_1602-user 4.0.3 IML74K 140 test-keys
ro.build.characteristics=default
#-----below add or modified by revo begin------------
ro.product.locale.language=zh
ro.product.locale.region=CN
persist.sys.language=zh
persist.sys.country=CN
ro.macro.pro=t6_1602-guangxin
ro.macro.subpro=t6_1602-guangxin-4.3_l035
ro.device.support.gps=1
ro.device.support.gsensor=true
ro.device.support.psensor=false
ro.device.support.lsensor=false
ro.device.support.msensor=false
ro.device.support.bt=true
ro.device.support.wifi=true
ro.device.support.uplmn=false
ro.device.flashlight=true
ro.device.single_camera=false
ro.sf.hwrotation=0
ro.build.display.id=T6GUANGXIN1602_4.3L035_CN_140813
ro.build.fingerprint=T6_6825C_SC2330B_GUANGXIN_4.3_L035_CN_16+2_RC_140813
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.config.ringtone0=Backroad.ogg
ro.config.ringtone1=Backroad.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=
ro.macro.music_light_style=true
ro.macro.single_signal=yes
universe_ui_support_revo=true
ro.lockscreen.android42=false
ro.lockscreen.four.point=true
ro.macro.androidlogo.jellybean=yes
ro.macro.incall_touch_lock=yes
ro.macro.InCallScreenOffTime=
ro.macro.focus=true
ro.macro.auto_time_zone=no
ro.macro.connectdata=no
ro.macro.default_inputmethod=baidu
ro.macro.is24hour=yes
ro.macro.ip_dail=yes
ro.macro.screen_brightness=b_80
ro.macro.volume_music=d_12
ro.macro.volume_ring_notifi=d_7
ro.macro.volume_alarm=d_5
ro.macro.volume_fm=d_15
ro.macro.screen_timeout=lvl_1
ro.macro.install_no_market=true
ro.macro.font_size=Normal
ro.macro.boot_ani_choose=no
ro.email.default.signature=
ro.macro.status_bar_bg=transparent
ro.macro.status_bar_bg2=part_transparent
ro.macro.status_bar_bg3=
ro.macro.baseband_mtk_type=MTK6589T
ro.macro.baseband_mtk_number=quad_core
ro.macro.showcpuwithbb=
ro.macro.android_version=4.2.1JOP40D
ro.macro.kernel_version=3.4.35-g1f428cc
ro.macro.lockscrn_no_statusbar=yes
persist.sys.timezone=Asia/Shanghai
ro.macro.fake_romsize=
ro.macro.increase_ram=
ro.macro.vibrate_on=yes
ro.macro.accele_rotation=false
dailpad_search_list_custram=
ro.macro.camera_fullscreen=
ro.macro.dtmf_volume=40
ro.macro.custom_logo=
ro.macro.cycle_slip=
ro.macro.simcardnumber=
ro.macro.shutdownanim=
ro.macro.wifi_tether_ssid=
ro.macro.audio_profile=
ro.macro.hide_qsb_bar=yes
ro.macro.haptic_feedback=
ro.macro.native_launcher=
ro.macro.dtmf_tone=
ro.revo.testcase_alert=true
ro.revo.testalert_code=true
ro.revo.dcaf_orientation=false
device.support.dccaf=0
device.support.dvcaf=0
ro.macro.not_show_focustip=
ro.revo.gs_replace_ps=true
ro.revo.gs_replace_ps_value=
ro.revo.call_connection_notify=
ro.revo.exchange.notification=
ro.revo.fakedisplaysize=
ro.revo.useoneincomingsrc=
scroll_quick_switch=
ro.contacts.showstarredonly=
ro.revo.ori_incallscreen=true
ro.macro.statusbar_add_font=
ro.macro.wifi_policy=0
ro.revo.android_calc_style=
ro.revo.homepage=
###---3rd party func property
ro.macro.lqplay_lock=
ro.macro.yl_lock=
ro.sky.browser.support=true
ro.macro.cooee_lock=no
ro.macro.ouxin_switch=
ro.macro.all_apps_button_pos=
ro.macro.ibingo_lock=
ro.macro.yllg_lock=
ro.macro.ringcool=
ro.revo.mcetools=
#-----add or modified by revo end-----------
ro.macro.fake_new_function=
ro.macro.fake_score=
ro.macro.fake_resolution=
ro.macro.fake_camera=
ro.macro.fake_cpu=
ro.macro.fake_cpu_hz=
ro.macro.fake_gpu=
ro.macro.fake_rom=
ro.macro.fake_ram=
ro.macro.fake_pixel=
ro.mocro.single_simcard=
ro.macro.pro_sub=
ro.macro.fake_cpu_model=MTK6589
ro.macro.fake_android_version=
ro.macro.fake_dpi=
ro.macro.fake_freq=
ro.macro.google_ui=
ro.macro.vibrate_last=
ro.macro.vibrate_sleep=
ro.revo.sound_save_path=
ro.revo.sales=
ro.revo.sales_number=
ro.revo.add.reboot.menu=
ro.macro.display_battery=
ro.com.android.dateformat=MM-dd-yyyy
ro.macro.own_wallpaper_lock=
ro.revo.power_save=false
ro.macro.close.dc.sound=no
ro.device.support.vt=0
ro.revo.uui_incallscreen=
ro.macro.sync_wallpaper=
persist.sys.salescount=
persist.sys.sales_num=
persist.sys.sales_time=
ro.macro.yingmai_googleui=
ro.macro.yingmai_zen=
ro.macro.mms_signature=
ro.macro.tracker=
persist.sys.trackerstatus=
persist.sys.trackernum=
persist.sys.trackerpass=
persist.sys.trackerimsi=
ro.macro.statusbardata_mkt=
ro.browser.fontsize=
ro.macro.simcardnozero=
# end build properties
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.gpu=mali
ro.opengles.version=131072
ro.device.support.mmc=1
hwui.render_dirty_regions=false
ro.hwui.text_cache_width=2048
persist.ttydev=ttyVUART0
#if our product support cmcc feature, then set the value true, else do nothing
ro.wifi.support.cmcc=true
#our sp6825c1 product supports Trout chip
ro.wifi.chip.vender=trout
# Can not install packages if the data space has used more than the following ratio value
ro.datastorage.threshold=85
#if out product surport trout chip, we set this
ro.fm.chip.vendor=trout
#if out product surport trout chip, we set this to support hci rset to power off
ro.bt.trout=true
ro.device.support.vt=0
#if our product support single link version
ro.system.property.singleconn=true
ro.product.hardware=sp8825C2_V1.0.0
#true default, false if bt/wifi should not coexist.
ro.btwifi.coexist=true
#if out product support fastboot feature, set as true
persist.sys.support.fastboot=false
# modify for AMS kill background process
ro.support.amskill=true
#if our product not support bt wifisoftap coexist
ro.btwifisoftap.coexist=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
lmk.autocalc=false
ksm.support=false
zram.support=true
zram_for_android.enable=true
persist.sys.service.delay=false
persist.sys.lowmem=16
ro.build.product.lowmem=1
persist.blcr.enable=0
ro.callfirewall.disabled=true
persist.msms.phone_count=2
persist.msms.phone_default=0
persist.sys.lowcost=true
persist.sys.sprd.modemreset=1
persist.sys.kdump.enable=0
dalvik.vm.heapstartsize=3m
dalvik.vm.heapsize=64m
dalvik.vm.heapgrowthlimit=48m
ro.config.ringtone=BeatPlucker.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.logappslow=0
ro.floatkey.show=false
persist.sys.kb.auto=1
device.support.face.smile=0
device.support.pano=0

have you already tried factory reset in cwm and clear cashe/data/dalvik cache? try deleting and reseting everything posible. This might remake partitions and reflash some files that maybe have somehow gone wrong and causing bootloop. Also sometimes apps or combinations of apps can make the phone bootloop. Then wiping dalvik cache can help or factory reset can delete the non-system apps that caused it. Either way, it's worth trying it.
If this didn't fix the problem, try to find somthing with a working laime l2+ and ask him to make an backup in cwm and sent his files to you. You should have a file named "clockworkmod" on your sd-card, check if there's a file named "backup" (if there isn't, just make it), and place the backup file inside this folder. The backup file should be name somthing like "2015-04-24.18.03.57" so just a date, and contain some files like boot.img, .android_secure.vfat, cache.ext4.tar, data.ext4.tar and so on. Then go into recovery and restore this backup.
That's the best I can do for you as I don't know a lot about pushing rom's with pc, don't have a laime l2+ myself and don't know anyone who have one.
Pleas hit thanks, as I took the time to try to help you

[Completed] [Q] [HELP][MT65xx][ROM] Locked/OS FUBAR/no brick but still heavy

Hi, thank you for taking the time reading my post and any help or directions you could give to solving my problem.
I was given a phone (Samsung Galaxy Note 3) to replace my aging LG Optimus P509.
When I received the SGN3 I did a wipe of the user data so it was pristine through the recovery feature to put it back to 'stock'.
And that's when my issues began.
PROBLEM #1
First thing that happened after wiping is I 'lost' the internal 16Gb SD storage.
PC would only see the 2Gb's of application storage. Android system would see the 16Gb's, BUT it was reported as 'filled' with 15Gb's of data. If I just DID a wipe of the user data then where did all this 'data' come from???
So started looking around the system using different root explorers to see if I could manually delete the bloated data.
Couldn't find it.
I DID discover that the 'folder' that the 16Gb storage was under had no permissions. Just a series of dashes where the permissions would be listed. The OS's corrupted somehow...
Used a different Home loader and IT was reporting the 16Gb internal SD storage as there and pretty much empty. But still no access.
So I take it to a 'phone repair' place and explain to the guy what my issue was. Figured he was just going to look around and see what he could see. Nope, he starts pressing buttons and gets to the "recovery screen"...eventually. When I realized what he had did it was too late to stop him.
PROBLEM #2
The 'recovery screen' was not what I once saw, blue and orange screen with a droid on it, to a black screen with white characters with three options. Fast Boot, Recovery, Normal
AND the screen was now upside down in orientation and you could not use the 'enter' key (volume up). Refuses to select anything. So no more recovery option.
I learned through researching the issues here on XDA that a replacement ROM would be something I should do to address my issues, just reflash. Start anew.
I learned that the Device (Samsung Galaxy Note3) is NOT a SGN3! It's a KnockNote (my term). To my understanding you cant flash an OEM ROM on a non-OEM device. It's a Mediatek MT65xx device, made by China.
So I start looking around for a ROM to put on there. Not much that I can understand...
Here is the kernel information that 'could' help with identifing the device.
Code:
SM-N9006
Android version: 4.4
Baseband Ver.: N9006ZCUBMI3
Kernel Version: 3.4.0-1590669
[email protected] #1
Wed Sep 11 23:59:42 KST 2013
Build Number: JSS15J.N9006ZCUBMI5
Possible model (android tuner, build information) MT6620 (mt6582)
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=ALPS.JB5.MP.V1.5
ro.build.version.incremental=eng.rs.1390483692
ro.custom.build.version=.N9006V116En20140123
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.4
ro.build.date=2014年 01月 23日 星期四 21:29:52 CST
ro.build.date.utc=1390483792
ro.build.type=user
ro.build.user=rs
ro.build.host=rs-ThinkStation-D30
ro.build.tags=test-keys
ro.product.model=Samsung GALAXY Note 3
ro.product.brand=alps
ro.product.name=lcsh82_wet_jb5
ro.product.device=lcsh82_wet_jb5
ro.product.board=lcsh82_wet_jb5
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=lcsh82_wet_jb5
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=lcsh82_wet_jb5-user 4.4 JDQ39 eng.rs.1390483692 test-keys
ro.build.fingerprint=alps/lcsh82_wet_jb5/lcsh82_wet_jb5:4.4/JDQ39/1390483692:user/test-keys
ro.build.flavor=
ro.build.characteristics=default
persist.sys.timezone=Asia/Shanghai
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.JB5.MP.V1.5
ro.mediatek.platform=MT6582
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.JB5.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
# Switching Menu of Mass storage and MTP
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
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.sf.hwrotation=180
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
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=MT6620
mediatek.wlan.module.postfix=_mt6620
ril.radiooff.poweroffMD=0
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Alarm_Morning_flower.ogg
ro.config.ringtone=Over_the_horizon.mp3
ter.service.enable=0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
So I began using it as basically a PDA until I could get things sorted out.
PROBLEM #3
I allowed my niece (9yrs) to play some games on it and...she set up a very nice and complicated pattern lock that was so pretty to her that she forgot the pattern. not a problem as long as wi-fi or cell service is on...which this device has neither.
(no SIM, I turned off wifi before I handed it to her)
My questions are these:
Q 1 : Can I install a recovery ROM, stock ROM to the device?
If so, can you direct me (link) to where I can find the one I should use, based on your knowledge?
Q2: I can not get into the phone (pattern lock), is there a way to establish a connection to the phone even though I don't have access to 'developer options'?
Q3: Could you describe the steps needed to complete this task, I KNOW there are tuts galore. That's part of the problem. So many different ways, options, etc.
Since I am residentially challenged at the moment due to a fire this device is pretty critical to me and I can't screw it up, no fails, no bricks.
Any and all help you could offer would be appreciated.
If you need any more information about the device or require clarification please ask your questions.
Additional Information:
No WiFi (local/cell)
No Cellular Service
No 'developer/debug options' (because I am locked out of device with a pattern lock, see above)
No Adb
***BoM***
If this post is in the wrong place please direct me where to place it. XDA is a large place with a lot to sort through.
***EoM***

Hi,
The only way to get past a pin lock you can't figure out is completely wiping and flashing the stock firmware again, or custom ROM.
You will need to find out more details on the device. Make, model and exact model number, as flashing something not made for your device will likely brick it.
That said, you will need to ask for help here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
And personally, I'd leave out the don't waste my time or yours part...as that likely will cause many to pass you by. Not every reply is going to be 100 percent accurate or relevant...but trying to help is better than not trying. That's the spirit here. And it's a part of any internet forum. Just my humble opinion.
Good luck!

Thank you. Thread closed.