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.
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
Yesterday my battery died half way through playing a game (not entirely unexpected, I'd been playing on my phone quite a bit that day and it still lasted 22-23 hours), I connected the charger that came with the phone and left it to charge while I got on with some uni work.
The phone vibrated to tell me the charge was complete so I disconnected the charger and turned the phone on as usual. After the samsung galaxy S2 splash screen, the screen lock appears and when I move it there are several error messages saying that various applications have had to stop (the main one seems to be TwLauncher but when I force close it, many others also force close). This continues for several seconds until the phone decides to restart itself and repeats the process ad infinitum until I can shut down the phone (I can manage this by not trying to get rid of the screen lock and just holding the power button until the menu appears).
I've had this phone a week (one of those days being today where it did not work at all) so it's still well within the return period but I was wondering if there is an obvious fix that I'm missing.
If not, I'll be ringing Samsung on Monday (I have coursework due for friday so I'll be devoting my samsung office hours time to that) and if they can't give me an easy fix I'll be ringing the place I bought it from and asking for an exchange.
So, has anyone else had similar issues and managed a simple fix?
Bump, I take it everyone else's phone is working then?
Giving this another bump in the hopes there's someone with a simple solution.
I don't want to have send my phone off and wait for the place to get stock.
there have been 2 firmware releases from samsung in the last couple of days, i assume you are running the latest firmware?
I can't even get the phone to stay on long enough for Kies to recognise it. It keeps restarting. Even when it was working I couldn't get Kies to work with it properly (I couldn't copy the contacts from the phone to the computer).
It's running the firmware it came with, but I can't check which version it is.
I was going to try flashing the new firmware via ODIN but I've been busy with coursework. Is this likely to solve the issue or will I just be giving the retailers ammo to reject my return?
go into recovery and do a factory reset
psp888 said:
go into recovery and do a factory reset
Click to expand...
Click to collapse
this is what I was looking for.
after googling, this sorted it out.
I just assumed download mode was the only other non-normal mode.
Thanks
Basic FAQs on the SGS1 forum mostly apply to SGS2 .Worth a look there before Google .
jje
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.
So I've had this problem for at the very least about a year now. If I think back, it's been going on for a lot longer than that.
It started off with my Galaxy S8 on ATT. It was subtle at first and I just presumed them to be glitches. Webpages would open by themselves. The back button would randomly go off at times. Things would "click" themselves. It wasnt as prominent as it is now so I just assumed it to be weird errors.
So around April of 2019 the glitches got so bad that I thought my phone was being hacked and I needed to get my own plan so I upgraded to an S10 on the T-Mobile network.
Things started off slow, but the same kind of problems kept happening. It just got a lot creepier because webpages started to open by themselves had significance to what was going on in my life. Like I had been fighting with my GF and a PsychologyToday article about narcissism opened on my phone which was beyond reaching distance.
I still had my S8 and used it at home to simply surf the web and such. There was a point where I thought I was going to end up in someone hacking my account and exposing stupidly taken nudes. Because I had my new S10 and was scared, I ripped the back of the S8 off and ripped the battery out.
This is where I believe I discovered one of the primary problems. Now the S8 might take a 15 second charge if I plug it into the wall, but it had enough juice to start up and when it accessed the PlayStore it showed up as two unique devices.
The PlayStore had two Galaxy S8's with just slightly different names accessing my account on the same day. I've almost always felt like I was guest on my phones while someone else was the administrator. My Note10+ had a similar issue which I will get to later.
So my S8 is toast now because the battery isn't removable on the fly. So I'm using the S10 now and the same problems keep happening. Things clicking themselves, webpages opening, as I'm typing something will hit space midword, and the creepy feeling of an omnipresent watcher.
I realized my S10's dictionary of used words was just kind of off. Words I wouldn't use started to show up in my autopredictions. One day perplexed by what was showing up, I just began hitting the center word. The sentence that popped up was something like "I really enjoyed the video of the 15 year old girl". Special note, my phone is beginning to lag terribly the farther I get into this. So freaked out by that 15 year old girl sentence I erased it, but curious repeated the process again. It turned into what looked like a suicide letter. I didnt know what to make of it, but thought I might get killed and set up to look like a pedophile/suicide case.
This is when I turned off it's network access and began using a low end prepaid Android. I actually went through two. At this point everything I touched techwise began to malfunction. For some reason my FiOS didn't want to work so I bought a hotspot pass from Xfinity. Long story short, this phone apparently used 300 GB of data in one week. The phone itself registered 30 GB for two months. The S10 I had bricked apparently had the capability to send cellular data stil as well. It wasn't a ton, but there shouldnt have been any. When I questioned T-Mobile they couldnt give me a straight answer.
So at this point I have a Galaxy S8 showing up as two devices, an S10 that should be off, and another phone that had 270 GB of data go missing. I tried calling Xfinity about the data, but couldn't get through. I tried my T-Mobile line, my father's Verizon line, a third party app combined a VPN, and even walked to a local firehouse around midnight. My grandmother's home phone line with Comcast even died while I tried to get though.
I tried a cheap trac phone, but the camera on that would turn off and on by itself. I'm not an apple fan but tried an iPhone 6S on the trac as well. Still had the same unnerving issues. I didnt trust the S10 so I hoped a clean start with new number on a new network would help so I got my grandmother to get me a Note10+ on her Verizon account.
This phone has acted the same way as the others and has had the same weird issues. Showing up as two devices? In Members I had two Note10's. The first was named something like "Verizon Note10+ 256 GB". It looked official but when selected under serial number it had my IMEI number. Now the second Note10 was named, generically, "Samsung Device". But when this was selected next to serial number was the correct one.
I questioned Samsung help about this, even asking which one to remove but couldnt get a straight answer from the rep. It was so vague and confusing I even gave the guy option a or b, and got nothing.
I was tinkering around with an app called 3C toolbox and at one point I believe my phone was running five simultaneous Android OS. When looking at an IP log I had taken, I took a few pictures from my laptops computer screen. I had the phone's wifi off, bluetooth off, mobile data off, and in airplane mode. I have no idea how it happened, but I guess my phone picked up a rogue connection somehow and the pictures began erasing themselves.
I cant be certain of what's going on but whoever has access is able to go into my accounts via my phone. Going back to the S8, I tried purchasing a recovery software because I thought looking into the innards of my phone might give me some insight. The email with the verification code was snoozed on me, and the only device logged into my gmail was my S8. There was no notification of a sign in attempt, so I presume it was snoozed through my device.
My tech in general has gone to hell this year. When the S8 was acting funny I was doing research on my very old laptop. The network driver uninstalled itself. This is when I bought a chromebook. The operating system corrupted within a week. For some reason I thought iOS might help so I bought an iPad. When I connected it to my home network during setup the pin changed bricking it. So I bought another chromebook, and decided to update and set it up in the Target I purchased it at. There was already an owner to the device. Things had been so wrong for so long I simply kept it. I bought another laptop which works ok, but you can tell something's off.
The most frustrating purchase beyond the Galaxy's was a Macbook Air. After trying to get iPad that bricked itself fixed, but couldnt I bought the Air on the spot with Apple Care. I sent logs and videos to Apple and was told it'd take a week. Two and half months later, questions unanswered, blatant videos, I was told nothing was wrong with it. The thing turned itself on just last month and I only know that because my router showed that it had connected.
At this point I've tried Bitdefender, Lookout, Malewarebytes, McAfee, Kaspersky, and probably a few others. In terms of VPNS I've tried a few. But going back to when my keyboards dictionary changed about liking underage girls and what seems to be the ability for someone to access my accounts and use them as their own I'm somewhat afraid of hiding myself. I wish there was the opposite, no logs, I want super logs.
But back to the main point. I've had three high end galaxy devices all with this same issue. I'm not sure who it is, but by power of deduction, Iwould guess the government. I mostly say that because of when I tried to save the data from Xfinity and five different forms of communication couldnt get through. From another standpoint the issue is larger than just my creepy stalking feelings because this could be hypothetically dormant on a massive amount of phones leaving bank accounts, social security numbers, really important information available for prying eyes. I wouldn't of realized until things got strangely personal.
The closest thing I found was Pegasus. I say that because I had friends phones who began to malfunction in the same way as mine and the only thing linking us were phone calls.
My bet is its a day one exploit. When my phone starts up it looks like it's skipping critical android functions. Story sounds crazy, but I've tried every OS and Network. Others have been having similar problems as well. Read the reviews for this ip address on whatsmyip 2607:fb90:5c3c:6fac::41:f20e:701. This IP broke into my Facebook silently and the only reason I found it was through downloading an archive of my facebook. And the only reason I did that was because it was like I was led there as things quickly highlighted themselves just long enough to catch a glimpse.
I tried ignoring it. But it's really hard to do. what got me today was my volume buttons decided to stop working. The down button works though because I can still take a screenshot. Of those I have many, I have the whole story documented because even I think it sounds ludicrous at points.
Hopefully when I send it to Samsung they can actually diagnose the problem.
I cant verify but half the time I talk to reps on the phone or through chats they dont work for the respective companies. A story for another time, but let's just say I just signed up for Hulu and when I asked why 24 devices were signed into my account they said it was a normal glitch. Understandable enough, but some had distinct names lik Andy's iPhone.
TL;DR - all my stuffs hacked, third party user controls device thinking it's you, possible key logging / video jacking meaning cell phone users passwords are highly susceptible
Hi all,
Received my 1 iii yesterday, spent several hours setting it up, tweaking, testing, transferring files--and love it. Been an LG V-series user for the last six years, but with LG bowing out and having moved toward radiused corners, rounded glass, notches, etc. anyway--I'm very glad Sony is still out there making sane, non-compromised phones with basic features like microSD, no hole punch, and headphone jacks that are now treated as "niche" or "enthusiast".
BUT, unfortunately, having a very odd problem, and can't find any examples of anyone else having the issue... but it basically makes the phone unusable.
Literally any time the screen turns off--whether via pressing the power button, or via an inactiivty screen time out--the phone either shuts down, or restarts.
I've done a factory reset several times, tested it with fully restored apps/settings/personal data/etc., and totally un-restored, makes no difference--the issue always happens. So it's not the fault of any setting I altered, app I installed or disabled, etc.
I remember the first time I booted up the phone--but none of the factory reset times since then--that it said something about some setting being on to prevent battery wear from the phone being accidentally turned on during shipping. So maybe there's some bizarre setting somewhere that auto-shuts-down the phone when the screen turns off? Otherwise I'm at a total loss...
Thanks in advance for any help!!
Here is one of two reviews from Amazon about this phone:
"Got in the infinity reboot issue right out of the box...a $1200+ phone, very disappointed .
Got it today on the release. Then start setup and update. Not even until all set up finished, it restarted first time. Then again in just about 15mins. Overall been through restart 12 times. Try hard reset and all other methods, not helping. Return....."
So, unless you are the one who left this review...you are not alone! This type of stuff makes me so disappointed!
Sounds like the reviewer on Amazon was having a different problem. Mine stays on perfectly fine as long as one is interacting with it--only shuts down/restarts if the screen turns off.
Given the variety of software states in which the problem occurs--vlank setup, full set-up, safe mode--seems like a rare hardware issue. As long as it can be replaced with a correctly functioning unit quickly, it's still the phone I want...
If not, I guess I ride out my LG V50 till it dies, and then quit using smart phones...
Having to ship it in for warranty repair. Seems like almost certainly a hardware problem--sounds like I "won" the lemon lottery. A bummer, but not an indictment of the phone generally.
But I'm still really digging the phone--when it works. Did a video A/B with my LG V50, and while it didn't strike me as miles better--it definitely was when full-screen. Not having to look at rounded corners and a notch is worth a lot to me. With font and display set to smallest settings, *love* the look and roominess of the screen.
I agree with not wanting notches, or punch holes...this is why I am interested in this phone...PLUS I truly miss having a notification LED. However, so far the reviews from end users/owners...not the "pro" reviewers on YouTube..is leaning towards the negative! My last three phones have been from OnePlus. Currently on the 8T. I know many have started to slam OnePlus for their practice of late patches and higher prices...but I have not had even ONE problem with any of the OnePlus phones I've had! They just work. I've had the 6, 7-Pro, and now the 8T. There's nothing out there that even interests me any longer that doesn't overheat, or freeze, or have unnecessary dedicated assistant buttons??? Disgusted with them all. I just might have to take a harder look at Apple!!!!
Outside of what appears to be a truly random and uncommon hardware issue that's affecting mine per this thread--I actually really loved the 1 mk iii so far.
I haven't had overheating issues, camera seemed excellent, loved the hardware build quality, *LOVE* having a proper screen again (including no notches, aspect ratio, and tons of room w/ fonts and appearance set to smallest). I will never buy a phone that doesn't have microSD support, and access on this phone is awesome (no tool needed).
I wouldn't be too quick to write it off--especially not for the likes of Apple, who provide a hugely compromised, feature-removing, closed-ecosystem product at an inflated price for what you get.
Keep in mind--it's the internet, so you're going to far disproportionatly have people needing to discuss problems. Folks for whom nothing goes wrong--for any product--won't tend to seek out places like this to say so. So I wouldn't let a really small sample of issues unduly color your view...
Hi I have the exact same issue. Received mine on the 24th and transferred everything over from Oppo find X2 pro. Thought it was me at first when trying to wake but it rebooted. All fine until used in car QI base. After 20 minute drive picked it up and tried to wake only for the same thing to happen. Did this several times yesterday and this morning both on and off charge and while cool to touch. Very disappointing as expected more for something that cost nearly £1200! Like the phone a lot and prefer it over the Oppo but cannot find a way around this. A new 256k micro SD card also being used so have tried without this, without the EE sim and factory reset but still it happens. It's unusable as is so will have to be replaced, unless any suggestions?
Have had a few good Android phones from Huawei P20 pro, Mate 20X to current Oppo in recent times but never had an issue like this.
Having to swap back to the Oppo is very time consuming and exasperating!
Shame as this is a stunningly good phone.
Mikehbw said:
Hi I have the exact same issue. Received mine on the 24th and transferred everything over from Oppo find X2 pro. Thought it was me at first when trying to wake but it rebooted. All fine until used in car QI base. After 20 minute drive picked it up and tried to wake only for the same thing to happen. Did this several times yesterday and this morning both on and off charge and while cool to touch. Very disappointing as expected more for something that cost nearly £1200! Like the phone a lot and prefer it over the Oppo but cannot find a way around this. A new 256k micro SD card also being used so have tried without this, without the EE sim and factory reset but still it happens. It's unusable as is so will have to be replaced, unless any suggestions?
Have had a few good Android phones from Huawei P20 pro, Mate 20X to current Oppo in recent times but never had an issue like this.
Having to swap back to the Oppo is very time consuming and exasperating!
Shame as this is a stunningly good phone.
Click to expand...
Click to collapse
Forgot to say there are others on here with similar issue, under random reboot thread.
After sending in for "repair" and receiving it back with no improvement (but "repaired"), Sony has finally agreed I'm due a replacement unit. Have shipped my first unit off, due to arrive to them next Wednesday. Will hopefully receive a properly-functioning replacement soon thereafter... Agree that, if the phone didn't have this bizarre issue, it would be great--very close to what I want in a phone (versus the myriad options out there that don't offer what I want, and insist on absurd design choices I detest).
So, we'll see. Certainly frustrating to have an issue like this on a phone that costs more than plenty of computers...
(To be clear, I had the issue literally every time, from the beginning, regardless of what I had/hadn't set up, installed, sim card/no sim card, micro SD/no micro SD, etc.).
I have Xperia™1 III but the phone is really stable for me, no random reboot. I have only heating issue. Xperia™ XZ2 Premium hasn't heat like this phone. My phone is Hong Kong device
Most likely not what caused your issue...but...it is NOT a good idea to allow any backup to install all your previous apps from an "old" phone to a new one. I know it can be a major pain and very time consuming to install everything from scratch when setting up a new phone...however...when you allow a backup to flow freely onto a new phone you are allowing all the junk to come back also! It's up to you, but I always install everything from scratch and it may not be related but...I have owned many, many phones and NEVER had all the problems that so many have all across the board. Am I just lucky, or is it because I have so much experience with computers and know how to set things up properly? YMMV
jaseman said:
Most likely not what caused your issue...but...it is NOT a good idea to allow any backup to install all your previous apps from an "old" phone to a new one. I know it can be a major pain and very time consuming to install everything from scratch when setting up a new phone...however...when you allow a backup to flow freely onto a new phone you are allowing all the junk to come back also! It's up to you, but I always install everything from scratch and it may not be related but...I have owned many, many phones and NEVER had all the problems that so many have all across the board. Am I just lucky, or is it because I have so much experience with computers and know how to set things up properly? YMMV
Click to expand...
Click to collapse
I think you have been lucky
Like you I have never had a problem and been in IT since the early 80's but this isn't something that's has been moved over. Sadly, the phone behaves the same wether out of the box or fully migrated. In the PC world I saw something similar with overheating and poorly cooled AMD processors in the 90's and am wondering if this is a heat related component batch issue?
Sony need to get a grip on this sharpish or they will be looking at refunds, which is never good.
The reboots are caused by the fingerprint reader. My new phone would bootloop while fast charging if my one and only configuration after a factory reset was setting a fingerprint.
DO NOT SEND IT IN FOR A WARRANTY REPAIR - - IT WILL GET WORSE
Get a refund.
First, Sony sent it to SBE with FedEx Ground, which currently takes about 2 weeks.
Second, SBE returned it bricked and voided my warranty. They said I flashed it but I had sent it in new and unmodified. I didn't even think they returned my own phone back because it had a UK/EU label and destroyed firmware. Sony Support would no longer help me because I was no longer a customer. SBE insisted I was a firmware flasher that deserved nothing. I ran EMMA and it showed my phone IMEI, locked bootloader, and stock firmware.
I finally found somebody on Sony Support who would give me an RMA. Maybe it was their mistake, but I wasted no time shipping it back. I'm doing a credit card charge reversal if I get any more crap from Sony/SBE.
I have spoken to Sony UK tech support and they have confirmed there is a reboot issue with some1iii's. Apparently, second line technical support have identified the issue (software) and there will be a revision released to cure this. When pressed, they couldn't give me a date for this and were a little vague. I was advised to return to my supplier for a refund.
Not good on a phone costing £1200 and surprised they haven't got their act together more quickly. They seem to be struggling getting phones shipped presently and my supplier has confirmed a 14 day wait if I want to re-order. I don't know if this is just poor advanced planning by Sony UK or if this is a Sony global problem trying to get hold of the components for manufacture.
Despite all the issues, this phone still ticks all the boxes for me so have decided to wait for the dust to settle!
Good to know there's some awareness now on Sony's part of this issue, and a plan yo resolve it via software (?). If the second unit I get has the same issue, I guess I'll wait a bit for that aoftware resolution--but deeply hoping I won't have the issue again.
I will say, I believe I tested not registering any fingerprints on at least one of the numerous factory resets I tried, and I believe the issue still occurred--had seen threads of similar issues stemming from the fingerprint reader on other manufacturer's phones, so tried to rule it out...
The original phone I got back from SBE wasn't bricked, it just wasn't in any way improved. Fortunately Sony didn't make any weird claims that I'd done anything wrong (I wouldn't know how to mess with "rooting" or whatever--no interest/need to). It was delivered to Sonyin San Diego by FedEx today--so hoping my replacement unit ships in the next day or two...
Mikehbw said:
Despite all the issues, this phone still ticks all the boxes for me so have decided to wait for the dust to settle!
Click to expand...
Click to collapse
Agreed. With LG gone, I really want the Xperia 1 iii to pan out--only phone that has microSD, no notches/currves/radiused corners, a hogh-res screen, and a headphone jack. If I can't get one to work properly, I'll probably just buy another LG V50, second-hand.