Stuck on bootloop - Nexus 5 Q&A, Help & Troubleshooting

OMG I must be the first one to get stuck in a bootloop I feel like such an idiot. I was googling and came across a toolkit by SkipSoft... it had the nexus 5 in it, so I used it... i managed to unlock the bootloader, install the custom recovery.. the phone rebooted and boots into CWM-based Recovery v6.0.4.4... but it bootloops ... when i try to mount i get the message error mounting /data skipping format... i cannot seem to mount the phone in order to push a rom to the phone... when i mount /data it says error mounting data
might anyone have a suggestion, i would try appreciate it
(i'd like to install the hammerhead rom. )

Just stay calm :good:
This is to completely start over: http://forum.xda-developers.com/showthread.php?t=2513701
Hammerhead is the codename of the device like the nexus 4 is "mako"
edit: CWM is fine, I suggest TWRP but that is just me. I used CWM on my nexus 4 and switched to TWRP on nexus 5 and will not go back.
This might help also its a toolkit: http://forum.xda-developers.com/showthread.php?t=2509428

mistahseller said:
Just stay calm :good:
This is to completely start over: http://forum.xda-developers.com/showthread.php?t=2513701
Hammerhead is the codename of the device like the nexus 4 is "mako"
edit: CWM is fine, I suggest TWRP but that is just me. I used CWM on my nexus 4 and switched to TWRP on nexus 5 and will not go back.
This might help also its a toolkit: http://forum.xda-developers.com/showthread.php?t=2509428
Click to expand...
Click to collapse
Wow, that first line helped a lot! Thank you. :laugh: the toolkit I was trying wouldnt work for me to restore back to factory, but the toolkit you suggested worked perfectly. I cannot thank you enough. That was the strange thing, when I used the toolkit and selected TWRP for some reason CWM got pushed instead.. so i was like ok thats fine, i'll just mount and install the rom and worry about it after...
so happy this worked, thank you Sir.

My nexus 5 just closed down with no warning while I was on twitter , now its showing the error message about all processes .score , gapps, store etc has stopped , its reset itself back to factory but won't load at all. Tried to do a factory reset and it doesn't seem to be taking , just going back to unfortunately , ______has stopped. Anyone help ?
Sent from my Nexus 7 using XDA Premium HD app

Yeah that happened to me once on my nexus 4. I loaded the jellybam ROM and my phone just took a dump on itself.
Do a factory reset, wipe the dalvik cache, wipe the partition cache, or ART if you are using that and then load back into your "stock rooted" I assume ROM.
Use this to start over it seems to work for everyone and it is not hard. http://forum.xda-developers.com/showthread.php?t=2509428
I suggest this ROM, it is stock, with busy box, deodexed etc. http://forum.xda-developers.com/showthread.php?t=2508194

Saint Dave said:
My nexus 5 just closed down with no warning while I was on twitter , now its showing the error message about all processes .score , gapps, store etc has stopped , its reset itself back to factory but won't load at all. Tried to do a factory reset and it doesn't seem to be taking , just going back to unfortunately , ______has stopped. Anyone help ?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I would recommend you don't use a tool kit. While they may work you never know for sure what they're doing unless you dive into them. I'd recommend http://forum.xda-developers.com/showthread.php?p=47156064

Related

Root/Install ROM first time - I think I screwed up.

The basic deal is I got bored of the software and decided that I should root an install some custom ROMs on my Nexus S.
I used the One click method posted I believe in the general forum and everything went smoothly. I downloaded the latest AOKP and CM zips, put them onto my phones memory and went on with my day.
So today I began to put on the AOKP ROM and it got stuck at the initiating swagger screen. And was stuck there for a good 20minutes. I didn't know what to do, so I battery pulled.
I thought I had some backup saved from the day before, but that wasn't the case. So now I'm essentially stuck in thee boot menu for clockwork and my phone has been rendered useless. If any of you guys know what I should do, please tell, I'm extremely pissed off at myself for letting this happen.
I deleted the Cache partition and Dalvik thing when I was first getting ready to put on the ROM. I didn't to a factory wipe, so that might be an issue? I don't know. I've also tried plugging the phone into my computer, but because I cant turn on USB mass storage, I can't look through that either.
Any help would be greatly appreciated. Thanks
Hi,
If ur in the bootloader screen scroll down until u see recovery. Then press the power button.
From recovery scroll down to mounts and storage to connect to computer via USB.
From here u have a few options bjt i would just download another ROM and its gapps or a ROM that already contains them.
Just be careful to get the correct zips for ur type of phone
Good luck
Vs Nexus S4G using tapatalk2
Wow. Thanks a lot. Do you think I should do a factory reset before I install a new rom?
EDIT: Hey vidaljs, thanks for the help! I got the CM10 ROM up and running, apparently I was running some really old version! That USB mount thing really helped!!
Chillingly Based said:
Wow. Thanks a lot. Do you think I should do a factory reset before I install a new rom?
EDIT: Hey vidaljs, thanks for the help! I got the CM10 ROM up and running, apparently I was running some really old version! That USB mount thing really helped!!
Click to expand...
Click to collapse
No worries
Next thing u should do is make a backup of this working ROM so u can always go back to it in a pinch.
And always follow what the developers suggest in their thread since they created it.
But when I go to a new ROM, I always do a factory reset, wipe cache and wipe Dalvic.
If u haven't found it yet, use titanium backup for ur apps so its easier to apply them to ur newly flashed ROM. The free version is fine but I've heard that paid version has some extra useful benefits.
Good luck and happy flashing.
Vs Nexus S4G using tapatalk2
vidaljs said:
No worries
Next thing u should do is make a backup of this working ROM so u can always go back to it in a pinch.
Click to expand...
Click to collapse
Yeah I should have done it first
Hi guys,
Almost same stroy, I tried to Root & install Cyanomodgen 10 on my Nexus S, but boot isn't working quite well, and I'm stuck at a circling image preparing the launch.
Recovery isn't working I got stuck at the image with the robot and the back and the exclamation mark on top of it and like 5 minutes later it launch the cyanomodgen ring again - and can't get in download mode.
I pretty don't get what I should do.
Any idea?
I feel I lack some info on my problem, I'll create a fresh post for it
thanks

baseband unknown :((

So i must have messed up my phone while using the all in one root unlocker and so on. Im not sure what i did, but i finally got my phone to boot, and now i get no service. Im on tmobile and it says i have no sim card. When i go into about phone it shows baseband unknown.
I really have no idea what to do. Ive never been stuck in this situation. Maybe someone more experienced can point me in the right direction?
any help would be appreciated!
aamzalag said:
So i must have messed up my phone while using the all in one root unlocker and so on. Im not sure what i did, but i finally got my phone to boot, and now i get no service. Im on tmobile and it says i have no sim card. When i go into about phone it shows baseband unknown.
I really have no idea what to do. Ive never been stuck in this situation. Maybe someone more experienced can point me in the right direction?
any help would be appreciated!
Click to expand...
Click to collapse
so furthermore, it looks like i have no data partition anymore, i can go on my chromebrowser on the phone and browse the web but when i try to install anything it says no sdcard. I also cant move anything to the phone via windows, it just freezes even tho i can see the phone and go into the internal storage.
Im really screwed here. Ive also used the fastboot files to flash back to google stock, but for some reason continue to find everything borked.
HELP PLZ!!! ahah
Also, finding that i cant mount any partition, cache, data, anything liek that. It seems like my partitions have been messed up . Not sure how to resolve that
Well it looks like your the first one to brick the nexus 5. If your imei is missing your screwed.
P.S.A DON'T USE TOOLKITS
Sent from my NEXUS 5
Might be helpful to others to explain exactly what you did to your phone.
lafester said:
Might be helpful to others to explain exactly what you did to your phone.
Click to expand...
Click to collapse
He used a tool kit. Who knows what it did to his phone
Sent from my NEXUS 5
I realize that maybe using the toolkit may not have been a good choice but considering im already here. Constructive advice might be a little more helpful... I know that with my old verizon GS3 if i lost my imei/ similar info, i could nv flash myself and get it back in certain cases. Does a similar thing not exist for the nexus 5? Id imagine that a truly unlocked device like this one should have a method to get back from anything?
aamzalag said:
I realize that maybe using the toolkit may not have been a good choice but considering im already here. Constructive advice might be a little more helpful... I know that with my old verizon GS3 if i lost my imei/ similar info, i could nv flash myself and get it back in certain cases. Does a similar thing not exist for the nexus 5? Id imagine that a truly unlocked device like this one should have a method to get back from anything?
Click to expand...
Click to collapse
If you've flashed the stick images and it hasn't fixed it then you might be out of luck. With the n4 there is a thread on how to restore the phone with LG nv flash in download mode. I don't think the tools or files are available yet for the n5 tho
Sent from my NEXUS 5
i dont know what i did, but i restored the factory image one more time, then booted to stock recovery and wiped all partitions. The phone booted and my imei and baseband are back. Working 100% now. Gonna sit out the rooting and so on for now. time to relax for a bit
So you can't fastboot flash anything? Can you fast boot flash twrp recovery from the android SDK on a PC?
Sent from my Nexus 7
aamzalag said:
i dont know what i did, but i restored the factory image one more time, then booted to stock recovery and wiped all partitions. The phone booted and my imei and baseband are back. Working 100% now. Gonna sit out the rooting and so on for now. time to relax for a bit
Click to expand...
Click to collapse
That's how I fixed my N4. I flashed the factory images 3 times.
Glad it's working finally
Sent from my Nexus 7
Ya, fastboot continued to work, and iw as able to flash the factory images.At first those werent fixing anything. the final time i flashed it right before it worked again, i let the phone sit and run the boot screen for about 30 minutes before i went to stock recovery and wiped. Then it booted perfectly.
The previous times i had flashed twrp and wiped which i believe was the cause in the first place.
Thanks all its working perfect now. The device is amazing,!
aamzalag said:
The previous times i had flashed twrp and wiped which i believe was the cause in the first place.,!
Click to expand...
Click to collapse
Sames just happened to me, but I didnt use a toolkit, i did it all manually.
Quick flash of the factory image sorted it. :victory:
UPDATE: Flashed TWRP again....All ok this time.
You guys unlocked the bootloader first right?
Sent from my SGH-I747
This has just happened to me. I have installed the stock images 2 times now.
Is there anything you guys did differently to make it work?
My N5 decided to wipe the baseband and IMEI when I went to wipe the cache through recovery. Tried to reflash factory images 5 times and each time, when the phone boots up, hangouts, camera and gallery apps force close and I still have no network signal or IMEI/baseband.
Worst bit is all I did was wipe the cache partition, done that a million times and never had this problem
Anyone know what i can do?
I've relocked the bootloader for now but I can't call Google because my only phone is the Nexus 5 so that's out of the question.
Edit:
Managed to fix it by using a slightly different set of fastboot commands.
Here's what I did:
adb reboot bootloader
fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
fastboot reboot-bootloader
fastboot -w update image-hammerhead-krt16m.zip
fastboot reboot-bootloader
That worked for me
WRAITH07 said:
My N5 decided to wipe the baseband and IMEI when I went to wipe the cache through recovery. Tried to reflash factory images 5 times and each time, when the phone boots up, hangouts, camera and gallery apps force close and I still have no network signal or IMEI/baseband.
Worst bit is all I did was wipe the cache partition, done that a million times and never had this problem
Anyone know what i can do?
I've relocked the bootloader for now but I can't call Google because my only phone is the Nexus 5 so that's out of the question.
Click to expand...
Click to collapse
After you flash the factory image, boot into recovery and do a factory reset.
You mentioned a cache wipe. Was this in CWM or TWRP? My N5 hung trying to do a cache wipe in CWM. After rebooting the sdcard was inaccessible. The solution was to flash TWRP from fastboot, and do an advanced wipe of only the cache, and give it TIME. Like 5-10 minutes. After another reboot I had the sdcard and radio back, but some write permission issues. One more reboot and everything was ok again.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
You mentioned a cache wipe. Was this in CWM or TWRP? My N5 hung trying to do a cache wipe in CWM. After rebooting the sdcard was inaccessible. The solution was to flash TWRP from fastboot, and do an advanced wipe of only the cache, and give it TIME. Like 5-10 minutes. After another reboot I had the sdcard and radio back, but some write permission issues. One more reboot and everything was ok again.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I had this issue while wiping cache in TWRP 2.6.3.0
Sent from my Nexus 5 using Tapatalk

[Q] Any way to recover lost EFS?

Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.
Cheesy Wotsit said:
Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.
Click to expand...
Click to collapse
The same thing happened to me. Flash the latest version of TWRP, wipe your cache again, and your phone will be back to normal.
not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app
ddloco said:
not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.
_MetalHead_ said:
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.
Click to expand...
Click to collapse
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go
So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk
Elisha said:
So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox
TheAtheistOtaku said:
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox
Click to expand...
Click to collapse
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk
Elisha said:
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i know, still doesnt hurt to be caution though
ddloco said:
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go
Click to expand...
Click to collapse
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.
_MetalHead_ said:
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.
Click to expand...
Click to collapse
Thanks for the help guys. Got it up and running again more by accident than anything. Seems like MetalHead was correct, the partition was fine but just not readable. Unfortunately in order to get up and running again I flashed all the stock images in flasboot and did a full factory reset in the stock recovery which fixed the problem. Sounds like I could have done without the full wipe after all but at least it's all fixed now.
As for backing up the EFS, lesson learned. I had the 1st official TWRP on the phone which had no option for EFS backup like the current one. Guess what I'll be doing right now??
Anyway, happy man again and thanks to all that replied :good:
I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app
Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )
ddloco said:
I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thats a bummer man. What kind of phone are you using now?
Lowresolution said:
Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )
Click to expand...
Click to collapse
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app
_MetalHead_ said:
Thats a bummer man. What kind of phone are you using now?
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got it , thanks mate Just upgraded my version of TWRP .
the nexus 4 is my phone I gave to my wife now that its hers I'm lucky to pick it up just to hop on xda but when its her Facebook time she hurrie up and kick me off lol the phone I'm using is an HTC inspire 4g it sucks
Sent from my Nexus 4 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?

[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

Categories

Resources