Database Info

Asus transformer tf101 going crazy

I have transformer tf101 (Honeycomb 3.2.1 + 16GB + Dock) that I purchased in August 2011. For first 6 months I was on stock ROM and everything was working fine. After that I flashed Android Revolution HD 2.2.0 on my tablet and then it started behaving crazily . Whenever I open browser it will automatically start zooming in/out, scrolling. It will totally go haywire and will start clicking left/right.
I searched on net and found that some of other unlucky guys are facing the same issue . I have attached a .txt file that contains the link to you tube video depicting the problem.
I have tried many ways such as using superwipe script and then reinstalling the ROM's. Even, I have tried with new ROMS(ICS one's) that are there but still the problem does not seem to go away. I have searched a lot but could not find the solution to this issue. Can somebody please guide me how to get rid of this problem. I believe this is the best android forum where I am hoping that someone will help me with this problem.

This is really basic but have you tried cleaning the screen?
Other then that, have you tried going back to a HC rom and see if you don't have any issues. I understand you want the latest and greatest version rom but to determine a fix and narrow down the problem maybe you should try all the alternatives.

Thanks for replying. I had cleaned up my screen and there was not a single app/widget on my homescreens. I flashed back to HC ROM but still the problem persist . I have tried all ways of flashing th ROM's but still the problem doesn't seem to go away. I have not tried the stock ROM for HC that came with my tablet (i didn't take the backup when I flashed new ROM).
Looking at the issue it seems to me as if this problem is software related rather than the hardware.If this would have been hardware related then I should have got this on day1 of my purchase.

stryke504 said:
This is really basic but have you tried cleaning the screen?
Click to expand...
Click to collapse
I think he meant literally "clean the screen." Like with a towel and some cleaner.

typci said:
I think he meant literally "clean the screen." Like with a towel and some cleaner.
Click to expand...
Click to collapse
And dont forget to wash your hands (Im serious, that actually affects the responsiveness of the screen)

I cleaned my screen (Literally ). The problem is still there . Can it be because of the browser. I am currently using Dolphin HD browser for my browsing. I will probably install stock browser and will check with it.

Your text file is rubbish too...no link, it's actually the HTML code for an error 404..which is funny.......not only is it not a working link, or even a link at all, it's a 404 in HTML..LMAO

Sorry for the bad attachment. I have the link.doc containing the link.

Yesterday, I tried with the stock ROM and everything was working fine till the point I connected my tablet to Wifi and upgraded my Google Market to Play store. As soon as the app was updated the same problem started recurring. Now I have uninstalled the updates for google play store but the problem is still there. But the good part is that the frequency of the random zooming/clicking has decreased and it happens in browser only. Earlier it was happening in all the apps. Can somebody please direct me to the link to US stock ROM (for HC 3.2.1). As of now I am running WW_ stock rom. I just want to try out the same with US_ stock ROM as well.

First of all, don't use super wipe script. Just wipe normally with CWM.
Do these options in CWM
1. factory reset/wipe data
2. clear cache partition
3. wipe dalvik cache
4. mounts and storage -> format /system
5. mounts and storage -> format /data (this is done by factory reset but just to be sure)
Get the official ICS rom from Asus' website. US or WW doesn't matter.
Flash it with CWM after doing the wipe procedure above.
Don't let google sync or anything restore any kind of back up.
If the same problem happens again, you got a problem that requires RMA.
Honestly it already sounds like you need to RMA but you should make sure before wasting money and time on RMA.

I will try these steps today. I never did these 2 steps while flashing ROM's
1. clear cache partition
2. wipe dalvik cache
I am just curious to know as to how this problem started when it was not there till the point I flashed a custom ROM.
I have a big problem with RMA. I purchased my tablet in US and so it has North American Warranty. I am not residing in US. Thus for RMA, I have to ship my tablet back to US which will be expensive as well as an overhead . So I am planning of trying all the possible steps before I have to ask the Asus support in my native country. Please let me know if you know any stable version of Stock ROM. I read and found that some of the stock ROM's are having serious issues with Wifi/GPS etc.

harshbedi said:
I am just curious to know as to how this problem started when it was not there till the point I flashed a custom ROM.
Click to expand...
Click to collapse
Something could have gone bad during flashing.
What version of CWM are u using?
---------- Post added at 07:55 AM ---------- Previous post was at 07:51 AM ----------
harshbedi said:
I will try these steps today. I never did these 2 steps while flashing ROM's
1. clear cache partition
2. wipe dalvik cache
Click to expand...
Click to collapse
YOU HAVE TO DO THOSE. Wipe dalvik cache is under Advanced.

I am using CWM 3.2.0.1 for recovery.
I am just hoping that it should be software/flashing issue.I just don't want to go for RMA .

harshbedi said:
I am using CWM 3.2.0.1 for recovery.
I am just hoping that it should be software/flashing issue.I just don't want to go for RMA .
Click to expand...
Click to collapse
i would first get on the newest version of recovery:
http://forum.xda-developers.com/showthread.php?p=16557195
it is touch based, but i just went into cwm and the regular method of volume and power keys work fine. AND you have to store the rom on the internal sd card in order to flash, it can't access the external card once you update.
and personally i'd wipe EVERYTHING like 3 times seems kinda of the standard.. i'm super ocd so i wipe it all 5 times before i flash.. might want to pick up an ASOP rom like
EOS:
http://forum.xda-developers.com/showthread.php?t=1520764
or KANG:
http://forum.xda-developers.com/showthread.php?t=1542302
see how that works.. could always pick up the stock ASUS rom though
FYI: to flash those new EOS and KANG roms you NEED to be on that version of cwm i linked

I have tried with various ROM's that are there in Development section but the problem does not seem to go away. I will upgrade my CWM and will check with stock ROM first. Once this is done then I will go for other versions of ROM's.
Just a quick question, for flashing the stock ROM for ICS i.e 9.2.17, I have to download the firmware from ASUS website and then flash it normally the way we do for other ROM's ?

harshbedi said:
I have tried with various ROM's that are there in Development section but the problem does not seem to go away. I will upgrade my CWM and will check with stock ROM first. Once this is done then I will go for other versions of ROM's.
Just a quick question, for flashing the stock ROM for ICS i.e 9.2.17, I have to download the firmware from ASUS website and then flash it normally the way we do for other ROM's ?
Click to expand...
Click to collapse
All this could have been caused by you never wiping cache and dalvik cache.
Yea, download the ICS firmware from Asus website. It will be in a zip. You extract it once. It will have another zip. That's the flashable zip.
You flash it in CWM like you would do for any other ROM.

Yes, I never wiped cache and dalvik cache.
I will check this today and will post my observations. I am keeping my fingers crossed and hoping that this should solve the problem.
Thanks for the info.

Thanks horndroid for the lovely info...It worked.
I cleared the cache and dalvik cache and then I flashed the new revolution 3.2.0 (ICS) Rom and as of no complaints. I have been using the tablet continuously for last 3-4 hours and no issues as of now. I am hoping that it continues to work the way it is functioning right now. I am loving my transformer again . I will use it for few more hours and will update my observations. I am still keeping my fingers crossed.
Moreover, Revolution 3.2.0 is awesome(Thanks to Mike and his team). Very stable and the GPS is awesome. Sitting in my room it acquired my position(No Wifi) within seconds.

horndroid said:
YOU HAVE TO DO THOSE. Wipe dalvik cache is under Advanced.
Click to expand...
Click to collapse
Yes. This is worth pointing out again and again.
Most roms (in my experience) wont even boot unless you wipe cache and dalvik.
And the roms that do boot runs like ****.

Now I have used my tablet for 16 hours..No issues..Running perfectly fine. I believe wiping cache has solved the issue.
I was reading about dalvik cache and came to know that during boot Android always create this cache (if it is not there). So if this problem comes again, can I wipe the cache and dalvik cache without flashing a new ROM. Is this advisable?

no keyboard on nexus s

I recently bought a nexus s and once rooted the keyboard dissapered. It was fine until i flashed a rom unsuccessfuly, then turned the phone off. Once turned back on the keyboard was no more. If anyone could help me find a zip. to flash or a way to put a new keyboard on the phone I would appreciate it. the phone is basicly useless without the keyboard now, ive tried recoving to factory condition, flashing from an earlier point, and so forth. Please help!!!

You probably didn't flash gapps, you can find them on www.goo.im
Sent from my Nexus S using Tapatalk 2

jojoost said:
You probably didn't flash gapps, you can find them on www.goo.im
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
i never knew keyboard was in Gapps, i thought it's included in all ROMS since its absolutely necessary as the OP stated.
here is a dump
UPDATE: uploading
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Billchen0014 said:
i never knew keyboard was in Gapps, i thought it's included in all ROMS since its absolutely necessary as the OP stated.
here is a dump
UPDATE: uploading
Click to expand...
Click to collapse
Dictionary http://db.tt/3echUtSP and IME: http://db.tt/EUAXXcsR

re: i flashed gapps
Sent from my Nexus S using Tapatalk 2[/QUOTE]
I flashed a gapps zip from the site you linked me to and now when the phone turns on it says setup wizard is not responding and give me the option to force close. Nothing happens from that point its just stuck in a force close loop. I hope to god i didnt brick this thing. Is there a way to fix this problem? I didnt backup before flashing gapps and ive tried to restore the phone and wipe it clean but no luck. Any help would be greatly appriciated because i just got the phone, mainly to use it as a fun project seeing as smartphone customization has become my new hobby, and Im usually very good at it but now I am just afraid ive bricked the phone and I bought it unlocked so i paid a fair amount of money for i. Please help if there is a solution. Thank You,

Do you still have access to CWM? Can you make a clean install of any ROM? Wipe dalvik, cache, factory reset, format boot, system, data, cache and install ROM.
Download another ROM (and follow instructions from OP) which is not the one you initially had problems with (or download again - might be a corrupt zip file).

Thank you
Oogway13 said:
Do you still have access to CWM? Can you make a clean install of any ROM? Wipe dalvik, cache, factory reset, format boot, system, data, cache and install ROM.
Download another ROM (and follow instructions from OP) which is not the one you initially had problems with (or download again - might be a corrupt zip file).
Click to expand...
Click to collapse
Thank you very much, I followed and executed your instructions and now im running ice cream sandwich 4.0.4. not bad from going from almost a bricked phone to running one of the best versions of android. I downloaded offical roms this time instead of custom ones, first a version 2.3.4 and a 4.0.3, flashed the ics rom first and worked like a charm. Thank you very much, even got an update 5 min after i flashed the rom. You saved me 200$ and the embaracement of having a worthless phone. Im sure ill have more questions in the future, so glad there are ppl out there with the same passion for smartphone customization that i have. Much obliged. Omar

Unresponsive touchscreen

I have asked this question in the Galaxy Note 10.1 Q&A, Help & Troubleshooting forum
http://forum.xda-developers.com/showthread.php?t=2368547
Hi all.
I rooted my note 10.1 yesterday using instructions from
[RECOVERY][RootGuide][ALL NOTE 10.1]Official CWM Recovery Touch & Non-Touch 6.0.3.1
I had to reinstall standard recovery to allow OTA updates. Today I reinstalled the custom recovery by using the above method to regain root, but the touch screen is now not working. All other functions, including spen solar to be working. I have reinstalled standard recovery, done a factory reset all to no avail. Does anybody have any advice on how to fix?
Thanks on advance

nepentanova said:
I have asked this question in the Galaxy Note 10.1 Q&A, Help & Troubleshooting forum
http://forum.xda-developers.com/showthread.php?t=2368547
Hi all.
I rooted my note 10.1 yesterday using instructions from
[RECOVERY][RootGuide][ALL NOTE 10.1]Official CWM Recovery Touch & Non-Touch 6.0.3.1
I had to reinstall standard recovery to allow OTA updates. Today I reinstalled the custom recovery by using the above method to regain root, but the touch screen is now not working. All other functions, including spen solar to be working. I have reinstalled standard recovery, done a factory reset all to no avail. Does anybody have any advice on how to fix?
Thanks on advance
Click to expand...
Click to collapse
Have you tried unrooting your Note 10.1 by installing the latest factory ROM for your model Note 10.1 and then doing a factory reset?
.

kkretch said:
Have you tried unrooting your Note 10.1 by installing the latest factory ROM for your model Note 10.1 and then doing a factory reset?
.
Click to expand...
Click to collapse
Hi KK,
just got in from work so can now download rom's.
can i check a couple of things first. the rom i am going to install is this from here:-
http://www.sammobile.com/firmwares/3/?download=16810
Thats for a UK N8000 - thats the correc tone?
Can i install this via recovery? Another mentions installing via [root] Mobile ODIN Pro.
Many thanks

Well, followed the instructions here:-
http://theunlockr.com/2013/01/14/how-to-unroot-the-samsung-galaxy-note-10-1/
installed the factory rom from samfirmware.com via odin, still no touch screen. What could i have done that stops the touchscreen workin even after a stock rom reflash?
ps SPen works fine.

nepentanova said:
Well, followed the instructions here:-
http://theunlockr.com/2013/01/14/how-to-unroot-the-samsung-galaxy-note-10-1/
installed the factory rom from samfirmware.com via odin, still no touch screen. What could i have done that stops the touchscreen workin even after a stock rom reflash?
ps SPen works fine.
Click to expand...
Click to collapse
Possible hardware failure

nepentanova said:
Well, followed the instructions here:-
http://theunlockr.com/2013/01/14/how-to-unroot-the-samsung-galaxy-note-10-1/
installed the factory rom from samfirmware.com via odin, still no touch screen. What could i have done that stops the touchscreen workin even after a stock rom reflash?
ps SPen works fine.
Click to expand...
Click to collapse
Those directions do not tell you to do a factory reset ....... You know some software blocks screen touch when using S-Pen so if you did not do a factory reset after flashing the factory firmware you need to.
Is your Note 10.1 acting like it knows when you removed the s-pen and put it back in?
.

kkretch said:
Those directions do not tell you to do a factory reset ....... You know some software blocks screen touch when using S-Pen so if you did not do a factory reset after flashing the factory firmware you need to.
Is your Note 10.1 acting like it knows when you removed the s-pen and put it back in?
.
Click to expand...
Click to collapse
Hi kk
No the spen being removed triggers the shortcut bar
Ive also done a factory reset via clockwork mod. Ill try a reset via the system settings now.

nepentanova said:
Hi kk
No the spen being removed triggers the shortcut bar
Ive also done a factory reset via clockwork mod. Ill try a reset via the system settings now.
Click to expand...
Click to collapse
If you flashed a factory rom you would have removed root and CWM or did you root again after installing factory rom?

kkretch said:
If you flashed a factory rom you would have removed root and CWM or did you root again after installing factory rom?
Click to expand...
Click to collapse
Yep,
have atteempted reflashing standard recovery, clockworkmod recovery, high on android recovery, standard rom, android revoultion rom. all installed succesfully put touch screen is still not working. the spen sensor detects when the pen is removed / inserted, and i can use the touchscreen via the pen. i think this rules out hw fault, but since i have tried to reinstall recoverys and roms to no success no idea what to try next (apart from retur n to store, but i have already returned once due to faulty simcard slot, and they didnt want to replace in-store as it was a marked down item when i bought it...)
Thanks all for the advice so far. Any ideas?
to clarify the touch screen stopped working immediately after flashing a custom recovery via odin.

took it back to store for replacement,
now im trying to decide whether to risk flashing again....

nepentanova said:
took it back to store for replacement,
now im trying to decide whether to risk flashing again....
Click to expand...
Click to collapse
I have use the method Zedomax shows in this video as well as his files to obtain root several times without issue. http://www.youtube.com/watch?v=nIYiXzcW7xs But as you know there is always a risk of damage when doing mods to your device so ........... it's up to you if you want to risk it or not.
If you decide to obtain root again here are a few links that have been helpful to me. Good luck with what ever you decide to do.
Root GalaxyNote Main web site http://rootgalaxynote.com/
How To Root Galaxy Note 10.1! [Easiest Method][CWM][Method 2][ICS/Jelly Bean] http://rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/ File download link http://downloadandroidrom.com/file/GalaxyNote10.1/rooting/RootGalaxyNote10.1.zip
How to Backup/Restore ROM using ClockworkMod Recovery on Galaxy Note 10.1 http://rootgalaxynote.com/galaxy-note-backup/how-to-backuprestore-rom-using-clockworkmod-recovery-on-galaxy-note-10-1/
How to Install Stock Recovery on your Rooted Galaxy Note 10.1 http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-install-stock-recovery-on-your-rooted-galaxy-note-10-1/ File download link http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar
How to Unroot/Unbrick Galaxy Note 10.1! [Factory Firmware] http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware/ Samfirmware link http://samfirmware.com/
.

Hi KK,
took a deep breath and tried rooting again - everything fine!
Have to say i was a little nervous, but i have been rooting android for 2 years + and didn't want to give up now! Just don't like seeing ads or not having a titanium backup to box.
Many thanks.

Hi
Did you solved that problem...I got it too

[Q] Will I be able to get my Bluetooth back ?

Hello there !
I can't toggle on Bluetooth in my GT-P3110 recently.. I'm not on airplane mode.. but WiFi works though...
I even flashed a CM ROM(10.1.3 right now) to see if it works.(may be an silly deed.. I'm just new to these android things)
I have uploaded two videos which shows what really happens when trying to turn on bluetooth...
When I was using the stock rom
After flashing CM
I think that I'm having some hardware failure (i.e. dropping the unit - I never dropped myself.. idk if it happened actually as I share this tablet with my family )
I want to know whether this can be repaired ?.
Is there a seperate accessory inside for Bluetooth which can be replaced ?
Thanks in advance !

Were you on stock firmware when you noticed your bluetooth is not turning on? Was it from the start of your new tablet? Take a look at this thread, someone has the same problem with you and solved it but his problem was caused of inproper flashing http://forum.xda-developers.com/showthread.php?t=2447156
You could also try to reinstall using wipe data/factory reset, wipe cache, wipe dalvik cache from clockwork mod and reinstalling cyanogen again to see if that fixes it.
As your last resort you could flash your tab back to stock recovery and fw (and use TriangleAway to reset your flash counter) and send it to Samsung for repair, especially if it still has warranty.
some other threads with your problem: http://forums.androidcentral.com/go...s/225585-4-2-upgrade-cant-turn-bluetooth.html

katsika said:
Were you on stock firmware when you noticed your bluetooth is not turning on? Was it from the start of your new tablet? Take a look at this thread, someone has the same problem with you and solved it but his problem was caused of inproper flashing http://forum.xda-developers.com/showthread.php?t=2447156
You could also try to reinstall using wipe data/factory reset, wipe cache, wipe dalvik cache from clockwork mod and reinstalling cyanogen again to see if that fixes it.
As your last resort you could flash your tab back to stock recovery and fw (and use TriangleAway to reset your flash counter) and send it to Samsung for repair, especially if it still has warranty.
some other threads with your problem: http://forums.androidcentral.com/go...s/225585-4-2-upgrade-cant-turn-bluetooth.html
Click to expand...
Click to collapse
Thanks for the reply... I noticed the issue when I was on stock stock ROM. I may have to send it to Samsung.
Thanks for the support :highfive:

Is it possible you have another kernel other than stock?
Sent from my XT907 using xda app-developers app

"Unfortunately, Phone has stopped working" error after factory reset

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?