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.
Related
I flashed CM 10.1 nightly 031313 with no problems. I've been using it for several days now and after using Google Maps navigation, I put my X912 in my pocket. I take it out and it's shut off. Try to turn it back on, safestrap, continue, then black screen but backlight is on. A sudden vibration and then the backlight turns off, then on and just sits there.
I wasn't doing anything special with the ROM like updating or anything. It just "broke" in my pocket. Tried a cache and dalvik wipe. Reinstall. Nothing.
Short of wiping that ROM Slot and starting over, any ideas?
cschuck320 said:
I flashed CM 10.1 nightly 031313 with no problems. I've been using it for several days now and after using Google Maps navigation, I put my X912 in my pocket. I take it out and it's shut off. Try to turn it back on, safestrap, continue, then black screen but backlight is on. A sudden vibration and then the backlight turns off, then on and just sits there.
I wasn't doing anything special with the ROM like updating or anything. It just "broke" in my pocket. Tried a cache and dalvik wipe. Reinstall. Nothing.
Short of wiping that ROM Slot and starting over, any ideas?
Click to expand...
Click to collapse
kernel problem
flash a new kernel and the latest one of your choice
maybe this will solve ur problem(try to find the kernel in the dev section)if still it causes problem then ask
Hi guys, I was using my phone messaging my friends. I put the phone down for about half an hour. When I pick it up again it is hot and will boot to the glowing slimbean logo (boot animation). I assume the phone ran out of battery, but even when I plug it in it will not boot past the logo. Do you guys have any idea as to what is going on, and how I can get my phone working again?
Try booting to recovery and wiping dalvik (hold both volume keys, plus power at the same time - release all after the Samsung logo appears). Phones don't usually freak out like this unless there's something the user either did or installed, especially those running stable slim roms.
On another note, the version you're running is very outdated; have you considered installing the last i777 slim rom, based on 4.2.2 (8.1)?
SteveMurphy said:
Try booting to recovery and wiping dalvik (hold both volume keys, plus power at the same time - release all after the Samsung logo appears). Phones don't usually freak out like this unless there's something the user either did or installed, especially those running stable slim roms.
On another note, the version you're running is very outdated; have you considered installing the last i777 slim rom, based on 4.2.2 (8.1)?
Click to expand...
Click to collapse
Thanks for your reply Steve!!
The reason why I'm still using 7.1 is because I was having battery problems on 8.0. I wasn't sure if the bug I had was fixed so I decided to stay behind. This was probably not the best choice but convenience and stability were something I wanted. I will try 8.1 after I backup my current setup if it works.
I believe its Google Now that has been causing me problems. Ever since I started using it my battery drains much faster, and the phone is hotter than usual. If wiping the cache works then I will delete it , otherwise I will probably have to wipe to factory which I really don't want to do.
OK so wiping the dalvik cache has allowed my phone to get past the bootloop. I get this message "Android is Upgrading.. starting apps" and its been stuck on it for a while. Any ideas?
This is weird, don't really know why - out of nowhere - your rom just all of a sudden won't boot.
And yes Google Now will kill ANY battery!
One other method would be to dirty flash 7.1 without doing any more wiping, if you want to keep it. If that doesn't work, full wipe/format system and start over.
Hope you get it working again!
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
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.
Hello. I have a boot loop issue with my SM-G850F. It happens immediately after camera launching, boot loop can last for minutes, but eventually the phone turns on and works alright except camera. Sometimes camera may work fine for some time but later it goes to boot loop again. Also if i restart my phone manually it also goes to boot loop. I tried to reflash it using Odin, different firmwares, home and factory, Kitkat and Lollipop, i did it with data and cache wiping from recovery every time. When Odin finishes it's job and a phone tries to reboot after reflashing - here boot loop starts again. But when i reflashed 4.4.4 and got a Lollipop OTA update, my phone got back to life, camera worked fine, it restarted fine with no boot loop anymore. But after about 6 months it happened again. The same situation, wiping didn't help, reflashing didn't help, and again reflashing 4.4.4 + OTA update did help, i don't know for how long. What may be the reason? I assume it's not a camera problem, OTA update shouldn't fix it, and it's not a battery for the same reason. What do you think?
ThorosPWNZ said:
Hello. I have a boot loop issue with my SM-G850F. It happens immediately after camera launching, boot loop can last for minutes, but eventually the phone turns on and works alright except camera. Sometimes camera may work fine for some time but later it goes to boot loop again. Also if i restart my phone manually it also goes to boot loop. I tried to reflash it using Odin, different firmwares, home and factory, Kitkat and Lollipop, i did it with data and cache wiping from recovery every time. When Odin finishes it's job and a phone tries to reboot after reflashing - here boot loop starts again. But when i reflashed 4.4.4 and got a Lollipop OTA update, my phone got back to life, camera worked fine, it restarted fine with no boot loop anymore. But after about 6 months it happened again. The same situation, wiping didn't help, reflashing didn't help, and again reflashing 4.4.4 + OTA update did help, i don't know for how long. What may be the reason? I assume it's not a camera problem, OTA update shouldn't fix it, and it's not a battery for the same reason. What do you think?
Click to expand...
Click to collapse
Maybe a hardware issue? Did you try ozcan or epsil rom? Do you have the same issues on those roms?
BarryPooter said:
Maybe a hardware issue? Did you try ozcan or epsil rom? Do you have the same issues on those roms?
Click to expand...
Click to collapse
After several hard resets the problem has gone, i don't know for how long though. So i have no idea is it a hardware issue or not. May it be a flash memory problem?