Help! my phone freezes and reboots.
ATT phone
Followed the GladRoot method for rooting. (worked fine used it for a day)
Installed GingerBlur 1.1 (Used for half a day then problems started)
Phone was about half battery so I stuck it on the charger.
I come back an hour or two later and the phone has the red Motorola dual core logo frozen on screen, phone was pretty hot.
Took out power and battery and waited for phone to cool.
Re-installed the battery powered up and the phone went into a boot loop (Sometimes with flashing indicator other times without once with a solid red).
Powered off and waited about 15 minutes.
Tried again, same thing.
Powered off removed sim and SD and did a SBF flash with 1.2.6
Flash completed without any problems, and phone booted, powered off and reinstalled sim.
Still having problems. Phone boots now but every 2-3 minutes it freezes and reboots >_< I managed to get through the motoblur setup and tried doing a factory reset. The process completed ok but I'm still having the freeze reboot problem.
Related
So my motorola mb300/backflip is really messed up and old so i stopped using it but yesterday i "rediscovered" it I succesfully used RSD to fix it then rooted and installed cm7 but then my battery got low and my phone wouldn't charge?! Eventually it died, and when I tried to boot it would get half way then die and restart, i could only get succesfully to j_r0dd's recovery so i wiped everything and tried reflashing gapps and cm7 it got halfway then, my phone died. Idk if that messed it up but i once again kept boot looping and could only get to j_r0dd's recovery i tried again and died again when verifying package. I just used rsd to restore back to 2.1 and then connected my phone to my wall charger but right when my phone powers up it shows the little spinning circle and says shutting down, it shuts down and then restarts and same thing again and again and again until i unplug it and then it really dies and doesn't even turn on. Any ideas what I could do?
dumgum89 said:
So my motorola mb300/backflip is really messed up and old so i stopped using it but yesterday i "rediscovered" it I succesfully used RSD to fix it then rooted and installed cm7 but then my battery got low and my phone wouldn't charge?! Eventually it died, and when I tried to boot it would get half way then die and restart, i could only get succesfully to j_r0dd's recovery so i wiped everything and tried reflashing gapps and cm7 it got halfway then, my phone died. Idk if that messed it up but i once again kept boot looping and could only get to j_r0dd's recovery i tried again and died again when verifying package. I just used rsd to restore back to 2.1 and then connected my phone to my wall charger but right when my phone powers up it shows the little spinning circle and says shutting down, it shuts down and then restarts and same thing again and again and again until i unplug it and then it really dies and doesn't even turn on. Any ideas what I could do?
Click to expand...
Click to collapse
Hey!! How are you now? I got my my backflip in "boot looping" situation. ME:rooted and installed cm7 but then my battery got low and my phone wouldn't charge?! Eventually it died, and when I tried to boot it would get half way then die and restart, i could only get succesfully to j_r0dd's recovery so i wiped everything and tried reflashing gapps and cm7 it got halfway then, my phone died. Idk if that messed it up but i once again kept boot looping and could only get to j_r0dd's recovery i tried again and died again when verifying package.
solutions?
dumgum89 said:
So my motorola mb300/backflip is really messed up and old so i stopped using it but yesterday i "rediscovered" it I succesfully used RSD to fix it then rooted and installed cm7 but then my battery got low and my phone wouldn't charge?! Eventually it died, and when I tried to boot it would get half way then die and restart, i could only get succesfully to j_r0dd's recovery so i wiped everything and tried reflashing gapps and cm7 it got halfway then, my phone died. Idk if that messed it up but i once again kept boot looping and could only get to j_r0dd's recovery i tried again and died again when verifying package. I just used rsd to restore back to 2.1 and then connected my phone to my wall charger but right when my phone powers up it shows the little spinning circle and says shutting down, it shuts down and then restarts and same thing again and again and again until i unplug it and then it really dies and doesn't even turn on. Any ideas what I could do?
Click to expand...
Click to collapse
I have successfully rooted and flashed the phone to Android2.3.7.
Anyone needs help can pm me~:silly:
NokiaBigS said:
I have successfully rooted and flashed the phone to Android2.3.7.
Anyone needs help can pm me~:silly:
Click to expand...
Click to collapse
Hi.are you have Solution???
Enviado desde mi LG-E987 usando Tapatalk 2
Hello.
I have a i9100 smartphone with stock XWLSW firmware. After last change of firmware I did not even root it. So it was all stock without root.
My battery was already in bad condition - from 9 AM till 2-4 PM it gets to 15%.
But anyway.
Yesterday it discharged to 1%, when I plugged charger into the phone. I left it working, and after a while I tried to turn the screen on, but the phone was not responding to power key. It was not turning on the screen, and long hold did not turn the phone on.
I unplugged the charger, took out battery and saw a small wet spot on sticker and on battery (maybe it leaked a bit).
Well, it was not the first priority at the moment, so I just wiped it, and put the battery back, then I turned the phone back ON.
It started, but now I have a boot loop at Samsung Logo. When the battery was still discharged I could hear the discharge signal after logo, and then the logo starts again, and discharge signal again, etc.
I left it in that state for a night with charger plugged in. In the morning - it was in the same condition.
Things I tried:
Removing battery for over 10 minutes, clearing Cache from recovery.
Both recovery and download modes are working.
So the question is - can I restore the phone without Factory reset?
If not - can I somehow backup my data (savegames, etc) before doing factory reset?
I just tried to update the firmware again using ODIN with no luck. It updated successfully, but than again hangs on Samsung Logo.
Rule 1: Don't complain until you haven't tried factory reset.So be a man,and do a full wipe.
^^^^
What he said. Also, flash a 3 part firmware, which will also wipe your phone & has a funny habit of fixing situations like this.
I was going to do a Factory Reset or flash 3 part firmware, but only after I backup data. That was my main point of creating this thread - how to backup data in this situation.
Anyway, I did install Philz kernel, wiped dalvik cache, cache partition - it helped, but not for long. I saw my desktop, but after few seconds it went into boot loop again. I then did a Custom backup of data only, and did a Factory Reset through recovery.
Now I try to restore data to see what it will give me.
So i have been having pretty much the same problem with some little differences.
First my battery seems OK, no leaking no nothing, but it might just got old as I've got the phone for over 2 years now... Second, my bootloop occurs after full discharge, when i try to turn on the phone afterwards it just gets stuck on Galaxy SII logo, not even the boot, and stays that way no matter how long i wait. Third, at about the last 5-8% my screen starts flickering as if it wasn't getting enough electricity which shouldnt happen too and never happend before 4 months or so.
So lastly I've been getting this bootloop every now and then. Ive got a temporary fix by backing up my phone through recovery then wiping it clean and then restoring. But i just cant figure out why it does that.... I mean wipe helps, but i do restore everything afterwards....
Without restoring the problem still occurs so its not like i restore something deffective in the sw that makes this happen...
Hello,
I rooted my S2 some time back with no problems and removed some Samsung bloatware. I did not install a custom ROM but did use Triangle Away to remove the start up screen. It's rooted with the Siyah Kernel
My issue is not with boot hanging, but hanging after starting,
My phone used to hang every now and then (twice a week) and a simple battery pull would solve the problem. Pull battery, reboot and it's fine.
Today, my battery ran out, and I placed it in charge and removed the phone after charging. My phone starts up fine, gets pass the Samsung logo, Siyah logo and I get my home screen. Here is where the problem starts.
I get the usual start up notifications e.g. "preparing USB storage", "power saving mode enabled" etc. I can then use the phone for roughly 4 seconds before it freezes. The touch screen does not respond. It freezes. The only thing that does work is pressing the home key 4 times to get negative colours. Apart from that, nothing. If I press the sleep button, the screen goes black and the phone is off. I restart and I get the same problem all over again.
TLDR: Rooted phone, hangs at homescreen upon boot, no custom ROM, battery pull doesn't work
Any help would be much appreciated!
ampeme12 said:
Hello,
I rooted my S2 some time back with no problems and removed some Samsung bloatware. I did not install a custom ROM but did use Triangle Away to remove the start up screen. It's rooted with the Siyah Kernel
My issue is not with boot hanging, but hanging after starting,
My phone used to hang every now and then (twice a week) and a simple battery pull would solve the problem. Pull battery, reboot and it's fine.
Today, my battery ran out, and I placed it in charge and removed the phone after charging. My phone starts up fine, gets pass the Samsung logo, Siyah logo and I get my home screen. Here is where the problem starts.
I get the usual start up notifications e.g. "preparing USB storage", "power saving mode enabled" etc. I can then use the phone for roughly 4 seconds before it freezes. The touch screen does not respond. It freezes. The only thing that does work is pressing the home key 4 times to get negative colours. Apart from that, nothing. If I press the sleep button, the screen goes black and the phone is off. I restart and I get the same problem all over again.
TLDR: Rooted phone, hangs at homescreen upon boot, no custom ROM, battery pull doesn't work
Any help would be much appreciated!
Click to expand...
Click to collapse
Tried wiping cache and dalvik cache in recovery?
Christiaan91 said:
Tried wiping cache and dalvik cache in recovery?
Click to expand...
Click to collapse
Haven't tried that but I will give it a go mate
The phone is rooted and has a few Xposed modules installed; stock ROM.
I shut the phone down every night. When I wake up and turn it on, every now and again it gets into an infinite boot - not a bootloop (at least not in my understanding). It either stays on the LG logo or the Tmobile logo. Sometimes it boots just fine and quick, sometimes takes a minute longer. Other times I have to hold the Power + Volume Down for a few seconds to reboot it, and it boots fine after that. Yet other times, I have to get into the Factory Reset mode and rebuild the Dalvik cache form within TWRP, after which it boots fine.
The weird thing is that when nothing is changed from the moment it loops to the moment it boots fine; it may only be a reboot away. Granted, I do have (quite) a few things frozen and/or removed in Titanium Backup, but should it affect the boot?
Has anyone experienced anything like that?
Attached are the warnings and errors captured while LiveBoot was running. The lines go really fast, and Nexus 5 shutter isn't capable of going that quick (that's why you can see double lines in certain places). The phone booted after I switched to my swap battery.
Just an update, I restored the earliest Nandroid backup and instead of uninstalling these apps, I froze them in TB. No boot issues so far.
Another update. This morning the problem seems to be back, it was stuck on the T-Mobile logo. Although I can rebuild the cache, it's worse now, because I haven't disabled any LG or system apps since the last restore.
Update to this update: after the T-Mobile logo reboot, it now stuck again on the LG logo and took two 5-minute waits before reboots; it booted fine on the third (essentially, the fourth) reboot upon swapping the battery.
Does anyone else experience this?
I have a RN5p which I bought from China. It was running the global ROM.
I bought it 3 months ago and until now it was working fine.
Yesterday I turned on USB debugging and tried to install ADB, but all I got was "ABD is not a recognized command" on my PC and then I assumed there was some issue with my PC and I unplugged my phone and turned off USB debugging (I used this method: https://www.xda-developers.com/insta...s-macos-linux/ and I never managed to get past step 4 cause powershell was screwing me over).
6-8 hrs later my phone's screen froze and I had to force reboot it (hold pwr button for 10s). Once it restarted it was working fine, but then it froze again, and this time it started to boot loop, never getting past the MI logo, sometimes the android with the 3 dots would show, but it usually just remains there or freezes and then reboots.
After like 15 reboots, I managed to reach the lock screen and unlock the phone and worked fine for 30 mins then froze again.
It took even more reboots this time to get it to boot but same thing, froze after sometime.
Now sometimes it doesn't even manage to get past the lock screen, just freezes and reboots.
Additional Notes: I highly doubt that this boot loop is bcoz of ADB as I never installed it on my phone
I checked online and my phone is running the offical international rom(checked on the mi website)
My bootloader is locked( tho I did unlock the oem unlocking setting for 5 secs just to see what happened and then locked it again, but this was at least 6 weeks ago)
Out of the 4 times I managed to get my phone running normally, it froze 2 times while I was watching Youtube and 2 times while it was locked
Running miui 10.0
I would love to have my phone back to normal
All help is appreciated.
It just turned on (while I was typing this) and I allowed OEM unlocking. I think it will be easier this way. And now its back to boot looping.