I have the 20141207 nightly installed and my phone now will automatically crash when i unlock it. An error report will come up but I have less than a second to look at it before everything crashes and it goes back to the lock screen. I cant access any of my files or data to backup. I can only see the error message for a second but its a null pointer exception coming from android.telephony.smsmessage.getO... (i cant read the rest) then from android.provider.Telephony.$Sms$In... ( again cant see the rest). There has to be something I can do to at least get my data off of it. Restarting the phone does nothing. The phone worked perfectly fine before that and I just randomly unlocked it and it started this.
Related
My phone has crashed and I can't get it to start working again.
Its booting up, but then it gets to a certain point and then nearly every single android service has an error and needs to be force closed.
I'm trying to connect it to Samsung Kies but its not connecting.
Can anyone tell me what's gone wrong and how to fix it? I'm running the stock ROM.
I've had Cyanogenmod 9 nightlies on my SGS2 since April. I didn't install every single one, but pretty much only those with good ratings, specifically those that had no complains about battery drain and heating...
Currently on the 06-28-2012 nightly. This ran fine at first, but over time, it started to occasionally crash into Kernel Panic. I figured I'd just pick a new nightly, but then I ended up having to travel and installation of a new nightly got delayed.
Now I'm home, and I can't use the phone at all, cause it crashes into Kernel Panic almost as soon as I unlock the screen after Android finishes booting. The last thing I see up in the message bar is "WhatsApp error" and the screen goes dark. It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
I don't think its a problem with WhatsApp, cause WhatsApp used to run fine, while Kernel Panics originally mainly seemed to happen after I got a "storage full" message. In response, I deleted a load of pictures after rebooting, to make sure there's free space, but it kept crashing occasionally, till now, its just unusable.
I've tried to flash a stock Samsung ROM (I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar.md5) but that hasn't been working either.
Kies drivers are installed on my Laptop. Odin sees the phone too.
I followed the instructions from the rom page, changed no settings in Odin, just picked PDA and selected the ROM.
Odin goes "Added" when I plug in the phone, verifies the ROM, then the whole thing hangs on "setting up connection"
So I unplug, pull the battery and then reboot, which works fine, but once booted, it won't stay on longer than a few seconds.
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Tsais said:
It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
<snip>
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Click to expand...
Click to collapse
What's preventing you from factory resetting from recovery?
Lack of knowledge is preventing me!
How do you factory reset from the "Kernel Panic Download Mode"...?
Download Android Commander from here:
http://androidcommander.com/
Boot your phone, don't unlock.
Start Android Commander, navigate to /data/apps and delete WhatsApp's apk (com.whatsapp1.apk or something like that) or rename it to .apk.bak
Restart your phone without unlocking.
Hope the errors gone.
I hope this is the best place to post this. If not, I am very sorry. I have found a few posts with same message BUT all of them I found were when this happens after installing a rom or updating, etc...
I have a Virgin s2. I just have original stock rom, Ive done nothing at all to it. I changed out my batteries, turned it on, then after it got loaded I got a popup saying "unfortunately the process com.android.phone has stopped"! I restarted then as soon as i tried to do something, i received it again. I restarted again & didnt get message til I had opened google & was waiting for search results to come up when I got message saying something about couldnt find a mobile network (or something like that), then got the "unfortunately the process....." popup. It started popping up over & over, including when I got a phone call (which made it impossible to answer, however I was able to call them back okay). I have already tried:
taking out the sdcard;
booting into recovery then wiping the cache partition;
booting into safe mode.
The popup &problem still continued. Oddly, after my husband ran "CM Security" though it found no problems, it was a little bit before it did it again and even now it doesnt popup quite as often as it had been but it still is enough to probably make the day at work very aggravating lol.
Please say theres still some hope! I'm not able to buy another phone right now. I am capable of doing anything possible to save it if you just tell me what would be best to do. I saw somewhere when I searched Google say that installing a custom recovery would probably fix it. If so, please point me to where I can find all the necessary things &instructions I need. Or if it would be better to do a factory reset, please tell me how to do it on this phone (or if I just need to go to recovery & simply do it).
ALSO I do have an identical s2 except it is Sprint & I havent came across a detailed guide for flashing the s2 from Sprint to Virgin that doesnt require the newest paid version of cdma workship, which i cannot currently afford.
Thank you for your time & assistance.
FIXED (at least so far)!
SOLVED!!! (I hope:fingers-crossed
Went ahead & just backed up contacts to sd card, then did a Reset through Recovery. So far no "Unfortunately the process com.android.phone has stopped" message. :highfive:
gdownloads said:
SOLVED!!! (I hope:fingers-crossed
Went ahead & just backed up contacts to sd card, then did a Reset through Recovery. So far no "Unfortunately the process com.android.phone has stopped" message. :highfive:
Click to expand...
Click to collapse
Great to hear you fixed (or partially fixed) your problem. The problem with updating stock roms using OTA or kies is that sometimes a factory reset or clearing the cache is required to remove some left over apps or unneeded files that might potentially make your phone give errors (like the ones you were experiencing). It is highly unlikely it is a software issue, unless it was a dodgy download, moreover unfinished file deletion or unneeded files would have caused this to happen.
Yesterday I updated a nightly build (cm-13.0-20151222-NIGHTLY-mako.zip) and unfortunately the phone began to show a series of problems (ouldn't make calls,couldn't access the contacts,...).
Reading on the internet i found many people suggesting to downgrade to a working build, so i downloaded the last one that was working on my phone (3 days earlier 12/19): the nightmare began!
After the boot, the phone (nexus 4) shows repeatedly "Unfortunately the process com.android.phone has stopped" and when i click on "ok" it just pops up again and again, until it automatically reboots, and the whole thing goes on for ever.
If i don't touch the phone it reboots automatically until the batteries are completely dead.
I have tried to adb push from bootloader but the terminal (from ubuntu) hangs there without signs of life. If i open nautilus and I try to copy the new build, my ubuntu freezes, only the mouse works without any use.
Is there a way to miraculously solve this problem?
shared_joy said:
Yesterday I updated a nightly build (cm-13.0-20151222-NIGHTLY-mako.zip) and unfortunately the phone began to show a series of problems (ouldn't make calls,couldn't access the contacts,...).
Reading on the internet i found many people suggesting to downgrade to a working build, so i downloaded the last one that was working on my phone (3 days earlier 12/19): the nightmare began!
After the boot, the phone (nexus 4) shows repeatedly "Unfortunately the process com.android.phone has stopped" and when i click on "ok" it just pops up again and again, until it automatically reboots, and the whole thing goes on for ever.
If i don't touch the phone it reboots automatically until the batteries are completely dead.
I have tried to adb push from bootloader but the terminal (from ubuntu) hangs there without signs of life. If i open nautilus and I try to copy the new build, my ubuntu freezes, only the mouse works without any use.
Is there a way to miraculously solve this problem?
Click to expand...
Click to collapse
use fastboot to manually flash the stock partitions, then it will be clean stock, and you can start over.
search google for how to setup fastboot on your linux machine if you dont know how, i cant help with that.
So I bought a new Poco F1 few days ago. And since I've been using it, I've been facing bugs.
So when I got the device it had Miui 9.6.14 installed on it. And I just wanted to unlock it and root it asap. As you know you have to wait 3 days to unlock it. But as soon as I put in the unlock request i.e by going to fastboot and on mi unlock it shows 99% complete then it says you have to wait for this much time.
As soon as I did that, I faced the first bug. That was related mobile network settings/usb tethering/*#*#4636#*#* code (engineering mode IDK). So when I clicked on usb tethering, turned off mobile data/wifi, or the phone lost signal, it rebooted, from boot splash (not boot logo). Maybe this was the ROM's way of preventing any big bugs why do I think that? I'll explain later. So after rebooting I could turn on/off usb tethering but not mobile data or wifi. I can turn them off as soon as the phone boots but if I do it later i.e. after unlocking the phone, it rebooted.
So this is one of the bugs that has been consistent, the one that never got away. Well sometimes it did went away but not for long. Like sometimes if I haven't turned off the internet in a long time or restarted the phone properly, the data turning on/off doesn't reboots the device, IF the device isn't connected in usb tethering. Like few days ago I discovered that usb debugging could fixed it, but that didn't lasted long either. Sometimes turning off usb tethering then mobile data very quickly afterwards worked, but didn't lasted long or only sometimes it would work.
So the advice I got earlier was that, just flash a new software. While I didn't technically flashed the new software, I flashed the similar software, deleting all user data & everything, but that didn't helped. As it seemed in the beginning, that bugs weren't there but they started appearing later on. Now IDK if I used a locked un-rooted device, these bugs wouldn't appear, not too sure about that.
And you maybe saying, well you didn't flashed the newer version of the rom, then that's the problem, Well IMO it isn't. Here's why - So when I flashed the same rom, the phone got locked cause I forgot to select the "clean all" option in MI flash instead of "clean all and lock". So I unlocked it again, flashed twrp and as you may know that when booting twrp for the first time it asks you two options, "allow system modifications" & "read only". And the last time I flashed it I chose the read only option. But this time it didn't asked me. Now do you understand? As I'm not an expert in this, the guy who gave me this solution said maybe the device tree wasn't cleared. So how does flashing a new version is gonna make a difference if all of the files don't get deleted? If it's not gonna start fresh? I also used the command "fastboot erase recovery" (as suggested by that fella), that didn't helped either, just an FYI.
So I decided to install other roms, thinking maybe that could help. It seemed like working in the beginning but soon it started to fall down. First OS I installed, Pixel Experience, didn't had such bugs earlier, but there was a little one. If I disconnected the phone while it was in usb tethering mode, it would reboot the same way it did with miui. If you turned usb-teth off first, it didn't rebooted. So I thought I could live with that. But later more bugs started to appear. The same thing, turn off the internet and the phone restarts.
Remember when I first said maybe it was OS's way of not having bigger bugs, So that happened this time. New bugs like when I try to get into an app's info, the settings would crash (stopped working). BTW you could getting into an app's info if you are able to find the said app, by going into storage, then to apps. Moreover sometimes when I'd try to open the camera it would just show blank, or very dark image of the environment, not moving though, and sometimes, it would just work.
Then I installed Lineage OS. Didn't find such bugs, but I'm pretty sure if I do all this usb tethering stuff in there as well, I'm gonna find these bugs.
Now you might be thinking that how am I installing all these roms, well that's cause of MultiROM. And if anyone here is gonna say well that's the problem. STOP! Stop right there. These bugs were present there before I even used MultiROM.
Some other bugs I'm facing RN in Miui -
Auto Rotate not working. If I want to go landscape, I'd have to open an app/game that opens in landscape and switch from there, cause it gets stuck, vice versa for portrait. And you can only view it in default position i.e. you can't rotate to other landscape position if you wanted.
Camera not working, showing "can't connect to camera" error.
When I play offline games while these bugs occur. When I connect the headphones, the audio also comes out of the speakers. After I restart the phone properly, that stops. (This bug was also present in earlier stages when MultiROM wasn't used)
When going into second space, I created a txt file in mixplorer and when I try to open it, the system reboots. And I just checked by installing a root checker in second space, it says not rooted, wow!
When going to default file manager and tapping on storage, it said "disconnected" and few seconds later saying something like "couldn't add error 10000". This used to happen before but not now, neither I use the default file manager anymore. Though if I'm too quick and unlock the phone, open a file manager or any app that uses storage, it would go blank. Don't know if the storage crashes or something else. But after a restart, it's fine.
One thing, after the phone restarts when these bugs happen, "Find My Device stopped working" or something similar always appear, I don't remember the exact message.
[*]There are somethings Gcam related but I don't think they're 100% bugs related. Cause I installed the latest version on Lineage OS and it works as far as I used it even features like Night Sight and Slo Motion. Now those errors could be related to older android versions or something else IDK. Things like camera lagging in picture mode not in video mode and some version just straight up not working even when they're supported by older android 8.1.
Now could it be a hardware problem, IDK as I said I'm not an expert. These other bugs could've appeared cause of MultiROM or me flashing a new firmware over older rom version in order to install PE, again IDK.
Fair warning : If you're just gonna come here and say, Oh! this all cause of MultiROM or cause you didn't installed newer miui, then don't waste your time, cause I'm not gonna read any arrogant answers. Neither if you say, try to do this or that. I'm not here for that either. Cause if I wanted to do hit and trial, I could've done it myself
But if you understand the situation and can provide expert help, then only please reply. So if you're willing to help & understand properly, and you want anything from me, like logs etc. just tell me how to do it, I'll provide. Or if you know some way to do proper fresh install, only if that can fix the bugs so that I don't have to deal with them anymore, I'm looking forward to your reply.