Database Info

[Q] Upgrade CyanogenMod 10.1 with goo.im not working

Hello Everyone,
Im new to this forum as a poster, I do have read quite a few tutorials on here on how to unlock/root/s-off my device but now Im stuck again and can't seem to find a solution.
I have a HTC Sensation Z710e and I'm running CyanogenMod 10.1-20130309-Albinoman887-pyramid. Now whenever I watch a movie I there are no troubles BUT when I scroll in the movie or pause it or whatever I get an error. I looked it up and found out my version is an unstable one. So a friend of mine explained to me I could update via Goo.im, and here's the problem. It says there are no updates for my device even though that friend of mine updated to 10.1-20130601-Albinoman887-pyramid in the same way.
I did get a message like 2 weeks ago there was an update available for my device but when I clicked the notice nothing happened.
Now my biggest question is, is there some way I can download an update zip in stead of the 10.1-20130601-Albinoman887-pyramid Rom and have to start all over again with all my apps, or am I just ****ed and need to start backupping what I want to backup and start over again?
Thx for any and all insights,
Marius

well if the rom is just an update from the same rom, get it from another repo (download it from your phone or pc) and flash it with TWRP/CWM
It should work, I've done many rom upgrades without wiping my system.

Daniel120201 said:
well if the rom is just an update from the same rom, get it from another repo (download it from your phone or pc) and flash it with TWRP/CWM
It should work, I've done many rom upgrades without wiping my system.
Click to expand...
Click to collapse
So you're saying I should just "install from sdcard" with my 4EXT and it will not wipe all my settings? Even though its a completely "new" ROM but just an update of the one I have right now? I dont have to invoke something like "update"?
I did already download the file with Goo.im (that did work ) and it was about 157mb, that gives me the feeling its a completely new ROM, that's why Im a bit hesitant
Thx for the info though

MariusJP is right, there's no need for a wipe when you are flashing an update, but it may depend from ROM to ROM and from update to update. Just flash it and look for problems. If there are problems you'll have to wipe.
You should do a Backup via CWM before flashing any new software especially when it's not a stable one.
Flashing this update won't wipe your settings and data.
Sent from my GT-I9100 using xda app-developers app

Sent from my HTC ChaCha A810e using xda app-developers app

Just like Daniel said, because its an update of the ROM Im using it just updates. I was just afraid it would reinstall everything but it didnt
Thx for all the help

[Q] Getting bsod after reboot on Liquid Smooth

Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.

CoolWolf22 said:
Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.
Click to expand...
Click to collapse
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jondroid2 said:
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.

CoolWolf22 said:
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.
Click to expand...
Click to collapse
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.

jd1639 said:
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.
Click to expand...
Click to collapse
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.

CoolWolf22 said:
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.
Click to expand...
Click to collapse
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link

theesotericone said:
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link
Click to expand...
Click to collapse
Thanks. I'll download that and keep it in reserve for future reference.

[Q] Buying the phone today and rooting?

If I buy the S3 from a verizon store today brand new, will I be able to root it and unlock the boot loader still or will it come with a firmware too new?
Sorry if this was answered before. Tried searching but couldn't find results. If they are out there then I blame iOS 7 and my iPhone that needs replacing

I'm not sure what, if any, updates they've had in the last few months but I just got my s3 in August. I did take an update on it and had no issues with using casual to root & unlock. Perhaps someone may have a more recent experience.
Sent from my Slim GS3

Yes you will still be able to root, our 4.3 update hasn't happens yet
Sent from my SCH-I535 using xda app-developers app

Rooting is a great idea- I'm loving 4.4 on the s3.

clembrowning said:
Yes you will still be able to root, our 4.3 update hasn't happens yet
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That's great to know. I take it I can use custom recovery, and replace the ROM entirely? I don't want to deal with an OTA removing root on me.
Thanks

fbiryujin said:
That's great to know. I take it I can use custom recovery, and replace the ROM entirely? I don't want to deal with an OTA removing root on me.
Thanks
Click to expand...
Click to collapse
You should have absolutely ZERO issues with rooting/using a custom recovery, etc... Casual couldn't be any easier.

MisterSprinkles said:
You should have absolutely ZERO issues with rooting/using a custom recovery, etc... Casual couldn't be any easier.
Click to expand...
Click to collapse
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.

KutuluMike said:
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.
Click to expand...
Click to collapse
Ah crap. Thanks for the warning. I decided to order a Verizon Moto X Dev Edition. Can't wait for that to arrive.
Thanks to everyone for the info/advice.

KutuluMike said:
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.
Click to expand...
Click to collapse
Not necessarily true on that... I got mine last month... I did have issues with using the latest casual Root method, but the all-in-one casual Root works perfectly! But I would suggest downloading rom manager and letting that app install recovery for you (TWRP and cwm touch both caused issues for me). If you need a step by step, pm me and I'll write it up for you...
Sent from my SCH-I535 using xda premium

Macrodroid said:
Not necessarily true on that... I got mine last month... I did have issues with using the latest casual Root method, but the all-in-one casual Root works perfectly! But I would suggest downloading rom manager and letting that app install recovery for you (TWRP and cwm touch both caused issues for me). If you need a step by step, pm me and I'll write it up for you...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I have no problem getting the recovery installed. The custom recoveries are just *non-functional* because they can't mount any partitions. The error logs' are pretty clear, and every custom recovery I've tried behaves exactly the same.

"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