Hey guys has anyone ever gotten a "Process System Isn't Responding" error message? My Dev Note 4 is seriously broke. I installed latest build yesterday, BOG5, and everything was fine until about an hour ago. Lost LTE, screen went black, phone would boot, now display is really dim and will not fully boot.
Update: Went into recovery, cleared Delvek and cache and rebooted just fine.
Related
Hey all, first time poster. I wrote a real nice explanation of my problem, but i lost it so anyways, i'll keep it short(ish).
The EVO is less than 3 weeks old, running the latest OTA, recently rooted using UnrEVOked 3, nothing fancy. I ran the battery down completely last night (first time since i got the phone) and once i got to a power source, it wouldn't boot correctly. It hangs at the white splash screen, and then finally boots up but won't respond to any touch input.
Also the phone seems to be running exceedingly slow, the boot process takes substantially long than normal once it gets past the splash screen and my live background is freezing and seems to be stuttering.
I launched into the bootloader and i get a "Touch Panel - Fail". LAME!
I'm not sure what to do at this point, whether i should wipe it or go back to stock or what. Any advice would be much appreciated.
UPDATE:
I managed to get the phone into the recovery console, make a back up (i was planning on going back to the stock image) and wipe the dalvik cache and fix permissions. I rebooted and voila! fixed. Hopes this helps any one else who has this problem.
Moral of this story: Travel with a charger.
Another update. It froze up again in the middle of sending a text. I rebooted by battery removal, and it did the same thing again. Super long splash screen and sluggish boot up, no touch response when it finally came up. I booted into recovery and cleared the dalvik cache again. Seems to be working again now. We'll see if it does it again.....
Well, the screen locked up again. I tried going through the whole process again. I wiped the caches and battery stats, nothing. I wiped all the storage and data, booted into a clean stock interface, nothing. Restored the backup image, and then at some point, through all the rebooting and whatnot, it just shut down completely. I can't even get it to the bootloader. I'm really feeling like it's a hardware problem, and i've made peace with sending it back for TEP, but i have no way to unroot it.
Any suggestions? Please......
Theres unroot processes out there. I cant remember where but ive seen them. Mine gets sluggish too, but after a reboot its ok. You cant even get into the bootloader tho. I'm not even close to an expert but.......uh I'd 'lose' it and call the insurance co....
Was running PA latest build. I took the battery out of the phone and switched with my wife. When I tried to power it back on, it was stuck on the boot screen with the PA logo. I tried flashing the ROM over and several different PA builds and flashed Gapps and I am able to get it to go past boot and to android is upgrading and it checks all the apps but then wont boot after "Starting Apps". I fell asleep last night while trying to get it fixed and when I woke up this morning, it was still on android is upgrading, starting apps. If I wipe data, it works. but nothing changed before I took the battery out. If someone has any pointers I would really appreciate it! I would hate to loose all my data!
I did make a nandroid of everything and tried wiping certain things at a time and its only when I wipe data, it works.
[Q] Flashed BlissPop 3.4, phone is stuck in the "Checking connection" screen
Hi, this is the first time I flash a new ROM on my G3 D855 (I've flashed xposed though) and everything seemed to be fine until I got to the Android setup screen. Wi-Fi had some trouble connecting to my network but it eventually did it, anyway I've left the phone for more than 30 minutes and it's still stuck in the "Checking connection" screen. Is there any way to fix this?
In case you're asking, I've backed everything up, did a factory wipe, flashed BlissPop, flashed gapps and wiped again the cache. Finally I rebooted
stef1997 said:
Hi, this is the first time I flash a new ROM on my G3 D855 (I've flashed xposed though) and everything seemed to be fine until I got to the Android setup screen. Wi-Fi had some trouble connecting to my network but it eventually did it, anyway I've left the phone for more than 30 minutes and it's still stuck in the "Checking connection" screen. Is there any way to fix this?
In case you're asking, I've backed everything up, did a factory wipe, flashed BlissPop, flashed gapps and wiped again the cache. Finally I rebooted
Click to expand...
Click to collapse
Try flashing just the ROM without the gapps, power it up, then reboot into recovery and flash gapps. That should get you past your "checking connection" screen.
stef1997 said:
Hi, this is the first time I flash a new ROM on my G3 D855 (I've flashed xposed though) and everything seemed to be fine until I got to the Android setup screen. Wi-Fi had some trouble connecting to my network but it eventually did it, anyway I've left the phone for more than 30 minutes and it's still stuck in the "Checking connection" screen. Is there any way to fix this?
In case you're asking, I've backed everything up, did a factory wipe, flashed BlissPop, flashed gapps and wiped again the cache. Finally I rebooted
Click to expand...
Click to collapse
Try to press back button while it is keep checking connection. It happened to me 3-4 times,
Anytime that happens i press back button and then forget the network and reconnect.
It should work
Hi everyone,
Being the more adventurous kind of person I am, and also rather sick of LG's android overlay, I decided to finally try rooting and installing a custom ROM, as my previous device was the Nexus 5, and I longed to return to the stock android world. It is a first for me to try this, so I read a few forum posts about it, and finally I rooted my G3 (D855 model), which went flawlessly. I then installed cyanogenmod 12 (I cannot remember which version, it was the most recent at the time) and I was finally satisfied by the software, which was as smooth as butter, unlike LGs skin. After a few months, I made the terrible mistake of installing one of the updates that where suggested, and then the problems began. While the phone was performing the update, it froze on the "optimizing apps" screen, and stayed so for several hours, until I decided to pull the plug on it, and it slowly died of a flat battery. I then tried to reboot the device, which stayed on the LG logo screen for a long time, until I again had to leave it to die. I then rebooted into TWRP recovery, which was the recovery I had installed and used to install CM12, and I tried to recover from the last backup I had performed a week prior about, and it failed with "error executing binary in script". After some googling, I found a forum where someone recommended to wipe the cache, data, system, and dalvik partitions. Having done this , the backup was successful and the phone was up again. A few days later I saw that CM13 with android M was released for the G3, and I decided to try it. I downloaded the rom, backed up my old version again and flashed it with TWRP. It worked, and the device booted into CM13, but I was greeted with a "process has crashed" message. I dismissed it, and the OS seemed to work, but then I realised it failed to recognize my SD card, and the phone internal memory (I own the 32GB model) was listed at a mighty 2gb. I decided to return to CM12 for the moment, so I rebooted into recovery, flashed the backup and got the same "error executing binary in script". I then wiped the cache, data, system, and dalvik partitions, and flashed my backup with no error. The phone reeboted, showed the LG screen, and then went black, then the LG screen, then black, etc... I quickly discovered this to be a boot loop. After some attempts to fix this, the phone booted to the LG screen, then the Cm logo pulsing, and then the "optimising apps". At the end of the process, the lock screen appeared, and after unlocking the device, I discovered it was back in CM13. This was suprising, and the errors I previously had were still here, so I returned to TWRP and tried to flash the original CM12 file I had, and this showed no error. After booting the device, CM13 greeted me again. I decided the device was seemingly possessed, and made the decision to unroot and reinstall into factory settings. But the first step of this process was out of reach, as the phone goes no further then the "download mode" screen with the small blue dots in the middle when I hold the volume down and plug it into the PC. After an hour on said screen, I pulled the plug and tried to reboot again. CM13 appeared once again, as if it was haunting my dreams, and I also found out that TWRP is no longer accessible, as the device stays on the blue loading screen of TWRP.
I have searched and not found anything saying how to get any further then this. I know that as I am not very experienced with this, it was rather foolish to act as I did, so spare me the lectures about that. But I didn't learn to ride a bike without falling off it, so it's kind of the same isn't it? Anyhow, is there someone out there who may assist me?
Many thanks to anyone who has any advice, I'm sick of my backup samsung S3 D:
Ed
Hey guys,
So I've been running on stock EPD1 and everything had been running smoothly. Last night my phone randomly shut down, even though it was at full battery. After trying to restart it, I got stuck in almost a boot loop. It would boot, and during the Samsung animation, it would freeze and restart. This would happen twice until the phone gave up I guess and the phone stays at a black screen with either a constant blue LED, or a blinking whitish-purple LED. I have tried using ODIN to flash back to stock EPD1 and EPF1. Both were successful in ODIN, but didn't solve anything. I can flash TWRP, but flashing any ROMs doesn't help. Wiping Data, System, Cache, and formatting hasn't done anything as well. I also used the Smart Switch and Kies emergency software recovery and initialization features. Again, both said they were successful, but didn't change anything. Sometimes the boot gets to the point where it says "Android is optimizing apps," but once that finishes, it crashes again. Am I 100% screwed? Thanks to anyone that can offer some advice.
Small update: After using the emergency recovery feature in Kies once more, the phone booted to the green "Android is starting..." screen and it counted through 35 apps and said it was starting. It crashed at that point. Not sure if that's progress.