Weird scenario here, just wondering if anyone else has come across anything similar. Opened up a brand new Moto E 2nd gen today. Set it up, phone freezes, reboot, did OTA update, phone bricks, flashed stock rom, phone is fine, set up, freezes and becomes unresponsive after installing some apps, reboot, stuck on "Android is upgrading Optimizing app 1 of 1" and sits there. I have retried the process over and over and continue to get the same result. I apologize for the poor layout of this post, as it is late and I've been working on this for a while now.. Did anyone else have similar problems when setting up and installing their apps initially?
At the time I'm done typing this, the phone has booted, but I'm weary that the same freeze will continue to happen. It just shows the system ui (nav and status bars) and a black screen and is completely unresponsive until I hold power to turn it off.
To me, this looks like a hardware defect. Something that should be covered by warranty, definitely as it is a "DOA" condition, since it first appeared when the phone was practically new out of the box. You should contact Motorola support so they exchange or repair the device. If they don't, then I've found that there are a few very helpful Motorola employees in their own Motorola support forums. That's where I'd go if the standard warranty support fails to accommodate you.
Related
Every time I reset or turn on my fone after shutting down, it will stuck at the logo boot up. It wasn't like that when I first bought the fone. Now it's getting worse and worse since the issue happens so frequently.
I have to take out the battery and put it back, then wait for about 3 to 5 mn before I turn the phone on.Then it would boot up as usual.
Is there anyone facing the same issue as I am? Any suggestion guys?
Are you experiencing excessive heat when this occurs? Also, can you give more info such as: does this happen only after recent charging or does it ever happen when the phone has been turned off for a long time? Was there any recent apps you installed or ROM changes when this started happening? Was there any potential damage done to the phone -dropped it, got it wet, or microwaved
When you say frequently, does that mean every time you restart? every other time? every five times?
Lastly, do you have any other issues/symptoms other than freezing at startup? Does the phone ever freeze during normal use?
i'd suggest you do a hard reset of your phone (hold down both vol up and vol down keys while powering on/resetting). that should fix the problem. if the problem still persists, it's probably some hardware faults.
Me too
My HD2 just started doing this too. It was fine for 7 weeks I have owned it. However, as described in this by OP, when doing soft reset would it would also get stuck on bootup logo. I'd have to remove the battery for a few minutes before it would bootup.
However, my HD2 also crashes and upon reboot then get stuck on bootup logo. It appears to crashes randomly eg not with any particular program or action.
I figured it was software issue so did hard reset. This worked fine. After hard reset the only software I loaded were Total Commander and Cookie Editor.
After Cookie Editor install I did soft reset and it got stuck on bootup logo. : (
So I did another hard reset but it hung up again upon reboot on bootup logo.
This appears to be a hardware issue. But has anyone else had same issue?
T-Mobile HD2
Stock ROM
Purchased July 6 2010 from Expansys
yes i am experiencing the same problem and i have uploded a video on youtube showing this! Yes my phone heats up when this happens..
Hi. I got this problem for quite sometime and am so used to taking out and putting back and taking out and putting back the batt.
But now I have another prob: my ringtone suddenly went soft and I now have to keep myself alert all the time to see if there's any incoming call or SMS.
I would like to do a hard reset but the question is: will it set my phone back to the stock ROM or still retain the updated version - 1.66.707.1?
Thanks in advance.
Stormrider75 said:
Hi. I got this problem for quite sometime and am so used to taking out and putting back and taking out and putting back the batt.
But now I have another prob: my ringtone suddenly went soft and I now have to keep myself alert all the time to see if there's any incoming call or SMS.
I would like to do a hard reset but the question is: will it set my phone back to the stock ROM or still retain the updated version - 1.66.707.1?
Thanks in advance.
Click to expand...
Click to collapse
It will retain whatever rom you are using
Htc Hd2 vodafone UK
HD2 issue
After some more searching it appears this is not uncommon for HD2. Its not clear to me if it is specific to T-Mobile HD2 or HD2 in general.
It appears to be a hardware issue. Although that is not 100% clear either. I find it hard to distinguish what some people report as 'freezing' which i believe is different to the issue described in this post which is 'hanging up' or 'getting stuck' on boot up screen - in my case it is the T-Mobile 'stick together' pink and white screen/logo.
(The 'freezing' issue that i believe is different to this 'getting stuck on bootup logo' issue appeared to have been resolved iwth new T-Mobile ROM - and I never experienced it on my HD2).
The resolution for getting stuck on bootup screen issue described here appears to have been to exchange HD2 (although some people exchanged up to 6 times and keep getting same issue!)
I think it is important to note that my HD2 performed fine for 7 weeks with lots of soft resets, hard resets, and lots of software installs (though no ROM reflashing) but within last week or so, start crashing randomly, then upon reboot get stuck on bootup screen/logo. This also became more frequent as time progressed. After doing hard reboot, the issue is now acute, eg it gets stuck on every reboot, and crashes more often.
This leads me to think some hardware has failed or degraded and is getting worse, maybe a connection/soldering etc?
However, is there any possibility that a ROM could 'degrade'? Can a ROM have a setting that is modifiable? (I know it is 'read only memory' but is it really?)
Anyways, love to hear from others on this issue.
Same problem here. Bought my HD2 in june. Cooked my own rom with Chucky's kitchen. Flashed different radios, hard resets, task 29 etc. Absolutely no problem. Worked fine for several weeks. But sometime it begun to freeze, auto resets, stuck at boot logo. It was getting worse. Even flashing stock rom it hungs at boot logo.
Now my HD2 is out for repair. Now waiting for returning. Hope they will change the motherboard.
several people have had their motherboards replaced and that has seemed to fix it for them. You'll probably have to fight with htc or your carrier, but should be able to get it replaced.
Hi guys. Another question:
I'm considering doing a hard reset. How do I store my messages before doing it? I can't seem to locate the folder that keeps all my messages.
TIA.
HD2 is an odd one
Thanks for replies. I really don't want to send it in .. but it will probably be the only way to resolve the issue. It will cost me courier there and back, and $20 'triage' fee .. total cost to me will be ~$100 just to have them look at it. Price of doing business I guess.
Anyways, I realized that one of my issues was that it was crashing when syncing. A little digging reveals that HTC Sense does something to all contacts when syncing first time putting a bit of html in contact notes field (weird but it is true .. its their way of reminding you bought an HTC phone?) So once I got it up and running, I disabled Sense and syncing went fine, no crashing.
(Btw, Sense also appears to do something with SMS msgs too so if you have lots it crashes on due to this reason too).
However, even with plain Jane MS today screen (eg not using Sense) it still crashed once on sync and again when listening to radio. Both times had to remove battery for few minutes before it would reboot without getting stuck at bootup logo.
But so far it seemed to be working 'better' without using Sense.
So, I re-enabled Sense to see what would happen and over a day it has crashed twice. I am going to see how it behaves for few days before sending it in as RMA repair.
Still, important point is that it was ok for 7 weeks, and then started crashing, more and more, even after hard reset, though some of issues may have been due to Sense (which is reported by many users).
It is still not a 'normal' thing for a $700 consumer device to have such erratic behaviour. So, given others have exchanged crashing handsets for new handset that has no issues points to underlying hardware issues as suggested above eg motherboard.
As comparison I also have HTC Diamond 2 which has been rock solid for 2 years of continuous use even with lots of software install, tweaking, reg hacks, etc.
Stormrider75 said:
Hi guys. Another question:
I'm considering doing a hard reset. How do I store my messages before doing it? I can't seem to locate the folder that keeps all my messages.
TIA.
Click to expand...
Click to collapse
I don't text a lot so i just hard reset without saving .. but do a quick search on on XDA for SMS backup or PIM backup .. during my searches I am sure i have seen a couple of utilities that do what you want.
genoki said:
I don't text a lot so i just hard reset without saving .. but do a quick search on on XDA for SMS backup or PIM backup .. during my searches I am sure i have seen a couple of utilities that do what you want.
Click to expand...
Click to collapse
Thanks. Btw I read before we can actually 'disable' Sense.
How do we do that?
Sense - go to Today
Go to Start - Settings
- iI you see the black HTC Settings (has 'Personalize' on top of items) then go to Menu and select 'All Settings' (this will show Windows Mobile's Settings. HTC Sense 'Settings' doesn't everything Windows Mobile Settings has or shows it differently)
- Select 'Today'
- Select the 'Items' tab in Today
- Check 'Windows Default' and click OK in top right.
This will 'swap' out HTC Sense 'today' with Windows Mobile standard Today screen and voila you will have 'disabled' HTC Sense and you are back to using Microsoft's Windows Mobile 6.5 version of Sense (not anywhere near as useful or neat-o to look at but hey they are pretty happy with it )
genoki said:
However, even with plain Jane MS today screen (eg not using Sense) it still crashed once on sync and again when listening to radio. Both times had to remove battery for few minutes before it would reboot without getting stuck at bootup logo.
But so far it seemed to be working 'better' without using Sense.
So, I re-enabled Sense to see what would happen and over a day it has crashed twice. I am going to see how it behaves for few days before sending it in as RMA repair.
Click to expand...
Click to collapse
Just by disabling Sense is not going to make it work. I had this problem with my HD2 also and without using Sense it seemed to be working (there were fewer crashes), but only for few days. My HD2 was getting worse day by day - it was not crashing only if it was not touched (it was crashing just cycling between Sense tabs or by initiating a call).
At repair center they told me (after three weeks of waiting) that the motherboard must to be changed.
Is it possible to damage it by flashing custom ROMs?
For me, this problem appeared after just one month of usage. I was flashed some custom ROMs.
Now, I have a new HD2 but I'm affraid to flash a custom ROM (at least in the near future).
I have my HD2 back. Took me 2 weeks, the repair center changed the motherboard and got an new IMEI.
Now all is working, no more stuck at bootlogo.
But i'm on stock rom (1.66) with 2.07 radio. No way to run Android with this radio. Hmm...
axman79 said:
Is it possible to damage it by flashing custom ROMs?
For me, this problem appeared after just one month of usage. I was flashed some custom ROMs.
Now, I have a new HD2 but I'm affraid to flash a custom ROM (at least in the near future).
Click to expand...
Click to collapse
I'm afraid as well to flash any custom rom now. For Android i need to HSPL and flash a 2.08 radio or greater to use it. But i'm stick on stock rom for sure.
I want to know as well if it possible to damage it by flashing customs roms ?
As i stated earlier, i flashed plenty of roms, doing task 29 etc., in the end stuck on bootlogo.
Thanks for the feedback on your repairs axman79 and Kalip. Btw, aside from courier cost there and back, did you have to pay the $30 'triage' fee or whatever they call it? Also, did they challenge your observations at all or did they just replace motherboard without question?
Yah, disabling Sense hasn't stopped my HD2 from crashing eith. Without using Sense it crashed several times while using Opera and more than a few times while syncing over the past three days. Also, it still gets stuck on reboot often, requiring battery to be removed for few minutes before rebooting.
So, guess I will send my HD2 in for RMA repair too (and wait for up to 3 weeks) and hope I get a functioning device in return.
Interesting though I didn't flash my HD2 but it went from 'good' to 'bad' in similar way that your two HD2's. From reading other posts around here on XDA and elsewhere it appears that HD2 motherboards fail with surprising frequency and for variety of reasons.
Would be nice to know if HD2 motherboards are unusually delicate and something physically breaks, or if there is some electrical operation, eg charging it on USB or unusual combination of button pushes that shorts something out?
The fact that battery has to be removed for few minutes in order to get thing to reboot hints that something requires charge to dissipate eg a component somehow 'locks up' which causes crash, and needs to be discharged by removing battery?
genoki said:
Thanks for the feedback on your repairs axman79 and Kalip. Btw, aside from courier cost there and back, did you have to pay the $30 'triage' fee or whatever they call it? Also, did they challenge your observations at all or did they just replace motherboard without question?
Click to expand...
Click to collapse
Was flashing stock rom with stock SPL, was at the shop where i bought it and they send it. I told them it stucks at bootlogo. Repair center changed motherboard without any question. Cost me nothing.
genoki said:
Also, it still gets stuck on reboot often, requiring battery to be removed for few minutes before rebooting.
Click to expand...
Click to collapse
Ja ja, same here.
genoki said:
So, guess I will send my HD2 in for RMA repair too (and wait for up to 3 weeks) and hope I get a functioning device in return.
Click to expand...
Click to collapse
Yes you will, but dont forget to flash back stock rom regarding SPL !
genoki said:
Interesting though I didn't flash my HD2 but it went from 'good' to 'bad' in similar way that your two HD2's. From reading other posts around here on XDA and elsewhere it appears that HD2 motherboards fail with surprising frequency and for variety of reasons.
Would be nice to know if HD2 motherboards are unusually delicate and something physically breaks, or if there is some electrical operation, eg charging it on USB or unusual combination of button pushes that shorts something out?
The fact that battery has to be removed for few minutes in order to get thing to reboot hints that something requires charge to dissipate eg a component somehow 'locks up' which causes crash, and needs to be discharged by removing battery?
Click to expand...
Click to collapse
I want to know as well !
hey guys. I am so glad I found this post! I have exact same issues ith my HD2, it's driving me nuts.
I kept sort of log and described my problems in this post: http://forum.xda-developers.com/showthread.php?t=712729
I think I have to send my HD2 for replacement or repair.
Can you please tell me how can I get my phone fixed/replaced?
I got the US T-Mobile version, but I don't have account in T-Mobile. Can I deal directly with HTC? Where do I have to call to get RMA number etc.
I would greatly appreciate your help!
KML
So this is quite irritating at the moment. Me and my mom both have a Sony Tablet S (SGPT111US/S). Now both mine and my mothers are causing difficulties right now, and both have very different problems. So I'll start off with my moms tablet since it may just need to be waited out for the problem to go away.
Mom's Tablet:
This was just a couple days ago, My mom says her tablet froze at 10:03 (like it really matters what the time it froze at is) on the cradle. She had to press the reset button to turn it off, however the unit will not Turn on or even go to the Android Recovery Menu to preform a factory reset. As of right now it is connected by the plug rather than being on the cradle. I'm hoping that this issue can fix itself since others have had this experience before and got theirs working just by letting it sit a couple days on the charger, however if you have any ideas on getting it working sooner that would greatly be appreciated.
My Tablet:
I honestly don't know what has happened. Until a couple days ago I turned on my tablet and after it boot up problems emerged out of random the second the lock screen appears every single app crashes, not once but continuously. Even the home screen will crash and continuously reload itself, so getting to any app won't be possible and even at that when i do get to an app it's already crashed and i'm back at the home screen. To help make matters worse, the tablet won't remove Apps permanently, i can uninstall them (oddly enough while every app crashes without them even starting the settings doesn't crash.) however if i reboot the tablet everything returns like nothing ever left. I have even went to the Android Recovery Menu to try to factory reset the device, but the factory resets doesn't even reset even though the ARM says it did. So i'm stuck with this crashing loop and a Non-Factory Resetable tablet. I have tried to see if maybe rooting the tablet could help, but not even the Tablet will load itself completely when connected to my Computer so rooting is out of the question as well. Also the Bluetooth and Wifi won't turn off as well.
In the end,
Both Tablets have the current update (4.0.3 RA5) and both are Not Rooted. They are out of warranty so last thing i want to do is call Sony to repair my tablets for a fee. I would also like to note my tablet has been sent in once for repairs because it was stuck looping the boot screen, so my tablet has had trouble in the past, but since then until now i have never had any problems. I will admit, i do sometimes install cracked apps, the app i installed just a day before all this happened was Minecraft 0.7.2.......I have installed it on my EVO and Walkman Z and no problems have occurred and they still have the game.
Please any help for these tablets will be Greatly appreciated. Please Will you help Me?
jobobishere said:
So this is quite irritating at the moment. Me and my mom both have a Sony Tablet S (SGPT111US/S). Now both mine and my mothers are causing difficulties right now, and both have very different problems. So I'll start off with my moms tablet since it may just need to be waited out for the problem to go away.
Mom's Tablet:
This was just a couple days ago, My mom says her tablet froze at 10:03 (like it really matters what the time it froze at is) on the cradle. She had to press the reset button to turn it off, however the unit will not Turn on or even go to the Android Recovery Menu to preform a factory reset. As of right now it is connected by the plug rather than being on the cradle. I'm hoping that this issue can fix itself since others have had this experience before and got theirs working just by letting it sit a couple days on the charger, however if you have any ideas on getting it working sooner that would greatly be appreciated.
My Tablet:
I honestly don't know what has happened. Until a couple days ago I turned on my tablet and after it boot up problems emerged out of random the second the lock screen appears every single app crashes, not once but continuously. Even the home screen will crash and continuously reload itself, so getting to any app won't be possible and even at that when i do get to an app it's already crashed and i'm back at the home screen. To help make matters worse, the tablet won't remove Apps permanently, i can uninstall them (oddly enough while every app crashes without them even starting the settings doesn't crash.) however if i reboot the tablet everything returns like nothing ever left. I have even went to the Android Recovery Menu to try to factory reset the device, but the factory resets doesn't even reset even though the ARM says it did. So i'm stuck with this crashing loop and a Non-Factory Resetable tablet. I have tried to see if maybe rooting the tablet could help, but not even the Tablet will load itself completely when connected to my Computer so rooting is out of the question as well. Also the Bluetooth and Wifi won't turn off as well.
In the end,
Both Tablets have the current update (4.0.3 RA5) and both are Not Rooted. They are out of warranty so last thing i want to do is call Sony to repair my tablets for a fee. I would also like to note my tablet has been sent in once for repairs because it was stuck looping the boot screen, so my tablet has had trouble in the past, but since then until now i have never had any problems. I will admit, i do sometimes install cracked apps, the app i installed just a day before all this happened was Minecraft 0.7.2.......I have installed it on my EVO and Walkman Z and no problems have occurred and they still have the game.
Please any help for these tablets will be Greatly appreciated. Please Will you help Me?
Click to expand...
Click to collapse
How's your mum's tablet doing right now? If the issue still persists after what you've tried, I'm thinking maybe just let it run out of battery, charge it back up and see what happens. Also, have you tried using the pccompanion software to redownload and reinstall a fresh firmware back onto your tab? It's a more 'thorough' reset method as opposed to a factory reset through the tab settings.
I bought an LG Mach LS860 (4.0.4 Ice Cream Sandwich) about a week ago, and I just found out about rooting. (This is my first Android.) I had no luck last night, but I tried today and I got it rooted.
Anyway... here's the problem: I was altering some settings with an app (I believe it was called Pimp My ROM.) and everything was fine. When I restarted, the battery was lower by about 7%. I figured the changes I made were the reason for this, so I went back and reverted them. However, when I restarted the phone this time, it wouldn't get past the boot screen. It would flash the Boost logo, go dark, then flash it again with an animation and a short vibrate. That's all. So I tried restoring the factory settings. (Volume down + power button, then power button and power button.) The phone went through and reverted settings, then rebooted. But THIS time, I got messages popping up like "Unfortunately, System UI has stopped." I believe there was something along the lines of "Unfortunately, Home has stopped." as well. On a layer below that at the bottom of the screen, there was another type of error. I think it had to do with voicemail. After the phone sat there for a bit as I looked online for a solution, the phone restarted again. Now it just goes to the problem from the beginning with the boot screen. My computer makes a noise indicating the USB is connected, but all my phone does is charge off it.
Any help would be much appreciated.
It's not necessarily that I'm inexperienced. I've done all sorts of flashing and things on PSP. Obviously Android is much more complex. But I know that it's not bricked unless it won't turn on at all. Because that's not a brick.
There's also very little (if any) development for this specific model. No one cares about the LG Mach because there are much more well-known phones. But I digress.
Please help. I'm extremely desperate to get this working again.
EDIT: I recently thought of another question. Would the hard reset erase all evidence of the root access? Considering I just bought the phone, I might be able to send it back. But obviously if they know I accessed the root, the warranty is void.
So I recently got my old bricked evolte replaced by Sprint. The one I was given worked fine the entire time the device was powered on. However, once turned off and back on, its screen would not work. It stayed like this for hours, until I finally started playing with it and realized it would come back on after playing with it for a little bit. I also found out that with this error the home screen pops up for a second when powering on your device, and that's exactly what I had. I read up on the error and found out it was a software error, and to reset to factory settings. So, this fixed it, I thought.
So now, after it is apparently fixed, it still does this to some extent. It will do this if the phone has been powered on for a while, and the screen won't stay off for more than like 2 or 3 minutes. Also the home screen doesn't pop up any more like it used to with the other error.
So what should I do? I was thinking of going to Sprint, but my problem is hardly reproducible. It only happens when it's been powered on for a long time, and won't do it twice in a quick succession. I feel that even if I could show them the problem, they might think they've fixed it when they haven't because it won't do it twice. I would like to root my device, but I'm afraid they're going to say that I'm the cause of the problem if I do that. If it's just a software problem though, maybe flashing a custom rom would fix the problem.
What do you guys think? What do you think is the best course of action? Any advice would be greatly appreciated. Thank you.
Never mind, I didn't know Sprint would order you a new phone if it was a minor problem like that. I thought they would only repair yours. So feel free to close this thread.
Hello:
So, the bottom line up front is I need help solving a problem with my now third, new Verizon Samsung Galaxy S4--it keeps restarting on its own, at random times, but most often after I lock the screen.
To go in more depth, if you think you may know the solution: I purchased the S4 when it first came out, some time in 2013 (not sure specifically, but it was new) and it worked just fine for 13 months (1 month past the warranty of course); this was back in August, when I got the latest Android update pushed to my phone from Verizon (4.4.2). A couple of weeks later, I would occasionally get overheating warnings that would very quickly disappear (like within a few seconds), and then the device started restarting itself... I cannot predict when it will restart, it's random, but like I said above, it usually happens most right after I lock the screen by pressing the right side button once. I started looking around on the internet for a solution then, but only found a couple of videos from earlier in 2013 where people were having battery problems (Google search has been letting me down more and more as the years pass). One day while at work, I was listening to Pandora as I always have with the phone in my front pocket, as I always have. A few hours later when I got home, not having taken the phone out of my front pocket since those last few hours at work, I went to answer a text message I had received; when I unlocked the phone, the screen was black, except for a small bit of white showing through some cracks UNDER the LCD, UNDER the screen protector, INSIDE my Otterbox Defender... the phone appeared to be working still, but the screen and touch screen did not. At that point I was pretty damn irritated and tried to find answers for a week with no luck... I called Verizon, they sent me on a goose chase to Samsung, who sent me back to Verizon, who got me in a conference call with Samsung and then left the call, and then Samsung ultimately said I would need to pay for repairs to the phone... SO... I went back to Verizon who again said I would have to talk to Samsung, but instead I just settled to giving Asurion (my phone insurance through Verizon, whom I pay an extra $9 monthly) $99 as a deductible to get a replacement S4...
Two days later I receive a brand new S4... spend hours setting it up the way I had my prior one... wasting tons of my valueable time to do so and bandwidth from my Concast ISP and the data cap they've decided to give us... one week later, the phone starts restarting itself... and this one did it more often than my prior one... EVERYTHING is up to date, minus a good amount of useless bloatware apps I never use from Samsung, like "Watch On," which I ignore... but everything necessary, I update. So, I go back to Asurion, who quickly ships me a 3rd S4...
Two days later I receive that third, brand new S4... spend hours setting it up the way I had my prior one... and now, this one is also restarting itself randomly. Interestingly, when I visited family for Thanksgiving, it restarted itself over and over and over much more frequently than when I'm at my place... at my family's place, they have very poor reception, and my phone usually has to work more to try to get the signal... IDK what the deal is, but maybe that information can be helpful to y'all.
Other things to note:
1) When I check the "RAM manager" by holding down the home button and then choosing "Task Manager", the phone is always using at least 800MB of 1.77GB of RAM... even when I choose "Clear memory" and it tells me 30 something apps have been closed... it jumps right back up to 800-900MB of usage.
2) I've tried factory resets on all three phones; with the first one where the screen cracked inside, I hooked the phone up via HDMI... within a couple of days, the restarting begins.
3) With the first replacement I received, I could not sent text messages with the default messenger app... and shortly after trying, it would restart.
4) I have used the same SIM card with all three phones since the issue began, when I first got the 4.2.2 update... I do not suspect the SIM card is the problem, but I'm also not savy with the phone... I know my way around it, but I'm not in the know.
5) I thought maybe it started because of some apps I had been trying, so I had deleted them, and the problem still persists.
6) I constantly have a Pebble Bluetooth smart watch connected to the phone... I have since I got it last Spring (2014).
7) I have never rooted the S4, overclocked it, underclocked it, or modded it in anyway because I do not know how, and I was afraid of what could happen in the future with whatever ROM I did flash onto the device if Verizon tried to push an update to it... I just don't know anything about the whole process, and I'm assuming it requires a lot of know how and babysitting of the device... I just want it to work.
8) I've replaced the battery twice; it doesn't seem to be the problem.
9) I've cleared the cache through the boot manager thing gotten to by holding a combo of buttons on the device while it's rebooting... it did not help.
Edit: 10) Today while I was listening to Pandora in the car, the audio began to skip and scratch, and then it paused for a moment, and then the phone restarted itself.
11) I forgot to mention that the reboot process itself is very fast compared to a manual restart performed by me... the phone will go black, the Samsung color rings will show a second after that, the logo appears then, the screen flashes the red Verizon logo, and then the devices is ready to be used... it's less than 10 seconds.
I've been searching around on the internet for about two months now while dealing with the problem and I can't find anything useful. Does anyone here know what my issue is and how I can fix it? Is there a way to pull error logs / information from the S4 somehow to give to someone to diagnose, like DxDiags on PC? I don't know how to read that stuff myself, but I know it can be very useful... I just don't know how to find that info inside of these very locked down ****boxes we call smartphones...
I truly appreciate any help I can get--sorry I can't offer anything in return; if I can't find a solution, I'm just going to go to my backup phone from 2011 (Droid X), and I will definitely never purchase another Samsung device, especially after they blamed me as the cause of the problem without even seeing the phone...
Thanks.
The problem is with the NG6 software build, and "probably" not with your phone. Go to Settings>About Phone> and see what Baseband Version is on your phone. If the last 3 letters are NG6, that's probably the problem. There is a new OTA update (as of 12/1).....Baseband Version ending in NK1, which corrects the rebooting problem. Either install the new update, or go back to the NC5 baseband version and that should solve your problem. Both NK1 and NC5 can be rooted if you desire.