SS 5.4 won't allow me to use chevyno1 tools?

[Oxymoron]

So this is weird. Tried to open chevyn01 tools and got this error. The only thing I've done since the last time I used chevy tools is switch from the ulv 800 kernel to the lv 1.1 kernel.


*customized tapatalk signature*

[ChevyNo1]

So this is weird. Tried to open chevyn01 tools and got this error. The only thing I've done since the last time I used chevy tools is switch from the ulv 800 kernel to the lv 1.1 kernel.


*customized tapatalk signature*

The ONLY way that could possibly happen is if something borks the build.prop - which my kernels would not do. Are you sure you didn't install anything else?? If you believe you haven't - send me your /system/build.prop to chevyno1.droid@gmail.com and I'll take a look ...

[Oxymoron]

You know what.... I did. I forgot that I edited the build.prop to change the lcd density. I changed it back right after, but I wonder if when I made the first change it made a backup, and that's somehow screwing it up. I'll double check... and post back.

*customized tapatalk signature*

[Oxymoron]

ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Sun May 29 17:29:15 EDT 2011
ro.build.date.utc=1289367602
ro.build.type=user
ro.build.user=chevyno1
ro.build.host=chevyno1-ubuntu
ro.build.tags=release-keys
ro.product.model=Droid
ro.product.brand=verizon
ro.product.name=voles
ro.product.device=sholes
ro.product.board=sholes
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=sholes
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=voles-user 2.2.1 FRG83D 75603 release-keys
ro.build.fingerprint=verizon/voles/sholes/sholes:2.2.1/FRG83D/75603:user/release-keys
# end build properties
#
# system.prop for generic sdk
#

rild.libpath=/system/lib/libmoto_ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240

# Default network type.
# 4 => CDMA / EVDO.
ro.telephony.default_network=4

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

# 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=28m
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.f eedback
ro.setupwizard.enterprise_mode=1
ro.com.google.clientidbase=android-verizon
ro.com.google.locationfeatures=1
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=20 00,0,0,120000,180000,540000,960000
ro.config.vc_call_vol_steps=7
ro.cdma.otaspnumschema=SELC,1,80,99
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.media.dec.jpeg.memcap=20000000
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
keyguard.no_require_sim=true
ro.rommanager.developerid=ChevyNo1
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=Simply Stunning 5.4
ro.kernel.android.checkjni=0
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

# Begin SimplyStunning Settings
default.color=white
ro.compcache.default=18
# End SimplyStunning Settings

I just remember I changed the boot animation too, but I don't think would matter, would it?

*customized tapatalk signature*

[Oxymoron]

Umm... like, bump.... and stuff.

*customized tapatalk signature*

[spc_hicks09]

Umm... like, bump.... and stuff.

*customized tapatalk signature*

Changing certain stuff in the build prop will make ChevyNo1 Tools think that you are running a ROM other than S.S.

You need to add the following lines to your build prop just above where yours says:
ro.build.version.sdk=10

Add the following:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRG83D
ro.build.display.id=Simply Stunning v5.4 Built from Source Code - 05-31-2011
ro.build.version.incremental=75603

Add those lines to your build.prop and you should be good to go. If you need anymore help just let me know!!!

[Oxymoron]

Thanks buddy, I'll do this in a little bit. I'm at work now... got to wire a few things. I appreciate the feedback. I didn't know what the entire build.prop was supposed to look like, so I didn't have anything to compare mine to.

Thanks again!

*customized tapatalk signature*

[ChevyNo1]

Thanks spc_hicks09 ... I have been busy and unable to get to the email that was sent ...

[Oxymoron]

Thanks again guys. ChevyNo1 Tools back in action. This is why I love this ROM, and forum.... the support.

I learn something new on here every day. Much appreciated!

*customized tapatalk signature*

[spc_hicks09]

Thanks spc_hicks09 ... I have been busy and unable to get to the email that was sent ...

Hey not a problem man. I got yer back! Lol

Sent from my Droid using DroidForums