Related
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.
My phone is stuck in airplane mode...
It just started earlier today, about the time I had lost signal and would have gone into roaming on the way to my dads house.
In the past Ive run Epic experience with xtreme kernel, and with 2.2 I have tried the original leak, Mammon, and I was on Quantum when it started doing this. I just tried wiping and reflashing to the newest version and its still stuck.
Any ideas?
Note: I did NOT make any attempt at flashing the 2.2 modem.
So this is what I did and it worked flash the stock rom firon or noobnl posted I foget and then flash to 2.2 again it worked for me after a few times.
Sent from my SPH-D700 using XDA App
So flash the stock 2.2 that Firon had posted to get airplane off, then flash back to whatever I want? Or do you mean flash stock as in out of the box 2.1?
Ive never had to odin or whatever all that jazz is, wasnt an option on the hero obviously, and I try to keep my messing with the epic to a minimum. So it makes me a little nervous.
Well you could flash the modem.bin in odn to make it easier idk wher t find that tho search the forums.
Sent from my SPH-D700 using XDA App
Similar Problem with Epic stuck in Airplane Mode
There is a similar thread about this problem under the Sprint Forums. Myself and several others have experienced multiple instances of the Epic randomly going into Airplane Mode on its own. Sometimes it gets stuck there for several hours. It appears that this has something to do with a weak signal. For me, it happens only at my home, where I have little to no signal. I have an Air Rave, but for some reason it appears to go into Airplane Mode more often with the Air Rave on than with it off. This is very frustrating. Sprint does not acknowledge the problem. They say it must be a hardware issue, and we should just get new phones, but I'm on my fourth phone, as is another person on the Sprint forum, so it appears to us that this is really some sort of software bug, but it does not occur often enough to cause Sprint or Samsung to take notice and do something about it.
This happened to me as well the day before yesterday... I had installed ViperRom IMpact, and had car home running navigating me to LAX, and all of a sudden, my phone reboots and then was always stuck in airplane mode after that. I recovered my original rooted rom, stock 2.1 just rooted, and worked fine... Installed SyndicateRom (2.1) and still could get signal. Tried to install another 2.2 ROM, and get the same thing where it's stuck in airplane mode... So I think I'm going to stick it out with SyndicateRom for a bit...
had the same problem a couple weeks ago for several hours. spontaneously fixed. and about 20 mins ago it went into the problem again. no apparent solution.
Possible solution...
I am on EF02 with EF10 modem. This happened to me after the phone was not touched for hours. After many reboots I decided to boot into clockwork (purple) and flush the cache and after the reboot service was restored. Possibly just a coincidence or maybe a solution?
-This is more for googlers than the op.
I have this problem pretty often when I am in a place with bad signal. Reboot the phone into clockwork recovery, in advanced options, fix permissions. This has fixed it every time. Also sometimes just rebooting it will fix it but that only seems to work randomly.
zndotcom said:
I am on EF02 with EF10 modem. This happened to me after the phone was not touched for hours. After many reboots I decided to boot into clockwork (purple) and flush the cache and after the reboot service was restored. Possibly just a coincidence or maybe a solution?
-This is more for googlers than the op.
Click to expand...
Click to collapse
I've had the same thing happen on EF02; every time, I pull the battery, boot into recovery, wipe caches & occasionally battery stats (hey why not), & every time the phone reboots with full service again.
I've seen it happen on my phone and a friend's phone. The advice below always works.
tragiquexcomedy said:
I've had the same thing happen on EF02; every time, I pull the battery, boot into recovery, wipe caches & occasionally battery stats (hey why not), & every time the phone reboots with full service again.
Click to expand...
Click to collapse
p3dr0maz said:
I've seen it happen on my phone and a friend's phone. The advice below always works.
Click to expand...
Click to collapse
Just had the same issue pop up on my wife's phone, & wiping caches fixed it a well. Thank God for XDA & Clockwork!
Ok, so my phone will not vibrate at ALL anymore. I don't want to pay the $50 to get a new one, and I don't want to have to revert back to stock and unroot and take it to Verizon to see if they can fix it.
So here's the details of what happened. I don't know if it's fixable, but I thought I'd see if anyone could offer some advice.
I was running DL30 Blackhole, very basic. Had a theme installed over it. Everything was running perfectly fine for a while. And then I was getting on the internet to do something, and connected to wifi. The wifi was through my college, so you had to login on their homepage instead of just entering a password, and the page wasn't coming up, internet was being extremely slow. So I tried turning off mobile data to see if it might force me to login to the page for wifi. Turned of 3G. Nothing happened. Turned off wifi. Turned 3g back on. Then I got a google system force close error and my phone rebooted itself.... Now I have no vibration AT ALL. No hatic feedback, no vibration for notifications. Nothing.
There was nothing even related to vibration that should have happened in this situation, my phone just freaked out. Didn't drop it or hit it on anything at all, it was laying flat on a table. So I don't know if something just fried my phone's vibration or what, but I would love it if someone out there had a suggestion for me.
I'd try just following the steps to update to super clean 2.4. some kernels act up on your version and drop the vibration. It happened to me. 2.4 is running awesome
Sent from my SCH-I500 using XDA App
Yeah I forgot to put that in the first post. I actual did a complete system wipe. Back to stock DL09, flashed the EB01 modem, and SC 2.4 over it. And still no vibration. I did all that this morning.
Also had a weird glitch where after I installed most of my apps I tried to boot into recovery and instead my phone decided to do a data wipe again, but that wasn't a HUGE issue (as long as it doesn't happen again).
Spazguitar306 said:
Yeah I forgot to put that in the first post. I actual did a complete system wipe. Back to stock DL09, flashed the EB01 modem, and SC 2.4 over it. And still no vibration. I did all that this morning.
Also had a weird glitch where after I installed most of my apps I tried to boot into recovery and instead my phone decided to do a data wipe again, but that wasn't a HUGE issue (as long as it doesn't happen again).
Click to expand...
Click to collapse
Try reverting back to stock again and prior to going back up to eb01 and superclean...wipe a few times.
I had a similar issue
Spazguitar306 said:
Ok, so my phone will not vibrate at ALL anymore. I don't want to pay the $50 to get a new one, and I don't want to have to revert back to stock and unroot and take it to Verizon to see if they can fix it.
So here's the details of what happened. I don't know if it's fixable, but I thought I'd see if anyone could offer some advice.
I was running DL30 Blackhole, very basic. Had a theme installed over it. Everything was running perfectly fine for a while. And then I was getting on the internet to do something, and connected to wifi. The wifi was through my college, so you had to login on their homepage instead of just entering a password, and the page wasn't coming up, internet was being extremely slow. So I tried turning off mobile data to see if it might force me to login to the page for wifi. Turned of 3G. Nothing happened. Turned off wifi. Turned 3g back on. Then I got a google system force close error and my phone rebooted itself.... Now I have no vibration AT ALL. No hatic feedback, no vibration for notifications. Nothing.
There was nothing even related to vibration that should have happened in this situation, my phone just freaked out. Didn't drop it or hit it on anything at all, it was laying flat on a table. So I don't know if something just fried my phone's vibration or what, but I would love it if someone out there had a suggestion for me.
Click to expand...
Click to collapse
I had a similar issue. I actually flashed my phone all the way back to stock. Still no vibrate. I think there could be an issue with the vibrate motor on the fascinate.
I say that because there was nothing I could do to bring vibrate back. All of sudden, it began working again for one day. After that one day vibrate and haptic working, it stopped working for another couple of days. Then, I dropped the phone on accident. Vibrate came back. Eventually, it stopped working again so I took the phone to verizon and they ordered me a new one.. No charge. I bought my phone in Sept 2010.
Good Luck!
When I flash DK28, I get to the home screen and screw around for a little bit and it vibrates, i think... ahh thats normal, something crashed. but a few seconds later I get another few vibrations and the screen turns off(or shows black?, but the 4 buttons on the bottom are still lit.) , shortly after I'm back where I was when you boot the phone, the arrow for unlocking and the desert rock background and it keep going over and over.
It only seems happy on di18, one quirk i hjave noticed is on dk28 the red light doesnt go on while its turning on.
Any ideas guys?
DK28 is deprecated and unsupported. Switch to EB13.
wahoa thats not a very helpful posting
The tar of DK28 is borked, but flashing to DI18 and then using the update.zip to DK28 works. Although this information is pointless to you since you went to EB13 already.
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!