Related
Hi guys,
My girlfriend was complaining that her Vibrant kept turning off. I figured it was her first smartphone and she was just doing something silly to it. The only way I could re-start it was to take the battery out and put it back in.
Then it happened to me. Its actually happen to me a few times now, and now its getting annoying.
Today I was driving back from work, listening to a podcast and then the sound cut out. So I looked at the phone to see what was going on, and the phone was off. Again had to take the battery out to get it to reboot. Battery was at 65% when it rebooted.
Later that night, I opened up the browser and the screen froze. This time, my homepage loaded, and then it froze. Again, I had to take the battery out to get it to reboot.
These are the same problems that my girlfriend is having, so now I'm looking for some help.
Our Vibrant's aren't rooted.
I run Launcherpro, she runs stock Touchwiz.
Any help would be grateful.
Thanks
I found a Thread in the I9000 forum. It seems that it is a known issue with Bell Vibrant and Samsung and Bell are working on a fix.
The issue seems to be that when your in an area were signal is weak, the switching of bands causes the phone to freeze. I'm not an expert, just passing on the information found from other users.
But every time my phone and the gf phone has crashed, it has been in an area with weaker signal. My drive home is 5 minutes out of the city of Calgary, it crashed on my way home. My gf phone crashes in her locker at work, the lockers are in the middle of warehouse.
Once I find the thread again, I'll post the link.
Having the same problems
LAHAL Droid said:
I found a Thread in the I9000 forum. It seems that it is a known issue with Bell Vibrant and Samsung and Bell are working on a fix.
The issue seems to be that when your in an area were signal is weak, the switching of bands causes the phone to freeze. I'm not an expert, just passing on the information found from other users.
But every time my phone and the gf phone has crashed, it has been in an area with weaker signal. My drive home is 5 minutes out of the city of Calgary, it crashed on my way home. My gf phone crashes in her locker at work, the lockers are in the middle of warehouse.
Once I find the thread again, I'll post the link.
Click to expand...
Click to collapse
I'm using a Vibrant T959 and I'm experiencing the same issues. My phone is set on GSM only but it random shuts off. I tried running a search on "shutting off" and "turning off" but wasn't able to find the old thread you've mentioned above.
Any help would be greatly appreciated. It's annoying as I can miss potentially important calls and not even realize my phone is off.
Thanks,
Matt
I have never posted here before though I troll and check out what is going on about my Vibrant often and have not seen this directly answered yet, so here goes.
I downloaded and installed the official froyo the other day from Kies Mini.
I have never attempted to even boot in recovery mode.
I have never attempted to root, rom or anything that you amazing people somehow figured out.
OK, so that should help get us somewhere to start.
I noticed today that my notification bar showed the signal as the 0/ (i don't know how to place that symbal correctly) as no signal. I let it go for a few minutes because sometimes Tmobile loses signal in my building. I noticed it outside on break and I tried to reboot. It rebooted but kept rebooting. I removed to battery and its still kept rebooting after letting it sit without the battery. I tried rebooting in recovery mode and deleting the cache memory (don't want to delete user info yet unless that is my only option to get fully reset) and its still rebooting.
Basically after I rebooted the first time, its runs slowly at the S, finally gets into the homescreen, shows signal (but none of my apps, no screen responses at all, just vibrates a few times while switching from no signal to signal) then reboots.
I am pretty much at a loss here. Would love any helps I can get.
Bump, please I don't mean to be annoying, but is this something I am going to have to revert to factory on? I saw someone else had a bricked phone after download and reboot constantly like me. Ugh, to wait so long for Tmo and now this??
The BEST thing to do, if you havent modded, or rooted is to take it to yor local t-mobile store if you have one. If not, call customer support and have them send a replacement.
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.
Phone shut off and will not turn on, will not charge, will not boot, nothing.... here's the backstory.
I root my girls EVO LTE for her just for the sake of backing up data and pictures and texts. She also enjoys Fresh ROM, but I never got around to putting it on this phone, bc at the time there was no need. Also, I never did get around to turning S-OFF, just rooted, stock rom, nothing else.
About 3 months ago, she had a random boot loop, which, after some googling, seemed to be a random problem that some people were experiencing, unrelated to root or anything. So we fixed her phone, updated it, at the time, and have since done nothing to it. A few weeks ago, she started have major problems. Texts would take 5 minutes to open, contacts would also, and sometimes she couldn't dial out. Problems that I hadn't gotten around to looking into.
Today, her phone just completely turned off and hasn't done anything since. Won't turn on, charging does not give it a light. I tried to boot into recovery etc. Is the phone completely BRICKED?
It's within the year warranty, but I know if sprint gets it back on and see it's rooted, they'll be assholes about it, even though it doesn't seem to be related.
jirafabo said:
Phone shut off and will not turn on, will not charge, will not boot, nothing.... here's the backstory.
I root my girls EVO LTE for her just for the sake of backing up data and pictures and texts. She also enjoys Fresh ROM, but I never got around to putting it on this phone, bc at the time there was no need. Also, I never did get around to turning S-OFF, just rooted, stock rom, nothing else.
About 3 months ago, she had a random boot loop, which, after some googling, seemed to be a random problem that some people were experiencing, unrelated to root or anything. So we fixed her phone, updated it, at the time, and have since done nothing to it. A few weeks ago, she started have major problems. Texts would take 5 minutes to open, contacts would also, and sometimes she couldn't dial out. Problems that I hadn't gotten around to looking into.
Today, her phone just completely turned off and hasn't done anything since. Won't turn on, charging does not give it a light. I tried to boot into recovery etc. Is the phone completely BRICKED?
It's within the year warranty, but I know if sprint gets it back on and see it's rooted, they'll be assholes about it, even though it doesn't seem to be related.
Click to expand...
Click to collapse
Does it show in device manager when you connect to a pc?
njfoses said:
Does it show in device manager when you connect to a pc?
Click to expand...
Click to collapse
Well I dont have the drivers installed bc I recently added an ssd and started from scratch, and like I said, I don't mess with her phone too often.
But it doesn't do anything when I plug it in via usb, doesn't make a sound, nothing pops up, and it doesn't try and connect. It's lifeless.
Some have had good results plugging into a wall charger for 6-8 hours and then it comes back to life.
It may work.
Sent from my PC36100 using xda app-developers app
Your timing is good, bricks tend to happen during major updates
Have your gf take her phone back to the Sprint store and say it won't turn on, charge etc. if the phone is truly bricked, they can't tell it was rooted or whatever. They should replace it because it's within the warranty period. If she has an SD card, take it out (especially if it had ROMs on it).
The key is have your girl friend do this, better would be to have someone's mother take it in.
bigmoogle said:
Your timing is good, bricks tend to happen during major updates
Have your gf take her phone back to the Sprint store and say it won't turn on, charge etc. if the phone is truly bricked, they can't tell it was rooted or whatever. They should replace it because it's within the warranty period. If she has an SD card, take it out (especially if it had ROMs on it).
The key is have your girl friend do this, better would be to have someone's mother take it in.
Click to expand...
Click to collapse
This is exactly what I done when I bricked downgrading firmware. An OTA had just been released and I told them I took the update and the phone died. They replaced it immediately no questions asked.
Sent from my EVO using xda premium
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.