Hi,
Its been complained about on couple of threads but im looking for some hope.
Im trying to get UBS Mobile Banking in Switzerland but its not compatible with SGS2 (due to my custom ROM, Root, who know why) This as many apps would most likely work if downloaded as apk and installed with e.g. rootexplorer.
Is there a way to trick the android market to get any apk from it ? Maybe some new generic account on google or else ?
Thanks
smartin said:
Hi,
Its been complained about on couple of threads but im looking for some hope.
Im trying to get UBS Mobile Banking in Switzerland but its not compatible with SGS2 (due to my custom ROM, Root, who know why) This as many apps would most likely work if downloaded as apk and installed with e.g. rootexplorer.
Is there a way to trick the android market to get any apk from it ? Maybe some new generic account on google or else ?
Thanks
Click to expand...
Click to collapse
have a play with this
https://market.android.com/details?id=ch.racic.android.marketenabler&hl=en
Tried that already,
I believe its not the network but more like some silly descriptor somewhere in phone identifier.
Weird thing. I did took another Androdid phone, downloaded the application from UBS but its not in system\app directory.
When in settings i try to copy it to SD card is says it is copy protected.
Sent from my GT-I9100 using XDA App
Guys,
Question to developers: how does market decide if an app is compatible our not ?
Some custom roms will see app on the market and some won't.
I did change the CSC to Swisscom and still nothing so its not that
Bests
Sent from my GT-I9100 using XDA App
Have you changed your dpi settings? Set it back to stock 240 and you should can download it...
Gesendet von meinem GT-I9100 mit Tapatalk
bgx,
my build.prop shows: ro.sf.lcd_density=240 so its not that
i start to think UBS Mobile banking is not compatible although comments on the market indicate it is.
My whole prop file
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=--VK-- Stable -XWKL1-[V3.2]-
ro.build.version.incremental=XWKL1
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Tue Dec 13 14:39:43 CET 2011
ro.build.date.utc=1323783583
ro.build.type=user
ro.build.user=root
ro.build.host=DELLBUILDER12
ro.build.tags=release-keys
ro.product.model=GT-I9100
ro.product.brand=samsung
ro.product.name=GT-I9100
ro.product.device=GT-I9100
ro.product.board=GT-I9100
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I9100XWKL1
ro.build.hidden_ver=I9100XWKL1
ro.build.changelist=809037
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=vi
ro.product.locale.region=VN
ro.wifi.channels=
ro.board.platform=s5pc210
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9100
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9100-user 2.3.6 GINGERBREAD XWKL1 release-keys
ro.build.fingerprint=samsung/GT-I9100/GT-I9100:2.3.6/GINGERBREAD/XWKL1:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9100XWKL1
ro.build.hidden_ver=I9100XWKL1
ro.build.changelist=809037
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
#
# system.prop for asop5000
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=64m
# Samsung USB default mode
persist.service.usb.setting=0
dev.powersave_fps=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.com.google.clientidbase=android-samsung
ro.com.google.gmsversion=2.3_r8
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
dev.sfbootcomplete=0
ro.com.google.clientidbase=android-samsung
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
keyguard.no_require_sim=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.opengles.version=131072
ro.setupwizard.mode=OPTIONAL
ro.secdevenc=true
ro.wtldatapassword=true
ro.error.receiver.default=com.samsung.receiver.error
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.enable.3g.prefix=1
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=9
ro.ril.hsxpa=3
ro.ril.hep=1
ro.ril.enable.a53=1
# pongsters special speed tweaks
windowsmgr.max_events_per_sec=150
wifi.supplicant_scan_interval=180
# Phone tweaks
ro.HOME_APP_ADJ=1
ro.media.enc.jpeg.quality=100
debug.sf.hw=1
ro.telephony.call_ring.delay=0
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
persist.adb.notify=0
debug.performance.tuning=1
video.accelerate.hw=1
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
ro.lge.proximity.delay=25
mot.proximity.delay=25
ro.config.hw_menu_unlockscreen=false
persist.sys.use_dithering=0
persist.sys.purgeable_assets=1
dalvik.vm.dexopt-flags=m=y
ro.mot.eri.losalert.delay=1000
thanks
UBS Mobile App
I do not think it is our problem to install this app on devices we have. It is a problem of UBS which apparently can not deliver working product. I have complained/informed them already and would suggest to do the same.
W.
WiktorMk said:
I do not think it is our problem to install this app on devices we have. It is a problem of UBS which apparently can not deliver working product. I have complained/informed them already and would suggest to do the same.
W.
Click to expand...
Click to collapse
I did complain and i did get answer that is should work on SGS2.
I did in the meantime flashed back to stock rom (from VK) and i could
download and install the app.
Then i loaded Ultratoxic (as this is odin so could easily get custom rom and not go via installation of CWM).
UBS mobile app is also visible and can be loaded into it.
So I figure there are some parameters in VK rom and some others
that block this an perhaps other apps.
cheers
Anybody managed to get the APK for this ?
Can somebody share their APK file ?
why hasn't anyone shared the apk ?
smartin said:
Tried that already,
I believe its not the network but more like some silly descriptor somewhere in phone identifier.
Weird thing. I did took another Androdid phone, downloaded the application from UBS but its not in system\app directory.
When in settings i try to copy it to SD card is says it is copy protected.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
since its not a systemapp you have to search for it in /data/app/, downloaded apps will be stored there.
KcDaRookie said:
since its not a systemapp you have to search for it in /data/app/, downloaded apps will be stored there.
Click to expand...
Click to collapse
Just use titanium backup then find the apk there.
Please post here!
Meanwhile I had a friend do it for me.
http://dl.dropbox.com/u/92090/UBS_Mobile_Banking_Titanium_Bakcup.zip
Unzip and place 3 files into the TitanuimBackup folder on your sdcard, then open Titanium backup and Restore.
Works on my GN
horadee said:
Meanwhile I had a friend do it for me.
http://dl.dropbox.com/u/92090/UBS_Mobile_Banking_Titanium_Bakcup.zip
Unzip and place 3 files into the TitanuimBackup folder on your sdcard, then open Titanium backup and Restore.
Works on my GN
Click to expand...
Click to collapse
how do you restore it from titatium ? it doesn't show on the list of app.
chance the build prop.to the right samsung names
i am sure its a build prop. problem... i have a china tablet and when i got it,it could not download anything from market not even facebook i therefor chance the build prop. to a galaxy tab name and now i can download all things to that tab...
so if you have custom rom((because the names in custom roms is not always right)) you wanna chance the build prop. with root explorer ect. to the proper names...SAMSUNG names just find a build prop. like that above and make your names the same. save it and root explorer makes a copy of your old prop. you can go back to if you want.. reboot your phone and now you can download all the normal apps for sgs2..
you can also if you want a game there is not compatibel with our samsungs sgs2..
chance it to whatever you like(htc sensation) install the game rewert back to your stock build prop. and play the game...
hope its usefull and sorry the english.. martin
Related
After getting the GN, I did the update to 4.0.2. Waited a few hours and then went to work. The store I work at has the ability to use NFC. I thought what the hell, I'll try it. Fired up the app cause it was already on my phone and created an account. Got the free $10. And then I made a purchase!!
What the hell? I though Verizon was blocking it. Anyway, I decide to update my apps thru the market and it brought down the newest Google Wallet APK from 12.12.11. Now when I open the app it states that I must have a Google Employee account and the only option is to press "ok" and it closes the app.
Anyone else tried this? Dont know if it works out the box and the update for it kills it or if it just takes time for Verizon to find out and they kill it on there side.
christianpeso said:
After getting the GN, I did the update to 4.0.2. Waited a few hours and then went to work. The store I work at has the ability to use NFC. I thought what the hell, I'll try it. Fired up the app cause it was already on my phone and created an account. Got the free $10. And then I made a purchase!!
What the hell? I though Verizon was blocking it. Anyway, I decide to update my apps thru the market and it brought down the newest Google Wallet APK from 12.12.11. Now when I open the app it states that I must have a Google Employee account and the only option is to press "ok" and it closes the app.
Anyone else tried this? Dont know if it works out the box and the update for it kills it or if it just takes time for Verizon to find out and they kill it on there side.
Click to expand...
Click to collapse
are you rooted? how did you get the app again. please elaborate
it is not on the market for me.
Honestly, I dont know how I got it. I thought it came with it. And I never had Wallet before on any ANdroid phone so it wasn't syncing it from prior. Was just going thru my apps list and it was there. Even after all this, I then unlocked my bootloader and that reset everything. Google wallet was still there and there was that update in the market. Going back to work today. Will probably lock and unlock again and try Wallet again to see if it works before updating it.
I am not rooted.
can you pull the apk and post up here please
Please post proof, I'm using a non rooted stock GSM NS and I don't see it in the market.
christianpeso said:
Honestly, I dont know how I got it. I thought it came with it. And I never had Wallet before on any ANdroid phone so it wasn't syncing it from prior. Was just going thru my apps list and it was there. Even after all this, I then unlocked my bootloader and that reset everything. Google wallet was still there and there was that update in the market. Going back to work today. Will probably lock and unlock again and try Wallet again to see if it works before updating it.
I am not rooted.
Click to expand...
Click to collapse
Using Astro or any other file explorer:
navigate to "/" (the root directory of the phone, root is not required to view the files here)
Go to the "System" folder
Long press on the "build" or "build.prop" file, and select "open as," then select "text"
I used "File Editor" in the pop up dialog that appears
DO NOT EDIT/CHANGE ANYTHING, just look!
scroll down and report all the lines that start with both "ro.build. ..." and "ro.product. ..."
I would bet you have a slightly different Google-employee-only test build...
---------- Post added at 09:03 AM ---------- Previous post was at 09:02 AM ----------
slackwaresupport said:
can you pull the apk and post up here please
Click to expand...
Click to collapse
yes, or this!
Or, ChristianPeso, can you download "Barcode Scanner" from the market, and generate a market link to the app via QR code? and upload the QR code image here?
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Verizon 4g lte GN. Does this not come with new phones?
christianpeso said:
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Verizon 4g lte GN. Does this not come with new phones?
Click to expand...
Click to collapse
Thanks, and no. This is potentially awesome news
s.m.knipe said:
thanks, and no. This is potentially awesome news
Click to expand...
Click to collapse
pull this apk!!!
My build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ICL53F
ro.build.display.id=ICL53F
ro.build.version.incremental=235179
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.2
ro.build.date=Thu Dec 8 01:28:56 UTC 2011
ro.build.date.utc=1323307736
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpbs6.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.product.name=mysid
ro.product.device=toro
ro.product.board=tuna
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=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=toro
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=mysid-user 4.0.2 ICL53F 235179 release-keys
ro.build.fingerprint=google/mysid/toro:4.0.2/ICL53F/235179:user/release-keys
ro.build.characteristics=nosdcard
# end build properties
#
# system.prop for toro
#
rild.libpath=/vendor/lib/libsec-ril_lte.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=1
# Ril sends only one RIL_UNSOL_CALL_RING, so set call_ring.multiple to false
ro.telephony.call_ring.multiple=0
# Turn on IMS by default
persist.radio.imsregrequired=1
persist.radio.imsallowmtsms=1
# Default ecclist
ro.ril.ecclist=112,911,#911,*911
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.clientidbase=android-verizon
ro.com.google.locationfeatures=1
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.setupwizard.mode=OPTIONAL
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.gsm.data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.gsm.2nd_data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.config.vc_call_vol_steps=7
ro.cdma.otaspnumschema=SELC,1,80,99
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.config.ringtone=Girtab.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
drm.service.enabled=true
camera.flash_off=0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
i dont see any real differences from yours to mine.
I have no idea then. Waiting for someone else with GN Verizon LTE running 4.0.2 to chime in with they got it or not.
I don't have it, nor can I locate it in the market, must be hidden. And mine's totally stock, got it yesterday at 9 AM.
this is mine.
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ICL53F
ro.build.display.id=Android Revolution HD 2.1.0 LTE by mike1986
ro.build.version.incremental=235179
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.2
ro.build.date=Thu Dec 8 01:28:56 UTC 2011
ro.build.date.utc=1323307736
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpbs6.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.product.name=mysid
ro.product.device=toro
ro.product.board=tuna
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=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=toro
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=mysid-user 4.0.2 ICL53F 235179 release-keys
ro.build.fingerprint=google/mysid/toro:4.0.2/ICL53F/235179:user/release-keys
ro.build.characteristics=nosdcard
# end build properties
#
# system.prop for toro
#
rild.libpath=/vendor/lib/libsec-ril_lte.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=1
# Ril sends only one RIL_UNSOL_CALL_RING, so set call_ring.multiple to false
ro.telephony.call_ring.multiple=0
# Turn on IMS by default
persist.radio.imsregrequired=1
persist.radio.imsallowmtsms=1
# Default ecclist
ro.ril.ecclist=112,911,#911,*911
#
# ADDITIONAL_BUILD_PROPERTIES
# BUILD.PROP_MODIFIED_BY_MIKE1986_FOR_ANDROID_REVOLUTION_HD
ro.com.google.clientidbase=android-verizon
ro.com.google.locationfeatures=1
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.setupwizard.mode=OPTIONAL
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.gsm.data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.gsm.2nd_data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.cdma.otaspnumschema=SELC,1,80,99
wifi.interface=wlan0
wifi.supplicant_scan_interval=120
ro.opengles.version=131072
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.config.ringtone=Girtab.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
drm.service.enabled=true
camera.flash_off=0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# Additional build.prop tweaks for Android Revolution HD
# Tweaks identyfication code
ro.ident=Android_Revolution_HD
# Disable debugging notify icon on statusbar
persist.adb.notify=0
ro.config.vc_call_vol_steps=100
Well damn, dont I feel lucky. Gonna wipe everything and restart again to see if I can get it to work. Will take some video if I do.
christianpeso said:
I have no idea then. Waiting for someone else with GN Verizon LTE running 4.0.2 to chime in with they got it or not.
Click to expand...
Click to collapse
*raises hand*
I got the 4.0.2 update yesterday. I didn't get Google Wallet.
christianpeso said:
Honestly, I dont know how I got it. I thought it came with it. And I never had Wallet before on any ANdroid phone so it wasn't syncing it from prior. Was just going thru my apps list and it was there. Even after all this, I then unlocked my bootloader and that reset everything. Google wallet was still there and there was that update in the market. Going back to work today. Will probably lock and unlock again and try Wallet again to see if it works before updating it.
I am not rooted.
Click to expand...
Click to collapse
can you go to app manager to see if you can uninstall the update?
usually available to stock applications.
rashad1 said:
Please post proof, I'm using a non rooted stock GSM NS and I don't see it in the market.
Click to expand...
Click to collapse
yes - how do we GLOBAL GSM users get google wallet?
its a bit ridiculous that i upgraded from Nexus S to Galaxy Nexus but LOSE a functionality!!!!
pull the apk first with adb!!!
Hey
Basically alot of apps in the market do not show up in the market because they are not compatible with the galaxy y. An example is scramble with firends" which doesnt show up in the market however i downloaded it and it worked on my phone but first i had to change the resolution from the default 120 to 100 using an app (my phone is rooted but i still have stock rom). Now i was wondering whether if i could clear the cache and data for the market.apk while my phone was set to 100dpi then would the market show all the apps that are not compatible with my phone because of the dpi? However the only problem is i can not find the market.apk in the list of all my apps??? I was wondering how do i get it to appear on the galaxy y like it does on other android phones/tablets???
Please help with this?
you need to edit your build.prop,
this is very risky but will detect your phone as another device and not SGY
example of build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=MerrukUltimateRom BETA
ro.build.version.incremental=DXKL2
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Mon 16 Jan 19:22:01 KST 2011
ro.build.date.utc=1323944521
ro.build.tags=release-keys
ro.product.model=GT-S5360 <----change here
ro.product.brand=samsung
ro.product.name=GT-S5360 <----change here
ro.product.device=GT-S5360 <----change here
ro.product.board=totoro
ro.product.cpu.abi=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=bcm21553
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-S5360 <----change here
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-S5360<----change here-user 2.3.6 GINGERBREAD DXKL2 release-keys
ro.build.fingerprint=samsung/GT-S5360/GT-S5360:2.3.6/GINGERBREAD/DXKL2:user/release-keys
# Samsung Specific Properties
ro.build.PDA=S5360DXKL2
ro.build.hidden_ver=S5360DXKL2
ro.build.changelist=0000
ro.build.buildtag=
# end build properties
#
# system.prop for GT-S5360<----change here
#
# SEC_USE_SIPC : if SEC_USE_SIPC is on, enable libsec-ril.so and block libbrcm_ril.so
#rild.libpath=/system/lib/libsec-ril.so
rild.libpath=/system/lib/libbrcm_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=
DEVICE_PROVISIONED=1
#debug.sf.hw=1
debug.composition.type=mdp
dalvik.vm.heapsize=64m
ro.sf.lcd_density=120
#media.stagefright.enable-player=false
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
ro.media.enc.hprof.file.format=3gp
ro.media.enc.lprof.file.format=3gp
ro.media.enc.hprof.codec.vid=m4v
ro.media.enc.lprof.codec.vid=h263
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.lprof.codec.aud=amrnb
ro.media.enc.hprof.vid.width=352
ro.media.enc.lprof.vid.width=176
ro.media.enc.hprof.vid.height=288
ro.media.enc.lprof.vid.height=144
ro.media.enc.hprof.vid.fps=30
ro.media.enc.lprof.vid.fps=30
ro.media.enc.hprof.vid.bps=384000
ro.media.enc.lprof.vid.bps=192000
ro.media.enc.hprof.aud.bps=23450
ro.media.enc.lprof.aud.bps=23450
ro.media.enc.hprof.aud.ch=1
ro.media.enc.lprof.aud.ch=1
ro.media.enc.hprof.aud.hz=8000
ro.media.enc.lprof.aud.hz=8000
ro.media.cam.preview.fps=15
dalvik.vm.jniopts=warnonly
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/GT-S5360.xml<----change here
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase=android-samsung
ro.com.google.gmsversion=2.3_r8
ro.config.notification_sound=13_Whistle_Default_message.ogg
ro.config.alarm_alert=1_Good_Morning.ogg
alsa.mixer.playback.master=Speaker
alsa.mixer.capture.master=Mic
alsa.mixer.playback.earpiece=Earpiece
alsa.mixer.capture.earpiece=Mic
alsa.mixer.playback.headset=Headset
alsa.mixer.capture.headset=Mic
alsa.mixer.playback.speaker=Speaker
alsa.mixer.capture.speaker=Mic
alsa.mixer.playback.bt.sco=BTHeadset
alsa.mixer.capture.bt.sco=BTHeadset
alsa.mixer.playback.bt.a2dp=BTHeadset
alsa.mixer.capture.bt.a2dp=BTHeadset
dev.sfbootcomplete=0
keyguard.no_require_sim=true
ro.config.ringtone=Over_the_horizon_Default_ringtone.ogg
ro.config.notification_sound=13_Whistle_Default_message.ogg
ro.config.alarm_alert=Alarm_Buzzer.ogg
ro.opengles.version=131072
ro.com.google.clientidbase=android-samsung
+=wifi.interface=wl0.1
ro.error.receiver.default=com.samsung.receiver.error
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
Thanks
But are you sure i don't need to clear the data of the market.apk first since i saw a thread which is similar to what you told me above but it says to clear market.apk data but i cant find this market.apk. instead does it mean the google play.apk???
its risky so ill make a backup of the build.prop but should i also make a nandroid backup? the only problem is i cant make a nandroid backup via the recovery mode?
rezler said:
Thanks
But are you sure i don't need to clear the data of the market.apk first since i saw a thread which is similar to what you told me above but it says to clear market.apk data but i cant find this market.apk. instead does it mean the google play.apk???
its risky so ill make a backup of the build.prop but should i also make a nandroid backup? the only problem is i cant make a nandroid backup via the recovery mode?
Click to expand...
Click to collapse
stock recovery does not have a back up feature
try cwm recovery instead
deathnotice01 said:
you need to edit your build.prop,
this is very risky but will detect your phone as another device and not SGY
[/size]
Click to expand...
Click to collapse
I tried it just now by replacing all the"GT-S5360" with "GT-I9100" but it didn't work. What should i change it to? please reply
rezler said:
I tried it just now by replacing all the"GT-S5360" with "GT-I9100" but it didn't work. A also cleared the data and cache in the google play??? Why hasn't this worked? Was i meant to replace it all with something else?
Click to expand...
Click to collapse
You can replace them by writing 'Nexus S' too...
Sent from heaven!
Hey2
What's build.prop for xperia QVGA types?
Sorry for my bad english
Sent from my Desire HD using xda premium
hmmm it still wont work, the apps are still not showing up. Can someone plz provided a edited build.prop file that should work plz or just provide the edited lines?
thanks
You can use chainfire 3d and fix market setting. Demolition inc THD will show up but not work on me
Sent from my Desire HD using xda premium
Use blackmarket and apktop to download apps
Sent from my GT-S5360 using XDA
http://codekiem.com/apk-downloader
try this one.
Now, i wonder if we can use the build prompts from the sprint note 2 on our att phone no more galaxy nexus build prompts.
http://www.androidguys.com/2013/05/...ort/?utm_medium=referral&utm_source=pulsenews
With ISIS being an epic fail, I can't believe that ATT has not done this yet.
Lets hope our great devs can find some value in the code, and hopefully hook us up.....g
Ok well my buddy just change his build prob to the sprint values and his wallet is working
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Andrew149 said:
Ok well my buddy just change his build prob to the sprint values and his wallet is working
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Wow could it be that simple???
Andrew149 said:
Ok well my buddy just change his build prob to the sprint values and his wallet is working
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Well.. your buddy is one lucky one.
I tried and it does not work.. it stops at "Device set up failed".
Funny thing is when I was checking my wallet from wallet.google.com, my phone was registered as Galaxy Nexus. My wallet was working once using Galaxy Nexus build prop to set up.
So mine was working with the galaxy nexus settings, I ran the script to revert it to the stock SkyNote values (SkyNote google wallet finalize). At this point google wallet does not open. I then replaced the 5 places that say t0lteatt with t0ltespr, reboot (you have to reboot for build.prop changes) and it works. Still says unsupported device but opens and appears functional. I didn't try gwallet before this update happened
Here is my build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id= JZO54K
ro.build.display.id=SkyNote 8
ro.build.version.incremental=I317UCAMA4
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Fri Jan 18 11:30:14 KST 2013
ro.build.date.utc=1358476214
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-80
ro.build.tags=release-keys
ro.product.model=SAMSUNG-SGH-I317
ro.product.brand=samsung
ro.product.name=
t0ltespr
ro.product.device=t0ltespr
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product= t0ltespr
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=t0ltespr-user 4.1.2 JZO54K I317UCAMA4 release-keys
ro.build.fingerprint=samsung/t0ltespr/t0ltespr:4.1.2/ JZO54K /I317UCAMA4:user/release-keys
ro.build.characteristics=att
# Samsung Specific Properties
ro.build.PDA=I317UCAMA4
ro.build.hidden_ver=I317UCAMA4
ro.build.changelist=578342
# end build properties
#
# system.prop for smdk4x12
#
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=320
ro.lcd_min_brightness=15
ro.kernel.qemu=0
ro.tvout.enable=true
persist.sys.storage_preload=1
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/
# Multimedia property for Smart View
media.enable-commonsource=true
# System property ril adb log on
persist.radio.adb_log_on=1
# System property for SIM
persist.radio.apm_sim_not_pwdn=1
# System property for Default touch key light duration
ro.button_key_light=6000
# System proverty for sys info indication
persist.radio.add_power_save=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
debug.hwui.render_dirty_regions=false
ro.sf.lcd_density=320
ro.error.receiver.default=com.samsung.receiver.error
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.hdcp2.rx=tz
ro.secwvk=220
ro.sec.fle.encryption=true
ro.config.ringtone=Dance_alone.ogg
ro.config.notification_sound=Fluorine.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.monkey=0
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=DISABLED
ro.com.google.apphider=off
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.1_r3
dalvik.vm.dexopt-flags=m=y,v=n,o=v,u=n
dalvik.vm.execution-mode=int:jit
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.HOME_APP_ADJ=1
ro.HOME_APP_MEM=7095
ro.HOME_APP_BROWSER_ADJ=1
ro.min.fling_velocity=7000
ro.max.fling_velocity=12000
ro.secure=0
ro.debuggable=1
ro.mot.proximity.delay=0
ro.lge.proximity.delay=0
ro.service.swiqi.supported=false
debug.performance.tuning=1
video.accelerate.hw=1
ro.ril.disable.power.collapse=1
ro.hdmi.enable=true
persist.adb.notify=0
persist.service.adb.enable=1
persist.service.mount.playsnd=0
persist.service.swiqi.enable=0
persist.sys.purgeable_assets=0
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
pm.sleep_mode=1
windowsmgr.max_events_per_sec=1200
wifi.supplicant_scan_interval=180
lpa.decode=true
lpa.use-stagefright=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
APP_SWITCH_DELAY_TIME=false
PROC_START_TIMEOUT=false
ro.media.enc.hprof.vid.bps=12000000
ro.media.enc.hprof.vid.bps=12000000
ro.media.enc.hprof.aud.bps=12000000
ro.media.enc.hprof.codec.vid=12000000
ro.media.enc.hprof.codec.aud=12000000
ro.media.enc.hprof.aud.hz=12000000
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.wma.enabled=1
ro.media.dec.aud.flac.enabled=1
ro.media.dec.vid.avi.enabled=1
persist.sys.shutdown.mode=hibernate
ro.ril.disable.fastdormancy=1
ro.ril.enable.amr.wideband=1
ro.telephony.call_ring.delay=0
ro.facelock.black_timeout=400
ro.facelock.det_timeout=1500
ro.facelock.rec_timeout=2500
ro.facelock.lively_timeout=2500
ro.facelock.est_max_time=600
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
ro.semc.enhance.supported=true
persist.service.enhance.enable=1
ro.semc.clearaudio.supported=true
persist.service.clearaudio.enable=1
ro.sony.walkman.logger=1
persist.service.clearphase.enable=1
ro.somc.clearphase.supported=true
persist.af.resampler.quality=255
htc.audio.swalt.enable=1
htc.audio.swalt.mingain=14512
af.resampler.quality=255
debug.kill_allocating_task=0
dev.pm.dyn_samplingrate=1
ENFORCE_PROCESS_LIMIT=false
ro.wmt.blcr.enable=0
ro.ril.sensor.sleep.control=1
usb_wakeup=enable
dev.bootcomplete=0
ro.config.hw_fast_dormancy=1
ro.config.hw_power_saving=true
ro.media.enc.hprof.vid.fps=75
ro.mot.buttonlight.timeout=1
ro.config.hw_quickpoweron=true
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
I want my Wallet back... Dang it Google....
Interesting..
Anyways, a guy in Sprint Note 2 called the google, and found out they are still working to have wallet working on Sprint Note too..
So, I guess we could wait a while and see if switching build.prop to Sprint works flawlessly or not.
http://forum.xda-developers.com/showpost.php?p=41491532&postcount=302
joeavery2 said:
So mine was working with the galaxy nexus settings, I ran the script to revert it to the stock SkyNote values (SkyNote google wallet finalize). At this point google wallet does not open. I then replaced the 5 places that say t0lteatt with t0ltespr, reboot (you have to reboot for build.prop changes) and it works. Still says unsupported device but opens and appears functional. I didn't try gwallet before this update happened
Here is my build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id= JZO54K
ro.build.display.id=SkyNote 8
ro.build.version.incremental=I317UCAMA4
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Fri Jan 18 11:30:14 KST 2013
ro.build.date.utc=1358476214
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-80
ro.build.tags=release-keys
ro.product.model=SAMSUNG-SGH-I317
ro.product.brand=samsung
ro.product.name=
t0ltespr
ro.product.device=t0ltespr
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product= t0ltespr
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=t0ltespr-user 4.1.2 JZO54K I317UCAMA4 release-keys
ro.build.fingerprint=samsung/t0ltespr/t0ltespr:4.1.2/ JZO54K /I317UCAMA4:user/release-keys
ro.build.characteristics=att
# Samsung Specific Properties
ro.build.PDA=I317UCAMA4
ro.build.hidden_ver=I317UCAMA4
ro.build.changelist=578342
# end build properties
#
# system.prop for smdk4x12
#
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=320
ro.lcd_min_brightness=15
ro.kernel.qemu=0
ro.tvout.enable=true
persist.sys.storage_preload=1
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/
# Multimedia property for Smart View
media.enable-commonsource=true
# System property ril adb log on
persist.radio.adb_log_on=1
# System property for SIM
persist.radio.apm_sim_not_pwdn=1
# System property for Default touch key light duration
ro.button_key_light=6000
# System proverty for sys info indication
persist.radio.add_power_save=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
debug.hwui.render_dirty_regions=false
ro.sf.lcd_density=320
ro.error.receiver.default=com.samsung.receiver.error
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.hdcp2.rx=tz
ro.secwvk=220
ro.sec.fle.encryption=true
ro.config.ringtone=Dance_alone.ogg
ro.config.notification_sound=Fluorine.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.monkey=0
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=DISABLED
ro.com.google.apphider=off
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.1_r3
dalvik.vm.dexopt-flags=m=y,v=n,o=v,u=n
dalvik.vm.execution-mode=int:jit
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.HOME_APP_ADJ=1
ro.HOME_APP_MEM=7095
ro.HOME_APP_BROWSER_ADJ=1
ro.min.fling_velocity=7000
ro.max.fling_velocity=12000
ro.secure=0
ro.debuggable=1
ro.mot.proximity.delay=0
ro.lge.proximity.delay=0
ro.service.swiqi.supported=false
debug.performance.tuning=1
video.accelerate.hw=1
ro.ril.disable.power.collapse=1
ro.hdmi.enable=true
persist.adb.notify=0
persist.service.adb.enable=1
persist.service.mount.playsnd=0
persist.service.swiqi.enable=0
persist.sys.purgeable_assets=0
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
pm.sleep_mode=1
windowsmgr.max_events_per_sec=1200
wifi.supplicant_scan_interval=180
lpa.decode=true
lpa.use-stagefright=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
APP_SWITCH_DELAY_TIME=false
PROC_START_TIMEOUT=false
ro.media.enc.hprof.vid.bps=12000000
ro.media.enc.hprof.vid.bps=12000000
ro.media.enc.hprof.aud.bps=12000000
ro.media.enc.hprof.codec.vid=12000000
ro.media.enc.hprof.codec.aud=12000000
ro.media.enc.hprof.aud.hz=12000000
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.wma.enabled=1
ro.media.dec.aud.flac.enabled=1
ro.media.dec.vid.avi.enabled=1
persist.sys.shutdown.mode=hibernate
ro.ril.disable.fastdormancy=1
ro.ril.enable.amr.wideband=1
ro.telephony.call_ring.delay=0
ro.facelock.black_timeout=400
ro.facelock.det_timeout=1500
ro.facelock.rec_timeout=2500
ro.facelock.lively_timeout=2500
ro.facelock.est_max_time=600
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
ro.semc.enhance.supported=true
persist.service.enhance.enable=1
ro.semc.clearaudio.supported=true
persist.service.clearaudio.enable=1
ro.sony.walkman.logger=1
persist.service.clearphase.enable=1
ro.somc.clearphase.supported=true
persist.af.resampler.quality=255
htc.audio.swalt.enable=1
htc.audio.swalt.mingain=14512
af.resampler.quality=255
debug.kill_allocating_task=0
dev.pm.dyn_samplingrate=1
ENFORCE_PROCESS_LIMIT=false
ro.wmt.blcr.enable=0
ro.ril.sensor.sleep.control=1
usb_wakeup=enable
dev.bootcomplete=0
ro.config.hw_fast_dormancy=1
ro.config.hw_power_saving=true
ro.media.enc.hprof.vid.fps=75
ro.mot.buttonlight.timeout=1
ro.config.hw_quickpoweron=true
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
I'll add that doing just the first three didn't work. It could be only the fingerprint or description that needs to be changed.
I'll try to minimize the change then build a zip.
What I don't know atm is if you need to do any steps as you would have needed to previously or if just telling play store and google wallet that it's a sprint phone is enough.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
I was able to download Wallet from Play Store after changing build.prop to match Sprint Note 2... even with only those 4 lines.
Problem is I keep getting "Device set up failed" message..
joeavery2 said:
I'll add that doing just the first three didn't work. It could be only the fingerprint or description that needs to be changed.
I'll try to minimize the change then build a zip.
What I don't know atm is if you need to do any steps as you would have needed to previously or if just telling play store and google wallet that it's a sprint phone is enough.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
So, I changed the first three, tried a few different ways, each change I rebooted and confirmed that Google wallet would not launch. I'm posting the relevent part of the build.prop, Make sure you change all the items in RED :
Code:
ro.product.name=[COLOR="Red"]t0ltespr[/COLOR]
ro.product.device=[COLOR="red"]t0ltespr[/COLOR]
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=[COLOR="red"] t0ltespr[/COLOR]
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=[COLOR="red"]t0ltespr[/COLOR]-user 4.1.2 JZO54K I317UCAMA4 release-keys
ro.build.fingerprint=samsung/[COLOR="red"]t0ltespr/t0ltespr[/COLOR]:4.1.2/ JZO54K /I317UCAMA4:user/release-keys
I tried building a Zip from it but it failed and I don't have time to mess with it ATM.
---------- Post added at 12:28 PM ---------- Previous post was at 11:41 AM ----------
Ok I removed Google wallet via the Wallet app delete from device, I then used the skynote done with wallet revert zip. I rebooted. With Build.prop still showing as a sprint device I was able to download the app, however it would not initialize, it hung. So instead I ran the SkyNote_google_wallet_step1 zip. Initialized Google wallet, Then installed the Sprint edited version of Build.prop. The last step is equivalent to what happens with the SkyNote_google_wallet_finalize.zip which only adjust the build.prop back to ATT Note from Galaxy nexus.
Basically the second step is all that changes, instead of using the finalize zip to set the build.prop to att, we need to set it to sprint. Since I currently can't get the zip to work, your stuck editing the build.prop on your own, unless someone else can manage to copy/paste it, just replace the one in the SkyNote_google_wallet_finalize.zip under system with a windows machine and try installing it.
Key thing to note. If you can get google wallet to initialize after the first step, let it finish and you'll get a notification that "google wallet is ready to use" At this point you could just leave the phone as is. The issue is that S-Pen apps won't work, as they check to see that the phone is a Note vs a Nexus. If you can't get this part to work then you have something else going on, like you un-installed google wallet incorrectly and it's locked up now. You may try the google wallet revert zip from skynote thread. It seems to me that the issue is that google wallet creates a bunch of files on the device needed to make things work properly. If they are not all deleted (un-installing the app or apk doesn't do this) then it will cause issues.
Anyway, I was able to uninstall everything, start from scratch and install it all again. I currently have the build.prop mod'd to be a sprint Note2 T0ltespr and Both Google Wallet and S-pen apps work.
Hopefully this is helpful!
joeavery2 said:
So, I changed the first three, tried a few different ways, each change I rebooted and confirmed that Google wallet would not launch. I'm posting the relevent part of the build.prop, Make sure you change all the items in RED :
Code:
ro.product.name=[COLOR="Red"]t0ltespr[/COLOR]
ro.product.device=[COLOR="red"]t0ltespr[/COLOR]
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=[COLOR="red"] t0ltespr[/COLOR]
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=[COLOR="red"]t0ltespr[/COLOR]-user 4.1.2 JZO54K I317UCAMA4 release-keys
ro.build.fingerprint=samsung/[COLOR="red"]t0ltespr/t0ltespr[/COLOR]:4.1.2/ JZO54K /I317UCAMA4:user/release-keys
I tried building a Zip from it but it failed and I don't have time to mess with it ATM.
---------- Post added at 12:28 PM ---------- Previous post was at 11:41 AM ----------
Ok I removed Google wallet via the Wallet app delete from device, I then used the skynote done with wallet revert zip. I rebooted. With Build.prop still showing as a sprint device I was able to download the app, however it would not initialize, it hung. So instead I ran the SkyNote_google_wallet_step1 zip. Initialized Google wallet, Then installed the Sprint edited version of Build.prop. The last step is equivalent to what happens with the SkyNote_google_wallet_finalize.zip which only adjust the build.prop back to ATT Note from Galaxy nexus.
Basically the second step is all that changes, instead of using the finalize zip to set the build.prop to att, we need to set it to sprint. Since I currently can't get the zip to work, your stuck editing the build.prop on your own, unless someone else can manage to copy/paste it, just replace the one in the SkyNote_google_wallet_finalize.zip under system with a windows machine and try installing it.
Key thing to note. If you can get google wallet to initialize after the first step, let it finish and you'll get a notification that "google wallet is ready to use" At this point you could just leave the phone as is. The issue is that S-Pen apps won't work, as they check to see that the phone is a Note vs a Nexus. If you can't get this part to work then you have something else going on, like you un-installed google wallet incorrectly and it's locked up now. You may try the google wallet revert zip from skynote thread. It seems to me that the issue is that google wallet creates a bunch of files on the device needed to make things work properly. If they are not all deleted (un-installing the app or apk doesn't do this) then it will cause issues.
Anyway, I was able to uninstall everything, start from scratch and install it all again. I currently have the build.prop mod'd to be a sprint Note2 T0ltespr and Both Google Wallet and S-pen apps work.
Hopefully this is helpful!
Click to expand...
Click to collapse
can u give a step by step to how make google wallet work on att note 2 , with all the file u need or install
Root your phone problem solved
Sent from my SAMSUNG-SGH-I317 using xda premium
joeavery2 said:
So, I changed the first three, tried a few different ways, each change I rebooted and confirmed that Google wallet would not launch. I'm posting the relevent part of the build.prop, Make sure you change all the items in RED :
Code:
ro.product.name=[COLOR="Red"]t0ltespr[/COLOR]
ro.product.device=[COLOR="red"]t0ltespr[/COLOR]
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=[COLOR="red"] t0ltespr[/COLOR]
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=[COLOR="red"]t0ltespr[/COLOR]-user 4.1.2 JZO54K I317UCAMA4 release-keys
ro.build.fingerprint=samsung/[COLOR="red"]t0ltespr/t0ltespr[/COLOR]:4.1.2/ JZO54K /I317UCAMA4:user/release-keys
I tried building a Zip from it but it failed and I don't have time to mess with it ATM.
---------- Post added at 12:28 PM ---------- Previous post was at 11:41 AM ----------
Ok I removed Google wallet via the Wallet app delete from device, I then used the skynote done with wallet revert zip. I rebooted. With Build.prop still showing as a sprint device I was able to download the app, however it would not initialize, it hung. So instead I ran the SkyNote_google_wallet_step1 zip. Initialized Google wallet, Then installed the Sprint edited version of Build.prop. The last step is equivalent to what happens with the SkyNote_google_wallet_finalize.zip which only adjust the build.prop back to ATT Note from Galaxy nexus.
Basically the second step is all that changes, instead of using the finalize zip to set the build.prop to att, we need to set it to sprint. Since I currently can't get the zip to work, your stuck editing the build.prop on your own, unless someone else can manage to copy/paste it, just replace the one in the SkyNote_google_wallet_finalize.zip under system with a windows machine and try installing it.
Key thing to note. If you can get google wallet to initialize after the first step, let it finish and you'll get a notification that "google wallet is ready to use" At this point you could just leave the phone as is. The issue is that S-Pen apps won't work, as they check to see that the phone is a Note vs a Nexus. If you can't get this part to work then you have something else going on, like you un-installed google wallet incorrectly and it's locked up now. You may try the google wallet revert zip from skynote thread. It seems to me that the issue is that google wallet creates a bunch of files on the device needed to make things work properly. If they are not all deleted (un-installing the app or apk doesn't do this) then it will cause issues.
Anyway, I was able to uninstall everything, start from scratch and install it all again. I currently have the build.prop mod'd to be a sprint Note2 T0ltespr and Both Google Wallet and S-pen apps work.
Hopefully this is helpful!
Click to expand...
Click to collapse
So you only had to change the text in red and now it's working? I have no problem editing the buildprop, I'm just unclear if there are any other lines that need to be edited.
---------- Post added at 07:27 AM ---------- Previous post was at 07:19 AM ----------
I changed all of the items in red, but when opening wallet I get an"insufficient secure element privelages for this system image (release keys)." message.
yongh said:
can u give a step by step to how make google wallet work on att note 2 , with all the file u need or install
Click to expand...
Click to collapse
Assuming you haven't had gWallet running on this device before, or you are coming from a clean install: All you need are the two files from the skynote thread, and follow his instructions (It's near the bottom on that post). Then using root explore or the like, Change the items of the build.prop that are in RED. After changing the build.prop you have to reboot for settings to take effect.
nosmohtac said:
So you only had to change the text in red and now it's working? I have no problem editing the buildprop, I'm just unclear if there are any other lines that need to be edited.
---------- Post added at 07:27 AM ---------- Previous post was at 07:19 AM ----------
I changed all of the items in red, but when opening wallet I get an"insufficient secure element privelages for this system image (release keys)." message.
Click to expand...
Click to collapse
I only changed the ones I've marked in red. I found this that may help you on the secure elements thing. Basically, from what I can tell, is you didn't reset, or didn't get a chance to reset your existing google wallet on the phone. If you use the third zip from the skynote rom thread posted above you can (should be able to) reset everything. Then start with the first step.
joeavery2 said:
So, I changed the first three, tried a few different ways, each change I rebooted and confirmed that Google wallet would not launch. I'm posting the relevent part of the build.prop, Make sure you change all the items in RED :
Code:
ro.product.name=[COLOR="Red"]t0ltespr[/COLOR]
ro.product.device=[COLOR="red"]t0ltespr[/COLOR]
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=[COLOR="red"] t0ltespr[/COLOR]
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=[COLOR="red"]t0ltespr[/COLOR]-user 4.1.2 JZO54K I317UCAMA4 release-keys
ro.build.fingerprint=samsung/[COLOR="red"]t0ltespr/t0ltespr[/COLOR]:4.1.2/ JZO54K /I317UCAMA4:user/release-keys
I tried building a Zip from it but it failed and I don't have time to mess with it ATM.
---------- Post added at 12:28 PM ---------- Previous post was at 11:41 AM ----------
Ok I removed Google wallet via the Wallet app delete from device, I then used the skynote done with wallet revert zip. I rebooted. With Build.prop still showing as a sprint device I was able to download the app, however it would not initialize, it hung. So instead I ran the SkyNote_google_wallet_step1 zip. Initialized Google wallet, Then installed the Sprint edited version of Build.prop. The last step is equivalent to what happens with the SkyNote_google_wallet_finalize.zip which only adjust the build.prop back to ATT Note from Galaxy nexus.
Basically the second step is all that changes, instead of using the finalize zip to set the build.prop to att, we need to set it to sprint. Since I currently can't get the zip to work, your stuck editing the build.prop on your own, unless someone else can manage to copy/paste it, just replace the one in the SkyNote_google_wallet_finalize.zip under system with a windows machine and try installing it.
Key thing to note. If you can get google wallet to initialize after the first step, let it finish and you'll get a notification that "google wallet is ready to use" At this point you could just leave the phone as is. The issue is that S-Pen apps won't work, as they check to see that the phone is a Note vs a Nexus. If you can't get this part to work then you have something else going on, like you un-installed google wallet incorrectly and it's locked up now. You may try the google wallet revert zip from skynote thread. It seems to me that the issue is that google wallet creates a bunch of files on the device needed to make things work properly. If they are not all deleted (un-installing the app or apk doesn't do this) then it will cause issues.
Anyway, I was able to uninstall everything, start from scratch and install it all again. I currently have the build.prop mod'd to be a sprint Note2 T0ltespr and Both Google Wallet and S-pen apps work.
Hopefully this is helpful!
Click to expand...
Click to collapse
ok i try this step but still not work so im kind confuse
1. install step 1 flash and add sprint build prop then setup up wallet , but fail ,
2nd try flash remove wallet zip and try again still fail
so please tell me step by step
Ok so I got it working but it says unsupported device any one have any ideas.
jjr3211 said:
Ok so I got it working but it says unsupported device any one have any ideas.
Click to expand...
Click to collapse
Working means you actually were able to get pass "setting up payment method" screen and seeing already registered card and/or were able to add another credit card?
Unsupported Device means your phone is rooted..
Just use modaco tool kit to hide that..
dvdmkr said:
Working means you actually were able to get pass "setting up payment method" screen and seeing already registered card and/or were able to add another credit card?
Unsupported Device means your phone is rooted..
Just use modaco tool kit to hide that..
Click to expand...
Click to collapse
yes it is working as it should be. and not to sound really stupid where do I get the modaco tool kit from.
jjr3211 said:
yes it is working as it should be. and not to sound really stupid where do I get the modaco tool kit from.
Click to expand...
Click to collapse
Can someone tell all the detail to get wallet to work please
Sent from my SAMSUNG-SGH-I317 using xda premium
dvdmkr said:
Working means you actually were able to get pass "setting up payment method" screen and seeing already registered card and/or were able to add another credit card?
Unsupported Device means your phone is rooted..
Just use modaco tool kit to hide that..
Click to expand...
Click to collapse
Thanks got it all sorted out and working just got to try it out here in the next day or so. Thanks for your help.
i edited my build prop via root explorer to decrease screen ppi,,,
it worked ,, i set it to value 186 :cyclops:
but i didn't liked the change ,,,,,
so went 2 edit the value back 213... :angel:
something wrong happened after that
maybe i edited the value above it
and now after booting the samsung logo has been rotated to landscape
and it hangs out there.....................
if anyone do have same [Samsung Galaxy Note 8.0 GT-N5100]
please provide me the STOCK build.prop
from internal storage (root folder) /sytem .:good:
Did you have any luck getting a copy of the default build.prop file. Even if I could get a text copy to compare what mine is currently with what the default is I think it would help.
atifjay said:
i edited my build prop via root explorer to decrease screen ppi,,,
it worked ,, i set it to value 186 :cyclops:
but i didn't liked the change ,,,,,
so went 2 edit the value back 213... :angel:
something wrong happened after that
maybe i edited the value above it
and now after booting the samsung logo has been rotated to landscape
and it hangs out there.....................
if anyone do have same [Samsung Galaxy Note 8.0 GT-N5100]
please provide me the STOCK build.prop
from internal storage (root folder) /sytem .:good:
Click to expand...
Click to collapse
Here: https://drive.google.com/file/d/0B9QvmNs9dpD-Yl9mRUctVDA4Z28/edit?usp=sharing
Or:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=JDQ39.N5100UBCML3
ro.build.version.incremental=N5100UBCML3
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sat Dec 21 11:22:02 KST 2013
ro.build.date.utc=1387592522
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-131
ro.build.tags=release-keys
ro.product.model=GT-N5100
ro.product.brand=samsung
ro.product.name=kona3gub
ro.product.device=kona3g
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=kona3g
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=kona3gub-user 4.2.2 JDQ39 N5100UBCML3 release-keys
ro.build.fingerprint=samsung/kona3gub/kona3g:4.2.2/JDQ39/N5100UBCML3:user/release-keys
ro.build.characteristics=tablet
# Samsung Specific Properties
ro.build.PDA=N5100UBCML3
ro.build.hidden_ver=N5100UBCML3
ro.build.changelist=2321387
ro.product_ship=true
ro.chipname=smdk4x12
# end build properties
#
# system.prop for smdk4x12
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.hwrotation=270
ro.sf.lcd_density=213
ro.kernel.qemu=0
ro.tvout.enable=true
persist.sys.storage_preload=1
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/
# Multimedia property for Smart View
media.enable-commonsource=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heapmaxfree=8m
ro.opengles.version=131072
debug.hwui.render_dirty_regions=false
drm.service.enabled=true
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
ro.sf.lcd_density=320
ro.error.receiver.default=com.samsung.receiver.error
ro.hdcp2.rx=tz
ro.secwvk=220
ro.sec.fle.encryption=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.crypto.support=recovery_mount|others
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.com.google.gmsversion=4.2_r3
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Thanks, That info was a life saver for me. Somehow it appears the ro.sf.lcd_density=213 had been changed to 320 and put me into a Touchwiz failure loop.
nstocke said:
Thanks, That info was a life saver for me. Somehow it appears the ro.sf.lcd_density=213 had been changed to 320 and put me into a Touchwiz failure loop.
Click to expand...
Click to collapse
How can I correct the same issue? I have the original but how can I put it back on the device if it keeps crashing?
My device was rooted so I was able to boot into recovery mode. From there I used adb to pull the /system/build.prop file. I edited the build.prop file correcting the lines that needed to be edited. I was unable to push the file back to its original location so I pushed it to /tmp/build.prop . I then used adb to got to shell and then became su and then copied the file from /tmp/build.prop to /system/build.prop and then rebooted. The commands looked something like this:
From adb directory
adb pull /system/build.prop c:\build.prop
edited c:\build.prop
adb push c:\build.prop /tmp/build.prop
adb shell
su
cp /tmp/build.prop /system/build.prop
reboot
The above was written from memory so I hope I got it all correct.
Is recovery mode the one that has clear cache and wipe data on the menu?
---------- Post added at 10:31 PM ---------- Previous post was at 10:23 PM ----------
I got it!!!!!
Outstanding plus good memory recall
Thanks
Guys.....
I have been out from xda.........
4 a while......
But i fixed that issue in one week
Of run in January itself......
Sorry 4 the late update....!
I managed to get the odin flashable .tar
Rom package in correspondence........!....
Which has always been a life saviour 4 me....,,,,
If any bugs comes in development.....
And pros is that odin never...
Wiped me....
Just restored the system back to default (repairs.....)
Without loss of data.....
Working like an OTA update.......
@Tetraguy
Thanks......buddy ????
I buy this t999 on internet, the display was broken and the seller told me that the model was i747, when i change the display.
I restore with KIES, the phone was upgrade to 4.3
The matter was thah te imei and S/N in case is not the same that appear in settings, i discover this after install.
The cell power on correctly, the matter is thah don´t the wifi, bluetooth; the camera says CAMERA ERROR, i try to install another app to works the camera but nothing happends.
When KIES upgrade the phone to 4.3, the version is UVUENC2.
What can i do to camera, wifi and bluetooh works, i was reading that its posible that my cell is T999L but i not shure,
Cause says thath can flash a rom of T999 in a T999L, sometimes when flash roms, don´t works some functions like camera, wifi, buetooth as mi cell.
http://forum.xda-developers.com/showthread.php?t=2370981
Can you help me, i´m noob in this cell.
I make root and make a backup of IMEI and build.drop
This is the content of build.drop file:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JSS15J
ro.build.display.id=JSS15J.T999UVUENC2
ro.build.version.incremental=T999UVUENC2
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Sat Mar 8 19:58:03 KST 2014
ro.build.date.utc=1394276283
ro.build.type=user
ro.build.user=se.infra
ro.build.host=R0210-18
ro.build.tags=release-keys
ro.product.model=SGH-T999
ro.product.brand=samsung
ro.product.name=d2tmo
ro.product.device=d2tmo
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=d2tmo
# Do not try to parse ro.build.description or
.fingerprint
ro.build.description=d2tmo-user 4.3 JSS15J
T999UVUENC2 release-keys
ro.build.fingerprint=samsung/d2tmo/d2tmo:4.3/
JSS15J/T999UVUENC2:user/release-keys
ro.build.characteristics=tmo
# Samsung Specific Properties
ro.build.PDA=T999UVUENC2
ro.build.hidden_ver=T999UVUENC2
ro.build.changelist=1962493
ro.product_ship=true
ro.chipname=
# end build properties
#
# system.prop for surf
#
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
ro.hdmi.enable=true
lpa.decode=true
lpa.use-stagefright=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
#
# system props for the data modules
#
ro.use_data_netmgrd=true
#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
# 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 property for Default touch key light
duration
ro.button_key_light=1500
#
# 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
# Keep SIM state on LPM mode
persist.radio.apm_sim_not_pwdn=1
# System proverty for sys info indication
persist.radio.add_power_save=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
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.vendor.extension_library=/system/lib/libqc-
opt.so
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.hdcp2.rx=tz
ro.sec.fle.encryption=true
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.ringtone=CLEAN_Tmo_Jingle.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.error.receiver.default=com.samsung.receiver.err or
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.crypto.support=recovery_mount|others
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.apphider=off
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-hms-tmobile-us
ro.com.google.clientidbase.am=android-tmobile-us
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=4.3_r1
ro.build.selinux=1
ro.config.tima=1
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=0
persist.gps.qc_nlp_in_use=0
What can I do to make work mi wifi, bluetooth and camera.
Thansk a lot.
Sounds like another one of these.
http://forum.xda-developers.com/showthread.php?t=2672790
If you got UVUENC2 running on there either by kies or odin then at least the motherboard is a T999. Im wondering if maybe you got mixed components from whoever sold it to you.
Check the imei and sn against the sticker under the battery.
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
Sounds like another one of these.
http://forum.xda-developers.com/showthread.php?t=2672790
If you got UVUENC2 running on there either by kies or odin then at least the motherboard is a T999. Im wondering if maybe you got mixed components from whoever sold it to you.
Check the imei and sn against the sticker under the battery.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Thanks, exactly, i forgot coment, the IMEI and SN is not the same that the numbers that appears in Settings.
I discover this when i change the display, and kies flash until i wrote i747m and serial in Kies flash t-mobile rom.
Other thing that i forgot, when i flash the fhon in download mode, don appears the progress bar, in others models that i have always shows the progress at the same time in odin, and in this case only odin shows the progress.
Thanks
I would contact the seller for an explanation before going much further, especially regarding the imei.
DocHoliday77 said:
I would contact the seller for an explanation before going much further, especially regarding the imei.
Click to expand...
Click to collapse
I tried contact the seller but i don´t have any answer, for this i try to make work wifi, camera and bluetooh.
What else can I do?
PD; The phone is unlocked, and works to make and recive calls.
Find the thread in general that hss the dialer codes and use that to check the cameras firmware version. Then grab an ATT rom and see if there is a corresponding file in the cameradata folder and copy it to yours. (Or you could try just copying the whole folder to see if it works).
If that doesn't work, I'm not sure what else to tell you...
DocHoliday77 said:
Find the thread in general that hss the dialer codes and use that to check the cameras firmware version. Then grab an ATT rom and see if there is a corresponding file in the cameradata folder and copy it to yours. (Or you could try just copying the whole folder to see if it works).
If that doesn't work, I'm not sure what else to tell you...
Click to expand...
Click to collapse
I flahs drivers camera and doesn´t works, I root and flash recovery TWRP, i was reading that maybe need to flash a different kernel, the question is what kernel you recommend me to flash to try to work the hardware.
Thanks
Stock kernel is all I use. Kernel thread is in General section. All you can do is try a few and see.
You said you flashed the camera driver? What exactly did you fo and what did you flash? Did you use the dialer code to check the cam firmware version?
When in download mode does it show the model?
DocHoliday77 said:
Stock kernel is all I use. Kernel thread is in General section. All you can do is try a few and see.
You said you flashed the camera driver? What exactly did you fo and what did you flash? Did you use the dialer code to check the cam firmware version?
When in download mode does it show the model?
Click to expand...
Click to collapse
I used this code:
*#34971539# Camera Firmware Update
based on this thread
http://forum.xda-developers.com/galaxy-s3/general/jb-4-1-2-camera-driver-t2006128
Cause this was my case
Rear Camera ZDFE02
Phone FW ZDFI02
After flashing
Rear Camera ZDFE02
Phone FW ZDFE02
But doesn´t works
In /system/cameradata, do you see SlimISP_ZD.bin? Or something to that effect...
Rear camera is the firmware version currently being used by the camera. Phone FW is the firmware loaded on the phone along with the rom or device firmware. So initially, what was on the phone was newer (this is normal btw). We used to be able to write the newer fw from Phone to Cam ourselves, but Damsung patched against that in 4.1.2.
In other words, whst it says for phone and rear cam do not need to match. Just make suure you have that ZD file in the cameradata folder.
DocHoliday77 said:
In /system/cameradata, do you see SlimISP_ZD.bin? Or something to that effect...
Rear camera is the firmware version currently being used by the camera. Phone FW is the firmware loaded on the phone along with the rom or device firmware. So initially, what was on the phone was newer (this is normal btw). We used to be able to write the newer fw from Phone to Cam ourselves, but Damsung patched against that in 4.1.2.
In other words, whst it says for phone and rear cam do not need to match. Just make suure you have that ZD file in the cameradata folder.
Click to expand...
Click to collapse
The file that you say is in cameradata folder, i don´t lnow whats the matter, and why don´t work the camera, bluetooth, & wifi.
Thanks