Hello.
I'm using GT-I9100 Resurrection Remix JB v3.1.3 on my Galaxy S2.
In the last couple of days the battery would overheat and die quickly because of drmserver that kept running for a long time. No idea why since I was offline and I never watch movies etc in any case.
I blocked it from startup with Gemini App Manager and all was well (the battery cooled down and would recharge quickly again) until I rebooted.
Now I'm getting stuck on the Resurrection animation boot logo. It seems it can't start up the interface.
Reinstalling Resurrection (I still had the installer in the phone) didn't change anything. It went through optimizing the apps and then hung again with the continuous boot logo animation.
Is there a way to enable all blocked programs again in the recovery console?
Would deleting the init.d folder take care of it or would I cause more havoc?
Thanks in advance for any pointers.
kanenas_0 said:
Hello.
I'm using GT-I9100 Resurrection Remix JB v3.1.3 on my Galaxy S2.
In the last couple of days the battery would overheat and die quickly because of drmserver that kept running for a long time. No idea why since I was offline and I never watch movies etc in any case.
I blocked it from startup with Gemini App Manager and all was well (the battery cooled down and would recharge quickly again) until I rebooted.
Now I'm getting stuck on the Resurrection animation boot logo. It seems it can't start up the interface.
Reinstalling Resurrection (I still had the installer in the phone) didn't change anything. It went through optimizing the apps and then hung again with the continuous boot logo animation.
Is there a way to enable all blocked programs again in the recovery console?
Would deleting the init.d folder take care of it or would I cause more havoc?
Thanks in advance for any pointers.
Click to expand...
Click to collapse
Resolved.
I let it boot up till it hung at the boot logo and used adb to access it.
To keep it short, the culprit was 'fused location' (com.android.location.fused) that I had disabled.
I tried to enable it with 'adb shell pm' a few times, got 'killed' messages instead of 'enabled', but during these tries, it finished the boot.
I rebooted the phone and it was back to normal.
Thanks.
Re: [Q] How to re-enable blocked services in recovery mode?
kanenas_0 said:
Resolved.
I let it boot up till it hung at the boot logo and used adb to access it.
To keep it short, the culprit was 'fused location' (com.android.location.fused) that I had disabled.
I tried to enable it with 'adb shell pm' a few times, got 'killed' messages instead of 'enabled', but during these tries, it finished the boot.
I rebooted the phone and it was back to normal.
Thanks.
Click to expand...
Click to collapse
Glad to see that you sorted it out yourself. And thanks for the tip.
Please add [SOLVED] to the title of ur post, so that others can benefit too.:thumbup:
"To err is human, to forgive is divine"
Sent from my SGS II
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.
Hello,
since yesterday my Galaxy S2 (summer 2011) started to act wierdly and I am trying to figure out what is the problem.
I was running the latest Sentinel ROM, and I found it "freezed". So I forced restart long pressing the power button. After the restart, I found it freezed again after some (short) time. It also freeze on the boot process.
Apparently in a random way.
So I tried from recovery a factory reset, full wipe, and reinstalling the ROM. Problem still present.
Today I tried logging with ADB logcat, but I can't figure out the issue from the log. I thought a problem with Mali driver shipped with the ROM, but actually it freezes sometime also on boot (so before loading the drivers)
I tried then to flash back the Samsumg original ROM (JB 4.1.2), which apllied nicely. However it freezes also with Sammie's ROM. Also on boot. By example I one time I got the black screen with the writing "Samsung Galaxy GT-9100" getting grey, with some horizonatl black lines. So frozen.
Flashed again with ODIN, again nicely, but it keeps on freezing on boot.
I am clueless. Could it be some issue with the battery? (it's the original, never replaced)
Any help or suggestion appreciated
Thanks
Update:
I tried to flash it back to GingerBread stock by Samsung with Odin. Applied nicely.
It still keeps on randomly hanging :-|
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.
Good day all
I bought this device from a seller of eBay (from USA), I am in South Africa
I had to network unlock this device, and it all ran perfect, no issues whatsoever
Recently I have noticed my device doing random reboots, once every day(literally), it will reboot when I take it off from charging or when I press pwer button to wake up. After reboot, it will show the Glowing Samsung Logo, and just stay there continueously.
To fix this, I need to do a factory reset, or just clear the Data partition then it works fine again.
This happens at random, so every day I need to reinstall all the apps, it is such a pain, and obviously something is wrong...
Device: Samsung Galaxy Note LTE (i717)
ROM: Blackstar Blackjelly 4.1.2
Baseband: I717 UCMD3
Recovery: TWRP (latest v.)
Just for the record, ,it all started happening recently, the first time it happened, I was browsing 9gag using the app, then my device rebooted in my hand while scrolling, agter going to recovery, my sdcard and internal sdcard has been formated, and all internal partitions has been formated to....
I have no idea what is causing this but I am pretty sure it is not the rom, since I have had this rom for a while now...
What kernel do you use, and can you take a logcat?
(To take a logcat, enable ADB, plug in your device to your computer, and run adb logcat from the Android SDK. You can grab that here: http://developer.android.com/sdk/index.html?hl=sk )
BachMinuetInG said:
What kernel do you use, and can you take a logcat?
(To take a logcat, enable ADB, plug in your device to your computer, and run adb logcat from the Android SDK. You can grab that here: http://developer.android.com/sdk/index.html?hl=sk )
Click to expand...
Click to collapse
after running the logcat with "
Code:
adb logcat > logcat.txt
" for just more than 2 hours, i stopped it...it is 1250kb, see attached, it is compresssed in a zip file
p.s. Im quite positive it shouldnt take that long
any help would really help!!!