I'm facing a very weird issue with bootloops.
I'm running 4.3 stock on a Galaxy s3, rooted with twrp.
I did a battery pull because my phone was playing music in a meeting and I had to quickly disable it (maybe it wasn't such a good idea)
The weird thing now is that my phone boot loops repeatedly on the Samsung logo... But it gets closer and closer to starting up every time.... At some point you see the beginning of the launcher but it reboots again.... At a certain point it finally loads up
I've tried wiping cache and dalvik cache partitions but it does the same (it caches apps, reboots and caches a few more until after 20 min it's as startup)
I'm wondering if there's a good way to run a diagnostic or log to find out what's happening, how about ' adb catlog' ?
If anyone has any other suggestions or advice, I'd appreciate it.
By the way, it's not a hardware issue because when I did a wipe, the problem was gone, so I restored this nandroid backup and the problem persists
Sent from my GT-I9300 using Tapatalk
Related
When i hold power button down reset phone, usually on accident in pocket but when it reboots. It gets stuck at loading screen progress bar 98% done wanna say and never goes to the next screen, will let sit for hour nothing, reboot phone sometimes get the samsung words and just stays their. Tried clear cache dalvik and reg. factory reset, fix permissions, still all same no proper boot. If restore from a backup works otherwise have reflash. Anyone have this issue before and is their a fix when happens so don't loose all texts and info in general.
Try nandroid manager @ playstore to retrieve texts & stuff
Sent from my confused Warp/Nexus using Tapatalk 2
downloaded sms backup auto backup every 3hours.. still wonder why i get that boot issue in end and if its fixable without reflashing or restoring a backup image
I'm running CM 10 on my EVO. I haven't updated it in a while so it's probably 10.1 or something. Random shutdowns would happen for no reasons sometimes when using the new YouTube app. Then yesterday when I turned on Bluetooth, the phone shutdown by itself. When it reboots it says Android is upgrading... and optimizing apps. Then it reboots and gets stuck in a bootloop. I can boot to bootloader and recovery. I've wiped cache, Dalvik cache, and nothing seems to fix it. Sometimes it boots and I can enter my PIN and use the phone for a few seconds until it reboots itself again. Also, there has been discolored streaks near the sides of the screen. When using the phone they're black, but when the screen is booting they're red on top of the black.
Does anyone have experience with such a problem? I want to try fixing this so I can backup my data before I reflash the ROM or anything.
If it's an older CM release that could be part of your problem. I would update to CM 10.2 and see if the problem persists. I'm currently running the 8/24 IRC build and it has been rock solid. If you continue to have issues you may have a hardware problem.
Sent from my EVO using XDA Premium 4 mobile app
Thanks for the reply. I did a wipe/factory reset from recovery after doing a backup. Everything seems to be okay now. I'm flashing CM 10.2 8/30 from the IRC to try it out.
I have a backup of the state when it wasn't booting properly. I was wondering if anyone had a similar problem with the turning on Bluetooth and then the shutting down by itself and bootloop. I want to be able to recover files from that state.
ok,30 minutes ago my gs3 was next to me and I had music on then all of a sudden the ''Samsung Galaxy S III" splash screen appeared.It kept appearing and disappearing so I took the battery out for a while then inserted it and it turned on.5 minutes later the same thing happened and now it is working again but well this might happen again.What could be the problem ? can it be SDS ? but I had my gs3 for a year and a half so I doubt that.I'm running wanamlite 4.1.2,have been using this rom for almost a year.(except for trying out a few other roms sometimes).
Reflash your rom, try first without a wipe.
Sent from my GT-I9300 using Tapatalk
Madarox said:
ok,30 minutes ago my gs3 was next to me and I had music on then all of a sudden the ''Samsung Galaxy S III" splash screen appeared.It kept appearing and disappearing so I took the battery out for a while then inserted it and it turned on.5 minutes later the same thing happened and now it is working again but well this might happen again.What could be the problem ? can it be SDS ? but I had my gs3 for a year and a half so I doubt that.I'm running wanamlite 4.1.2,have been using this rom for almost a year.(except for trying out a few other roms sometimes).
Click to expand...
Click to collapse
You can try this:-
Go to recovery and do factory reset. (You will loose all software installed by you, may b contact & sms too)
Wipe Cache & Dalvik Cache
Tried a factory reset and tried restoring to a an old backup,didn't help.I didn't try reflashing the rom, I doubt it will work because restoring to a backup that was working fine didn't help either.I'm thinking about giving it to samsung,hope they won't blame rooting and custom rom for the problem but I'm out of warranty period anyways.
Try another rom! But with a clean install! don't restore your nadroid backup data, use Titanium Backup for your apps.
I noticed that it happens when I actually use the phone(like for a few minutes) but when it's idle,it operates normally.
I don't have any other roms right now and I can't download any because my internet is limited currently.
UPDATE: It looks like the problem is the power button because when the phone does boot,the boot menu keeps showing up and when I pull the battery and insert it again,it boots automatically.I will get it fixed,thanks all.
Hello!
I am guessing I will have to reinstall but just in case, while trying to play South Park on Firefox yesterday the phone just went into a reboot which was odd.
Then it got stuck on the xperia wall paper trying to restart to I forced it to shutdown and tried wiping dalvik and cache partition even on my 3rd try and even reflashing the Doom kernel and still either gets stuck on the wallpaper or it will show the updating process then after the count down ends, it says updating apps and never changes from there.
I can feel the phone vibrating like it does right before it shows the home screen but it never happens.
So, unless someone knows of a miracle cure, it seems I will be reinstalling tonight.
Right now I am using my Wife's Note 2 with pink case...cool! :laugh:
shaolin95 said:
Hello!
I am guessing I will have to reinstall but just in case, while trying to play South Park on Firefox yesterday the phone just went into a reboot which was odd.
Then it got stuck on the xperia wall paper trying to restart to I forced it to shutdown and tried wiping dalvik and cache partition even on my 3rd try and even reflashing the Doom kernel and still either gets stuck on the wallpaper or it will show the updating process then after the count down ends, it says updating apps and never changes from there.
I can feel the phone vibrating like it does right before it shows the home screen but it never happens.
So, unless someone knows of a miracle cure, it seems I will be reinstalling tonight.
Right now I am using my Wife's Note 2 with pink case...cool! :laugh:
Click to expand...
Click to collapse
boot into recovery
do nandroid back up
wipe /data and caches
reboot
If that was successful restore apps and data using one of the backup managers and reboot before each new app until you find the one that is the problem?
My phone (Nexus 4) appears to be soft-bricked, and will not boot up. When I turn on the device, it appears to get part way through the boot process but it never completes, and the bootsplash just keeps spinning forever. The top of the phone where the radios/gps/etc are gets very hot during this time.
I've tried: clearing caches within TWRP, factory reset, loading a couple new ROMs, wiping all partitions and reformatting, updating TWRP. Nothing seems to help.
I'm starting to think it's a hardware problem, but I'm hoping that someone might be able to give me some ideas that I haven't tried yet. I can get into TWRP and can load ROMs.
Some background: My phone is a Nexus 4 (mako) and had Cyanogenmod 13.1 prior to the issues, which has been running fine since last year. Recently my phone was acting glitchy/slow, so I decided to clear the cache and dalvik cache a couple weeks ago. This worked great and got things working well again. When I set things up again I also decided to start using DroidWall, which was the only app on my phone using root. About a week ago I also replaced the battery inside the phone since my old battery was shot and could barely keep a charge. The new battery has been working well, and does not appear to be the part of the phone heating up when the phone is stuck booting.
An update. I found that with the Slim ROM loaded, I can run `adb logcat` while the phone is booting to see what's happening. Lineage OS does not seem to ever get far enough to be seen by adb.
When viewing the Slim logcat, there are a lot of logs generated. Within, there are some DEBUG and backtraces displayed. And, I think the phone may be stuck trying the same thing over and over again as I've seen a section appear about the camera several times.
Earlier today I opened up my phone again, and noticed some pressure contacts on the back cover of the case. I cleaned them all to make sure they were making good contact, but it hasn't helped.