Thanks to Designgears, there is a new leak for I777 ROM:
Odin One-Click downloader: http://rootzwiki.com/topic/11366-firmware-i777uckk6-galaxy-s-ii-att/
CWM Flashable i-777 UCKK6 modem extracted from this leak: http://www.multiupload.com/KA01Q9AHX2
System partition dump with Superuser embedded: http://www.victorlara.net/system.img.zip (thanks to vlara)
Code:
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.UCKK6
ro.build.version.incremental=UCKK6
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Tue Nov 29 19:49:45 KST 2011
ro.build.date.utc=1322563785
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-74
ro.build.tags=release-keys
ro.product.model=SAMSUNG-SGH-I777
ro.product.brand=samsung
ro.product.name=SGH-I777
ro.product.device=SGH-I777
ro.product.board=SGH-I777
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I777UCKK6
ro.build.hidden_ver=I777UCKK6
ro.build.changelist=770444
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=s5pc210
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I777
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I777-user 2.3.6 GINGERBREAD UCKK6 release-keys
ro.build.fingerprint=samsung/SGH-I777/SGH-I777:2.3.6/GINGERBREAD/UCKK6:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I777UCKK6
ro.build.hidden_ver=I777UCKK6
ro.build.changelist=770444
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
#
# 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=OPTIONAL
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.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.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=ATT_tone.ogg
ro.config.notification_sound=S_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.monkey=0
ro.opengles.version=131072
ro.error.receiver.default=com.samsung.receiver.error
ro.secdevenc=true
ro.wtldatapassword=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Anyone try it?
Sent from my GT-I9100 using xda premium
Ill give it a shot.
Noticed its an exe. How would you flash that?
I presume this will put in the new bootloader... This file is a one-click-odin archive that I'm not aware how to dissect onto separate pieces to get rid of bootloader, add root, etc.
NJGSII said:
Ill give it a shot.
Noticed its an exe. How would you flash that?
Click to expand...
Click to collapse
it's self-flashable, odin-like wrapper. Be warned that it may overwrite the bootloader to the newer version that is known to be jig-immune. However there was a post on how to revert it back.
558 megabytes!
So you put the phone into download and use odin to load it.
Correct?
^^ Yessir.
You can use mobileodin app to install it also. MobileOdin WILL NOT flash the bootloaders in case it has them.
Sent From My KickAss ATT SGS2 SPORTING CM7
Anyone try it out yet?
RockRatt said:
You can use mobileodin app to install it also. MobileOdin WILL NOT flash the bootloaders in case it has them.
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
So to use mobile Odin, I first dl this to computer, then put in root of SD? Run Odin app and let it do it's thing?
Sent from my SAMSUNG-SGH-I777 using XDA App
What's new in this update?
Sent from my SAMSUNG-SGH-I777 using XDA App
Qortez1 said:
What's new in this update?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
+1
Anyone who has flashed let us know if the sporadic wifi issue has been fixed from KK5.
Cdub5 said:
So to use mobile Odin, I first dl this to computer, then put in root of SD? Run Odin app and let it do it's thing?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Yes that will work. I just download it to my phone, open mobile Odin, choose the downloaded rom, flash away.
I have not had a chance to download it yet as I didn't go home from work yesterday and for the first time I am being throttled. So once it downloads on this slow ass Starbucks wireless I will let you know how it goes/feels. I am ONLY doing it so I can pull out the modem so I probably wont stay long.
Sent From My KickAss ATT SGS2 SPORTING CM7
I would like to know if this fixes the wifi not syncing problem...
Beware, this is probably infested with that thing called Carrier IQ...
Longcat14 said:
Beware, this is probably infested with that thing called Carrier IQ...
Click to expand...
Click to collapse
So that's the only thing that was updated. HMMMMM
*puts on tin foil hat*
Seriously though the 2.3.6 leak that I'm currently running doesn't have it.
NJGSII said:
So that's the only thing that was updated. HMMMMM
*puts on tin foil hat*
Seriously though the 2.3.6 leak that I'm currently running doesn't have it.
Click to expand...
Click to collapse
Wait, this leak doesn't have it?
Could've been stripped out... good thing though.
Longcat14 said:
Wait, this leak doesn't have it?
Could've been stripped out... good thing though.
Click to expand...
Click to collapse
No, I'm talk about the 2.3.6 leak that's here.
http://forum.xda-developers.com/showthread.php?t=1353513
Not sure about the one in this thread as I haven't got around to putting it on the phone yet.
Anyone that has actually installed would they be willing to pull the UCKK6 modem.bin from it?
In adb or terminal emulator, must be rooted:
Code:
dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
Related
Hello everyone,
I was using VeganTab as my ROM of choice for a long time, and recently switched to CyanogenMod7 for a change and a more traditional Android feel.
With VeganTab, I had no issues using the Market. Every app I wanted to download was available in the market. Using CyanogenMod7, when I go to download apps I get a "this application is not available for your device" message on several apps. Firefox being one of them, which the gTablet should be able to support.
Why would one ROM work and the other doesn't on the same device? Has anyone else encountered this and know how to fix it?
Hello, I have one Gtab running CM7 what version/build are you on? Which apps are not showing up other than Firefox? Have you modified anything (build.prop)? If I remember right I had to modify the build.prop to get some apps to show up.
The apps in the market are set up to show only to devices that they are designed to be run on. When you change roms, your device shows up differently to the Market, so some apps might appear that weren't there before and some may dissappear. Read through the thread where you got the rom from and you may find some tips. Also as a temp. solution you can download the .apk files for many apps either to your PC or the the tablet and "side load" it (go to file manager and tap the downloaded .apk to install). Open a root file explorer and go to /system and open build.prop. Let me know what is says for product board, region and lcd density.
Thanks for the quick response Dave.
So far, Agenda Widget and Firefox are the two I can't get through the market. I haven't tried a ton of others yet.
I've been playing with the bool.prop file a little bit, based on tutorials I've seen here and at other forums. This thread seems to offer the best advice, but didn't work for me.
Below are my build.prop values at current time:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GRI40
ro.build.display.id=GRI40
ro.build.version.incremental=eng.cyanogenmod.20110505.210139
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.3
ro.build.date=Thu May 5 21:02:03 CDT 2011
ro.build.date.utc=0
ro.build.type=user
ro.build.user=cyanogenmod
ro.build.host=scout73
ro.build.tags=test-keys
ro.product.model=GTablet
ro.product.brand=passion
#ro.product.brand=nvidia
ro.product.name=passion
#ro.product.name=harmony
ro.product.device=olympus
#ro.product.device=harmony
ro.product.board=harmony
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=malata
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=harmony
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=passion-user 2.3.3 GRI40 102588 release-keys
ro.build.fingerprint=nvidia/harmony/harmony/harmony:2.2/FRF91/20101123.172729:eng/test-keys
# end build properties
#
# system.prop for harmony
#
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
# Density set to 161 to allow market to function properly
ro.sf.lcd_density=161
wifi.interface = wlan0
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=32m
# For emmc phone storage
ro.phone_storage = 1
# Add external mount points
ro.additionalmounts=/mnt/emmc;/mnt/usbdisk
# Add reference RIL
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.setupwizard.enable_bypass=1
keyguard.no_require_sim=1
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.rommanager.developerid=cyanogenmod
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.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.0.3-Harmony
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Looks from your build.prop file that you are on an older build of CM7. The apps you mentioned, Firefox and Firefox Beta, and the Agenda Widget show up and work on mine. You could try using some of the values in my .prop file here, or update to a newer version of CM7. You might be able to install over your current build without wiping your data, but back up first of course.
Thanks Dave. Can you link me to a stable, updated version of CM7?
There is a CM7 rom hosted here at XDA:
CYANOGENMOD7.2.0-RC0-BUILD98-REPACK
Or you can go to Cyanogenmod Wiki. Don't forget to download the Gapps separately from the bottom of the same page and install them too.
I apologize in advance if it is not allowed to post a link to their wiki page .
Actually I have had this problem ALOT, no matter what version of CM7 I use on it. Its even worse when the new Market gets pushed to it, I usually have to downgrade it back and remove the MarketUpdater.apk so it stays on the old one.
I am running the ICS Alpha/Beta (forget which) right now so everything works, albeit very slow.
I had the same issue it's the odd LCD density of 161 that market doesn't like. I changed mine to 200 then do the standard market fix reboot and it should be fine.
Sent from my HTC Glacier using xda premium
WARNING:
For devs and experts ONLY!
This is not fully functional and it is not well tested yet!
I do not take responsibility for any damage you cause your player!
This is an unofficial port of CM9 alpha to the Galaxy Player 4.0 (USA).
Preparation
MAKE A FULL BACKUP! Make sure you can recover using heimdall or odin.
Backup /system using "dd" use with odin/heimdall, just in case:
dd if=/dev/block/stl9 of=/mnt/sdcard/system.img bs=512
Backup your apps if you care about them
Installation
Download the ROM for your device
Boot into recovery and install the ROM
Do a full wipe. Wipe data, cache, dalvik, everything
Reboot, and you should have cm9!
Issues?
Post any other issue here and I will respond when I get a chance.
Please do NOT send me PM's.
Download
http://www.mediafire.com/?wch69mtgwx4ssra
Note: gapps is not currently included in the ROM.
THIS IS STILL IN TESTING. PLEASE LEAVE A COMMENT TELLING ME HOW WELL IT WORKED.
When will international version be released?
thanks for your efforts
I dont have an international device so i cant release it.
Tcollins412 said:
I dont have an international device so i cant release it.
Click to expand...
Click to collapse
are you aware of what changes must be made to make it compatible with an international device? also i tried installing the usa version but clockworkmod aborts the installation. (i know that if i flash the usa versions my home button won't work, but i just wanted to check)
im sure therell be devs with intl versions willing to help. iean whats the difference between the usa and intl version if its just a few lines in a piece of code it should be easy to change.
but at least be grateful lots of hard works been put into this i was gonna wait beford ruining the show asking for a intl version.
minipot said:
im sure therell be devs with intl versions willing to help. iean whats the difference between the usa and intl version if its just a few lines in a piece of code it should be easy to change.
but at least be grateful lots of hard works been put into this i was gonna wait beford ruining the show asking for a intl version.
Click to expand...
Click to collapse
I've thanked Tcollins twice, trust me I really appreciate his hard work and I'm sorry it didn't come across as such.
I think I found the problem with clockworkmod aborting the installation, inside the .zip file, rather than going straight to the contents of the rom with the system folder, etc. there is another folder named nightly cm9 player inside the original nightly cm9 player folder.
I do have a intl device. The only difference is the home button. As the difference in the build is the kernel where you have to chose in the config aries_EU and remove aries_US (I don't know if you understand what I mean)
zaclimon said:
I do have a intl device. The only difference is the home button. As the difference in the build is the kernel where you have to chose in the config aries_EU and remove aries_US (I don't know if you understand what I mean)
Click to expand...
Click to collapse
so by changing that line in the kernel the home button works? do I need ubuntu to unpack the zimage?
theraf said:
so by changing that line in the kernel the home button works? do I need ubuntu to unpack the zimage?
Click to expand...
Click to collapse
You must do that with the defconfig file. And yes you need linux to unpack. But the problem is where is Tcollins source?
what do you mean by my source?
Tcollins412 said:
what do you mean by my source?
Click to expand...
Click to collapse
Your device tree and kernel source. How have you built that.
@Tcollins412
I just took a look at the zipfile and it seems that there's a folder within a folder and while I haven't tried to flash it yet, I don't think it will flash that way. Thanks.
Mike T
your right. im reuploading it.
Tcollins412 said:
your right. im reuploading it.
Click to expand...
Click to collapse
I just took a look into your updater-script. Have you take a galaxy s CM9? Because it seems to be the case.
Code:
ssert(getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" ||
getprop("ro.product.device") == "galaxysmtd" || getprop("ro.build.product") == "galaxysmtd" ||
getprop("ro.product.device") == "GT-I9000" || getprop("ro.build.product") == "GT-I9000" ||
getprop("ro.product.device") == "GT-I9000M" || getprop("ro.build.product") == "GT-I9000M" ||
getprop("ro.product.device") == "GT-I9000T" || getprop("ro.build.product") == "GT-I9000T");
Tcollins412 said:
your right. im reuploading it.
Click to expand...
Click to collapse
Thanks for the re-upload and thanks for taking on this project for the 4.0. As mentioned in my pm, I will test it over the next couple of days.....or sooner.
Mike T
nope. i took a couple things from it though.
and no problem and thank you
zaclimon said:
Your device tree and kernel source. How have you built that.
Click to expand...
Click to collapse
Agreed.
Could you post your device and vendor files on github, like how tdmcode has done for cm7 amd cm9? That way people could fork your project and try to fix some of the issues there might be. We could also get an aokp and aosp build as well.
Thanks.
Sent using Tapatalk
---------- Post added at 03:07 PM ---------- Previous post was at 02:45 PM ----------
EDIT:
Have you flashed this yourself? I took a look at the build.prop and it seriously looks like you just took an I9000 CM9 nightly and posted it here, hoping that somebody would try it out and brick their device.
Here is the build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=eng.jenkins.20120429.031009
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sun Apr 29 03:10:25 PDT 2012
ro.build.date.utc=1335694225
ro.build.type=userdebug
ro.build.user=jenkins
ro.build.host=cyanogenmod
ro.build.tags=test-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=aries
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=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9000
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9000-user 2.3.5 GINGERBREAD XXJVT release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.5/GINGERBREAD/XXJVT:user/release-keys
ro.build.characteristics=default
ro.cm.device=galaxysmtd
# end build properties
#
# system.prop for smdkc110
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmodnightly
keyguard.no_require_sim=true
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.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=9-20120429-NIGHTLY-galaxysmtd
ro.modversion=9-20120429-NIGHTLY-galaxysmtd
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.opengles.version=131072
wifi.interface=wlan0
wifi.supplicant_scan_interval=20
ro.telephony.ril_class=SamsungRIL
ro.telephony.ril.v3=icccardstatus,datacall,signalstrength,facilitylock
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.vold.switchablepair=/mnt/emmc,/mnt/sdcard
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
dalvik.vm.checkjni=false
ro.vold.umsdirtyratio=20
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
And it won't flash even if someone tried to, due to the getprops in the updater-script that zaclimon posted a few posts above.
Of cource my suspicions could be totally wrong, and I apologize if they are, but until your source is released, I strongly advise people to not flash this. Just take a look at the build.prop and you know that it won't be compatible with the YP-G1.
Tcollins412 said:
WARNING:
For devs and experts ONLY!
This is not fully functional and it is not well tested yet!
I do not take responsibility for any damage you cause your player!
This is an unofficial port of CM9 alpha to the Galaxy Player 4.0 (USA).
Preparation
MAKE A FULL BACKUP! Make sure you can recover using heimdall or odin.
Backup /system using "dd" use with odin/heimdall, just in case:
dd if=/dev/block/stl9 of=/mnt/sdcard/system.img bs=512
Backup your apps if you care about them
Installation
Download the ROM for your device
Boot into recovery and install the ROM
Do a full wipe. Wipe data, cache, dalvik, everything
Reboot, and you should have cm9!
Issues?
Post any other issue here and I will respond when I get a chance.
Please do NOT send me PM's.
Download
http://www.mediafire.com/?wch69mtgwx4ssra
Note: gapps is not currently included in the ROM.
THIS IS STILL IN TESTING. PLEASE LEAVE A COMMENT TELLING ME HOW WELL IT WORKED.
Click to expand...
Click to collapse
Thanks. I'll port a aokp(may be this rom is 4.0.3
Sent from my galaxy s using XDA
klin1344 said:
Agreed.
Could you post your device and vendor files on github, like how tdmcode has done for cm7 amd cm9? That way people could fork your project and try to fix some of the issues there might be. We could also get an aokp and aosp build as well.
Thanks.
Sent using Tapatalk
---------- Post added at 03:07 PM ---------- Previous post was at 02:45 PM ----------
EDIT:
Have you flashed this yourself? I took a look at the build.prop and it seriously looks like you just took an I9000 CM9 nightly and posted it here, hoping that somebody would try it out and brick their device.
Here is the build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=eng.jenkins.20120429.031009
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sun Apr 29 03:10:25 PDT 2012
ro.build.date.utc=1335694225
ro.build.type=userdebug
ro.build.user=jenkins
ro.build.host=cyanogenmod
ro.build.tags=test-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=aries
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=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9000
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9000-user 2.3.5 GINGERBREAD XXJVT release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.5/GINGERBREAD/XXJVT:user/release-keys
ro.build.characteristics=default
ro.cm.device=galaxysmtd
# end build properties
#
# system.prop for smdkc110
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmodnightly
keyguard.no_require_sim=true
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.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=9-20120429-NIGHTLY-galaxysmtd
ro.modversion=9-20120429-NIGHTLY-galaxysmtd
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.opengles.version=131072
wifi.interface=wlan0
wifi.supplicant_scan_interval=20
ro.telephony.ril_class=SamsungRIL
ro.telephony.ril.v3=icccardstatus,datacall,signalstrength,facilitylock
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.vold.switchablepair=/mnt/emmc,/mnt/sdcard
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
dalvik.vm.checkjni=false
ro.vold.umsdirtyratio=20
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
And it won't flash even if someone tried to, due to the getprops in the updater-script that zaclimon posted a few posts above.
Of cource my suspicions could be totally wrong, and I apologize if they are, but until your source is released, I strongly advise people to not flash this. Just take a look at the build.prop and you know that it won't be compatible with the YP-G1.
Click to expand...
Click to collapse
I took a look into his lib folder and he have the gralloc.aries.so instead of gralloc.s5pc110.so So it can be a CM9 nightly in which he replaced the kernel. Let's see how it will turn.
This is my fourth Samsung Android device, and you'd think I'd be beyond brilliant noob moves... but apparently not.
I got TWRP recovery installed on my device fine (Sprint SPH-L600)... but, since I saw this phone is a Tri-Band, I assumed that it was more or less identical regardless of provider (yeah... I know already... don't say it)
So now I'm looking for my old factory firmware to Odin back in because now my Samsung message just sits on my screen after boot animation.
All I wanted was root... which I managed to find after it was too late... so if I can get back to stock I'm good.
Anybody out there have any ideas on downloading the stock firmware again. I see the customs that are out aren't fully working yet... and all I was really missing with stock was hot spot and root access. I can live w/o hotspot and usb tether for now, and I solved my root issue.
Thanks in advance for any help.
B
Im in same boat as your I soloved it by cwm recovery install silent rom temporarily it worked , now till we get hands on the stock usa version sprint rom, for those who have sprint galaxy mega 6.3 dont do rooting yet till someone figure out a safe way to root sprint version
Sent from my GT-I9200 using xda app-developers app
---------- Post added at 08:09 PM ---------- Previous post was at 07:26 PM ----------
Correction its silentlight rom but no lte or 3g works grrr!
Sent from my GT-I9200 using xda app-developers app
Hmmm
Maybe all we need is some kind soul to make a nand backup of his stock firmware and post that back? Not sure. One of the drawbacks of being the first on your block with the new toy? I think so...
Yea right sprint mega is not the same rom as att or verzion!
Sent from my GT-I9200 using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
One thing is if you had checked about and seen the firmware info what prefix is that for usa region?
Sent from my GT-I9200 using xda app-developers app
How is lte working on this phone? Have the lg g2 and there are serious issues with sprints spark....
Sent from my LG-LS980 using Tapatalk
LTE Performance
Well... off topic, but I boot-looped the phone the first day that I got it... so not a great idea about how it runs on the network. My old phone (Epic4GT) was WiMax and it occasionally had 4g (and was fast when it did...). Sprint is phasing out WiMax in the coming months so I wanted an LTE. BUT... as far as I've observed so far, I NEVER had a 4G connection. Missing in the setup screens is the traditional "4G switch", but you can switch selection between CDMA and LTE/CDMA/Evo (among others)... and I tried toggling in and out of the LTE option and it never indicated to me 4GLTE on the notification area. Again, though... I only had it running for a short time, so I could have missed something. Really hoping someone antes up a stock firmware somehow so I can get on with trying it out for real. (to bring it back around to originating topic)
I think for now you can only pickup the 1900mhz lte until sprint updates the APN with logon info for the other bands. Though you won't see 800mhz for a few years they are converting the wimax towers over to ltd so you will get that once the APN works
Sent from my LG-LS980 using Tapatalk
I finbaly got the phone mode working but stilk at 1x instead of 3g hmmmm
Sent from my GT-I9205 using xda app-developers app
Tri-Band information
I actually read this morning that the S4 Mini is the only one (of the 4 sprint phones that will get Spark LTE) that is actually functioning. They are planning on doing OTA updates to enable it in the other three in the coming months. As for the 800 MHz broadcast... it's not WiMax, but actually the old Nextel hardware that their going to use. So for now, unless you have the S4 Mini, don't plan on using your 4G or Spark at all until Sprint updates your phone OTA.
Firmware Version Anyone?!?
So I found some other stock firmware for the Mega on different carriers by searching the actual firmware build number. Is there anyone out there with a Sprint Mega who would be willing to look into their phone info to see what the build number is on your firmware and pass that along in this thread please?
Thanks so much in advance.
dug though nandroid backups files on laptop and behold! i got the orginal build.prop here it is!!
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=JDQ39.L600VPUAMI6
ro.build.version.incremental=L600VPUAMI6
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Wed Sep 18 00:02:17 KST 2013
ro.build.date.utc=1379430137
ro.build.type=user
ro.build.user=se.infra
ro.build.host=R0302-18
ro.build.tags=release-keys
ro.product.model=SPH-L600
ro.product.brand=samsung
ro.product.name=meliusltespr
ro.product.device=meliusltespr
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=meliusltespr
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=meliusltespr-user 4.2.2 JDQ39 L600VPUAMI6 release-keys
ro.build.fingerprint=samsung/meliusltespr/meliusltespr:4.2.2/JDQ39/L600VPUAMI6:user/release-keys
ro.build.characteristics=phone,chameleon
# Samsung Specific Properties
ro.build.PDA=L600VPUAMI6
ro.build.hidden_ver=L600VPUAMI6
ro.build.changelist=1708610
ro.product_ship=true
ro.chipname=MSM8930AB
ro.build.version.software=MI6
# end build properties
# Evolution RIL (8xxx)
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=c2d
debug.compbypass.enable=1
dalvik.vm.heapsize=36m
debug.enable.wl_log=1
persist.hwc.mdpcomp.enable=true
#
# system props for the cne module
#
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.feature=0
#
# System prop for Tvout/HDMI
#
persist.sys.camera.connect=0
persist.sys.videomode=0
ro.hdmi.enable=true
lpa.decode=true
lpa.use-stagefright=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
# System 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
ro.opengles.version=131072
#
# 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=0
# System property for Default Brightness
ro.lcd_min_brightness=20
ro.lcd_brightness=120
#
# 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=240
# System property for PreloadInstaller
persist.sys.storage_preload=1
# Use CDMALTE Phone
telephony.lteOnCdmaDevice=1
# Enable time services daemon
persist.timed.enable=true
# Keep SIM state on LPM mode
persist.radio.apm_sim_not_pwdn=1
# Don't wait the card state for RADIO POWER request
persist.radio.no_wait_for_card=1
# For sys info indication
persist.radio.add_power_save=1
# Snapshot Setting
persist.radio.snapshot_enabled=1
persist.radio.snapshot_timer=22
# Control EONS (true = EONS enabled, false = EONS disabled)
persist.eons.enabled=false
# Data modules
ro.use_data_netmgrd=true
# Use CP SE13 Table
persist.radio.use_se_table_only=1
# Default ECCList
ro.ril.ecclist=911,#911,*911
# Support Global Mode (Global Mode project)
ro.config.multimode_cdma=1
# Use data service state for signal display (Except USC CS devices)
ro.config.combined_signal=true
# Chameleon Default Operator (SPR with Chameleon)
ro.cdma.default_numeric=310000
ro.cdma.default_alpha=Chameleon
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.vendor.extension_library=/system/lib/libqc-opt.so
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.sec.fle.encryption=true
ro.hdcp2.rx=tz
media.enable-commonsource=true
ro.secwvk=144
ro.config.ringtone=Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Alarm_Morning_flower.ogg
ro.config.media_sound=Over_the_horizon_Acoustic.ogg
ro.monkey=0
ro.error.receiver.default=com.samsung.receiver.error
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.setupwizard.mode=DISABLED
ro.com.google.apphider=off
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=4.2_r3
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
see? i was able to find out info about it yep
You da man!
Thanks dude! Exactly what I was looking for. Much appreciated...
Err... I take that back. I thought I was bright enough to figure out how to solve my problem with that information... but I'm just not that smart, darn it.
Any techier types out there who can tell me what I can do with this info (not THAT!)... I'd appreciate being pointed in the right direction. I guess for me the only way I can think to get back running again is to get the L600VPUAMI6 Firmware so I can flash it with Odin again... but I can't find it posted anywhere and (as stated before) I brilliantly neglected to do a nandroid backup of my stock setup before flashing the new firmware (wrong model).
Alternatively, if anyone has a stock SPH-L600 and could make a nandroid backup of all the pretinent files I did figure out how to write that into an "update.zip" (from a helpful online primer...) so I can plunk that in with recovery... but I haven't had any takers yet with the backup intact (for my model).
So I'll keep trying to figure it out I guess.
Of course any help is welcome.
For those planning to roit it please perform a nandroid backup there are apps in google playstore that not need root espically the boot.img! Id want anyone upload virgin sprint stock rom itll help us get back to working normally you can link the uploaded file here
Sent from my GT-I9205 using xda app-developers app
fyi.... you can always go to any sprint store and find that one and go in setting,more,about phone and take a snapshot of that revision including kernel version with your camera phone and post the pic in here simple?
blohman said:
So I found some other stock firmware for the Mega on different carriers by searching the actual firmware build number. Is there anyone out there with a Sprint Mega who would be willing to look into their phone info to see what the build number is on your firmware and pass that along in this thread please?
Thanks so much in advance.
Click to expand...
Click to collapse
---------- Post added at 10:30 AM ---------- Previous post was at 09:54 AM ----------
It has dawned on me that why no 3g or lte is bec the roited boit.img made by other mega from diffrent carrier is not the same kernel version so what I would do is use the boot.ing and extract it theb build a kernel with correct version and make a new boit.img it should restore it the config is very specfic about this model ive done mune on htc evo 4g and it worked like charm what I need is for someone who has stock rom and note the kernel version and adb pull /proc/config.gz and send that to me?
Sent from my GT-I9205 using xda app-developers app
Firmware Version
I actually had done what you suggested yesterday (sort of... since I'd already upgraded my old phone to the Mega, I don't actually have a [working] camera phone at the moment)... so I did it the old fashioned way... pen and paper.
The firmware version for the Sprint version is L600VPUAMI6 (that's a capital "I", like in Ice Cream... not a 1).
I still can't find it, even though I now know the version number. Still hoping someone may post it up here.
The kernel version is really 3.4.0 with build number appended yeah I looked at it in sprint store I noticed in phone satus it should show imei and network status saying evdo,3g ... hmm mine didnt shows so I suspect the sim card or efs protected folder is screwed fyi the sim card I cant figure out how to remove it bec it dies have inei is printed so if those who have mega please use efs pro to back it up!
Sent from my GT-I9205 using xda app-developers app
---------- Post added at 09:02 PM ---------- Previous post was at 09:00 PM ----------
Also those have stock boot imge in mega is pull up /proc/config.gz by mean of adb pull and id like to get that file for compiling kernel
Sent from my GT-I9205 using xda app-developers app
Running wrong rom (sort of...)
Learned a little more last night. Apparently Samsung has a arrangement with Best Buy (learned in chat w/ a Samsung tech). You can take your Samsung phone in and they can reflash it w/ stock rom again. You lose everything you had installed - but my phone was brand new, so I wouldn't lose anything really. The caveat is that they have to HAVE the rom in there proprietary system. They still DON'T have the SPH-L600, so I remained out of luck getting the stock rom. I don't know if they have the T-mobile rom.
What I HAVE ended up doing is putting an I9205 rom in (Cassie's XtraLite?) and "most" of my phone is working again. No 3G (or 4G), but phone works and wifi works... so it's limping along. Going to play w/ Kies today to see if it can figure the phone out, now that it's actually booting. It appears that, like Best Buy, Kies still doesn't have access to the factory rom (online) yet. I may just try to flash some of my old modems onto this and see if I can wake up the 3G if Kies doesn't come up with a complete package.
Will they charge to reflash it? Thanks for the info i was afraid not take it to sprint store for voiding warranty if they find out
So...
About kies, i have trouble with it not reonizing my phone no matter what drivers are properly instalked either kies or kies3 so what gives?
Sent from my GT-I9205 using xda app-developers app
Ive got info from one of xda user that successfully rooted his sprint mega with lte working im going get him to back up the stock rom and hopeflly he agrees to....
Sent from my GT-I9205 using xda app-developers app
Best Buy
They tried to flash my rom (no luck...didn't have the SPH-L600 rom available to their proprietary software [SMART?]... he even called Samsung and they said it's not available yet - have to wait until they distribute it I guess). Anyhow, they didn't charge or say anything about charging. Maybe they have the T-Mobile... not sure on that one.
BTW... Finally got Kies to understand which firmware I wanted (have to ask "case sensitive", i.e. sph-l600 doesn't work... SPH-L600 does!) Then only to have Kies say it doesn't support flashing that rom yet (lol - I detect a theme here, i.e. play the waiting game until either Samsung releases it, or an actual Sprint tech has a heart and leaks the rom so we can get back to stock).
For now still limping along mocking an i9205 w/ Cassie's XtraLite custom rom - no 3G or 4G (or data of any kind). Phone works... so does wifi.
Hey guys. Does anyone by chance have a BELL stock ftf that they could link me or re-direct me where i can find one? I cant use any other ones at the moment.
Since i updated to the latest 4.3 and went to downgrade to re root my device i have been having issues with my device and can't get any data connectivity on my phone but can make calls.
I was hoping to flash the stock rom so that everything will work again.
Yeah i can use the apn settings for bell to achieve most of my data connectivity but i would perfer full usage until i can get full root.
originalspic said:
Hey guys. Does anyone by chance have a BELL stock ftf that they could link me or re-direct me where i can find one? I cant use any other ones at the moment.
Since i updated to the latest 4.3 and went to downgrade to re root my device i have been having issues with my device and can't get any data connectivity on my phone but can make calls.
I was hoping to flash the stock rom so that everything will work again.
Yeah i can use the apn settings for bell to achieve most of my data connectivity but i would perfer full usage until i can get full root.
Click to expand...
Click to collapse
I'm on Bell and have no data connectivity issues on 4.3?
Unfortunately I don't have the old FTF's - I was considering extracting them prior to upgrading but I didn't really want to wait any longer.
What issues are you having?
Have you installed the C6806 firmware?
hassanmahmood said:
I'm on Bell and have no data connectivity issues on 4.3?
Unfortunately I don't have the old FTF's - I was considering extracting them prior to upgrading but I didn't really want to wait any longer.
What issues are you having?
Have you installed the C6806 firmware?
Click to expand...
Click to collapse
yeah i have the similar issue. when i downgraded from 4.3 to 4.1 with a 6806 it didn't transfer my bell info over. I am not able to access any data connection unless setup the apn for bell and then i get connectivity. i am currently running 4.2.2 under a c6833 model with apn set up and works alright. but a lot of my bell stuff is gone and would like to have something setup just in case. the rest of the phone does work pretty darn well so far. except it keeps trying to ask to update to 4.3 again. I was going to un-root the device and try to do the update but i am unsure how it would fair with the phone since its not c6833 and not 6806. And instead of it saying "LTE" it says "4G" with is more of a little thing that bugs me personally lol
originalspic said:
yeah i have the similar issue. when i downgraded from 4.3 to 4.1 with a 6806 it didn't transfer my bell info over. I am not able to access any data connection unless setup the apn for bell and then i get connectivity. i am currently running 4.2.2 under a c6833 model with apn set up and works alright. but a lot of my bell stuff is gone and would like to have something setup just in case. the rest of the phone does work pretty darn well so far. except it keeps trying to ask to update to 4.3 again. I was going to un-root the device and try to do the update but i am unsure how it would fair with the phone since its not c6833 and not 6806. And instead of it saying "LTE" it says "4G" with is more of a little thing that bugs me personally lol
Click to expand...
Click to collapse
I still don't understand what you mean by 'works alright' - what is it you are missing?
Adding the apn and having it be there when you put the phone on the first time are no different from one another? So long as you have the exact settings?
Post screenshots of your APN settings and I'll tell you if you're missing something.
hassanmahmood said:
I still don't understand what you mean by 'works alright' - what is it you are missing?
Adding the apn and having it be there when you put the phone on the first time are no different from one another? So long as you have the exact settings?
Post screenshots of your APN settings and I'll tell you if you're missing something.
Click to expand...
Click to collapse
I have the network working now as good as its going to get. so no more problems ATM. The only thing at this point is to have a copy of the original bell ftf. jujst incase i have to send this puppy out for repairs or if i decide to sell it.
originalspic said:
I have the network working now as good as its going to get. so no more problems ATM. The only thing at this point is to have a copy of the original bell ftf. jujst incase i have to send this puppy out for repairs or if i decide to sell it.
Click to expand...
Click to collapse
wait for the next firmware udate and build a FTF from that and post an upload to the FTF thread.
Did you get the bell ftf plz share
originalspic said:
Hey guys. Does anyone by chance have a BELL stock ftf that they could link me or re-direct me where i can find one? I cant use any other ones at the moment.
Since i updated to the latest 4.3 and went to downgrade to re root my device i have been having issues with my device and can't get any data connectivity on my phone but can make calls.
I was hoping to flash the stock rom so that everything will work again.
Yeah i can use the apn settings for bell to achieve most of my data connectivity but i would perfer full usage until i can get full root.
Click to expand...
Click to collapse
Plz if you got the ftf files plz share i need the bell ftf
Or you know, you could get the right FTF from PC Companion, which downloads the regional version (in this case the Canadian version) since it looks up the device's CDA number. Just keep that in mind if you're going to send it in for repairs or whatever. Just un-root (if you're rooted), re-lock the bootloader (if it's unlocked - and remember to restore the TA partition) and just repair it using PC Companion. It's what i did when i sent my Ultra in for repairs last week.
LordManhattan said:
Or you know, you could get the right FTF from PC Companion, which downloads the regional version (in this case the Canadian version) since it looks up the device's CDA number. Just keep that in mind if you're going to send it in for repairs or whatever. Just un-root (if you're rooted), re-lock the bootloader (if it's unlocked - and remember to restore the TA partition) and just repair it using PC Companion. It's what i did when i sent my Ultra in for repairs last week.
Click to expand...
Click to collapse
+1
We, the global community cant help you Canadians with this one. Someone up there has to DL the firmware and build the FTF
I guess we could DL it but it would take a but of jiggery-pokery in the build.prop, and it might work???
LordManhattan said:
Or you know, you could get the right FTF from PC Companion, which downloads the regional version (in this case the Canadian version) since it looks up the device's CDA number. Just keep that in mind if you're going to send it in for repairs or whatever. Just un-root (if you're rooted), re-lock the bootloader (if it's unlocked - and remember to restore the TA partition) and just repair it using PC Companion. It's what i did when i sent my Ultra in for repairs last week.
Click to expand...
Click to collapse
Yeah see i did that and it did not work at all..which i thought wtf. so i think i got to wait for kitkat to relase and just go from there....gah XD
Could someone with a bell 6806 copy and post the first 40 odd lines (or a zip of the whole thing) of the build.prop? I'll see if I cant build a FTF for Bell phones
Bell ftf ?
I tried to repair my phone with pc companion with flash mode when finished i found it was the same firmware 14.2.A.1.136 US Generic that i took from the repository and flashed earlier. Made an ftf from PC companion with the help of Flashtools flashed it and found the same. When i go to Bell website to see what is the latest software it says Android: 4.3 Firmware: 10.4.B.0.569. I think it has to do something with the CDA 1276-1569-R4B I guess it is for the US unbranded. I have no idea what is the CDA for Bell Canada c6806. Could some one help. If i get things right i can post the FTF so plz help.
---------- Post added at 01:15 AM ---------- Previous post was at 01:07 AM ----------
Can someone tell me what is the Customization version for Bell Canada Xperia Z ultra just to see if it stays same after flashing another FTF from another country.
Got it but upload speed too slow
Got the Bell frimware and also made the FTF but upload speeds are very slow may take 2-3 days I guess. Please suggest file hosting servive with best upload speeds my broadband gives me 500kbps but i get only 50kbps with google drive and dropbox
Cda for canada bell c6802
blueether said:
could someone with a bell 6806 copy and post the first 40 odd lines (or a zip of the whole thing) of the build.prop? I'll see if i cant build a ftf for bell phones
Click to expand...
Click to collapse
please can you make an ftf file from pc companion with cda version
*cough* @blueether
Sent from my C6833 using Tapatalk
I'll play whan I get home from work
Sent from my Xperia Z Ultra using Tapatalk
Sorry, not enpugh to get Sony to thing that my C6802 is a Bell C6805
Build prop
blueether said:
Sorry, not enpugh to get Sony to thing that my C6802 is a Bell C6805
Click to expand...
Click to collapse
##### Merging of the /util/data/semc_kernel_time_stamp.prop file #####
ro.build.date=Tue Nov 19 19:53:25 2013
ro.build.date.utc=1384858405
ro.build.user=BuildUser
ro.build.host=BuildHost
##### Final patch of properties #####
ro.build.product=C6806
ro.build.description=C6806-user 4.3 RHINE-1.1-131125-1201 eng.hudsonslave test-keys
ro.product.brand=Sony
ro.product.name=C6806
ro.product.device=C6806
ro.build.tags=release-keys
ro.build.fingerprint=Sony/C6806/C6806:4.3/14.2.A.0.290/eng.hudsonslave:user/release-keys
######################## Customized property values #########################
ro.semc.version.cust=1276-3513
ro.semc.version.cust_revision=R3B
ro.somc.customerid=6334
ro.cst.prm=1276-3472:R6B,1276-3470:R6B
#############################################################################
ro.config.ringtone=xperia.ogg
ro.config.notification_sound=notification.ogg
ro.config.alarm_alert=alarm.ogg
ro.semc.content.number=PA4
################# Updating of the SW Version #################
ro.semc.version.fs_revision=14.2.A.0.290
ro.build.id=14.2.A.0.290
ro.build.display.id=14.2.A.0.290
##### Values from product package metadata #####
ro.semc.product.model=C6806
ro.semc.ms_type_id=PM-0430-BV
ro.semc.version.fs=BELL-LTE
ro.semc.product.name=Xperia Z Ultra
ro.semc.product.device=C68
ro.product.model=C6806
# begin build properties
# autogenerated by buildinfo.sh
ro.build.version.incremental=eng.hudsonslave
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.type=user
ro.product.board=MSM8974
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8974
# ro.build.product is obsolete; use ro.product.device
# Do not try to parse ro.build.description or .fingerprint
ro.build.characteristics=default
# end build properties
#
# from device/qcom/msm8974/system.prop
#
#
# system.prop for msm8974
#
rild.libpath=/vendor/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
# Start in global mode
ro.telephony.default_network=0
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=c2d
persist.hwc.mdpcomp.enable=true
debug.mdpcomp.logs=0
dalvik.vm.heapsize=36m
dev.pm.dyn_samplingrate=1
persist.demo.hdmirotationlock=false
ro.hdmi.enable=true
tunnel.decode=true
tunnel.audiovideo.decode=true
tunnel.multiple=true
lpa.decode=false
lpa.use-stagefright=true
persist.speaker.prot.enable=false
qcom.hw.aac.encoder=true
#
# system props for the cne module
#
persist.cne.feature=1
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
mm.enable.smoothstreaming=true
media.aac_51_output_enabled=true
#37491 is decimal sum of supported codecs in AAL
#codecs: AVI AC3 ASF AAC QCP DTS 3G2 MP2TS
mm.enable.qcom_parser=37491
# VIDC: debug_levels
# 1:ERROR 2:HIGH 4:LOW 0:NOLOGS 7:AllLOGS
vidc.debug.level=1
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data.netmgrd.qos.enable=true
ro.data.large_tcp_window_size=true
#system props for time-services
persist.timed.enable=true
#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
# System property for cabl
ro.qualcomm.cabl=1
#
# System props for telephony
# System prop to turn on CdmaLTEPhone always
telephony.lteOnCdmaDevice=0
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=none
ro.qc.sdk.sensors.gestures=true
ro.qc.sdk.gestures.camera=false
ro.qc.sdk.camera.facialproc=false
#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
tunnel.audio.encode = true
#
# from device/somc/rhine/system.prop
#
#
# platform specific part of system.prop
#
#System prop for gralloc
persist.gralloc.cp.level3=1
#System props for the MM Audio
media.aac_51_output_enabled=true
# system property for somc thermal solution
ro.somc.thermal=system_monitor
#System props for the MM modules
encoder.video.profile=high
# aDSP sensors
ro.qualcomm.sensors.qmd=true
debug.qualcomm.sns.hal=w
ro.qc.sdk.sensors.gestures=false
ro.qc.sensors.max_accel_rate=false
ro.qc.sensors.max_gyro_rate=false
ro.qc.sensors.max_mag_rate=false
ro.qualcomm.sensors.pedometer=true
ro.qualcomm.sensors.pam=false
ro.qualcomm.sensors.scrn_ortn=false
# Default values/Locales for the hiding languages feature
ro.product.locale.excluded=ar_EG ar_IL fa_IR iw_IL
# Modem power save enabled
persist.radio.add_power_save=1
# Do not use mdp composition for more than 3 pipes
debug.mdpcomp.maxpermixer=3
# Disable mixed mode
debug.mdpcomp.mixedmode.disable=1
#
# from device/somc/togari/system.prop
#
#
# product specific part of system.prop
#
ro.usb.pid_suffix=19C
# NFC
ro.nfc.on.default=true
ro.nfc.se.sim.enable=true
ro.nfc.se.smx.enable=false
ro.nfc.icon.enable=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product-res-path=framework/SemcGenericUxpRes.apk
ro.com.android.dataroaming=false
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.com.google.clientidbase=android-sonyericsson
ro.com.google.clientidbase.ms=android-sonymobile
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.3_r1
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.sf.lcd_density=320
ro.hwui.texture_cache_size=48
ro.hwui.layer_cache_size=32
ro.hwui.r_buffer_cache_size=4
ro.hwui.path_cache_size=24
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=5
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
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=0
ro.qc.sdk.izat.service_mask=0x0
persist.gps.qc_nlp_in_use=0
ro.gps.agps_provider=1
ro.service.swiqi3.supported=true
persist.service.swiqi3.enable=1
ro.drm.active.num=6
ro.drm.active.0=marlin,1
ro.drm.active.1=playready,1
ro.drm.active.2=dtla,1
ro.drm.active.3=marlin_import,1
ro.drm.active.4=ckb,1
ro.drm.active.5=widevine,1
ro.sony.fota.encrypteddata=supported
---------- Post added at 10:29 AM ---------- Previous post was at 10:20 AM ----------
blueether said:
Sorry, not enpugh to get Sony to thing that my C6802 is a Bell C6805
Click to expand...
Click to collapse
I think that should be enough
Can you help sir
LordManhattan said:
*cough* @blueether
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Can you help our Canadian community by making an FTF with the help of given Build.prop please
Here it is thank you guys for your support
Got the .290 firmware for Bell mobility Canada
https://www.dropbox.com/s/1t6vmf9bfn...0Canada .ftf Hope this helps some one
Hello people, as i dig into some information about phone build prop settings and the samsung framework i found some interesting info
https://zapek.com/blog/how-to-make-your-galaxy-note-4-fast-again/
this guide is for the note 4, but works wonders on our galaxy alpha
basically it disables agressive samsung ram management, and uses the one closer do AOSP, it made my phone better, you guys can try you just need root and a build prop editor!
only works on stock samsung roms and maybe stock based roms!
Thanks man I will try it
Hi I can't find a line sys.config.samp_spcm_enable=
martinforester said:
Hi I can't find a line sys.config.samp_spcm_enable=
Click to expand...
Click to collapse
Which rom do you use?
because I found it in stock rom.
I have stock 5.0.2 oryginal rom
martinforester said:
I have stock 5.0.2 oryginal rom
Click to expand...
Click to collapse
in the #SAMP_SPCM line
victoram said:
Hello people, as i dig into some information about phone build prop settings and the samsung framework i found some interesting info
https://zapek.com/blog/how-to-make-your-galaxy-note-4-fast-again/
this guide is for the note 4, but works wonders on our galaxy alpha
basically it disables agressive samsung ram management, and uses the one closer do AOSP, it made my phone better, you guys can try you just need root and a build prop editor!
only works on stock samsung roms and maybe stock based roms!
Click to expand...
Click to collapse
Hi, can you give step by step instructions on how to do this? Thanks!
victoram said:
Hello people, as i dig into some information about phone build prop settings and the samsung framework i found some interesting info
https://zapek.com/blog/how-to-make-your-galaxy-note-4-fast-again/
this guide is for the note 4, but works wonders on our galaxy alpha
basically it disables agressive samsung ram management, and uses the one closer do AOSP, it made my phone better, you guys can try you just need root and a build prop editor!
only works on stock samsung roms and maybe stock based roms!
Click to expand...
Click to collapse
Will this only work for LL 5.x.x? I have KK 4.4.4 and can't find any of these files. Thanks.
I applied this and it works , Less Heat and Phone feels mutch more responsive and snappier .
Thanks for sharing !
cqdiep said:
Will this only work for LL 5.x.x? I have KK 4.4.4 and can't find any of these files. Thanks.
Click to expand...
Click to collapse
i think it is only on lolipop based touch wiz
victoram said:
i think it is only on lolipop based touch wiz
Click to expand...
Click to collapse
Makes sense, I should have read the title more carefully. I'm running KK without any problems.
I don't think so, I have Lollipop and I don't have any of these lines
martinforester said:
I don't think so, I have Lollipop and I don't have any of these lines
Click to expand...
Click to collapse
you shouldd only have this line: "sys.config.samp_spcm_enable=true" change it to false
=====> sys.config.samp_spcm_enable=false
you have to add these 3 manually.
sys.config.samp_enable=false
ro.config.fha_enable=true
ro.sys.fw.use_trim_settings=false
I don't have this line
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LRX22G
ro.build.display.id=LRX22G.G850FXXU2COI3
ro.build.version.incremental=G850FXXU2COI3
ro.build.version.sdk=21
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.0.2
ro.build.date=Fri Sep 11 19:17:32 KST 2015
ro.build.date.utc=1441966652
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWHD7522
ro.build.tags=release-keys
ro.product.model=SM-G850F
ro.product.brand=samsung
ro.product.name=sltexx
ro.product.device=slte
ro.product.board=universal5430
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos5
# ro.build.product is obsolete; use ro.product.device
ro.build.product=slte
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=sltexx-user 5.0.2 LRX22G G850FXXU2COI3 release-keys
ro.build.fingerprint=samsung/sltexx/slte:5.0.2/LRX22G/G850FXXU2COI3:user/release-keys
ro.build.characteristics=phone
# Samsung Specific Properties
ro.build.PDA=G850FXXU2COI3
ro.build.hidden_ver=G850FXXU2COI3
ro.config.rm_preload_enabled=0
ro.build.changelist=5614954
ro.product_ship=true
ro.chipname=exynos5430
persist.sys.storage_preload=1
# end build properties
#
# HWUI_BUILD_PROPERTIES
#
ro.hwui.texture_cache_size=24
ro.hwui.layer_cache_size=16
ro.hwui.path_cache_size=4
ro.hwui.shape_cache_size=1
ro.hwui.gradient_cache_size=0.5
ro.hwui.drop_shadow_cache_size=2
ro.hwui.r_buffer_cache_size=2
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
#
# from device/samsung/slte/system.prop
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
#
# system.prop for universal5430
#
# LCD Density
ro.sf.lcd_density=320
ro.arch=exynos5430
ro.kernel.qemu.gles=1
persist.demo.hdmirotationlock=false
#DHA
ro.config.dha_cached_max=4
ro.config.dha_empty_init=24
ro.config.dha_empty_max=24
ro.config.dha_defendth_enable=false
ro.config.dha_th_rate=1.83
#LMK Tuning
ro.config.dha_lmk_scale=1.45
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.tima=1
ro.config.timaversion=3.0
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapmaxfree=4m
dalvik.vm.heapminfree=1m
dalvik.vm.heapsize=384m
dalvik.vm.heapstartsize=8m
dalvik.vm.heaptargetutilization=0.75
ro.opengles.version=196608
ro.sf.lcd_density=480
debug.hwc.winupdate=1
debug.hwc.otf=1
ro.hdcp2.rx=tz
ro.secwvk=220
ro.securestorage.support=true
ro.build.scafe=americano
ro.build.scafe.size=short
ro.build.scafe.shot=single
ro.build.scafe.cream=white
security.mdpp=None
ro.security.mdpp.ver=1.1
ro.security.mdpp.release=5
ro.security.vpnpp.ver=1.4
ro.security.vpnpp.release=4.1
security.mdpp.result=None
ro.security.mdpp.ux=Enabled
ro.security.reactive.triggered=false
ro.error.receiver.default=com.samsung.receiver.error
ro.config.ringtone=Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Morning_flower.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.security.reactive.active=1
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.security.icd.flagmode=single
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.0_r3
persist.sys.dalvik.vm.lib.2=libart.so
ro.build.selinux=1
dalvik.vm.isa.arm.features=div
ro.config.knox=v30
ro.kernel.qemu=0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.version.sdl=2101
martinforester said:
I don't have this line sys.config.samp_spcm_enable=true
Click to expand...
Click to collapse
do you have the smart manager app?
I don't know what is it, I use "Root Browser" to browse files
martinforester said:
I don't know what is it, I use "Root Browser" to browse files
Click to expand...
Click to collapse
you probably don't have the smart manager app, it's an stock app from samsung, the line that you don't have is to disable that app from killing any tasks.
just add the 3 other lines and you should be fine.
I rooted my Alpha today and I would like to do this tweak, but I don't know how. I see the "sys.config.samp_spcm_enable=true" line in my build.prop. My question is where do I add these lines:
sys.config.samp_enable=false
ro.config.fha_enable=true
ro.sys.fw.use_trim_settings=false
Do I put them at the very bottom of the file or in the #SAMP_SPCM section where the other line is?
My first time having a rooted android so i'm a noob
Juusoavk said:
I rooted my Alpha today and I would like to do this tweak, but I don't know how. I see the "sys.config.samp_spcm_enable=true" line in my build.prop. My question is where do I add these lines:
sys.config.samp_enable=false
ro.config.fha_enable=true
ro.sys.fw.use_trim_settings=false
Do I put them at the very bottom of the file or in the #SAMP_SPCM section where the other line is?
My first time having a rooted android so i'm a noob
Click to expand...
Click to collapse
The first line you can add to #spcm as well, I think.
The second and the third lines can be added to
# ADDITIONAL_BUILD_PROPERTIES.
This is just below the #spcm section.
Note that I don't know that for sure, but I have just done it myself and it seems OK ).
Good luck mate )
Sent from my SM-G850F using Tapatalk
asetmumin99 said:
The first line you can add to #spcm as well, I think.
The second and the third lines can be added to
# ADDITIONAL_BUILD_PROPERTIES.
This is just below the #spcm section.
Note that I don't know that for sure, but I have just done it myself and it seems OK ).
Good luck mate )
Sent from my SM-G850F using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply! I already got it working few days after the post though.