Related
Can someone lead me to the files I need to flash my Fascinate back to 2.1 from the Froyo update. I'm not sure what files or Odin i need to do this. I'm having an issue with my 3G disappearing and dropping since going to the OTA froyo and never had problems with it on 2.1 so i'm trying to go back to stock 2.1, maybe even try to goto Froyo again [maybe something got corrupted or something]. Before i got about getting a new one, i'd like to see if I can flash back to 2.1 and get it working again.
There's a stock package that you can use to Odin back to DL09 (eclair) here. That same thread gives an easy way to get back to froyo if you want to try again.
Alternatively, if you're just having connectivity issues, you could simply try another radio. Some people have a better time with DL09 modem, at least compared to EB01 and EC01 (not sure whether anyone finds it better than the current one), and you can Odin just the modem here. You might want to try this first and see if it does the trick. DL09 modem works fine with leaked froyo releases, so it should be okay with the official one.
blandj said:
There's a stock package that you can use to Odin back to DL09 (eclair) here. That same thread gives an easy way to get back to froyo if you want to try again.
Alternatively, if you're just having connectivity issues, you could simply try another radio. Some people have a better time with DL09 modem, at least compared to EB01 and EC01 (not sure whether anyone finds it better than the current one), and you can Odin just the modem here. You might want to try this first and see if it does the trick. DL09 modem works fine with leaked froyo releases, so it should be okay with the official one.
Click to expand...
Click to collapse
I just flashed it back to 2.1 and im still having an issue with the 3G disappearing and dropping, you say try different radios? Which should I try, im kinda new to this, so far its lookin like i'm going to have to get a new phone. It makes me angry cuz it worked perfectly fine on 2.1 then when i updated, now the 3G just disappears randomly
qwiktune said:
I just flashed it back to 2.1 and im still having an issue with the 3G disappearing and dropping, you say try different radios? Which should I try, im kinda new to this, so far its lookin like i'm going to have to get a new phone. It makes me angry cuz it worked perfectly fine on 2.1 then when i updated, now the 3G just disappears randomly
Click to expand...
Click to collapse
Here is an all together Rom, Theme, Radio, one stop shopping for you courtest of nitsuj17, cause he is that nice. http://forum.xda-developers.com/showthread.php?t=1013312
And a link to fix everything, instructions, files, programs, another one stop shop, but for fixing tour oops during the learning process, courtesy of me, I am helpful but i don't think anyone ever accused me of being nice. http://forum.xda-developers.com/showthread.php?t=1026746
Have fun, learn away, and don't be scared of it. Trust me, I have only heard of one person not having success recovering their phone, that was today so it is still undetermined if they were successful or not. Don't you wish a car had that kind of success rate.
DaleV said:
Here is an all together Rom, Theme, Radio, one stop shopping for you courtest of nitsuj17, cause he is that nice. http://forum.xda-developers.com/showthread.php?t=1013312
And a link to fix everything, instructions, files, programs, another one stop shop, but for fixing tour oops during the learning process, courtesy of me, I am helpful but i don't think anyone ever accused me of being nice. http://forum.xda-developers.com/showthread.php?t=1026746
Have fun, learn away, and don't be scared of it. Trust me, I have only heard of one person not having success recovering their phone, that was today so it is still undetermined if they were successful or not. Don't you wish a car had that kind of success rate.
Click to expand...
Click to collapse
Do you think changing the radio version or whatever will fix my problem here. I mean in my search to find out if anyone else has been having their 3G randomly disappear i havent see to much report. I just dont get how it was working fine with 2.1, once i installed froyo it started this problem, now im flashed back on 2.1 and it seems still "broken." Even the Verizon techs had no idea what was going on with it when i took it in. I mean can software screw up the hardware?
I was told by a Verizon rep that they knew that this OTA update would cause this problem in a certain percentage of devices and they just sent me a new one. The second in 2 weeks. When I went in and complained they just went straight to the computer and ordered me a new 1 both times, no ?'s asked really. Just hope you're still under warranty.
xdaddylongstrokex. said:
I was told by a Verizon rep that they knew that this OTA update would cause this problem in a certain percentage of devices and they just sent me a new one. The second in 2 weeks. When I went in and complained they just went straight to the computer and ordered me a new 1 both times, no ?'s asked really. Just hope you're still under warranty.
Click to expand...
Click to collapse
Hmmm, Time to go to stock and head in the store so people don't have to watch me ***** anymore. Hopefully 3rd time will be a charm.
good day.
xdaddylongstrokex. said:
I was told by a Verizon rep that they knew that this OTA update would cause this problem in a certain percentage of devices and they just sent me a new one. The second in 2 weeks. When I went in and complained they just went straight to the computer and ordered me a new 1 both times, no ?'s asked really. Just hope you're still under warranty.
Click to expand...
Click to collapse
nope, i got mine from a friend, so my only option here, buy a new one off someone else, sell mine on craigslist for the same price doin an even swap, stay on 2.1 on the new one i get lol
For those of you who haven't gotten a new phone yet or found this, here is the fix for this headache of a problem
http://mobiletech.knguyentu.com/2011/04/samsung-fascinate-random-3g-disconnect.html
Alright, so first off I've had a few phones which I have rooted and modded to the extreme. Got a great deal on a e3d and came over.
Saw that i had hboot 1.50 and *tear*, however I followed the directions to a T and unlocked the phone, installed recovery, and threw on some well known mods.
MeanROM
CleanROM
Virus ROM
etc etc
Anyway, in all of the ROMs the camera is distorted, and when you try to use 3d it comes out greenish pixelated and crashes. When you take a 2d picture you can't see what you're pointing at, but when you click it takes a picture but well...see attachment.
Now here's what i have tried:
Re-wiped ROMs several times.
Installed Stock Kernals, and every kernel I could find.
Used the Flash app, used adb reboot-bootloader and then booted into recovery to flash roms, and most recently I re-locked the phone and used the RUU updater and Unrooted and installed stock back on phone.
STILL having same problem with camera.
So I'm asking anyone who'd like to help please, because if I can't get it working I'm taking it to sprint hopefully they'll replace it.
I would try running the RUU and see if that will get the camera going.
If it runs on stock then maybe your downloads got goofed up or somethin?
Also I think MeanROM is 2.17 base? (correct me if I'm wrong) but I think you need to update firmware on the phone for stability. The camera could be related. However I also think Virus' ROMs are 2.08, so that almost makes me think that this paragraph could be wrong.
wassti said:
I would try running the RUU and see if that will get the camera going.
If it runs on stock then maybe your downloads got goofed up or somethin?
Also I think MeanROM is 2.17 base? (correct me if I'm wrong) but I think you need to update firmware on the phone for stability. The camera could be related. However I also think Virus' ROMs are 2.08, so that almost makes me think that this paragraph could be wrong.
Click to expand...
Click to collapse
Already tried unrooting and flashing RUU. Still nothing....
Edit: I tried a factory recovery and no dice.
I'm going to try re-rooting and sending the camera file to the phone. Maybe it got corrupted?
Still open to suggestions.
Nope....
Sent from my PG86100 using xda premium
Ok so camera is clearly hardware issue. I relocked and factory reset. Camera still didn't work, today I clicked camera to show a friend. I had a twenty and accidently rubbed it on the screen and magically a picture appeared but it was split. I took a picture and boom it works. I'm going to mod it again when I get home, and I'll document the results, need to find out what happened.
Sent from my PG86100 using xda premium
It's a software issue. I am going to attempt to flash the kernel again and see if I can get it to work, anyone want to give me some tips?
It looks like I am having precisely the same issue. My camera worked fine until today. I restored a Nand backup of my original stock yesterday, but the camera was working fine after that. It started acting up when my wife called me on Qik Video. Tried restarting the phone numerous times, no dice. Came on XDA to hunt for stock kernels, thinking maybe my kernel got borked in the restore process? I'm truly shocked at just how huge a pain in the rear this phone is in terms of modding. Seems I am constantly having problems with it.
RavenFB said:
It looks like I am having precisely the same issue. My camera worked fine until today. I restored a Nand backup of my original stock yesterday, but the camera was working fine after that. It started acting up when my wife called me on Qik Video. Tried restarting the phone numerous times, no dice. Came on XDA to hunt for stock kernels, thinking maybe my kernel got borked in the restore process? I'm truly shocked at just how huge a pain in the rear this phone is in terms of modding. Seems I am constantly having problems with it.
Click to expand...
Click to collapse
Mine was actually a hardware issue, it was coincidental that the camera stopped working when I changed roms. Anyway, I have a refurbished phone on its way and hoping for hboot 1.4 I doubt it though.....
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
I had a stock EVO 4G LTE running ICS, I upgraded OTA to Jellybean....had problems with the proximity sensor after the upgrade, so I put CM10 stable on it - and that worked fine for a month. Worked very well actually!
For curious reasons, I wanted to go back to the stock ROM and see if I was just imaging the issues (which Im not, others have reported), so I downloaded the "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed"
I relocked the bootloader and installed the RUU. Installed fine. However, the phone was SUPER slow. The camera had problems too...but for example, Id make a call and it would ring and call time start, but 10 seconds later the phone would vibrate indicating the call went thru, even though I was a good 4-5 rings in.
So I went back to CM10 - the same exact version I went to before. It was still on my SD Card. Totally unstable. Freezing, rebooting, screen goes blank for no reason...just all sorts of weird problems. Would freeze and reboot during a call, but the caller would still be on the line!
I reflashed the ROM like 5 times, ever time clearing cache, davlik, factory reset, and system. Still completely goofy.
I read there was a problem with the 3.15 RUU, so I followed these directions here.
http://forum.xda-developers.com/showthread.php?t=2097150
But that still didnt help.
Right now Im back on the STock JB ROM. At least I can take phone calls with it, but I'd like to return to CM10.
Any suggestions would be VERY apprecaited!
Thanks.
More things I am noticing:
The Flashlight app doesnt work anymore
Camera doesnt work then causes the whole phone to become unresponsive.
Bump!
Can anybody help me out? Im dying over here without a phone that works.
the phone app keeps crashing. If i reboot, things work ok UNTIL I make a phone call....then nothing works.
Very strange!
I would try wiping 3 times
Sent from my EVO using Tapatalk 2
---------- Post added at 09:44 AM ---------- Previous post was at 09:35 AM ----------
Also are you restoring things from the titanium backup?
Sent from my EVO using Tapatalk 2
MerkoPCS said:
I had a stock EVO 4G LTE running ICS, I upgraded OTA to Jellybean....had problems with the proximity sensor after the upgrade, so I put CM10 stable on it - and that worked fine for a month. Worked very well actually!
For curious reasons, I wanted to go back to the stock ROM and see if I was just imaging the issues (which Im not, others have reported), so I downloaded the "RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed"
I relocked the bootloader and installed the RUU. Installed fine. However, the phone was SUPER slow. The camera had problems too...but for example, Id make a call and it would ring and call time start, but 10 seconds later the phone would vibrate indicating the call went thru, even though I was a good 4-5 rings in.
So I went back to CM10 - the same exact version I went to before. It was still on my SD Card. Totally unstable. Freezing, rebooting, screen goes blank for no reason...just all sorts of weird problems. Would freeze and reboot during a call, but the caller would still be on the line!
I reflashed the ROM like 5 times, ever time clearing cache, davlik, factory reset, and system. Still completely goofy.
I read there was a problem with the 3.15 RUU, so I followed these directions here.
http://forum.xda-developers.com/showthread.php?t=2097150
But that still didnt help.
Right now Im back on the STock JB ROM. At least I can take phone calls with it, but I'd like to return to CM10.
Any suggestions would be VERY apprecaited!
Thanks.
Click to expand...
Click to collapse
i say you should flash MEANBEAN, its a stable JB rom and some of the bugs like the proximity sensor have been fixed thanks to the devs here at XDA. its running very smooth for me. the only issue for me is that google's navigation doesnt work, but telenav works just fine. just wipe your phone about 3 or 4 times (i always do that to ensure i get a clean install on any rom). good luck!
I would re-download CM10 and verify checksum since you didn't mention that.
Sent from my EVO using xda app-developers app
Thanks for the replies.
Really all I want to do at this time is go back to stock, which I currently am on.
But even on the stock 3.15 ROM, it is very very unstable. The phone is majorly delayed. I get 1 ring on incoming calls before it goes to voicemail - but the person calling hears the normal 5-6.
For CM10, I used the same zip file (stayed on my SD card) that I used without problem for almost a month.
I took the phone to sprint (back to stock) and they couldnt figure it out. Getting a replacement tomorrow.
Could I just have a coincidental hardware problem? Seems odd if that is the case, the phone was working perfectly until I went back to stock using the 3.15 RUU
I got my replacement phone last night, did an OTA upgrade to JB in the store and the proximity sensor didnt work...
was about to tell the rep to just order me a GS3, but I said hold off....I really prefer the 4GLTE over the S3
Went home and flashed Meanbean......WOW!
Just like stock, and the prox sensor works!
so my plan is to just keep this ROM until HTC fixes the issue in their next maintenance release.
in TWRP, i made a backup and selected all the options Is this sufficient to get me back to stock, then do an OTA upgrade for the maintenance release, if and when it comes out?
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