Related
Morning, Fellow Forumers!
I've been using my HD2 for a few months now, and every day my frustration grows. This thing is unstable as hell. It either stops responding completely, or the phone application hangs (sometimes it's impossible to hang up a call), or just the backlight works, or the UMTS stops working... PAIN AND MISERY! I have it upgraded to the latest official firmware, but it doesn't help at all. Tried the Touch Tools to turn off unneccesary stuff - still no good.
It's even worse when it's BT'd to my Audi MMI. Every 10 seconds or so it's completely stuck for like 2-3 seconds. It looks like the BT firmware has not been optimized at all and whenever it refreshes the phonebook/calls list/etc with my car, the GUI is dead. Fixing that would be great stuff.
So, I'm asking to point me in the right direction. I don't care about warranty or anything, just want this device to be stable! Since the official FAQ is like 10 pages long... is there a FAQ's FAQ?
Basically - what's my first step? Thanks in advance!
PS: It's a retail version (non-branded) purchased in Poland.
Your solution Must be somewhere here:
http://forum.xda-developers.com/forumdisplay.php?s=&daysprune=-1&f=534
And Here:
http://forum.xda-developers.com/forumdisplay.php?s=&daysprune=-1&f=735
As for me I am very happy with my stock Rom,so far...!!
I have no problems with stock and with most of cooked ROMs
Have you tried re flashing the latest stock rom off the htc website?
task29 can solve most problems, however if you have done all those steps and still getting problams, you may have a faulty unit and it might need to be sent back for repair/replacement.
Really sorry to hear about your problems. Wish I could give you a good solution, other than to do a hard reset and then upgrade to the latest ROM. I am running a stock ROM and the HD2 is the best phone I have ever had. And I have had a few. Good luck.
I used my hd2 on a stock rom for ages, and it was stable enough, with the odd crash occassionally. I recommend using a custom rom. Since a custom rom, my battery life has improved dramatically, my hd2 runs faster and is so stable, i cant crash it if i really try!
Duttys V9 is a personal favourite
Thanks for your help, guys. I decided to reflash to chuckyROM's wm + android 2.2. On android, everything works so much smoother. The only problem is in 80% of the cases, phone would crash when I try to perform a BT call. Might be a wrong radio version, will keep trying.
tompken said:
Thanks for your help, guys. I decided to reflash to chuckyROM's wm + android 2.2. On android, everything works so much smoother. The only problem is in 80% of the cases, phone would crash when I try to perform a BT call. Might be a wrong radio version, will keep trying.
Click to expand...
Click to collapse
Bt calls are still unstable for everyone... work in peogress.....
Sent from my HTC HD2 using Tapatalk
UPDATE: Thank you guys so much for the help! My phone is running well so far! The GPS works well enough for navigation, and I should hopefully be able to limp through until my full upgrade. I can't tell you guys how thankful I am that you all took the time to help me answer my questions and get my phone going again!
what would you do? I have a Vibrant, and have done quite a lot of troubleshooting with it. Tmo's tech support said it's a hardware issue and that they've done all they can.
I've tried just about all the Froyo ROMs on it, and things seem to work well for a while, then it gets odd. I regularly clear my call logs, messages, and browser cache. I use wifi whenever I'm at home, and whenever I'm in the minivan I have my phone plugged in.
I am currently running Axura - Moped/FishmanMod v1. This has seemed to work the longest.
Lately, though, I've been missing phone calls...as in, no notification, no log, nada. I rebooted last week and suddenly had a voicemail icon...I had 7 new voicemails. One from my son's teacher. I never knew she even called. I've since reinstalled Tmo Visual Voicemail and at least now I think I'm getting my voicemails. Missing phone calls can't happen though. We don't have a landline, and we have a child with health issues. I have to be available.
Other issues:
*My battery died about halfway through the day yesterday, even though it had charged fully overnight.
*This thing is slowing down. As in, taking a photo with my phone isn't really viable. By the time it finally snaps the picture, my kiddo has grown an inch.
*Lag! I'm using Swiftkey X and it often hangs on a key for several seconds before finally typing it. It's very slow to open apps, etc as well.
Does anyone have any more advice for me? I'd love to run an ICS or JB ROM, but having the ability to call 911 is not negotiable for me. Woodrube and some others have given me some great advice, which has helped, but I'm still having some issues.
I could pare down the apps and use it just as a phone, but what would be the point of having an Android...and data? I need the calendar, email, task list, etc. to keep track of everyone.
I'd love to try to figure out how to make this phone last longer. I could upgrade now, but our checkbook doesn't like the idea.
Personally I'd Odin back to stock JFD and either do a reflash or pick a new ROM (bionix comes to mind).
Could do a fresh install of the apps you want on your phone. Your battery could be going bad and may need to be replaced, and if your sim card is getting old, you may need to stop by T-Mobile and have them replace it.
Not sure if that could be the trouble with your notifications or voicemail, but they are all quick things to try that should be cheap and quite possibly very effective.
The_MamaBee said:
what would you do? I have a Vibrant, and have done quite a lot of troubleshooting with it. Tmo's tech support said it's a hardware issue and that they've done all they can.
I've tried just about all the Froyo ROMs on it, and things seem to work well for a while, then it gets odd. I regularly clear my call logs, messages, and browser cache. I use wifi whenever I'm at home, and whenever I'm in the minivan I have my phone plugged in.
I am currently running Axura - Moped/FishmanMod v1. This has seemed to work the longest.
Lately, though, I've been missing phone calls...as in, no notification, no log, nada. I rebooted last week and suddenly had a voicemail icon...I had 7 new voicemails. One from my son's teacher. I never knew she even called. I've since reinstalled Tmo Visual Voicemail and at least now I think I'm getting my voicemails. Missing phone calls can't happen though. We don't have a landline, and we have a child with health issues. I have to be available.
Other issues:
*My battery died about halfway through the day yesterday, even though it had charged fully overnight.
*This thing is slowing down. As in, taking a photo with my phone isn't really viable. By the time it finally snaps the picture, my kiddo has grown an inch.
*Lag! I'm using Swiftkey X and it often hangs on a key for several seconds before finally typing it. It's very slow to open apps, etc as well.
Does anyone have any more advice for me? I'd love to run an ICS or JB ROM, but having the ability to call 911 is not negotiable for me. Woodrube and some others have given me some great advice, which has helped, but I'm still having some issues.
I could pare down the apps and use it just as a phone, but what would be the point of having an Android...and data? I need the calendar, email, task list, etc. to keep track of everyone.
I'd love to try to figure out how to make this phone last longer. I could upgrade now, but our checkbook doesn't like the idea.
Click to expand...
Click to collapse
Well, although it isn't too helpful to say...I honestly believe that if you simply must be available because you have a child with health issues, you definitely should not be tinkering with your device. True, my phone runs better, faster, stronger, and longer (ha daft punk) than it did running stock, but I have certainly had the occasional issue such as data issues, force closes, battery drains, SODs, etc, etc...it's simply a fundamental part of the life of modifying your phone. It's not to say that you won't have issues if you kept it stock, but you really shouldn't be messing with your phone if you don't have a land line and you NEED to be available for something so important.
Now, onward!
I will look into similar occurrences of your problems and report back..(sorry in class atm, then off to a meeting). Until then, Gl!
you could try and use a cyanogenmod based Rom. They are one of the best roms out there except you can't as of right now call 911 (some phones can and some cant ) also gps is semi-broken.
blizzardproof said:
you could try and use a cyanogenmod based Rom. They are one of the best roms out there except you can't as of right now call 911 (some phones can and some cant ) also gps is semi-broken.
Click to expand...
Click to collapse
Thanks for the advice, but not an option. I have to have 911 capability, and we're pretty active geocachers, so my GPS gets used a ton. I've been so tempted by CM Roms, and my husband is rocking one on his One S, but going without 911 isn't an option.
After this last round of my phone's slowness, we did ODIN back to stock, then did the ((*^&^%$*&^) updating it to Froyo. (Yay!) We were hoping that taking it back to stock would help our issues, but it actually seemed slower. (And oh, the agony of using TouchWiz!) I very, very carefully added back ONLY the apps I used on a daily basis, watching carefully to see if there were any issues. It was crazy slow.
We then went to this last ROM and I added back apps even more slowly. I noticed that I had issues after I put the Zedge app back on, so it's gone. I also noticed that it acted funky after I put Google Goggles on, so it's gone as well.
I am not, by the way, storing any music on my device. I stream it through Google Music.
I do have another battery for it. I'll put Battery Calibration on and swap batteries to see if that helps. Good idea.
Also, my SIM is pretty old. I hadn't thought about seeing if I could get a new one! I know it solved some issue LONG ago with my BlackBerry. I'll see if I can do that at our TMo store today. Appreciate that suggestion.
I've been just about the give up on this phone altogether and just going with the One S like The Hubs, but forking over the money for it (not to mention that it would be $200 for me and $49.99 for a new contract!) is just not in the budget now. Might be getting close to something we just can't avoid though.
Try flashing back to stock 2.1 with repartition checked. Then flash one of Fishman/Moped 2.2 ROMS ( he has odin files if you prefer that method). I think you may still have some "ghosts" left behind from the last ROM or two you had on your phone. A fresh odin to stock with repartition checked should get rid of any "ghosts". Also when restoring apps make sure you restore app only, not app+data. Remember, after installing a ROM allow your phone to sit for a good 10 minutes then reboot before you use the phone.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
Try flashing back to stock 2.1 with repartition checked. Then flash one of Fishman/Moped 2.2 ROMS ( he has odin files if you prefer that method). I think you may still have some "ghosts" left behind from the last ROM or two you had on your phone. A fresh odin to stock with repartition checked should get rid of any "ghosts". Also when resorting apps make sure you restore app only, not app+data. Remember, after installing a ROM allow your phone to sit for a good 10 minutes then reboot before you use the phone.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
That could definitely be it. I used to just restore all my apps+data with My Backup Root. I'll see if I can convince The Hubs to help me work on the phone this weekend. I'll let you know how it goes. Thanks!
Okay, we did the repartition flash, then put it on FishmanMod Blue 2.2 Frankenstein Slim. Seems to be running a little better, but now my GPS won't lock at all. I've rebooted, tried Samsung GPS Restore (never locks) and GPS Test. Test sees 4-5 satellites but doesn't ever lock on. I've tried Nav as well and it is not able to lock on.
I've checked our forums and I see a lot of fixes, but no recent fixes and most of them are for 2.1. I've tried dialing the *#*# numbers, but they don't do anything.
I sure could use some suggestions. I'd like to be able to use my GPS. I know it's generally an issue with Vibrants, but mine has never failed to lock on before. Might be slow, might take it until the end of the block, but it always locks. Until now...
Thanks in advance!
Go to the Dev section and look for a thread called GPS Fixes by Solisfiend. It'll be buried way back and I'm mobile so I can't link it. It has directions and app to fix Froyo GPS.
I have 2 posts in there, 1 is clarification of some things and the other is a download app you can use. Should work well for you.
Thank you, Woodrube. I'll do just that.
ETA: Found the link.
http://forum.xda-developers.com/showthread.php?t=1393991&highlight=gps+fixes
Sent from my SGH-T959 using xda app-developers app
On every Jellybean rom, I have calling issues. On some roms, call audio wont work. On the rom I just flashed, it would not make or receive calls all together. Also, this happens only after a certain period of time. And it goes from sporadic occurances to permanent. It takes about a day or two for these issues to start appearing. This is so god damn frustrating because in the beginning the rom works perfectly, I spend all my time setting it up, and then a day or so later, I get these issues that make the phone completely unusable. Its absolutely ridiculous, and If anyone has any ideas, please please let me know. I love the JB roms but they all seem to make my phone unusable after a short time.
Please help....
JB roms are still a work in progress. And your problems could be caused/made worse by your setup (apps, widgets, tweaks, etc...). If you are using different kernels/radio, it can also contribute to problems. There are just too many variables.
My answer : use an ICS rom. ICS roms are alot more stable on our phone right now.
H0rn3t920 said:
On every Jellybean rom, I have calling issues. On some roms, call audio wont work. On the rom I just flashed, it would not make or receive calls all together. Also, this happens only after a certain period of time. And it goes from sporadic occurances to permanent. It takes about a day or two for these issues to start appearing. This is so god damn frustrating because in the beginning the rom works perfectly, I spend all my time setting it up, and then a day or so later, I get these issues that make the phone completely unusable. Its absolutely ridiculous, and If anyone has any ideas, please please let me know. I love the JB roms but they all seem to make my phone unusable after a short time.
Please help....
Click to expand...
Click to collapse
I am observing similar issues. I didn't used to happen before. I mean it did happen but it was a rare thing. But now it is more often. Almost everyday I have to reflash because of loosing phone audio.
I was rocking AOCP 3.1 , Worked really sweet and then decided to update to go for AOCP 4.1 and since then no rom that I tried have saved me. In fact I had to revert back to stock. What rom are you using?
People, it's a known issue on all JB Roms.
Don't open a thread about it.
xaragen said:
I am observing similar issues. I didn't used to happen before. I mean it did happen but it was a rare thing. But now it is more often. Almost everyday I have to reflash because of loosing phone audio.
I was rocking AOCP 3.1 , Worked really sweet and then decided to update to go for AOCP 4.1 and since then no rom that I tried have saved me. In fact I had to revert back to stock. What rom are you using?
Click to expand...
Click to collapse
I have the exact same issue now, It doesnt look like any rom is saving me right now.. my phone wont make calls or receive texts at all. I was running cookies and cream 4.1.2 and everytime i flash a JB rom it just seems to get worse and worse...
EDIT: I got it back on ICS. I guess I will just have to wait to use any JB roms... its unfortunate cause I love the JB roms hahaha
I have had issues with JB as well. I, just like the OP, would experience a perfectly working phone for a day or two then **** would hit the fan for no apparent reason. The phone would start locking up, randomly rebooting, apps would fail or not load, etc etc etc.
On most ROM's I didn't even have anything installed outside of the stock apps that CAME with the ROM.
Since then I have moved to a deoxed stock ICS ROM and honestly am not looking back. ICS is fast, stable, feature packed, and JUST WORKS.
My thing with JB was it's speed...but I was also comparing a barebones JB to the stock Gingerbread that came with the phone. I wasn't aware of how fast ICS was or I would have just gone with it long before hand!
But yeah, either way it goes, for me, no matter the ROM, JB always seemed to mess up at one point or another. Got annoying. Been going with ICS for over a week now with ZERO issues what so ever. No reboots, no crashes, no freezing, no nothing.
NEVERMIND..... ICS worked for one call, and now no calls work... great....
ICS roms are very stable.
You may have flashed your rom/kernel/radio incorrectly, or made some tweaks, or installed incompatible apps... There are too many variables.
Revert back to completely stock setup and see if the problems persist.
H0rn3t920 said:
NEVERMIND..... ICS worked for one call, and now no calls work... great....
Click to expand...
Click to collapse
I'll take a stab, what gapps? Do you use a call blocker of any kind?
Sent from my Samsung-SGH-I717 using xda premium
Same. I think it's the same for a lot of people, and I think the ones who say things run great either ignore the problems or are just extremely lucky.
Switch to Padawan. It's rock solid and you get all the fanciness of jelly bean. Since switching to it I've completely lost the itch to try out random JB ROMs. I have cool animations, Google Now, and ICS Browser+. And until I rebooted earlier to mess with stuff, I was at 142 hours uptime without any problems.
I'm not calling anyone a liar, though. I just think some people ignore more or are, as stated, lucky. I've done wiped everything, went back and wiped stuff post ROM, ran 3rd party (3rd ROM party) kernels and the ones that come with it. I've set cron to fix permissions on boot. And other than gapps -- which I always flash what the dev says to -- I run about ten 3rd party apps, and that's mostly made up of solid apps -- dropbox, exdialer, ics browser+.. etc..
Padawan, or even Nebula.
These ROMs are by the same dev, and the only difference is that Nebula is based off of Canadian version, which has even less bloat. It is better than stock.
I have been on Nebula for about a week, and no random reboots, no lockup, no phone problems. Everything just works.
ddochi11 said:
Padawan, or even Nebula.
These ROMs are by the same dev, and the only difference is that Nebula is based off of Canadian version, which has even less bloat. It is better than stock.
I have been on Nebula for about a week, and no random reboots, no lockup, no phone problems. Everything just works.
Click to expand...
Click to collapse
I like padawan, and Im on it now. But i still am getting this random issue where calls do not go through. Its so aggravating that Im about to smash my phone against the wall. Its happening all the time now and when I need to make a call, I cant. god damnit
have you flashed the most recent modem?
Yes, that was my next question.
Have you at any point flashed a different kernel/radio/modem? If you have, or if you do not know, search for stock kernel/radio/modem and flash them to see if it helps.
yes, uclf6 modem but eventually it just gives out.. idk what the issue is here everything works fine for a few days and out of the blue when I need my phone i cant receive or make calls anymore its INFURIATING
yes, uclf6 modem but eventually it just gives out.. idk what the issue is here everything works fine for a few days and out of the blue when I need my phone i cant receive or make calls anymore its INFURIATING
Revert back to complete stock and see if the issue still exists.
Mobile Network Type
Ltilt2 said:
People, it's a known issue on all JB Roms.
Don't open a thread about it.
Click to expand...
Click to collapse
I have had a similar issue with the JB rom's...so far I've tried only two and seem to find the aokp_quicyatt_jb_milestone-1 rom. I have noticed issues with my phone and LTE network coverage...meaning, I can see the signal go from 4G LTE to 3G to H, then gone...I looked at the phone status settings and noticed the mobile network type with this rom is LTE:13 and with the stock ICS rom (prior to rooting and flashing) it was LTE:14...is there a way that I can change it via terminal? Thank you in advance for any help on this. The one big difference I can see so far is the battery life...much better. Any help is greatly appreciated.
Issues are known....Thread Closed & Thank You.
My EVO 4G LTE has, with all custom ROMs, lost stability after a month or two, developing different arrays of performance quirks or problems.
I'm interested in if there's a way to test the hardware on the phone? I'm tired of switching / reinstalling ROMs.
At first I thought the problem was that the ROMs were unstable but I've chosen from the bet ones available - PACman, Viper, a couple others I can't recall right now. The phone is rooted via Dirty Racun FYI...
Currently, with Carbon, the problems consist of:
With screen lock off, when waking the phone via the power button, something on the current screen will activate, whether it's an app shortcut on the homescreen, or a function inside of an active app.
Setting for LTE / 3G will not stay on 3G (LTE coverage is spotty enough that I just don't use it)
Random crashes / resets / bootloops; occasionally the phone will freeze on the loading screen with the Carbon logo and require me to hard-reset it.
Once in a while it's ignored my alarm clock.
Usually when dialing out, the phone will hang and fail to connect / ring, and I'll have to hang up and dial out a 2nd time to connect / ring through.
With ROMs I've used in the past, the arrays of problems have been different but of similar nature. At first I was inclined to blame the ROM in use but as my phone is the common element between them, I'm interested in how I can determine if I have a lemon on my hands or what.
Thanks for reading this.
Go back to stock rooted and see how it runs.
Captain_Throwback said:
Go back to stock rooted and see how it runs.
Click to expand...
Click to collapse
I'm not unwilling to do that, but I have extra time this weekend to run diagnostics as well if there's any method by which that's possible? It seems to take a few weeks for problems to start developing when I install a fresh ROM.
baccaruda said:
I'm not unwilling to do that, but I have extra time this weekend to run diagnostics as well if there's any method by which that's possible? It seems to take a few weeks for problems to start developing when I install a fresh ROM.
Click to expand...
Click to collapse
Any such diagnostics when not on a stock ROM can be issues with the custom ROM, not the device. If they occur when on stock, that helps determine hardware may be at fault.
Most of the AOSP ROMs suffer from kernel and data issues because they use the same base. You might want to try the Android 4.3 RUU as well since that's the latest we have for the device.
Captain_Throwback said:
Most of the AOSP ROMs suffer from kernel and data issues because they use the same base. You might want to try the Android 4.3 RUU as well since that's the latest we have for the device.
Click to expand...
Click to collapse
Ah, thanks for this. I didn't think it would be reasonable to blame the ROMs across the board. I'll look into the 4.3 RUU.
Hello friends,
I recently picked up an i717 and am in the process of sorting it out. It was originally a Bell phone, though of course it's unlocked these days. I've been hacking at various Android phones for years now and have managed to work through just about everything, but this has me stumped...
I've tried almost all the 4.4 roms, and most of the 4.3 as well. I've tried various kernels/modems/combinations/etc. I've used CWM and TWRP. They all invariably lead to the phone either rebooting constantly from the "optimizing apps" dialogue, or a few times I've made it to the welcome screen, but it's always just up for a minute or two, crashes, then reboots. I haven't found a live download for 4.2 yet, so I don't know if it would work or not. 4.1 stock and Padawan run just great. I've been doing multiple full wipes before installation, flashing the rom a few times, then hitting the caches a few more times for good measure. I can't imagine my flashing technique being at issue here.
I do know that there is at least some physical damage to the phone. The capacitive buttons don't work. But it doesn't see immediately obvious to me that these would be related. Of course, I've seen stranger things. Running Padawan the phone will hum right along at max speed all day with no apparent issues, so that side of the hardware seems okay.
Sometimes CM roms will end up at the CM welcome screen and pop up a "com.android.acore has stopped" dialogue. But the constant reboots are there on every rom I've tried.
Does anybody have any ideas?
Outside of the, every once in a while you just need to go all the way back to stock just to make sure all the garbage is taken out, have you considered the infamous stuck power button?
Though I have yet to, many have experience the stuck power button. It may feel ok and you may even hear it click, but that doesnt mean anything. Give your phone a couple good flicks to the back behind the button. Though it does seem odd that it would run one rom without issue and not others, but it is worth a shot.
Again taking your phone to 100% stock every blue moon or so can be a good remedy too.
Keep us posted. We can work you through this.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I thought about the power button issue. However, it proceeds to boot into the OS until after a time when the screen locks then reboot, which would seem too long to be the power button in any case. Regardless, a few sharp flicks didn't help much. And, of course, it runs quite happily all day long running on 4.1.
I have restored to stock JB, though admittedly not earlier than that. I guess I could try going all the way back to GB to see if that makes any difference.
In my experimentation tonight I've found that 4.2 also does not work, while I can add 4.1 non-tw roms to the working list. My best guess seems like something about one of the many under-the-hood things that changed with 4.2 doesn't get along with something about my particular phone. But, who knows.
For now I'll try rolling back to GB in Odin and see where that gets me.
I would say ICS is about as far back as you need. Recently I was having issue getting anything 4.3 and up to work or even flash. No different recoveries had effect either.
Wiped slate clean and started over from ICS, and Bob was my uncle. Everything that failed before was not an issue. Running latest 4.4 now and might I say "Orgasmic"
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Ahh, if only I were on 4.4 on my Note, life would be good Though, to be honest, I'm quite digging this thing, even at 4.1.
Last night I rolled back to GB, and had no luck. Although the Odin tar that I found apparently didn't include recovery, so that had to be flashed separately. I don't know if that might make a difference. That might be my experiment for tonight if I can find a tar that includes everything. Might be easier to find on ICS.
Just running my mind through other stuff I've thought of, I remember reading about kitkat having some issues with SD cards, so I've mostly been experimenting with the card pulled and a fresh format on the internal storage, with no real difference. Tried safe mode, no dice (not that I would expect this to make a difference on a fresh flash, but who knows lol...).
It's just such a weird thing. It boots into the OS with seemingly no issues. On occasions when I can actually get to the lock screen, everything runs fluid as can be until it freezes and reboots. Sometimes when it gets stuck at the 'optimizing' screen it'll just restart the count every boot, sometimes the number of apps to be done go down each time until there are 3-4 left which persist through each reboot.
I wonder if I could check logcat via adb before it reboots. Might be able to find some clues there.
Here's a factory firmware image of 4.1.2 to be flashed with Odin.
http://www.mediafire.com/view/g7gn29h7nu63id5
I've used this to revert many times. Install it. Run it once, then factory reset and run it for at least a few hours. If you experience issues you probably have hardware failure. If you don't have issues you can proceed with installing the latest clockwork mod recovery. Then wipe system and internal memory 3 times with recovery. Now flash the zip of your favorite kit Kat rom. Reboot and run it. Then factory reset and hopefully run it forever! If you're on a kit Kat build and experience sd card issues, there's an xposed module that might be able to help with that.
Thanks a lot, Bro. I'm downloading the image right now and will flash it then give it some time to settle in. Fingers will be crossed!
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Bassism said:
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Click to expand...
Click to collapse
Have you tried to turn on USB Debugging and run "adb logcat" to see what errors are causing the problem? If it is an optional program or hardware feature you may be able to disable it and run the newer ROMs. I know bluetooth has been an ongoing pain point for people. Which modem are you running? I know that some of the older modems do not work with the newer ROMS.
Good luck.
Brett
corrupt radio
i had the same issue, flashed 4.4.4 and ran like a charm for 1 day them the radio took a dump. downgraded and worked for another day.
imei became unknown and the no radios were able to fix this. went as far back as 2.3.6 hoping my radios would be fixed and no dice.i have tried endless for weeks to fix my phone and seems doomed.
none of the bricked threads helped and flashing stock with odin is no help. there seems to be no fix to the null imei and unknown baseband