• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Nexus 5 (Latest Hammerhead??) invalid cache

D

dropshort

Newbie
The Nexus 5 crashed boot fails at the 4 Dots.

Tried to reload to factor settings

Mount/cache yields invalid cache. (tried several times!)

Phone shop could not force a factory image reload.

Is there a fix? By whom? Brick??

DS
 
It's it rooted? Do u have access to a windows PC or any computer with either Ubuntu or Debian installed? do u have USB debugging enabled? Can u boot into bootloader mode? and if so can u please post a picture so we can see what we are dealing with? Answer these question ASAP and I should hopefully be able to help u
 
aurey2244 said:
It's it rooted? Do u have access to a windows PC or any computer with either Ubuntu or Debian installed? do u have USB debugging enabled? Can u boot into bootloader mode? and if so can u please post a picture so we can see what we are dealing with? Answer these question ASAP and I should hopefully be able to help u
Click to expand...

Rooted? No
Ubantu? No / Not at this time.
USB Debugging? err.. I assume no I did a factory restore!
Bootloader Mode Yes When I reqeust a cache clear I get the error cache failure.

What I see is the rolling dots (after GOOGLE) until the charge no longer supports it.

DS
 
aurey2244 said:
Shoot, does this mean u at least have windows? And have u tried wugs Nexus toolkit?
Click to expand...

I will soon a fast processor to convert from window to Unix Ubantu Possible.
This will happen when upgrade the existing systems.
I took the phone to a repair shop. They failed to reload the OS. So I have it back.

The question is So we have a hardware problem or a software problem?

If I know how it might be fixed I will find someone who can do it!

DS
 
You might go here: https://developers.google.com/android/nexus/ota
and download the latest firmware for your device and follow the instructions and see if the device will boot.

To get to recovery mode on your device follow these instructions:
  1. If your device is on, turn it off.
  2. Press & hold the Volume down button. While holding Volume down, press & hold the Power button until the phone turns on. You'll see the word "Start" with an arrow around it.
  3. Press the Volume down button until you highlight "Recovery mode."
  4. Press the Power button to start recovery mode. You'll see an image of an Android robot with a red exclamation mark (you may also see "No command").
  5. Press & hold the Power button. While holding Power, press the Volume up button once. Then release the Power button.
Once there, you can choose the apply update from ADB option that is in the other instructions.
 
I did the switch to factory settings several times.
The procedure worked to the point that the mount /cache failed.
The operation was a success but the patient died.

DS
 
Yes, but flashing factory images is different than performing a factory reset. A factory reset only wipes user data whereas flashing the images actually overwrites all the partitions. If it's a software issue, flashing the factory or ota images should fix it (so long as you can flash them) but if it's a hardware issue, there's nothing you can do short of repair/replacement.
 
Brian706 said:
Yes, but flashing factory images is different than performing a factory reset. A factory reset only wipes user data whereas flashing the images actually overwrites all the partitions. If it's a software issue, flashing the factory or ota images should fix it (so long as you can flash them) but if it's a hardware issue, there's nothing you can do short of repair/replacement.
Click to expand...
True, if the phone got damaged then it's a good chance that could b the problem such as water damage or burning the motherboard by letting the phone overheat (did that b4), he should at least try to format the phone via fastboot, no ota's. I've had a similar problem to where my data partition was corrupted and my phone would boot, had to reformat the phone by flashing an md5 stock rom file for my Samsung, sucked lol. Hopefully he can get windows or Linux, hell he could prolly fix that with a chromebook and an Ubuntu chroot installed, chances are his cache partition got corrupted by an update
 
aurey2244 said:
he should at least try to format the phone via fastboot, no ota's.
Click to expand...
Just wanted to point out that these ota images I'm mentioning are not your typical ota update. They are full factory images applied through adb sideload. This is a new thing Google started and they are the equivalent of flashing the factory images through fastboot, but will work in cases where the factory images won't. These don't require an unlocked bootloader like the factory images do, and without a booted device, they won't be able to allow OEM unlocking in developer options. Thus the factory images won't work in this case.
 
Brian706 said:
Just wanted to point out that these ota images I'm mentioning are not your typical ota update. They are full factory images applied through adb sideload. This is a new thing Google started and they are the equivalent of flashing the factory images through fastboot, but will work in cases where the factory images won't. These don't require an unlocked bootloader like the factory images do, and without a booted device, they won't be able to allow OEM unlocking in developer options. Thus the factory images won't work in this case.
Click to expand...
Oh yeah ik, if his bootloader isn't unlocked then he might as well unlock it then use fastboot, even still if sideload didn't work then fastboot if that don't work then well brick lol unless your like me and others who know how to replace the motherboard and other hardware in it. Well done man, at least you'll never get bricked unless u really try, hopefully dropshort can use our advice and get unbricked, wish I could do it for him
 
aurey2244 said:
Oh yeah ik, if his bootloader isn't unlocked then he might as well unlock it then use fastboot
Click to expand...
The problem is, is that he can't unlock the bootloader because of the extra security measures now. You have to have a functional device and check the option to allow bootloader unlock in the settings. Without enabling that, there's no way to unlock. That's why I think it's pretty cool that Google started making the ota images. It allows you to accomplish the same thing with a locked bootloader.
 
My objective was to take the phone to someone who had the knowledge, skill, and tools to fix the problem.
However they failed. If you permit me to read between the lines the problem seems repairable, so it is reasonable for me try another shop. Agreed?

DS
 
If it's a software issue, there's a good chance it's repairable by you, at home, if you're willing. If you could try what I suggested in this post, that might take care of the issue.

If it's too much, have someone else try it. I know it can be a bit confusing setting up and using ADB if you don't know your way around a computer well, but if you're willing to try, I'm willing to try and help.

I'd even go so far as connecting remotely if needed.
 
dropshort said:
Brian, Thank you. I will give it a go in a while.
I have a bunch of other alligators biting my assets.

DS
Click to expand...
Indeed go for it, is Pretty simple, and u could always search how to use adb on windows as with Ubuntu that's unnecessary because adb via Linux recognizes nexus phones without the need to edit anything, good luck and hopefully u can make it work. Side loading is pretty simple, keep us posted on your status
 
Brian706 said:
The problem is, is that he can't unlock the bootloader because of the extra security measures now. You have to have a functional device and check the option to allow bootloader unlock in the settings. Without enabling that, there's no way to unlock. That's why I think it's pretty cool that Google started making the ota images. It allows you to accomplish the same thing with a locked bootloader.
Click to expand...
And I had no idea they put that in as an option now, I'm guessing for extra security? Man I almost forgot this was a nexus phone made by LG
 
aurey2244 said:
And I had no idea they put that in as an option now, I'm guessing for extra security? Man I almost forgot this was a nexus phone made by LG
Click to expand...
It doesn't have anything to do with LG though. It's just Android. Since Lollipop, this has been the case. I have it on my Nexus 6. It's also on the 5x and 6p.
 
Brian706 said:
It doesn't have anything to do with LG though. It's just Android. Since Lollipop, this has been the case. I have it on my Nexus 6. It's also on the 5x and 6p.
Click to expand...
I'm sorry kinda naive when it came down to the bootloader thing, I've been using hammerheadcaf Bliss pop for quite a while now and never bothered to check the newest stock build for difference from the one I used to be on
 
dropshort said:
The OS is Marshmallow v6.0. But somehow I suspect you new that
Yes the Nexus 5 was built by LG.
Click to expand...
Did u get it to work? Hopefully u got it, I've seen others having the same issue as you, I don't understand why it just happens out of nowhere to ppl, especially the ones that don't even care for unlocking the boatloader
 
I sent he Nexus 5 to LG Canada. They replaced the mother board. I can only assume it was defective that the cache was defective. Thank you for your offers of assistance.

DS
 
You must log in or register to reply here.
Back
Top Bottom