So I was hoping that anyone here could shed some light on an issue that one of my friends who just bought a Nexus is having. His N1 is bone stock, and is an AT&T model. Every once in a while, completely out of the blue, the screen will turn black and restart, but then enter an infinite boot loop, where the only solution is to remove the power adapter and battery.
In trying to pinpoint the problem, we have noticed:
-It really only tends to happen when the device is plugged in.
-It's not related to the battery, charger, or microSD (since we tried mine to no avail)
-It's probably not kernel, ROM, or radio related (we let it do the OTA 2.2 update, and the crashes were still present)
I don't understand why it only happens when the phone is plugged in. The phone isn't hot to the touch, so I doubt that the battery is over heating.
Any help will be greatly appreciated. Thanks!
PS. I tried searching, but the only mention of boot loops I could find were on custom ROMs and Kernels...
Exact Same problem and Phone here!!!
Just got it today too! Please any suggestions would be nice! Want to root this phone but to afraid there is a hardware issue!
My friend ended up calling HTC and they asked him to return it, which he did, for a full refund. Ironically, he ended up getting a Samsung Galaxy S (ATT Captivate variety). Nexus one, although less powerful, is more sleek in my book...
I've got almost the exact same problem on an AT&T N1 running Froyo FRF91, the two differences I have are that the phone does feel hot to the touch, and that it never happened on 2.1. If anybody has some info on this it would be greatly appreciated, but I will be calling HTC/Google in the next few days to see if we can resolve this problem.
Hey guys,
I had a very similar problem with my phone rebooting while charging especially on the Car Dock. I ended up doing an exchange with Google/HTC and received another unit. This one now has no problems with rebooting. I suggest calling and getting your units replaced. My guess is there was a bad batch that have hardware issues.
Jay
jpav80 said:
Hey guys,
I had a very similar problem with my phone rebooting while charging especially on the Car Dock. I ended up doing an exchange with Google/HTC and received another unit. This one now has no problems with rebooting. I suggest calling and getting your units replaced. My guess is there was a bad batch that have hardware issues.
Jay
Click to expand...
Click to collapse
What can I do if it is unlocked? Any chance they still help you out? Or just forget it?
I don't think it would hurt to just give them a call. I have read some forums where people have sent unlocked phones in for repair and then got them back fixed and re-locked. It is worth a shot instead of having a faulty phone. I did the exchange option and it did take me a while to get my replacement phone, but that was due to HTC moving their repair facility according to the tech. The techs that I have talked to have been helpful. If I thought a tech was no good I just hang up and try again with a different person.
Jay
I have been having pretty much the exact same issues.
I have an AT&T unlocked/rooted N1.
Random reboots frequently when the phone is charging via plug or USB for seemingly no reason. I thought it may have been an app, or combination of apps, so I tried a combination of different steps to try and find a solution.
Wiped data/cache
Wiped data/cache & fix apk permissions (Amon Ra 1.7.0.1)
Wiped data/cache and flashed the current ROM I was using again
Wiped data/cache and flashed different ROMs (both 2.1 and 2.2 w/proper radio) including MCR r16-21, PhoenRom, LeoFroYo, Cyanogen 5/6 RC1 and even tried intersectRaven's Kernel's
Reformated the SDCard both via gparted from Ubuntu live cd and Amon Ra's recovery 1.7.0.1
Swapped out the SDCard thinking possibly a bad block
And finally re-flashed back to shipping stock 2.1 and stock recovery w/successful OTA 2.2 install
All steps I was able to get my N1 to randomly reboot plugged in or not. I even had it sitting on my desk at work unused for 30-40 min (running CM RC1) and it rebooted with no user input what-so-ever. It happens more often while plugged in but was not limited to charging state.
All that said, I finally called support, took about 30 min total to arrange a replacement. This included a factory reset while on the phone with the tech and I was able to get the phone to reboot within a few minutes of first boot.
Take it for what it is worth, but I am positive that this is a hardware issue in my case. Just hope my replacement goes without penalty (unlocked and all) and that my new N1 doesn't have the same issues.
Related
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts
Hey guys, I've got a problem and am hoping the minds at XDA can help.
My brother and I both have a Nexus One and both have unlocked bootloaders. I've never had a problem installing custom roms or restoring back to the shipping rom, or suffered any problems whatsoever.
However his phone, suffers random reboots all the time. I unlocked his bootloader and from the very first Rom we had problems. I double-checked my methods and even tested it again on my phone with no problem whatsoever. So, he got back into town today and I restored his phone to the shipping rom (userdata, boot, system, radio, etc.) It still randomly reboots. I thought it might have been a bad battery and swapped it out with a different one, and I was able to mess around longer with the phone, but it still rebooted on its own accord.
I told him he could call HTC, but more than likely he would have to pay 180 dollars to replace the motherboard on the phone. He says he'll just deal with the random reboots instead of the possibility of paying the money.
Does anyone have any suggestions as to what the problem could be, because after reflashing the shipping rom I'm out of ideas. Another odd thing I noticed with his phone from the get-go was the haptic feedback and vibrations in general, they were barely noticeable, almost non-existent as compared to my and my friend's nexus one.
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Mine reboot when it overheats during charging. There are several overheating threads u should check out.
Sent from my Nexus One
Just be honest
houmi1 said:
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Click to expand...
Click to collapse
From what I hear, if your honest and tell google that you unlocked your bootloader they will still repair your device, I don't know about replacing it if it can't be repaired. But before you go that route try troubleshooting. Make sure you have the correct radio, not all roms come with the correct radio. Non-compatible kernals can become a issue to, if you flashed a custom kernal. I get the bootloop problem if I flash a rom without wiping, which I never do, except when the instructions say no wipe required, and then I get the bootloop issue. So try a full wipe, data, dalvik & cache, ext, and then reflash your rom.
I had random reboots up the wazoo. My phone was unlocked/rooted/running FRF93. I downgraded to other versions of Froyo and even went back to 2.1/CM and it was still rebooting.
Turns out that HTC actually puts it through a reasonable testing procedure to determine if it was in fact the user that damaged the phone. So even if it is unlocked/rooted and the phone passes the test, you will get your repair free of charge just like me. I'm currently waiting for them to ship my phone back.
Although I have heard horror stories from HTC, so I really think it depends on the moon cycle...
Like a poster above said, BE HONEST. Let them know the truth that it's rooted/unlocked but currently running a standard ROM. If they give you the standard "if it's rooted, you're going to have to pay", tell them that you're heard of their testing procedure to determine if it's the user's fault. Go to a supervisor if you have to.
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
houmi1 said:
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
Click to expand...
Click to collapse
Any updates? I have a similar issue
Yeah I basically think it's heat related and unrelated to the firmware, RAM, etc.... I had the phone at a very cool place and it works perfectly, and when I started using it, as it got hot, it started rebooting, and I noticed the back of the phone was very hot.
So I think nxt was right #2 in this thread.
Houman
The above observation would seem to make sense. My phone would reboot while trying to watch youtube videos sometimes, but ALWAYS within a few minutes of using it on the mains...
I have since had it sent back to HTC to have the phone repaired. I had rooted my phone just to get 2.2 however as it was a genuine hardware issue they replaced the main board and now not only does the phone not reboot anymore, the issues I had with no 3G (only Edge) have disappeared too. Happy
BANE
Hi
So I got my phone back from htc, they basically fixed it and even locked the bootloader so all is well
Just FYI
Houman
My wifes captivate has the random shut down issue. Already got replacement phone and it started back up after a few weeks. If I use Odin one click to restore ucjf6 (or upgrade her phone to froyo) will this end my shutdown woes? I have been under the impression that the shutdown issue was a software problem.
I can't say I've ever heard of that happening to a stock rom (I'm guessing you never flashed any custom ROMs on to it)...
At this stage, I think it'll be better off if you take it back to AT&T as you've not really done anything to it (modding/romming wise).
Its out of warranty.she has been dealing with it by using an app from the market. I was hoping that upgrade to froyo would over write the defective software. Then I got to thinking that maybe odin would do the same thing.
The app from the market works perfectly, but it kills her battery life(it's called Captivate Keep Alive from Blue Steel).
Hmm, then yeah I suggest for you to flash her phone... Possibly to a custom ROM at this stage. Stock ROMs usually have way too much bloatware.
Also, if you can please check what version of Captivate she has... It'll be underneath where her battery is.
Usually a four digit code (1006,1007,1008,etc).
Hers is 1008.
Yeap, you should be fine to use any of these ODIN files.
2.1 - http://www.megaupload.com/?d=SBSMALFJ
2.2 - http://www.megaupload.com/?d=QL6NX702
If you need instructions, just yell again
I would probably recommend the 2.2 one (if you're not going to flash any custom ROMs).
If you are thinking of custom ROMs, then I recommend going to 2.1.
Thanks for the help. I, and my wifes battery, appreciate it.
My cappy also just randomly shuts off, but i know it isn't the battery because I've switched batteries from another cappy. I also heard there were re-calls on some cappy's as well. can it also be a hardware problem?
I have installed Firefly 3.0 on my captivate every now and then when the battery gets low to like 30% it turns off and then i gotta pop the battery out and pop it back in because it randomly shuts down. It has happened in games, phone calls from friends that are in iraq, and various other things. I just reloaded fire fly onto my phone but I am not sure whats going on with it.
After trying about everything to kill this gremlin, deleting widgets, CKA, Load Monitor, etc., I went back to JF6, charged the phone fully and let it run. The problem is still here. On the very next battrery cycle after reverting to JF6, the random shutdown occurred again while running off battery with a bone stock set-up. The battery was at about 70% when the failure occurred. (It is a new battery too.)
I bot my fone last Sept, just shy of one year ago. So today I called ATT and after a short discussion with the rep, a replacement is on the way. I described the problem and advised that one by one I had un-installed all the widgets and apps that I thought might be causing problems, then mentioned resorting to the factory reset.
A few questions followed. Then I was on hold awhile. I'm really glad I reverted to JF6 and ran the stock set-up to the fail condition. It allowed me to speak to the rep with confidence, and high hopes that they would get me an exchange. When it came time to answer questions about the Settings About details, it was all right as rain.
Now the question is will the new device have the power-off Gremlin? We shall see!
Guess I'll have some fun flashing different set-ups for these next few days 'til the replacement arrives.
Then one last flash to JF6 and back this first cappy goes...
If you are experiencing this shutdown issue, get back to stock and see if it stays. If you have had your phone less than one year, and it's dying on you, you should be able to get a refurb.
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
No one? I guess this really is a tough one.
Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!
Sn0wdune said:
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!
Click to expand...
Click to collapse
I think I have the same problem as you did. After suddenly dropping and rebooting, my battery level jumps back up when the phone starts, and again, and again. The phone is functioning normally only when plugged in. I also presume that it is a battery problem, but the fact that the battery level rises back after dropping, makes me wonder.
EDIT: Problem solved with buying a new battery.
Sorry to jump in, just curious, did you solved this? If you do, hope to hear your solution, might help others in future
SGs3n SlimKat9.0(Android-Andi)