Database Info

Phone keeps rebooting, even in recovery?

Hi. I was toolin' along doing real well on CleanRom 4.5 for several days. Starting yesterday, the phone would randomly reboot itself to the HTC screen. I figured I had a bad app or something. Today, I went to open an app (Draw Something) and the phone froze for a bit. Then it rebooted, and now I cant get it booted back up. I usually never make it past the HTC screen. Got into recovery once but it rebooted in the middle of clearing the cache.
Any advice?

Welp, just made it through cache and dalvik and rebooted in the middle of factory reset. I wonder if I'm doing more harm than good.

Got it recovered and wiped fully, but it still keeps rebooting. Starting to feel like a hardware issue.

hcricket said:
Got it recovered and wiped fully, but it still keeps rebooting. Starting to feel like a hardware issue.
Click to expand...
Click to collapse
Wipe system than factory reset ....than flash a new Rom if u can without it rebooting :crying:

omario8484 said:
Wipe system than factory reset ....than flash a new Rom if u can without it rebooting :crying:
Click to expand...
Click to collapse
Thank you for the reply. I have the battery recharging in recovery right now (which I am thrilled it is doing, lol). What does it do when you wipe /system? Clear off the OS? Would you move a new ROM over to SD card first?

hcricket said:
Thank you for the reply. I have the battery recharging in recovery right now (which I am thrilled it is doing, lol). What does it do when you wipe /system? Clear off the OS? Would you move a new ROM over to SD card first?
Click to expand...
Click to collapse
So when u go into wipe menu in twrp it will show options : cache dalvic cache and external never press external unless u know what you're doing!
So do u have any Rom backups if so try restoring that and if not dl like clean Rom final version 5 and mount it sd in recovery and move that over and for the sake of itright now when your gunna install a new Rom in the wipe menu just choose factory reset ...your using twrp recovery right?

omario8484 said:
So when u go into wipe menu in twrp it will show options : cache dalvic cache and external never press external unless u know what you're doing!
So do u have any Rom backups if so try restoring that and if not dl like clean Rom final version 5 and mount it sd in recovery and move that over and for the sake of itright now when your gunna install a new Rom in the wipe menu just choose factory reset ...your using twrp recovery right?
Click to expand...
Click to collapse
Thank you. I wiped everything, including /system and put CleanROm final 5 on it. Everything looked beautiful but I got to the setup screens and rebooted. I'm back in recovery and charging now. Oddly, it has stopped rebooting from recovery. The only other thing I can think of is a bad sim card? Can that make a phone go crazy?

hcricket said:
Thank you. I wiped everything, including /system and put CleanROm final 5 on it. Everything looked beautiful but I got to the setup screens and rebooted. I'm back in recovery and charging now. Oddly, it has stopped rebooting from recovery. The only other thing I can think of is a bad sim card? Can that make a phone go crazy?
Click to expand...
Click to collapse
What's your battery at?

Removed the SIM card and it froze while booting, with lots of graphical tearing. *sigh*

hcricket said:
Removed the SIM card and it froze while booting, with lots of graphical tearing. *sigh*
Click to expand...
Click to collapse
Keep that simmy in there..now what's your battery ....when does it reboot ...when trying to get into aroma installer?
---------- Post added at 09:28 PM ---------- Previous post was at 09:25 PM ----------
Worst case scenario you can relock the bootloader and run an RUU. But I think u can get out of this without having to do that

I replaced the SIM. Battery at 90% now, was 44% when I started. Fortunately, it is charging from TWRP.
It reboots all over the place - from fastboot, from recovery, from the boot.img, from the lock screen. I made it all the way to Android setup at one point and it rebooted. It most often just gets to the HTC screen and hangs - it reboots the least from recovery, just once in a great while.

hcricket said:
I replaced the SIM. Battery at 90% now, was 44% when I started. Fortunately, it is charging from TWRP.
It reboots all over the place - from fastboot, from recovery, from the boot.img, from the lock screen. I made it all the way to Android setup at one point and it rebooted. It most often just gets to the HTC screen and hangs - it reboots the least from recovery, just once in a great while.
Click to expand...
Click to collapse
Dam so it's actually booting up and your getting to the rom... Umm what'd you do to your phone did u install something bad that's laying around on your sd or idk ! This is weird

omario8484 said:
Dam so it's actually booting up and your getting to the rom... Umm what'd you do to your phone did u install something bad that's laying around on your sd or idk ! This is weird
Click to expand...
Click to collapse
Oy. Add reboot during aroma installer to that list. I just tried to flash again but no go.

hcricket said:
Oy. Add reboot during aroma installer to that list. I just tried to flash again but no go.
Click to expand...
Click to collapse
Hold down your power button until your screen turns black and than see if it's still rebooting

Still no go. Thank you for your help - I've got it to 98% battery, powered it down, and I'm going to the bar, hah hah.

try flashing CM10 instead of a Sense rom. Aroma can cause freezes and reboots on its own. I would also be scared to run the RUU also since your phone freezes randomly. whats was your stock version?

It doesn't sound like you do, but if you installed a custom kernel that is overclocked then it could be that your device can't handle the higher CPU frequency. CleanROM 5 final I don't think has a custom kernel though. It could also be a bad CPU or memory hardware.

denversc said:
It doesn't sound like you do, but if you installed a custom kernel that is overclocked then it could be that your device can't handle the higher CPU frequency. CleanROM 5 final I don't think has a custom kernel though. It could also be a bad CPU or memory hardware.
Click to expand...
Click to collapse
I have had this happen. Viper has stock kernel listed in post 4 I would try flashing that.
Sent from my HTC One X using xda premium

kleeman7 said:
I have had this happen. Viper has stock kernel listed in post 4 I would try flashing that.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I told him to flash a rom that doesn't use aroma. He is getting freezes all the time. TWRP used to freeze up on me all the time after the 2.20 ruu until twrp 2.2.2.0 was released. Phone still has trouble getting into recovery from the bootloader though. He should install CM10 or codefirex without using a custom kernel. Maybe run "fastboot erase cache" in bootloader then wipe cache,dalvik,factory reset,system,external in recovery then flash CM10 or codefirex and gapps. keep it plain until you find issues you can attribute to the rom or to the phone. i have had very few issues with latest builds of jb aosp roms besides some battery stuff.

Well, although I had fully charged it and then powered down, now that I am ready to work on it this AM, it wont start at all. I'm thinking she's gone, captain.
Thank you everyone for the replies.

Serious issues trying to flash new rom!

Ok, I have an AT&T HTC One X. I have already rooted the phone and I have been running Venom Rom successfully for quite some time now. I decided I wanted to give some other roms a try today and I am running into some weird issues that I can't seem to figure out. To clarify my set up, I am not trying to run any custom kernels or anything that would potentially cause the issues I am experiencing. The roms I have tried and had these issues on are King Kang, Paranoid Android, and CM 10 official. With each the issues are always the same. First of all, I can't even type anything because Android Keyboard keeps force closing. Secondly, none of my hardware keys work at all except the back key, volume rocker, and power (home and recent apps do not function at all except to vibrate). Basically it leaves the phone completely unusable. I have gone back to Venom Rom for now because I have NEVER had any issues out of it. If anyone has any ideas why I am being plagued with these issues I would appreciate some feedback because I can't seem to find anyone else experiencing these kinds of issues honestly. Also I might add that I used a method to downgrade my HBOOT to, I believe, 1.09 instead of 1.14 because of the need to flash kernels separately with 1.14. My phone has worked flawlessly installing any ICS roms. This seems to only happen with JB roms. Thanks for your help in advance guys!

Factory reset in TWRP, and wipe Dalvik and cache before flashing any new ROM?
And to confirm, you are flashing the respective boot.img extracted from each ROM file, every time you've flashed a new ROM?

redpoint73 said:
Factory reset in TWRP, and wipe Dalvik and cache before flashing any new ROM?
And to confirm, you are flashing the respective boot.img extracted from each ROM file, every time you've flashed a new ROM?
Click to expand...
Click to collapse
Yeah, I of course did a factory reset and wiped cache and dalvik.
As far as the boot.img, I was under the impression that was only necessary for those with HBOOT 1.14 which is why I reverted my HBOOT. That was the only reason I have read anywhere to have the extract the boot.img. I am not new to Android or rooting.

guitarjuggalo said:
Yeah, I of course did a factory reset and wiped cache and dalvik.
Click to expand...
Click to collapse
If you don't tell us, we don't know. Its a common mistake, and better to ask, rather than the possibility of your issue just being something simple like not wiping.
guitarjuggalo said:
As far as the boot.img, I was under the impression that was only necessary for those with HBOOT 1.14 which is why I reverted my HBOOT. That was the only reason I have read anywhere to have the extract the boot.img. I am not new to Android or rooting.
Click to expand...
Click to collapse
Ah, I see I read that part too quickly. Confirm on the hboot screen that you are in fact on hboot 1.09, since you seem unsure.
And you are on TWRP, not CWM right?

Yea he wouldn't even boot up if he was on 1.14...
OP, are you doing a titanium backup?
Sent from my One X using Tapatalk 2

redpoint73 said:
If you don't tell us, we don't know. Its a common mistake, and better to ask, rather than the possibility of your issue just being something simple like not wiping.
Ah, I see I read that part too quickly. Confirm on the hboot screen that you are in fact on hboot 1.09, since you seem unsure.
And you are on TWRP, not CWM right?
Click to expand...
Click to collapse
Yes, I am on 1.09 for sure and using TWRP.

InflatedTitan said:
Yea he wouldn't even boot up if he was on 1.14...
OP, are you doing a titanium backup?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
No, I haven't done a titanium backup. When things didn't work for whatever reason in any of those roms I just went back to the nandroid backup I had for Venom Rom that I did before jumping to any of those roms.

That's odd... usually a 100% fresh install comes out with good results lol.
Sent from my One X using Tapatalk 2

InflatedTitan said:
That's odd... usually a 100% fresh install comes out with good results lol.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah, it is very weird. I have never encountered these kind of issues. I have been using android since the original G1 on T-Mobile and haven't encountered issues with roms this horrible. Installing any of those roms makes my phone pretty much unusable. All 3 of them (haven't tried others) exhibit the same issues. Android keyboard force closes over and over again and won't ever pull up, and the home and recent apps buttons don't work at all. Also just about any Google app or service I tried to use was crashing out.

What are you using to download?
Sent from my One X using Tapatalk 2

InflatedTitan said:
What are you using to download?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Downloading through wi-fi on my computer and sending it to the phone via USB. Also dried downloading directly to the phone over wi-fi. Results are all the same.

So, it appears that nobody has an answer?

Did you check the md5 of the zip before flashing?
I had a problem where the Rom would install fine but issues loading. Md5 of the zip on my pc was good but was bad on my sdcard. Got messed up while transferring I guess.
Also try updating to latest twrp
Sent from my HTC One XL using xda app-developers app

Make sure you aren't flashing 4.2 gapps on a 4.1 ROM. That could cause a lot of Google app FCs.
Sent from my One X using xda app-developers app

lauterm said:
Make sure you aren't flashing 4.2 gapps on a 4.1 ROM. That could cause a lot of Google app FCs.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I officially feel retarded. Thank you so much! That was indeed the issue. FML lol :good: :victory:

Its amazing that gapps controls so much that it even screwed my hardware keys with the wrong version. I really appreciate all the suggestions guys.

No Data

Hey guys,
I seriously tried looking everywhere but could not find an answer.
I flashed my shift to JellyBellyCM10.
Everything works. voice and Wifi but no cell data doesnt get anything. Can only go online using wifi. Ive installed the radios from the link below.
http://forum.xda-developers.com/showthread.php?t=1479466
Could anyone tell me why I dont have any data?
Just to get it out of the way i wiped wiped wiped....
Thanks in advance.

Have you tried...
Other roms?
Flashing clean? (Again)
Sent from my PG06100

CNexus said:
Have you tried...
Other roms?
Flashing clean? (Again)
Sent from my PG06100
Click to expand...
Click to collapse
Other roms...
in a sense yes...
the other versions of the same "roms"
flashed clean...many times. im going nutz

Try a GB rom like newSense or Supreme Sense
Sent from my PG06100

What are your flashing procedures? Are you wiping EVERYTHING multiple times and/or performing superwipe multiple times,depending on which recovery you are using?

im fairly certain im wiping everything multiple times.
im using this recovery
recovery-clockwork-5.0.2.0-speedy
So maybe im flashing wrong but i rooted the phone. downgraded to 2.2 to s-off. then flashed the radio, wipe wipe wipe. flash rom.
also tried wipe wipe wipe. flashed the radio then flashed the rom.

Hm, did you check the md5sum on the radio you flashed?
Sent from my PG06100

CNexus said:
Hm, did you check the md5sum on the radio you flashed?
Sent from my PG06100
Click to expand...
Click to collapse
i did. when i upped the radio. i tried under 2.2 and my data was working fine. so i tried that then flashed the new rom then i lose data.

This happened to me when I switched my account to an Epic 4G I was working on; when I switched it back to the Evo Shift, I couldn't get data.
I can't say this will or won't help you, or that it's even the right way to go about things. I activated another phone we had lying around, through sprint.com. And then I reactivated the shift again and went through all the steps, put the ##code in etc., and when it rebooted, it was working. And it will still have whatever ROM you installed on it (duh). Sounds like a mess but it worked for me.
I think ## 786 # does a hard reset if I'm not mistaken. You could also try that first to avoid the hassle of what I did.

klund29078 said:
This happened to me when I switched my account to an Epic 4G I was working on; when I switched it back to the Evo Shift, I couldn't get data.
I can't say this will or won't help you, or that it's even the right way to go about things. I activated another phone we had lying around, through sprint.com. And then I reactivated the shift again and went through all the steps, put the ##code in etc., and when it rebooted, it was working. And it will still have whatever ROM you installed on it (duh). Sounds like a mess but it worked for me.
I think ## 786 # does a hard reset if I'm not mistaken. You could also try that first to avoid the hassle of what I did.
Click to expand...
Click to collapse
tried that
also i cant use the ## codes without using a sense rom if im not mistken. but thank you

cardriver said:
im fairly certain im wiping everything multiple times.
im using this recovery
recovery-clockwork-5.0.2.0-speedy
So maybe im flashing wrong but i rooted the phone. downgraded to 2.2 to s-off. then flashed the radio, wipe wipe wipe. flash rom.
also tried wipe wipe wipe. flashed the radio then flashed the rom.
Click to expand...
Click to collapse
I was trying to ask for specifics of your wiping process, sorry. Now that you mention which recovery, make sure you go into the mounts & storage menu and 'format' pretty much everything but 'sdcard' multiple times each. I know alot of people take the term 'wipe' and assume we mean just the 'wipe data/factory reset' and 'wipe cache' options that are displayed on the main menu, just want to make sure.
If you are already doing that then disregard.

BigSplit said:
I was trying to ask for specifics of your wiping process, sorry. Now that you mention which recovery, make sure you go into the mounts & storage menu and 'format' pretty much everything but 'sdcard' multiple times each. I know alot of people take the term 'wipe' and assume we mean just the 'wipe data/factory reset' and 'wipe cache' options that are displayed on the main menu, just want to make sure.
If you are already doing that then disregard.
Click to expand...
Click to collapse
oh yeah. anything that said wipe. i wiped. except the sd.

I had am issue like this when I switched ROMs from Sense to AOSP at one point. Ended up having to nandroid back to Sense and update PRL and profile. Have you tried going back to a Sense ROM, updating those then reflashing the CM10 ROM?

brandontowey said:
I had am issue like this when I switched ROMs from Sense to AOSP at one point. Ended up having to nandroid back to Sense and update PRL and profile. Have you tried going back to a Sense ROM, updating those then reflashing the CM10 ROM?
Click to expand...
Click to collapse
in the process of trying that now. ill let you guys know how it goes...

ok. after flashing back to 2.2 and rooting. then flashing the new radio. reinstalling a cm7 rom i was able to gain access to the web and then update to ICS/JB.
Thank you everyone for your help

"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?

[Q] Recovery is broken??? I Don't Know.. Please Help

So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:

alexdzk said:
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
Click to expand...
Click to collapse
Did you wipe data and cache before flashing the new rom?

This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?

I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064

mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
jd1639 said:
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
I'll try this then if it doesnt work ill try the factory reset/ relock whatever, thanks.

mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
no its CWM

You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk

mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
housry23 said:
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. I said it in my post.

alexdzk said:
Yes, I did. I said it in my post.
Click to expand...
Click to collapse
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk

housry23 said:
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.

alexdzk said:
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
Click to expand...
Click to collapse
Good. Glad you got it worked out. Was probably an old build of whatever recovery and because of the way KitKat changed things, there were a lot of problems wiping when the phone first came out. If you find any more good deals on your local Craigslist, PM me. I want a black n5 instead of my white one.
Sent from my Nexus 5 using Tapatalk