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.
Related
After I restarted my Cell the boot animation keeps on replaying after the slight vibrate, same thing hapens for 10 mins then the mobile starts.
Its not normal
Can anyone help?
HI
Its really not normal.
Never happened to me.
U shud probably try
1-unmount sdcard/ check last installed application which might caused this
2-take all backups and go to cwm recovery and clear user data and caches.
3-If all these doesnt solve, then reflash cm7!
hirentherock555 said:
HI
Its really not normal.
Never happened to me.
U shud probably try
1-unmount sdcard/ check last installed application which might caused this
2-take all backups and go to cwm recovery and clear user data and caches.
3-If all these doesnt solve, then reflash cm7!
Click to expand...
Click to collapse
Found a partial solution after formatting the cell twice like a fool
Last night while playing Dangerous chambers 3D or somthing my cell got hanged.
Later it wouldnt restart or anything so had to pull out the battery.
After it started it went into loop mode.
I got worried
Formatted it once.
All ok later then again after some apps it went in loop mode.
Couldnt figure out which app was causing the prob.
Then today morning after some reasearch found out that:
In CM7 settings in settings menu> Tablet tweaks> disable lock screen> Tick
This is what i used to do to use an alternate lock screen.
After removing the check all is fine untill now.
Will update if anything happens next.
I also met this problem when trying to develop a CM7 ROM myself (from HPA CM7 BETA2). My problems are:
1. After building successfully, apps inside the output /system/app folder are bigger (in size, of course) than the original HPA ROM (ADWLauncher in HPA is 731.5K, and mine after building is 1M)
2. After flashing to DV, my phone hangs at the CM7 logo. It's OK to type "sudo adb devices" to see that my device is attached, but then any command other than that will receive "error: closed"
Guys, do you know what's the problem with my build?
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.
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Have you performed a factory reset? (It will delete all your data and apps)
rp-x1 said:
Have you performed a factory reset? (It will delete all your data and apps)
Click to expand...
Click to collapse
Yes, when the phone was new and the restarts were annoying. It fixed it for 1 day. The next day it was restarting again.
This would point to an app you've installed causing the issue. Factory reset again and install each app one by one until the restarts happen to find out which.
SteveTM said:
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Click to expand...
Click to collapse
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
cmstew said:
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Click to expand...
Click to collapse
Will try it when I'll have time for it, thanks for the help!
I have a sprint note 4. I don't have it activated currently and use it as a tablet of sorts. Recently it's been giving me problems and I've wanted to break it. I got it about 2 years ago, and since then I rooted it, then installed twrp recovery, then flashed custom software. The software I used was called Dr.Ketans I believe, it combined the note 5 and s6 edge plus softwares. It started to crash occasionally so I installed cyanogenmod onto it. It worked for a bit, but now when Turing the device on, it takes like 10-15 minutes to boot up. And it only stays on for 5 minutes before it crashes and freezes. When it does that, the only way I can boot it up again is take the batter out and put it back in a few times because sometimes I get an error message. The error message barely happens but it says something along the line of "cant boot up". If I use twrp, my phone doesn't freeze. I've tried reinstalling the software, I've tried formatting the entire phone and refreshing. Nothing seems to work. I've even tried changing my kernel but I'm not entirely sure what it is, and how it affects the phone. I'm not the smartest with phones, but I'm good with following directions and googling. If anybody can help me I'd greatly appreciate it cause I've been dealing with this issue for 3 months.
Reinstall the original firmware and make sure it doesn't freeze / crash with it and then you can reinstall the custom software. Make sure that you have the required recovery, bootloader, and baseband version to run the newer custom roms. The requirements should be located in the OP.
I appreciate the response. I will try this as soon as possible. Should i use odin to flash or would it be possible to use twrp recovery? Also, what do you mean when you say the requirements are in the OP?
You should use Odin to recover to make sure you have a fresh start.
The requirements of the rom you pick afterwards should be in the OP.
Hi,
So here's my problem. (Sorry, it's a long story)
I purchased a phone from a french company ("Archos") three months ago. The Android phone was working fine until lately when I've been getting random freezes. When I would scroll on an app (Twitter's Feed, Reddit Homepage), the phone would freeze. The only way to solve this problem was by rebooting entirely the phone. Sometimes, the phone would also freeze at random moments (on the Lock Screen, the Homepage, etc...) with the only issue being to restart the phone.
I tried to factory reset the phone but it kept on freezing, even freezing on the first page of the Android Setup Wizard (The one with the "Welcome" label and the "Get Started" button) preventing me from touching the "Get Started" button. After multiple reboots and factory resets the phone was still freezing randomnly.
One thing to know is that the phone was apparently running Cyanogenmod since it's primary launcher was Trebuchet. So, I tried to install a stock copy of Android Nougat (7.0) hoping it would fix the problem. The thing is, there's no TWRP image available for my device (Archos Sense 55S). Instead, I used an tool name "SP Flash Tool" to flash directly a copy of Android onto my phone (I managed to find one online).
But the problem did not get solved. Now, it's worse. Before, even though the phone kept on freezing on the first page of the Android Setup Wizard, 1/12 of the time, it would let me touch the "Get Started" button and proceed with the rest. Now, it won't let me touch the button at all, it seems like the application is not receiving any input at all. I know the screen isn't broken because the "Enter SIM Card password" prompt works perfectly fine and when I want to turn off the phone, I can easily select "Power Off", "Reboot", confirms "OK" on the "The Phone will restart" dialog box, adjust the volume levels, the screens responds! But on the Android Setup Wizard: nothing's happening.
I am desperate. It feels like I have tried everything. I cannot install anything else (through ADB & Fastboot) since I can't unlock the bootloader because I can't allow OEM and/or USB debugging (I can't access the settings without completing the Android Setup Wizard). My question is there a way to install a custom rom with SP Flash tool? If so, is it recommend? Won't that brick the phone? Or is it too late now, and it's over?
Thank you for your time.