every few hours my fuze becomes super slow, and power cycling it resets the phone back to factory settings, aka hard reset.
so i have found out by vigorously searching the forums, that my internal storage may have some corrupt sectors that i need to deal with using RAPHDIAG.nbh
it seems i must have this file on my sd card and then hard reset the phone and it will go about reformatting the internal storage after which i can reload the rom - IS THIS CORRECT? i have never done this before.
also my case is stuck to my phone so i cannot remove my sd card, in which case if i do said procedure, can i then active sync to reflash a good rom onto my phone? if not should i load the rom onto the card as well before hand so then i can use the flash by sd card method?
please help i need to get my phone working asap.
DId you try installing an official build and then going back to the cooked ROMs? That solved it for me long time ago..
no i did not. i was too impatient so i went ahead with the raphdiag.nbh, which took about 4 seconds to flash the nand. after that i reloaded tael, and it seems a bit faster and hasn't hard reset in the 4-5 hours that it normally does.
if it does this again, i might revert to the stock and then redo the custom rom procedure.
thanks and i will keep u updated.
Hope it works out for you.
A similar thing happened a flash and a couple of hard resets solved it for me.
Happened to me also a long time ago with one of the first NRG Roms.. The cure to my problem was flashing back to a stock AT&T rom and then reflashing the new rom you have again.. Hope this helps
i have to say the xda community is the most helpful i have ever seen, and for that.. kudos community, kudos.
so far i have reformatted the nand to fat using the raphdiag.nbh, and it seems as though that made the phone faster, and has been successful in solving the problem for this 1 day, i'll probably not customize my phone for a few days until im sure its fixed, or else its a trip to stock and back.
PS
since it made my general operation faster, im wondering if its any harm to keep fat formatting the nand on a regular basis before every new rom flash that i do on there? would that damage the system any?
also we need to document this raphdiag.nbh procedure so that people dont have to hunt for hours and then take a shot in the dark figuring out how it works (it took me 20 minutes to realize there was a selectable operation on screen)
weird things happened today morning again. going to revert to stock and then back.
im assuming i dont have to go to the stock spl, just the rom and radio.
Related
OK, Heres the scenario, This is a replacement T-959 vibrant, sent from either TMO or Samsung, really not sure! My 1st phone never had any issues with modding, and always cooperated! Until I used KIES to update one day and It bricked, because of primary and SBL corruptions. [I know!!, found out 5 mins too late about using KIES] Anyway, since Ive had this replacement phone its done nothing but fight me from the start, never has acted right I think and I feel there's something wrong HW wise with it. My problem with it now, is it wont accept any other custom ROM I try to install, and only works with either 2.1 or 2.2 stock OEM ROM's. Meaning, Anything else ROM wise, It wont go past the last part of boot sequence, and just keeps looping, and does it over and over again! Ive tried all of Simple Honeys, Toxic 8's Roms, and each time it goes thru the loading successfully, and then starts it boot-up, but every single Flash Ive done, ROM wise, it hangs up and loops at the very last part of booting up. Ive come to realize now, it isn't the ROMS, but the phone " I THINK" Each time I tried a Custom ROM install, I started with stock fresh JFD install, and wiped and cleared out everything before starting another ROM install, but with each attempt that I try to go past anything other than Froyo stock, It does this boot loop problem at the final part!! It seems like who ever sent it to me, did something to the phone to prevent this. Modding it I mean. like right now I'm on Eugenes Froyo, with the 2E RECOVERY, It was working fine, until I upgraded the Eugenes kernel, which is suppose to work with this ROM, technically the phone still runs, but as soon as I did this, I now cant get into the two drives as mass storage to tranfer files, says insert disk, like as if its a CD Rom drive, WTF!! And like I said, this phone wont accept any other ROMS now, past stock Eclair or Froyo OEM and kernels as well. I don't understand what the problem is, My guess is they flashed something to prevent modding or its just a corrupted HW issue, anybody ever seen this before. I wish I had just JTAG'd my first phone with Josh over at Mobile Tech, and saved myself all this heartbreak and frustration, but its too late for that now! So anyway, I need to determine for sure if this phones screwed, HW wise or if there is SW to get this phone straighten out, to where it'll work right like my first one used to, and begin to accept custom ROM's like it should be able to do!! I'm at my last end with this phone, and I'm desperate to get a solid reason/answer for whats happening here, because Ive followed all the instructions and standard procedures to insure that all the attempted installs of the ROMS I mentioned go correctly. And its boiling down to either HW issues or a SW issue they created before they shipped it to me, or last but least hopefully a SW fix here, that can get the HW/phone to act right again, and maybe salvage this phone, otherwise I'm thinking I need to buy another brand new phone and hope for the best. I just don't want to be stuck and limited with Froyo stock, for the rest of my time using this phone, I want my freedom to choose again, like I had before, and also It ran so much better than OEM anyways!
Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data
Sent from my SGH-T959 using XDA App
Quote" Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data"
If you had picked up on it in my post, have already done this dozens of times!! Oh and BTW, when at JFD = 2.1 Eclair, it wont allow the 2 drives access to in Cabled USB mass storage, and therefore unable to CWM flash with zips, then I must go to 2.2 Froyo next to be able to get past that problem, but again when I go from there to any custom ROM, it fails to boot at the very end, and starts its looping. Again, the 1st phone I had, never ever, behaved like this!! Same phone but, different dates of manufacturing and also this one came from either Samsung or TMO in Plano,TX where that's all, they do is send out phones for replacement, and this one wasn't in a original box, something they worked on, grabbed off the shelf, and sent to me!! Its just a shame that 99% of all the ROMS are in zipped form, instead of TAR files, at least then I could've tried flashing some of them from, Eclair to see if that made a difference, but when they are zipped, you must use CWM recovery to flash, and thus again presents another problem as far as what I'm going thru here!
Got any thing else, Idea wise, that actually hasn't been tried yet, that makes sense??
OK, Ive made some progress, It seems for whatever stupid reason, that unlocking my phone, [jailbreaking] was the culprit of this phones renegade behavior, I simply restored it back to a locked status as a TMO provider, and Wholla, the phones now acting right!! And I have been able to get it to the ROM I wanted and flash a better kernel as well with 0 defects!!! And then I jailbroke it again, and its working flawlessly.
Personally I don't understand why that had a bearing on its behavior, but nun the less it did. And has cause me a few extra wrinkles around my eyes in stress trying to figure this out by myself, especially when all the suggestions and procedures I did was for nothing, until this phone was restored to a locked condition again!!
Go figure Right???? Grrrrrrrrrrrrr!!!! Anyway I hope mentioning this will prevent someone else in losing their hair or sanity!!
hello i think we have the problem, i also have openline my vibrant to be able to use here in our country.. i have 2.1 eclair, i just want to know what 2.2 ROM did you used coz you've said that it's ok to upgrade it to 2.2, but not other ROM, where did you get it.. can you pm me the link
thanks
I Have restorted to being the noob that signs up to ask a question...The other day I was driving (pre-root) and I look down to notice my phone had power cycled on its own. I thought it would come back one, boy I was wrong....
It spiralled into endless boot cycle. It would at first reboot get to the 4g screen and then back to the htc...over and over. I was able to get into Hboot, and atempt to do a factory reset that didnt help because it became a endless reboot that way as well.
Now before any of you say "why dont you warranty replace the phone" Im a VZW agent, alas we dont have a warranty on our phones when it comes to our concessions lines...
Now, at that point I said enough is enough and I delved into the world of rooting. I self taught everything within a few hours. I had my phone unlocked and ready to go. I picked Ineffabile (http://forum.xda-developers.com/showthread.php?t=1420513) to use as a rom, I followed the procedure to a T it installed correctly, but then when it came back on everything seemed to work fine...for about 5 minutes and then it happened agian a power cycle all over again. and again...and again. It now comes on works for about 5mins and then reboots.
Im at a complete loss at this point I have gone back into the SD card and deleted the ph98 file etc.... I just dont know what to do. I need this phone to work.
Any help is appreciated Thank you so much!
I know you said it's not the wcdma problem but will your phone stay booted with the back cover off?
Else I'd ruu back to stock. Could try the different radios and see if it helps.
If you want to try the older radios and are on the OTA you'll have to hexedit you mainver. There's a guide if you look.
older radios? Im still new to this so I applogize...
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
Here's a couple guides to help you get familiar with rooting stuff:
http://androidforums.com/evo-3d-all-things-root/389787-beginners-guide-rooting-android-devices.html
http://androidforums.com/evo-4g-all-things-root/129648-quick-intro-rooting-those-new-rooting.html
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
feralicious said:
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
Click to expand...
Click to collapse
I dont have insurance =/ and cant get it either. Im trying to find the radios, and what kernal should I be flashing? because I cannot find the one that should match the rom im using.
What I dont understand is why the phone powers on, works for a few moments like nothing is wrong what so ever. Then freezes and reboots.
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
http://themikmik.com/showthread.php...-Beats-Tweaks-2-01-605-11&p=164906#post164906
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
feralicious said:
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
Click to expand...
Click to collapse
This is a clean SD card, and I didnt create a backup because I couldnt get the phone past Hboot when it was doing boot cycles previous to the root. I re-ruu'd right now. And im starting from scratch. I used clockwork before, Im trying amon ra now.
I recently installed the nightly build of ICS on my samsung vibrant. Today the phone had a error that said encryption cannot be completed phone must be erased. I let it do a factory reset . Then I got stuck in a endless boot cycle showing the vibrant logo and then the cynogen guy for a few seconds then reboot. I could still access the recovery menu but it refused to flash any roms I threw at it. I downloaded and ran odin 1 click recovery and it changed my tmobile phone to a att phone. And it lost the recovery mode. It just shows att screen first then samsung vibrant second and just reboots. I can still get into download mode and flash roms using odin 3 but no matter what rom I select or if I choose repartion or not the flash will go through successfully but then the phone reboots into same problem as before. I suspect the recovery files are gone since no button combination anymore gets me into recovery. Is there anything else I can do?
Man I am having the exact same problem. I really hope someone can figure something out soon. Did yours randomly get that error? Or did you actually try to encrypt your phone?
Sounds like you used the wrong Odin 1 Click. If it installed Captivate bootloaders, that would cause a problem.
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
It just happened
It happened on its own. Was working fine all day walked in my house as as soon as it hit wifi it started going crazy. I had the data plan turned off months ago. Maybe theres something to it connecting up to the net. I have found out if you install your sim you get a reduced menu of recovery options but without sim it just constantly reboots. it only gives option of reboot, reinstall packages,delete all user data, delete cache data. If you try reinstalling the packages theres nothing there. Deleting caches made no differance. ADB does work and responds while in this lesser form of recovery is there a easy way to use adb to force a full system flash?
Thanks
That link was perfect had a link to eugenes no brick froyo rom which fixed my problem. Dloaded that used its pit and tar files and repartioned and im back to stock. Going back to team whiskeys mod. If all ICS roms has bugs like that is unusable.
bfranklin1986 said:
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Do you have access to BOTH your internal and external SD cards? The Encryption Bug is totally and completely random and does not discriminate. There is currently no known reason or solution. Several of us across a few different devices have been working on this for months.
Consider yourself luck if you have access to both SDs as you are the 2nd person to get in and out today. Many, many others have not been as fortunate.
If you could please pull up this thread and put as much information in there as possible, it would be greatly appreciated. Are you unlocked, what happened right before, what bootloaders are you on, what ROM were you trying to flash, what ROM did you end up getting booted,....those types of things. As much detail as you can muster together, after you catch your breath and relax a minute.
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Update
I think I might have pulled the trigger to quick. While the link above did give me Eugenes rom which at least got me out of the boot cycle both internal and external sd shows 0 and I am unable to load anything on either card. I have tried differant microsd cards all of them show the same thing. So eugenes rom got me working kind of but cant store anything at all. That sucks loved my vibrant and its almost out of contract and planned on using on prepay.
Agreed 100 %
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Moped_Ryder said:
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Click to expand...
Click to collapse
chickenmon said:
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Click to expand...
Click to collapse
I got tagged on a Nook Color with it. BUT, since the Nook Color has a feature that no others I think do (you can boot a ROM straight from an SD card and not mess with the oringinal OS at all), I was able to just pull my Microsd out and reformat it and then put CM7 on it for my wife.
So far from what I have seen and been working on:
Vibrant, Captivate, My wife's Nook Color, A few Transformers, SGSII,...
Anything I can do?
Anything I can do to get my partions right again? I can flash the twm 5.2.2 but none of the roms i throw at it including ics passion stays in a boot cycle. Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
chickenmon said:
... Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
Click to expand...
Click to collapse
You may want to bring up this issue directly in Merio90's thread. I believe Alex9090 went thru possibly similar issues and may be able to help you in that thread (unless she happens to pop in here).
I'm assuming you were trying to mount sdcard and emmc within recovery first (storage and mounts)? If you do have access to recovery again and can mount the external sdcard, maybe try repartitioning the card within recovery (using the parameters in Merio90's instructions)? Then transfer your rom zip and re-flash.
People have actually flashed Eugene's Froyo post-EU ... but without an ext sdcard. Quite an oddity. It's the only one (AFAIK) that'll fully boot up (even after losing int sdcard access due to EU) yet without an external sdcard in place.
Your assumptions are correct. I cannot mount emmc. I cannot flash any rom via 2.5 or 5.2 recovery only through odin and only eugenes rom still allows phone to boot but no mounting of internal or external sds. Ive spent about 3 days on this. There must be some hardcore adb commands to force a true factory reset partioning and all. Very annoying. Thanks for the help if I find any ways to fix it I will repost it here.
Might be bricked?
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Not related at all to my original problem.
tenantrep said:
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Click to expand...
Click to collapse
First of all, not to sound like a ****; but it's rude to hijack someone elses thread. You should've created your own thread for this.
Second; you might have fried your bootloader which in turn, yeah, that's bad and you might have bricked your phone.
Did you try to boot into recovery via the battery pull method. If not, try that and see how it works. I would link you to the instructions but I'm too lazy and tired right now to search for it and again, this is someone else's thread. Just do a search for it and you should find it.
If you need more help or guidance, create your own thread and start there.
Noticed your running Ice Cream Zenwich rc1.3. How do you like it. Ive installed slim 3 times today and twice I have gotten the encryption error within a hour. Needless to say not impressed major pain in the ass to have to do a million and half tricks with awm, adb, popping sd cards in and out etc.
Update
Also the current build of ics slim does not allow the imei information to be retrieved from sim for tmobile requiring a reflash of the modem. You have to download and install a new modem. I used csm5. The guide on the link in this post dow work but its a real pain and requires lots of trial and error. Wondering if google intentionally bricking these things knowing we all got gadget lust for the sIII now.
chickenmon said:
Noticed your running Ice Cream Zenwich rc1.3. How do you like it ...
Click to expand...
Click to collapse
ICZen_rc1.8.3 (AOKP #39, ICS 4.0.4) + subZero #144 (New Test Kernel just released in mr_pyscho's RootzWiki kernel thread) is Linaro infused ... and I've got to say the combo is THE fastest rom experience I've ever had on my Vibe. Whatever MP did in his new test kernel just blows the doors off the previous performance limits.
Btw .. you keep encountering EU again. Really odd unless possibly your external card wasn't partitioned correctly. Not a knock directly on you, but it is a common occurrence lately. FYI, I repartitioned mine directly from recovery.
Also ... Br1cK'd (ICZen) and mr_psycho (subZero) are aware of the EU situation and try to include safeguards in their builds. However, until we know the exact root cause of EU, we're all just shooting in the dark. Imo, it's at least comforting to use a rom & kernel where the dev's are at least mindful of EU.
Hi there
I am relatively new to the world of custom ROMs. I have an S2 Galaxy and I have been using CM7.1 without fault for a few months. The other day, without any explicable reason, my phone rebooted. All good so far. What happened after that, though, has got me stumped and is driving me CRAZY. Heres what happens: The phone "resets" to a backup i did at the end of July. When I say it resets, i mean it literally wipes everything and reverts back to the previous backup. Ok, so this is still believable. But... now it goes into this GroundHog Day scenario several times a day, reverting back to the same backup. Yes, it means I have to update the same apps which I delete as soon as it does it. I can wipe my cache, i can reset to factory... I can flash other ROMS - which I get told is done successfully - I can physically remove my SD card... I can re-flash it through Odin... down to kernel level... and every time i reboot... it comes back to the same darn backup, even with the SD Card sitting on my desk. Is there ANYONE out there who has had this happen before? Its driving me nuts. Is there perhaps a way I can totally, completely and utterly WIPE my phone and start from scratch? Any help would be MUCH appreciated!
Hello, all. First, I'd like to say thank you for taking the time to read this and potentially try and help me out. Any assistance with this matter would be greatly appreciated!
I added the (Non-standard) to the title, as I've been flashing and modding this phone for over two years, and I've never experienced this issue. I'm not the type to ask for assistance, as my research skills are well above par, but after digging through literally countless forums and topics, I have yet to find anything quite like my situation...
ISSUE: Performed recent flash attempt to epinter's CM10.1. Now loads to Moto splash, sits there the usual few seconds, but when it comes time to load the rom, it reboots and starts the process again... (I swear I think I see it trying to load the rom splash for like a micro second, but then it could just be the delirium of long hours researching and fighting this problem.) Now, you might be thinking, "Eh, pretty common...", right? Yeah, me too, until I couldn't fix it like I've done a million times before... I can boot into recovery. I have performed ALL standard actions regarding flashing a new rom, yet the problem persists. The problem persists now no matter what rom I attempt to flash. Now you might be thinking, "Just flash your nandroid recovery...", but I wish, oh how I wish I could... I am currently using CWM-based Recovery 5.0.2.7, although I've tried more than a few different recoveries since this issue, all provide the same results... Which is nothing. I'm at the end of my rope here.
I've even tried flashing TWRP (two different versions) so I could at least get some charge to the battery so I could continue this debacle, but it hangs at the TeamWin splash screen...
Fastboot loads fine. Wipes performed to system, caches, partitions, etc, to no avail... Battery pull, already tried...
I've covered all the basic fixes, but my issue seems to be bigger than my knowledge base (at the moment).
Okay, here's the exact details of what led up to this...
My Atrix WAS unlocked, rooted, and using RR's CWM for recovery at the time. I had flashed everything coming and going as the scene grew, but eventually went back to CM7.2 and had been running it for ages. Well, I decided to try something new, and settled on trying BeanStalk. Flashed Aroma Prep, no problem. Flashed ROM and Gapps, no problem. Booted up fine. Decent start on the rom, but a little too buggy yet for me. So on this note I wiped and restored my CM7 nandroid backup, no problem. All was well, until I came across epinter's CM10.1 and thought, "Eh, why not?" (...and now look at the mess I'm in!) Performed a new nandroid backup of my CM7, and began the process that ended me... Everything went along just fine. Performed all my wipes, flashed my zips, rebooted, and BAM... boot loop! Little did I know what kind of headache I was in for, until I couldn't restore my backup. Now, I'm just praying I find a solution before my battery drains out completely...
SIDE NOTE: While attempting to restore fails and just resets recovery back to the main screen, there are no visible errors reported. Attempting to flash ANY of my other roms results in the same behavior. Flashes "appear" to go smoothly, but the end result is the same... I did notice upon attempting to flash BeanStalk again that there is an error reported in the aroma installer. It performs all wipes correctly, but when it comes time to actually install, it reports a broken symlink error, or something to that effect... (I would reproduce the install error message, but at the moment I'm trying to hang onto as much battery life as possible. My apologies for the inaccuracy of any statement.)
PLEASE, LADIES AND GENTLEMEN, I BEG OF YOU... If anybody has been unfortunate enough to have found themselves in my shoes, then hopefully you were lucky enough to get it figured out by now and would be willing to pass along the info. Although not my primary phone anymore, it still gets more than it's share of use. I'd hate to see it go out this way...
Any help to guide me in the right direction would be most appreciated! Thank you all in advance!