Verizon Killed my TBolt

Definitely cannot blame Verizon for what happened to your phone. They don't recommend rooting devices and rooting it at your own risk. Like mentioned, when you root you need to make sure you don't have future updates set to go. Updates from the carrier can't be done on a rooted phone.
 
If its working, then the first thing you need to do is to turn off the updates. If you are rooted you need to download Root Explorer from the Market. Then, using RE, you need to go to system/etc/security and look for a file named otacerts.zip, in Root Explorer at the top change the directory to R/W and then change otacerts.zip to otacerts.zip.bak, then change the permissions back from R/W to R/O and close Root Explorer.

Now you will have time to look around and find a custom rom that appeals to you. I found one for myself this morning put in on my TB.

Good Luck!

File Expert will do the same thing - and is free. :) I am running the latest 2.11 leak but did this just in case. Also, I have the boot loader on perm unlock. :)
 
Definitely cannot blame Verizon for what happened to your phone. They don't recommend rooting devices and rooting it at your own risk. Like mentioned, when you root you need to make sure you don't have future updates set to go. Updates from the carrier can't be done on a rooted phone.

how about if i rooted then when i ran the exe to upgrade to 2.10.605 it unrooted my phone,, will that recieve updates
 
how about if i rooted then when i ran the exe to upgrade to 2.10.605 it unrooted my phone,, will that recieve updates

I doubt it, a bunch of us installed the leaked MR2 upgrade back in June and then we never received the official one. We had to manually install the official RUU. It must check to see if you are running the software version they expect, which for the next OTA would be the 1.70 MR2.
 
I finally selected CL3ANTH3ORY v1.2. Really nice rom, really stupid name!

Very clean debloated rom, so far, everything works (get candystor to upgrade wifi tether) and it runs nicely. Too any roms have what I consider a bunch of kiddie stuff for backgrounds and "looks". I'm not a kid, I don't want my phone to look like an overamped kids version of star wars. I love playing with my phone but I also need it to work and to work well. I am a business person who runs my own business and if I'm meeting with other business owners or professional type person I don't want to turn on my phone and have near naked women, red flashing thunderbolts or other type stuff on my phone. YMMV!

I couldn't agree more. I thought I was the only one left who still valued function over form.
 
I doubt it, a bunch of us installed the leaked MR2 upgrade back in June and then we never received the official one. We had to manually install the official RUU. It must check to see if you are running the software version they expect, which for the next OTA would be the 1.70 MR2.

is there a way to reroot my TB with 2.10.605 and keep the rom, or even not keep the rom
thanks for any help you can offer even though you did not get TB yet(sorry) . i have funny feeling you have allready researched TB so you can play when you do
 
Good info in this thread, I had the error this morning and had to do a restore (clockwork) to get it working again.
For those who don't have Root Explorer, here's how I disabled OTA via ADB (omit the >$#, obviously).
Code:
>adb shell
$ su
# cd /system/etc/security
# mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
# mv otacerts.zip otacerts.zip.bak
# mount -o remount,ro -t ext3 /dev/block/mmcblk0p25 /system
# exit
$ exit
 

Latest posts

Trending Posts

Forum statistics

Threads
957,101
Messages
6,971,482
Members
3,163,719
Latest member
annahernandez51