Related
Hi everyone, I've been lurking around here unregistered since I got my first Android device last year, namely the ZTE Blade.
Now however, I'd love to get help because somehow I've managed to make my brand-new tablet not to boot, and I seek expertise from the experts.
I've searched around both Google and here on XDA, but haven't found anything because I don't know how to search for it, due to the fact that the error is in Chinese.
So to make a story short I just arrived today from a trip in HongKong.
I was very pleased with my ZTE Blade so I decided I'd buy a cheap Android-running tablet during my stay, and so I did.
I got myself an "Acho C908", which I tested in the store first. May be an unknown brand, but it's a really nice tablet.
It sure has nice specifications and I was pleased with the performance for the price I payed, however I managed to make things worse.
Everything was going good except I couldn't install any apps in Playstore, I always got the “Error Processing Purchase DF-BPA-09″. So I searched this error up and found the guide: ...technipages.com/google-play-error-processing-purchase.html
I followed the guide and cleared the data from Google Services Framework. However, after doing so things got bad. My tablet began to freeze so I restarted it. After it booted the "explorer" (forgot the name in Android, refering to Windows-term) didn't answer and crashed and the tablet froze again.
So I rebooted it again and here's where I got stuck.
The thing is that I don't seem to have bricked my tablet, because I'm able to pass the boot logo, however I'm getting stuck at something else. The worse thing is that because of the tablet being a Chinese one, the text is in Chinese! However, this happened to me at the airport when I was heading back from HongKong so I managed to ask some Chinese people.
Here's the "error".
XXX.img692.imageshack.us/img692/4594/tableth.jpg
(please replace the XXX with WWW)
From what the Chinese people I asked told me, it says something about "Password Failure" and that I would need to "Reset to Default Settings"?
I have tried to enter some sort of Factory Settings/Hard Reset mode, but holding Volume+ or Volume- or both together during turn on of the device yielded nothing but getting stuck at the first logo during start-up, namely "ACHO".
So do you have any guesses on what to do?
I actually bought two of these tablets, one for me and one for my father. So if there's any information on the working tablet you would need to help me, I would be able to provide you with that.
I'd love to get my new tablet working.
Thank you very much in advance.
Best Regards
Nikkop
acho c98
nikkop said:
Hi everyone, I've been lurking around here unregistered since I got my first Android device last year, namely the ZTE Blade.
Now however, I'd love to get help because somehow I've managed to make my brand-new tablet not to boot, and I seek expertise from the experts.
I've searched around both Google and here on XDA, but haven't found anything because I don't know how to search for it, due to the fact that the error is in Chinese.
So to make a story short I just arrived today from a trip in HongKong.
I was very pleased with my ZTE Blade so I decided I'd buy a cheap Android-running tablet during my stay, and so I did.
I got myself an "Acho C908", which I tested in the store first. May be an unknown brand, but it's a really nice tablet.
It sure has nice specifications and I was pleased with the performance for the price I payed, however I managed to make things worse.
Everything was going good except I couldn't install any apps in Playstore, I always got the “Error Processing Purchase DF-BPA-09″. So I searched this error up and found the guide: ...technipages.com/google-play-error-processing-purchase.html
I followed the guide and cleared the data from Google Services Framework. However, after doing so things got bad. My tablet began to freeze so I restarted it. After it booted the "explorer" (forgot the name in Android, refering to Windows-term) didn't answer and crashed and the tablet froze again.
So I rebooted it again and here's where I got stuck.
The thing is that I don't seem to have bricked my tablet, because I'm able to pass the boot logo, however I'm getting stuck at something else. The worse thing is that because of the tablet being a Chinese one, the text is in Chinese! However, this happened to me at the airport when I was heading back from HongKong so I managed to ask some Chinese people.
Here's the "error".
XXX.img692.imageshack.us/img692/4594/tableth.jpg
(please replace the XXX with WWW)
From what the Chinese people I asked told me, it says something about "Password Failure" and that I would need to "Reset to Default Settings"?
I have tried to enter some sort of Factory Settings/Hard Reset mode, but holding Volume+ or Volume- or both together during turn on of the device yielded nothing but getting stuck at the first logo during start-up, namely "ACHO".
So do you have any guesses on what to do?
I actually bought two of these tablets, one for me and one for my father. So if there's any information on the working tablet you would need to help me, I would be able to provide you with that.
I'd love to get my new tablet working.
Thank you very much in advance.
Best Regards
Nikkop
Click to expand...
Click to collapse
try to download the new firmware here:
http://www.acho.com/downc.asp?ID=3476
put it in sd card
boot the tablet in recovery mode (vol- and on)
launch "update frome external card
reboot
I don' remember al the steps: please read the istruction on achos site too, at the same link above
bye
Hi all,
My Galaxy S II keeps crashing. The phone will just power off and the battery will drain right out and the only way to turn it back on is take the battery out then charge it again. Sometimes if I am quick and realised it has crashed I can take the battery out and turn it back on and the battery will have drained 30% in an hour.
Does anybody know why the phone might do this or is there a way I can track whether something in particular is crashing the phone via a log or something like that?
Thanks
Yes there are apps that can do that.
So whats the score.......are you on latest o2 or latest unbranded.
Post the about phone details lol.
Hi,
It is on the latest H3G UK firmware and is unlocked via the Galaxy S Unlock app by Helroz (so via nv_data.bin)
4.0.4
I91000NELP4
Build: IMM76D.XWLPY
Any ideas and what is the app called?
Thanks
Hello,
Just thought I would take this opportunity to join this thread since I have been suffering from a very similar (if not identical) problem on my S2 too. It's quite lengthy, apologise for that - hope to give as clear a picture as possible:
- S2 originally from vodafone contract, am now with giffgaff
- 1 year and 6 months old
- not rooted, have always used Samsung official firmware
- updated to ICS 4.0.4 about a month ago(?)
- Kernel version 3.0.15-1056084, build number: IMM76D.BULPG
I must say I can't be certain if the random crashes started (it would sometimes heat up really hot, or sometimes not warmed up at all), phone will just turn off. Can't turn back on without taking battery out and re-inserting.
Similarly, the battery level will drop by 30+% once the battery is re-inserted.
Have experienced once where it started up in "safe mode" and although everything was still there, the apps I have put in folders were all listed cos the folders were gone. Restarted and it wasn't in safe mode anymore, but had to create new folders and sort my apps again.
The random turn offs can happen every few days, or twice a day. Don't know why it happens.
I haven't installed many new apps (some are by japanese developers but worked fine before and after I updated firmware), asked at a Vodafone store and they suggested it could be a battery problem. (offered to send it off for repair, but will take 7-10days and factory reset, which I want to avoid...)
So bought and changed a new battery (from Samsung website) which looked good (no random shut downs for a week) but it all started again last night. So it's not the battery.
Suspected it's most probably software problems.
After upgrading to 4.0.4 firmware, the phone cannot display phone serial number/network etc etc under the "legal information" in settings.
The battery log seems funny too, I would re-insert battery and restart, the battery log will still show it's been on battery for 20+hours.
I've also spotted that there're 2 OS running when looking at the battery log - when I upgraded from gingerbread to ICS, I did not do a factory reset (is that absolutely necessary?) but phone has been working perfectly for a few months after the upgrade so I thought nothing of it....
I wanted to post a screenshot but not allowed cos I'm new to forum... =(
Is it because there're 2 OS so it's clashing...?
Since I haven't rooted, I'm not sure what I can do - last resort is to wait until JellyBean rolls out from Samsung and factory reset when I upgrade?!
Hope I've given enough info to get help easier.
PS: Kies is testing my temper. Tried to solve the "this device is not supported by KIES" problem by reinstalling whilst not connected to internet, kind of worked, allowed me to backup small files (such as call logs) but when it comes to big bits e.g. photos, it will show the "unexpected error" message again.....
also got "wssyncmlnps has stopped" on my phone...
ARGH!!! just wana backup my stuff before it completely turns into a brick!
zetsuboumeow said:
Hello,
Just thought I would take this opportunity to join this thread since I have been suffering from a very similar (if not identical) problem on my S2 too. It's quite lengthy, apologise for that - hope to give as clear a picture as possible:
- S2 originally from vodafone contract, am now with giffgaff
- 1 year and 6 months old
- not rooted, have always used Samsung official firmware
- updated to ICS 4.0.4 about a month ago(?)
- Kernel version 3.0.15-1056084, build number: IMM76D.BULPG
I must say I can't be certain if the random crashes started (it would sometimes heat up really hot, or sometimes not warmed up at all), phone will just turn off. Can't turn back on without taking battery out and re-inserting.
Similarly, the battery level will drop by 30+% once the battery is re-inserted.
Glad to know it is not just me. I'm hoping I can get an app that will log what is going on right up until crash time!
Have experienced once where it started up in "safe mode" and although everything was still there, the apps I have put in folders were all listed cos the folders were gone. Restarted and it wasn't in safe mode anymore, but had to create new folders and sort my apps again.
The random turn offs can happen every few days, or twice a day. Don't know why it happens.
I haven't installed many new apps (some are by japanese developers but worked fine before and after I updated firmware), asked at a Vodafone store and they suggested it could be a battery problem. (offered to send it off for repair, but will take 7-10days and factory reset, which I want to avoid...)
So bought and changed a new battery (from Samsung website) which looked good (no random shut downs for a week) but it all started again last night. So it's not the battery.
Suspected it's most probably software problems.
After upgrading to 4.0.4 firmware, the phone cannot display phone serial number/network etc etc under the "legal information" in settings.
The battery log seems funny too, I would re-insert battery and restart, the battery log will still show it's been on battery for 20+hours.
I've also spotted that there're 2 OS running when looking at the battery log - when I upgraded from gingerbread to ICS, I did not do a factory reset (is that absolutely necessary?) but phone has been working perfectly for a few months after the upgrade so I thought nothing of it....
I wanted to post a screenshot but not allowed cos I'm new to forum... =(
Is it because there're 2 OS so it's clashing...?
Since I haven't rooted, I'm not sure what I can do - last resort is to wait until JellyBean rolls out from Samsung and factory reset when I upgrade?!
Hope I've given enough info to get help easier.
PS: Kies is testing my temper. Tried to solve the "this device is not supported by KIES" problem by reinstalling whilst not connected to internet, kind of worked, allowed me to backup small files (such as call logs) but when it comes to big bits e.g. photos, it will show the "unexpected error" message again.....
also got "wssyncmlnps has stopped" on my phone...
ARGH!!! just wana backup my stuff before it completely turns into a brick!
Click to expand...
Click to collapse
So glad it is not just me. I'm hoping I can use an app to log what is going on when crash time happens. Can someone tell me what the app is called please?
Rackers said:
So glad it is not just me. I'm hoping I can use an app to log what is going on when crash time happens. Can someone tell me what the app is called please?
Click to expand...
Click to collapse
Me too facing above all,unfortunately riding in same boat.
Hey, guys, I know there are a lot of these issues with a lot, if not all, of the HTC smartphones, but I've only seen a few of these for the HTC Radar, and they all seem to give the same answers. Hopefully my explanation of the problem will help!
So, I got the phone thanksgiving weekend 2011, so I've had it for about a year. One day around the beginning of April this year, my phone randomly began a restarting loop, where it would gradually restart itself from a blank white screen over and over, then it went to the HTC screen over and over, and then periodically switched between the HTC screen and the black "Windows Phone" load screen over and over again. I tried taking off the battery cover and leaving it for a couple of minutes and then hours, but I put it back and it just kept rebooting. I was left without a phone for about two days.
On the second day, I put it on the charger and left it in my dorm while I was in class all day, and when I came back, it was rebooting still, but I noticed that it always made it to the "Windows Phone" logo loading screen and then restarted. After about 4 reboots, it went back to normal and I was able to use the phone. After the next couple of months, it stopped doing it in such a long period of time, but the battery usage went up almost 30-40% than what it used to be. Once in a while, it would reboot once, but then it would be back to normal.
This time, in late October, it started the reboot thing again, but this time, only going up to the HTC screen and looping that. I tried taking the battery cover off again and leaving it for hours, but same problem now. So I decided to leave it off for a day. By this time, I had my HTC Desire HD as backup, but it was unlocked, and at the time when I bought it, I didn't know anything about HSDPA numbers, so I could use my T-Mobile SIM, but no mobile network, since it's a Telus/AT&T phone.
I tried charging it, but this time, it lasted for a whole week. After rebooting over and over, it would last 3 hours, then stop because the battery would die out. So I just left it, and left it, and weeks went by, and my warranty had long since expired, so I couldn't go to HTC about this. I even called them to see what I could do, and they told me to do a Factory Reset, well... here is a list of the things I tried:
- IMAGE CRC: At first I didn't know what this was, and so I looked it up. After finding out what it was, I tried it, and I got two numbers: BL CRC-0xD19F79E1 and OS CRC-0x4CC706B. I looked those up on the internet and got nothing. I restarted the phone, and nothing happened at all. (If there was something else I was supposed to do here, please tell me!)
- Factory Reset: This was the LAST thing I wanted to do, but I had no choice and I tried it, hoping the error would be fixed. So I scrolled down to it, everything seemed to be normal, it gave me a warning, and I clicked it ... I was very suspicious of this, because as soon as I clicked "Factory Reset", it said "Reset complete. Press Volume Down to restart". I mean IMMEDIATELY after. Now, I KNOW that Factory Resets take much longer than an instant to actually have happened. But I restarted anyway. ... Nothing, still. I tried it several times after that, only to get the same result.
Those are the two options I tried, besides looking on the internet... if I can avoid buying a new Radar, I would like to, at all costs, because the next time I have a decent amount of money, I would like to save it for something else. Is there anything else I could try to resolve this issue, or at least gain more information on the problem?
Thank you all very much for reading my post!
BladedYouth said:
Hey, guys, I know there are a lot of these issues with a lot, if not all, of the HTC smartphones, but I've only seen a few of these for the HTC Radar, and they all seem to give the same answers. Hopefully my explanation of the problem will help!
So, I got the phone thanksgiving weekend 2011, so I've had it for about a year. One day around the beginning of April this year, my phone randomly began a restarting loop, where it would gradually restart itself from a blank white screen over and over, then it went to the HTC screen over and over, and then periodically switched between the HTC screen and the black "Windows Phone" load screen over and over again. I tried taking off the battery cover and leaving it for a couple of minutes and then hours, but I put it back and it just kept rebooting. I was left without a phone for about two days.
On the second day, I put it on the charger and left it in my dorm while I was in class all day, and when I came back, it was rebooting still, but I noticed that it always made it to the "Windows Phone" logo loading screen and then restarted. After about 4 reboots, it went back to normal and I was able to use the phone. After the next couple of months, it stopped doing it in such a long period of time, but the battery usage went up almost 30-40% than what it used to be. Once in a while, it would reboot once, but then it would be back to normal.
This time, in late October, it started the reboot thing again, but this time, only going up to the HTC screen and looping that. I tried taking the battery cover off again and leaving it for hours, but same problem now. So I decided to leave it off for a day. By this time, I had my HTC Desire HD as backup, but it was unlocked, and at the time when I bought it, I didn't know anything about HSDPA numbers, so I could use my T-Mobile SIM, but no mobile network, since it's a Telus/AT&T phone.
I tried charging it, but this time, it lasted for a whole week. After rebooting over and over, it would last 3 hours, then stop because the battery would die out. So I just left it, and left it, and weeks went by, and my warranty had long since expired, so I couldn't go to HTC about this. I even called them to see what I could do, and they told me to do a Factory Reset, well... here is a list of the things I tried:
- IMAGE CRC: At first I didn't know what this was, and so I looked it up. After finding out what it was, I tried it, and I got two numbers: BL CRC-0xD19F79E1 and OS CRC-0x4CC706B. I looked those up on the internet and got nothing. I restarted the phone, and nothing happened at all. (If there was something else I was supposed to do here, please tell me!)
- Factory Reset: This was the LAST thing I wanted to do, but I had no choice and I tried it, hoping the error would be fixed. So I scrolled down to it, everything seemed to be normal, it gave me a warning, and I clicked it ... I was very suspicious of this, because as soon as I clicked "Factory Reset", it said "Reset complete. Press Volume Down to restart". I mean IMMEDIATELY after. Now, I KNOW that Factory Resets take much longer than an instant to actually have happened. But I restarted anyway. ... Nothing, still. I tried it several times after that, only to get the same result.
Those are the two options I tried, besides looking on the internet... if I can avoid buying a new Radar, I would like to, at all costs, because the next time I have a decent amount of money, I would like to save it for something else. Is there anything else I could try to resolve this issue, or at least gain more information on the problem?
Thank you all very much for reading my post!
Click to expand...
Click to collapse
May be it is a Hardware problem. Why you don't try to put HSPL and to cook custom rom ? I do this on mine few days ago and now the phone is more useful than before. I cooked HD2O ROM and till now working fine for me. When you change bootloader with HSPL may be it will work out if it is a Software problem. Also you need to change Radio Firmware other wise the device can not boot. When I am doing HSPL a few times phone just loop restarts and not start but after I do everything like it was in treads here and flash new radio the phone is working fine now. But may be there is a Hardware problem.
Tonyco1 said:
May be it is a Hardware problem. Why you don't try to put HSPL and to cook custom rom ? I do this on mine few days ago and now the phone is more useful than before. I cooked HD2O ROM and till now working fine for me. When you change bootloader with HSPL may be it will work out if it is a Software problem. Also you need to change Radio Firmware other wise the device can not boot. When I am doing HSPL a few times phone just loop restarts and not start but after I do everything like it was in treads here and flash new radio the phone is working fine now. But may be there is a Hardware problem.
Click to expand...
Click to collapse
Thank you very much for responding! So just to be clear, how exactly do I go about flashing a ROM on the Radar, and a new radio? On Android phones, its much easier to root the device or simply place the ROM folder in there and make it work. I have no experience with doing this to a Radar, as I was previously led to believe that this was impossible. Should I just browse this forum?
BladedYouth said:
Thank you very much for responding! So just to be clear, how exactly do I go about flashing a ROM on the Radar, and a new radio? On Android phones, its much easier to root the device or simply place the ROM folder in there and make it work. I have no experience with doing this to a Radar, as I was previously led to believe that this was impossible. Should I just browse this forum?
Click to expand...
Click to collapse
Yes just browse this forum but only section about Windows Phone 7 Development and Hacking. You will find DFT exclamation of how to install HSPL. In mine it was very easy because I not receive Country ID fail my phone was buy in Europe. If you receive Country ID error you need to proceed with goldcard it is explained there but first proceed without goldcard if it work it is very easy. Also when you proceed SPL2.05 it is not clear in the topic but you need to be in bootloader so you should start your phone with VolUp and VolDn keys pushed this is not explained in the topic and I waist a lot of time till figured out. After that just download one of the 7.8 ROMs here in Radar section and write it down. Also download new radio and use some RUU to put it on the phone before the ROM other wise the phone can not boot. Try and after that if you have problems write down here.
MY RADAR TURNED BACK ON! I don't know exactly what happened, but after a couple of reboots, the battery indicator flashed and then it rebooted twice until finally turning on the full amount.
Tonyco1 -- Thank you very much for staying with me and replying to my request! Although what you suggested is not needed for my booting issue, I'm going to try it anyway to see if I can actually boot 7.8! Thank you again.
BladedYouth said:
MY RADAR TURNED BACK ON! I don't know exactly what happened, but after a couple of reboots, the battery indicator flashed and then it rebooted twice until finally turning on the full amount.
Tonyco1 -- Thank you very much for staying with me and replying to my request! Although what you suggested is not needed for my booting issue, I'm going to try it anyway to see if I can actually boot 7.8! Thank you again.
Click to expand...
Click to collapse
OK but you need to but some custom ROM my phone turn back on when I put custom ROM a lot of features and works really good.
First off, I'd like to say my S2 is the Virgin Mobile version (model i9210) so I'm not sure if it's okay for me to post this in this forum or not. Feel free to move it where it should be, I won't be offended.
Edit: Originally had posted this in the Samsung Galaxy S2 forum, but it was nicely moved to this forum in hopes that it would be seen more~ So to clarify, my phone is the Virgin Mobile Samsung Galaxy S2, running Android 4.1.2, model number SPH-D710.
The ROM I have is BiftorROM-V8-JB-XWLSN-NoWipe.
Onward. This is my first Samsung phone AND my first Galaxy, and when I decided to root my phone, I had no idea how much different it would be from my past phones. How I didn't completely brick this phone, is nothing short of a miracle. I had trouble with some ROMs so someone eventually linked me to a Sprint stock ROM, saying it was compatible with my phone.
Since then I've been using that ROM, despite having a Virgin Mobile phone, with no problem. Recently I noticed an app I use (SD Maid) was listing my phone as unrooted. It was weird but I ignored it, because the app still worked. Even later, I noticed other apps that require root access were not working correctly, so I decided to download a root checker.
Status: Unrooted
Well, then. I'm not sure how this happened, or what's going on, but I figured again, it was no big deal because my ROM was running perfectly and I had no desire to change my ROM or anything else soon. Last night my phone started acting completely different. Lagging like crazy, and when I tried to unlock my phone, it would take a good 15 seconds just for the screen to turn on and my lock screen to start functioning normally. Then another 20 seconds or so for the screen to register my touch and actually unlock my phone. I tried disabling all lockers, but my screen would just turn black and I would still have to wait.
A friend suggested that I simply go through the process of rooting as though my phone really were unrooted and just hope that fixes it, but I'm not sure if that would be a good idea. If my phone wasn't operating so slowly this wouldn't be as big of a problem, but it is, and I'm pretty afraid that I'll mess my phone up somehow.
I once found a forum with the topic the same as mine but I haven't been able to find it since, so I'm hoping someone here could point me in the right direction. Do I go through the root process, maybe try just reflashing my current ROM? I've also thought about just doing a system restore on my phone and see if that helps. Thanks in advance.
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.