[Q] Device goes into Kernel Panic faster than I can make any change - Galaxy S II Q&A, Help & Troubleshooting

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.

Related

[Q] CM 7 Boot animation looping *SOLVED*

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?

[Q] phone won't reset, update or even whipe any data

hi all,
Since a week or 2 my phone is constantly giving messages like this: "The application LogsProvider (process com.sec.android.provider.logsprovider) has stopped unexpectedly"
When i make a new contact or a new file on my phone, it disapears after rebooting. When i uninstall all my apps and reboot the phone, all the apps are back and nothing has been uninstalled. Even when i format the sd card on my pc, and reboot the phone, all the content is back as if nothing has happened.
When i try to reset it to factory settings, it opens in recovery mode. When i then select to wipe all data or wipe cache and reboot, nothing has happened to it, everything is still on the phone like before. Even when i deselect the backup and automatic recovery checkboxes before i reset to factory settings, nothing has been wiped.
When i try to update the phone with kies, the update installs correctly, but when the phone reboots, the same old firmware is still installed and the settings are intact.
When i try to update the phone with Odin, everything goes well, and it says 'pass' in green color. when i reboot the phone, the same old firmware and settings are still there.
I run stock firmware from november '11, which i can tell by dialing *#1234*
Can anyone help me identify this problem, and is there a solution? It really looks like this phone has some write protection or something..
i made a youtube video that describes the problem, but this forum doesn't allow me to make a link.
anyway, my phone stays stuck on the 3rd of september and that sucks.. any solutions plz?
the video
i can't post the link, so let's try it like this:
First type the 'www', then the 'youtube', then the '.com', then type 'watch?v=n6SH8QDJr94&feature=g-upl'
Flash custom kernel, do a factory reset in CWM and see if the data is gone.
i've already tried to install cwm, but first i needed to root my phone. When i tried to root it, it could not find the Root.zip on the sd card, although i'm pretty sure i put it there, it just disapeared after the reset, just like all the other files..
Flash it [kernel] through Odin (PC).
allright, i will try that, thanks already!
ehm, even that didn't do anything, i will upload a youtube video in a few minutes..
the youtube video:
type 'youtube', then '.com', then '/watch?v=P_D2EbPF0Ik&feature=youtu.be', without the '..
really strange how i can update the kernel and nothing has changed!
I really start thinking there is some kind of write protection or the internal storage is totaly screwed up?
Seems your nand is partially borked, and is stuck in a state where it will not update the memory, so it is "stuck" at a specific point in time.
I have heard that it's POSSIBLE (and I stress possible) that flashing with repartition ticked with the PROPER .pit file will resolve your issue, but I cannot say this with any certainty as I have not actually done this myself. But at this point, it seems you don't really have anything to lose by trying.
I can't seem to find a reliable download link for the .pit file for the I9100 right now... it's called u1_02_20110310_emmc_EXT4.pit. I'll see if I can't find one when I have a spare moment.
EDIT: Found one - http://forum.xda-developers.com/showpost.php?p=28321934&postcount=35. BUT!!! Only use it if you are positive you have an I9100. (check on the label under the battery) Flash it with a stock firmware with re-partition checked.
False alarm. Turns out the link is dead.
EDIT 2: This looks promising... http://forum.xda-developers.com/showthread.php?t=1448351

Trying to recover a soft Bricked i9000

Hey
So this old i9000 phone came with some Horrible bloatware I wanted to get rid of.
I flashed a stock Rom with Odin, (I've done it many times before on a different i9000)and Wiped Data and Cache afterwards, And 3 different Roms give me this problem:
When the phone finally initializes, Everything keeps Stopping unexpectedly. I've tried to get to enabling ADB to maybe view the logcat but I can't even get to the settings.
I did notice in the recovery mod an error that said something about System/CSC/CEL/system not being accesible (And i'm surprised it's still there after 3 flashes, CEL being the CSC for the bloatware company)
What do I do?
Currently on Stock rom with stock recovery.
Edit:
Okay, I have managed to race through the crashes, Launch the Home app, and enable ADB... so we have that now... "ADB devices" Shows its connected.
Edit2:
They all crash with "java.lang.ClassNotFoundException:" Right now Home screen is working but anything i try to run crashes
Edit3: It's like the old Gmail account is HARD CODED to it, What the hell? 3 rom flashes and countless factory reset, The account is still there, I cannot get rid of it.

[Q] Phone/Launcher keeps rebooting

First off all, I'm not sure if this question is answered else where.
I have my S2 almost since the day it came out in NL.
Today a problem occurred. After I boot my phone it keeps rebooting the launcher (not sure if that's the correct name). The phone it self stay's on, I don't go back to the Samsung logo or what else - just Android it self keeps rebooting.
I run Go Launcher Ex for a long time, never had problems with it.
I assume it's a memory problem.
Had a similar problem about a year ago, where my internal memory was stuffed. After removing some apps etc. my phone was just fine again. Problem today is I cant do anything. Connection with pc fails, because of the rebooting software. I'm not even fast enough to get to the Android settings.
Edit: I tried booting in Safe Mode. Which works, till it reboots into normal mode.. and keeps rebooting. And of course there's no time to get something done in safe mode.
- Phone get's really hot when this all happens. An other indication for a stuffed memory(card) I think?
- Removed the SD + SIM, no changes.
Edit:
I was quick enough to change the launcher to something else (i believe Nova, via Home Switcher). Then reboot my phone in Safe Mode with Nova on, then the reboot of the software starts again.. and it forces itself into Go Launcher Ex without Safe Mode.
Thanks in advance,
DrushNL said:
First off all, I'm not sure if this question is answered else where.
I have my S2 almost since the day it came out in NL.
Today a problem occurred. After I boot my phone it keeps rebooting the launcher (not sure if that's the correct name). The phone it self stay's on, I don't go back to the Samsung logo or what else - just Android it self keeps rebooting.
I run Go Launcher Ex for a long time, never had problems with it.
I assume it's a memory problem.
Had a similar problem about a year ago, where my internal memory was stuffed. After removing some apps etc. my phone was just fine again. Problem today is I cant do anything. Connection with pc fails, because of the rebooting software. I'm not even fast enough to get to the Android settings.
Edit: I tried booting in Safe Mode. Which works, till it reboots into normal mode.. and keeps rebooting. And of course there's no time to get something done in safe mode.
- Phone get's really hot when this all happens. An other indication for a stuffed memory(card) I think?
- Removed the SD + SIM, no changes.
Edit:
I was quick enough to change the launcher to something else (i believe Nova, via Home Switcher). Then reboot my phone in Safe Mode with Nova on, then the reboot of the software starts again.. and it forces itself into Go Launcher Ex without Safe Mode.
Thanks in advance,
Click to expand...
Click to collapse
go in e3 recovery and perform factory reset
DrushNL said:
First off all, I'm not sure if this question is answered else where.
I have my S2 almost since the day it came out in NL.
Today a problem occurred. After I boot my phone it keeps rebooting the launcher (not sure if that's the correct name). The phone it self stay's on, I don't go back to the Samsung logo or what else - just Android it self keeps rebooting.
I run Go Launcher Ex for a long time, never had problems with it.
I assume it's a memory problem.
Had a similar problem about a year ago, where my internal memory was stuffed. After removing some apps etc. my phone was just fine again. Problem today is I cant do anything. Connection with pc fails, because of the rebooting software. I'm not even fast enough to get to the Android settings.
Edit: I tried booting in Safe Mode. Which works, till it reboots into normal mode.. and keeps rebooting. And of course there's no time to get something done in safe mode.
- Phone get's really hot when this all happens. An other indication for a stuffed memory(card) I think?
- Removed the SD + SIM, no changes.
Edit:
I was quick enough to change the launcher to something else (i believe Nova, via Home Switcher). Then reboot my phone in Safe Mode with Nova on, then the reboot of the software starts again.. and it forces itself into Go Launcher Ex without Safe Mode.
Thanks in advance,
Click to expand...
Click to collapse
Go to recovery and wipe cache and wipe dalvik Cache. If still not working then do Factory Reset. If the problem is still there than flash the rom again.
Sent from my GT-I9100 using Tapatalk
As my main goal was to get my data from the phone I suprised myself a lot and I'm copying as we speak the whole /emmc/ via SDK tools.
It's gonna take a while - I assume it's copying the whole 16GB.
After that I'll try factory reset's etc. and check if I can use my phone again.

[Discussion/Q-A/Help] Tired of buggy Software/ROM, Need your help to Fix It.

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.

Categories

Resources