Database Users

[Request] US 9.2.1.27 build.prop

Please see:
http://forum.xda-developers.com/showthread.php?t=1816022

Head on over to the OTA 9.2.1.27 US/WW/TW - CWM zip thread, download the rom you want (US, WW, or TW). Once you have the .zip rom downloaded on your pc, simply extract it, go to the /system folder and you can find the build.prop from there
Hold on, those are just patch updates.. You will actually need to download the rom from Asus' support page do as stated above.

It goes a little something like this:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.US_epad-9.2.1.27-20120615
ro.build.version.incremental=US_epad-9.2.1.27-20120615
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jun 15 17:45:41 CST 2012
ro.build.date.utc=1339753541
ro.build.type=user
ro.build.user=
ro.build.host=Mars
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=US_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=EeePad
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.2.1.27-20120615 release-keys
ro.build.fingerprint=asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.2.1.27-20120615:user/release-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libpath=/system/lib/libmbm-ril.so
rild.libargs=-d /dev/ttyACM0 -i wwan0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
wifi.version.driver=V6.1.24
gps.version.driver=V6.9.12
keyguard.no_require_sim=true
ro.kernel.qemu=
bt.version.driver=V8.30
gsm.bodysargsm=32,26,29,29
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r1
ro.com.google.clientidbase=android-asus
ro.wifi.country=US
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

fone_fanatic said:
Head on over to the OTA 9.2.1.27 US/WW/TW - CWM zip thread, download the rom you want (US, WW, or TW). Once you have the .zip rom downloaded on your pc, simply extract it, go to the /system folder and you can find the build.prop from there
Hold on, those are just patch updates.. You will actually need to download the rom from Asus' support page do as stated above.
Click to expand...
Click to collapse
Neither one would work: because it is contained in in the blob file. If you or anyone could tell me how to get it out ( without running Linux, and building the unblob tool from github, and etc.), I would be very appreciative.
gee one said:
It goes a little something like this:
Code:
...
[/QUOTE]
Thank You, Thank You
Just what I needed
Click to expand...
Click to collapse

[ROM][WIP][Quad-MX][HK] MIUI V4 & ICS 4.0.3

MIUI V4
CAN ANYONE HELP ME PORT CWM? SEND ME A PM!
Working:
Camera (Cant take pictures without SD)
Sound
WIFI
DATA
Calls & SMS
Not Working:
Internal SD (Not mounted)
Download: Comming Soon
Vanilla ICS
Working:
Camera (Cant take pictures without SD)
Sound
WIFI
DATA
Calls & SMS
Not Working:
Internal SD (Not mounted)
Download: Comming soon
DO YOU THINK YOU CAN HELP ME? SEND A PM!
Sources:
Kernel Source: https://github.com/lvchaqiu/meizu-mx-kernel
MIUI Recovery Source: https://github.com/MiCode/patchrom_mx/tree/ics/bootable/recovery
More to come soon...

For later use

wasnt MIUI V4 imported?

ernmin said:
wasnt MIUI V4 imported?
Click to expand...
Click to collapse
Not for the quad-core model

Is there a way to build the MIUI V4 on the Flyme Base and not the buggy Stock ICS ??

eliaztheone said:
Is there a way to build the MIUI V4 on the Flyme Base and not the buggy Stock ICS ??
Click to expand...
Click to collapse
It is probably possible, but there is no good miui device rom to start from, because Nexus S and Galaxy Nexus is based on JB. I would not base on touchwiz-based MIUI for GalaxyS 2 and 3.

Im trying to port CM9, im stuck at cm9 bootanimation, and logcat not working :s

just for HK.
Sent from my M032 using xda app-developers app

As far as cwm, either use koush's builder at builder.clockworkmod.com and put the recovery.img in and recovery.fstab, or unpack stock recovery using a ramdisk unpack (aka boot.img unpacker) tool and copy over recovery.fstab and default.prop to cwm and repack.
Sent from my SPH-D700 using Tapatalk 2

xboxfanj said:
As far as cwm, either use koush's builder at builder.clockworkmod.com and put the recovery.img in and recovery.fstab, or unpack stock recovery using a ramdisk unpack (aka boot.img unpacker) tool and copy over recovery.fstab and default.prop to cwm and repack.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
The MX uses recovery-uboot.img and is not packed the same as a normal recovery.img

It's not an issue. As I reckon, CWM recovery imgs lack the 64-byte u-boot header (IH_MAGIC) for the ramdisk, they are the ones that are not "the norm".
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p2
/data ext4 /dev/block/mmcblk0p3
/cache ext4 /dev/block/mmcblk0p4
/misc emmc /dev/block/mmcblk0p9
/recovery emmc /dev/block/mmcblk0p10
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mass_storage
# begin build properties
# autogenerated by buildinfo.sh
ro.build.cta=noncta
ro.build.id=IML74K
ro.build.display.id=Flyme 1.0.3
ro.build.mask.id=4.0.0-7929_zh-HK
ro.build.version.incremental=eng.mobileapp.20120725.003030
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=2012年 07月 25日 星期三 00:30:53 CST
ro.build.date.utc=1343147453
ro.build.type=user
ro.build.user=mobileapp
ro.build.host=mobileapp
ro.build.tags=test-keys
ro.product.model=M03X
ro.product.brand=Meizu
ro.product.name=meizu_mx
ro.product.board=mx
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Meizu
ro.product.locale.language=zh
ro.product.locale.region=TW
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=meizu_mx-user 4.0.3 test-keys 7929_zh-HK
ro.build.fingerprint=Meizu/meizu_mx/mx:4.0.3/IML74K/eng.mobileapp.20120725.003030:user/test-keys
ro.build.characteristics=phone
# end build properties
#
# system.prop for mx
#
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyACM0
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.com.android.dateformat=MM-dd-yyyy
ro.opengles.version=131072
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.sf.lcd_density=320
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.config.ringtone=Crystal.ogg
ro.config.notification_sound=VideoRecord.ogg
ro.config.mms_sound=Ripples.ogg
ro.config.email_sound=VideoRecord.ogg
ro.config.calendar_sound=Jump.ogg
ro.config.alarm_alert=Morning_Dew.ogg
ro.telephony.default_network=0
persist.sys.timezone=Asia/Hong_Kong
persist.sys.meizu.region=hk-tw
persist.sys.meizu.codepage=big5
ro.meizu.setupwizard.flyme=false
ro.meizu.setupwizard.setlang=true
ro.meizu.region.enable=true
ro.meizu.contactmsg.auth=false
ro.meizu.customize.pccw=false
ro.meizu.autorecorder=true
ro.meizu.visualvoicemail=true
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

TwoPointZero said:
It's not an issue. As I reckon, CWM recovery imgs lack the 64-byte u-boot header (IH_MAGIC) for the ramdisk, they are the ones that are not "the norm".
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p2
/data ext4 /dev/block/mmcblk0p3
/cache ext4 /dev/block/mmcblk0p4
/misc emmc /dev/block/mmcblk0p9
/recovery emmc /dev/block/mmcblk0p10
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mass_storage
# begin build properties
# autogenerated by buildinfo.sh
ro.build.cta=noncta
ro.build.id=IML74K
ro.build.display.id=Flyme 1.0.3
ro.build.mask.id=4.0.0-7929_zh-HK
ro.build.version.incremental=eng.mobileapp.20120725.003030
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=2012年 07月 25日 星期三 00:30:53 CST
ro.build.date.utc=1343147453
ro.build.type=user
ro.build.user=mobileapp
ro.build.host=mobileapp
ro.build.tags=test-keys
ro.product.model=M03X
ro.product.brand=Meizu
ro.product.name=meizu_mx
ro.product.board=mx
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Meizu
ro.product.locale.language=zh
ro.product.locale.region=TW
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=meizu_mx-user 4.0.3 test-keys 7929_zh-HK
ro.build.fingerprint=Meizu/meizu_mx/mx:4.0.3/IML74K/eng.mobileapp.20120725.003030:user/test-keys
ro.build.characteristics=phone
# end build properties
#
# system.prop for mx
#
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyACM0
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.com.android.dateformat=MM-dd-yyyy
ro.opengles.version=131072
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.sf.lcd_density=320
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.config.ringtone=Crystal.ogg
ro.config.notification_sound=VideoRecord.ogg
ro.config.mms_sound=Ripples.ogg
ro.config.email_sound=VideoRecord.ogg
ro.config.calendar_sound=Jump.ogg
ro.config.alarm_alert=Morning_Dew.ogg
ro.telephony.default_network=0
persist.sys.timezone=Asia/Hong_Kong
persist.sys.meizu.region=hk-tw
persist.sys.meizu.codepage=big5
ro.meizu.setupwizard.flyme=false
ro.meizu.setupwizard.setlang=true
ro.meizu.region.enable=true
ro.meizu.contactmsg.auth=false
ro.meizu.customize.pccw=false
ro.meizu.autorecorder=true
ro.meizu.visualvoicemail=true
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
I have a cwm build but its not uboot, so its not working

The recovery-uboot.img file from Meizu does NOT have a ANDROID header. The CWM one i built does. We need to convert it to a valid uboot image.

useless

darycs2006 said:
useless
Click to expand...
Click to collapse
Your post is useless

instead of useless I will be more than happy beta testing for this project count me in.:laugh:
from norway

I would love to be able to put MIUI or vanilla ICS on my Meizu MX 4-core. I don't even use it at the moment since I can't stand Flyme OS.
Good luck with the project! I will follow it closely.

As for CWM - is a kernel rebuild really necessary?
Shouldn't a normal ramfs mod of the original recovery be plenty given that the required modules are loaded by the original recovery kernel image?

thank you for your work about MX-4core，I am a user of this phone from china，I can't help you with android development,But I wish I can help you somewhere~~~

ykker said:
thank you for your work about MX-4core，I am a user of this phone from china，I can't help you with android development,But I wish I can help you somewhere~~~
Click to expand...
Click to collapse
Hit the thanks button, if nothing else

Photosphere not working [SOLVED]

I solved my camera issues yesterday BUT noticed today that the photosphere is not working, I get the following msg "Sorry, your device is not yet supported. Model: unknown (LGE)"
Anyone know how to solve this error?
Cheers
Rooted - 4.2.1

the ro.product.model and the ro.product.brand files are missing from the build.prop How do i get these again?

did you root it? if so, simply reflashing your rom without wiping the data would be the easiest solution.

Nuu~ said:
did you root it? if so, simply reflashing your rom without wiping the data would be the easiest solution.
Click to expand...
Click to collapse
I'm rooted but on stock. I tried restoring the first back-up right after I rooted but that didn't seem to work.
SOLUTION: I added the two missing lines in the build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JOP40D
ro.build.display.id=JOP40D
ro.build.version.incremental=533553
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.1
ro.build.date=Tue Nov 20 00:56:01 UTC 2012
ro.build.date.utc=1353372961
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpba6.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Nexus 4
ro.product.brand=google
ro.product.name=occam
ro.product.device=mako
ro.product.board=MAKO
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
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=mako
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=occam-user 4.2.1 JOP40D 533553 release-keys
ro.build.fingerprint=google/occam/mako:4.2.1/JOP40D/533553:user/release-keys
ro.build.characteristics=nosdcard
# end build properties

how do I install CWM recovery on att S4?

I'm following these instructions: http://wiki.cyanogenmod.org/w/Install_CM_for_jflte
using the "AT&T variant" instructions. I've already done root. I ran the "install-cwm.cmd". just a dos window blinked open and went away. I dont know how to install ClockworkMod Recovery. it just says rename to recovery.img. it doesn't say how to actually install it. when I "hold Volume Up, Home & Power.". the phone goes into android system recovery 3e instead of CWM recovery. I assume CWM recovery is not installed and the instructions don't say how to install it.
thanks.

Gabe3 said:
I ran the "install-cwm.cmd". just a dos window blinked open and went away. I dont know how....
Click to expand...
Click to collapse
Ekhm... may I ask one small question?
Of course, while reading the prerequisites, and verifying the tools you are using, you have recognized that Loki uses adb command?
And, knowing that, you of course do know that to do anything via adb from Windows based PC, you need to have the Android SDK installed and working?
EDIT: one more question: just by the accident, have you even though about placing your question in ATT section, or even looking for your solution, for example here???

spamtrash said:
Ekhm... may I ask one small question?
Of course, while reading the prerequisites, and verifying the tools you are using, you have recognized that Loki uses adb command?
And, knowing that, you of course do know that to do anything via adb from Windows based PC, you need to have the Android SDK installed and working?
EDIT: one more question: just by the accident, have you even though about placing your question in ATT section, or even looking for your solution, for example here???
Click to expand...
Click to collapse
still lost. I dont see a guide in the att section. where can I get the latest CWM Recovery lok file?

Gabe3 said:
still lost. I dont see a guide in the att section. where can I get the latest CWM Recovery lok file?
Click to expand...
Click to collapse
What is your model of phone?

Joku1981 said:
What is your model of phone?
Click to expand...
Click to collapse
AT&T Galaxy S4 SGH-i337
I was going to use this guide: http://galaxys4root.com/galaxy-s4-root/how-to-install-cwm-recovery-on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
but the recovery lok file in the guide is pretty old.
I've also tried using odin but it fails.

Gabe3 said:
AT&T Galaxy S4 SGH-i337
I was going to use this guide: http://galaxys4root.com/galaxy-s4-root/how-to-install-cwm-recovery-on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
but the recovery lok file in the guide is pretty old.
Click to expand...
Click to collapse
Is it really so hard to go to General section of I337 to find this thread, or, if you'd look deeper, to look into this, where, in section Step 2: Rooting Your Device - you have very specific split what is for which model is what type of custom recovery (and, it seems that CWM is for I337M, a Canadian version ONLY) preferred, at least for rooting.
however, Section 3 provides easy instruction step by step what you shall do...

Gabe3 said:
AT&T Galaxy S4 SGH-i337
I was going to use this guide: http://galaxys4root.com/galaxy-s4-root/how-to-install-cwm-recovery-on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
but the recovery lok file in the guide is pretty old.
Click to expand...
Click to collapse
The codename is "jflteatt". Also known as SGH-I337. CWM is old for this new phone, use Philz Touch now:
- Guide for flash the recovery: HERE
- This is the file for install it (select latest version): HERE

spamtrash said:
Is it really so hard to go to General section of I337 to find this thread, or, if you'd look deeper, to look into this, where, in section Step 2: Rooting Your Device - you have very specific split what is for which model is what type of custom recovery (and, it seems that CWM is for I337M, a Canadian version ONLY) preferred, at least for rooting.
however, Section 3 provides easy instruction step by step what you shall do...
Click to expand...
Click to collapse
looks like motochopper root failed. It said failed when I did it but it prompted me to reboot the phone so I thought it worked and superuser app got installed. superuser says "the superuser binary (su) must be updated. please choose an installation method. recovery mode installation is recommended for htc devices."
also, when I use root checker it says I don't have root. looks like back to step 1. I tried motochopper again and it still says failed.

just used the CASUAL application and checked root checker, still no root.
heres the casual log:
[*] Waiting for device...
Waiting for ADB device connection. When Windows 7 recognizes the device, we will continue. Don't touch anything.
[*] Device found.
[*] Pushing exploit...
2816 KB/s (1283460 bytes in 0.445s)
[*] Pushing root tools...
3916 KB/s (96260 bytes in 0.024s)
4132 KB/s (1578585 bytes in 0.373s)
[*] Pushing recovery to device...
4225 KB/s (10484224 bytes in 2.423s)
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
installing superuser to system partition
/system/bin/sh: su: not found
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=KOT49H.I337UCUFNB1
ro.build.version.incremental=I337UCUFNB1
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Tue Feb 11 22:30:13 KST 2014
ro.build.date.utc=1392125413
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWDD5521
ro.build.tags=release-keys
ro.product.model=SAMSUNG-SGH-I337
ro.product.brand=samsung
ro.product.name=jflteuc
ro.product.device=jflteatt
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=jflteatt
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=jflteuc-user 4.4.2 KOT49H I337UCUFNB1 release-keys
ro.build.fingerprint=samsung/jflteuc/jflteatt:4.4.2/KOT49H/I337UCUFNB1:user/release-keys
ro.build.characteristics=att
# Samsung Specific Properties
ro.build.PDA=I337UCUFNB1
ro.build.hidden_ver=I337UCUFNB1
ro.build.changelist=505595
ro.product_ship=true
ro.chipname=apq8064
# end build properties
#
# from device/samsung/jflteatt/system.prop
#
#
# system.prop for surf
#
ro.sf.lcd_density=480
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=gpu
dalvik.vm.heapsize=36m
debug.enable.wl_log=1
persist.hwc.mdpcomp.enable=true
debug.mdpcomp.logs=0
#
# system props for the cne module
#
persist.cne.feature=0
lpa.decode=false
tunnel.decode=true
tunnel.audiovideo.decode=false
lpa.use-stagefright=true
qcom.hw.aac.encoder=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
media.aac_51_output_enabled=true
#33395 is sum of supported format flags in AAL
#Formats: AVI AC3 ASF AAC QCP DTS 3G2
mm.enable.qcom_parser=33395
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data.netmgrd.qos.enable=false
#system props for time-services
persist.timed.enable=true
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
persist.audio.lowlatency.rec=false
# 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
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
# 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 prop to enable ehrpd capability
ro.config.ehrpd=true
# System property for cabl
ro.qualcomm.cabl=0
# 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
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=none
ro.qc.sdk.camera.facialproc=true
ro.qc.sdk.gestures.camera=false
ro.qc.sdk.sensors.gestures=false
#property to check if dynamic resolution change is supported in framework
ro.streaming.video.drs=true
#property to enable user to access Google WFD settings.
persist.debug.wfd.enable=1
#property to choose between virtual/external wfd display
persist.sys.wfd.virtual=0
#system prop for setting rmnet mux mode
persist.rmnet.mux=disabled
#
# System prop for Tvout/HDMI
#
persist.sys.camera.transform=0
persist.sys.camera.connect=0
persist.sys.videomode=0
ro.hdmi.enable=true
# System property for Default Brightness
ro.lcd_min_brightness=10
ro.lcd_brightness=143
# System proverty for sys info indication
persist.radio.add_power_save=1
# Keep SIM state on LPM mode
persist.radio.apm_sim_not_pwdn=1
# use se table when search list
persist.radio.use_se_table_only=1
# System prop for PLMN
persist.radio.fill_eons=1
# System prop for SPN
persist.radio.prefer_spn=0
media.enable-commonsource=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.vendor.extension_library=/vendor/lib/libqc-opt.so
ro.build.scafe=americano
ro.build.scafe.size=short
ro.build.scafe.shot=single
ro.hdcp2.rx=tz
ro.secwvk=144
ro.securestorage.support=true
security.mdpp=None
ro.security.mdpp.ver=1.0
ro.security.mdpp.release=2
security.mdpp.result=None
ro.sec.fle.encryption=true
ro.hwui.texture_cache_size=48
ro.hwui.layer_cache_size=32
ro.hwui.path_cache_size=8
ro.hwui.shape_cache_size=2
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=4
ro.hwui.texture_cache_flush_rate=0.5
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=512
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
ro.error.receiver.default=com.samsung.receiver.error
ro.config.ringtone=ATT_Firefly_Default.ogg
ro.config.notification_sound=Whisper.ogg
ro.config.alarm_alert=Alarm_Morning_flower.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.security.mdpp.ux=Enabled
ro.setupwizard.mode=OPTIONAL
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-att-us
ro.com.google.clientidbase.am=android-att-us
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=4.4.2_r1
persist.sys.dalvik.vm.lib=libdvm.so
ro.kernel.qemu=0
ro.build.selinux=1
ro.config.knox=1
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=1
ro.qc.sdk.izat.service_mask=0x5
persist.gps.qc_nlp_in_use=0
ro.gps.agps_provider=1
[*] Installing Recovery
/system/bin/sh: su: not found
[*] rebooting into recovery. Ensure that you "Install Superuser" in after you reboot into Android for security reasons!
done
Script Complete
Click to expand...
Click to collapse

Gabe3 said:
looks like motochopper root failed. It said failed when I did it but it prompted me to reboot the phone so I thought it worked and superuser app got installed. superuser says "the superuser binary (su) must be updated. please choose an installation method. recovery mode installation is recommended for htc devices."
also, when I use root checker it says I don't have root. looks like back to step 1. I tried motochopper again and it still says failed.
Click to expand...
Click to collapse
The thread u created was for install custom recovery or root ur phone? If you want root ur phone too, follow this GUIDE, special for your device model.

Joku1981 said:
The thread u created was for install custom recovery or root ur phone?
Click to expand...
Click to collapse
well I wanted to root my phone so I could install cwm recovery to let me put cm11 on. but looks like my firmware version "NB1" isn't able to be rooted.

Gabe3 said:
well I wanted to root my phone so I could install cwm recovery to let me put cm11 on. but looks like my firmware version "NB1" isn't able to be rooted.
Click to expand...
Click to collapse
I answered you the 2 questions: Flash custom recovery and root ur phone :highfive:

Joku1981 said:
I answered you the 2 questions: Flash custom recovery and root ur phone :highfive:
Click to expand...
Click to collapse
thanks. it would have worked if my phone didn't have the NB1 firmware.

I'm finally able to give an answer instead of reading one.
I sent you a personal message with my post since I can't post links yet, as I've just made an account. Been lurking forever it was time. I will post it here when I can for any future passersby.

need the original build.prop

I need the build.prop of the shield TV as I try to spoof my Shield Tablet to buy shield TV only games from the PlayStore.
Yes I know that some games might not work on the tablet but I ordered a Shield TV and just want to prepurchase the games, which I can't do without a compatible device.
I already tried downloading the OTA update and extract the puild.prop with an linux explorer but the file seems to be encrypted or compressed.

anybody?

If you care to download the full oem images you can extract it from there unfortunately I'm not yet rooted (waiting for marshmallow first) so I can't pull mine for you

nex86 said:
I need the build.prop of the shield TV as I try to spoof my Shield Tablet to buy shield TV only games from the PlayStore.
Yes I know that some games might not work on the tablet but I ordered a Shield TV and just want to prepurchase the games, which I can't do without a compatible device.
I already tried downloading the OTA update and extract the puild.prop with an linux explorer but the file seems to be encrypted or compressed.
Click to expand...
Click to collapse
here is mine:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47D
ro.build.display.id=LMY47D.35739_609.6420
ro.build.version.incremental=35739_609.6420
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1
ro.build.date=Thu Oct 8 13:57:46 PDT 2015
ro.build.date.utc=1444337866
ro.build.type=user
ro.build.user=NVIDIA
ro.build.host=mobile-u64-396
ro.build.tags=release-keys
ro.build.flavor=foster_e-user
ro.product.model=SHIELD Android TV
ro.product.brand=NVIDIA
ro.product.name=foster_e
ro.product.device=foster
ro.product.board=
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=NVIDIA
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=foster
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=foster_e-user 5.1 LMY47D 35739_609.6420 release-keys
ro.build.fingerprint=NVIDIA/foster_e/foster:5.1/LMY47D/35739_609.6420:user/release-keys
ro.build.characteristics=tv
# end build properties
#
# from device/nvidia/soc/t210/system.prop
#
# opengles.version is 16.16 (maj.min) fixed point
ro.opengles.version=196609
persist.tegra.nvmmlite=1
persist.wlan.ti.calibrated=0
ro.sf.override_lcd_density=1
# glcomposer composition
persist.tegra.compositor=glcomposer
persist.tegra.decompression=cde-client
# WAR for bug 1536227: Restrict all ZBC clears to transparent black:
persist.tegra.AF73C63E=0x80007ffd
# disable input resampling
ro.input.noresample=1
#enable Miracast game mode support
nvwfd.gamemode=1
#max resolution supported for Miracast is 1080p, represented interms of macroblocks
nvwfd.max_macroblocks=8160
# usb vendor and product ID definition
ro.nv.usb.vid=0955
ro.nv.usb.pid.mtp=B430
ro.nv.usb.pid.mtp.adb=B431
ro.nv.usb.pid.rndis=B434
ro.nv.usb.pid.rndis.adb=B435
ro.nv.usb.pid.ptp=B432
ro.nv.usb.pid.ptp.adb=B433
#Set audioflinger resampler quality to DYN_HIGH_QUALITY
af.resampler.quality=7
#
# from device/nvidia/platform/t210/system.prop
#
wifi.interface=wlan0
wifi.Xinterface=xlan0
ap.interface=wlan0
# boot animation property
persist.bootanim.preload=1
#pbc properties
pbc.log.on=0
pbc.hist.size=5
pbc.step.period=700
pbc.polling.period=100
pbc.throttle.depth=0
persist.sys.pbc.enabled=1
persist.sys.pbc.hyst=5
persist.sys.pbc.psys.cap=10000
persist.sys.pbc.ibat.cap=4000
persist.sys.pbc.pbat.cap=30000
persist.sys.pbc.inf.game.mode=1
persist.sys.pbc.inf.socthres=20
persist.sys.pbc.pbat.slope=1.5
persist.sys.pbc.pbat.intercept=-7
persist.sys.pbc.over.cfboost=true
persist.sys.pbc.cfboost.floor=800000
persist.sys.pbc.gfboost.floor=300000
#disable Eco mode with charger
persist.sys.NV_ECO.IF.CHARGING=false
#playback type device, for cec
ro.hdmi.device_type=4
#used to enable adb over tcpip on port 5555 from Settings app
persist.system.adb.tcp.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.sys.media.avsync=true
dalvik.vm.heapstartsize=12m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=448m
ro.build.version.ota=2.1(22.18.61.16)
drm.service.enabled=true
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.0_r2
ro.com.google.clientidbase=android-nvidia
ro.sf.lcd_density=320
ro.nrdp.modelgroup=SHIELDANDROIDTV
ro.nrdp.audio.otfs=false
ro.radio.noril=true
ro.tegra.tz3.sorting=1
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.features=div
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

*deleted...wrong thread. Doh!