Related
So my Eris has gotten bad with the "trackball always moving left" problem, and I'm taking it back in to Verizon. I currently have GSB v1.6, and I need to put it back to stock. I dl'ed the RUU (2.36.605.1) and every time I run it, following the instructions, it gives me an error saying I have less than 30% battery power, when the battery is fully charged. Occasionally it just gets stuck on the verifying information screen.
I've tried wiping the battery stats from the recovery, I've tried reinstalling two different versions of HTC Sync, which seemed to get it past the "verifying" screen. I even tried restoring a nand backup of Sense I did before I started flashing roms.
I'm stuck. What would cause it to read 100% as less than 30? Also, while I'm on my stock Sense rom, is there any way to just unroot it without using RUU? It's in the condition it was in the day I rooted.
Edit: It's Error(120) not 220. I typed the wrong one in the title.
prsguitaruser said:
So my Eris has gotten bad with the "trackball always moving left" problem, and I'm taking it back in to Verizon. I currently have GSB v1.6, and I need to put it back to stock. I dl'ed the RUU (2.36.605.1) and every time I run it, following the instructions, it gives me an error saying I have less than 30% battery power, when the battery is fully charged. Occasionally it just gets stuck on the verifying information screen.
I've tried wiping the battery stats from the recovery, I've tried reinstalling two different versions of HTC Sync, which seemed to get it past the "verifying" screen. I even tried restoring a nand backup of Sense I did before I started flashing roms.
I'm stuck. What would cause it to read 100% as less than 30? Also, while I'm on my stock Sense rom, is there any way to just unroot it without using RUU? It's in the condition it was in the day I rooted.
Edit: It's Error(120) not 220. I typed the wrong one in the title.
Click to expand...
Click to collapse
This should be what you want. Good luck! No idea about the battery % issue unless it's just severely out of calibration.
roirraW "edor" ehT said:
This should be what you want. Good luck! No idea about the battery % issue unless it's just severely out of calibration.
Click to expand...
Click to collapse
I didn't even know this existed. Downloading now. Thanks.
prsguitaruser said:
I didn't even know this existed. Downloading now. Thanks.
Click to expand...
Click to collapse
You're welcome!
It worked perfectly. I'm back to unrooted Stock 2.1.
prsguitaruser said:
It worked perfectly. I'm back to unrooted Stock 2.1.
Click to expand...
Click to collapse
Woot! Glad it went smoothly for you.
hey folks,
i have encountered an annoying problem that has made using the s2 quite an unpleasant experience recently.
I bought my s2 about 4 months ago. after 2 weeks or so i switched to miui (galnet) and have stuck to miui ever since. later i switched to langthangs releases as well as siyahs kernels (loving both, major props to them).
around mid of december, my phone suddenly started to crash. up till then i had a couple of freezes here n there, maybe once or twice a months. but since then, even though i did not change anything, my phone has been crashing more often, like 5-10 times a week. updating kernel and rom didnt help.
i experience two types of crashes:
a) freeze: phone just stops working. i have to take out the battery to reboot
b) reboots: phone just reboots out of the blue. sometimes it reboots 3-4 times in a row, like after the first reboot the phone does nothing for 2-3 minutes, then reboots again and so on
i am not sure if that helps, but most of the time the freezes occur while using the internet, the market and playing games. reboots occur randomly, even if the phone is not used at all.
i haven't done any overclocking, just undervolting using voltage control. but i had been using the reduced voltages for weeks, long before the crashes started to occur. and yes, i did try switching back to the stock voltages.
i may have dropped my phone a couple of times, but none of the drops was really bad as it has no scratches or dents.
Anyone else having the same experience?
Is there a way to check if -maybe- the ram/rom is defect? If nothing helps, i think i ll have to flash a stock rom and submit a warranty claim
I would go on a limb saying its MIUI's fault. Wich version of Syiah are you using? Try to reflash different version, I found that 2.6.2 is stable. Also the new one 2.6.6 wich I'm currently testing is stable to, other ones were kinda buggy.
Also are you undervolting or UC'ing ?
If all else fails flash different ROM, after testing many of them I found the latest Criskelo to be stable as a rock.
The only way to really tell is to flash back to a stock rom and see if the freezes/reboots still occur...
Sent from my GT-I9100 using Tapatalk
well, i have tried different roms. and yeah, i am undervolting and underclocking (200-1000).
but isnt it strange? i have been using miui for months without any problems, and baaam ... suddenly the phone starts crashing? i mean at the time the freezes and reboots started to occur, i had been using the same system (kernel,rom,setting,apps) for weeks without any problems.
i ll try going back to stock. if that doesnt help, ill send it in.
btw. i have flash stock via odin, will the exclamation mark during the bootup process vanish?
dabrain23 said:
btw. i have flash stock via odin, will the exclamation mark during the bootup process vanish?
Click to expand...
Click to collapse
Yep, hence you flashed original firmware the dredded(by some) yellow triangle will dissapear.
It will reapear as soon as you root your device.
that last sentence was supposed to be "if i flash stock via odin ..."
ok. ill try that and report back.
BUT
if flashing a stock rom helps, the problems much likely lies with the custom rom. but if so, why did they work perfectly fine until recently?
i may have dropped my phone a couple of times, but none of the drops was really bad as it has no scratches or dents.
Logic says that is the answer .
jje
u think so?
the phone just slipped out of my hand a couple of times, but it never fell on the floor (lets say 30cm or more).
and why would sth like that cause freezes like that? i mean my sisters ace has a totally shattered glass and its still working perfectly fine.
anyway, backing up all my stuff and trying a stock rom tmr
Hi,
I have a Galaxy S2 on TMobile in the UK. Not rooted, just been upgraded to ICS with the official firmware through Kies.
Ever since then I've been randomly getting a black screen - i.e. phone doesn't respond to any of the buttons to turn the screen on. Only way to get the phone to work again is a battery pull. Haven't installed any apps from prior to ICS, and prior to ICS I didn't have this problem.
As well as getting a black unresponsive screen it seems to get really warm. Not the normal been playing a game warm, but bordering on really hot. When I do the battery pull and restart there's also been a big battery drain - have lost half the battery before and the phone warning is on screen saying it's about to run out of battery when it was 60% charged before.
I'm guessing no one's going to have a simple answer to this (although it would be great if anyone does, but I've searched and haven't found anything) - but any tips on trying to identify what the cause is? Could it be a bad app maybe?
I tried logcat but didn't really understand it (!) and I wasn't sure if it would record what happened before a battery pull anyway. What's a way of recording what's going on that will stay recorded after a battery pull?
Any tips to help get the bottom of this would be much appreciated
Many thanks
Andrew
First backup data and factory reset .
Still a problem reinstall the firmware.
Checkfus will let you download it and flash via Odin .
Or take it to a service centre is the other choice .
jje
factory reset m8 if ur carrying ur bckup frm gb ,than some apps r not fine wiv ics...jus use ur ics wivout ur bckup of apps and download betterybattstat and some apps to c wats draining,ull get some idea.
magosalas said:
Hi,
I have a Galaxy S2 on TMobile in the UK. Not rooted, just been upgraded to ICS with the official firmware through Kies.
Ever since then I've been randomly getting a black screen - i.e. phone doesn't respond to any of the buttons to turn the screen on. Only way to get the phone to work again is a battery pull. Haven't installed any apps from prior to ICS, and prior to ICS I didn't have this problem.
As well as getting a black unresponsive screen it seems to get really warm. Not the normal been playing a game warm, but bordering on really hot. When I do the battery pull and restart there's also been a big battery drain - have lost half the battery before and the phone warning is on screen saying it's about to run out of battery when it was 60% charged before.
I'm guessing no one's going to have a simple answer to this (although it would be great if anyone does, but I've searched and haven't found anything) - but any tips on trying to identify what the cause is? Could it be a bad app maybe?
I tried logcat but didn't really understand it (!) and I wasn't sure if it would record what happened before a battery pull anyway. What's a way of recording what's going on that will stay recorded after a battery pull?
Any tips to help get the bottom of this would be much appreciated
Many thanks
Andrew
Click to expand...
Click to collapse
I am having exactly the same problem. This has started just after upgrading to ICS. (I have an unlocked S2 CSC:XEU). Never had this problem before. I tried hard reset but the problem is still there.
I have upgraded using Kies.
I have the same problem on unlocked S2 CSC:XEU. not rooted...
reset didn't work. full wipe - the same problem
ics problems
hi, i have the following problems after updating to official ICS,
wifi sometimes gets stuck between on/off
sometimes phone goes to sleep and does not respond
wake up is slower than in GB
after numerous hard resets and re-flashing ICS with odin these issues persist.
I recommend re-flashing the official GB version and wait till samsung sort their crap out.
all these issues are kernel related. the wifi issue is reported to be a faulty stock kernel and the black unresponsive screen also is a kernel issue I faced with some beta kernels.
my tip, before you hesitate to go back to GB, give one of the custom kernels a try. Siyah, Speedmod, ... just for the moment don't tweak anything and make sure you really flash an ICS kernel (!!). Just flash one of these kernels and give it a try, you don't even have to do it with odin and thus increase the counter, but you can use that variant. When you are in CWM, instead of flashing the SU zip file, flash the custom kernel zip which will root your phone, too.
Now give the custom kernel a try and see if your issues are gone.
If you don't like it, just flash the stock kernel with odin and uninstall SU and Busybox, and you are back to stock ICS.
I had the same problem. Kernel. Flash the latest siyah kernel and sleep of death will dissapear
Sent from my GT-I9100 using XDA
I'm getting the exact same issue running Siyah 3.3.2 and CM9. Also happened with stock ICS.
First few times it happened the phone was in my pocket and I felt it get warm. Only way to recover it was to hold power button in for about 10 seconds and it then reboots. I thought the screen was unlocking in my pocket and it was switching off due to overheating... but
Happened again today whilst I was using the phone. Screen went black and phone started getting hotter and hotter. I now think something is causing some kind of loop that causing the lockup / heat up and the phone is actually still on until I press and hold the power button.
I'm currently trying a "record" with CatLog but I can reproduce the problem easily apart from it happening 4 times in the 4 weeks I've had the phone.
(Its a I9100P if that makes any difference)
First of all, my phone is running jellybomb version 2, freeza beastmode kernel 2.0 and cpu running at 2.7. I've never had problems before until one day I downloaded a file that had a virus, so I decided to do a restore using twrp. The restore failed and my phone and it got screwed, I've tried several methods to get it running again and I finally found the solution. I flashed the brickbug file and it was fixed. Now I noticed that sometimes when I restart the phone, it won't restart, it just powers off. There are also times when my phone just blacks out and freezes and I have to do a battery pull. There are also incidents where after boot up from a restart or battery pull, my touch screen won't respond. It's really weird. I dirty flashed to jellybomb version 2 from version 1, I doubt that's the issue since these problems started happening after I flashed brickbug to fix my phone. Anyone know what could be wrong or a fix? It's not a huge issue since my phone works fine most of the time, but it gets a bit annoying when the problem does happen. Last resort would be wipe absolutely everything and start over..
Sent from my SM-N900P using XDA Premium 4 mobile app
vizi0nz said:
First of all, my phone is running jellybomb version 2, freeza beastmode kernel 2.0 and cpu running at 2.7. I've never had problems before until one day I downloaded a file that had a virus, so I decided to do a restore using twrp. The restore failed and my phone and it got screwed, I've tried several methods to get it running again and I finally found the solution. I flashed the brickbug file and it was fixed. Now I noticed that sometimes when I restart the phone, it won't restart, it just powers off. There are also times when my phone just blacks out and freezes and I have to do a battery pull. There are also incidents where after boot up from a restart or battery pull, my touch screen won't respond. It's really weird. I dirty flashed to jellybomb version 2 from version 1, I doubt that's the issue since these problems started happening after I flashed brickbug to fix my phone. Anyone know what could be wrong or a fix? It's not a huge issue since my phone works fine most of the time, but it gets a bit annoying when the problem does happen. Last resort would be wipe absolutely everything and start over..
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Honestly my phone does the same with occasional random reboots and lock ups requiring battery pulls (Even the power button-menu-power up didn't restart to twrp) and even then restarting doesn't usually go without a hitch. Even when I was running stock root my phone would get stuck at the yellow sprint screen from time to time and I'd have to go TWRP and wipe Dalvik and Cache, then Dalvik again to get it to reboot.. The only reason I didn't unroot was was because even when my phone was new and out of the box, stock it wouldn't reboot cleanly all the time.
It got a little better after the firmware updates but it still hasn't gone away entirely.
I do expect it to get cleared up eventually but for now just take it as a fact of life with this phone.
demetrios3 said:
Honestly my phone does the same with occasional random reboots and lock ups requiring battery pulls (Even the power button-menu-power up didn't restart to twrp) and even then restarting doesn't usually go without a hitch. Even when I was running stock root my phone would get stuck at the yellow sprint screen from time to time and I'd have to go TWRP and wipe Dalvik and Cache, then Dalvik again to get it to reboot.. The only reason I didn't unroot was was because even when my phone was new and out of the box, stock it wouldn't reboot cleanly all the time.
It got a little better after the firmware updates but it still hasn't gone away entirely.
I do expect it to get cleared up eventually but for now just take it as a fact of life with this phone.
Click to expand...
Click to collapse
Yeah, I've been wiping dalvik and cache too, to get my phone back to normal at times too.
Sent from my SM-N900P using XDA Premium 4 mobile app
vizi0nz said:
First of all, my phone is running jellybomb version 2, freeza beastmode kernel 2.0 and cpu running at 2.7. I've never had problems before until one day I downloaded a file that had a virus, so I decided to do a restore using twrp. The restore failed and my phone and it got screwed, I've tried several methods to get it running again and I finally found the solution. I flashed the brickbug file and it was fixed. Now I noticed that sometimes when I restart the phone, it won't restart, it just powers off. There are also times when my phone just blacks out and freezes and I have to do a battery pull. There are also incidents where after boot up from a restart or battery pull, my touch screen won't respond. It's really weird. I dirty flashed to jellybomb version 2 from version 1, I doubt that's the issue since these problems started happening after I flashed brickbug to fix my phone. Anyone know what could be wrong or a fix? It's not a huge issue since my phone works fine most of the time, but it gets a bit annoying when the problem does happen. Last resort would be wipe absolutely everything and start over..
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds like its the beastmode kernel issues. Flash version 1.8 and see if that fixes your issues.
I would run the MJ4 tar via Odin to start totally fresh.
I am having a similar issue. my phone will just reboot on its own and freeze up a lot. i dont think its the kernel because it has been happening ever since i first installed the jellybomb rom and had a lite kernel installed. now switched to beast 2.3 and still having the same issues. im gonna flash 1.8 and see if it gets any better. but people are posting positive results on the 2.3 . dont know what to do. its frustrating
sillykaos said:
I am having a similar issue. my phone will just reboot on its own and freeze up a lot. i dont think its the kernel because it has been happening ever since i first installed the jellybomb rom and had a lite kernel installed. now switched to beast 2.3 and still having the same issues. im gonna flash 1.8 and see if it gets any better. but people are posting positive results on the 2.3 . dont know what to do. its frustrating
Click to expand...
Click to collapse
Before going through all that mess, toss on a stock kernel and see if your issues go away. You'll narrow down the issues right quick.
Compusmurf said:
Before going through all that mess, toss on a stock kernel and see if your issues go away. You'll narrow down the issues right quick.
Click to expand...
Click to collapse
Ill give it a shot when i get home. barely have service here at my office. ill post my results back.
Compusmurf said:
Before going through all that mess, toss on a stock kernel and see if your issues go away. You'll narrow down the issues right quick.
Click to expand...
Click to collapse
My phone has been doing this from the time i took it out of the box on October 4. It was ever worse then, so much so that I returned the phone exchanged it for a new one. The problems continued and I questioned my decision to upgrade to the Note 3 but then the firmware upgrades improved things a little.
I can tolerate the issues now and I do expect them to go away on future updates
edgar360 said:
Sounds like its the beastmode kernel issues. Flash version 1.8 and see if that fixes your issues.
Click to expand...
Click to collapse
I flashed 2.3 kernel and it seemed to fix most problems.. I just get Internet shutdowns here and there.. So far that's the only problem.
Sent from my SM-N900P using XDA Premium 4 mobile app
vizi0nz said:
I flashed 2.3 kernel and it seemed to fix most problems.. I just get Internet shutdowns here and there.. So far that's the only problem.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
2.3 is the shiz, bro. I know some have issues with it, but for me it far exceeds even 1.8. Even with no overclocking, 1.8 would do odd stuff, like go to off when I'd selected restart (plugged in or not), &c. With 2.3, I've yet to run into any issues, the phone behaves as I've directed it. I overclock it using profiles in SetCPU, and the cores stay cool. With 1.8, no such luck.
As to Internet shutdowns, I have found that the browser plays a role in things. Having never used the stock browser, I switch mainly between boat browser and chrome, and both will occasionally freeze. Long back press to kill is my fallback.
Sent from my SM-N900P using Xparent BlueTapatalk 2
what your describing
Your phones should run flawlessly all the time. I would take issue that when the phone starts acting buggy, it's just normal for this phone.....I disagree with that, there is a issue somewhere if you have these issues occasionally.
Just my 2 cents
Well it took my slack ass a couple weeks to flash the stock kernel due to my issues. and after a few days my phone hasnt randomly rebooted. So i take it my phone is not liking the BEAST right now? This is just some poopoo.
So here is my current problem: My phone will drastically slow down when trying to multitask. I.e. I basically cant do anything when Pandora is running or ill start to get stops and skips (not connection related), and occasionally, depending on the app, the phone with freeze for an extended period, things disappear from the screen, then it goes blank and back to lock screen asking for pattern rather than fingerprint for "added security." (this is what I'm calling a crash)
Many apps will also start to lag and crash after periods of time, even running on their own. Like tumblr, meetme and facebook.
I have my CPU usage up, and idle is around 7 across the board. Once it starts to creep up above 12-15 is when ill start to get the lagging, lock ups and freezes occur around 20-30, and I've seen it spike as high as ~55 before a crash. Thing is, I'm getting lock ups and freezes while the graphical bar (the red, green, blue one) is barely moving past the CPU usage numbers.
Sorry, I'm not too sure what info to provide. This is a new problem for me. My old phone (running a 1.2ghz quad core, LG optimus G) was able to multitask better than this phone. I never had any skips or freezes while running pandora AND one of those other apps on that phone. Is this a corrupted install? Is this Octo core phone just THAT slow?! I'm not super experienced with ADB, but experienced enough to use it if need be. Any help would be appreciated.
KobaltPanther said:
So here is my current problem: My phone will drastically slow down when trying to multitask. I.e. I basically cant do anything when Pandora is running or ill start to get stops and skips (not connection related), and occasionally, depending on the app, the phone with freeze for an extended period, things disappear from the screen, then it goes blank and back to lock screen asking for pattern rather than fingerprint for "added security." (this is what I'm calling a crash)
Many apps will also start to lag and crash after periods of time, even running on their own. Like tumblr, meetme and facebook.
I have my CPU usage up, and idle is around 7 across the board. Once it starts to creep up above 12-15 is when ill start to get the lagging, lock ups and freezes occur around 20-30, and I've seen it spike as high as ~55 before a crash. Thing is, I'm getting lock ups and freezes while the graphical bar (the red, green, blue one) is barely moving past the CPU usage numbers.
Sorry, I'm not too sure what info to provide. This is a new problem for me. My old phone (running a 1.2ghz quad core, LG optimus G) was able to multitask better than this phone. I never had any skips or freezes while running pandora AND one of those other apps on that phone. Is this a corrupted install? Is this Octo core phone just THAT slow?! I'm not super experienced with ADB, but experienced enough to use it if need be. Any help would be appreciated.
Click to expand...
Click to collapse
I would first try a clean flash/factory reset/cache wipe but is there a reason why you are still using cm13 vs los14? I had no issues with cm13 but los14 is much better anyways.
NinjaL said:
I would first try a clean flash/factory reset/cache wipe but is there a reason why you are still using cm13 vs los14? I had no issues with cm13 but los14 is much better anyways.
Click to expand...
Click to collapse
Los14 was not avail when I was flashing my phone. I use it for business so its always risky to flash and what not. Never had a problem, I just don't wanna risk it. But if this is the case, may as well move to los14.
KobaltPanther said:
Los14 was not avail when I was flashing my phone. I use it for business so its always risky to flash and what not. Never had a problem, I just don't wanna risk it. But if this is the case, may as well move to los14.
Click to expand...
Click to collapse
Ah I see, yeah makes sense haha
Yeah I would backup and then try a clean flash/factory reset if you want to stay on cm13, other than that, I don't know anything general you could do as far as staying on marshmallow goes.
Los14 and Los14 based roms are much smoother however and most of the bugs have been worked out by now. If you're not set on staying with marshmallow, try out some of the nougat roms :good:
Obv you'll want to backup, wipe, flash a rom, flash gapps, wipe cache/dalvik, and reboot but you prob know the drill already haha. You are on twrp or cm recovery?
NinjaL said:
Ah I see, yeah makes sense haha
Yeah I would backup and then try a clean flash/factory reset if you want to stay on cm13, other than that, I don't know anything general you could do as far as staying on marshmallow goes.
Los14 and Los14 based roms are much smoother however and most of the bugs have been worked out by now. If you're not set on staying with marshmallow, try out some of the nougat roms :good:
Obv you'll want to backup, wipe, flash a rom, flash gapps, wipe cache/dalvik, and reboot but you prob know the drill already haha. You are on twrp or cm recovery?
Click to expand...
Click to collapse
Nah, I'm not stuck with MM. I like to stay with the best available, so yeah, I'll definitely go with Los14. Thanks for the input! As long as its smoother and allows me to actually multitask, I'm sold. I tend to use TWRP, but that's probably just because its what I'm used to. The interface is nice. And you can update OTA.
KobaltPanther said:
Nah, I'm not stuck with MM. I like to stay with the best available, so yeah, I'll definitely go with Los14. Thanks for the input! As long as its smoother and allows me to actually multitask, I'm sold. I tend to use TWRP, but that's probably just because its what I'm used to. The interface is nice. And you can update OTA.
Click to expand...
Click to collapse
Yeah twrp is what I use too :good: