So I have been having problems with my Focus 1.3 and the GPS not working after installing Mango. Everything has been official, and I think I found a permanent fix.
I found it because AT&T won't swap out my phone anymore, because I am now on my 5th replacement.
However, it really sucks because I have tested it and you need to flash back to the stock ROM to do this. I tried backups from in between and they just don't work.
After flashing down to stock, start the update process in Zune. Every time an update is applied, and Zune starts searching for more updates, CANCEL IT!
Disconnect your phone and turn it off. Wait about 30 seconds to a minute, and turn it back on.
Re-connect your phone and repeat until you have all the updates.
I tries letting my phone sit through on auto and my GPS was gone in an hour. Doing this, I have had it work for over a day. I haven't been able to test longer because of the flashing needed to verify.
Related
My phone has been working fine for a few months now, after several flashes (cant pick a ROM ) anyway, a few days ago it started acting funny. It would freeze just doing normal everyday tasks, then it would just start working again like nothing happened after about 2 minutes. Now today, it freezes on my welcome splash (the one after the htc, the windows splash). and it just sits there. Sometimes, if I let it sit for about 10 minutes, it will start up-VERY SLOWLY, and if you go into any menus, it freezes. I tried to re-flash, but it wont establish an activesync connection. Is there anyway to get the phone to flash in my situation? Hopefully, I could flash it back to a cingular rom and send it in for warranty.
Did you tried to hard reset your Wizard by resetting while holding Comm Manager and Voice Command button?
Yeap, runs through the set up, gets to the screen where it says "customizing in 3...2...1" and shuts off.
Well, today, it completely died. Won't turn on, tried a new battery.....nothing. Do you think, since it won't turn on, I may be able to sneak it by Exchange By Mail???
Fixed it! For some reason, the first time I tried a new battery, it didn't work. Tried it again just for the hell of it, and it fixed it. Strange.....
My G1 has recently started playing up. The problems first started with cyanogen 4.1.9999 - it would loose signal, but a reboot sorted this out and it may only happen once every two or three days if that. It was an unstable ROM, no biggy.
But then one day, after rebooting, it got stuck at the android screen then just turned itself off. This repeated several times before it just wouldn't turn on. I left it for a while and tried again later, it turns on, boots but no signal. Rebooting did nothing.
I reflashed (without wiping) cyanogen 4.1.999. and everything seems okay. But then the phone started crashing and rebooting rather a lot, and rather unpredictably. So I wiped, flashed the ADP rom and then cyanogen 4.2.1 rom. This process was a massive brainache - plugging in the usb cable managed to crash the phone within 2-5 min guaranteed, it automatically rebooted.
So here I am. Cyanogen 4.2.1 - after a complete sdcard format, wipe, ext3 repair and flash. The problems still persist! But it's temperamental, a lot of the time I loose signal still, it often reboots itself and hates anything plugged in the usb when it's turned on - making charging the thing awkward.
I used the log collector app to get these logs
http://nopaste.info/17b5351296.html
http://nopaste.info/2e98b9d044.html
At some point during those logs, the signal is lost. The log collector doesn't seem to retrieve a very long backlist, these were taken minutes apart but don't overlap, so I haven't caught a crash. I'm not sure if there are better ways to view logs/debug?
But it's all very temperamental. Occasionally it boots up and life is fine. But more often than not it will loose signal and reboot itself somewhere along the line.
Has anyone come across anything like this before? When it looses reception if I manually try an connect to a network it will say
"This SIM does not allow a connection to that network"
Click to expand...
Click to collapse
I've read that could perhaps be a problem with the sim... but the sim wouldn't cause reboots would it?
Any advise would be great. I bought the G1 off ebay just under a year ago, so no warranty.
I updated my phone manually through Mini Kies.
Before the update with or without OCLF applied, the phone would never freeze. Since I've applied the update the day before yesterday, the phone has locked up three times. Basically what happens is, the screen will, well, freeze, and my button presses do absolutely nothing, I hit the back button- phone vibrates, does nothing, same with home button. To power it off I either hold the power button for 5-10 seconds, I have not yet had to pull the battery. HOWEVER. This last time it froze, I powered down the device but the phone would not turn back on. I pulled the battery from the phone and inserted it back in and after doing so my phone powered back on with no problem. It's a bit concerning though. Probably the worst thing about all of this is the fact that my phone runs great! Fast and responsive, GPS seems to be spot on. Except about once a day since the update, it freezes.
Any ideas? I have no experience with modding/flashing anything so I get really nervous with things like installing custom roms. I was thinking I could roll back the update and then re-do the update. I doubt I'd get the update OTA though, I updated my girls device OTA and she has had no problems so far.
I was even considering flashing Bionix, but again, very nervous to do so. I even had trouble just creating a nandroid backup! I couldn't get into clockwork recovery to do so.
Can anyone just baby me with this? Tell me where to start?
Thanks :/
I would suggest you flash back to stock firmware using Odin.
Go into the Development section and look at the directory sticky. There is a link in there for a thread on how to go back to stock firmware.
Once you flashed back to stock, i suggest using it on stock for a day or two to make sure the phone work correctly. Once you verified the phone working then try to update to JI6 again via Kies mini.
Other than that you can start to mess around with flashing different custom firmware and mods. It hard to brick the phone since you can always go into download mode and odin back to stock.
Be adventurous! Good luck!
would you suggest that I go back to stock before trying to flash bionix?
Wearespacepeople said:
would you suggest that I go back to stock before trying to flash bionix?
Click to expand...
Click to collapse
You should go to JFD then to JI6. Freezing isn't normal, I don't have any freezing. If it was randomly freezing there would have been a 10 page thread on it already.
I've also had it freeze twice on me. Went from rooted Stock to JI6 using Odin. /shrug
Same issue after applying JI6 OTA. I unrooted before applying the OTA, but have now reapplied OCLF with stock.
Same issue. Frozen hard twice. Browser exits randomly. Battery drains about twice as fast as before JI6.
I went from fresh Stock to JI6 via Odin. I don't know if I can wait for Froyo. I may just go back to stock again, even with the broken GPS.
I bet the OP has a bunch of apps installed.
A lot of people are blaming the update, but I'm almost sure there are many rogue apps in the marketplace, because last night I was getting freezes and after I uninstalled all the apps I don't actually need (or use very frequently) all of the freezing just stopped. The phone runs smoothly now. And removing those apps + removing the Task Manager widget from one of my screens increased my battery life by ~200%.
I installed BioNix 1.9.1 (with JI6) and I'm still getting occasional freezes, but I'm wondering if they are due to Angry Birds which I installed at the same time as my original JI6 OTA update. I'm seeing some reports (forum.androidcentral.com/motorola-droid/38906-freezes-weird-stuff-angry-birds.html) , but I have no idea if this is a valid idea.
Anyone else seeing freezes with JI6, but not angry birds?
I've also been having freezing problems, and I think they're GPS related.
The last time was last Friday. I was driving down to Washington DC using my phone for turn-by-turn navigation, and it froze about 1/3 of the way there. I had to pull the battery out to restart. When I got to my destination, I was using Maps and then the browser, and while the GPS icon was on the notification bar, telling me it was trying to find my position, my phone froze again. Again, I had to pull the battery out. Both happened within around a 1.5-2 hour period. I realized it may be due to the GPS, so I turned off GPS right away. It's now Monday afternoon and my phone hasn't frozen since.
heya guys,
I'm on stock FW on my GS4S i9505 and yesterday morning i update to 4.3 OTA.
It was working all day just fine without issues or lag for the matter.
Today morning when i woke up, my phone was plugged into the charger and was turned off.
I turned it on by couple of mins later it would freeze and wont unlock, just black screen with a red light flashing on the top left of the phone.
I had to pull out the battery and put it back everytime i wanted to try and boot it.
I did that 3 times within 10mins and the 4th time it just stopped turning on all together.
Anyone has this issue and maybe can give tips on how to fix this if possible?
Thanks in advance.
re: auto updates
Smokie Smokerson said:
heya guys,
I'm on stock FW on my GS4S i9505 and yesterday morning i update to 4.3 OTA.
It was working all day just fine without issues or lag for the matter.
Today morning when i woke up, my phone was plugged into the charger and was turned off.
I turned it on by couple of mins later it would freeze and wont unlock, just black screen with a red light flashing on the top left of the phone.
I had to pull out the battery and put it back everytime i wanted to try and boot it.
I did that 3 times within 10mins and the 4th time it just stopped turning on all together.
Anyone has this issue and maybe can give tips on how to fix this if possible?
Thanks in advance.
Click to expand...
Click to collapse
You will need to go to SamMobile.com and download the official odin flash firmware
for your phone's exact model and flash it using Odin.
That will get the phone into good working condition with the stock 4.2 firmware.
After that you can use the phones built-in updating system again and most likely it
will work just fine. Just be sure that the battery is at least half full before the phone
starts the auto-update process.
Perhaps you installed some app or game from the playstore which did not play nice
with your phone and caused the 4.3 update to get stuck or it could have been the
battery if it did not have enough charge in it.
You should try to get the phone into download mode to see if it can be Odin flashed.
Hold the volume down key at the same time while holding the the power key down
for 20-30 seconds and see if it goes into download mode.
If it does you have nothing to worry about.
NOTE: before trying download mode be sure to remove the battery for 5 seconds
and replace it, making sure the phone is in a power off state before trying to boot
it into download mode.
Misterjunky said:
You will need to go to SamMobile.com and download the official odin flash firmware
for your phone's exact model and flash it using Odin.
That will get the phone into good working condition with the stock 4.2 firmware.
After that you can use the phones built-in updating system again and most likely it
will work just fine. Just be sure that the battery is at least half full before the phone
starts the auto-update process.
Perhaps you installed some app or game from the playstore which did not play nice
with your phone and caused the 4.3 update to get stuck or it could have been the
battery if it did not have enough charge in it.
You should try to get the phone into download mode to see if it can be Odin flashed.
Hold the volume down key at the same time while holding the the power key down
for 20-30 seconds and see if it goes into download mode.
If it does you have nothing to worry about.
NOTE: before trying download mode be sure to remove the battery for 5 seconds
and replace it, making sure the phone is in a power off state before trying to boot
it into download mode.
Click to expand...
Click to collapse
Thanks for the reply dude.
I'd love to do that, but i dont see how this is possible since the phone doesnt boot up at all anymore.
Any ideas?
Maybe your battery is dead? Because it's known issue on Galaxy S4 phones.
Try another charger.
I tried with my wife's S4 battery and my colleague's S4 battery.
Also tried with 3 different charges that came with the S4, no dice... :/
I had to take it back to the store, it was under warranty still.. they are sending it back to Samsung and will get it back in 2-3 weeks, same phone repaired or a refurb i guess.
After doing more search and with the help of some falks from #Android @ EFNET, we came to the conclusion that its an issue with the EMMC chip just like the first generation of Note 2 and S3.
What's pissing me off is that Samsung fixed the issue on Note 2 with a new patch of phones, so newer phones didnt have the EMMC issue as far as i can tell. SO why the hell would they still use it for the S4 is beyond me.
Just a word of advice, if this happens to anyone, make sure you run a backup as soon as it boots back up the first time.
In my case, it booted 3 times by removing the battery and putting it back and froze 3 times, there was no 4th.
If i tried to backup the phone the first or second time it booted, i could still have my data to be restored on the new repaired phone.
This should be marked as closed unless some other people with the same issue want to discuss it here.
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
I have had this issue on both at&t and t-mobile firmwares, but only while rooted.
Best thing to do is to re-flash the stock firmware again(or go to a different firmware if you'd like) but this is the reason I'm currently avoiding root. It soft bricks about a month in and is an easy fix but its annoying.
Was wondering about that too (flashing the stock firmware). But, will it wipe everything I had on there? Will any of my txt msg's and photo's or summat be lost to the ether?
Stupid question, I know, but had to be asked.
Thinking about flashing stock firmware and rooting agin for the sake of being able to do it again lol.
Well, if you flash stock, it does factory reset. That's why I have backups lol all I have to do is log into my Google account and everything is there.
buntobo said:
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
Click to expand...
Click to collapse
Did you have security log or security update disabled as that updates and causes weird after affects.
buntobo said:
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
Click to expand...
Click to collapse
These two threads describe exactly your issue and solution - http://forum.xda-developers.com/verizon-s7-edge/help/g930t-updates-unroots-overnight-t3426636 and http://forum.xda-developers.com/tmobile-s7-edge/help/rooted-weeks-rebooted-stuck-t-mobile-t3425814
I had the same problem, twice I had a rooted device totally lock up and had to re-do everything. But after disabling the security updates as advised, I'm currently going on two months without a problem.
Hope this helps!