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.
Related
Installed Cyanogen 6.1.1 and GApps yesterday (wiped cache partition, Dalvik cache and battery stats before installing). Was working great all night and most of today. Much faster, not crashing like the JIT was causing my phone to do.
This afternoon the battery seemed to be charging slowly so I restarted the phone. The phone kept getting stuck in the boot screen (with the blue android on a skateboard). I took the battery out and tried again. Same thing happened about 4 times, then finally it went through and started the phone. However, everything started crashing one by one when i got into my phone (force close) and I wasn't able to do anything. I had to pull the battery out again to restart.
It seems to be a toss up now, it either gets stuck in a boot loop or it starts up and everything crashes. I can't even get into XRecovery for some reason so I can't wipe to factory defaults. Seems like the phone is wrote off.
Is there anything I can do? Any help would be appreciated as I am lost without this phone.
Hello xda!
Well, I have a problem, yesterday my phone was working great, but today when I woke up, I found my phone in the CM9 boot screen and it never pass through it. Sometime during the night I woke up and checked the time with the phone and everything was FC'ing, calendar, contacts, and many other system and non-system app were crashing, then I rebooted to fix that crazyness and here I am, stuck in the boot screen. :/
I don't know what's wrong, yesterday everything was fine! I did not fiddle with anything this night! Did I sleepwalk?
The phone is a SGS2 i9100 with CM 9.1 (and the boot animation of CM10).
So far, I tried wiping the dalvik cache, but I'm still stuck. I hope we can fix this without having to wipe everything... It was long ago since I did the last backup.
You could try a dirty flash of whatever CM9 build you're currently running without wiping. To be honest though, this probably won't work (but it won't make things 'worse'). Then try a wipe. And if none of that works, back to stock via Odin & either restore your backup or start from scratch (re-flash whatever rom/kernel you want, restore your apps & contacts, etc, etc).
But what it puzzles me is what happened tonight that the SO broke.
And the upper part of the phone, around the camera (where the main board is placed) gets extremely hot, I even left the phone 5 minutes in the refrigerator stuck at the boot screen to see if waiting long enough would do something, but it didn't.
I guess I'll try doing what you said, and if that doesn't work I'll start from scrath. Anyway I wanted to update to JB. I'll lose some pulled apps from the Play Store but... meh
Could be something hardware on the fritz, or the heat could be related to the firmware problems you're seeing. Don't put the phone in the fridge; fridges tend to be a bit moist, you don't want to expose the phone to moisture like that.
I guess you'll find out if it's hardware or not when you fix it; if the heating issue remains once you've got it running 'normally', then there might well be something hardware-related going on.
pealery ito
Deses said:
Hello xda!
Well, I have a problem, yesterday my phone was working great, but today when I woke up, I found my phone in the CM9 boot screen and it never pass through it. Sometime during the night I woke up and checked the time with the phone and everything was FC'ing, calendar, contacts, and many other system and non-system app were crashing, then I rebooted to fix that crazyness and here I am, stuck in the boot screen. :/
I don't know what's wrong, yesterday everything was fine! I did not fiddle with anything this night! Did I sleepwalk?
The phone is a SGS2 i9100 with CM 9.1 (and the boot animation of CM10).
So far, I tried wiping the dalvik cache, but I'm still stuck. I hope we can fix this without having to wipe everything... It was long ago since I did the last backup.
Click to expand...
Click to collapse
Just try to flash CM9 again without wiping data, wipe only cache partition and dalvik cache, you will not lose data.
I tried reflashing CM9.1, but it's still not working... I'm starting to get worried.
This night I will try to flash a stock rom with odin and wipe everything. And if that don't works... well, damn.
I did say it probably wouldn't work. You're getting in a tizz over nothing, to be honest. You're acting as if your phone's busted (it isn't). Go back to stock & start from there.
Man, I guess it's normal to get a little worried when your phone doesn't get through the boot if I didn't do anything to it... but I wasn't THAT desperate, I was pretty sure it was something software related. Sorry if I gave that impression. D:
I just tried to load a backup that I did back in January and the phone booted, so I guess my only option is start from scratch (and leave my phone far away from me during night).
Thanks for the help!
You are not the 1st person for things going "bump in the night",and you wont be the last.
Seems mostly to happen when cm10 is mentioned.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
I'm hoping someone on here can help me. I've had a few lingering issues that I can't seem to resolve. I run AOKP, but at this point, I may go completely back to stock to see if the issues resolve.
- The main issue is the random freezes on boot. It is really random, but definitely has gotten worse over the past few months. Basically, the phone freezes at the first boot screen about 60-75% of the times I reboot. I've had to pull the battery sometimes once (if I'm lucky), and sometimes 3-4x, just to get it to boot past the Samsung screen. This is compounded by the second issue I'm having:
- Loss of data. Actually, more specifically, it is data not coming back when I leave a no-signal area. I live in a no-signal area and depend on a VZW home tower. I don't get a solid signal until about 2 miles out from my house, just after I leave the neighborhood. After I clear the area, I get a strong cell signal, but data never becomes available. Toggling mobile data or cycling airplane mode does not resolve it. I have to reboot, which can bring me to the stuck boot screen, where I'm pulling my battery to get back up and running (often when I'm driving... which really sucks).
This weekend, I wiped the phone as fully as I could. I don't believe I restored it completely to stock, as the phone still showed the unlocked icon when booting. I did, however, restore the phone to the stock MDK ROM, re-rooted, reinstalled TWRP (through GooManager), and reinstall the 11/14 AOKP ROM. It did not seem to help.
Shortly after wiping the phone, I was 99% sure I had figured out the boot issue. For some reason, I got the idea to pop out my sdcard while it was stuck at the boot screen. As soon as I popped the card out, it moved past the Samsung screen and changed to the Google "X". The card was a SanDisk Ultra 32GB, which some people have had dismounting issues with, so I thought I hit the jackpot. I tested it several times, and as soon as I popped the card out, it would start booting each time.
I was excited when I hit the road this morning. Unfortunately, the data bugged hit me as soon as I got out of the neighborhood. As before, I had to reboot to get it back. That is when it stuck on boot again. I did not have an sdcard in, though. It took for cycles of pulling the battery before I finally booted up.
I'm stuck. I really don't know what else to do. I've tried every ROM/radio/kernel combination out there, except for bone stock. I used a combination of different guides to get as close to stock as I could, but I still didn't get there. I'm sure I missed something, but I'm not sure what. The steps I took to restore are below.
Is there a PIT file I can use to repartition the phone? I know that is frowned upon unless the phone is completely bricked, but I don't know what else to try. Just from experience, I'd doubt it's a hardware issue... but who knows:
Steps I took to "restore" phone:
- Flashed SCH-I545_MDK_562219_Stock_Restore.tar.md5 in Odin
- Rebooted, then went back to Odin to install MD2 kernel
- Booted into stock ROM, enabled dev options, USB debugging, etc...
- Rooted, rebooted, installed GooManager
- Installed TWRP through GooManager
- Installed 11/14 AOKP, gapps, faux 0123m, and MJ7 radio
Hi everybody, I have a problem and I don't know what to do, so I'm hoping I can get some help with this.
I bought a used cheap tablet off ebay a few months ago. It looked new and came with everything, but its always had software issues. It would be working fine then it would get infinite errors saying various android processes have stopped, it would automatically close apps when I tried to run them, and would prevent me from even changing the settings. This was a frequent problem which I solved by doing a factory reset. This was practically an everyday occurrence until I learned to clear the cache several times a day, which gave me probably around 5 to 7 days before I would have to reset it.
Well, the other day my tablet froze up and wasn't responding. I left it for a long time with no change. I turned it off and rebooted and was greeted by the infinite error problem. I turned it off and cleared the cache from the recovery menu. I tried to boot the tablet and it got stuck at the shiny android logo and won't go past that point. It won't boot into safe mode either.
I tried to do a factory reset like I've done countless times. As soon as I tell it to do the factory reset it says...
-- Wiping data...
Formatting /data...
and.. it does nothing. It never finishes or gets past this point. Not knowing what to do I've turned it off and tried again, I've tried rebooting it but it still won't go past the android logo. I've tried just letting it sit while supposedly "formatting" but that didn't do any good either. Has anyone else encountered this problem before?
I've been trying to figure out how to fix it as I'm broke and can't just go buy another tablet. I'm assuming my only option at this point is to flash a rom, but does it need to be rooted in order to do that? Can I even flash a rom when the tablet won't even do a factory reset and format the data?
Any ideas?
Thanks in advance.
Hello guys,
So, i have rooted my Device (BQ M5) 1 Month ago and installed Xposed on it. Everything was fine until yesterday, where i was underway and streaming via Chrome a video. I didn't close Chrome and simply locked my phone. Several minutes later, when I tried to unlock my phone, i directly noticed heavy lag (response 2seconds - 2min - locks device). I thought a reboot might solve this issue, but i was wrong. I started to uninstall several previously installed apps and tweaks (where the newest App/Tweak was 8 days "young".
After a reboot, still heavy lagging. I opened TWRP and Cleared Dalvik and Cache, did a reboot in System, Recovery and Bootloader. I even flashed the device with a complete fresh OS. The problem still remains. After several re-flashings, some cache clear, factory resets and SuperSu unrootement i somehow managed to get it to work again. So I started from 0 again, and installed all previous apps, and root apps. Everything was fine for several hours (connected to Wi-Fi), so i was installing Xposed again, with 2 apps/tweaks: Flat Style bar, youtube adaway. Everything was still allright untill i left the house. I unlocked my device 50min later (for the first time when i left my house) and boom, the lagging was back. (Don't have internet outside my house).
As soon as i came back, i retried everything to remove the lag, however I did now several things in addition for over 3h and the lagging sill remains. I down and upgraded the OS, formatted the data, did every clear in TWRP and Bootloaded that i could find. I reset it via Settings and flashing. I installed SuperSu and de-installed it.
I don't know what else i could do, to solve this issue. The lag remains when using TWRP, Bootloader, using the Device, or when the Booting animation of android appears (slow animation or with a "fps of 0,05").
Please help me!
Device: BQ M5
Had Android 5.1.1. on it and Installed xposed sdk22 arm, and installed SuperSu via TWRP.
All files were downloaded from official posts here on xda, or from the brands website.
p.s. Even the littlest information which could help, please share!
p.p.s Here's a video that shows whats going wrong. After the reboot the booting animation continues like this around 1-3min. and then at the unlock screen, the "lag" still remains. What i noticed too, is that the charging animation in the top right is running flawlessly, however opening apps and all the rest is really slow!
youtube(dot)com/watch?v=Htuhj8UzWs4