Hi all,
Not sure if anyone can help.
I have seen loads of posts about the com.android.phone has stopped working problem but none are like what happens to my phone.
I have a rooted note 2 and running jedi x17 rom (4.1.2 based on the standard touchwiz) all works fine no problems.
I want to go to a 4.3 rom like cm/pacman/pa etc but whenever I flash the rom and reboot after 2 min the com.android.phone has stopped comes up, but only once after I reboot, everything works fine and I can get on the Internet and make calls etc, it's just annoying.
I have even gone back to unrooted stock and started again but the problem still happens, any help would be great.
I'm on the EE network in the UK, I was wondering if Apn settings could be a problem.
try after flashing to wipe cache and do a factory reset, see if that works.
Related
So I wanted to flash the new jedi rom on my note2. I was running myrom. Through recovery I wiped the system and then I wiped cached. The usual. I have flashed many roms so I knew what I was doing.
So then I flashed the new jedi rom. And its wasnt working because this kept popping up without even letting me use the phone-> 'android.process.acore has stopped unexpectedly'. And then I was like wth? I flashed back and recovered my previous rom and data and that rom worked just fine again.
So I did some reserch and I came across another forum that claims the fix is to flash SUPERWIPE. So I did so, then I flashed the jedirom again and it was working fine without any popups of any errors.
Then I noticed my wifi would not even turn on at all. I press the botton to turn on, and it says turning on, then it will go back to saying turn on, as if I never tried to turn it on at all. Please help guys as much as u can. Everything else works jist fine on my phone btw.
Tmobile sght889 gnote2
i did a factory data reset as I'm giving my mom my s4 and taking her nexus 4 so after i reset it the wifi stopped working, I've ref lashed cyanogenmod 3 times now none of which works, what i don't get is that wifi was working fine before the reset, does anyone know how to get this working again? thanks in advance
I'm thinking this is an issue with cyanogenmod because i flashed danvdh's 4.4.4 stock based rom and it works fine now, id say CM is fine but there are some problems that still show up every now and then
Hello,
I rooted my M919 and tried a few ROMs to hopefully find one that I liked, but it seems that they all have bugs that make the phone unusable for me. (Flashed a Google Edition rom, the proximity sensor didn't work anymore, so I couldn't end a call, ever).
Now I am trying to flash the stock firmware, and it seemed to have worked, except I get the com.android.phone has stopped, CONSTANTLY. I already have tried clearing data/cache several times, no luck.
Any ideas?
Thanks!
jtleniger said:
Hello,
I rooted my M919 and tried a few ROMs to hopefully find one that I liked, but it seems that they all have bugs that make the phone unusable for me. (Flashed a Google Edition rom, the proximity sensor didn't work anymore, so I couldn't end a call, ever).
Now I am trying to flash the stock firmware, and it seemed to have worked, except I get the com.android.phone has stopped, CONSTANTLY. I already have tried clearing data/cache several times, no luck.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Try using a different recovery. I've had that problem before, baseband and IMEI were shown as unknown and com.android.phone would force-close constantly. I don't know why the recovery would cause that, but switching recoveries worked for me.
I had this same issue yesterday, very strange that I would see this listed here about the same time. I haven't done anything different, that I haven't done before. Then I flashed the stock T-Mobile rom and it still kept doing it. Apn settings disappeared when this happened.
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
I don't know what happen,but i will try to explain my problem.
I tryed different ROMS, but never switch out from Stock Roms (Stock, Genisys and now Imperium). I never had problems, everything always runs fine as it's supposed to be. However, yesterday afternoon i got the first "Camera has stopped working", Whatsapp can't access camera and also the camera Apps keeps FC. I tryed to reboot, clean data and cache, cleank dalvik. Nothing helped, so this morning i flash the last Imperium versio (5.0, i was onto 4.0).
It helps, because than camera starts to work again and no problem. After 7-8 hrs, the problem comes back again but also with "InCallUI has stopped working". So i flashed again Imperium Rom, but even at the startup Wizard the "Camera has stopped working" message appears istantly. When i finish the wizard, if i try to Call the UI does not appear (but the call starts and who i call receive my call lol). I tryed few flash but no helps, still got problems.
When i flash i go to TWRP, clean system, data, dalvik cache, cache. Then i flash the zip. I haven't installed any mods after, just messaging apps and social apps.
What the hell is happening and what i need to do to resolve this problem?! I thought switch to CM/AOKP/RESURRECTION and try another rom but i prefer to stay into stock .. I have also thought to flash KDZ of the last 815 release and than again Imperium, maybe it helps.
Any tips? Thanks for your time.
Vipery said:
I don't know what happen,but i will try to explain my problem.
I tryed different ROMS, but never switch out from Stock Roms (Stock, Genisys and now Imperium). I never had problems, everything always runs fine as it's supposed to be. However, yesterday afternoon i got the first "Camera has stopped working", Whatsapp can't access camera and also the camera Apps keeps FC. I tryed to reboot, clean data and cache, cleank dalvik. Nothing helped, so this morning i flash the last Imperium versio (5.0, i was onto 4.0).
It helps, because than camera starts to work again and no problem. After 7-8 hrs, the problem comes back again but also with "InCallUI has stopped working". So i flashed again Imperium Rom, but even at the startup Wizard the "Camera has stopped working" message appears istantly. When i finish the wizard, if i try to Call the UI does not appear (but the call starts and who i call receive my call lol). I tryed few flash but no helps, still got problems.
When i flash i go to TWRP, clean system, data, dalvik cache, cache. Then i flash the zip. I haven't installed any mods after, just messaging apps and social apps.
What the hell is happening and what i need to do to resolve this problem?! I thought switch to CM/AOKP/RESURRECTION and try another rom but i prefer to stay into stock .. I have also thought to flash KDZ of the last 815 release and than again Imperium, maybe it helps.
Any tips? Thanks for your time.
Click to expand...
Click to collapse
try the KDZ. if it continues then it must be a hardware problem..
raptorddd said:
try the KDZ. if it continues then it must be a hardware problem..
Click to expand...
Click to collapse
Thanks for reply, i have fixed the problem. Just pull out and put in the battery, idk what happen it seems to be solved now.