145 replies to this topic

[irishpride]

This definitely makes me feel a lot more comfortable about maybe trying out the official version, thanks P3 and TBH!

[Sponsored Links]

• Back to top

[928Droid]

validoption said:

Isn't the stock odexed OTA 2.3.15? Or did I miss something? I just want to be sure.

What he said ^^^^^ Confused as how getting back to the older leak 2.3.13 is "Stock" when current OTA is 2.3.15 ???

I noticed all the 2.3.13 chatter on Twitter, but thought it was typos....maybe not.

Regardless, still TONS better than a Bootlooped DX, and once you get to 2.3.13 you should be able to get back to 2.3.15 with ADB or custom Update.zip.

To Team Black Hat please consider making a 2.3.15 version of this to avoid confusion and having mismatched systems scattered everywhere.....besides, us newbs get confused enough as it is.... add into the mix, "I got 2.3.13 ...or is it 2.3.15" will confuse us newbs even more when looking for compatible Themes and/or ROMs. :-) It makes support for those super smart cool Themer and Romer Dudes so much harder :-) Heck us newbs frustrate them enough as it is with all the same questions over and over....adding "will this work with 13 and 15... or just 13.... or just 15" to all the other same ole repeated questions.....well, .it could make them go grey a lot quicker...and have to increase their meds even more....poor guys :-)

Thanks again to P3 and Team for a Droid X 2.2 "ANTI-BL solution" very much needed and VERY much appreciated!!

Keep up the great work!!!

[p3droid]

YOu should all check your posts, everyone who received the OTA should be on 2.3.13...That is the version our phones are on.

[kgbrown247]

p3droid said:

YOu should all check your posts, everyone who received the OTA should be on 2.3.13...That is the version our phones are on.

actually it is Version.2.3.15.mb810.verizon.en.us from ota. i checked my x and my wifes as well

Edited by kgbrown247, 23 September 2010 - 06:34 AM.

[Mark_Venture]

p3droid said:

YOu should all check your posts, everyone who received the OTA should be on 2.3.13...That is the version our phones are on.

Are you sure?

Per ->

Please Login HERE or Register HERE to see this link!

Verizon is pushing Version.2.3.15.MB810.Verizon.en.US/BP _ C _ 01.09.07P.

I know 2.3.13 was the first leak... and 2.3.15 leaked recently as well, so yeah it gets confusing.

[928Droid]

p3droid said:

YOu should all check your posts, everyone who received the OTA should be on 2.3.13...That is the version our phones are on.

I know you have been very busy doing all this cool stuff for us...but sorry, the Offical OTA is 2.3.15 NOT 2.3.13...at least according to Motorola/Verizon Documention and my Phone and everyone else's I know that got it the official OTA way :-)

I know you are much yonger than me...but surely yours eyes aren't already going bad like mine are` :-)

Motorola Website Froyo update Documention.....

Please Login HERE or Register HERE to see this link!

Verizon Froyo update Documentation and installlation documents...

Please Login HERE or Register HERE to see this link!

Please Login HERE or Register HERE to see this link!

BTW, WalMart sells Reader Glasses ...real cheap!!!

Sorry, couldn;t resist, you know how much I appreciate what you do, and thanks again!!!

BUT, PLEASE make a 2.3.15 system SBF for us lucky people that got the REAL update!!! :-)

[avlfive]

kgbrown247 said:

actually it is Version.2.3.15.mb810.verizon.en.us from ota. i checked my x and my wifes as well

After running the .sbf, that is my version number. 2.3.15.mb810.verizon.en.us

[kgbrown247]

so you have successfully used the sbf provided here?

[avlfive]

kgbrown247 said:

so you have successfully used the sbf provided here?

Read the post above yours again.

[928Droid]

FYI,

Here is the untouched build.prop (attached below, remove the .zip) that was installed with my OTA update at 7am eastern yesterday... maybe this will help.

Text from OTA Build.prop:

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=VZW

ro.build.display.id=VZW

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=55

# 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 = 45


# 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=30m

# 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=450

# 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=450

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=1

# 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=3000

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=DroidRollin.ogg

ro.build.config.version=GAS_NA_GCXSHAD00VZW_P022

ro.build.config.date=Wed_Sep_01_21:13:04_-0500_2010

Attached Files

•  build.prop.zip   8.19K   21 downloads

[kgbrown247]

[/QUOTE][/QUOTE][quote name='avlfive']Read the post above yours again.[/QUOTE]

you didnt specificaly say what sbf and with all the bricking going on, i am not about to assume wtf you are referring to!!!! lol, i would like to make sure before i delve back into customizations. just coverin my ashlo

Edited by kgbrown247, 23 September 2010 - 07:25 AM.

[928Droid]

avlfive said:

After running the .sbf, that is my version number. 2.3.15.mb810.verizon.en.us

IF the build.prop is not included in the P3's "System SBF", that doesn't mean anything at all...could just be reading from your original BP that didn't get replaced with the SBF.... as seen from my last post, a build.prop is just text, we can easily edit it to say anything, doesn't mean you have all or any of the 2.3.15 files. Only the pros like P3 and other ROM Devs could verify if the files are from 13 or 15. In reality I doubt there is any real differences between the system/app and system/framework files of 13 and 15, but just in`case there is, I prefer everything to match. The stuff in all the other system folders is honestly still a mystery to me (OK, not including the Media and Fonts folders, I'm not that dense :-), so I am sure something had to have changed there between the 2 versions.????

[AndroidX]

Once again I am amazed. An custom SBF is released so people who have gotten their devices stuck at the boot logo can successfully recover their device and people are complaining that its not good enough. Simply amazing!!! Maybe it was better when you were stuck an the M logo. Be thankful that you can fix it and quit bitching. I mean WTF... How about they pull it and say screw us unappreciative SOB's

[javroch]

I'm also curious, if this is the 2.3.15 update, if we can simply use this System SBF to upgrade from 2.1 without it upgrading the bootloader / kernel / signatures / etc. I'm not sure if that would work, but this way we could even still downgrade to 2.1 for the time being no?

I'm also curious what types of things this System SBF would NOT fix. So, that I can have at least a list to start of things to make sure not to do.

Edited by javroch, 23 September 2010 - 07:36 AM.

[AndroidX]

Don't you people have something better to do than f***ing b***h about s**t!!! This actually really pisses me off. If I was stuck on M I wouldn't give a f**k what it took to resurrect my device!

Edited by Andrew, 23 September 2010 - 05:46 PM.

[avlfive]

928Droid said:

IF the build.prop is not included in the P3's "System SBF", that doesn't mean anything at all...could just be reading from your original BP that didn't get replaced with the SBF.... as seen from my last post, a build.prop is just text, we can easily edit it to say anything, doesn't mean you have all or any of the 2.3.15 files. Only the pros like P3 and other ROM Devs could verify if the files are from 13 or 15. In reality I doubt there is any real differences between the system/app and system/framework files of 13 and 15, but just in`case there is, I prefer everything to match. The stuff in all the other system folders is honestly still a mystery to me (OK, not including the Media and Fonts folders, I'm not that dense :-), so I am sure something had to have changed there between the 2 versions.????

This could very well be the case. So if p3droid is saying that it's .13 and not .15, I'm gonna take his word for it since he posted the files.

So even though my version says that, I probably am on .13, and thanks for bringing it to my attention.

[avlfive]

AndroidX said:

Once again I am amazed. An custom SBF is released so people who have gotten their devices stuck at the boot logo can successfully recover their device and people are complaining that its not good enough. Simply amazing!!! Maybe it was better when you were stuck an the M logo. Be thankful that you can fix it and quit bitching. I mean WTF... How about they pull it and say screw us unappreciative SOB's

^^^^
This!

[avlfive]

kgbrown247 said:

you didnt specificaly say what sbf and with all the bricking going on, i am not about to assume wtf you are referring to!!!! lol, i would like to make sure before i delve back into customizations. just coverin my ashlo

So if you're worried about covering yourself, you MUST have been smart and read the whole thread, right? If you did, you'd find it very clear that I ran the .sbf a couple of times due to problems and was finally successful in doing so.

Edited by avlfive, 23 September 2010 - 07:47 AM.

[quadjacks]

I plucked the OTA update from the cache and instead of allowing the update, I renamed the file and used the old procedures to update to the OTA, if that makes any since. So my question is, since this SBF is 2.3.13, then after I SBF, I can just use the old update procedures to get back to 2.3.15, correct?

[javroch]

javroch said:

I'm also curious, if this is the 2.3.15 update, if we can simply use this System SBF to upgrade from 2.1 without it upgrading the bootloader / kernel / signatures / etc. I'm not sure if that would work, but this way we could even still downgrade to 2.1 for the time being no?

I'm also curious what types of things this System SBF would NOT fix. So, that I can have at least a list to start of things to make sure not to do.

Not complaining, I'm very thankful.. just curious ^