[Q] Origin of Cause Code 97 Problem - Thunderbolt Q&A, Help & Troubleshooting

Hello!
I got a new Thunderbolt a little over a week ago. I rooted it using Revolutionary v0.4pre4 and then flashed the newest versions of Imoseyon's leanKernel and CM7. It wasn't until afterwards that I attempted to make a phone call and discovered that Verizon couldn't authenticate my account. (Cause Code 97) Long story short, I ended up reverting back to stock Sense and getting a new authentication key after almost a week (the first tech I talked to didn't give me one). I would like to try CM7 and leanKernel again, but am extremely green with smartphones and am not sure how to diagnose which part of the process messed up my key. I really can't afford more downtime at the moment.
My question is: Could CM7 or leanKernel have caused my AKey problem? Has anyone else had the same experience with this ROM/kernel? (google only turns up one example of a CM7 user experiencing this problem)
I believe I heard it's possible for the phone to come that way from the store, and suspect rooting with Revolutionary could also have been the culprit. I would love to lay my fears to rest however (or confirm them I guess) before I give it another go.
Thank you guys in advance!

swod_woosh said:
Hello!
I got a new Thunderbolt a little over a week ago. I rooted it using Revolutionary v0.4pre4 and then flashed the newest versions of Imoseyon's leanKernel and CM7. It wasn't until afterwards that I attempted to make a phone call and discovered that Verizon couldn't authenticate my account. (Cause Code 97) Long story short, I ended up reverting back to stock Sense and getting a new authentication key after almost a week (the first tech I talked to didn't give me one). I would like to try CM7 and leanKernel again, but am extremely green with smartphones and am not sure how to diagnose which part of the process messed up my key. I really can't afford more downtime at the moment.
My question is: Could CM7 or leanKernel have caused my AKey problem? Has anyone else had the same experience with this ROM/kernel? (google only turns up one example of a CM7 user experiencing this problem)
I believe I heard it's possible for the phone to come that way from the store, and suspect rooting with Revolutionary could also have been the culprit. I would love to lay my fears to rest however (or confirm them I guess) before I give it another go.
Thank you guys in advance!
Click to expand...
Click to collapse
Learn ADB and use it to root. The easy way is not always the best way.
Sent from my Synergized Thunderbolt via XDA Premium App

Related

Help. Trying to update my Bolt to Gingerbread

Hi guys, I have a rooted Bolt currently running 1.70.605.0. I rooted when i got it back in May and since then I installed a rooted update of Froyo. The phone has been dropping network connection a lot lately that it's very aggrevating. I am thinking it may help fix my problem if I update to Gingerbread with the new radio.
i downloaded the file 2.11.605.3.zip from the TeamBamF.net site last night but now I am sort stuck. It's been so long since I rooted this phone so I kinda need some help. I search everywhere but haven't found a thread where there is like a step by step direction. If someone can provide me some assistance or point me to the right thread I would so much appreciate it.
Vince
The data dropping out may be due to some work/upgrades in your area ... call VZW to see if they know anything.
As far as updating to GB, my advice is tread lightly ... especially if you're just wanting a stock version of it. There are bugs, the biggest being voice mail notifications not working, that may drive you nuts. That being said, there are several custom ROMs around that have fixes/tweaks that make this plagued GB build VZW & HTC released much more manageable. Look around and there are a few "stock" custom ROMs out there - or if you prefer a totally different look/feel there are several Sense 3.0 ports to choose from too.
As far as a how-to guide, the best one I've seen is THIS ONE. Read it and get knowledge my friend
Happy flashing!
2.11.605.3.zip is the [gb] patch - "It changes camera libs, and some insignificant
framework, and apks." as stated on teambamf.net, i did read it is running smooth,
increased battery life but,with issues pertaining to vm notification error and front facing camera
upside down. i agree with Yank talk with carrier, im currently running dasBAMF Forever
kernel 2.6.35.10 stock radios have had no issues.
vinny2006 said:
Hi guys, I have a rooted Bolt currently running 1.70.605.0. I rooted when i got it back in May and since then I installed a rooted update of Froyo. The phone has been dropping network connection a lot lately that it's very aggrevating. I am thinking it may help fix my problem if I update to Gingerbread with the new radio.
i downloaded the file 2.11.605.3.zip from the TeamBamF.net site last night but now I am sort stuck. It's been so long since I rooted this phone so I kinda need some help. I search everywhere but haven't found a thread where there is like a step by step direction. If someone can provide me some assistance or point me to the right thread I would so much appreciate it.
Vince
Click to expand...
Click to collapse
Can you link me to that download? I would like to see exactly what you are making reference to before I comment.
Some of those update .zips are the full unrooted rom. You wouldn't want to flash that. You want to make sure and look for something like...
"Rooted Debloat Blah Blah Blah"
The link provided by Yank is a good one. #3 for "Flashing a Rom".
Also another hint (just in case you are unfamiliar with recovery). the camera buttons toggle up/down and the power button is used to make a selection. you can select "go back" by toggling to it and selecting it or you can use the soft back key.
hope that helps.
As to the voicemail issue, Eris has fixed that. Took him 30 minutes, he said.
Sent from my ADR6400L using Tapatalk
Did you read this?
http://teambamf.net/showthread.php/718-How-to-flash-a-ROM

[Q] Radio, which one is everyone using ?

Just curious on which radio everyone gets best results with ? I ran the mr3, 3.5 but it seemed to have a lot of data drop, so i reverted back to mr2.5 leak, this one used to be so reliable but now its acting just like the mr3s.. or maybe the network now has much more load but id still like to see wut everyone is running
I am using the one that came with the mostly stock (rooted and deodexed) official MR2 release (not leaked). This was before the one click rooting method came out so my phone is rooted the old fashioned way with the complicated engineering bootloader method.

Should I bring in my 3d to sprint to fix?

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

[Q] freezes! help pleaseee

Hi everyone, I've been having serious problems and if anyone can help me I'd love you forever. I got a rezound a week ago and loved it. I decided to root and rom it and afterwards my screenwould randomly freeze. I tried every GB rom and no matter which rom I was on it would freeze
I thought maybe my phone was defective so I returned my phone and got a brand.new.resound. once I installed.inef on my new phone it started freezing again. No apps loaded just stock inef. Could it be my sim card? Any help would be greatly appreciated.
mforminio7 said:
Hi everyone, I've been having serious problems and if anyone can help me I'd love you forever. I got a rezound a week ago and loved it. I decided to root and rom it and afterwards my screenwould randomly freeze. I tried every GB rom and no matter which rom I was on it would freeze
I thought maybe my phone was defective so I returned my phone and got a brand.new.resound. once I installed.inef on my new phone it started freezing again. No apps loaded just stock inef. Could it be my sim card? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Is it an actual freeze or is Sense crashing? I saw that a lot when I still had a ROM with Sense. If you're hitting home but not going anywhere then that's probably the case. No real cure for it other than to try unlocking and tossing another ROM on. You could also have something wrong with your SD. Pull that out for a while and see if the freezing/crashing still occurs.
You said no apps loaded so I assume you didn't restore any data from another phone either?
I've been running Ineffabilis for a month now without that issue so it shouldn't be the ROM. What happens after the freeze? Do you have to reboot or does it go away? (I don't know why I'm asking that cuz I don't know how to fix it no matter what your answer! But I like pondering and the more info the better for when someone more knowledgeable comes by.)
You could also try flashing a different kernel and see if that helps. I just put on AnthraX and it's running nice and smooth.
MrSmith (that feels so formal after all these months, I might have to call you Smitty now ), or anyone else... would there be an error log generated somewhere that could be looked at?
mforminio7 said:
Hi everyone, I've been having serious problems and if anyone can help me I'd love you forever. I got a rezound a week ago and loved it. I decided to root and rom it and afterwards my screenwould randomly freeze. I tried every GB rom and no matter which rom I was on it would freeze
I thought maybe my phone was defective so I returned my phone and got a brand.new.resound. once I installed.inef on my new phone it started freezing again. No apps loaded just stock inef. Could it be my sim card? Any help would be greatly appreciated.
Click to expand...
Click to collapse
I think the problem is in the kernel and not the rom. I had issues with gingerbread rom/kernel combinations. What are you using to control your CPU? Just making sure you aren't using more than one app, but since you didn't mention that you may not be adjusting clock speed at all.
I would recommend flashing an ICS leak and Sebastians modified kernel and seeing how that does. It's not as stable as an OTA but I don't see problems with random reboots and freezes on ICS even when overclocked to 1.7.
Hi guys thanks for the replys. Its not the kernel or rom because I've tried every gb kernel and every gb rom and my problem still persists. And I've swapped out dif SD.cards as well so I'm really scratching my head lol. Could it be the sim card? I think it needs to be hardware related but my last resound had the same issue but the sim is the same. And when it freezes I mean the screen just stops updating. You can press the buttons but the screen will stay frozen until a battery pull. Thanks!
maybe go get a new phone if u say u have tried all those things?
mforminio7 said:
Hi guys thanks for the replys. Its not the kernel or rom because I've tried every gb kernel and every gb rom and my problem still persists. And I've swapped out dif SD.cards as well so I'm really scratching my head lol. Could it be the sim card? I think it needs to be hardware related but my last resound had the same issue but the sim is the same. And when it freezes I mean the screen just stops updating. You can press the buttons but the screen will stay frozen until a battery pull. Thanks!
Click to expand...
Click to collapse
Yeah, see about getting a new SIM from Verizon then and see if that works since that's the only constant.
Just got a brand new rezound yesterday.. returned my last rezound for the same issue but they used my old sim. Idk what could be causing it
Make them give you a new SIM.
feralicious said:
Make them give you a new SIM.
Click to expand...
Click to collapse
Yea Ill pick one up tonight and update the thread. Hopefully that's the problem. Thanks for the suggestions fera
Didn't solve my problem.. I'm really out of ideas at this point and its so frustrating BC the phone is sick
I would try running the RUU and bring it back to stock and see what happens.
Yes I would also recommend relocking and installing the latest RUU and see what it does. If it persists you will be stock unrooted and should be able to have them replace it under warranty.
Sent from my ADR6425LVW using Tapatalk
I actually think the cause of my lockups were due to some buil.prop edits. Does anyone have the debug.sf.hw=1 gpu tweak in their rom? And if so are you experiencing any lockups? I ahve used the RUU and everything was fine but all these roms look to yummy to stay away from lol

[Q] Can't receive texts (weird situation), can it be Leedroid tweaks?

I don't want to turn this into a blaming thing, but just looking to rule out some possibilities.
I have the stock rom with chad's kernel and leedroid tweaks (flashable zip). I'm on the 2.17 version too, but baseband that was previous to it because I had texting issues with the newest baseband.
The problem is, without warning and without doing anything (no new apps, no new mods, etc) I will stop receiving text messages. I have to dial a phone number and when the call connects, I get my texts. I have to have tech support push something to the phone to fix it, but it lasts maybe a week or 2 before it craps out again...
I didn't have this happen until I did go back to a stock rom and put leedroid tweaks on (rather than I think Eternity Rom at the time?). I thought it was Sprint being sprint for a while... I tried going back to full stock (as in data wipe too), but that didn't resolve it. Now, my texts were already broken when I tried that, so that might not have said much. But since I didn't have texts working on full stock, I didn't connect it to leedroid.
Now, my brother, about a month later, did the same thing. He flashed a rom (but can't remember which) then leedroid tweaks because they weren't a part of it. He has the Evo 3D too. After flashing leedroid, he mentioned having issues receiving texts... I just don't know if this is coincidence or if there's something to this.
I don't really see what flashing that mod could do to break my texting, but my knowledge of this sort of thing is pretty limited. Is this even possible? Is someone else having or had similar problems like this?
EDIT: After talking with tech support, and since this has been an on-going issue, they are rebuilding my text messaging service from scratch, or something along those lines. Said it would take a while, so I don't know if it worked yet. But if this means anything to someone, I'm curious.
gk1984 said:
I don't want to turn this into a blaming thing, but just looking to rule out some possibilities.
I have the stock rom with chad's kernel and leedroid tweaks (flashable zip). I'm on the 2.17 version too, but baseband that was previous to it because I had texting issues with the newest baseband.
The problem is, without warning and without doing anything (no new apps, no new mods, etc) I will stop receiving text messages. I have to dial a phone number and when the call connects, I get my texts. I have to have tech support push something to the phone to fix it, but it lasts maybe a week or 2 before it craps out again...
I didn't have this happen until I did go back to a stock rom and put leedroid tweaks on (rather than I think Eternity Rom at the time?). I thought it was Sprint being sprint for a while... I tried going back to full stock (as in data wipe too), but that didn't resolve it. Now, my texts were already broken when I tried that, so that might not have said much. But since I didn't have texts working on full stock, I didn't connect it to leedroid.
Now, my brother, about a month later, did the same thing. He flashed a rom (but can't remember which) then leedroid tweaks because they weren't a part of it. He has the Evo 3D too. After flashing leedroid, he mentioned having issues receiving texts... I just don't know if this is coincidence or if there's something to this.
I don't really see what flashing that mod could do to break my texting, but my knowledge of this sort of thing is pretty limited. Is this even possible? Is someone else having or had similar problems like this?
EDIT: After talking with tech support, and since this has been an on-going issue, they are rebuilding my text messaging service from scratch, or something along those lines. Said it would take a while, so I don't know if it worked yet. But if this means anything to someone, I'm curious.
Click to expand...
Click to collapse
Thanks for the call to receive tip man! I frequently will stop getting texts randomly and it sucksssss. I carry around my Ipod with me and just send a text to my phone if I think I'm not getting texts. It is quite annoying sumtimes...
also im running mean rom v3.0 with leedroid tweaks and chads latest kernel
Swyped from mah 3vo!
I have been running leedroid tweaks on meanrom for a few weeks now with no issues. Do you use the stock messaging app, or something downloaded from the market?
I currently using Leedroid Tweaks and AnthraX kernel.
Im not having any issues so my guess is sprint fault since it happened even after you went back to Stock.
Thanks guys. I'm not sure what exactly fixed it... It could have been the rebuild thing they said they were doing or it was me flashing a custom rom. I have since flashed back to the setup I had before but everything still working. Oh well, was just really frustrating.
Sent from my PG86100 using XDA
dyep8ball03 said:
I have been running leedroid tweaks on meanrom for a few weeks now with no issues. Do you use the stock messaging app, or something downloaded from the market?
Click to expand...
Click to collapse
it happens to me on both....
dyep8ball03 said:
I have been running leedroid tweaks on meanrom for a few weeks now with no issues. Do you use the stock messaging app, or something downloaded from the market?
Click to expand...
Click to collapse
Sorry I kinda missed this post. I use the stock messaging app. Tried go sms pre once to see if that could resolve it. Same problem though.
Either way, it's working again now. The question is for how long...
Sent from my PG86100 using XDA

Categories

Resources