Hi,
I really don't understand what just happened with my Galaxy S2. It was on and well, then crashed for no reason and displayed two error messages in a loop: "Falcon Pro has stopped unexpectedly" (that's my Twitter client) and "android.process.media has stopped unexpectedly". I had not even the time to click on "OK" before the other message appeared and so on, so I forced the reboot by pressing the power button.
Now the phone is stuck on the "S2" logo when booting.
I tried wiping the parition cache, it did nothing.
I have Android 4.0.something, Samsung/Bouygues original rom with Siyah kernel.
What can I do (without losing all my data if possible)?
Thank you...
Zuddi said:
Hi,
I really don't understand what just happened with my Galaxy S2. It was on and well, then crashed for no reason and displayed two error messages in a loop: "Falcon Pro has stopped unexpectedly" (that's my Twitter client) and "android.process.media has stopped unexpectedly". I had not even the time to click on "OK" before the other message appeared and so on, so I forced the reboot by pressing the power button.
Now the phone is stuck on the "S2" logo when booting.
I tried wiping the parition cache, it did nothing.
I have Android 4.0.something, Samsung/Bouygues original rom with Siyah kernel.
What can I do (without losing all my data if possible)?
Thank you...
Click to expand...
Click to collapse
Do you still have the original rom zip on your sd card? If you do, you could try a dirty flash of it on top of your current setup. Wipe cache/dalvik cache and then flash the rom zip. Seeing as you're having FC's, you could also fix permissions in recovery, can't hurt.
Edit: Note, that's attempting to not wipe your data. If that doesn't work you'll likely have to factory reset from recovery.
Hopper8 said:
Do you still have the original rom zip on your sd card? If you do, you could try a dirty flash of it on top of your current setup. Wipe cache/dalvik cache and then flash the rom zip. Seeing as you're having FC's, you could also fix permissions in recovery, can't hurt.
Edit: Note, that's attempting to not wipe your data. If that doesn't work you'll likely have to factory reset from recovery.
Click to expand...
Click to collapse
No, I didn't have any rom on my card...
I tried to wipe dalvik, fix permission, wipe cache and reboot but the problem was not fixed.
So I said goodbye to my data, did a factory reset and that worked. Phew!
Thank you
Related
Have flashed my S2 a few times, and happy with XXKI4, and also rooted using the CF-Root method.
However, seem to be getting a few Force Close errors here and there.
Market sometimes force closes when im not even using it, And if i go to Settings-Location+Security-Find my mobile, both Sim change alert, and remote controls throw up a com.android.settings Force Close.
I have wiped cache, dalvik cache, and fixed permissions using CMW recovery.
Any ideas chaps?
Thanks.
Would a Hard reset maybe solve this?
mk2vr6 said:
Have flashed my S2 a few times, and happy with XXKI4, and also rooted using the CF-Root method.
However, seem to be getting a few Force Close errors here and there.
Market sometimes force closes when im not even using it, And if i go to Settings-Location+Security-Find my mobile, both Sim change alert, and remote controls throw up a com.android.settings Force Close.
I have wiped cache, dalvik cache, and fixed permissions using CMW recovery.
Any ideas chaps?
Thanks.
Click to expand...
Click to collapse
Would be my first impression too.
Just do a complete system / nandroid backup in recovery mode (or by using the CWM Manager app).
Then Boot into recovery mode and do a factory reset.
Then reboot into recovery again, wipe cache partition and Dalvik cache too.
Then reboot the phone.
If that does not help, then you may have to flash the ROM (and afterwards CF-Root kernel) again.
Please remember to backup before and wiping cache(s) after flashing.
That will prevent most common FCs.
Good luck !
I had the same problem on my galaxy note, happened when i disabled the samsungservice.apk under system/app (was trying to remove Samsung bloat)
Put back the samsungservice.apk there and no more forced closes for the find my phone settings
I was flashing CM9 from CM7 on my Motorola Defy, botched it up intially due to a slip of my finger which led to me to Clear the cache first. But then I restarted the entire process by Clearing Data -> Installing -> Flashing Kernel and so on...
But when I tried to clear the Dalvik Cache, the phone didn't delete it. It didn't give me a message that it wiped the cache, but it didn't say otherwise either. This led me to believe that the cache just didn't exist anymore.
As a result, I'm unable to install apps - Says there is no memory and I need to make more. Also, everytime the phone comes on is treated as the first time. It takes me through the whole process of Setting up an account and everything. This has rendered my phone obsolete.
Please help me!
Thanks in advance.
~Bloo (newb) ^_^
EDIT: Solved, reflashed the stock SBF. But is this the only solution? :O
Have you tried doing a clean install?
Honestly, any time you get issues like this where the phone gets stuck (either in a boot loop or resetting your settings every boot, etc.) it's best to just wipe/factory reset and re-flash everything.
This is also why it's important to make backups so that if something does go wrong when flashing, you can just restore and be good to go.
If by a clean install you mean starting from wiping data, flashing the ROM on again and going on to clear cache and dalvik cache; Yes I did that. But I'm unable to clear the cache.
I ought to have created a backup, didn't.
So how can I go about fixing this issue?
bloomark said:
If by a clean install you mean starting from wiping data, flashing the ROM on again and going on to clear cache and dalvik cache; Yes I did that. But I'm unable to clear the cache.
I ought to have created a backup, didn't.
So how can I go about fixing this issue?
Click to expand...
Click to collapse
A clean install seems like the main thing to do (again). If you want, you could try going back to stock.
Installing again didn't do the job. Still can't wipe Dalvik Cache and the Setting still reset on every boot.
The chief problem I have with this is that I'm in India whereas the stock baseband is Europe. So to change it I've to reboot and can't do that because it resets every boot. @[email protected]
Is it a problem with the Kernel?
I'll go back to stock, but it seems a bit complex and I'm afraid I'll brick my phone. :'(
EDIT: Felt it was important to mention that the boot screen still shows CM7.1 and not CM9
I have a similiar problem.
Everytime I choose clear Dalvik men, it looks like he freezes for about a second or two. Then you see the 'menu' no - no - no - no - yes, clear dalvik memory - no - no - no (or something like that) pop up for half a second, and then it is gone. Is this a problem in CWM? Or is it in my phone?
I have a similar problem too! When I hit 'clear dalvik cache', the CWM screen just flashed once and nothing happened, and nothing says 'cleared dalvik cache' or similar...
Me too , how to solve it? Can anyone help? Mine is samsung gio
I have an issue similar to yours with my tablet (samsung galaxy tab 4 10.1 or SM-T430NU) in which it doesn't mount /data and it doesn't let me wipe to factory. Still haven't found how to fix this.
Hi.
Met a problem with my GT-I9300. When I shut the phone off it just reboots. The phone was rooted and running a custom rom when this started. Now I have unrooted with mobile Odin and flashed a official firmware but the problem persists.
I have even tried a battery pull. When battery is inserted again the phone remains off til I push the powerbutton. But when I try to turn it off after this it just reboots again.
Anyone else had this? Tips on what to do?
I've never had any luck fixing this problem. I always had to wipe and flash. However, as a temporary fix, you can power off from recovery.
Sent from my GT-I9300 using Tapatalk
can I ask what you are doing when you turn it off?
Sent from the asylum
Just to clarify, even wipe the phone and restore it to stock completely by flashing official firmware doesnt solve it.
When I turn it off I hold powerbutton til i get the powermenu. From there I choose "turn off". Phone does what it should, screen goes off and everything, only a few seconds later the phone boots again.
basse10000 said:
Just to clarify, even wipe the phone and restore it to stock completely by flashing official firmware doesnt solve it.
When I turn it off I hold powerbutton til i get the powermenu. From there I choose "turn off". Phone does what it should, screen goes off and everything, only a few seconds later the phone boots again.
Click to expand...
Click to collapse
If the phone was totally cleaned formatted sd card and stock firmware installed then its a hardware problem .
But my guess is it as not totally clean .
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
I have now tried to wipe and format sys/data/cach/sd in cwm. Flashed stock firmware via odin. Still same issue. Guess its hardware.
Thanks anyway.
This may sound strange, but is this the clock problem the Desire HD had.
In time settings, uncheck the auto update.
Change time & date to something random.
Power off and pull the battery before it reboots.
Give it a min, power up, reselect auto update and reboot.
Should be good to go. If its the same problem that is.
Sent from the App that Time Forgot.
It also happens to me yesterday, I wipe cache, system, data, reinstall roms (CM and AOKP) and is still happening
r0uzic said:
It also happens to me yesterday, I wipe cache, system, data, reinstall roms (CM and AOKP) and is still happening
Click to expand...
Click to collapse
It happened also to me once. I flashed my rom in the same order as you did. But what my problem solved was, I made a wipe AFTER I installed the ROM. After that, I didn't had this issue anymore.
These are the steps I did...
- Get into the CWM recovery
- Wipe Data/factory reset
- Wipe Cache
- Wipe Dalvik-Cache
Hope it works also to you...
Solved
I solved it by flashing a later official firmware - XXALF6.
Darkrider82 said:
It happened also to me once. I flashed my rom in the same order as you did. But what my problem solved was, I made a wipe AFTER I installed the ROM. After that, I didn't had this issue anymore.
These are the steps I did...
- Get into the CWM recovery
- Wipe Data/factory reset
- Wipe Cache
- Wipe Dalvik-Cache
Hope it works also to you...
Click to expand...
Click to collapse
basse10000 said:
I solved it by flashing a later official firmware - XXALF6.
Click to expand...
Click to collapse
Thanks, I'll try twice methods
Update: It's rare, but has returned to work normal and I doing nothing
Hello,
i found a solution for that problem. You will lose some sd card files.
go to settings-storage-others (or other) and mark all files. Then delete them an go to downloadmode to reflash you firmware. Reboot and the problem is missing.
ok i had download odin, and flashed everything went great, it reset and just hung on the boot logo for like 5 min, then installed TWRP and flashed Superuser and wiped cache and dalvik and then rebooted, same thing it will not get past the att boot logo, i do not have kies installed but i do have the usb drives. could that be and issues?
Bradl79 said:
ok i had download odin, and flashed everything went great, it reset and just hung on the boot logo for like 5 min, then installed TWRP and flashed Superuser and wiped cache and dalvik and then rebooted, same thing it will not get past the att boot logo, i do not have kies installed but i do have the usb drives. could that be and issues?
Click to expand...
Click to collapse
If you used Odin kies wouldn't be involved. I had similar problem. I did a complete wipe (both caches, system and data) then installed via Odin again. Now all is good.
Sent from my SAMSUNG-SGH-I717 using xda premium
thank you, that worked.
if anyone has this problem again save yourself some time. reboot into recovery and factory reset. Worked for me.
440bro said:
if anyone has this problem again save yourself some time. reboot into recovery and factory reset. Worked for me.
Click to expand...
Click to collapse
also rebooted into stock recovery and factory resetted. FInally booted, give it some time (likke 5-10 minutes) after the ATT logo freeze, Its probably building the bloatware cache.
Keep in mind installing this rom is a change of rom base and not just a little tweek -- all the wipes we usually do and backups of everything should be done to ensure a clean install.
It is a nice stock rom, and I was shocked at the amount of at&t bloat included.
chrisrotolo said:
also rebooted into stock recovery and factory resetted. FInally booted, give it some time (likke 5-10 minutes) after the ATT logo freeze, Its probably building the bloatware cache.
Click to expand...
Click to collapse
Lololol bloatware cache
It's building the dalvik cache, just like every Rom does when you wipe dalvik cache, or factory reset as dalvik is on the data partition.
AT&T are just freaking amateurs, they didn't make the boot animation loop at all... so once it's done and is building the cache. It appears to have just stopped there.
So I installed Nokia Z Launcher and everything worked fine, but when I rebooted my Note 2, I got stuck in a boot loop.
I read elsewhere that someone stopped this by going into recovery mode and clearing data. I don't see an option for this in CWM Reovery except "wipe data/factory reset.
Would wipe cache partition or wipe dalvik cache solve this boot loop or would this just make things worse?
I was trying to keep from reflashing if possible.
MrNetwork said:
So I installed Nokia Z Launcher and everything worked fine, but when I rebooted my Note 2, I got stuck in a boot loop.
I read elsewhere that someone stopped this by going into recovery mode and clearing data. I don't see an option for this in CWM Reovery except "wipe data/factory reset.
Would wipe cache partition or wipe dalvik cache solve this boot loop or would this just make things worse?
I was trying to keep from reflashing if possible.
Click to expand...
Click to collapse
cache/dalvik probably won't fix your issue, most likely will have to hard reset, or odin
I had finally had to do a factory reset. I am glad I back up every night with Titanium Backup. The only thing that hasn't restored properly is Gmail. I no longer get emailed pushed or get notifications. I have to manually check for mail. Other than that, everything is good.