Database Develop

Phone often freezes with froyo ....keep having to pull battery

What is happening? Pulled battery 5 times already today...what should I do and would pulling battery as often as this affect my phone or battery?
-------------------------------------
Sent via the XDA Tapatalk App

Anyone?
-------------------------------------
Sent via the XDA Tapatalk App

What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.

What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
Click to expand...
Click to collapse
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App

rensky said:
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.

I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..

Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
Click to expand...
Click to collapse
I did wipe prior flashing to Paul's zip with radio.
-------------------------------------
Sent via the XDA Tapatalk App

I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App

rensky said:
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3

SurfHost said:
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
Click to expand...
Click to collapse
does it work?

Im having similar issues with my 2.2 installation. I have it installed on my wife's non-rooted N1.
Not just that but the market is not even usable. Even if I clear cache.
Again, her phone is not rooted, I wipped everything from her phone then applied Froyo and its been a nightmare. Her phone isn't even stable enough to use and I cant seem to figure it out.
I need to find a way back to 2.1 without having to root her phone. She is adamant about me not doing that to her phone even though Ive rooted all the phones I've ever used with no issues.

I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.

Ive tried all that on her phone. I just wiped it again completely and re flashed just in case that was the issue. Phone still had all the issues described in this thread.
I wiped the sd card, wiped all previous system files via the stock recovery and re flashed the update zip. You cant get anymore clean than that and its still so unstable the phone its unusable. I have to either hope soft booting works or pull the battery as a last ditch.
Is there any way I could downgrade her phone to 2.1 without rooting? I tried the shipping rom in the sticky above but it seems that isn't totally legit for stock use because the phone doesn't like how its signed.
I guess I could call google/htc tomorrow but who knows where that'll get me. The only bonus iud that her phone is not rooted so she didn't really have her warranty voided.
-------------------------------------
Sent via the XDA Tapatalk App

I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Click to expand...
Click to collapse
I was worried if I was the only one with this problem. Phone improved today (3rd day of using) but I didn't do anything to it. Only hanged once when someone called. Hanged on calling in screen and had to pull battery.
Only once compared to 7 times yesterday!
-------------------------------------
Sent via the XDA Tapatalk App

rensky said:
does it work?
Click to expand...
Click to collapse
Yes until now it does. Sometimes the power button is reacting a little late but i havent had to pull the battery yet with the older radio.

You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.

krabman said:
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
Click to expand...
Click to collapse
I'll give this a shot when I get home from work. I'll report back on if it works or not. Thanks for the idea.

Interesting, not that I'm complaining, but after a few days of using 2.2 it seems more stable now....? haven't had any freezes today...yet.
Power button response also getting better.
-------------------------------------
Sent via the XDA Tapatalk App

I haven't had any issues for a few days as well. Still wondering if it had to do with the battery level.
-------------------------------------
Sent via the XDA Tapatalk App

SurfHost said:
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Older radios are not 100% compatible.

[Q] Same Problem, 2 different Roms

I've been having issues with my Captivate any time I flash a rom onto it. Last week I flashed Cognition 3.02 onto it. Everything worked fine for about 18 hours. Then, all of a sudden the phone would vibrate twice and reboot and go straight to the cognition boot screen, and never get past that. I would then take out the battery for a few minutes. Place it back in and turn the phone on. After being on for a bout 20-25 seconds it would do it again. So, I booted into recovery and wiped my user data. That seemed to stop it from doing that for the time being. So I took that opportunity to back some things up and you Odin and Master Clear to go back to 2.1.
After about a day I flashed Firefly 1.5 onto the phone. It has been working for about a week. This morning when I woke up (about 10minutes ago) I got out of bed, and unplugged my phone from the charger, read two text messages, and it began all over again.
Is this a common problem?

When you restore your apps, you're not restoring system data too are you?

cappysw10 said:
When you restore your apps, you're not restoring system data too are you?
Click to expand...
Click to collapse
When I flashed the ROM's I didn't restore anything in terms of apps. I just moved a folder of pictures back into the folder in the Camera. That's it.

Dr3amCast said:
It has been working for about a week.
Click to expand...
Click to collapse
Oh wow. I never was on a ROM except for 1 for that long to see if this issue comes up.
The one I was on for than was di11igaf's 2.5 version. Try using dilligaf's ROM n see if the issue comes again.
This time, pls format ur internal SD too before u flash.

Dr3amCast said:
When I flashed the ROM's I didn't restore anything in terms of apps. I just moved a folder of pictures back into the folder in the Camera. That's it.
Click to expand...
Click to collapse
Are u installing any themes on the ROMs? Some themes are incompatible and cause these FCs.

Nope, no themes or anything like that. Whenever I've flashed, I've only installed a few apps, them being E strongs task manager, eBuddy and GoSMS. The first time I only installed those because I wanted to make sure everything was good w/Cognition, but it gave me that problem, so I didn't instally any this time with firefly to see if it was the apps or something. But I guess it wasn't. I'm using Odin as I type this to flash back to 2.1. I did a master clear before of my internal memory, I'll do it again. Not sure if I should flash another rom or not.

Dr3amCast said:
Nope, no themes or anything like that. Whenever I've flashed, I've only installed a few apps, them being E strongs task manager, eBuddy and GoSMS. The first time I only installed those because I wanted to make sure everything was good w/Cognition, but it gave me that problem, so I didn't instally any this time with firefly to see if it was the apps or something. But I guess it wasn't. I'm using Odin as I type this to flash back to 2.1. I did a master clear before of my internal memory, I'll do it again. Not sure if I should flash another rom or not.
Click to expand...
Click to collapse
I am not sure of master clear, personally. I prefer format of my internal SD so its clean. Sometimes I mount it on computer, and use windows quick format.
Flash the ROM and kernel in my sign, n see how it goes with u. Once u r comfortable, let me know, and I shall post my voltage settings for optimal battery life too.

Correct me if iam wrong but I think both roms are based on rogers froyo build. Maybe try something jpy based, or andromeda which is armani base

diablo009 said:
I am not sure of master clear, personally. I prefer format of my internal SD so its clean. Sometimes I mount it on computer, and use windows quick format.
Click to expand...
Click to collapse
master clear formats the internal SD....

Pirateghost said:
master clear formats the internal SD....
Click to expand...
Click to collapse
I tried this once in CWM and ended getting my external SD too formatted. Ever since I prefer to stay away from it.

diablo009 said:
I tried this once in CWM and ended getting my external SD too formatted. Ever since I prefer to stay away from it.
Click to expand...
Click to collapse
Master clear is done through ODIN one click or via the dialer code....CWM doesnt have a 'master clear', it has formatting options....but our external sd card is not handled the same way most other android devices is handled. different mount points i believe.

Well I went to use Odin and it froze up on me so I had to unplug my Captivate and I got that dreaded phone.../ ! \...pc symbol. Took me all day of trying different key combos, finally I saw this link:
http://forum.xda-developers.com/showthread.php?t=889128
To making a jig from the 100k ohm resistors. It took me about 45 minutes to get because those resistors are so annoying but I got it and flashed it back. Then formatted my internal sd using Master Clear. Both of those roms are based on the Froyo 2.2, so I think maybe i should try a rom based on JPY or armani. However, now no matter what I do I can't get into recovery to root my phone...I've tried the 3 button trick as well as using adb...no luck...

There is an odin on the development section with a three button fix

mcord11758 said:
There is an odin on the development section with a three button fix
Click to expand...
Click to collapse
So I should flash it again using that one?

To be honest I am not sure but obviously if you are going to use roms you need there button combo

Why!?!?!?
mcord11758 said:
Correct me if iam wrong but I think both roms are based on rogers froyo build. Maybe try something jpy based, or andromeda which is armani base
Click to expand...
Click to collapse
This made sense in my mind soI flashed Andromeda on two days ago, and same problem. I've pieced together that each time it begins to occur. My phone has been on and just sitting, charging. When I unplug the charger cord, a minute or two later it will start doing that and won't stop. This time each vibration was short it did it once...pause...then 3 times. Then restarted. Rebooted, stayed on for a good 5 minutes, then did it again. Each time the interval has gotten shorter and shorter. I tried plugging the phone back into the charger but no luck. I really don't have any idea what could possibly be wrong? I guess my captivate's not meant to be customized at all

Is it telling you which app is force closing
Sent from my SAMSUNG-SGH-I897 using XDA App

iamamp3pimp said:
Is it telling you which app is force closing
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
+1 something in your setup its not playing nice. Try un installing apps you have downloaded one by one till behavior stops, or flash fresh and install apps over time to monitor which its the problem child

mcord11758 said:
+1 something in your setup its not playing nice. Try un installing apps you have downloaded one by one till behavior stops, or flash fresh and install apps over time to monitor which its the problem child
Click to expand...
Click to collapse
One thing I did try randomly last night was Flight Mode. When I boot my phone and its in Flight Mode, it doesn't cycle the rebooting or anything everything works. As soon as I take it out of flight mode, within minute or two it starts the reboot cycle. I tried deactivating data network mode, no luck as well. I will try uninstalling all of my apps, or wiping all of my user data and reinstalling slowly to see if that works.

Are you restoring anything that had to do with your phone

i might be bricked

i was trying to test all the 2.3.4 roms nd now my phone wont go past the white htc screen even when i restore 2.3.3 help?

If it turns on it's not bricked
Re-download a rom zip, boot to recovery, wipe everything, then flash the rom
(assuming you can still get to recovery [HOME+POWER] since it wasn't mentioned)
Sent from my Android using Tapatalk

i can get to recovery but when it says that i sucessfully flashed the rom then i go to reboot system it just stays at the white HTC screen idk wat to do my nandroid wont even work now its doing the same thing i have no clue what i did wrong?

are you using firerat's?
wiping before restoring nandroids/flashing a new Rom?
what recovery are you using?
what rom is your nandroid?
have you tried to re-download the rom you are flashing? (the one that stays on the HTC screen)
How long is it staying on the HTC screen?
do you have adb installed?
Sent from my Android using Tapatalk

just FYI, next time you ask for help you should post some of the answers to kyouko's questions without anyone having to ask. we can't help you as well if we don't know these things.

I put 5$ on the ROM he was flashing uses an uncapped kernel...

3 letter word; RUU.
Start from scratch and be careful what you flash before you flash it
Happy flashing buddy. Be careful!
Sent from my HERO200 using XDA Premium App

Maybe you just need to let it sit on the HTC screen for a while longer to see if it finally starts booting up. Sometimes it can take a couple of minutes. Try not to watch it, if you can.

scataldo721 said:
i was trying to test all the 2.3.4 roms nd now my phone wont go past the white htc screen even when i restore 2.3.3 help?
Click to expand...
Click to collapse
If your still having problems send me a pm I might be able to help. Good luck.
#Root/Hack-Mod_Always*

Drunkpilot said:
Maybe you just need to let it sit on the HTC screen for a while longer to see if it finally starts booting up. Sometimes it can take a couple of minutes. Try not to watch it, if you can.
Click to expand...
Click to collapse
I've had them go as long 5 mins. or so

Some Roms just won't flash.

Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.

Maybe he dont follow the instructions correctly
Sent from my GT-N7000 using xda premium

meminiau said:
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Click to expand...
Click to collapse
What method is he using to flash? If using pc Odin does the flash get stuck at factoryfs. Img?
Was he on ics stock and did he perform any factory resets on it?
If answers are yes, it's likely he's got traces of damage on his emmc chip, but we need to know where the flash is failing to understand further.
Sent from my GT-N7000 using xda premium

No and no.
His phone came with GB. He downloads the ROMs using his computer then transfers the zip to then flash using CWM recovery.
He has tried lots of different ROMs. He tried to install a new ROM the other day but before doing so he deleted a few ROMs he still had on the SD card. He flashed the new ROM and it didn't work. He freaked coz he didn't do a backup first, but he tried installed the ROMs that were still on the SD card and found them all but one to work, and the one that worked was a ROM that he had tried before but didn't work then, but this time it did work...
What is happening? Is there something he can do?
Swiped on my Gnex

meminiau said:
No and no.
His phone came with GB. He downloads the ROMs using his computer then transfers the zip to then flash using CWM recovery.
He has tried lots of different ROMs. He tried to install a new ROM the other day but before doing so he deleted a few ROMs he still had on the SD card. He flashed the new ROM and it didn't work. He freaked coz he didn't do a backup first, but he tried installed the ROMs that were still on the SD card and found them all but one to work, and the one that worked was a ROM that he had tried before but didn't work then, but this time it did work...
What is happening? Is there something he can do?
Swiped on my Gnex
Click to expand...
Click to collapse
Try flashing rom with pc odin instead of cwm.
Check out Dr ketan sticky thread in rom development for directions on how to use pc odin. It's simple.
Let us know how you progress.
Sent from my GT-N7000 using xda premium

meminiau said:
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Click to expand...
Click to collapse
No problem at all.
Sent from my GT-N7000 using xda premium

What?????
Swiped on my Gnex

Sounds very odd - only though is he's not following instructions correctly..

[Q] S5830D restarting on its own. any solutions?

I would be ok with this if it wasn't almost every time the phone is left alone.
i thought maybe installing CM would help but it still does it, went back to stock firmware (S5830DTLKI4) with no resolution.
It appeared to only be doing it when it is put to sleep, but after i unlocked it and tried to send a text with my Bell Canada sim card the phone restarted again.
It certainly isnt a SoD, because it is turning itself back on.
wifi is off, GPS is off, Bluetooth is off, and it is doing this on a 100% stock install; no market apps installed, no google account even linked.
so it appears to be restarting when i let it go to sleep, and when i try and send a text using a non-Koodo sim card. (although i dont know the effects with a Koodo sim; never had one)
I went to samfirmware and downloaded a md5 for the UK network Orange, but it didnt fix anything as far as i know, i didnt unlock it but it was still restarting itself.
Im wondering is this a software issue (if so, what is happening and is there a way to fix it?), or is this a hardware issue (perhaps there is a faulty capacitor somewhere on the board that isnt filtering voltage spikes and causing the device to reboot because of that)?
i couldn't find any references to this problem ever really being addressed.
help would be greatly appreciated.

The stock Samsung firmware for a Koodo S5830D is unstable, often when I was using it I would get reboots and freezing and a NO SIM CARD error constantly. If you have it rooted and want to install a custom ROM that won't reboot itself, I would recommend taking a look at CM9.1 RC4.1 by Wayland_ACE. I have never experienced a random reboot on that ROM. http://forum.xda-developers.com/showthread.php?t=1868121
Although of course you have to choose the right ROM for you. If you want to stay on Gingerbread, the official CM ROM (or an unofficial version) for the Ace should do the trick. If you don't care as much about stability experiment!
If the firmware is unstable (as it is with Koodo's stock ROM) it won't matter if it is locked or unlocked, if you want stability, change your ROM.

Narwhal73 said:
The stock Samsung firmware for a Koodo S5830D is unstable, often when I was using it I would get reboots and freezing and a NO SIM CARD error constantly. If you have it rooted and want to install a custom ROM that won't reboot itself, I would recommend taking a look at CM9.1 RC4.1 by Wayland_ACE. I have never experienced a random reboot on that ROM. http://forum.xda-developers.com/showthread.php?t=1868121
Although of course you have to choose the right ROM for you. If you want to stay on Gingerbread, the official CM ROM (or an unofficial version) for the Ace should do the trick. If you don't care as much about stability experiment!
If the firmware is unstable (as it is with Koodo's stock ROM) it won't matter if it is locked or unlocked, if you want stability, change your ROM.
Click to expand...
Click to collapse
i tried installing the rom you linked to but im still getting the reboot problem; is there something im doing wrong?
i wiped the user data, cleared the cache, and wiped dalvik, then installed the rom you linked, using clockwork 5.0.2.6
however it still seems to want to reboot, what is going on here?

blueblitzpup said:
i tried installing the rom you linked to but im still getting the reboot problem; is there something im doing wrong?
i wiped the user data, cleared the cache, and wiped dalvik, then installed the rom you linked, using clockwork 5.0.2.6
however it still seems to want to reboot, what is going on here?
Click to expand...
Click to collapse
In CWM go into mounts and storage> mount /data, /system, /sdcard. Should fix bootloop.

Narwhal73 said:
In CWM go into mounts and storage> mount /data, /system, /sdcard. Should fix bootloop.
Click to expand...
Click to collapse
its not a bootloop though, it's booting into CM and then once the screen goes to sleep the phone restarts itself, just like it did on the stock rom.
i already tried mounting data, system and sdcard, but it didnt help any.

Last resort... After flashing via odin, reboot into recovery & do a factory reset. If the problem persists, stop posting here & rush to service centre with the unrooted stock rom on your phone.
Sent from my GT-S5830 using xda premium

Venomous Viper 119 said:
Last resort... After flashing via odin, reboot into recovery & do a factory reset. If the problem persists, stop posting here & rush to service centre with the unrooted stock rom on your phone.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
i was hoping id get a better answer than that, but ok then.
ive always hit factory reset and clear cache before using a stock rom, else it will boot loop.
i suppose i'll reload the stock firmware and take it in to the nearest mobile center, i dont know how much good itll do though, the phone is from anther carrier and i got no warranty papers when i bought it off a friend.

racer_25 said:
i was hoping id get a better answer than that, but ok then.
ive always hit factory reset and clear cache before using a stock rom, else it will boot loop.
i suppose i'll reload the stock firmware and take it in to the nearest mobile center, i dont know how much good itll do though, the phone is from anther carrier and i got no warranty papers when i bought it off a friend.
Click to expand...
Click to collapse
Since you don't have the warranty, you'll have to pay for the service anyway. Just be sure that the phone serial no. that's on the label after taking out the battery is intact & you are all fine to get a clean service. There's nothing much you can do by yourself as it doesn't appear to be a software problem. But it might quite happen b'coz of a faulty battery. My friend's galaxy y had the issue & a replacement killed it. So may be it with you. Anyways, before buying you can try it out with your friend's battery & hope to see if the issue is solved & then go buy one. If this doesn't help, head for service as said earlier.
Sent from my GT-S5830 using xda premium