Unfortunately, Android System has Stopped! Help Please! - AT&T LG G3

Last night I decided to switch to ART from Dalvick runtime. Ever since, when android finishes loading, I get the error message "Unfortunately, Android System has Stopped." I've tried returning to stock (I'm rooted) and neither of my windows computers can see my phone which is weird because I unrooted my LG G3 recently with no problems. I've performed a hard (factory) reset numerous times. Sometimes the android system loads up OK but as soon as I reboot or power down I have the error message again. I'm at my wit's end. I can't return the phone because it's still rooted and I can't get it to work. When it boots, the LG screen appears normally. The At&t screen appears normally. Please help! I'm desperate.

If you're okay with losing info, give this a shot. I'm not sure exactly why it's doing this unless you had xposed framework before. Anyway, follow the steps and it should fix it. I'm not sure if you've tried going into the boot loader yet and doing a factory reset through there. So you can try whatever you like
http://forum.xda-developers.com/showthread.php?t=2785089

I can't get a computer to recognize the phone. I have tried a hard reset and I still get the error message. Any other ideas?

I had the same issue after I tinkered with something I shouldn't have tinkered with. I think I installed GravityBox, didn't like what it did, tried to factory reset, and started getting the Android System error consistently.
That link mcnick posted will serve you well. I would however use this thread since it's tailor made for the AT&T variant.
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827

Related

[Q] I think my XOOM is possessed, HELP!

I want to start out stating that i am very familiar with android's but have never experienced anything like this.
The first thing I tried was to oem unlock it from fastboot, which it claimed to do however i am skeptical as nothing else seems to stick, attempted to install cwm and TWRP neither with any success, even though it says the action was performed successfully.
The strangest thing is that i deleted all the apps on the device from settings/app, but when i rebooted my device they all came back!
All i wanted to do was do a factory reset, which also claims to finish successfully but after rebooting from recovery mode, i am back where i started.
App Updates also do not work as every time the tablet reboots, the apps have to be re-updated.
Its like the tablet is stuck in a read only state and when it reboots all changes are lost.
Like i said, this thing is acting weird and i have no idea where to go from here. Any help would be greatly appreciated!
[Update: Tried RSDLite, same results, Result is PASS however after system reboot everything is the same.]
Another update, tried downloading HWI69 which is the stock rom, tried to fastboot each image but nothing sticks even though it seems to say it writes it to the system. I'm starting to think the NAND memory is locked up and cannot be written to anymore if that's even a possibility.
BUMP

unfortunately process com.android.phone has stopped

I tried to dial the # and I got this message unfortunately process com.android.phone has stopped
now every time I hit ok it comes back - after 3 times phone reboots and starts over the same message.
Phone is stock - just got updates OTA it is Global version
please advise if anyone had same issue and possible resolution. I checked some solutions from GAlaxy s2 and 3 but all of them require phone to actually work - I cant get to settings
thank you
Well i had the same problem after flashing many different roms. My mistake was forgetting to wipe to factory reset before flashing. Maybe this will solve your problem too.
Having this issue as well!
This started happening to me this morning. I am running CM12 Nightlies. I tried factory resetting...still happens. I tried everything. I even tried fastboot flashing the device to 100% stock...the first time I booted up after flashing stock and locking bootloader....the phone says "Unfortunately, the process com. android. phone has stopped". EVEN AFTER A FULL FLASH BACK TO STOCK UNROOTED 4.4.4!
HELP PLEASE!

[Q] Hard Bricked, Security Error Boot Loop D800 after Lollipop OTA attempt.

Hey XDA,
I have a D800 that is totally stock. I have no custom recovery, and have never rooted the device.
A couple days ago I got the notification for an OTA update. I hit the notification, and rebooted the phone. It started the update process. It got through the first step. When it started the second part of the update, a black box popped up, and a code like "ERR 0x04ff" or something like that popped up. The phone rebooted, and got stuck in a boot loop with a "Security Error." The phone will boot up, show the LG logo, then show a slightly different LG logo with "Security Error" underneath it, then reboot and start the process over. I started messing around with the power button and volume keys to see what different modes I could boot it into. Initially I could boot it to the Factory data reset screen, the Hardware Mode Keys screen, and I got it into Download mode once. I didn't have any of the software or files available at the time to do anything with Download mode, so I opted to try a Factory reset. The phone attempted a Factory Reset. The little android with wiggly ears, and the spinny cube thingy popped up for about 4 seconds, and the phone rebooted.
Since trying that initial Factory Reset, I have been unable to get the phone into Download mode. I've tried doing the Factory Reset multiple times to no avail. I have not seen fastboot at all.
At this point, the only thing I can do with the phone is boot it to the Factory Data Reset screen, and to the Hardware Keys Mode screen. It will not do a factory reset. The android pops up for about 1-2 seconds, and the phone reboots, and goes right back to the boot loop with the security error.
I'm at a loss at this point. I've called AT&T, and unfortunately my phone is out of warranty by about 3 weeks. So they can't just mail me a replacement. Does anyone have any ideas? I can't seem to get it to be recognized by my PC, on Windows or Ubuntu. I get the feeling that it's just hard bricked, and there really isn't anything else I can try.
Any suggestions would be greatly appreciated
TL-DR: Totally stock D800, no custom recovery or root. Security Error Boot Loop after OTA attempt. No download mode or fastboot, factory reset is ineffective. Not recognized by PC. What do I do now?
bob51dole said:
Hey XDA,
I have a D800 that is totally stock. I have no custom recovery, and have never rooted the device.
A couple days ago I got the notification for an OTA update. I hit the notification, and rebooted the phone. It started the update process. It got through the first step. When it started the second part of the update, a black box popped up, and a code like "ERR 0x04ff" or something like that popped up. The phone rebooted, and got stuck in a boot loop with a "Security Error." The phone will boot up, show the LG logo, then show a slightly different LG logo with "Security Error" underneath it, then reboot and start the process over. I started messing around with the power button and volume keys to see what different modes I could boot it into. Initially I could boot it to the Factory data reset screen, the Hardware Mode Keys screen, and I got it into Download mode once. I didn't have any of the software or files available at the time to do anything with Download mode, so I opted to try a Factory reset. The phone attempted a Factory Reset. The little android with wiggly ears, and the spinny cube thingy popped up for about 4 seconds, and the phone rebooted.
Since trying that initial Factory Reset, I have been unable to get the phone into Download mode. I've tried doing the Factory Reset multiple times to no avail. I have not seen fastboot at all.
At this point, the only thing I can do with the phone is boot it to the Factory Data Reset screen, and to the Hardware Keys Mode screen. It will not do a factory reset. The android pops up for about 1-2 seconds, and the phone reboots, and goes right back to the boot loop with the security error.
I'm at a loss at this point. I've called AT&T, and unfortunately my phone is out of warranty by about 3 weeks. So they can't just mail me a replacement. Does anyone have any ideas? I can't seem to get it to be recognized by my PC, on Windows or Ubuntu. I get the feeling that it's just hard bricked, and there really isn't anything else I can try.
Any suggestions would be greatly appreciated
TL-DR: Totally stock D800, no custom recovery or root. Security Error Boot Loop after OTA attempt. No download mode or fastboot, factory reset is ineffective. Not recognized by PC. What do I do now?
Click to expand...
Click to collapse
Try this guide, it should help. Good luck.
http://forum.xda-developers.com/showthread.php?t=2662445
Sent from my LG-D800
Swetnes said:
Try this guide, it should help. Good luck.
http://forum.xda-developers.com/showthread.php?t=2662445
Sent from my LG-D800
Click to expand...
Click to collapse
Thanks for the reply. I was about to reply saying my phone wouldn't go into download mode, but then I randomly decided to use a different usb port, and now it went into download mode.
I'll give it a shot now and see what i can do
Ok, It seems I'm back up and running. I followed this guide http://forum.xda-developers.com/showthread.php?t=2432476 which re-flashed me to 4.2.2. I'm going to try and upgrade using LG PC Suite from my laptop, and see if I have better luck this time.
Lesson learned, try every USB port when trying to boot into download mode.
Thanks for the help

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.
Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-
So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.

Debugging J7 Prime Restart issue

Pardon for a long story but someone gave this Samsung J7 Prime(SM-G610F) to me with an issue "An Error Has Occurred While Updating The Device Software". So I gave Samsung Smart Switch a try sadly they removed the Initialize option and old version don't seam to do what it suppose to do so I wen to a traditional Odin flashing. I then look for a stock rom for the phone that I think is the right one. Started with android 6 MM region pakistan and flashing went well. I was able to use it for a good hour or two until I notice it restarted by it self, then it keeps doing it 10-20 seconds after booting up. I though its the firmware I'm using so I went and look for Oreo version this time I region india (I don't know if region matters). So I flashed it again and tested the device again. I'm still able to use it for a good while till it restarted again. I then keep testing it to see what may be causing the problem. I notice that when the WIFI is on it just crash the phone to reboot so as soon as the phone reboots I turned the wifi off and it didn't crash anymore. I then factory reset the phone cleared everything, wipe cache then installed benchmark tools first. Thing I notice is it crashes when Google Play store is trying to install or download something. I tested it a couple of times to see when it crash and it does crash when downloading or installing something. I was still able to install 3Dmark and run it with wifi off. It completed the test without crashing so it couldn't the processor issue. I then look for another rom and tried flashing it. This time I had issue with it failing at system.img even if I use recent rom that worked. I then keep trying till flashing TWRP worked and flashing the rest of the rom is fine again.
What bothers me is why doesn't it crash during the first couple of hours. I've search similar issues and they say it may have been and app issue. I've already disabled bunch of app but nothing changed. Run the phone in safe mode but this time instead of crashing and rebooting right away it freezes for a few seconds. I suspect if google play or something being an issue since I've tried disabling it and it didn't crash for a couple of hours. Looked for allot of related thread but none of them seam to solve my problem.
I suspect either its the rom that I'm using and it can only be fixed by using the original rom, or its having a memory issue but don't know how to pin point it. Anyone can suggest on how I can debug this? I'm used to debugging things in real time and my knowledge with android is a quite slim but as a programming understanding the errors won't be a problem. I hope.
Edit: Hmm. Does copying kernel log with TWRP work or the kernel logs get overwritten every time the phone reboots? Because I see the kernet logs but don't see anything failing except for something saying SHUTDOWN but I don't think thats it. :S
Still no reply. :S I think its /system dismounting it self while doing a write operation. but it doesn't trigger until a certain amount of time after the phone is flashed or factory reset. I have to go to recovery and mount system back but that only happens on marshmallow. over version it remounts it self after the random reboot. After factory reset I'm able to install COD mobile and play a couple of match. after a long while it just decides to reboot.
I also tried z3x and after reading PIT from phone OK. the phone just reboots and flashing completes without it doing any flashing.

Categories

Resources