Ive just about had it with the resets like crazy ive had this tbolt for more then 30 days i know thats way pass the 14-day mark but im just curious would they let me exchange it out for a different android device just curious
Have you considered you have a bad device? Maybe you should exchange it first? (got another tb I mean).
I would say try and get a different thunderbolt. I don't know if they do this yet but back in the day when I was rocking the blackberry your. I had about 3 your replacements that were "bad" and finally offered me the bold. I think you need to go threw 3 device or more of the same and then they will let you get something else
Sent from my ADR6400L using Tapatalk
i was thinking about getting it replaced with another tbolt just fear i may get another in the same manner in which mine is in... ive did hard resets till i was blue in the face- pulled the battery tons of times... i want to love this device but just isnt flowing right
for me my motorola droid was the champ compared to this wish i didnt sell it now
Are you rooted? Did you flash any radios?
Sent from Verizon in Phoenix, AZ, running a rooted Thunderbolt, with Lightning Rom v3.3.1 / Adrynalyne 4.4.3
yes i was rooted at one time and yes i did flash the new radio but ive reverted back to out of box stock un-rooted with s-on stock kernel and radio -
Ive had mine a month, rooted and running bamf. No problems. Have 4g when im in 4g area. U may have a bad device
Sent from my ADR6400L using XDA App
cjmcmillion said:
yes i was rooted at one time and yes i did flash the new radio but ive reverted back to out of box stock un-rooted with s-on stock kernel and radio -
Click to expand...
Click to collapse
Have you experienced any more reboots?
Sent from Verizon in Phoenix, AZ, running a rooted Thunderbolt, with Lightning Rom v3.3.1 / Adrynalyne 4.4.3
Sounds like you just have a bad device. I'm rooted running BAMF 1.6 and the newest radio. I've never had a reboot.
Related
I'm new to the Thunderbolt world. Previously learned all I know from my old OG Droid. Then relearned all from my Droid X. Now on a tbolt. Learned all about this now. Currently running das bamf 1.6.3 and loving it. Sure would love gingerbread but unsure how daily cm7 is.
Anyway my question is this whole bit about radios. I read thru the radio thread and many others but still unclear as to what/which I should be running. I took a screenshot of my settings/about page that shows my current radio.
I'm not in a 4g area. I have not had a single reboot since i got the phone 13 days ago. Been running bamf since 9 days ago. from what i can tell, I'm on the old radio but thats where i get confused. this thread http://forum.xda-developers.com/showpost.php?p=13093559&postcount=1 has different setups and i'm unsure of what one to go with or if it is even necessary to change anything.
Any help would be great. I've been a lurker here for over a year but never needed any help until now. got to get my post count up haha. Thanks guys.
pitchblack86 said:
I'm new to the Thunderbolt world. Previously learned all I know from my old OG Droid. Then relearned all from my Droid X. Now on a tbolt. Learned all about this now. Currently running das bamf 1.6.3 and loving it. Sure would love gingerbread but unsure how daily cm7 is.
Anyway my question is this whole bit about radios. I read thru the radio thread and many others but still unclear as to what/which I should be running. I took a screenshot of my settings/about page that shows my current radio.
I'm not in a 4g area. I have not had a single reboot since i got the phone 13 days ago. Been running bamf since 9 days ago. from what i can tell, I'm on the old radio but thats where i get confused. this thread http://forum.xda-developers.com/showpost.php?p=13093559&postcount=1 has different setups and i'm unsure of what one to go with or if it is even necessary to change anything.
Any help would be great. I've been a lurker here for over a year but never needed any help until now. got to get my post count up haha. Thanks guys.
Click to expand...
Click to collapse
You're on the old radio, if you look in the baseband in the screenshot yours ends in r which is the stock version. The new one ends in w_1.
Im like you, i don't have 4G available to me either. I flashed radios and all i got was reboots. Flashed back to stock radio, reboots stopped, but tethering went to ****. I flashed the 2nd or 3rd radio down on the radio thread, an so far i have not had any reboots. So if its not broke, don't fix it, but if you must try the radios, do it in consecutive order down the list til you find one that works.
I really like the second radio from the top, it seemed to help my GPS lock on faster and I have a better signal. I also had issues of random reboots with the leaked new radio, so far with the second one on that page no reboots and increased performance.
Thanks guys. That's what I figured. Everything is working perfect...gps, calls, even 4G just worked driving thru easton pa. Nice to have everything working but addicted to this stuff lol.
Maybe I'll just leave well enough alone for now. Very happy with the tbolt but would love to see 2.3.3 or .4 with sense. Loving bamf remix but missing gingerbread from my Droid X. Damn phones. Wish I could have multiple haha.
Sent from my ADR6400L using Tapatalk
Figures. Soon as I go getting cocky, my gps starts acting up. If I go to Maps, it finds me just about instantly. However if I go to navigation and click maps or driving directions, it says searching for gps. After 2 minutes I just backed out of it. Nuts.
Gps (first time I tried navigation on 1.6.3) worked perfect on 1.6.1. Why would it come up instantly on maps but not nav? Damn. Downloaded all the posted radios. Hoping I didnt have to use any...
Sent from my ADR6400L using Tapatalk
Flashed all listed in link. Gps still says searching on every radio. Going with link 1 for now and see how it goes.
The last link in the link I posted is the stock radio/baseband, correct?
Sent from my ADR6400L using Tapatalk
I flashed the first radio on the list but it didn't update my LTE radio. Any thoughts why?
Unsure. I'm currently on the radio in link 1. Going great. Unsure of LTE changing. I don't have 4g here so I can't test if and how it works. Not sure how you check which LTE radio I have anyway... sorry I can't be more helpful.
Sent from my ADR6400L using Tapatalk
No matter what I do.. the software and build number don't change.
Thanks for the response.
Just got the Gingeritis Rom, which is a 2.1 sense 2.3.4 gingerbread Rom, and getting the radio to work properly was a pain.
Just noticed my 6 bar reception in Bamf changes from white and full at my house to none periodically. Seems like it does out for a second. Maybe time for stock kernel again...
Sent from my ADR6400L using Tapatalk
pitchblack86 said:
Flashed all listed in link. Gps still says searching on every radio. Going with link 1 for now and see how it goes.
The last link in the link I posted is the stock radio/baseband, correct?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Credit goes to: kejar31 over at XDA
(I didn't write this, but i cant find the thread that I found it in)
Download and flash the ImproveGPSlock.zip found here:
http://www.mediafire.com/?7ujg6lws6k8cosj
Hi.
I am about to unroot and go back to otb stock. I am wondering if anyone knows for sure when the random reboots that I, and several others encounter, first started because I need to know whether to do the OTA after I go back to stock.
From my memory....... :
Wasn't there 2 OTA's?
And the random reboots started after installing the 2nd one?
So should I just install the first one.......orrrr......does it automatically only give one OTA direct to the 2nd one released?
Or should I not install any OTA's at all and patiently wait for Gingerbread........
Thanks!
We have MR1, MR2, and MR2.5 but I think only MR1 was an official OTA (dont quote me on it tho since I have been rooted since I got the phone and have never received an OTA). I think the reboot issue has been a problem for a lot of people for the entire time and isnt a new thing. IIRC MR1 caused quite a few reboot issues but not for everyone. I personally ran w/o any reboots until I got to 2.5 and even then I have only ever had 1. Its just what works best for you.
You will be waiting patiently for quite a while for official GB from what I have heard on the boards but you can always try out some of the GB ROMs that we have already.
Beastclaw said:
We have MR1, MR2, and MR2.5 but I think only MR1 was an official OTA (dont quote me on it tho since I have been rooted since I got the phone and have never received an OTA). I think the reboot issue has been a problem for a lot of people for the entire time and isnt a new thing. IIRC MR1 caused quite a few reboot issues but not for everyone. I personally ran w/o any reboots until I got to 2.5 and even then I have only ever had 1. Its just what works best for you.
You will be waiting patiently for quite a while for official GB from what I have heard on the boards but you can always try out some of the GB ROMs that we have already.
Click to expand...
Click to collapse
You are correct Beast there has only been one official OTA. My wife is not rooted but I am
Well I went back to stock because I was gonna try to go to Verizon today and swap it out.....
I find it funny this exactly what I was going to ask today myself. I'm also running bamf remix 1.8, have tried all the radios and even installed bamf 2.0 for GB with the Mr 2.0/2.5 radios. Still got reboots. Now I want to go back to stock and unroot so I can go back to the store and swap it
Just wonder if its worth it, maybe if they let me swap SD cards
I just un-rooted my phone about two days ago. After, I did the OTA update. I hadn't seen any problems until today. I live in a 4G area and work in a (up until Monday) 3G area. Since Monday they have been testing out a 4G tower. I have had 4G until this morning, I just figured that they were still testing it out and had switched it off. Well, about an hour ago I got my first Reboot. When the phone came back up I noticed that the 4G had just came back on. I'm pretty sure that's what triggered my reboot. So in short, as long as they keep the 4G going I don't have any issues.
Just curious is the update worth doing? And if i do it do i go ahead and install the GB bamf rom and radio? or just go back to my current 1.8 remix?
im curious what you guys have your phones overclocked at? I am rooted on the RC3 bamf 3.0 and the only time I have seen reboots is when i had my phone overclocked to high. now that im at 1.42 on the bamf cpu (I disabled my setCPU) and it has been solid.
So I have gotten a 3d 2 weeks ago as a replacement through asurion for my broken evo 4g and like most people on xda it is only natural to root it and slap on a rom the second you get your hands on it. I checked the hboot and to my hearts content it was 1.4, and easy as cake to root since I was coming from evo 4g. The dilemma is that I have tried several roms and everyone I have loaded would give me random reboots and eventually it would just keep rebooting as soon it loads to the home screen. Realizing maybe if I just loaded it back to stock it would help. The random reboots have cut down but I still get it and it's really frustrating. I have checked the battery and it is not loose, and at this point I don't know what to do. I realize that if I go to the sprint store I have to be able to show them the problem. I am also worried that they will update my hboot to 1.5 and claim that I didn't update system software and just send me on my way. Anyone experiencing the same symptoms as mine? Should I just bring it in to sprint to see if I can get a new one?
Thank you
Sent from my PG86100 using Tapatalk
They will update it I suggest you use a format all zip and flash a haus stock rooted ROM or run a ruu hour that works the got me that way updated my phone cause it was over heating
Sent from my PG86100 using Tapatalk
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Yeah I loaded the RUU on it and turned S-off back on. Just sucks because when it doesn't random reboot or bootloop it works great.
Sad Panda said:
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Click to expand...
Click to collapse
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Is your battery loose?
I thought I had this problem at first too but I just popped a business card behind the battery and Viola no random reboots
Sent from my PG86100 using xda premium
bakarus said:
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Click to expand...
Click to collapse
Not a problem at all, that is what the community is all about. Free exchange of information, open source advancement of the platform and technology. Everyone gives a little, and takes a little.
I know there is a dialer code that works to give you that information without the need to install any application, or the need for root access, but after lots of research I was unable to find which one would give that info. However, there is a very useful app that you might want to have anyway. It is called "elixir 2", available on the market for free. Once installed, information > click"processor" > more information > processor: (mine says: ....rev. 2 (v71))
Let us know what yours says [for curiosity sake] please
Quick note, if you replaced the phone through asurion and try to replace it doesn't sprint, don't they refer you back to asurion?
Sent from my PG86100 using xda premium
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
kpsingh said:
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I requested then not to and they still did the update
Sent from my PG86100 using Tapatalk
So just an update, I finally decided to bring it in store today with it rooted and s-off. I was just so sick and tired of it randomly rebooting I just walked into the Sprint store. Technician brought it in, updated the hboot 1.5 =*(. I checked bootloader, and of course I see the locked in capital letters, but I am still s-off. Does that mean I can still load TWRP and root it? Or do I have to follow the HTC method to root it? Thanks for all the help guys!
If it still says s-off, i believe you are good! but that sounds odd, because otherwise we should all be able to update are hboot after rooting? If anyone knows about this...but anyway...
It was not the hboot upgrade but the firmware upgrade that you needed. You did not have to take it to sprint to do that, they have the firmware update without hboot flooting around the dev threads. 2.3.4 and above roms require the new firmware or you'll get the problems you had. No that you have the firmware a lot of the more cutting edge roms still get reboots with most advanced kernels, you have to watch your rom kernel combo, or stick with the stock kernel.
As for flashing, if you really are s-off still, then you can flash anything you want just like on the ol 4g Let us know. Lucky bastard, have fun
[edit] Found this a few threads down:
"I did what you did, had 1.40 and flashed the wrong update, got 1.50 LOCKED with S-off. You can still flash ROMs and Kernels with no issues. I just had to reload TWRP recovery. Then I flashed the 1.40 Bootloader and all was well.
You can grab 1.40 and flash from here: http://forum.xda-developers.com/show...eng+bootloader
***To others reading this...do not flash this, unless you are S-OFF with 1.50 hboot***
You do not need to UNLOCK using the htcdev method. Just flash the 1.40 hboot and you will be fine."
So reinstall twrp, flash 1.40, and have 1.40 s-off and flash the good way
Yep just flashed old hboot 1.3 and merrily rooted, so far so good running cleanrom 2.9 and taking sad panda's advice trying to figure out if it's app related. I am suspecting that it is groove ip running in the background. So far just installed cleanrom and added tapatalk and SwiftKey
Sent from my PG86100 using Tapatalk
Hey guys,
Havent been on in a while, now im confused and need some help. Ive been running Shiftsense 1.4X since it was released months ago before DroidTheory vanished. i feel my radio is starting to act up now that big red flipped the 4g switch in my area. i came to look for an update rom to run, but now everything is different. It appears the radios are separated now and ive never flashed them that way and i just need a little advice on getting my phone back up to date. Any help is appreciated. Thanks in advance!
bking_soda said:
Hey guys,
Havent been on in a while, now im confused and need some help. Ive been running Shiftsense 1.4X since it was released months ago before DroidTheory vanished. i feel my radio is starting to act up now that big red flipped the 4g switch in my area. i came to look for an update rom to run, but now everything is different. It appears the radios are separated now and ive never flashed them that way and i just need a little advice on getting my phone back up to date. Any help is appreciated. Thanks in advance!
Click to expand...
Click to collapse
You can still find them together if you search hard. If you cant, just flash them one at a time after renaming, thru bootloader. Its really pretty simple. Several good roms out thsre. Eternity is fantastic with sense 3.5 and beats, shiftsense is awesome also, gingerbread rock is the latest leak stripped down and rooted, i keep it on my sd card for when i need that basic rom. Make sure you update your radios first. The mr4 3.0 leak and thunderstick fullblown are also great roms. Good luck dude.
Sent from my ADR6400L using XDA App
Does anyone happen to have a link to the most recent radios paired up as one flash through bootloader? I can't seem to find one. I'd really prefer flashing them separately last resort. Just a comfort thing I guess.
bking_soda said:
Does anyone happen to have a link to the most recent radios paired up as one flash through bootloader? I can't seem to find one. I'd really prefer flashing them separately last resort. Just a comfort thing I guess.
Click to expand...
Click to collapse
I dont, but there just as easy to flash seperatly.
Sent from my ADR6400L using XDA App
http://forum.xda-developers.com/showthread.php?t=1048128
There is a newer radio than what is shown in that thread, look for the 2.11.605.9 radios.
Hey guys. Little new to the TBolt crew here.
I've been rooting for a bit. Did an HTC Hero, a DROID Eric, an Incredible... Now I've got a TBolt sitting here that I just rooted about an hour ago. It was running 4G just fine both before and after the root, but after installing a CM7 ROM (SFK's to be precise) I haven't seen 4G pop up since. I've tried a couple other CM7 roms, but nothing seems to make a difference - it only runs on 3G.
I was thinking it might be a radio problem, but admittedly I'm pretty novice with this stuff. I just flash what sounds interesting, and if it's not as stable as I'd like I find something else to flash. Does anyone have any ideas what's wrong? And what I can download to fix it?
EDIT: After giving up and deciding to go back to my backup of "stock" that I'd just made... now it's failing to properly back up. This wonderful error about data being corrupted with the only button available being "I'm Feeling Lucky" and still no 4G, only 3G. Now I'm at a complete loss.
I have a Nexus sitting next to me clearly connected to 4G just fine, so I know it's not a network issue. What the heck is going on here?
I'm sure you have, but never know... have you checked your wireless network settings?
Settings--Wireless & Networks--Mobile Networks--Network Mode.
Make sure LTE/CDMA is selected.
Sent from my ADR6400L using xda premium
most roms are built with a specific radio in mind i would try to flash one of the newer radios they work better drain less battery and are more compatible with rooted roms.