Related
Hey guys,
I'm running the Octane ROM on my SGS4G, and suddenly both my home and search touch keys stopped functioning. However, they ARE triggering haptic feedback (a vibration in the phone when pressed)
Does anyone know what causes this and what's a common trouble shooting route?
I updated my binary in super user and updated busybox...nothing changed.
Also, I don't know if this is related to the problem but it happened at the same time: text msg notifications are permanently as if the phone is on silent; no sound or vibration. Just a status bar icon.
Thanks in advance to anyone who can help, this phone is my only daily.
Sent from my SGH-T959V using XDA App
Have you rebooted the phone? If so, I'd suggest doing a backup then performing a factory data reset.
Yea I rebooted several times..
could I just wipe the dalvik?
If I only do that, what information is lost on my phone?
Also the update from busy box said it might require I do a package reinstall "without" a factory wipe for the update to take effect... Any suggestions on that?
Sent from my SGH-T959V using XDA App
Stafaa said:
Yea I rebooted several times..
could I just wipe the dalvik?
If I only do that, what information is lost on my phone?
Also the update from busy box said it might require I do a package reinstall "without" a factory wipe for the update to take effect... Any suggestions on that?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
You could always try wiping caches first. No data loss that way. The Davlik cache will rebuild itself over time.
I'm nto sure about BusyBox, though. Maybe someone else has an idea?
What about the cache partition?
I guess my question is, what exactly are you wiping when you wipe the dalvik and when you wipe the cache partition?
and is it a safe practice for when strange problems like this arise?
Just wiping the cache.completely safe and the first thing to try after a reboot.also I would suggest fixing permissions when clearing the cache
Sent from my SGH-T959V using Tapatalk
Well I found the answer to what they both are Here
Figured I'd post it for anyone who every comes across this thread.
But thank you for going into more detail about it Somairotevoli.
where is it i fix permissions? In super user you mean?
And i just finished doing a full wipe =/
fixed the problem...but just sucks. Im glad i removed the SD card before hand, I think it tried to format it.
Does a factory wipe touch any SD files?
Stafaa said:
Well I found the answer to what they both are Here
Figured I'd post it for anyone who every comes across this thread.
But thank you for going into more detail about it Somairotevoli.
where is it i fix permissions? In super user you mean?
And i just finished doing a full wipe =/
fixed the problem...but just sucks. Im glad i removed the SD card before hand, I think it tried to format it.
Does a factory wipe touch any SD files?
Click to expand...
Click to collapse
Fix permissions in the advanced option of cwm
And no factory reset does not wipe sd unless you tell it to when you're doing it from your settings menu
Sent from my SGH-T959V using XDA App
ah, gotcha.
Wish I woulda have tried that before wiping.
Another question: After the wipe, I lost all the fonts that were originally there after I first installed Octaine ROM.
I'm thinking I should just reinstall the package, but I'm afraid I cant remember if I had to disable VOODOO lagfix first and whether or not i still have to change the mounting points before i reinstall the rom..
Stafaa said:
ah, gotcha.
Wish I woulda have tried that before wiping.
Another question: After the wipe, I lost all the fonts that were originally there after I first installed Octaine ROM.
I'm thinking I should just reinstall the package, but I'm afraid I cant remember if I had to disable VOODOO lagfix first and whether or not i still have to change the mounting points before i reinstall the rom..
Click to expand...
Click to collapse
Glad you got it working though sucks you had to wipe everything. To be safe I would disable voodoo though I do not know if it's necessary. Definitely go into CWM and re-check the mounts first before flashing.
Well, unfortunately, after a full wipe... everything worked fine for one day... then suddenly the phone froze and restarted. After reboot, some apps had the android image on their icon and ALL OVER my wallpaper was a skull and cross bones image...cascaded in rows and columns all over the background..
and ofcourse.. my home and search buttons are non-functional once again...
What does this mean??
Stafaa said:
Well I found the answer to what they both are Here
Figured I'd post it for anyone who every comes across this thread.
But thank you for going into more detail about it Somairotevoli.
where is it i fix permissions? In super user you mean?
And i just finished doing a full wipe =/
fixed the problem...but just sucks. Im glad i removed the SD card before hand, I think it tried to format it.
Does a factory wipe touch any SD files?
Click to expand...
Click to collapse
I'm running the Octane rom too, and have started having problems with all four buttons, but mainly the outside settings and search ones. Other roms do the same for me now, so I don't think it's the problem. I have fully wiped, reformatted, fixed permissions, you name it.
It dosen't seem to matter what happens, they still resist working properly. So are you saying that doing a wipe/reinstall/permission fix did it for you? I can't tell if it's a physical thing or a software thing, but I'm leaning more toward software.
Stafaa said:
Well, unfortunately, after a full wipe... everything worked fine for one day... then suddenly the phone froze and restarted. After reboot, some apps had the android image on their icon and ALL OVER my wallpaper was a skull and cross bones image...cascaded in rows and columns all over the background..
and ofcourse.. my home and search buttons are non-functional once again...
What does this mean??
Click to expand...
Click to collapse
You should probably re download your desired rom, do a full wipe (data, cache, and dalvik) and re flash. this sucks but should work. Did you by chance ever flash a kf series 2.3.3 ROM?
Sent from my SGH-T959V using XDA App
Stafaa said:
Well, unfortunately, after a full wipe... everything worked fine for one day... then suddenly the phone froze and restarted. After reboot, some apps had the android image on their icon and ALL OVER my wallpaper was a skull and cross bones image...cascaded in rows and columns all over the background..
and ofcourse.. my home and search buttons are non-functional once again...
What does this mean??
Click to expand...
Click to collapse
After the wipe did you install a new ROM or stay on Octane? Maybe try wiping & install Raver's KJ6 stock via Odin or CWM. Run stock for a few days and see if the problems persist.
Sent from my SGH-T959V using XDA App
Hi there. I currently am running the Legend 2 ICS Edition ROM for Infuse 4G. I just noticed there is a new update Legend 3 ICS. If I want to keep all my files and apps, do I just flash the Update file (instead of the Full Wipe file)? And do I need to go through the same process, clear cache, dalvik cache, etc.? Probably no need to wipe data and factory reset.
Any help is much appreciated! Thanks.
Yakusoya said:
Hi there. I currently am running the Legend 2 ICS Edition ROM for Infuse 4G. I just noticed there is a new update Legend 3 ICS. If I want to keep all my files and apps, do I just flash the Update file (instead of the Full Wipe file)? And do I need to go through the same process, clear cache, dalvik cache, etc.? Probably no need to wipe data and factory reset. Any help is much appreciated! Thanks.
Click to expand...
Click to collapse
I suggest do a full wipe, if you want to keep your app, "tibu" titanium backup is great and well worth app, buy it...I did and worth every dime. IMHO Tibu will and can backup your apps and restore them.
So I suggest get tibu, backup your apps, do a full wipe install Leg3 go back to Gplay download/install tibu back on, then use the program to restore your apps only in this case.
Plus tibu can do a full backup of your data & apps, say you find your DD but want to test other ROMs, use tibu to backup data & apps, go test the another ROM, and want to come back to your DD ROM, you can then do a full data & app restore...plus there are lots of YouTube vid on Titanium Backup app.
Yakusoya said:
Hi there. I currently am running the Legend 2 ICS Edition ROM for Infuse 4G. I just noticed there is a new update Legend 3 ICS. If I want to keep all my files and apps, do I just flash the Update file (instead of the Full Wipe file)? And do I need to go through the same process, clear cache, dalvik cache, etc.? Probably no need to wipe data and factory reset.
Any help is much appreciated! Thanks.
Click to expand...
Click to collapse
You can do the update and keep your files, which is the reason for the update. Though, like Bigjoe says, a full wipe is always prefered, but not necessary.
Yakusoya said:
Hi there. I currently am running the Legend 2 ICS Edition ROM for Infuse 4G. I just noticed there is a new update Legend 3 ICS. If I want to keep all my files and apps, do I just flash the Update file (instead of the Full Wipe file)? And do I need to go through the same process, clear cache, dalvik cache, etc.? Probably no need to wipe data and factory reset.
Any help is much appreciated! Thanks.
Click to expand...
Click to collapse
The reason why everyone suggests a full wipe is so that you dont potentially run into any problems after the flash. ie flash not working, or camera wont load... little things like that that make it hard to narrow down problems. One of the main things people are going to ask is did you wipe before you installed? It helps to eliminate and remnants of left over roms so that you dont have any issues with the new rom. Its called a Bad flash.
I hope i answered your question!
Thanks for all the replies! So whether it is the full wipe ROM or the update ROM, both go through the same procedure of booting into CWM first? I will try Tibu for app backup! :good:
Stuck at blue loading loop
Hey, I am new so bare with me, I just flashed this rom onto my Infuse 4g and it seems to be restarting itself and looping to the Blue Android/Dust loading screen. It seems to fix with a fresh install of the rom, but shortly starts after everything seems fine. Please help!
araidis said:
Hey, I am new so bare with me, I just flashed this rom onto my Infuse 4g and it seems to be restarting itself and looping to the Blue Android/Dust loading screen. It seems to fix with a fresh install of the rom, but shortly starts after everything seems fine. Please help!
Click to expand...
Click to collapse
Try doing an odin or hemdall back to stock with partitioning, then flash the full wipe rom.
http://forum.xda-developers.com/showthread.php?t=1524081
http://forum.xda-developers.com/showthread.php?t=1705260
So I've been using your latest release (full wipe Legend v3) and I did factory reset, clear cache and dalvik cache, fixed permissions, etc. The phone is occasionally laggy now, usually when I open web browser it would stay on the white screen a several seconds. Sometimes, when I open my phone, it would stay on the black screen even though I never turned it off and it still has battery. So I had to long-press the button to restart. I've already rebooted and shut down numerous times but these problems still persist.
Also, bluetooth doesn't work for me. When I enable it from settings, the "Turn bluetooth on" checkbox stays unchecked and does nothing.
Should I reflash again? I did to a Titanium Backup to restore apps and settings... Any help is appreciated! Thanks.
turkish ?
i wonder if turkish is included or not ?
turnazurna said:
i wonder if turkish is included or not ?
Click to expand...
Click to collapse
With any rom, you should be able to install More Locale 2 from the Play Store to get support for Turkish (and many other languages).
Yakusoya said:
So I've been using your latest release (full wipe Legend v3) and I did factory reset, clear cache and dalvik cache, fixed permissions, etc. The phone is occasionally laggy now, usually when I open web browser it would stay on the white screen a several seconds. Sometimes, when I open my phone, it would stay on the black screen even though I never turned it off and it still has battery. So I had to long-press the button to restart. I've already rebooted and shut down numerous times but these problems still persist.
Also, bluetooth doesn't work for me. When I enable it from settings, the "Turn bluetooth on" checkbox stays unchecked and does nothing.
Should I reflash again? I did to a Titanium Backup to restore apps and settings... Any help is appreciated! Thanks.
Click to expand...
Click to collapse
My bet is the tibu restore of your settings is what is causing the issues, I've had problems and have known others that had problems when restoring system settings with tibu, especially if the tibu backups were done on another rom.
crt60 said:
My bet is the tibu restore of your settings is what is causing the issues, I've had problems and have known others that had problems when restoring system settings with tibu, especially if the tibu backups were done on another rom.
Click to expand...
Click to collapse
I only started using tibu when I had Legend ICS v2 and then I immediately upgraded to v3 using the full wipe ROM. And then I restored all apps and settings. I'll try wipe and re-flash without restoring any settings in tibu. But honestly, I only wanted to backup my widget and screen settings (such as app shortcuts on home screens) but tibu didn't back that up.
Yakusoya said:
I only started using tibu when I had Legend ICS v2 and then I immediately upgraded to v3 using the full wipe ROM. And then I restored all apps and settings. I'll try wipe and re-flash without restoring any settings in tibu. But honestly, I only wanted to backup my widget and screen settings (such as app shortcuts on home screens) but tibu didn't back that up.
Click to expand...
Click to collapse
I would try reflashing to stock, then reflashing the rom again, are you converting to ext4 at all or just using rfs?
crt60 said:
I would try reflashing to stock, then reflashing the rom again, are you converting to ext4 at all or just using rfs?
Click to expand...
Click to collapse
I'm a noob so I don't know what those are. :laugh: But I've only flashed ZEUS final and then Legend ICS v2 and v3. Full wiped and cleared cache on all those flashes.
I've reflashed to stock and then back to Legend 3 without restoring anything. It is all better now, very snappy. The bluetooth can be turned on now but for some reason, it doesn't detect my Jabra headset no matter how many times I scan. But it detects my Macbook Pro...
I was having this issue where I couldn't make calls or get my contacts to come up without seeing
Unfortunately, the process android.process.acore has stopped
keep crashing. I finally decided it was best to RUU the 1.85 image and start from scratch. Well that didn't solve the problem! Any ideas what is going on? I can't bring up my contacts, make phone calls, and my google acct won't sync contacts. Any ideas anyone?
google.com
see if that works huh
http://www.shaneycrawford.com/2011/...d-process-acore-problem-on-an-android-device/
Your Android device (tablet, phone, Android TV) gives you the following message.
“The process android.process.acore has stopped working.”
The solution:
Settings –> Applications –> Manage Applications –> All (button on the top that lets you see all applications) –> scroll down to “Contacts Storage” –> Click on “Clear Data”.
This worked on my Android TV and I have seen reports of it working on other Android devices.
Click to expand...
Click to collapse
expertzero1 said:
google.com
see if that works huh
http://www.shaneycrawford.com/2011/...d-process-acore-problem-on-an-android-device/
Click to expand...
Click to collapse
i tried all that already. clearing all the data off apps. factory wipes, master resets. ran out of ideas to try.
I am in the same boat right now. Was having some different issues so I decided to RUU 1.85 and then rooted and unlocked. After installing cleanrom, I start getting phone, contacts, and messages to start crash with no error message. After a while it started giving android.process.acore errors. I've tried:
-Factory wipe, cache and dalvik wipe
-Re-flashing the ROM
-Flashing a different ROM
-clearing app data for contacts, Google framework services, etc.
-fixing permissions
All with no fix. Next step for me was RUU again, but it sounds like that won't do it. Any thoughts out there would be appreciated.
Sent from my HTC One XL using xda app-developers app
this happened when i first installed clean rom 4.0. I immediately re-installed 4.0 and it fixed it. strange... I see some devs say you must wipe 3 times before installing any rom. its worth a try. Also maybe use a different recovery than you have been using. most important thing is to re-download the rom and check the MD5. dude the other day downloaded the rom 6 times with different MD5 before he got a good download. If that is the case, check the memory on your computer as well as hard drive. either of those bad could be corrupting the download. Good luck.
nugzo said:
this happened when i first installed clean rom 4.0. I immediately re-installed 4.0 and it fixed it. strange... I see some devs say you must wipe 3 times before installing any rom. its worth a try. Also maybe use a different recovery than you have been using. most important thing is to re-download the rom and check the MD5. dude the other day downloaded the rom 6 times with different MD5 before he got a good download. If that is the case, check the memory on your computer as well as hard drive. either of those bad could be corrupting the download. Good luck.
Click to expand...
Click to collapse
+1..thats why i always verify md5
Sent from my HTC One X using XDA
Verified the MD5 on the ROM, all checked out there. I'm re-downloading the RUU from a different mirror, so we'll see how that goes. May give switching recoveries a try in the meantime.
Well I was able to get mine to work. I switched back to CWM from TWRP, wiped and installed CleanROM (had Nocturnal running). After the wipe and then flash of CleanROM, I was shocked to see the Nocturnal boot animation. I figured something had gone screwy, and I wiped 5 times in recovery, and then installed CleanROM on top of itself 2 extra times. Rebooted and now all is working again. Not sure what the main issue was from the beginning, but hope this helps you out a little OP. Maybe run RUU again?
ddebart2 said:
Well I was able to get mine to work. I switched back to CWM from TWRP, wiped and installed CleanROM (had Nocturnal running). After the wipe and then flash of CleanROM, I was shocked to see the Nocturnal boot animation. I figured something had gone screwy, and I wiped 5 times in recovery, and then installed CleanROM on top of itself 2 extra times. Rebooted and now all is working again. Not sure what the main issue was from the beginning, but hope this helps you out a little OP. Maybe run RUU again?
Click to expand...
Click to collapse
i'll try switching back to cwm from twrp. what version of cwm worked for you?
trant01 said:
i'll try switching back to cwm from twrp. what version of cwm worked for you?
Click to expand...
Click to collapse
ok well after switching back to cwm and doing wipes for 5 times before installing cleanrom 4.1 it finally worked. can make calls and text without having that error. thanks for the input!!
Thanks for this post. Had the exact same issue. Reverted to the 1.85 RUU and still had it. CWM + Flashing a rom a couple of times and wiping multiple times did the trick.
Glad to be of help. I was stressing over this issue for about 2 days myself. Good to hear it helped someone else too.
Sent from my HTC One X using xda app-developers app
I'm not a dev, but it's obvious to me something is wrong.
I re-flashed the eaglesblood ICS rom using clockworkmod recovery v.5.8.1.3 (touch version)
everything seemed okay.
until i started putting apps back on my phone with app backup and restore.
I was getting "process syystem has stopped responding" all over the place.
Then the phone crashed.
it keeps booting, only three apps seem to be running that show themselves in the taskbar, Groove IP, GV SMS integration, and Battery Notifier (Big Text)
It sits there, one one of the home screens, LW animating slowly as it will.. then the phone reboots for no reason.
I installed 4 or 5 different logcat apps but i can't make heads or tails of them
and adb logcat > logcat.txt just spits out this :
/sbin/sh: exec: line 1: logcat: not found
dmesg spits out the log i'm attaching.
Can anyone help me? If i can save the log from one of the logcat apps, will that help?
I'd rather not have to reflash and re-install apps AGAIN.
Where you flashing EB 4.0.4 from gingerbread ?
In any case a full wipe and reflash of the ROMs would work fine. Then reflash the appropriate gapps, But when restoring the apps using TB just restore at apps and not their data. They sometimes don't play well.
I had a similar issue when I tried flashing the 4.2 gapps on 4.1.2 keyboard would crash everytime and any app that uses even one of the google services would crash right away.
I cleared dalvic cache did a dirty flash over my existing 4.1.2 , reflashed the 4.1.2 gapps then I fixed permissions and in was good to go.
Sent from my LG-P999 using xda app-developers app
Barracuda1101 said:
Where you flashing EB 4.0.4 from gingerbread ?
In any case a full wipe and reflash of the ROMs would work fine. Then reflash the appropriate gapps, But when restoring the apps using TB just restore at apps and not their data. They sometimes don't play well.
I had a similar issue when I tried flashing the 4.2 gapps on 4.1.2 keyboard would crash everytime and any app that uses even one of the google services would crash right away.
I cleared dalvic cache did a dirty flash over my existing 4.1.2 , reflashed the 4.1.2 gapps then I fixed permissions and in was good to go.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
so a dirty reflash and fix permissions might help?
Funny enough, after posting that, and hitting reboot on CWM recovery.. the phone came up with the cord plugged in, and seems to be stable for now.
Uhm. i was flashing from.... heck if i know, i've tried a bunch of roms.
the phone INITIALLY was 2.3.4
back when i started.. months ago.
Eve_brea said:
so a dirty reflash and fix permissions might help?
Funny enough, after posting that, and hitting reboot on CWM recovery.. the phone came up with the cord plugged in, and seems to be stable for now.
Uhm. i was flashing from.... heck if i know, i've tried a bunch of roms.
the phone INITIALLY was 2.3.4
back when i started.. months ago.
Click to expand...
Click to collapse
grrrrrrrrrr. i'm back at the crashing behavior
I see "equalizer activated " then the phone gets stuck... that same "equalizer activated" thing came up when i added speakerboost... wonder if it's the cause..
Eve_brea said:
grrrrrrrrrr. i'm back at the crashing behavior
I see "equalizer activated " then the phone gets stuck... that same "equalizer activated" thing came up when i added speakerboost... wonder if it's the cause..
Click to expand...
Click to collapse
*grumble* damn sun-downer phone. SO all night it was crashing.. So i finally got irritated when i went to bed, yanked the battery out and plopped it on my night-stand by my fan.
This morning i put the battery in, turn it on, and it seems stable.
What the heck?!
logs.
So... between all the log apps i've played with i have a bunch of logs.. if anyone could look them over and tell me if they see a problem, i'd appreciate it.
Re-download Rom+Gapps
Place on SD card
Re-nvflash cwm recovery 5.0.2.0
Wipe data/cache/davlk/battstats/format system
Install rom+gapps
Wipe cache/davlk/battstats
Fix permissions
Reboot
Using touch is sometimes buggy, 5.0.2.0 is most stable. Restoring apps/data is sometimes a messes things up.
Sent from my LG-P999 using xda app-developers app
Guys, I'm running Purity room with Franco kernel and PA GAPPS. I've had this problem recently, where my room is running perfectly. But when ever I do a factory reset through CWM 6.0.4.5 and reboot, the error "phone had stopped" pops up and all I can do is long press the power button to reboot into recovery and restore a backup.
Any ideas guys?
Sent from my Nexus 5 using XDA Premium 4 mobile app
I would suggest redownloading purity and Gapps and franco kernel (You just never know). Flash them individually and boot into the phone and see which one is causing you problems; after a factory reset with wiping cache/ dalvik. If this does not work try a different ROM (I always keep a stock rooted/deodexed on my phone), if it still persist I would do a full wipe start over from scratch.
mistahseller said:
I would suggest redownloading purity and Gapps and franco kernel (You just never know). Flash them individually and boot into the phone and see which one is causing you problems; after a factory reset with wiping cache/ dalvik. If this does not work try a different ROM (I always keep a stock rooted/deodexed on my phone), if it still persist I would do a full wipe start over from scratch.
Click to expand...
Click to collapse
Thanks for the reply, however, Ive already done the following:
1- Wipe Data/Factory reset > Reboot: "Phone has stopped" Error
2- Wipe Data/Factory reset > Install Purity (with/without GAPPS) > Reboot: "Phone has stopped" Error
3- Wipe Data/Factory reset > Install Puroty (with/without Franco kernel) > Reboot: "Phone has stopped" Error
4- Wipe Data/Factory reset > Installed other ROM> Reboot: "Phone has stopped" Error
5- Wipe Dialler/SIM toolkit > Wipe Data/Factory reset > Reboot: "Phone has stopped" Error
Cache/Dalvik Cache cleared every time.
The old backup still works, I even dirty flashed the new Purity version over it and works ok. The problem only arises after Wipe Data/Factory Reset.
Couldn't find any other solutions, any other suggestions?
Well I would say that if it works after your backup and then dirtyflashing a newer version of purity then leave it go, this is probably not the best option but if it works.... My other option in my previous post was to completely wipe the phone and start over as in back to stock and start over.
Something could've corrupted, who knows, maybe something went wrong with your installation of a bootloader. You said you are running CWM 6.x.x.x, try flashing the stock bootloader and then reflashing a different bootloader I suggest TWRP but there are other options. I used CWM on my nexus and it did it's purpose but when I flashed TWRP onto my nexus 5 it was just more clean and it had touch, go figure.
I'd try using Titanum Backup and clearing the data of the phone, dialer storage, etc after the reset. Had a similar situation the other day that doing that resolved. Hope that helps. Problems like this can be annoying.
Just thought of this: Could be your recovery. Might not be wiping things correctly. If what I suggested doesn't help, then try TWRP. I've found very few things that TWRP is not better at vs CWM (on officially supported phones).
OK try to install cyanogen mode and let me know what happened
Sent from my Opal 800 using xda app-developers app
mistahseller said:
Well I would say that if it works after your backup and then dirtyflashing a newer version of purity then leave it go, this is probably not the best option but if it works.... My other option in my previous post was to completely wipe the phone and start over as in back to stock and start over.
Something could've corrupted, who knows, maybe something went wrong with your installation of a bootloader. You said you are running CWM 6.x.x.x, try flashing the stock bootloader and then reflashing a different bootloader I suggest TWRP but there are other options. I used CWM on my nexus and it did it's purpose but when I flashed TWRP onto my nexus 5 it was just more clean and it had touch, go figure.
Click to expand...
Click to collapse
Will try resetting and well then install twrp ... let's see. Can't let it be coz I need to be able to test other roms and stuff.
Sent from my Nexus 5 using XDA Premium 4 mobile app
es0tericcha0s said:
I'd try using Titanum Backup and clearing the data of the phone, dialer storage, etc after the reset. Had a similar situation the other day that doing that resolved. Hope that helps. Problems like this can be annoying.
Just thought of this: Could be your recovery. Might not be wiping things correctly. If what I suggested doesn't help, then try TWRP. I've found very few things that TWRP is not better at vs CWM (on officially supported phones).
Click to expand...
Click to collapse
Yeah that would be an easier option to try before resetting... Will try twrp as well.
Sent from my Nexus 5 using XDA Premium 4 mobile app
You can install any ROM it does not have to be cyanogen mod.
why is that the goto for everyone?.....
---------- Post added at 12:18 PM ---------- Previous post was at 12:18 PM ----------
es0tericcha0s said:
I'd try using Titanum Backup and clearing the data of the phone, dialer storage, etc after the reset. Had a similar situation the other day that doing that resolved. Hope that helps. Problems like this can be annoying.
Just thought of this: Could be your recovery. Might not be wiping things correctly. If what I suggested doesn't help, then try TWRP. I've found very few things that TWRP is not better at vs CWM (on officially supported phones).
Click to expand...
Click to collapse
What does TWRP not do that CWM does?
mistahseller said:
You can install any ROM it does not have to be cyanogen mod.
why is that the goto for everyone?.....
---------- Post added at 12:18 PM ---------- Previous post was at 12:18 PM ----------
What does TWRP not do that CWM does?
Click to expand...
Click to collapse
CM is usually the go to to try something else because A) It's usually the most stable of aftermarket Roms due to the larger community and user support B) been around the longest / out for the most phones so is more well known C) it's different than AOSP so if you have issues with AOSP AND CM then you know something is really going on. That being said, CM is boring and plain to me. I appreciate that they are a good base to work off of but just by itself - yawn.
There have been a time or 2 that something would not flash through TWRP or CWM is recommended by the dev, though this is few and far between on this phone. I mod phones all the time (have done over 100 different ones) and sometimes things just work better on one than the other for various reasons.
es0tericcha0s said:
CM is usually the go to to try something else because A) It's usually the most stable of aftermarket Roms due to the larger community and user support B) been around the longest / out for the most phones so is more well known C) it's different than AOSP so if you have issues with AOSP AND CM then you know something is really going on. That being said, CM is boring and plain to me. I appreciate that they are a good base to work off of but just by itself - yawn.
There have been a time or 2 that something would not flash through TWRP or CWM is recommended by the dev, though this is few and far between on this phone. I mod phones all the time (have done over 100 different ones) and sometimes things just work better on one than the other for various reasons.
Click to expand...
Click to collapse
The problem im facing doesnt seem to be related to stability .... can try twrp though to make sure there isnt a problem with flashing or resetting through CWM.... Should I directly install TWRP over CWM or should I first reset my phone with stock and then root again before installing TWRP?
Ad.Shk2 said:
The problem im facing doesnt seem to be related to stability .... can try twrp though to make sure there isnt a problem with flashing or resetting through CWM.... Should I directly install TWRP over CWM or should I first reset my phone with stock and then root again before installing TWRP?
Click to expand...
Click to collapse
The stability idea was referring to the other poster's confusion over why someone suggested trying CM in the first place.
You can install TWRP over CWM with no issues. I typically just fastboot the recovery image, though if you aren't comfortable with that, then install the app GooManager and installing the OpenRecovery script in there will do the trick for you. No reason to go all the way back to stock at all for that. If I had a $1 for every time I had issues because of some file / recovery /formatting incompatibility, then I'd probably be able to take my wife out to a fancy dinner. Heh (I work on a lot of phones, it's my job. ) If you need help with either method, feel free to hit me up on Hangouts or make sure to post quote me because otherwise I'll forget to check back on the thread. Good luck.
es0tericcha0s said:
The stability idea was referring to the other poster's confusion over why someone suggested trying CM in the first place.
You can install TWRP over CWM with no issues. I typically just fastboot the recovery image, though if you aren't comfortable with that, then install the app GooManager and installing the OpenRecovery script in there will do the trick for you. No reason to go all the way back to stock at all for that. If I had a $1 for every time I had issues because of some file / recovery /formatting incompatibility, then I'd probably be able to take my wife out to a fancy dinner. Heh (I work on a lot of phones, it's my job. ) If you need help with either method, feel free to hit me up on Hangouts or make sure to post quote me because otherwise I'll forget to check back on the thread. Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help bro. I just flashed TWRP (fastboot method) and wiped my phone, the problem "unfortunately, phone has stopped" persists..... Any ideas?
Ad.Shk2 said:
Thanks a lot for the help bro. I just flashed TWRP (fastboot method) and wiped my phone, the problem "unfortunately, phone has stopped" persists..... Any ideas?
Click to expand...
Click to collapse
Ah, that sucks man. Ok, well, next things to try include:
Wipe cache + dalvik
Go to Advanced / Fix Permissions
Reboot
Do you have a PIN on your SIM card? I was reading through the Purity thread and some were saying they had your problem and disabling that resolved.
es0tericcha0s said:
Ah, that sucks man. Ok, well, next things to try include:
Wipe cache + dalvik
Go to Advanced / Fix Permissions
Reboot
Do you have a PIN on your SIM card? I was reading through the Purity thread and some were saying they had your problem and disabling that resolved.
Click to expand...
Click to collapse
Nope no pin.... Will try the permissions thing and shall let you know.
Sent from my Nexus 5 using XDA Premium 4 mobile app
es0tericcha0s said:
Ah, that sucks man. Ok, well, next things to try include:
Wipe cache + dalvik
Go to Advanced / Fix Permissions
Reboot
Do you have a PIN on your SIM card? I was reading through the Purity thread and some were saying they had your problem and disabling that resolved.
Click to expand...
Click to collapse
No luck my friend, I'm back on cwm... antyother ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Ad.Shk2 said:
No luck my friend, I'm back on cwm... antyother ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It looks like at this point, it's time to try another rom or update the Purity one. That, or maybe try this: http://forum.xda-developers.com/showthread.php?t=2526844
Dw about it. Fixed it. Apparently there was a problem with the com.android.phone/telephony. UnInstalled them, and then factory reset my phone. Then installed the Rom again. All well thanks for you help bro.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Ad.Shk2 said:
Dw about it. Fixed it. Apparently there was a problem with the com.android.phone/telephony. UnInstalled them, and then factory reset my phone. Then installed the Rom again. All well thanks for you help bro.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You're welcome. Glad all is well again.
I had the same problem. But i did not make a backup..
How can I unninstall phone apk from recovery?