Database Info

[Q] self resetting thunderbolt woes?

yes i flashed a rom quite a few days ago- did a wipe on everything -rom loaded everything runs find ... twisted sense 1.5 with kernel that comes with sorry for my spelling trying to figure out whats going on anyway back to the problem at hand
im having issues were i could be doing anything on my tb all of a sudden it resets to the htc loading screen im like ok just a minor thing but it is now getting on my nerves i feel like i might of done something wrong yet im very cautious on how i flash rom using rom manager and its up to date of course. so i was thinking should i change it back to stock to see if that might cure my reset woes ? or just unroot and take it back ? any suggestions are helpful

This seems to be a known issue and is related to the new radio. Did you flash that?

*** UPDATE ***
I reverted back to...
-baseband verison
1.02.00.0103_2r
-kernel ver.
2.6.32.21-gb05544a [email protected] #1
tue mar. 1
-build number
1.12.605.6 CL338893 release-keys
-still rooted with S-on instead of S-off
Still doing the reset here and there...

yes i did flash the radio

Try reverting your radio back to stock (there is a thread in the Dev section) and see if it helps. I have been having this issue too, but it isn't bothering me enough right now to change it. Also I'm not sure if you can use the new framework with the old radio -- you may have to use an older ROM.

thats what im going to try

I have the new radio and I have never experienced resetting with any of the roms, etc. I might just be one of the lucky ones!

- thanks for rubbing it in -lol
Thats good...
i might be considering taking my tb back to get another if this doesnt work

lol my TB is stock and restarted 4 times by itself yesterday

crazed_z06 said:
lol my TB is stock and restarted 4 times by itself yesterday
Click to expand...
Click to collapse
do you have the new radio ? or out of box stock?

cjmcmillion said:
*** UPDATE ***
I reverted back to...
-baseband verison
1.02.00.0103_2r
-kernel ver.
2.6.32.21-gb05544a [email protected] #1
tue mar. 1
-build number
1.12.605.6 CL338893 release-keys
-still rooted with S-on instead of S-off
Still doing the reset here and there...
Click to expand...
Click to collapse
ok-
baseband changed to - 1.16.00.0223r
kernel changed to 2.6.32.21-gb05544a [email protected] #1
sat feb 19th
s-on and no longer rooted
hopefully no more resets if so im returning for another tb...
not giving up on a great device

cjmcmillion said:
ok-
baseband changed to - 1.16.00.0223r
kernel changed to 2.6.32.21-gb05544a [email protected] #1
sat feb 19th
s-on and no longer rooted
hopefully no more resets if so im returning for another tb...
not giving up on a great device
Click to expand...
Click to collapse
Damn that was harsh! lol really the first thing should have been to try a different kernel. It has become known with the tb they are not all created equal. Kernels or I should say switching them can make a big difference.

LeoD said:
Damn that was harsh! lol really the first thing should have been to try a different kernel. It has become known with the tb they are not all created equal. Kernels or I should say switching them can make a big difference.
Click to expand...
Click to collapse
yes i tried those before hand...but decided hey lets do a fresh start
which i reverted back to stock since i do enjoy the rooting process
in which i followed the ....
[ROOT] PermRoot + Unlock Bootloader - Safer/Easier 4/21/2011
http://forum.xda-developers.com/showthread.php?t=996616
followed by installing the radio on this thread the top...
Flashed -> CDMA Radio version: 1.16.00.0402w_1
LTE radio version that came with 1.13.605.7...
Thanks To Adrynalyne -
[RADIO] The Obligatory Thunderbolt Radio Thread
http://forum.xda-developers.com/showthread.php?t=1045081
Then i Installed the Rom Twisted Sense 1.5 running
kernel 2.6.32.21_bamf_4.42 which everything is running
smooth like silk now....Thanks Hedney3!!! Pick the Rom up here >>>>
http://forum.xda-developers.com/showthread.php?t=1040413
i suggest picking up the battery calibrator and ZDbox in the
market -

Well my problem with resetting still exisits i returned to stock now
i seem to still be having this problem...
so hopped over to verizon to speak with someone about this and they
told me this was a functionality of the phone that they could send
me a replacement out but would cost me shipping and handling and also
stated if they didnt find anything wrong with it that i would have to
pay full retail !!! i was like BS *&^&&%^%^ *^%^%$&^$% well you get
the point.
i still have the same tbolt just trying to figure out what to do now was thinking of returning for another tbolt but fear
that this so called " functionality " of the phone ... any suggestions?

my phone was fine until I decided to flash the new radio. I reverted back to stock radio and I'm still getting reboots

yes same here i told verizon about my tbolt self resets like once every hour if im on it they told me it was a part of the functionality of the tbolt

My old one did that.
My old TBolt did that, kind of like resetting the Sense interface (which takes forever). I called them and talked with a really nice guy, and he explained a hard reboot should fix it (which didn't and I lost my call, and got connected with a capital B the next time around _-_)
I also was having issues with the memory card getting "wiped" (data still there, just not viewable in phone) and (the kicker) my phone would reach temperatures of 69degC while charging, while off.
That last one had them change it out right quick.

No automatic resets at all here, and I've had it on and using it most of the time throughout the LTE outage and after. No resets when on EvDO/HRPD; no resets when on LTE/eHRPD; no resets when on EvDO/eHRPD. It only resets when I tell it to!
As for the connection, well... I do get the occasional dropout on LTE. More problems tonight than most nights with that. But EvDO seems to be pretty stable as always.

i didnt have any problems during the outage since im not in a 4g lte area

cjmcmillion said:
yes i tried those before hand...but decided hey lets do a fresh start
which i reverted back to stock since i do enjoy the rooting process
in which i followed the ....
[ROOT] PermRoot + Unlock Bootloader - Safer/Easier 4/21/2011
http://forum.xda-developers.com/showthread.php?t=996616
followed by installing the radio on this thread the top...
Flashed -> CDMA Radio version: 1.16.00.0402w_1
LTE radio version that came with 1.13.605.7...
Thanks To Adrynalyne -
[RADIO] The Obligatory Thunderbolt Radio Thread
http://forum.xda-developers.com/showthread.php?t=1045081
Then i Installed the Rom Twisted Sense 1.5 running
kernel 2.6.32.21_bamf_4.42 which everything is running
smooth like silk now....Thanks Hedney3!!! Pick the Rom up here >>>>
http://forum.xda-developers.com/showthread.php?t=1040413
i suggest picking up the battery calibrator and ZDbox in the
market -
Click to expand...
Click to collapse
Just a FYI for you, I do not have problems with reboots nor do I have most problems most say they are having, however my tb just did not like twisted sense 1.5. For me anyway I couldn't stay on it very long.
I have an idea if you want to give it a try. it will take some time and effort but on the other hand it just might save you the trouble of having to return your tb.
First, do a full wipe of data/cache, do it twice to be sure. flash BAMF, (either one don't matter). once you boot up go to settings/SD & phone storage and do a factory reset. let it reset and come back up. it will take a while to boot and you might even get errors which is ok.
Now hit the power button and reboot into recovery again wipe data/cache 3x, wipe cache 3x.
now try to install your rom. just for the heck of it at least for now stay away from twisted sense. I would use BAMF at least till you see if this solves your problem.
once you have your rom installed flash imoseyon's (SAFE) kernel.
If you do try this let me know how you make out. This has solved many issues for me in the past many times.
actually I stand corrected it was NOT twisted sense that gave me a problem it was tesla coil that I had problems with. so your choice there.

[Q] No cell after 2.3.6 (and many attempts to fix it)

ok here goes, first off, i apologize if this is in any way redundant to someone's else question. with the amount of people whose phone got wrecked with the 2.3.6 update im sure somebody has had the problem im having.
like many people i just clicked "install" when google pushed the 2.3.6 ota. my phone was running 2.3.4. rooted. when it rebooted, i was greeted with the android exclamation mark.
i happened to have a clockwork backup so i tried restoring my backup. and restore it did, but not the radio. after the google update my radio was something like NO GSXXK1 or so. i tried the radio fix here:
http://forum.xda-developers.com/showthread.php?p=14564429&mode=linear#post14564429
i tried reflashing the stock 2.3.3 rom from google, wiping the bootloader and all. ive in fact tried many many things that ive read on xda and google forums.
now, ive managed somehow to have a running 2.3.4 with cell signal. using the efs file copy method in he link above. that restored my 3g and ability to place phone calls but sms arent working. i did the *#*#4636#*#* thing and notice that smsc is 00, i tried to set to the right value of +17057969300 for Rogers canada but all i get is an update error followed by a crash.
and now, funny, my search button is acting weird, like an eye that keeps twitching.
im not very knowledgeable in this stuff, just enough to get by and install custom roms but clearly im in over my head now.
why did copying my 3 efs file in the root of the sd card restore signal? i dont think these files really belong there, so just what the heck happened?
is there a way i can restore my nexus S to google stock rom when they shipped the phone? i mean, a complete wipe, sd, boot, radio...everything.
if i can start back with the stock phone, i can re-root again and start fresh.
any ideas please??
im physically tired of reading everything, misleading information and constantly flashing back and forth hoping its gonna work. oh and mandatory angry comment: thank you google for effing up my phone!
edit:
the only stock rom i tried i the 2.3.3 stock update available in clockwork. made no results.
current specs:
my phone is a i9020a
current baseband : NO DGSXXKD1
current build: GRJ22
android ver: 2.3.4
core: 2.6.35.7-ge382d80 [email protected] #1

Follow my last thread posted
Sent from my Nexus S using xda premium

Thanks dude, i had actually done that and did manage to get a signal back. its SMS that just wont work and when do the INFO thing to set the right value, i either get update error or a crash.
i installed stock rom 2.3.4 and install radio uckd1. that made my signal work even without having to move the efs files on the root of the sdcard. but still no sms.
is anybody else getting sms problems? this was working before the 2.3.6 fiasco.
im with rogers canada, in ottawa.

ok, just to loop the loop on this one and hoping it will be of use to somebody else.
my sms issue wasnt related to my phone at all, once i had a signal back, that's as far as the phone was concerned.
i placed a call to rogers to let them know i couldnt sms anymore.
long story short, they tried many things but ultimately, its doing the "hard" reset on the network for my phone that did it. im sure there a better name for it but basically they erased my phone from their network, i had to wait about an hour for the change to propagate. when i powered the phone back, it resynced everything and sms was back online without a single thing to do.

[Q] Clicking sound during calls after nvflash

I had previously ran some custom ROMs (Cyanogen, etc) on my G2x, but this past year I had gone back to the stock 2.3.4 ROM. I did leave my phone rooted.
Recently I had decided to give my phone to someone else and wanted to do a factory reset to get rid of my info.
I followed the steps on the T-Mobile support site.
I held down on the volume while turning it on.
After a second I got the "S/W Upgrade" screen.
I left my phone alone for a while, but the screen never went away. After unhooking it my phone seemed bricked.
I followed the following guide to fix it and it restored my phone to 2.3.3:
http://forum.xda-developers.com/showthread.php?t=1248644
The phone seemed to work fine, but all of a sudden I started hearing clicking.
I decided to try to update to 2.3.4, but my phone is a refurbished phone and won't do the OTA update.
I downloaded the LG driver and tool to try to update, but it said my phone already had the latest update. It detects my software version as V21Y when it's actually V21e.
Here is more of my phone info.
Model number:
LG-P999DW
Android version:
2.3.3
Baseband version:
M6600A-SCAUTNZ-2.0.9720T 1 [MAR 11 2012 10:00:00]MP:TRUGLE_08.09.02R_MDM
Kernel version:
2.6.32.9
Build number:
GRI40
Software version:
LG-P999-V21e
Any help would be appreciated. Thanks.

Flash this in CWM to fix the audio: http://www.mediafire.com/?8spjkaknyg5bd30
You have the 2.3.3 software installed which doesn't have the audio files working for the baseband that comes with the 2.3.4 update

xBkKx said:
Flash this in CWM to fix the audio: http://www.mediafire.com/?8spjkaknyg5bd30
You have the 2.3.3 software installed which doesn't have the audio files working for the baseband that comes with the 2.3.4 update
Click to expand...
Click to collapse
Hey. Thanks for the reply.
Is there a way just to flash a working 2.3.4 rom?
Also, when I install this fix, do I just keep the files zipped and keep it at the root of my sd card when I run CWM?
I've been following step-by-steps so my grasp of the flashing process is tenuous at best.

Yes just pick select zip from external sd and flash away.

Cannot make phone call after flashing s4 RUU (Europe version)

"com.android.dialer has stopped unexpectedly" shows every time i try to call.
this happened after i ran 4.1.1 RUU (europe version). however, i switch back to Tmobile version, still counter the same problem.
my phone:
- Tmobile version S4 HTC One S
- S-OFF w/ superCID (11111111)
- now running CM10.1 (phone call features works on this but not on any RUU)
i really want to switch back to official RUU since i get used to sense interface instead of android native.
please suggest! thanks a million!!!

Did you restore any apps, like with TB or ROM toolbox?
Sent from my One S using xda app-developers app

oLEFTo said:
"com.android.dialer has stopped unexpectedly" shows every time i try to call.
this happened after i ran 4.1.1 RUU (europe version). however, i switch back to Tmobile version, still counter the same problem.
my phone:
- Tmobile version S4 HTC One S
- S-OFF w/ superCID (11111111)
- now running CM10.1 (phone call features works on this but not on any RUU)
i really want to switch back to official RUU since i get used to sense interface instead of android native.
please suggest! thanks a million!!!
Click to expand...
Click to collapse
You might want to try running the RUU again, since it might be a one-off thing.

usaff22 said:
You might want to try running the RUU again, since it might be a one-off thing.
Click to expand...
Click to collapse
i have ran RUU at least 4 times already.
still got the same result. sigh...

What about downloading one of the RUUs again. Do any custom ROMs work?

usaff22 said:
What about downloading one of the RUUs again. Do any custom ROMs work?
Click to expand...
Click to collapse
i tried viper also...still doesn't work.
i will try to re-download the ruu...wish me luck!

Did you run this one?
ya, seems to be a version for the S One SE if you read through the thread...
So return to latest JB RUU and check for the JB OTA then. You should also perform a full wipe from custom recovery before.

[Issue] Wifi will not turn on? Running Stock rom.

Alrighty here is the deal. Just got the phone today (5/21/2014)
What I've done so far:
S-off
flash supersu.zip
flash defaultteather
disabled cdrom
insecure kernal mod (for rom toolbox)
Unoffical CWM
Software information:
Android 4.4.2 (Obviously)
Sense 6.0
Software number 1.55.605.2
Kernal Version: 3.4.0-g2e0a4a7
[email protected]#1
smp preempt
I have tried a catch/davlik wipe, about to try a full data wipe.
Any help on this one would be great, if the full wipe fails and I dont hear anything today I may just try and flash ViperOneM8 1.6.0 and see if it works or if my phone is just defective. I ordered it off amazon no contract for 650$ so no warrenty except for HTC's Advantage.
Thanks guys,
-Derrick

Quick update
So just a fast update since I just got home and flashed my new lovely sexy phone. I flashed CleanRom + Advanced Power Menus + Social Intergration addon and hey guess what? Wifi was already on and connected to my 5.0ghtz network just fine. If anyone else is having this same issue, idk which one of the mods messed up the wifi part on stock but just s-off and flash a rom.
Anywho, problem semi-solved for now. No idea what caused it or why, seems like Im the only person who had this issue.