Bricked Nexus S - Nexus S Q&A, Help & Troubleshooting

Right, I was using the Team Whiskey/Trinity ROM on my nexus S. worked fine. Saw MIUI ROM with english lang pack, fancied a change. Installed both. Re-Boot. Sticks at the MIUI boot animation. Tried to get rid of it through Clockworkmod, to no avail.
I have both of the above mentioned ROMs on my phone, any help would be grand.
Adam.

Its not bricked. Turn off phone. Hold volume rocker up while powering on the phone. Enter recovery mode. Wipe system. Wipe cache. Advanced>wipe dalvik. Install rom of choice again. Reboot.
Sent from my Google Nexus S using XDA App

it did that because you didnt wipe and do what peeturr said.
wipe dalvik,cache,factory -> reflash MIUI -> flash MIUI language
reboot.

Cheers for the quick reply, followed the steps..
No luck, still lingering at the Trinity Boot animation. Will a Nandroid fix it or make it worse?
Adam.
@Zephik, again followed those steps, stuck at the MIUI boot animation.

FIXED. It was me being inpatient and flapping. Thanks Zephik and Peeturr.

adam.rose4 said:
FIXED. It was me being inpatient and flapping. Thanks Zephik and Peeturr.
Click to expand...
Click to collapse
Hehe, it is slow on booting because when you wipe Dalvik and Cache. Android is rebuilding the cache so it takes longer than usual. This only happens when you wipe those two, it'll go back to normal on the second (and beyond) boot.

thank god for u guys. I made the same mistake of flashing a new rom before wiping. And it bricked my nexus s. I think u guys just made my day, idk wut id do without yall lol. Thanks a million!

lugo389 said:
thank god for u guys. I made the same mistake of flashing a new rom before wiping. And it bricked my nexus s. I think u guys just made my day, idk wut id do without yall lol. Thanks a million!
Click to expand...
Click to collapse
it is not that easy to brick an android

Related

[q] need help bad plz someone

Ok went to install coredroid on my inspire and ive installed roms before with no problem. I did a full wipe and started the install and now it is stuck on the screen say. ( Formatting partions,,, Mounting partitions,,,, Cleaning cache & Dalvik Cache & old data,,,,, writing shared systems) been like this for at least 30 min now wth can i do..
drewg0407 said:
Ok went to install coredroid on my inspire and ive installed roms before with no problem. I did a full wipe and started the install and now it is stuck on the screen say. ( Formatting partions,,, Mounting partitions,,,, Cleaning cache & Dalvik Cache & old data,,,,, writing shared systems) been like this for at least 30 min now wth can i do..
Click to expand...
Click to collapse
Maybe a bad download.....try to get the rom file again and flash it. I installed CoreDroid V9.3 yesterday no problem at all.....
Check the MD5sum before going through. Make sure that you flashed the multidevice rom and not the Sensation....
drewg0407 said:
Ok went to install coredroid on my inspire and ive installed roms before with no problem. I did a full wipe and started the install and now it is stuck on the screen say. ( Formatting partions,,, Mounting partitions,,,, Cleaning cache & Dalvik Cache & old data,,,,, writing shared systems) been like this for at least 30 min now wth can i do..
Click to expand...
Click to collapse
dont flash from any kind of rom manager software, only do it from recovery (in case you werent)
drewg0407 said:
Ok went to install coredroid on my inspire and ive installed roms before with no problem. I did a full wipe and started the install and now it is stuck on the screen say. ( Formatting partions,,, Mounting partitions,,,, Cleaning cache & Dalvik Cache & old data,,,,, writing shared systems) been like this for at least 30 min now wth can i do..
Click to expand...
Click to collapse
I love Coredroid ROM it is an awesome ROM. I flashed the new one Coredroid 9 and absolutely hatedv it had nothing but issues with it. I'd stick with Coredroid 8.1. Best thing would be remove battery remove SD Card and use and adapter place Coredroid ROM zip on root of SD as well as FULL WIPE 1.5 zip on root of SD. Then enter recovery thru hboot with holding volume down and power button at same time then flash full wipe then flash Coredroid. Should do the job.
I dont know about the Coredroid 9 multi device deal i had issues with it and completely hated it. Though I do love Coredroid but I will stay with Coredroid 8.1cause it works flawless for me. Thou now Im addicted to Absolution (lol)
Good Luck
RE
Ive already done a full wipe can i still take battery out and sd and dowload 8.1 and still put it on my phone i just scared since i did full wipe i wont be able to get back into recovery
drewg0407 said:
Ive already done a full wipe can i still take battery out and sd and dowload 8.1 and still put it on my phone i just scared since i did full wipe i wont be able to get back into recovery
Click to expand...
Click to collapse
Yeah, you can do that. Full wiping shouldn't delete recovery, you should still be able to get into recovery via HBOOT and then from there you can mount your sd card, put 8.1 on there and flash as normal. This is assuming that you haven't done anything already to screw up your recovery..
RE:
all ive done is full wipe and tried installing man i thought i bricked my damn phone i started getting scared my wife is in basic training for the army and this is my only way to talk to her
drewg0407 said:
all ive done is full wipe and tried installing man i thought i bricked my damn phone i started getting scared my wife is in basic training for the army and this is my only way to talk to her
Click to expand...
Click to collapse
My good sir, take a breath and relax...okay good! Alright, the good news is that 90% of the people who think they bricked their phone initially, don't actually have a bricked phone. I don't want to build your hopes up and say you aren't there but let's not say its bricked until it really is!
Let's start from scratch...can you get into HBOOT (holding the vol. down and power). If you can get into HBOOT, all is not lost. Once in HBOOT, you can hit the power button and it will scan for a PD98IMG.zip, hopefully you don't have one on there. After its done scanning you should be able to use the vol. rocker to select recovery. Enter recovery and follow my previous instructions. If you cannot get into recovery, there are some RUUs in the "PD98IMG.zip" form in the stock ROM thread that you can put on your SDcard and flash through HBOOT that will get you into a working ROM and you can reinstall a recovery and get back to flashing as normal.
thx
Ok thanks to all who replied got into bootloader through cmd prompts but im installing rom now ill let yall know how it goes
everything good thank you
Then click the Thanks button of those that helped you. They deserve it.
Good job not hard to fix many issues. We just have to take a deep breath and calm down. Ifs when people freak out that they start doing stupid things to their phones making matters worse. Nothing that a quick search won't cure.
Sent from my Inspire 4G using xda premium

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.

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

[Q] Stuck at Tmo Screen

I recently tried to root my Galaxy Blaze under ICS 4.0.4. I downloaded files from a thread that explained step by step how to do from k0nane. When I ran Odin it said PASS. Now the only thing the phone does is vibrate, Samsung screen comes up, and the stays loading in the Tmobile screen. What do I need to do? Please help.
centenj said:
I recently tried to root my Galaxy Blaze under ICS 4.0.4. I downloaded files from a thread that explained step by step how to do from k0nane. When I ran Odin it said PASS. Now the only thing the phone does is vibrate, Samsung screen comes up, and the stays loading in the Tmobile screen. What do I need to do? Please help.
Click to expand...
Click to collapse
You need to read.. All you need to do is go to the ROM BIBLE Thread and read on how to root your phone..
http://forum.xda-developers.com/showthread.php?t=1574556
What!
Thanks for the reply. Im not good at this stuff or know codes lol. What do you mean by ROM BIBLE.
Well I got it working finally. The only thing IM trying to get working is to go around TMo mobile tethering. I downloaded barnacle and can't get it to work.
Sent from my SGH-T769 using xda app-developers app
Are you on ICS? If you have titanium backup go into it and look for tetherprovision and freeze it. Gets around T-Mobile tethering restriction.
Sent from my SGH-T769 using xda premium
Done!
Im done, running CM10 and 4.1.2.
Weird!
As a couple of days pass I noticed my phone turning off a couple of times a day. Could it be that I have the wrong kernel. I never changed the kernel after installing the new ROM.
centenj said:
As a couple of days pass I noticed my phone turning off a couple of times a day. Could it be that I have the wrong kernel. I never changed the kernel after installing the new ROM.
Click to expand...
Click to collapse
Its a bug in CM10
Sent from my CM10 Blaze
im_awesome_right? said:
Its a bug in CM10
Sent from my CM10 Blaze
Click to expand...
Click to collapse
I haven't had a random reboot since Dec.lol you guys need to perform full cleans when flashing.
What Happened
As a couple of months enjoying the advantages of CM10, this morning I receive a call and the stayed vibrating. I shut it off and the phone would not turn back on. I booted in CWM and wiped my cache and davlik, also did a factory reset and the phone did the same thing. The only thing it does is show the Samsung sign and thats it. Someone help please.
centenj said:
As a couple of months enjoying the advantages of CM10, this morning I receive a call and the stayed vibrating. I shut it off and the phone would not turn back on. I booted in CWM and wiped my cache and davlik, also did a factory reset and the phone did the same thing. The only thing it does is show the Samsung sign and thats it. Someone help please.
Click to expand...
Click to collapse
Wipe everything again including system in mounts and re flash ur rom and gapps and it should fix ur problem
!¡!¡!¡!¡!¡!PLEASE click THANKS if I helped!¡!¡!¡!¡!¡!¡!
johnb380 said:
Wipe everything again including system in mounts and re flash ur rom and gapps and it should fix ur problem
!¡!¡!¡!¡!¡!PLEASE click THANKS if I helped!¡!¡!¡!¡!¡!¡!
Click to expand...
Click to collapse
Do you mean in the mounts and storage screen in CWM, format the system?
how long did you wait after rebooting?? It will take up to 5 minutes or more to rebuild the cache
centenj said:
Do you mean in the mounts and storage screen in CWM, format the system?
Click to expand...
Click to collapse
Yes. Wipe that (system), cache, davlik cache, and factory reset. Wipe each of them atleast 2 times, since your having issues. Then flash ROM, then gapps, reboot and wait 10 minutes, then reboot and complete the start up.
centenj said:
Do you mean in the mounts and storage screen in CWM, format the system?
Click to expand...
Click to collapse
Yes sir make sure to wipe that too and what I do after flashing a rom is wipe cache and dalvik again then flash gapps and kernel (if needed) then reboot
!¡!¡!¡!¡!¡!PLEASE click THANKS if I helped!¡!¡!¡!¡!¡!¡!
Got It
Thanks alot guys got it back running.

[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