Rooted Bolt Trying to Force Update

garyhesq1

Well-known member
Mar 5, 2011
57
1
8
Visit site
Guys, my bolt is rooted with a stock ROM. Last night I woke up to see my screen on and in the Clockwork menu. I rebooted and now it it boots up, shuts down and as best as I can tell is trying to install the new update. I don't want it right now as I don't have time to reroot, install a custom ROM and rebuild the phone. I deleted the update.zip off the SD card and that didn't help. Is there a way to get it outa the reboot loop?

Edit: I wanted to add that is does actually throw up the shutting down screen so something is telling to do that.
 
Last edited:

BattleSwine

Well-known member
Jun 29, 2011
498
30
0
Visit site
Guys, my bolt is rooted with a stock ROM. Last night I woke up to see my screen on and in the Clockwork menu. I rebooted and now it it boots up, shuts down and as best as I can tell is trying to install the new update. I don't want it right now as I don't have time to reroot, install a custom ROM and rebuild the phone. I deleted the update.zip off the SD card and that didn't help. Is there a way to get it outa the reboot loop?

Edit: I wanted to add that is does actually throw up the shutting down screen so something is telling to do that.

Cyberwarrior's top post. Can you copy the string he's looking for? It should allow for the edit you need to stop OTA. I'm not sure about the loop....
 

yodatom10

Well-known member
Mar 20, 2011
1,754
209
0
Visit site
Can u get into recovery mode. If yes u can go in and make a backup of your current rom. And then all you have to is reroot and restore your backup. If the phone has all ready download the ota and trying to install it chances of u being able to stop it are very slim.
 

garyhesq1

Well-known member
Mar 5, 2011
57
1
8
Visit site
Yes I can get into recovery. So I will do that procedure and then and run the string that Cyber Warrior mentioned. Thanks!! That will save me some time!
 

shakeyblack

New member
Apr 3, 2011
1
0
0
Visit site
Ok mine is doing the same thing but its taking me to the clockwork mod recovery screen, what do I do from there?
My phone will boot up, and for about 15 seconds its normal, then it just shuts down?:(
 

BattleSwine

Well-known member
Jun 29, 2011
498
30
0
Visit site
Ok mine is doing the same thing but its taking me to the clockwork mod recovery screen, what do I do from there?
My phone will boot up, and for about 15 seconds its normal, then it just shuts down?:(

Do you have a Nandroid of you current ROM? you should be able to use volume rocker to select it (recovery) power button "enter". This should get you back to where you were (temporally I'm afraid). Cyber Warrior is working on the actual fix.
 

garyhesq1

Well-known member
Mar 5, 2011
57
1
8
Visit site
Welcome to the club. I just did a ROM backup, restore to factory settings and the phone booted and ran fine. I then did a restore of the ROM and the shut down problem came right back. I might try restoring an old ROM back up and then seeing if MyBackup Pro can get me back where I was....
 

BattleSwine

Well-known member
Jun 29, 2011
498
30
0
Visit site
Just an FYI, I have my phone up and running again. I checked the build.prop file and there is no line of text that matches the description in the link.

Nothing with release keys? Or may be it's looking for build number? Any way you can copy to a post? Not sure how big it is....
 

garyhesq1

Well-known member
Mar 5, 2011
57
1
8
Visit site
Below is my build.prop file. I caught the phone counting down to a reboot/update. It gave me the option to delay it and made me put in a time. I have till 5PM. I am going to watch it and see if it lets me delay it again....

ro.ril.oem.ecclist=112,911
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.def.agps.mode=6
ro.com.google.clientidbase=android-htc
ro.com.google.clientidbase.yt=android-htc
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.vs=android-verizon
ro.com.google.clientidbase.gmm=android-verizon
ro.com.google.clientidbase.ms=android-verizon
# begin build properties
# autogenerated by buildinfo.sh
ro.com.google.clientidbase=android-verizon
ro.build.id=FRG83D
ro.build.display.id=FRG83D
ro.build.version.incremental=338893
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=?…* 2?œˆ 26 22:27:28 CST 2011
ro.build.date.utc=1298730448
ro.build.type=user
ro.build.user=root
ro.build.host=HPA008
ro.build.tags=release-keys
ro.product.model=ADR6400L
ro.product.brand=verizon_wwe
ro.product.name=htc_mecha
ro.product.device=mecha
ro.product.board=mecha
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
ro.build.product=mecha
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=1.12.605.6 CL338893 release-keys
ro.build.description=1.12.605.6 CL338893 release-keys
ro.build.changelist=338893
ro.product.ua=
ro.build.fingerprint=verizon_wwe/htc_mecha/mecha/mecha:2.2.1/FRG83D/338893:user/release-keys
ro.build.project=174685
ro.product.version=1.12.605.6
keyguard.no_require_sim=1
# end build properties
#
# system.prop for mahimahi
#

ro.sf.lcd_density=240

debug.fb.rgb565 = 0

#+from QCT Fusion
rild.libpath=/system/lib/libril-qc-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=
persist.rild.ril.bva=0
persist.rild.ril.ltedr=0
persist.rild.ril.ltedrtable=max_retries=infinite,10000
persist.rild.ril.adminAPN=vzwadmin
DEVICE_PROVISIONED=1
debug.sf.hw=1

#
# system props for the cne module
#
persist.cne.UseCne=false
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.be.ge.sqi.min=0
persist.cne.be.ge.sqi.max=100
persist.cne.be.umts.sqi.min=0
persist.cne.be.umts.sqi.max=100
persist.cne.be.hspa.sqi.min=0
persist.cne.be.hspa.sqi.max=100
persist.cne.be.1x.sqi.min=0
persist.cne.be.1x.sqi.max=100
persist.cne.be.do.sqi.min=0
persist.cne.be.do.sqi.max=100
persist.cne.be.wlan.sqi.min=0
persist.cne.be.wlan.sqi.max=100

#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=16
persist.data_netmgrd_mtu=1428

#
# system props for telephony modules
#
#device supports LTE
ro.config.lte=true
#device supports EHRPD
ro.config.ehrpd=true
#device supports simultaneous 1x voice + LTE
ro.config.svlte1x=true
#-from QCT Fusion

# Default network type.
# 8 => CDMA/EVDO/LTE auto mode preferred.
ro.telephony.default_network=8

wifi.interface=eth0
wifi.supplicant_scan_interval=15

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

# For the default value of agps
ro.ril.def.agps.mode = 2

# For emmc phone storage
ro.phone_storage = 0

#
# This file describes the media capabilities and profiles
# using system properties.
#
# Note: The property key and value has some length
# limit as defined by PROPERTY_KEY_MAX and
# PROPERTY_VALUE_MAX, respectively
#
# WARNING: We may not use system properties for specifying
# media capabilities and profiles in the future
#
ro.media.enc.file.format = 3gp,mp4
ro.media.enc.vid.codec = m4v,h263,h264
ro.media.enc.vid.h263.width = 176,1280
ro.media.enc.vid.h263.height = 144,720
ro.media.enc.vid.h263.bps = 64000,6000000
ro.media.enc.vid.h263.fps = 1,30
ro.media.enc.vid.m4v.width = 176,1280
ro.media.enc.vid.m4v.height = 144,720
ro.media.enc.vid.m4v.bps = 64000,6000000
ro.media.enc.vid.m4v.fps = 1,30
ro.media.enc.vid.h264.width = 176,1280
ro.media.enc.vid.h264.height = 144,720
ro.media.enc.vid.h264.bps = 64000,6000000
ro.media.enc.vid.h264.fps = 1,30

# For FOTA setting (leave empty value to use default)
ro.htc.checkin.url = http://andchin.htc.com/android/checkin
ro.htc.checkin.crashurl = http://andchin.htc.com/android/crash
ro.htc.checkin.url_CN = http://andchin.htccomm.com.cn/android/checkin
ro.htc.checkin.crashurl_CN = http://andchin.htccomm.com.cn/android/crash
ro.htc.checkin.exmsg.url = http://fotamsg.htc.com/android/extra/
ro.htc.checkin.exmsg.url_CN = http://fotamsg.htccomm.com.cn/android/extra/
ro.config.htc.nocheckin = 1

# Release Bluetooth HW/SW information
ro.bt.chipset= Broadcom BCM4329-B1
ro.bt.version= Bluetooth 2.1 + EDR
ro.bt.stack= Broadcom BTL-A
ro.bt.stack.version= 2.0.50.032
#0x10000010010100101000011 represent bt profile list
ro.bt.profiles= 4270403

# Properties of BTLA stack
service.brcm.bt.activation = 0
service.brcm.bt.srv_active = 0
service.brcm.bt.hcid_active = 0
service.brcm.bt.btld = 0
service.brcm.bt.btld_pid = 0
service.brcm.bt.avrcp_pass_thru = 0
service.brcm.bt.avrcp_toggle = 1
service.brcm.bt.btport_redir_on = 1

#Welly_Fang
ro.cdma.home.operator.numeric = 310012
ro.cdma.home.operator.alpha = Verizon
ro.htc.device.slot1 = RUIM

# jerry.pj_chen [Start]20100730 For Verizon data retry
ro.cdma.data_retry_config = max_retries=infinite,0,0,60000,120000,480000,900000
ro.com.android.dataroaming = true
# jerry.pj_chen [end]20100730 For Verizon data retry

# For opensense sdk
ro.htc.common.version = 2.0.0.0

# Set Horizontal VVM = true and HorizontalBUA = true for Incredible#C/Lexikon/Mecha Verizon build
# Then Verizon VVM/BuA program can check this property to known if there is a Native VVM/BuA in ROM
ro.HorizontalVVM = true
ro.HorizontalBUA = true



#
# 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.networklocation=1
ro.setupwizard.mode=DISABLED
ro.config.ringtone=QuietlyBrilliant.mp3
ro.config.notification_sound=Zeta.mp3
ro.config.alarm_alert=NewDay.mp3
ro.config.cal_notification=Epsilon.mp3
ro.config.msg_notification=Gamma.mp3
ro.setupwizard.mode=OPTIONAL
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.com.google.clientidbase=android-verizon
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.2_r9
media.a1026.nsForVoiceRec=0
htc.audio.alt.enable=1
htc.audio.hac.enable=1
ro.media.codec_priority_thumb=so
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
--
Gary
 

garyhesq1

Well-known member
Mar 5, 2011
57
1
8
Visit site
I just double checked how I renamed that file. I had a space between the period and the BAK. Would that have prevented it from stopping OTA? If so, now do I need to retstore my old ROM again and then rename that file all over or, since I fixed it will the OTA not take place? I caught it at 5PM and told it to hold off till tomorrow.
 

Members online

Trending Posts

Forum statistics

Threads
942,957
Messages
6,916,660
Members
3,158,750
Latest member
CrisBowles513