I installed the original Froyo leak (2.3.9) way back when it came out, and haven't done any upgrading since. As all of these new updates are coming out, I was wondering what the best strategy to get an up to date phone would be? Is there a specific upgrade path I need to follow to get to the latest updates, or can I just go straight to 2.3.320/340 if I install the zip? Thanks in advance for your help!
I installed the original Froyo leak (2.3.9) way back when it came out, and haven't done any upgrading since.
I am in the same boat. Mine is also Rooted.
Frankly, my phone runs pretty damn well right now. Most of the reported updates don't fix problems that I have actually encountered. I really don't want to go through a fiasco like Motorola's last release.
Yeah, mine still runs well, I just don't want to get so far behind the updates that an upgrade path doesn't exist to Gingerbread or 3.0 if we get it. If you're rooted, you should be able to install some of the ROMs that are based on the newer releases, but I can't help you much with that since I'm not rooted right now.
I'm not sure how - but I'm in the same boat too. I had a stock rooted phone. I did the OTA upgrade to 2.2 and then rooted my phone. Not sure how or why, but my version is 2.3.9 MB810.
Not even sure what it means to "use the 2.2 SBF file" means, or how I got to 2.3.9.
I'm not sure how - but I'm in the same boat too. I had a stock rooted phone. I did the OTA upgrade to 2.2 and then rooted my phone. Not sure how or why, but my version is 2.3.9 MB810.
Not even sure what it means to "use the 2.2 SBF file" means, or how I got to 2.3.9.
I'm not sure how - but I'm in the same boat too. I had a stock rooted phone. I did the OTA upgrade to 2.2 and then rooted my phone. Not sure how or why, but my version is 2.3.9 MB810.
Not even sure what it means to "use the 2.2 SBF file" means, or how I got to 2.3.9.
Ditto. I'm in the same boat. Stock everything, went to official OTA froyo update. Only rooted. Mine is at 2.3.9 MB810 and no update avail. wtf?
Some users obtained an advanced copy of a Froyo SW upgrade that placed them on SW version 2.3.9. This version of SW cannot be upgraded over the air to 2.3.15.
To have your handset upgraded to the final version of DROID X SW upgrade 2.3.15, please contact your local verizon retail store for a walk-in visit to upgrade your handset."
Some users obtained an advanced copy of a Froyo SW upgrade that placed them on SW version 2.3.9. This version of SW cannot be upgraded over the air to 2.3.15.
To have your handset upgraded to the final version of DROID X SW upgrade 2.3.15, please contact your local verizon retail store for a walk-in visit to upgrade your handset."
You've got to be shittin me. I purposely stuck to the officials to prevent having to sbf or do a complete wipe and lose all my apps and settings and the time required to restore them and now this....
And I need the friggin update because I'm still getting the random soft resets which are a pain in the arse.
You've got to be shittin me. I purposely stuck to the officials to prevent having to sbf or do a complete wipe and lose all my apps and settings and the time required to restore them and now this....
And I need the friggin update because I'm still getting the random soft resets which are a pain in the arse.
Same here man.
I am going by the store when I get off work and if they can't back my stuff up I am going to be pissed. I am downloading Appbrain now just in case they can't save my stuff. At least I may have my apps backed up with Appbrain.
I am going by the store when I get off work and if they can't back my stuff up I am going to be pissed. I am downloading Appbrain now just in case they can't save my stuff. At least I may have my apps backed up with Appbrain.
Keep us posted how that goes at the store. I'm irked about this and don't want to have the hassle in setting up my phone again.. ringtones, settings, apps, ect... if it can be avoided but I reckon I will not be happy until I get the update due to the random resets and occasional audio loss and whatnot.
Device(s): Thunderbolt-I Haz the 4G's!
Girlfriend has my old Droid X
Thanks: 168
Thanked 345 Times in 210 Posts
Quote:
Originally Posted by LaZeR
Keep us posted how that goes at the store. I'm irked about this and don't want to have the hassle in setting up my phone again.. ringtones, settings, apps, ect... if it can be avoided but I reckon I will not be happy until I get the update due to the random resets and occasional audio loss and whatnot.
So mad I could eat ice cream...
ok heres what I dont get.... when you say you only stuck with the officials... then theres no way you should be on 2.3.9.... 2.3.9 was never released as an OTA download from Verizon...
now, if you did an update.zip or something that you installed, that could have brought you to 2.3.9... but I dont see how you could possibly be on 2.3.9 from the OTA
Moto/Verizon even said from the start that there was "no path" to get from the LEAKED froyo (2.3.9 & 2.3.13) to the official OTA froyo (2.3.15) ...
There is in fact a path to do it though... Its not that big of a deal to do the SBF honestly... I cant even tell you how many times Ive done it.
__________________
Gtalk is the same as my sn.
PHoldridge7232 on twitter
ok heres what I dont get.... when you say you only stuck with the officials... then theres no way you should be on 2.3.9.... 2.3.9 was never released as an OTA download from Verizon...
Seriously I don't get it. There must be goblins in my phone because I upgraded to Froyo VIA the OTA. Now way back when, I had originally done the upgrade.zip but long since sbf.d back to 2.1 and I know I was on 2.1 and did get the OTA froyo. I swear it even once said 2.3.15 but now I don't remember.
Device(s): Thunderbolt-I Haz the 4G's!
Girlfriend has my old Droid X
Thanks: 168
Thanked 345 Times in 210 Posts
did you ever install build props or a ROM or Theme or anything like that? now I'm wondering if you are actually on 2.3.15 but your build props were changed by something you installed to read 2.3.9
I'm in the same boat with the first leaked Froyo from the summer. My phone has been pretty much garbage the past few weeks. Soft resets, drops 3g if I look at it wrong, stuttering like mad, etc. I'd like to get on the official path and maintain root access. Any help is appreciated, but I plan on catching up this week.
EDIT: And I'm also on 2.3.9. (Kernel 2.6.32.90gfb07887)
__________________
I love my rooted Droid X 2.2 more than my family.
Last edited by j_ryan; December 8th, 2010 at 10:45 AM.
Please note, installing the SBF does NOT wipe your settings or text messages or installed apps.
If you are already on FroYo (albeit 2.3.9 instead of 2.3.15), there's no reason why installing the SBF will cause any of your settings to disappear.
If you are on any version of 2.2 or 2.1 right now, you can use the SBF to put yourself back on the "normal" upgrade path. I'm not positive, but I think if you use the 2.2 SBF over 2.1, you need to do a factory reset. But in any event, you can get back to a normal state with the 2.2 SBF.
did you ever install build props or a ROM or Theme or anything like that? now I'm wondering if you are actually on 2.3.15 but your build props were changed by something you installed to read 2.3.9
I have Rom Manager V2.5.0.7 (not even sure why I had installed it) - but I never flashed to a different Rom if that makes sense.
Ok I just remembered something else I did. I downloaded the enhanced "Build.prop" edit from xda or wherever some time back. How could I go about checking the line (for the version) if it exists in it and fixing it back?
Ok I just remembered something else I did. I downloaded the enhanced "Build.prop" edit from xda or wherever some time back. How could I go about checking the line (for the version) if it exists in it and fixing it back?
Device(s): Thunderbolt-I Haz the 4G's!
Girlfriend has my old Droid X
Thanks: 168
Thanked 345 Times in 210 Posts
Quote:
Originally Posted by LaZeR
Ok I just remembered something else I did. I downloaded the enhanced "Build.prop" edit from xda or wherever some time back. How could I go about checking the line (for the version) if it exists in it and fixing it back?
if you have root explorer
open it>system>build.prop>5th line down (might be other places, I just know thats where mine is) should say "ro.build.version.incramental=" then whatever version your on...
Now, I dont know if you can just edit it there and reboot and it works or how else to go about changing it... one of the devs would know better then me there
if you have root explorer
open it>system>build.prop>5th line down (might be other places, I just know thats where mine is) should say "ro.build.version.incramental=" then whatever version your on...
Now, I dont know if you can just edit it there and reboot and it works or how else to go about changing it... one of the devs would know better then me there
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=VZW
ro.build.display.id=VZW
ro.build.version.incremental=2.3.9
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Tue Aug 10 21:58:48 CDT 2010
ro.build.date.utc=1281495528
ro.build.type=user
ro.build.user=w30471
ro.build.host=il93lnxdroid08
ro.build.tags=test-keys
ro.product.model=DROIDX
ro.product.model.internal=MB810
ro.product.brand=verizon
ro.product.name=shadow_vzw
ro.product.device=cdma_shadow
ro.product.board=shadow
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=shadow_vzw
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cdma_shadow-user 2.2 VZW 2.3.9 ota-rel-keys,release-keys
ro.build.fingerprint=verizon/voles/sholes/sholes:2.2/FRG01B/45394:user/release-keys
# end build properties
#
# system.prop for CDMA Shadow
#
# rild.libpath=/system/lib/libril-moto-umts-1.so
rild.libpath=/system/lib/libmoto_ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.default_usb_mode=2
# BEGIN Motorola, a18772, 05/19/2010, IKSHADOW-5584
# Add 411 to DAN List for VZW.
ro.mot.ril.danlist=611,*611,#611,411
# END IKSHADOW-5584
persist.ril.ecclist=911,*911,#911
persist.ril.modem.mode =1
# This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec=60
# This defines the min duration between two pointer event
ro.min_pointer_dur=10
# USB modes allowed for UI and switching
ro.ngp_available=1
ro.modem_available=0
# Default network type.
# 4 => CDMA / EVDO.
ro.telephony.default_network=4
ro.com.google.clientid=android-motorola
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.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.config.vc_call_vol_steps=7
# wlan interface
wifi.interface = tiwlan0
# 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 = 90
# Indicate carrier OTA SP number schema
# refer to frameworks/base/telephony/java/com/android/
# internal/telephony/cdma/CDMAPhone.java for the schema:
ro.cdma.otaspnumschema=SELC,1,80,99
# 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
# The URL for safety information
ro.url.safetylegal=http://www.motorola.com/staticfiles/Support/legal
# our HTML browser (not WAP browser ) does not need to specify UAProf URL
ro.mot.hw.uaprof=
# Enable HAC to also display Call Setting Menu Option.
ro.mot.hw.HAC=1
# Motorola, a19622, 12/28/2009, IKSHADOW-204 / Location Settings for android
# Property to set enabling state of the location privacy setting feature.
# Motorola, a19622, 03/16/2010, IKSHADOW-2141 / Disable feature 33067
#ro.mot.settings.locprivacy=1
# ERI feature
# 0 OFF
# 1 ON
ro.mot.eri=1
# Motorola, a22976, 13/5/2010, IKSHADOW-5203
# Delay for Loss Of Service alert
ro.mot.eri.losalert.delay=2000
# If time from last RoamInd change to SID change less than below, not play alert
ro.mot.eri.sidalert.delay=1000
# END IKSHADOW-5203
# Motorol,a6889c,02/Feb/2010,IKSHADOW-619
# Proximity Sensor feature
# 0 disable
# 1 enable
persist.mot.proximity.touch=1
# End IKSHADOW-619
# BEGIN Motorola, a22976, 25-Feb-2010, IKSHADOW-702, FID 31841
# VZW Requirement Specifications: NETWORK BASED PLUS CODE DIALING
# 0 disable
# 1 enable
ro.cdma.nbpcd=1
# END IKSHADOW-702
# BEGIN Motorola, a22976, 12-Mar-2010, IKSHADOW-1784, Power Up Tone
# Motorola, a22976, 12-Apr-2010, IKSHADOW-3298, Remove temporary power up tone
# BEGIN Motorola, wbdq68, 21-May-2010, IKSHADOW-3372, Turn ON Power Up Tone
# Motorola, a22976, 26-May-2010, IKSHADOW-6164, Remove power up tone to keep the same as Droid
#persist.mot.powerup.tone=/system/media/bootup.ogg
# END IKSHADOW-3372
# END IKSHADOW-1784
# BEGIN Motorola, a22417, 22-Mar-2010, IKSHADOW-2345,default data roaming is on
ro.com.android.dataroaming=true
# END Motorola, a22417, 22-Mar-2010, IKSHADOW-2345,default data roaming is on
persist.mot.a2dp.direct = 0
# System property for SMC
ro.service.start.smc=1
# BEGIN Motorola, a21951, 17-Apr-2010, IKSHADOW-3602
# 0 disable
# 1 enable
persist.mot.usb.mediasync = 1
# END Motorola, a21951, 17-Apr-2010, IKSHADOW-3602
#Proximity sensor debounce time
mot.proximity.delay=150
# disable touch below 60 pixels
mot.proximity.distance=60
# BEGIN Motorola, pkd348, 26-Apr-2010, ISHADOW-4035
# true Horizontal BUA is preloaded, not allow to install standalone version of BuA from Android Market
# false Horizontal BUA is not preloaded
ro.HorizontalBUA=true
#Proximity sensor debounce time
mot.proximity.delay=150
mot.proximity.distance=60
# BEGIN Motorola, pkd348, 26-Apr-2010, ISHADOW-4035
# true Horizontal VVM is preloaded, not allow to install standalone version of VVM from Android Market
# false Horizontal VVM is not preloaded
ro.HorizontalVVM=true
# BEGIN Motorola, a22976, 21-May-2010, IKSHADOW-5385
# For Shadow only, NOT applied to Droid2 as requirement different
ro.mot.buttonlight.timeout=0
# END Motorola IKSHADOW-5385
ro.mot.master_clear.shredsd=false
# BEGIN Motorola, pkd348, 09-July-2010, IKSTABLEONE-1236
# true enable the feature of In case of Emergency, default is false
# false disable the ICE feature
ro.mot.fid.29967.ice=true
# BEGIN MOTOROLA, vfhk68,24-July-2010, IKSTABLEONE-2469
# true enable the feature of 33531
# false disable the feature
ro.mot.fid.33531.keylock_ecm=true
#END
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.kernel.android.ril=yes
persist.ril.mux.noofchannels=7
persist.ril.mux.ttydevice=/dev/ttyS0
persist.ril.modem.ttydevice=/dev/ttyUSB0
persist.ril.features=0x07
persist.ril.mux.retries=500
persist.ril.mux.sleep=2
ro.config.notification_sound=Droid.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=false
ro.default_usb_mode=0
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
ro.telephony.sms_segment_size=160
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.2_r5
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=1000
ro.url.safetylegal=http://www.motorola.com/staticfiles/Support/legal/?model=A855
ro.setupwizard.enable_bypass=1
ro.com.google.clientid=android-motorola
ro.com.google.clientidbase=android-verizon
ro.com.google.clientidbase.am=android-verizon
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.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.config.vc_call_vol_steps=7
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.com.motorola.smartsensor=true
ro.media.capture.maxres=8m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=60
ro.media.capture.flash=led
ro.media.capture.classification=classD
ro.media.capture.useDFR=1
ro.media.camera.focal=3564.0,3564.0
ro.media.camera.principal=1632.0,1224.0
ro.media.camera.skew=0.0
ro.media.camera.distortion=0.0,0.0,0.0,0.0,0.0
ro.media.camera.calresolution=3264,2448
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientid=android-motorola
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.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/MotoMB200/profile/MotoMB200.rdf
ro.build.version.full=Blur_Version.2.3.9.MB810.Verizon.en.US
ro.config.ringtone=DroidRollin.ogg
ro.build.config.version=GAS_NA_GCXSHAD00VZW_P022
ro.build.config.date=Tue_Aug_10_21:58:11_-0500_2010
can someone confirm that. when i had to SBF 2.1,for some reason i remember losing everything that wasn't on the SD card...
The SBF does not replace user data. Period.
If you had to downgrade from 2.2 -> 2.1, you had to do a factory reset as part of the process so you lost everything. But that was not caused by the SBF.
my build prop is the exact same as yours lazer. so could we get a original build prop and replace it?
and on a side note. i just tried the OTA. and it said i was up to date.
Last edited by bobomatic; December 8th, 2010 at 11:53 AM.
my build prop is the exact same as yours lazer. so could we get a original build prop and replace it?
That's what I'm after. I posted a request in the "rooted" section also. I think it's in two (maybe more) occurrences we need changed both in the top section and again at the bottom currently.
my build prop is the exact same as yours lazer. so could we get a original build prop and replace it?
and on a side note. i just tried the OTA. and it said i was up to date.
I would think so..
Can anyone provide the factory build.prop for 2.2.315?
I think that would resolve the issue.
Wonder what happens if you delete the build.prop and reboot?
Device(s): Thunderbolt-I Haz the 4G's!
Girlfriend has my old Droid X
Thanks: 168
Thanked 345 Times in 210 Posts
yeah editing build props I'm not sure about... like I said, a Dev would know better then I would there....
Maybe we can get a MOD to move this to the root section for you guys?
FWIW I've read that they may have pulled the OTA right now since it was only meant for the test group...
Device(s): Thunderbolt-I Haz the 4G's!
Girlfriend has my old Droid X
Thanks: 168
Thanked 345 Times in 210 Posts
ok, for what its worth, heres mine... im on 2.3.15 BUT im on ApeX 1.0.2.2 so I dont know if this will all match up for you. I may have a backup though so give me a few to check
EDIT: nope, I dont have a backup of it...
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=VZW
ro.build.display.id=Apex 1.0.2.2
ro.build.version.incremental=2.3.15
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Wed Sep 1 21:13:50 CDT 2010
ro.build.date.utc=1283393630
ro.build.type=user
ro.build.user=w30471
ro.build.host=il93lnxdroid08
ro.build.tags=test-keys
ro.product.model=DROIDX
ro.product.model.internal=MB810
ro.product.brand=verizon
ro.product.name=shadow_vzw
ro.product.device=cdma_shadow
ro.product.board=shadow
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=shadow_vzw
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cdma_shadow-user 2.2 VZW 2.3.15 ota-rel-keys,release-keys
ro.build.fingerprint=verizon/shadow_vzw/cdma_shadow/shadow:2.2/VZW/23.15:user/ota-rel-keys,release-keys
# end build properties
#
# system.prop for CDMA Shadow
#
# rild.libpath=/system/lib/libril-moto-umts-1.so
rild.libpath=/system/lib/libmoto_ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.default_usb_mode=2
# BEGIN Motorola, a18772, 05/19/2010, IKSHADOW-5584
# Add 411 to DAN List for VZW.
ro.mot.ril.danlist=611,*611,#611,411
# END IKSHADOW-5584
persist.ril.ecclist=911,*911,#911
persist.ril.modem.mode =1
# This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec=68
# This defines the min duration between two pointer event
ro.min_pointer_dur=10
# USB modes allowed for UI and switching
ro.ngp_available=1
ro.modem_available=0
# Default network type.
# 4 => CDMA / EVDO.
ro.telephony.default_network=4
ro.com.google.clientid=android-motorola
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.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.config.vc_call_vol_steps=7
# wlan interface
wifi.interface = tiwlan0
# 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 = 120
# Indicate carrier OTA SP number schema
# refer to frameworks/base/telephony/java/com/android/
# internal/telephony/cdma/CDMAPhone.java for the schema:
ro.cdma.otaspnumschema=SELC,1,80,99
# 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=48m
# The URL for safety information
ro.url.safetylegal=http://www.motorola.com/staticfiles/Support/legal
# our HTML browser (not WAP browser ) does not need to specify UAProf URL
ro.mot.hw.uaprof=
# Enable HAC to also display Call Setting Menu Option.
ro.mot.hw.HAC=1
# Motorola, a19622, 12/28/2009, IKSHADOW-204 / Location Settings for android
# Property to set enabling state of the location privacy setting feature.
# Motorola, a19622, 03/16/2010, IKSHADOW-2141 / Disable feature 33067
#ro.mot.settings.locprivacy=1
# ERI feature
# 0 OFF
# 1 ON
ro.mot.eri=1
# Motorola, a22976, 13/5/2010, IKSHADOW-5203
# Delay for Loss Of Service alert
ro.mot.eri.losalert.delay=2000
# If time from last RoamInd change to SID change less than below, not play alert
ro.mot.eri.sidalert.delay=1000
# END IKSHADOW-5203
# Motorol,a6889c,02/Feb/2010,IKSHADOW-619
# Proximity Sensor feature
# 0 disable
# 1 enable
persist.mot.proximity.touch=1
# End IKSHADOW-619
# BEGIN Motorola, a22976, 25-Feb-2010, IKSHADOW-702, FID 31841
# VZW Requirement Specifications: NETWORK BASED PLUS CODE DIALING
# 0 disable
# 1 enable
ro.cdma.nbpcd=1
# END IKSHADOW-702
# BEGIN Motorola, a22976, 12-Mar-2010, IKSHADOW-1784, Power Up Tone
# Motorola, a22976, 12-Apr-2010, IKSHADOW-3298, Remove temporary power up tone
# BEGIN Motorola, wbdq68, 21-May-2010, IKSHADOW-3372, Turn ON Power Up Tone
# Motorola, a22976, 26-May-2010, IKSHADOW-6164, Remove power up tone to keep the same as Droid
#persist.mot.powerup.tone=/system/media/bootup.ogg
# END IKSHADOW-3372
# END IKSHADOW-1784
# BEGIN Motorola, a22417, 22-Mar-2010, IKSHADOW-2345,default data roaming is on
ro.com.android.dataroaming=true
# END Motorola, a22417, 22-Mar-2010, IKSHADOW-2345,default data roaming is on
persist.mot.a2dp.direct = 0
# System property for SMC
ro.service.start.smc=1
# BEGIN Motorola, a21951, 17-Apr-2010, IKSHADOW-3602
# 0 disable
# 1 enable
persist.mot.usb.mediasync = 1
# END Motorola, a21951, 17-Apr-2010, IKSHADOW-3602
#Proximity sensor debounce time
mot.proximity.delay=150
# disable touch below 60 pixels
mot.proximity.distance=60
# BEGIN Motorola, pkd348, 26-Apr-2010, ISHADOW-4035
# true Horizontal BUA is preloaded, not allow to install standalone version of BuA from Android Market
# false Horizontal BUA is not preloaded
ro.HorizontalBUA=true
#Proximity sensor debounce time
mot.proximity.delay=150
mot.proximity.distance=60
# BEGIN Motorola, pkd348, 26-Apr-2010, ISHADOW-4035
# true Horizontal VVM is preloaded, not allow to install standalone version of VVM from Android Market
# false Horizontal VVM is not preloaded
ro.HorizontalVVM=false
# BEGIN Motorola, a22976, 21-May-2010, IKSHADOW-5385
# For Shadow only, NOT applied to Droid2 as requirement different
ro.mot.buttonlight.timeout=0
# END Motorola IKSHADOW-5385
ro.mot.master_clear.shredsd=false
# BEGIN Motorola, pkd348, 09-July-2010, IKSTABLEONE-1236
# true enable the feature of In case of Emergency, default is false
# false disable the ICE feature
ro.mot.fid.29967.ice=true
# BEGIN MOTOROLA, vfhk68,24-July-2010, IKSTABLEONE-2469
# true enable the feature of 33531
# false disable the feature
ro.mot.fid.33531.keylock_ecm=true
#END
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.kernel.android.ril=yes
persist.ril.mux.noofchannels=7
persist.ril.mux.ttydevice=/dev/ttyS0
persist.ril.modem.ttydevice=/dev/ttyUSB0
persist.ril.features=0x07
persist.ril.mux.retries=500
persist.ril.mux.sleep=2
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=false
ro.default_usb_mode=0
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
ro.telephony.sms_segment_size=160
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.2_r5
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=1000
ro.url.safetylegal=http://www.motorola.com/staticfiles/Support/legal/?model=A855
ro.setupwizard.enable_bypass=1
ro.com.google.clientid=android-motorola
ro.com.google.clientidbase=android-verizon
ro.com.google.clientidbase.am=android-verizon
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.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.config.vc_call_vol_steps=7
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.com.motorola.smartsensor=true
ro.media.capture.maxres=8m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=60
ro.media.capture.flash=led
ro.media.capture.classification=classD
ro.media.capture.useDFR=1
ro.media.camera.focal=3564.0,3564.0
ro.media.camera.principal=1632.0,1224.0
ro.media.camera.skew=0.0
ro.media.camera.distortion=0.0,0.0,0.0,0.0,0.0
ro.media.camera.calresolution=3264,2448
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientid=android-motorola
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.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/MotoMB200/profile/MotoMB200.rdf
ro.build.version.full=Blur_Version.2.3.15.MB810.Verizon.en.US
ro.config.ringtone=Moto.ogg
ro.build.config.version=GAS_NA_GCXSHAD00VZW_P022
ro.build.config.date=Wed_Sep_01_21:13:04_-0500_2010
Last edited by ECFfighter7232; December 8th, 2010 at 12:09 PM.
The Following 2 Users Say Thank You to ECFfighter7232 For This Useful Post:
Thank you ECF.. I did the two changes I quoted in Upgrade from 2.3.9 Advice to reflect to the 2.3.15.. Repushed. Rebooted. and now I'm at the 2.3.15 as the version. Tried the update but as mentioned elsewhere it is possibly not available atm so time will tell.
Thank you ECF.. I did the two changes I quoted in Upgrade from 2.3.9 Advice to reflect to the 2.3.15.. Repushed. Rebooted. and now I'm at the 2.3.15 as the version. Tried the update but as mentioned elsewhere it is possibly not available atm so time will tell.
Laser
Can I do this on my phone somehow? I am not at home right now.
Or maybe attach your file? (this would be best as we could keep build edits from xda)
Device(s): Thunderbolt-I Haz the 4G's!
Girlfriend has my old Droid X
Thanks: 168
Thanked 345 Times in 210 Posts
hopefully that did the trick for you then. I'm dl'ing the system dump now (not sure which one though, just doin it for shits and giggles) to see whats in that build.prop
edit: nope, it was just all the apk files...
Last edited by ECFfighter7232; December 8th, 2010 at 12:30 PM.
Thank you ECF.. I did the two changes I quoted in Upgrade from 2.3.9 Advice to reflect to the 2.3.15.. Repushed. Rebooted. and now I'm at the 2.3.15 as the version. Tried the update but as mentioned elsewhere it is possibly not available atm so time will tell.
awesome! thats one down. now what about being deoxed? has anyone updated with that still in the phone?
Last edited by bobomatic; December 8th, 2010 at 12:31 PM.
Back to my original question for a moment... Sounds like the suggestion was to sbf to 2.1 then follow all the OTA upgrades? Are there update zip files available that would allow me to go upgrade from my current setup to the newest update?? Thanks!
Back to my original question for a moment... Sounds like the suggestion was to sbf to 2.1 then follow all the OTA upgrades? Are there update zip files available that would allow me to go upgrade from my current setup to the newest update?? Thanks!
If you are on 2.2, an SBF to 2.1 will brick your phone.
If you have a STOCK phone, rooted or not, and have a modified Build Prop, then your problem is related to incorrect information in the Build Prop that was circulating at various sites. The ZIP file above will cure that problem.
Motorola has pulled the update. It was only intended for certain test users - me included - but I missed my window of opportunity because of the Build Prop file.
If you have a installed a pre-release FROYO, then the posts suggest you SBF to 2.2, not 2.1.
Alright, I am a total newb when it comes to this stuff. I'm not rooted or anything like that but I am running the leaked Froyo. What is my best option to upgrade that wont brick my phone or erase all my stuff?
Last edited by Sideshowbob492; December 8th, 2010 at 09:52 PM.
Well, while the files did change my version number on the phone, there is evidently still something wrong with the file. I downloaded and tried to install the update - there is a link here on the main page of this site - installing the file indicated an error in build.prop.
So...two questions:
1) Does a factory wipe recreate an original build.prop file?
2) Does someone have an ORIGINAL, unmodified, same as new build.prop file?
Well, while the files did change my version number on the phone, there is evidently still something wrong with the file. I downloaded and tried to install the update - there is a link here on the main page of this site - installing the file indicated an error in build.prop.
So...two questions:
1) Does a factory wipe recreate an original build.prop file?
2) Does someone have an ORIGINAL, unmodified, same as new build.prop file?
Thanks.
Ditto: Just discovered this via above method myself.
Search that page for another link to the Droid X Back to Stock files, and search the page that loads for "back to stock". There are two zip files. One for "Deoxed" and one for "Odexed"
And, it sounds like Deoxed has something to do with Themes - and I've never done that, so while I'm downloading both files, I'll be using the Odexed file.
Last edited by jcarlosfox; December 9th, 2010 at 10:44 AM.
Reason: Figured out what deoxed means.
Search that page for another link to the Droid X Back to Stock files, and search the page that loads for "back to stock". There are two zip files. One for "Deoxed" and one for "Odexed"
And, it sounds like Deoxed has something to do with Themes - and I've never done that, so while I'm downloading both files, I'll be using the Odexed file.
If this breeds success for you, please post the working build.prop. Thanks
Motorola DROID X is an Android powered smartphone with a 1GHz processor, huge 4.3-inch display with 480x854 pixels resolution, 8-megapixel camera with 720p motion video capture and many other features. It's the newest addition to Motorola... Read More
Upgrade from 2.3.9 Advice
Just discovered this via above method myself.
