Okay, so I have never had any problems with this phone....until now. It suddenly fell into a crash/reboot cycle for about 8 hours until it finally crashed entirely. When I try to turn it on, it simply says "Google" on it. Then it stays on until the battery is dead. I tried to do a hard reset, and this is all that comes up...
christianpowell said:
Okay, so I have never had any problems with this phone....until now. It suddenly fell into a crash/reboot cycle for about 8 hours until it finally crashed entirely. When I try to turn it on, it simply says "Google" on it. Then it stays on until the battery is dead. I tried to do a hard reset, and this is all that comes up...
Click to expand...
Click to collapse
Well looks like it was unable to mount your sd card. For this, you have a fix. Please use the search button and i guess you will have to flash the stock factory image once again. Hope this helps.
christianpowell said:
Okay, so I have never had any problems with this phone....until now. It suddenly fell into a crash/reboot cycle for about 8 hours until it finally crashed entirely. When I try to turn it on, it simply says "Google" on it. Then it stays on until the battery is dead. I tried to do a hard reset, and this is all that comes up...
Click to expand...
Click to collapse
Try formatting cache a couple of times. This is caused due to a messed up /cache partition. If the bootloader is unlocked, you can manually flash the cache.img via fastboot. It will most probably fix it
vin4yak said:
If the bootloader is unlocked, you can manually flash the cache.img via fastboot. It will most probably fix it
Click to expand...
Click to collapse
I'm guessing he may be running completely stock.
OP, if attempting formatting of your cache doesn't work, you may have to bite the bullet and unlock your bootloader. That means you will lose everything on the phone.
This line: "e: failed to mount .../misc No such file or directory" is bothers me. That should not be missing.
Probably you have faulty emmc.
I assume you are on 100% stockt.
I wish I could have a device like yours to take a closer look on the gpt header partition.
Try do factory reset it could take 6 minutes or more. Be patient
. If that not solved your problem theb do a test. Try to unlock your bootloader. Then restart your device then check lock status again. If it goes back to locked then your problem is that the emmc is broken.
If that is the case can you allow me to take a look at your phone through teamviewer? If you are in then contact me on hangouts: [email protected] then we could arrange a time which good for both of us.
Wipe your cache partition.
It appears you did:
fastboot erase cache
Rather than:
fastboot format cache
Find a cache.img for your system version and push it through fastboot. Been there.
You guys are right, I am running completely stock. I am on Tmo and they have a replacement phone coming my way...Perhaps a better question is, should I be concerned about sending this thing in with all of my info still on it, or does it appear to be gone? I hesitate sending it in as a broken device with all of my stuff still on it. Thanks for your responses and you time.
christianpowell said:
You guys are right, I am running completely stock. I am on Tmo and they have a replacement phone coming my way...Perhaps a better question is, should I be concerned about sending this thing in with all of my info still on it, or does it appear to be gone? I hesitate sending it in as a broken device with all of my stuff still on it. Thanks for your responses and you time.
Click to expand...
Click to collapse
To wipe it completely, run fastboot oem unlock (google it if that doesn't mean anything to you) then fastboot oem lock
The phone will be back to factory state and ALL of your personal information will be scrubbed
Same thing happened to my phone it's easily fixable. Don't take my lack of posts as lack of knowledge. You need to fastboot push cache.IMG.
SilkyJohnson said:
Same thing happened to my phone it's easily fixable. Don't take my lack of posts as lack of knowledge. You need to fastboot push cache.IMG.
Click to expand...
Click to collapse
Considering you push in ADB and flash in fastboot I'd be suspect about your knowledge.
theesotericone said:
Considering you push in ADB and flash in fastboot I'd be suspect about your knowledge.
Click to expand...
Click to collapse
I literally mean push the file to the phone, but here's the command since you want to be an ass:
fastboot flash cache cache.img
(assuming image file is named cache)
SilkyJohnson said:
I literally mean push the file to the phone, but here's the command since you want to be an ass:
fastboot flash cache cache.img
(assuming image file is named cache)
Click to expand...
Click to collapse
I wasn't trying to be an ass. You just need to be a little more specific when dealing with things. That last command is the correct one. But your first post would have had some poor noob pulling his hair out after trying to push with fastboot.
Related
Are there any other secret options for restoring a bricked phone other than RSD and ADB fastboot?
See here, post #45 & #49 for a synopsis: http://forum.xda-developers.com/showthread.php?t=2095536&page=5
Basically during the failed flashes my phone ID changed and now it won't verify with ADB or RSD, the device name is no longer XT987 or whatever, now the device name is "fastboot Asanti_C S" and even though the phone and pc recognize they are connected, the connection doesnt verify.
Any workarounds? Edit the XML file maybe?
Please help, desperate.
matt2k12 said:
Are there any other secret options for restoring a bricked phone other than RSD and ADB fastboot?
See here, post #45 & #49 for a synopsis: http://forum.xda-developers.com/showthread.php?t=2095536&page=5
Basically during the failed flashes my phone ID changed and now it won't verify with ADB or RSD, the device name is no longer XT987 or whatever, now the device name is "fastboot Asanti_C S" and even though the phone and pc recognize they are connected, the connection doesnt verify.
Any workarounds? Edit the XML file maybe?
Please help, desperate.
Click to expand...
Click to collapse
Device recognized by RSD Lite as "fastboot Asanti_C S" while booted to bootloader UI is completely normal.
Adb not working while booted to bootloader UI is completely normal (adbd is not running on the phone).
Does fastboot work?
What's the response to this command?
Code:
fastboot devices
I guess when I said ADB isnt working I should have said ADB fastboot isnt working. It doesnt read any commands. It just says device not connected or whatever, USB read error, something like that maybe "fails to recognize", I forget the exact term. The computer makes the chime noise for connection/de-connection and the fastboot menu on the phone says usb connected, and also RSD lite reads the device. It just fails on step 1 of the flash, USB error. The devices acknowledge that they are there, or that something is plugged in/into, but its like they can't agree on what the phone is or is supposed to be called or located or whatever.
The sprint store guy says he couldn't fix it. I don't know what I am paying $48 a year for service and repair for.
Hopefully I'm just noobing out real bad and someone can help me out but I don't think thats the case.
I will try that command when I get my phone back in about an hour. I know there is always hope but.... I dunno. I unbricked before with RSD and it was easy money. I even used ADB or whatever to push my recovery, so I am familiar with the basics, typing in some really basic code in xml or fastboot or whatever.... but as far as ADB fastboot and RSD, I think they are toast. I've restarted the computer, the programs, etc. Re-installed drivers.
kabaldan said:
Device recognized by RSD Lite as "fastboot Asanti_C S" while booted to bootloader UI is completely normal.
Adb not working while booted to bootloader UI is completely normal (adbd is not running on the phone).
Does fastboot work?
What's the response to this command?
Code:
fastboot devices
Click to expand...
Click to collapse
The response is: T069503WI4 fastboot
Well, your phone seems like being far from a brick to me, according to the info you've provided so far.
The crucial question is if you're still able to use the fastboot command to interact with the phone or not.
great.
extract the system.img and cdrom from 4.1.2 sprint FXZ and try to flash them:
Code:
fastboot flash cdrom cdrom
fastboot flash system system.img
fastboot oem fb_mode_clear
kabaldan said:
Device recognized by RSD Lite as "fastboot Asanti_C S" while booted to bootloader UI is completely normal.
Adb not working while booted to bootloader UI is completely normal (adbd is not running on the phone).
Does fastboot work?
What's the response to this command?
Code:
fastboot devices
Click to expand...
Click to collapse
After being so bummed out and missing half an important day of work and not being in contact with anyone, I just went to pick up my phone from the Sprint store... and they are going to replace it for free! It has to ship from somewhere. They also let me keep this old one, of course, cuz I bought it, but still I had no insurance only the equip protection plan and they could have asked me to swap. It does kill my plans of using the MPQ on a road trip next week unless it gets here Monday but overall I am supremely satisfied with the customer service of Sprint. Think about it: I bricked my phone on my own free will, voided the warranty, screwed it up and all this stuff.... and they are going to replace it for free with no insurance, no deductible, no cost of any kind to me! I really don't know why. I just went in and told them it bricked on the jellybean update but that I tried to fix it and I could do no more. Then when I called to check in they told me it was bricked, and I would need a new one, and by the way, you dont have insurance. I asked them if there was any warranty or anything and they said no since it had been rooted. After that I went to a meeting and then stopped by both Radio Shack and Best Buy where the phone is still selling for $550-600+ outright with the intentions of buying one and billing it to one of my jobs which I hate to do. But I came back to my office instead knowing there would be an insightful post from one of the members here and read kabaldan's post so I figured I should go get the phone and try it out. What do I have to lose right? Well, I went in and asked for my phone back and they had me waiting for a few minutes. When they came out with the phone they said "We found another option and we can give you a new replacement for $50 but you would have to sign up for insurance as part of the deal." And I was like, well sure, sign me up! So they went back to the back and I was all happy about only having to pay $50 and all this. Then next thing I know the guy comes up to me and tells me not only is it going to be free, but that the insurance he mentioned isn't mandatory either. So no change in phone bill, no change in my bank account, and Sprint makes a customer extremely happy when they didn't even have to. Only downside is the shipping time. Its not like I went in there and acted irate or made threats of leaving or anything. I have been a customer for 10 years now so it feels like a nice present. They always take care of me. When I was asking the tech why they were giving it to me for free he was kinda at a loss for words, I dont know why, maybe they didnt want everyone in the store to know they were hooking me up. So I started laughing to myself and said to him "Maybe its Sprint giving me credit back for all that LTE service I've been paying for the last 2 years huh?" (we dont have LTE in the area) And he said "They're not that nice." HAHA! So I guess the store just overrided the system or something, hooked me up on their own, I dunno. But there is one happy Sprint customer here! Thats for sure.
Now what to do with this bricked MPQ? I would love to get it running. I can't describe how much I would love that as I don't see any good qwerty sliders coming anytime in the near or far future. As you can see I always need a back up, if its not from damage its me bricking them. Worst case scenario, how much is it worth in parts? I just feel like there has to be something.that can fix it cuz its at least showing fastboot. Something is going on in there.....
kabaldan said:
great.
extract the system.img and cdrom from 4.1.2 sprint FXZ and try to flash them:
Code:
fastboot flash cdrom cdrom
fastboot flash system system.img
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Does it matter where I extract them to? Or just that they are decompressed?
Thank you for your help. I feel that if I hadn't read you post, if you hadn't posted, I might have not went back for the phone today, and maybe the same crew wouldnt have been working there, and probably I wouldnt have gotten the free phone out of the deal. It already turned from a net loss into a gain, and if you can help me with this other one it will be a great blessing in disguise. Crazy.
Sorry with all the quoting I wasn't trying to quote so many times. I know it sends an email every time.
matt2k12 said:
Does it matter where I extract them to? Or just that they are decompressed?
Thank you for your help. I feel that if I hadn't read you post, if you hadn't posted, I might have not went back for the phone today, and maybe the same crew wouldnt have been working there, and probably I wouldnt have gotten the free phone out of the deal. It already turned from a net loss into a gain, and if you can help me with this other one it will be a great blessing in disguise. Crazy.
Click to expand...
Click to collapse
The extracted cdrom and system.img files have to be placed in the directory from which you run the fastboot command.
Ok thanks I might not get to it tonight so I will report back tomorrow. Thanks again.
matt2k12 said:
The response is: T069503WI4 fastboot
Click to expand...
Click to collapse
kabaldan said:
great.
Click to expand...
Click to collapse
matt2k12 said:
Ok thanks I might not get to it tonight so I will report back tomorrow. Thanks again.
Click to expand...
Click to collapse
Yea man, if you get a serial number and 'fastboot' showing up in fastboot devices, you are golden. No brick
kabaldan said:
great.
extract the system.img and cdrom from 4.1.2 sprint FXZ and try to flash them:
Code:
fastboot flash cdrom cdrom
fastboot flash system system.img
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Ok well when I try to extract the files, there is an error on both files. They won't extract! The progress bar goes to about 60 or 80 percent then fails and the 7Zip message says "CRC failed in 'asanti_.....' File is broken." !
When I type in the "fastboot oem fb mode clear" command it says OKAY 0.007s finished. Total time 0.009s
I guess my fastboot is working and the file is broken. Maybe its a bad fzx file from Sprint? And thats why the store couldn't fix it either? I am going to try and re-download the fzx from that link and see if those files fail again.
matt2k12 said:
I guess my fastboot is working and the file is broken. Maybe its a bad fzx file from Sprint? And thats why the store couldn't fix it either? I am going to try and re-download the fzx from that link and see if those files fail again.
Click to expand...
Click to collapse
This was going to be my suggestion. I flashed with the 4.1.2 FXZ, so I doubt the download itself is bad... perhaps just your download was bad...
arrrghhh said:
This was going to be my suggestion. I flashed with the 4.1.2 FXZ, so I doubt the download itself is bad... perhaps just your download was bad...
Click to expand...
Click to collapse
Any pointers on fastbooting the whole thing? I'm still and always will be a noob, obviously. Or is it just those things 3 or 4 things you told me earlier?
matt2k12 said:
Any pointers on fastbooting the whole thing? I'm still and always will be a noob, obviously. Or is it just those things 3 or 4 things you told me earlier?
Click to expand...
Click to collapse
Well I need to do a bit more research on manually fastbooting. I'm betting if you look at that XML file you can figure out the commands it is sending, and send those same commands... This is probably where kabaldan found those other commands.
Give me a minute.
matt2k12 said:
Any pointers on fastbooting the whole thing? I'm still and always will be a noob, obviously. Or is it just those things 3 or 4 things you told me earlier?
Click to expand...
Click to collapse
Well, by your description, the process has been interrupted when you've been flashing system.
Therefore almost everything is already in place and what's missing is to flash the system and the cdrom.
Code:
fastboot flash cdrom cdrom
fastboot flash system system.img
And unset the sticky bit that tells the phone to always boot to fastboot.
Code:
fastboot oem fb_mode_clear
kabaldan said:
Well, by your description, the process has been interrupted when you've been flashing system.
Therefore almost everything is already in place and what's missing is to flash the system and the cdrom.
Code:
fastboot flash cdrom cdrom
fastboot flash system system.img
And unset the sticky bit that tells the phone to always boot to fastboot.
Code:
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Reading the XML, these are the only remaining steps after system.img is flashed other than erasing. It erases tombstones, cache and userdata, then does the fb_mode_clear.
Good luck matt2k12.
Hey guys, wanted to follow up since I let this thread sizzle...
I got the phone running on Friday. I think the Sprint store was just lazy. They had done something to the phone but it was still stuck in fastboot. Well when I got it back to my office and started messing with fastboot it restarted back on my ICS twisted ASANTI build without me even flashing or doing anything. It was almost like a failsafe mode or automatic restore or something. But there was a problem. It still had the security credentials from JB while running ICS. So it was shutting the phone down constantly, as soon as they verified.
What I ended up doing was pulling the security file from the JB zip file and placing it in the ICS zip file. Then I went to a clean ICS flash with the JB security file. Then I could do a clean upgrade to JB from there.
Did it all with RSD lite. Edited the zip files with 7zip. The security file I am referring to is gpt_main0 or whatever.
Well that's good, glad to hear you're back up and running.
So long as fastboot works and your device is recognized by a PC, I don't think you're ever really bricked. It's honestly difficult to truly and completely "brick" one of these phones, trust me...
Hey guys, I bricked it real good this time, and now my title is true. RSD doesnt show the device, and Fastboot won't work. Details:
Last night I downloaded CM10.1 at home and was going to flash it before I went to bed. Well it was a bad download or something so I was going to restore a TWRP back up I made earlier in the day. Well apparently that backup didn't flash properly and so the only thing I could get the phone to do last night was get to fastboot mode. TWRP was gone or not working. So I left it in fastboot all night and left it on the charger so I could flash it with RSD lite this morning. Everything was going good until I got to my work computer, phone still in fastboot mode, and when I plugged the phone into my computer's USB, the screen went black and fastboot went away. Now there is just a green LED showing when its plugged into the computer, or charger, and an audible noise on PC. Every now and then the "Warning Bootloader Unlocked" screen will come up and just stay there. It never goes away unless I hard reset (Power + Vol Dwn).
However, fastboot does not show the device serial number upon typing "fastboot devices". It just skips a line and doesnt do anything, just sets up another command prompt. No response. No serial #. Also when I type "adb reboot fastboot" of course it says "device not found".
I have work to do today so I am going to let it sit. Sometimes funny things happen with this phone when you let it sit for a while. Also when it runs out of batteries and gets restarted sometimes it helps. Very temperamental phone.
Any pointers? Any way to get this thing going? I'm going to let the battery drain and see if that helps but it could be 6 or 8 hours from now. Also going to clear up my computer and shut it down and restart it so I have a good working station.
I have a Nexus 5 that I purchased from Ebay, and I'm trying to flash stock krt16m to get the device working.
Here are some things that I've noticed:
When I fastboot oem unlock, I will see the lock state change to unlock, but then when I execute fastboot reboot-bootloader, the lock state after reboot will show locked.
This presents a problem when trying to run the script flash-all.sh because upon reboot of the boot-loader I'm unable to flash other images. So, I modified the script to do the following:
fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
fastboot reboot-bootloader
fastboot oem unlock
sleep 10
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
fastboot reboot-bootloader
fastboot oem unlock
sleep 10
fastboot -w update image-hammerhead-krt16m.zip​
so that I could change the lock state to unlocked after every reboot before flashing the next image.
This succeeds, but when the Nexus 5 boots, it gets stuck in an 'X' boot loop. Sometimes I see messages like Unfortunately google.process.gapps failed, or similar. I'll also get into X boot loops where I don't get error messages, but I do get messages like, "Starting apps" and similar.
I tried factory reset/wipe in recovery mode, to no avail. I get error messages like, "failed to mount cache".
I tried flashing the stock cache, then formatting it, to no avail.
I also tried to sideload the stock images with adb when in recovery mode. Also to no avail.
The Ebay listing didn't give much information, but it did mention that this was a T-Mobile Nexus 5.
Help me! What else can I do?
Sounds like a nand failure. The boot loader staying locked is a key indicator of that. There's not really much more you can do.
theesotericone said:
Sounds like a nand failure. The boot loader staying locked is a key indicator of that. There's not really much more you can do.
Click to expand...
Click to collapse
Just to be clear, we're talking about the part: Sandisk SDIN8DE4 16 GB NAND flash?
Is there anyway that I can prove it's bad, besides the bootloader not staying in an unlocked state?
seanmeir said:
Just to be clear, we're talking about the part: Sandisk SDIN8DE4 16 GB NAND flash?
Is there anyway that I can prove it's bad, besides the bootloader not staying in an unlocked state?
Click to expand...
Click to collapse
The bootloader and the fact that you can't format anything are key signs. It's happened quite a few times on the N5 and I'm not aware of anyone who was able to fix it. Keep in mind I don't have the device in my hand but the symptoms you are describing are those of a bad nand.
I'd also vote for a corrupted NAND (As far as I remember, in the best situation the only way to fix a bad NAND is to power cycle it again.. and good luck doing that.. in the worst its just dead.). You bought a broken phone .
Also you don't need much more: If after rebooting the NAND is in the previous state, whatever you do, the NAND is broken.
Yes, your eMMC is definitely dead/damaged. It has happened to a few people, and it was the exact same every time. RMA or send in for repairs.
No one is going to "fix" the eMMC itself, not even LG, as it isn't worth the effort nor cost to do so. Any repair job will simply be a motherboard swap.
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?
ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/
If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:
Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!
You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.
Unlocked, rooted, TWRP, Cataclysm Final Lollipop (my phone never played nice with any MM ROM I tried, so I just went back to this and have been great ever since)
My phone has been rock stable for months, today I pull it out of my pocket and the screen is black. I turn it back on and it freezes on the Google screen with the unlock logo.
I can get into bootloader via power+voldown, but if I launch recovery it gets past the Google screen but then freezes on the TeamWin page.
Any suggestions, please? Searches intimate power button issues, but given I get no bootloops, I can turn the phone off reliably by holding the power button down, and it freezes at the same point consistently, it's hard for me to think that's the issue in my scenario, too. Thank you!
As an update, I used fastboot to successfully flash the newest version of TWRP, just to be sure, but it still gets stuck in the same spot, as does trying to boot normally.
Try flashing a stock ROM including userdata.img file.
audit13 said:
Try flashing a stock ROM including userdata.img file.
Click to expand...
Click to collapse
Thanks for the suggestion. Is there any way to get my personal data off before I do this?
I guess beggars can't be choosers, but I'd hate to lose anything I don't have backed up already if it ends up being another issue after all (the power button, etc.).
A corrupted ROM can prevent a clean, freshly-installed recovery from launching properly?
Thanks again.
Try flashing different version of TWRP? Maybe one of them will allow you to mount the data partition and copy off your data.
While trying to flash the (stock) new system images, I keep getting "remote: flash write failure" and/or "remote: failed to erase partition." This is via a toolkit or manually via fastboot.
The bootloader remains unlocked through all this
It's especially odd, since now I'm getting it on my recovery partition, which I was able to write to earlier today.
A cursory search of this forum suggests I'm SOL unless I replace the whole motherboard, at which point I might as well get a new phone. Do you (all) concur?
Last ditch thought: I went jogging when it went dead--outside chance a connection to the memory on the motherboard got jostled and could be reattached? Or is it fried?
Continued thanks.
The memory is soldered into place but it is possible that something happened during your jog. I also jog with my nexus 5 for 20 to 30 km per week and have done so for the past year without any issues.
First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:
Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw
Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked
ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great
It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.
hmm not a bad idea at all. Thank you!