In the past month, I have had 3 different Dell Streaks due to unrelated RMAs (Had 1 for 6 months that stopped charging due to a hardware connection damage; the next one permanently shut down soon after I received it) so I am trying to avoid having to call Dell for another replacement if it isn't just my phone which has the following problem:
Certain games are causing the phone to shut down, flash the buttons 3 times, and reboot. This problem happens consistently when I play Death Worm Free so I will use that as a test app though it has happened while playing other games as well.
Software config:
To diagnose the problem, I have tried playing Death Worm Free on my phone after correctly flashing to 351, 353, and 354. On all ROMs, the game crashed the phone even when I had not installed any other apps from the market.
The game is reasonably fun so you won't be dissappointed, but I don't want to call for a replacement just to have the same problem... so I ask:
can anyone download Death Worm Free from the market and install it and play for longer than 20 minutes without it crashing the phone? (I would link to it but I can't... not allowed... noob forum member). Note: nothing besides games are crashing the phone. It may be heat or it may be a problem running graphics intensive apps.
It would be a great help for me. If you do help me and install the game and play it, please let me know whether it crashed your phone also or if you played successfully and what ROM you are using. Also, any alternative suggestions?
Use Navigator every time you go anywhere. If it's the phone dying under pressure, that should trigger it. If it works perfectly then the problem is likely the game.
Sounds like the problem I had. Even long phone calls could trigger it. I just got my replacement yesterday.
Update; I reflashed to 353 (the latest ATT stock that came with the phone in question) and I am again stuck with an older version of swype (yet nobody in this forum has compared the swype versions in each Dell build) but the games are slightly more resilient. I wish I knew... can anyone answer: if I install a custom ROM like streakdroid, can I reinstall my 353 stock rom in case I still want to use a RMA (and have it unrooted?)?
Yes you can revert from a custom ROM to a stock ROM. Unless there are AT&T apps that you use for a stock ROM I suggest BB 351.
Radimus’s Universal Guide to Flashing a ROM – MUST READ if you want to flash a ROM or upgrade (or revert to stock)
marvin02 said:
Yes you can revert from a custom ROM to a stock ROM. Unless there are AT&T apps that you use for a stock ROM I suggest BB 351.
Click to expand...
Click to collapse
What is BB 351? The stock build? I alread posted that the games were crashing the phone with that build. People seem happy with build 354 so I will stick with that once anyone answers my question about whether it is my phone that is crappy or streaks in general that cannot handle the game.
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
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Chakker3D said:
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Click to expand...
Click to collapse
You are using a leak or *beta* rom which is far from stable
And no installing many roms can not damage any hardware
Sent from my GT-I9100 using xda premium
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Chakker3D said:
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Click to expand...
Click to collapse
Having a similar, if not identical issue on latest Westcrip ROM. Near as I can tell, seems to be related to memory management: while on BT, RAM space drops almost 200Mb. While changing songs, or surfing the tracklist/phonebook, it can cause the RAM to reach a critical level. This causes the OS to crash and the phone to reboot (my case a soft reboot from the animation only) in order to create space. I would chalk this up to inefficient memory management by a beta ICS rom. Look for this to be sorted out in the future with official releases and custom kernels/roms.
Thanks for your response.
Yeah when I installed resurrection, I also ran in to that problem. I had no idea how to diagnose it. But it makes sense, bottling up the ram to the brink of reboot.
Thats what initially was happening to me, soft boot, took a few seconds and was back in. But extended crashes seemed to cause corruption.
Yeah so the XXLPH seems to have an issue. Because I also tried foxhound and got the same result.
I just got back in from testing my BT on my car stereo using my stock rom of KG2 and it played for 20 minutes and i chatted for 19 without any problems.
So I am glad it wasnt anything seriosu. But only reason I was concerned is I found nobody else to have the problem and I felt a bit isolated
But im reading the official ICS rom is out in Europe so im sure we will see some new roms out in the next little while.
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
Hi everybody,
I'd like to hear your thoughts on my problem.
I have been flashing my i9300 since the day I have it. I wasn't impressed with stock TouchWiz (4.1 I believe?) I have been switching between TW based and AOSP roms alot. I just never found the rom I liked. All of them began to run slow, if they were not already slow. (I do not blame any of the roms I have used, I want to point that out)
Recently I sent the phone back for repair, because it had a burnt in screen. So I went ahead and flashed full stock and reset the counter and all the fun stuff. When I rebooted the phone (100% clean wipe, flashed a Netherlands rom) I noticed that the phone was slow as living h*ll. I had flashed it to a "out off the box" experience but the phone was just about useless. I went ahead and flashed a different Netherlands rom, which was a tad bit faster. I went with it and sent it back.
When I received the phone back in my mailbox, they had flashed stock again (why would one flash stock if just the screen had to be replaced?). I noticed that the phone was extremely slow again!
I decided to believe that it was TW to blame, and flashed Omni KitKat. This was fine for about a week, after which the phone would randomly lock up and system.apk began to crash every 30 minutes or so.
I then decided to start with a clean plate and flashed CM11 (full wipe, including media and all). I have been using that for a little over 2 months now, but the same issues are starting to occur. I have tried it without any 3rd party apps installed, without success. The phone locks up about every 5 minutes with the screen on, I can't listen to music (Google Music or PowerAMP) and then switch to another app, because the music will then stop. If I press the home button, there is an 3-10 second delay, after which system.apk decides to reload along with the launcher (Google Now Launcher), things like that. Sounds like a memory problem to me.
I think it might have something to do with a baseband issue, because of the fact that I have had problems similar before, which were (sort of) solved by flashing a different baseband. But I don't think that Sammy's basebands are compatible with CM11, and I have yet to come across a problem with a CM11 baseband on the internet.
Do any of you experts know an explanation to my problem? Would you suggest sending the phone back for repair?
Thanks in advance
FistFull95 said:
Hi everybody,
I'd like to hear your thoughts on my problem.
I have been flashing my i9300 since the day I have it. I wasn't impressed with stock TouchWiz (4.1 I believe?) I have been switching between TW based and AOSP roms alot. I just never found the rom I liked. All of them began to run slow, if they were not already slow. (I do not blame any of the roms I have used, I want to point that out)
Recently I sent the phone back for repair, because it had a burnt in screen. So I went ahead and flashed full stock and reset the counter and all the fun stuff. When I rebooted the phone (100% clean wipe, flashed a Netherlands rom) I noticed that the phone was slow as living h*ll. I had flashed it to a "out off the box" experience but the phone was just about useless. I went ahead and flashed a different Netherlands rom, which was a tad bit faster. I went with it and sent it back.
When I received the phone back in my mailbox, they had flashed stock again (why would one flash stock if just the screen had to be replaced?). I noticed that the phone was extremely slow again!
I decided to believe that it was TW to blame, and flashed Omni KitKat. This was fine for about a week, after which the phone would randomly lock up and system.apk began to crash every 30 minutes or so.
I then decided to start with a clean plate and flashed CM11 (full wipe, including media and all). I have been using that for a little over 2 months now, but the same issues are starting to occur. I have tried it without any 3rd party apps installed, without success. The phone locks up about every 5 minutes with the screen on, I can't listen to music (Google Music or PowerAMP) and then switch to another app, because the music will then stop. If I press the home button, there is an 3-10 second delay, after which system.apk decides to reload along with the launcher (Google Now Launcher), things like that. Sounds like a memory problem to me.
I think it might have something to do with a baseband issue, because of the fact that I have had problems similar before, which were (sort of) solved by flashing a different baseband. But I don't think that Sammy's basebands are compatible with CM11, and I have yet to come across a problem with a CM11 baseband on the internet.
Do any of you experts know an explanation to my problem? Would you suggest sending the phone back for repair?
Thanks in advance
Click to expand...
Click to collapse
The problem might occur because of memory which one of my friend had earlier. Can you tell me how long copying files into phone storage takes?? Do you feel like ROMs are geting installed slowly than previous, slow copying of files?
ASOP Roms like CM never come with baseband. they use the same baseband that you already have in your phone. Only Stock based comes with baseband in their firmware. Sometimes(not most of the time) it can be if you are using different baseband than the one of the firmware, like if you have 4.1.2 and installed baseband of older version like of 4.1.1 but this is exceptional..
Thanks for your reply!
I don't think the internal sd has gotten slower tbh. I tried to copy an 2gb dummy bin from the extsd to my infernal sd, which copied with an average speed of 9mb/s.
I have tried experimenting with different TW based roms in the past, so I might still have a wrong baseband / ril. Is there a way of checking this?
Sent from my GT-I9300 using XDA Free mobile app
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