Develop Bugs

[SOLVED] Installation Problem

Hi folks,
I did rooted my arc 3 months back and i can still access my super user, yesterday i installed cwm for xperia phones successfully.
I tried to flash 4.0.4_Xperia-S_deodexed-V2.5beats using CWM(previous version stock 2.3.5). I did cleared the cache and all the stuff, but now i cannot boot to OS or CWM or anything, literally i can't use my phone.
It just shows up screen with Sony Ericsson Logo goes no where.
Please help me guys I want to install any custom ROM on my phone please suggest me
Thank you so much guys.

You have probably wiped data too which is a factory reset. Run your back up or reflash.

XperienceD said:
You have probably wiped data too which is a factory reset. Run your back up or reflash.
Click to expand...
Click to collapse
Thank you my friend, are there any guides to reflash, will it surely works if i reflash.
forgive me if i am asking too many questions.

badriinvenkat said:
Thank you my friend, are there any guides to reflash
Click to expand...
Click to collapse
Plenty, see the stickys in the general section.

XperienceD said:
Plenty, see the stickys in the general section.
Click to expand...
Click to collapse
i reflashed an old version 2.3.4 and every thing is working fine, got an OTA update on phone and downloaded the update using wifi and it turned off as the part of update process, thats it and never turned on :crying::crying::crying:
i tried again to flash the same version but never worked!!! what can i do now

Flash THIS with the flastool and report back.

i tried that just now and it does the same result, after flashing the .ftf file it says to take the cable off and turn it on. It never turns on but when i press the power button it blinks the green LED (donno what it does mean!!)
any ways thanks for your suggestion.

Try THIS instead, if that doesn't work then not sure.

XperienceD said:
Try THIS instead, if that doesn't work then not sure.
Click to expand...
Click to collapse
Thank yo so much my friend you really helped me a lot, sorry for keep asking you(I mean i should have searched everywhere before asking you)
My phone is working back :victory::victory::victory::victory::victory:

badriinvenkat said:
Thank yo so much my friend you really helped me a lot, sorry for keep asking you(I mean i should have searched everywhere before asking you)
My phone is working back :victory::victory::victory::victory::victory:
Click to expand...
Click to collapse
Excellent. Sometimes we just can't see the wood for the trees, myself included.

[Q] unfortunately the process.android.process.acore has stopped

Hey guys so i know there are plenty of threads going over this issue and even a official t mobile page explaining how to fix the issue but I'm all out of options. So i was running the stock rooted rom and saw a beats installer app in the market and decided to check it out. I proceeded with the process but when i got to the end and the app said the phone will now reboot the phone froze. I waited but after awhile decided to reboot the phone. I rebooted and the phone stayed stuck on the Samsung screen. I then proceeded to flash the stock rom i found online ( i think it was adroid police ) and rebooted. I noticed the phone didnt wipe though. I didnt have to log into google or anything. When i got back home, everything and its mom started to fail. Pop up screens so bad that i had to pull the battery and went back into odin and decided to oding the stock rooted rom. Got back to the home screen ( my phone didnt wipe after odin either ) and everything was failing still. I decided i better factory reset. That helped alot. After all day of getting my phone back together and loosing game data, i went to play virtual city and that wouldnt load. I gave up and uninstalled. I then went to join my contacts and after deleting contacts my phone pops the same error. What now? Hoping someone knows something i dont. Thanks guys.

If anyone cares, I did another factory reset but from the settings menu instead of recovery and the phone seems to be running great so far. Keeping my fingers crossed
Sent from my SGH-T999 using Tapatalk 2

knarfies said:
If anyone cares, I did another factory reset but from the settings menu instead of recovery and the phone seems to be running great so far. Keeping my fingers crossed
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.

I'm also getting the same error. I started getting it after trying to root with the odin procedure with no flash counter increase. when i flash the stock image back it works normally, but i want root!

dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
Googled your post, worked for me on the Tab 10.1 after flashing a CM10 update without clearing user data. Thanks!

dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
This also worked for me! just curious how did you know to clear contact and contact storage ?
Thanks again now to import my contacts back...

dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
Thanks, you saved my bacon! I thought I would have to delete all my user data, but I did this after a flash and it worked perfectly. Appreciate your post!

dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
Had the same problem, and your advice worked like a charm.
Thanks a lot.

No problem. Glad it helped.

[/COLOR]
knarfies said:
If anyone cares, I did another factory reset but from the settings menu instead of recovery and the phone seems to be running great so far. Keeping my fingers crossed
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Love you <3

Just wanted to say thanks for the post. Helped me as well when I flashed the new AOKP rom on my VZ Galaxy Nexus. :good:

Android bug
The problem occurs due to a bug in android , when you have saved a contact's birthday as 29 Feb, which occurs only in leap years. temporary solution is to change the birth date to any other date until google releases a fix .

I get the error with google failing more than I'd like to count...

knarfies said:
If anyone cares, I did another factory reset but from the settings menu instead of recovery and the phone seems to be running great so far. Keeping my fingers crossed
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for this! Solved the error message on my S2

dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
Dear sir, you just made my day! i was so freaked out

THANK YOU!

Hi
I have this problem "unfortunately the process android.process.acore has stopped".When ever I 'Power ON or Restart' my SKyrocket(I727)..This issue started after flashing the new JB ROM--][UCLL3] SUPERLITE SAMSUNG JB 4.1.2 > (http://forum.xda-developers.com/showthread.php?t=2066468)
I have already tried with "clearing data on contact and contact storage in app manager"..Any other tips?
BR
My device was earlier running on SUPERLITE CM10 JB4.1.2 RoM | V8.0 (http://forum.xda-developers.com/showthread.php?t=1862244)

Same Issue
knarfies said:
If anyone cares, I did another factory reset but from the settings menu instead of recovery and the phone seems to be running great so far. Keeping my fingers crossed
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I had that issue. Took me a while to figure out that I had forgotten to clear all my caches when I flashed the new 4.2.1 AOKP ROM. Cleared the caches and the problem was resolved.
-ss

dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
I also did this stuff..but,this 'data' on 'contact/contact storage' never gets cleaned...as soon as clearing,I go back and check again,it contains the 'data' agin..What do i 'miss'?

dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
Worked for me too! thanks!

I'm so close to downgrading....

Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.

Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.

Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...

If you updated from 4.1 to 4.2 without a full wipe there's potential for a lot to go wrong. There could be some app running as a service that isn't fully compatible with 4.2 causing your issues.
With that being said, I would try fully resetting the device, no need to re-flash the stock image because it's already in place on the device anyway.
Install apps that are known to work on 4.2 ONLY. Then, you can begin testing to see if it becomes stable. After that, do what you want.

mortenmhp said:
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Click to expand...
Click to collapse
Thanks, I'll give a try!

cymru said:
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
Click to expand...
Click to collapse
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.

g8who said:
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
Click to expand...
Click to collapse
Yeah, it's as if someone should add a search button to the forum :silly:

cymru said:
Yeah, it's as if someone should add a search button to the forum :silly:
Click to expand...
Click to collapse
But searching takes time...
And it's not like you can make it through a page in either General or Q&A without tripping over a 4.2 whine thread.

g8who said:
Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Click to expand...
Click to collapse
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.

jpildave said:
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
Click to expand...
Click to collapse
This guy is correct MMuzzy has been the most stable for Vzn Gnex. I only have a qualm with the GPS, but that's every phone
Sent from my Galaxy Nexus using xda premium

Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1

Only bluetooth problem
LeBaldi said:
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Click to expand...
Click to collapse
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again Also... sometimes when the phone goes into sleep mode it disconnect the connection with handset... It never happen in 4.1.
I downloaded the factory image of 4.2.1 from Google and flash it... still the same. I saw people saying a clean install... Should I do another kind of install other than I did?
Can someone please tell me if got this kind of bluetooth problem and have solved it? How?
Thanks

abcorp said:
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again
Click to expand...
Click to collapse
i have also encountered that behaviour, gets greyed out while "Turning off".

[Q] stuck in bootloop with no back up plz help!!!

i think im out of luck here and this is the first time this has happened to me. i recently rooted my note 2 using the toolkit that was in the thread for all variants. i used the mack rom with the perseus kernel. then i recently read that they recommend updating the kernel. i downloaded the kernel and for got about clearing the cache and dalvic cache before flashing. i rebooted and now stuck in bootloop with no backup. i just want to get it to work again but i got a bad feeling that there is nothing i can do about this since i can get anything to my internal memory. twrp is my recovery and they dont mount the sd card yet. any suggestions?

wittmannj said:
i think im out of luck here and this is the first time this has happened to me. i recently rooted my note 2 using the toolkit that was in the thread for all variants. i used the mack rom with the perseus kernel. then i recently read that they recommend updating the kernel. i downloaded the kernel and for got about clearing the cache and dalvic cache before flashing. i rebooted and now stuck in bootloop with no backup. i just want to get it to work again but i got a bad feeling that there is nothing i can do about this since i can get anything to my internal memory. twrp is my recovery and they dont mount the sd card yet. any suggestions?
Click to expand...
Click to collapse
I might suggest holding vol-down/home/power together while b-looping, see if you could get into DL mode, flash something in odin to get back to stock at least, start over. or try to see if that will work with recovery, reflash the kern. but you may be SOL on your current data.
and there's always batt pulling before trying to get to recovery/DL mode, but i try to avoid it when possible. but sometimes that's all ya get.

thank you
kingdazy said:
I might suggest holding vol-down/home/power together while b-looping, see if you could get into DL mode, flash something in odin to get back to stock at least, start over. or try to see if that will work with recovery, reflash the kern. but you may be SOL on your current data.
and there's always batt pulling before trying to get to recovery/DL mode, but i try to avoid it when possible. but sometimes that's all ya get.
Click to expand...
Click to collapse
thank you very much... i just got done down that exact thing with the odin program it saved my butt!!!! this was my first post (been to shy) and definatly wont be my last. and once again thank you for helpling out fortunately for me i was able to get it done!

Download Mode is Samsung's gift to humanity. They created as penance for being so slow rolling out Android OS updates.
Sent from my SPH-L900 using Tapatalk 2

Please read forum rules before posting
Rule 15 tells you where to post if you are confused
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

wittmannj said:
thank you very much... i just got done down that exact thing with the odin program it saved my butt!!!! this was my first post (been to shy) and definatly wont be my last. and once again thank you for helpling out fortunately for me i was able to get it done!
Click to expand...
Click to collapse
welcome to the community! and good job posting the info that someone would need to be able to help, it's important to give the details on how one arrives at the problem so someone can troubleshoot.

Unfortunately settings has been stopped?

What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.

I'm sure I'm not the first one and only one who got this message. Could anybody please help?
Thank you very much!

testrider said:
What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.
Click to expand...
Click to collapse
I don't know about stock, but flashing a custom ROM should fix it. (Try reflashing stock 4.1.2)
Smack that thanks button If I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.

Irwenzhao said:
I don't know about stock, but flashing a custom ROM should fix it. (Try reflashing stock 4.1.2)
Smack that thanks button If I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.
Click to expand...
Click to collapse
I don't know why flashing a custom ROM would fix it, as I did not have this before and I did not change
my ROM...

testrider said:
I don't know why flashing a custom ROM would fix it, as I did not have this before and I did not change
my ROM...
Click to expand...
Click to collapse
U could try reflashing stock rom if u don't want a custom one.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.

testrider said:
What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.
Click to expand...
Click to collapse
I would just re-flash a stock rom. Maybe stock+root. Sorry I've rooted many times and never had that issue on a stock rom.

0.o said:
I would just re-flash a stock rom. Maybe stock+root. Sorry I've rooted many times and never had that issue on a stock rom.
Click to expand...
Click to collapse
Thanks for the reply. It'll be great if I can find out why then I can fix the root cause. We really don't want every time we have a problem we just do factory reset/wipe all/reflash and pray for the best?
It really seemed that there was no answer. I googled it and saw lots of people having the same problem but no solution.
I may have to flash the stock rom but I don't think that will fix the problem. Mine is running a stock ROM

testrider said:
Thanks for the reply. It'll be great if I can find out why then I can fix the root cause. We really don't want every time we have a problem we just do factory reset/wipe all/reflash and pray for the best?
It really seemed that there was no answer. I googled it and saw lots of people having the same problem but no solution.
I may have to flash the stock rom but I don't think that will fix the problem. Mine is running a stock ROM
Click to expand...
Click to collapse
The only way to get to the root problem is run a logcat of the error. We could guess all day long. I mean did you freeze anything, delete anything, flash a mod, use an xposed module? There are hundreds of things that could be wrong, but without a logcat it would take a long time to guess your specific error.
Sent from my SGH-T889 using xda app-developers app

kintwofan said:
The only way to get to the root problem is run a logcat of the error. We could guess all day long. I mean did you freeze anything, delete anything, flash a mod, use an xposed module? There are hundreds of things that could be wrong, but without a logcat it would take a long time to guess your specific error.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I'll remember to get a logcat next time. Right after the message popped up, correct?

testrider said:
Thanks. I'll remember to get a logcat next time. Right after the message popped up, correct?
Click to expand...
Click to collapse
Yep right after it happens. If there is something that triggers it. Reboot, to clear the log, then trigger the fc and pull log
Sent from my SGH-T889 using xda app-developers app