Hello guys, a couple of days ago my N7100 Note 2 started freezing randomly (while browsing the net via firefox/chrome, using Whatsapp, or even when unlocking or locking the screen) it was with a stock Android 4.1.2 (no root or anything , RIGHT OUT OF THE BOX) after a factory reset (backup & reset option) it didn't get fixed . then I decided to update to 4.3 via Kies (After a hard reset - the Vol up + home + lock buttons method) which I heard often helps in these cases, and it didn't, if anything the hangings and freezing only increased after I did that.
Then, I read online that its a common problem within the Note 2 model and that I just got an "Insane/Bad chip" or something, that dies over time.
(I have this phone for exactly 1 year now)
I dont think its an app-related issue, and obviously rooting wont help (no custom ROMs have been previously installed or anything.)
The question is, Is there anything to do before I go out and buy a new phone ?
This is very urgent due to the fact that Im using my smartphone like 24hours a day (reading,working on projects,sketching and lots of other stuff, and I actually cant handle anything without it, a lot depends on this phone.
so basically just tell me if should I go to the store today and get some S4/S5 or something instead of hoping my Note 2 will gain its functionality back ? Thank you in advance for your help.
Related
Yesterday my battery died half way through playing a game (not entirely unexpected, I'd been playing on my phone quite a bit that day and it still lasted 22-23 hours), I connected the charger that came with the phone and left it to charge while I got on with some uni work.
The phone vibrated to tell me the charge was complete so I disconnected the charger and turned the phone on as usual. After the samsung galaxy S2 splash screen, the screen lock appears and when I move it there are several error messages saying that various applications have had to stop (the main one seems to be TwLauncher but when I force close it, many others also force close). This continues for several seconds until the phone decides to restart itself and repeats the process ad infinitum until I can shut down the phone (I can manage this by not trying to get rid of the screen lock and just holding the power button until the menu appears).
I've had this phone a week (one of those days being today where it did not work at all) so it's still well within the return period but I was wondering if there is an obvious fix that I'm missing.
If not, I'll be ringing Samsung on Monday (I have coursework due for friday so I'll be devoting my samsung office hours time to that) and if they can't give me an easy fix I'll be ringing the place I bought it from and asking for an exchange.
So, has anyone else had similar issues and managed a simple fix?
Bump, I take it everyone else's phone is working then?
Giving this another bump in the hopes there's someone with a simple solution.
I don't want to have send my phone off and wait for the place to get stock.
there have been 2 firmware releases from samsung in the last couple of days, i assume you are running the latest firmware?
I can't even get the phone to stay on long enough for Kies to recognise it. It keeps restarting. Even when it was working I couldn't get Kies to work with it properly (I couldn't copy the contacts from the phone to the computer).
It's running the firmware it came with, but I can't check which version it is.
I was going to try flashing the new firmware via ODIN but I've been busy with coursework. Is this likely to solve the issue or will I just be giving the retailers ammo to reject my return?
go into recovery and do a factory reset
psp888 said:
go into recovery and do a factory reset
Click to expand...
Click to collapse
this is what I was looking for.
after googling, this sorted it out.
I just assumed download mode was the only other non-normal mode.
Thanks
Basic FAQs on the SGS1 forum mostly apply to SGS2 .Worth a look there before Google .
jje
First off, I have read all of the other soft brick threads on both xdadev and other sites, but all of them seem to address issues that come about as a result of a failed root attempt. My phone is 100% stock, running 4.1.1, and has been working great for months. I haven't installed any new apps in a few weeks, but my phone has been doing any regular updates. Today, my phone completely locked up about 5 separate times (about 2-3 hours apart for each). Each time, the only way to get my phone back was by pulling the battery (even the 10+ second press of the power button didn't work)... annoying, but manageable.
After the last lock up, my phone got stuck on the SAMSUNG logo (not the S-III logo). I let it sit there for about 45 minutes, and it was pulsing the entire time. Finally, I gave up and pulled the battery one more time. After putting it back in, the phone gets to the S-III logo, but the S is not pulsing. I've let it sit on that for over an hour - with no luck.
The failed root threads all suggest installing ODIN, rooting, wiping everything, then installing a stock firmware. I'm really hoping there is something else I can try, since wiping my phone would be extremely painful at the moment...
Anyone have any ideas?
Backup data factory reset and wipe >>> Or return phone to a service centre .
jje
Sadly as this may be, mine derped out exactly like yours one week after I bought it. It would randomly reboot, lag a lot until the day I woke up to that brilliant Samsung boot screen and nothing more helped.
Had not done anything to it so I returned it for a replacement. Turns out I had a faulty unit.
Sorry bro, guessing it's the only thing that will get yours sorted again. While I know in every product there will always be faulty units, I'm seeing dead sgs3 threads very frequently, I'm guessing Samsung's build quality isn't that good...
Sent from my GT-I9300 using XDA Premium App
It might be worth remembering ...
shaunco said:
First off, I have read all of the other soft brick threads on both xdadev and other sites, but all of them seem to address issues that come about as a result of a failed root attempt. My phone is 100% stock, running 4.1.1, and has been working great for months.
...
Click to expand...
Click to collapse
It might be worth remembering that there ARE a certain percentage of faulty units - those are all covered by warranty
It is also worth pointing out that accuracy can be a ***** - there is no "normal" Galaxy S3 that 2 or more months ago was running 4.1.1 - so if you indeed have 4.1.1 that is as a result of some (probably OTA) upgrade at some point in that interval
JJEgan said:
Backup data factory reset and wipe >>> Or return phone to a service centre .
jje
Click to expand...
Click to collapse
I would love to backup my data, but since I had a stock bootloader (not CWM or one of the others) and the PIT seems gone, I'm SOL.
xclub_101 said:
It might be worth remembering that there ARE a certain percentage of faulty units - those are all covered by warranty
It is also worth pointing out that accuracy can be a ***** - there is no "normal" Galaxy S3 that 2 or more months ago was running 4.1.1 - so if you indeed have 4.1.1 that is as a result of some (probably OTA) upgrade at some point in that interval
Click to expand...
Click to collapse
Yeah, bad wording on my part. When I bought it (the first day Amazon sold the I9300), it had 4.0.4. It has had 4.1.1 since mid-October. My comment of it "working great" was in relation to the random lockups (and now the stuck at logo issue).
Lucky for me, the phone is a work phone, so I bought a new I9300 at Fry's this morning and at least got my service and all my apps back, along with the data for the apps that were nice enough to put it on the SD...
This means my focus has shifted from returning my old I9300 to a working state to simply getting data off of it. If the bootloader shows "no product", it seems that the partition table is shot. Loading a new partition table would destroy the underlying data... so, is there anything I can do (even things that are physically destructive to the phone) to get the data (even as a single binary blob) off the internal 16GB storage?
As I said, I'm happy to rip this thing to pieces, if there is a way.
I installed jellybam 7.4 the day it was released and since then I had an issue where the phone would regularly freeze with the only way of fixing it to restart the phone (holding in the power button).
I had originally just upgraded without wiping the phone, so figured last night I'd do a complete wipe (zoots megawipe) and start again. However today I am still getting the same freezes (in fact twice in the last 10 mins!).
Any ideas what might be causing this? Is there any diagnosis app that i can run to see what's causing the freezing?
I wiped again today and installed 7.5 and still the same issue.
Thanks in advance!
I'm having the sort of the problem so I thought I could borrow this thread since our problems seems to be similar.
Can boot the device without any problems, but it freezes randomly.
Tried:
* Different roms (want to use Slim Bean and are currently using it)
* Full wipe / Factory reset
* Wipe cache / Dalvik cache
* Not allowing Android to restore my apps after factory reset (in case some app was causing this)
* Tried latest Perseus kernel (but got a bootloop so reflashed everything)
http://forum.xda-developers.com/showthread.php?t=2133401
the solution...
Sent from my Supercharged V12 Samsung Galaxy S3 using Tapatalk
Very bad Samsung After Sale Services
I'm very unhappy with Samsung
I got the same problem. Cannot use it because the screen freezes all the time so I need to unplug the battery for restart each time.
Then I decided to sent my phone to Samsung repair services. After 2 weeks, they sent it back to me.
Back to home, I turned on my phone and made a reset for the first installation but when I tried to connect into my google account, the screen has been frozen once again !!!. Then after and after ...
So the screen touch issue has not been solved even if my phone just came back from Samsung repair services. !
According to the repair document, they has just reinstalled the firmware but did not take care of the hardware.
So if this problem is well known why Samsung did not take care of this problem correctly ?
Now, They keep my phone for more than 4 weeks and did not give me a decent replacement phone with 3G at least.
For those who has got this problem, I recommand you to write clearly the problem with a letter joined to your request for the repair services before you send your phone.
Thanks.
nhariamine said:
http://forum.xda-developers.com/showthread.php?t=2133401
the solution...
Sent from my Supercharged V12 Samsung Galaxy S3 using Tapatalk
Click to expand...
Click to collapse
Thanks for your answer
Really hope this is the cause and fix for our collective problems.
Update:
After doing what I was told to do in that post the freezing was significaly lower. They still occur but not as much, from 40 times yesterday to 1 today so far.
Unfortunately I came across that thread a couple days ago, have tried the DFG method lots of times and I still get freezes. Now arguably they aren't now as frequent, but I've had days where it doesn't freeze at all, so that may just be luck.
Possibly stupid question... Are you able to flash a new firmware whilst keeping your custom ROM?
Hello erveyone i have a mega 6.3" which is now 1 year and 3 months old (comes from november 2013). Since a week or 2 the battery got problems with charging (10% in 2 hour) but working fine except that. So i visited the samsung experience store this weekeind. And well things got worser there: while i was waiting for someone to help me my phone frozed but that happens a lot so well i decided to put my phone on and off and since then its in a bootloop.. sometimes it starts like 2 seconds i see my unlock screen and can select which launcher i want to use and then it goes off but mostly it just goes onn off on off on off on off..
My phone is not rooted or anything
I have some really important documents over there so if there is a way to keep them while fixing this that would be lovely!
It was on kitkat i guess
Either try to reflash your ROM without any wipes using PC Odin or simply just do a factory reset in recovery. A factory reset shouldn't erase stored documents. If you mean actual files stored on the device. However don't blame me for data loss. This is why you should always have everything backed up with Dropbox etc
Sent from my GT-I9205 using Tapatalk
My wife and I both bought Samsung Galaxy Alpha phones when they were released. It was a fine phone until about a year ago when they updated. After that update both phones became miserably slow. As in, sometimes can't even respond in time to answer phone calls slow. Today I started the GPS and it didn't offer directions until I arrived at the destination. Yet, sometimes it'll be very fast as if nothing were wrong.
I know it's not a hardware problem because it's affecting both phones. I just replaced the battery on one of the phones (taken from a new Galaxy Alpha). Doing a factory reset didn't fix the problem. Resetting the phone helps some but not for long. I'm wondering if it's just FUBAR now? Should I try rooting the phone? Maybe Google fixed the problem in a later update.
If you factory reset it and restore everything back again you won't help the phone in anyway (if that's what you did), try using a custom ROM like EpsilROM, then delete unnecessary system apps, also try using less RAM hungry apps like Facebook or find a way to kill apps when you don't use them