Ok, I've been having this issue since DK28. Ever since I updated to DK28, I've been having frequent freezes and lock ups (~5times a day). It sometimes happens when I'm not using the phone at all, for example when it is charging overnight it will have the red led light on (sometimes with the 4 capacitive buttons on the bottom lit up) and won't respond to anything I do to it.
Sometimes the phone freezes when I'm using it, and in this case the phone gives a single vibration followed by three quick ones, and it repeats this vibration sequence (1->3 quick bursts->1->3 quick bursts->...). And sometimes it will even reboot itself and most of the times it freezes again immediately and repeats the vibration sequence (on rare occasions it resumes normal operation). But normally, I have to do a battery pull.
I had my hopes on EB13 fixing this issue for me but I still have this issue. Ever since I had this problem I tried almost every single custom and stock DI18,DK28,EB13 ROMs out there but nothing fixed it, albeit DI18s did reduce the frequency of freezes to about 1~2 a day. I googled and searched on this forum and two of the suggestions were to remove the SD card completely and do a fresh install of stock ROMs and both didn't work.
Anybody have similar issues? I don't even want root or custom ROMs anymore... I just want a phone that can function without having to pull the battery out all the time.
I would try backing up the data on your sd card, then reformatting it. I have seen a lot of problems caused by sd card errors.
After that, I would odin to fully stock di18. Run that for a while and see if your problems are still there. If so, I dont know how to help you.
Per your suggestion, I formatted the sd card and used odin to install stock DI18. Unfortunately I'm still getting freezes... Could it be something I'm doing wrong using odin? I uncheck everything except Auto Reboot (I did on accident had the F. Reset Time checked on a couple of occasions in the past, could this be the reason?). Load the victory_8G_100528.pit file, and DI18 tar in PDA. Using Odin3+v1.61. Is rebooting all the time the only solution to my problem?... I'm desperate
Wondering if you some how got a corrupt download on the stock files for odin. Seems unlikely but dont have many other ideas for you. I pulled this from the wiki:
Odin Stock Flashing
What is ODIN? ODIN appears to be a Samsung factory piece of software that is designed to flash multiple phones at one time. Works very well and is easy to use.
Odin : http://www.sdx-downloads.com/devs/noobnl/Odin3+v1.61andepic.pit.zip
USB driver, under the Software category here: http://www.samsung.com/us/support/downloads/SPH-D700ZKASPR
IMPORTANT: Make sure you have installed the drivers before starting. Also, remove the SD card from the phone (this may not be necessary, but having the SD card installed has caused Odin to fail for a number of people, so might as well just do it).
1. Open odin
2. Put your phone in download mode (Shut it off, wait for lights to all go out, then hold 1 on the keyboard while powering up)
3. Connect phone (you should see odin put a Com4 or something like that in the first box. The actual number is NOT important what is important is something popped up there when you connected your device, meaning ODIN can see it)
4. Select the victory_8G_100528.pit on the right in the pit section
5. In the PDA Section place the full Stock DI18 tar (SPH-D700-DI18-8Gb-REL.tar.md5 approx 255 MB) for a full wipe and full return to stock. You can get the file from a number of sources here: http://www.multiupload.com/X9AB1U56JV
6. Hit start. It will do its thing. Doesn't take long you can see the progress bar. If it sits on File Analysis for longer than 30 seconds its not going to happen. See the troubleshoot section below.
7. Device should reboot and should be done. You will have to root / install ClockworkMod.
Click to expand...
Click to collapse
You could try a fresh download and follow those steps. Redownload all the files from these sources before you try again. There are a lot of versions of the files floating around.
A stock epic on DI18 should not be having force closes. Pretty much ever.
By any chance are you restoring data from a backup? If you are that might be the problem.
Is the phone damaged perhaps? Dropped too many times?
Just throwing some ideas out there. Where there is a will there is a way. You should not be getting these FCs. Got to be a way to fix it.
Related
Phone is Verizon Galaxy Nexus, running the vicious jellybean build that first came out (yeah I was too lazy to install a new ROM when the first Jellybean build I got my hands on worked fine)
Alright so here's the sequence of events,
Last night - phone working just fine
When I went to look at my phone and set an alarm for when I went to sleep I noticed it was powered off. So I tried to power it on and it hanged at the Google logo. It did this for about 20 minutes, and then I pulled the battery and tried again. This time I left it at the Google logo bootscreen over night (plugged in). Note: I'm not sure if it was bootlooping or hanging at this point, I don't remember it vibrating)
I'm awaken in the morning by the sound of my phone vibrating every 10 seconds. I look at my phone and it's at the unlock screen but the only things I can do are emergency call and, strangely, it asks me to enter a password to decrypt my phone. I never encrypted it. I started freaking out, at this point I probably should of started Googling for a default password or something, but in my morning stupor I rebooted the phone and it just bootlooped on me.
I got into CWM recovery, looked for a NANDROID backup but it kept telling me sdcard wasn't mounted, and attempting to mount it failed. I'm not seriously scared.
Reboot back in to CWM recovery to see if anything changes. Nope.
I Google this problem and land on this page. (I guess I can't post links, but it tells me I just have to reflash CWM) I think, "oh, I just have to reflash CWM. Not too hard!
I downloaded the GN toolkit and update to the latest CWM touch.
Attempted to reboot phone - nothing happens. All buttons unresponsive, no battery shows up when trying to charge. My laptop doesn't find it.
More Googling. I land on this page (link removed - GSM forums for legija's .bat unbrick fix thing), so I try plugging in my phone to my laptop without the battery, sure enough I see the OMAP 4460 device attempting to install. I follow the instructions and install the OMAP drivers, but when I plug in my phone it acts as if its being unplugged and replugged back in constantly. It won't stay connected for more than 3 or 4 seconds without reconnecting, so any attempts to try and use the .bat file fail
And so that's where I am. I have my phone plugged in right now incase for some reason it isn't charged, but I'm stuck. I hope I gave enough information for anyone to help me, thanks!
Sleete said:
[*]More Googling. I land on this page (link removed - GSM forums for legija's .bat unbrick fix thing), so I try plugging in my phone to my laptop without the battery, sure enough I see the OMAP 4460 device attempting to install. I follow the instructions and install the OMAP drivers, but when I plug in my phone it acts as if its being unplugged and replugged back in constantly. It won't stay connected for more than 3 or 4 seconds without reconnecting, so any attempts to try and use the .bat file fail[/list]
And so that's where I am. I have my phone plugged in right now incase for some reason it isn't charged, but I'm stuck. I hope I gave enough information for anyone to help me, thanks!
Click to expand...
Click to collapse
some also have had this issue "It won't stay connected for more than 3 or 4 seconds without reconnecting, so any attempts to try and use the .bat file fail"
but no, they've managed to do it in the end, it's just that you have to be ultra-quick
can you still get in fastboot/bootloader? if yes, flash latest twrp (i'm sure it supports encryption); if after flashing twrp it still doesn't work, flash google stock images by following the procedure here
Thought I should update this in case anyone else manages to hard-brick their phone, but I sent it in to Samsung and they replaced the entire mobo under warranty. I think they either didn't care or it was bricked enough where they couldn't tell I rooted it. Also good side effect of fixing the finicky USB port on my phone. Happy ending!
So I just wanted to flash omega rom onto my T-Mobile i9505 galaxy s4. It worked, but the wifi didn't work, and it said that I needed to flash a file through odin. I flashed the file, but an error occurred in odin. Then, I unplugged my phone, and booted it into twrp recovery. All of a sudden, it asked me for a password, which I did not set. So I hit cancel, then did a wipe of the cache and user data. I then tried to go and flash an old rom, but all of my microsd card files were not there! The folders were showing up, but not the files. Then I tried to boot my phone and it wouldn't boot at all. After trying to install a stock firmware through odin, the phone turns on for 2 seconds, then shuts off. I can't get into recovery anymore either.
First, do you mean you have a T-Mobile M919 S4 and you tried to flash an i9505 ROM?
You are able to, but I want to just clear things up.
Let me write a little something, then we'll see if we can get you back to where you want to be.
- Sometimes when things don't go 100%, you gotta take a deep breath, step away and then go over the steps you took to get to the point of where the issue started. When in doubt on what to do next, youccan read around the threads on xda and other resources. After doing a little research and you still have doubt, just ask questions by posting the issue likeyyou're doing now.
The natural reaction is to fix the issue, and to do this and that without being sure. The combination of the latter with a little panic and perhaps not enough patience, can make matters worse. I'm not saying all of the above pertains to your situation, but some of the comments may, as they have to me during certain situations. Anyway, something to keep keep in mind for the future
Now to the issues at hand.
Can you get into download/ODIN mode?
Power down the phone and pull the battery.
Wait 10s and insert the battery but Don't power on the phone.
Hold power button & volume down button at the same time until the screen turns on.
When you've read the above, let me know if you're able to get your S4 into Download/ODIN mode.
Fixed
The problem was that the phone was just completely out of battery, and I was trying to flash the stock firmware onto it but it could not boot into it because there was no battery. Charged it, and could access recovery and the phone booted! Yeah I guess I wasn't patient and made a simple mistake. OP, Please close thread thanks!
bob10123 said:
The problem was that the phone was just completely out of battery, and I was trying to flash the stock firmware onto it but it could not boot into it because there was no battery. Charged it, and could access recovery and the phone booted! Yeah I guess I wasn't patient and made a simple mistake. OP, Please close thread thanks!
Click to expand...
Click to collapse
Ah, :good: to hear.
I sometimes forget to add that step and another into my tutorial/how to posts:
- Prior to ROM installation, please make sure you have at least 50% battery charge available.
- Please check your usb cable to be in good working order.
The above are 2 reminders are a of couple of the most overlooked steps prior to flashing ROMs and other associated goodies
Hello all! Let me start by saying that i have researched a ton and there is a lot of great information on here. The info I've read however doesn't seem to work for me.
My situation is I spilled a little bit of water on my phone (really not much), but it got inside my phone a little, which was already rooted using auto root. My power button thinks its constantly being pushed (i think). It doesn't bootloop, but as soon as i pop the battery in it turns on, and my phone was unresponsive to me clicking the power button. The rest of the phone was fully functional and i checked with Tmobile and it is still under warrenty (didn't mention the water). They told me to backup the phone which i was able to do in kies with no problem. Then they said do a factory reset, which again I did with no problem. It didn't solve my issue which i kinda knew it wouldn't, so the next step for me was to unroot my phone so i can return it. I popped it in odin, selected the original firmware and it started , then it disconnected by itself. Now the firmware upgrade screen pops up, but i am still able to get it into download mode (for me since the power button is suspect) i just have to hold the home and volume down, pop in the battery and it goes to download mode. The problem is that every time i try to hit start in Odin it gets to the part about the PIT partition and disconnects and says there is no PIT partition. Everywhere i've read says to either use a PIT partition (can't find one for the M919) or that the partition is in the m5 file, which as far as i can tell it is not (at least not it's own file). I've tried downloading the stock firmware from a multitude of different places even Sammobile with no luck and I've also tried different computers, different cables, and all the USB ports available to me.
Can anyone please tell me where to go from here please? I need to get this replaced asap!
Are you asking for a .pit file to repartition? If so, I've attached one for a 16GB SGH-M919 ONLY, dumped from my own SGH-M919 through Heimdall. Download the .zip, unzip it somewhere. In Odin, check repartition, and click PIT and select this file. Hopefully this fixes your problem, but use this at your own risk.
View attachment SGH-M919.zip
I've had my Samsung Galaxy Tab S 8.4 (SM-T705Y) for just over two years now and it has worked brilliantly beside the odd issue here and there, including the device freezing from time-to-time. Each time that particular freezing issue has happened, I've used the 'Power and Volume Down buttons' technique and it has successfully fixed the issue.
Now, a few days ago, I was using my tablet for normal morning things; music app playing in the background, YouTube opened on the side, using the preinstalled Browser and Google Chrome apps, etc. I am not sure if it was updating any Google or Samsung apps at the time. The screen froze up so I left it for a few minutes, seeing if it would unfreeze. When it didn't, I used the same Power and Volume Down technique, which successfully forced-restarted the tablet. There was a small mistake I made doing this; I was holding down both the Power button and Volume Up button. It took me around thirty seconds to realise why the screen wasn't turning off and switched to the Volume Down button. At the time, both my earphones and the charging cord were connected.
However, upon the loading screen, I noticed that it did not pass the Samsung logo screen with the little explosion of blue circles and just kept replaying the same animation repeatedly. The Application History and Back buttons did not light up and the device did not vibrate as it normally does when it boots up. I repeated the Power-Volume Down technique to see if that would fix the issue. Once again, the tablet rebooted normally but was stuck at the logo screen playing the animation. I tried this same force-restart again, this time without the charger plugged in. No change.
So, I left it running through the animation while doing Google searches through forums and getting into contact with Samsung as to what the issue could be. I'll list down below what my tablet can and can't do at the moment and hopefully someone will have a clue as to what is going on and how to fix it. I will point out now that it was not going through a firmware update at the time, the device is not rooted and nor do I plan on taking that path with it, and I have not made any changes to it that can void the warranty.
It can:
- Recharge (The battery icon will show up if it is force-restarted and the charger is plugged in at the time.)
- Reboot (It's not exactly stuck in a bootloop, more of just the 'explosion' animation replaying over-and-over.)
- Enter Recovery Mode
It cannot:
- Enter Safe Mode
- Be Shut Down without the charger attached (As stated above, the device will only turn off with the Power-Volume Down buttons held for about 30 seconds and that causes the device to restart, not turn off. The only way for it to completely shut down is to have the charger connected and then unplug it after the battery icon appears.)
I have tried removing the SD card and placing it back in, power-cycling it, letting it run on the animation until the battery runs out and then letting it recharge to 100% before turning it on again, connecting it to Samsung Smart Switch (which recognises that there is a Samsung device connected, but not being able to register the device itself), and wiping the Partition Cache (Also note; the Recovery Mode has the 'No Command' sign with the android laying down and the red triangle with the exclamation point above it. Clearing the Partition Cache seemed to go smoothly, however when I chose the 'reboot device now' option, the 'No Command' sign changed to 'Error!' and rebooted the device anyway.) I am now currently trying another technique written on a different website (though since I am a new user, I cannot post up URLs at the moment). So far, plugging in the earphones alone hasn't worked and the device is currently connected to my laptop - which is shut off - and still has the earphones connected, but the animation is the only thing the screen is still showing.
I have important files saved in the internal storage of my Tab S and I do not have them backed up, which is the only issue that's stopping me from just going ahead and doing a Factory Reset as I cannot lose these files.
I am unsure if my Tab S is soft-bricked or if this is another issue entirely and I just missed something that could have already fixed it.
Yes, this is a long and detailed post, but hopefully with these details, someone will be able to help with this issue. If I can restore my Tab S to its condition before the freeze, that would be amazing, but I can definitely settle with only being able to salvage my files from the internal storage and then performing a Factory Reset on it.
Thank you in advance~
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
edan1979 said:
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
Click to expand...
Click to collapse
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
AussieMouse said:
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
Click to expand...
Click to collapse
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
edan1979 said:
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
Click to expand...
Click to collapse
Alright, I'll try that and let you know how it goes. Is there any specific website I should download the firmware (4.4.2 KitKat) from? (Yeah, I agree with you there! Still, just to be on the safe side~)
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
edan1979 said:
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
Click to expand...
Click to collapse
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
AussieMouse said:
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
Click to expand...
Click to collapse
MM is ok. I dont have any problem with it.
edan1979 said:
MM is ok. I dont have any problem with it.
Click to expand...
Click to collapse
Thank you so much for your help! I managed to find the KitKat 4.4.2 firmware on SamMobile and flashing it restored everything~
Have had this problem for about two weeks now. Every time I get the phone able to boot (either by reflashing a rom or odin) it will work for a few hours then it'll freeze in the middle of use or idle and restart. After restarting a few times the phone will no longer boot and I have to reflash it with odin or TWRP. It's happened so much though that as of today even if I get it to start it'll end up freezing up shortly after booting, get stuck on the black start screen and hang there until I pull the battery. At that point the phone will only boot into download or recovery. I'm at the end of what I can do and out of ideas.
So far I have tried
Odin to:
N910PVPS4COK1_N910PSPT4COK1_N910PVPS4COK1_HOME.tar.md5
N910PVPU4DPH4_N910PSPT4DPH4_N910PVPU4DPH4_HOME.tar.md5
and flashing multiple different roms to try to fix it.
Sometimes it won't even mount data, cache, system, etc within twrp.
I've also tried to format each individual partition when it wouldn't start no matter what and that did make it so it was able to start but the same problems were there after it did start.
I've searched and I cannot find a solution to anything similar to the problem I'm having. If anyone has any ideas they'd be greatly appreciated.
justintworley said:
Have had this problem for about two weeks now. Every time I get the phone able to boot (either by reflashing a rom or odin) it will work for a few hours then it'll freeze in the middle of use or idle and restart. After restarting a few times the phone will no longer boot and I have to reflash it with odin or TWRP. It's happened so much though that as of today even if I get it to start it'll end up freezing up shortly after booting, get stuck on the black start screen and hang there until I pull the battery. At that point the phone will only boot into download or recovery. I'm at the end of what I can do and out of ideas.
So far I have tried
Odin to:
N910PVPS4COK1_N910PSPT4COK1_N910PVPS4COK1_HOME.tar.md5
N910PVPU4DPH4_N910PSPT4DPH4_N910PVPU4DPH4_HOME.tar.md5
and flashing multiple different roms to try to fix it.
Sometimes it won't even mount data, cache, system, etc within twrp.
I've also tried to format each individual partition when it wouldn't start no matter what and that did make it so it was able to start but the same problems were there after it did start.
I've searched and I cannot find a solution to anything similar to the problem I'm having. If anyone has any ideas they'd be greatly appreciated.
Click to expand...
Click to collapse
Try falsh repair firmware with pit file in odin.
Do factory reset immediately from recovery after flash firmware to get clean OS.
You can download repair firmware from here
https://www.androidfilehost.com/?fid=24591020540821805
Extract firmware you will get pit file inside of it.
Trex888 said:
Try falsh repair firmware with pit file in odin.
Do factory reset immediately from recovery after flash firmware to get clean OS.
You can download repair firmware from here
https://www.androidfilehost.com/?fid=24591020540821805
Extract firmware you will get pit file inside of it.
Click to expand...
Click to collapse
I used both of them for a restore and did a factory reset and things looked good for about 30 minutes and now its back to the random freezes that turn into a restart
justintworley said:
I used both of them for a restore and did a factory reset and things looked good for about 30 minutes and now its back to the random freezes that turn into a restart
Click to expand...
Click to collapse
I suppose this is a long shot, but are you running on the original or an old battery? It's possible that a bad battery is causing the reboots. I was back and forth to the Sprint store about 4 times in one week. They first tried flashing the firmware. (Yeah, I could have done it, but I have insurance.) They sent me home and on the way my phone rebooted itself. I got a replacement Note 4, but it started getting hot, then also rebooting. They "let" me upgrade to a Note7, which I loved. I had to give it back even though it was from the new, supposedly safe batch. At this point, I couldn't even get the Note 4 to boot at all. Boot loops, or would boot into download mode. Couldn't do anything with it, except pull the battery. Got a third Note 4, but also ordered a new battery pack from Sprint. They were and still are, only $24.95, with free shipping! You get a new battery, an external charging unit and a carrying case for the battery. (You have to use your own charger.) This finally fixed the problem. I had two batteries when I ordered the new one. I'm pretty sure one of the older batteries was defective, even though it wasn't bulging. I'm still using the other one that's also older, even though it is bulging a bit. It charges and runs fine. No over-heating. So, my problem was a combination of a defective battery and a couple of bad phones. The other thing was some of the previous firmware seemed to make some Note 4s run hot or get hot while charging. Things are much better since PG1. YMMV.
I had this issue and sent my phone back to Samsung THREE TIMES, I thought I bricked my phone from custom rom.
Turns out it was my battery. Sounds dumb, but true. Strangely even with battery out, I was having issue. Once I put in new good battery issue resolved.
I had that issue on my pc and my note. I had a creepy stalker in full control of my device (which basically was a virtual machine). I could tell when I was on the right track to get rid of him because it shut me down. I can't say that's what's going on with you but it is a thing.
Sent from my SM-N910P using Tapatalk
Note 4 batteries are dying for lots of people anywhere from 18 months to just over 2 years, and the symptom is often fail to boot, boot loops, etc. As piggynuts said, it's not logical, but it's true. It happened to me, and when I replaced the battery, everything was fine.