Develop Bugs

[Q] [HELP REQUEST] E: Can't mount /cache/recovery/command

I hope i'm posting this in the right section but I'm having a major problem. After draining the battery on my Gnex, I brought it home and put it on the charger. It came up with the battery charging symbol for awhile then when it booted it showed the Google splash screen for about a minute. Then rebooted, showed the google image again and went into CWM Recovery with the following message.
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
When I tried to wipe data and cache and factory reset it comes up saying it's completed but then says the same error message as above underneath it.
I've tried full factory reset with the GNex toolkit and still nothing.
I also can't mount the cache in CWM Recovery, it just says Error mounting /cache!
I'm at a loss at this point. I hope someone knows what to do. It seems that if I can get into fastboot and CWM Recovery there should be a way out but I can't find one. Thanks in advance for any advice you guys have.
-Nate

try flashing CWM again? wiping dalvik or fixing permissions perhaps

OK, clicking Wipe Dalvik gets me to the Click yes to wipe Dalvik but also gives this error:
E: unknown volume for path [/sd-ext]
But then when I click yes it says Dalvik Cache wiped.
Fixing permissions just says Complete with no problems.
Reflashing CWM completes fine but still the same error as before when I try to boot.
Thanks for the suggestions.
-Nate

Just a slight update to the problem. It appears that no matter what I do as far as using the tool kits to return to stock or reflash stock images, CWM recovery is still always there and the Bootloader version also doesn't change. I've tried both 4.0.1 and 4.0.2 and the bootloader version is always PRIMEKL01.
I'm assuming if there was a way to get into the sdcard memory from windows with fastboot, that would be the solution to my problems but searching for if that's even possible has turned up nothing :-(
I think i'm genuinely screwed at this point.
-Nate

If you flash cwm then you HAVE to boot into Android at least once before entering cwm or it will give you the error messages. Just boot into Android, then enter cwm and everything will be fine. This is explained in my ToolKit option for flashing cwm.
EDIT: Can you boot into Android at all?
Mark.

Can't boot into android whatsoever. If I hit power like I normally would it shows the google image and the little unlocked lock for about a minute. Then reboots, shows that again and goes right into CWM with the error from the first post about not mounting /cache

natepalm said:
Can't boot into android whatsoever. If I hit power like I normally would it shows the google image and the little unlocked lock for about a minute. Then reboots, shows that again and goes right into CWM with the error from the first post about not mounting /cache
Click to expand...
Click to collapse
Sorry I think I jumped the gun when replying originally. Cwm will not mount properly until after you have booted into Android at least once after flashing it so thats out until you have fixed Android. You cannot access the sdcard from fastboot it needs adb to push/pull files which in turn needs your phone booted into Android.
What Android build is your phone on? Is it stock or custom? What exact modifications have you made to the phone in terms of flashing roms/kernels/radios/bootloaders?
Can you enter fastboot mode?
Dont worry too much im sure we can fix it
Mark.

It was on AOKP B22. It has CWM 5.5.0.4.
The fastboot screen says this:
Product Name - Tuna
Variant - Toro
HW Version - 9
Bootloader Version - PRIMEKL01
Baseband Version - I515. FA02 CDMA - I515.FA02
Carrier Info - none
Serial Number - lots of numbers
Signing - Production
Lock State - Unlocked
I also just tried the instructions from this guide http://forum.xda-developers.com/showthread.php?t=1426207 which all completed successfully.

natepalm said:
It was on AOKP B22. It has CWM 5.5.0.4.
The fastboot screen says this:
Product Name - Tuna
Variant - Toro
HW Version - 9
Bootloader Version - PRIMEKL01
Baseband Version - I515. FA02 CDMA - I515.FA02
Carrier Info - none
Serial Number - lots of numbers
Signing - Production
Lock State - Unlocked
I also just tried the instructions from this guide http://forum.xda-developers.com/showthread.php?t=1426207 which all completed successfully.
Click to expand...
Click to collapse
So you just restored a Stock Rom to your phone via odin?
If so does it still not boot into Android?
Mark.

Nope. Still doing the same thing. Also nothing changed on the fastboot screen as far as info.
-Nate

natepalm said:
Nope. Still doing the same thing. Also nothing changed on the fastboot screen as far as info.
-Nate
Click to expand...
Click to collapse
Have you used the GNex ToolKit to flash back to recovery (using that method) already? Im not sure what odin flashes but I know exactly what the google stock image flashes.
You could try relocking the bootloader, then unlocking it again which will force a full wipe of you phone and may fix something.
You mentioned that the bootloader version doesnt change after flashing but it wont as its the same version across the different stock builds.
If you flash a google stock image via the ToolKit (option 8 and download *THIS* image to use if you have an LTE Model) and let it reboot then see what happens. The procedure will flash the stock recovery back to your device so keep a note of what happens after it reboots and if it ends up back in recovery as it did before then it will be a screen with a little android man with a red triangle in the middle.
If your phone still isnt booting after all that then maybe you need to consider relocking the bootloader and sending it back under warranty.
Mark.

OK so I tried unlocking and locking. No change. Did the GNex toolkit option 8. Completed successfully but it didn't reboot the phone afterwards. Just stayed on the fastboot screen with this on the bottom: Fastboot Status - OKAYPRIMEKL01 highlighted in blue.

natepalm said:
OK so I tried unlocking and locking. No change. Did the GNex toolkit option 8. Completed successfully but it didn't reboot the phone afterwards. Just stayed on the fastboot screen with this on the bottom: Fastboot Status - OKAYPRIMEKL01 highlighted in blue.
Click to expand...
Click to collapse
So it didnt reboot after it finished flashing?
Did you try pressing the power button when the top of the fastboot screen says 'START' to force the reboot?
The last thing I can think of (if the above didnt do anything) is to try booting the phone with one of my insecure boot images to check if theres a problem with the boot partition:
Enter fastboot mode on your phone and start the ToolKit (v5.3)
Choose option 20 to open a new command prompt
In the new command prompt type
fastboot-toolkit boot root\boot_lte_ICL53F_insecure.img
Click to expand...
Click to collapse
followed by return.
This will attempt to boot the phone using the insecure boot image of the ToolKit.
What happens with that (exactly the same as before or anything different)?
Mark.

OK, I tried that and it completed. Rebooted the phone but unfortunately same scenario. Boots twice then into CWM with the same list of errors mounting cache. :-\
Thanks a ton for all your help by the way, I truly appreciate it.
-Nate

One thing I should mention is when I say I unlocked and locked the bootloader and it didn't change, I mean it stays unlocked no matter what I do. It'll come up and say its locked or unlocked but as soon as the phone reboots its always unlocked. It seems like whatever is happening nothing can actually write to the part of the phones memory it needs to so nothing sticks. If that makes any sense, i'm just guessing.
-Nate

natepalm said:
OK, I tried that and it completed. Rebooted the phone but unfortunately same scenario. Boots twice then into CWM with the same list of errors mounting cache. :-\
Thanks a ton for all your help by the way, I truly appreciate it.
-Nate
Click to expand...
Click to collapse
So even though you said you flashed the google stock image earlier it still has cwm on even though it should have been overwritten with the stock recovery.. very wierd.
natepalm said:
One thing I should mention is when I say I unlocked and locked the bootloader and it didn't change, I mean it stays unlocked no matter what I do. It'll come up and say its locked or unlocked but as soon as the phone reboots its always unlocked. It seems like whatever is happening nothing can actually write to the part of the phones memory it needs to so nothing sticks. If that makes any sense, i'm just guessing.
-Nate
Click to expand...
Click to collapse
All the procedures must be completing (at least in the eyes of your pc and phone) or you would get error messages from the ToolKit when flashing. As you said before its like nothing is being written to the phone even though it says it is.
One thing is to try flashing a newer bootloader in case thats been corrupted in some way (if we can).
Download the latest bootloader *HERE* and extract the .img file from the downloaded zip file. Copy the PRIMELA03.img file to the 'put_img_files_to_flash_here' folder in the ToolKit and flash it using option 12. Make sure you select FLASH (2) and flash it to the BOOTLOADER partition (2).
After the flash fastboot should restart and if it went on correctly then the Bootloader version will now say PRIMELA03.
If it changed then try reflashing the stock google image as before. If it didnt change the bootloader then I really am out of ideas.
Mark.

I tried that. Says flash complete both on the fastboot screen and GNex Toolkit but when it comes back on the bootloader version doesn't change. Still PRIMEKL01. I can't believe it but I think this is my first truly bricked android phone. If only there was a way to get into the memory of the phone through fastboot or odin or something maybe we could repartition it somehow. But it seems like the parts of memory I need fixed are just completely inaccessible at this point.
-Nate

Go through the complete reset manually following this thread:
http://forum.xda-developers.com/showthread.php?t=1366806
Using this stock Google image:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
It has to work, otherwise it could very well be a complete brick

Unfortunately, it goes through all that saying its complete but when it boots back up nothing changes. CWM is still there. Bootloader still unlocked.
-Nate

Then your internal memory is borked IMO

want to relock bricked nexus 7, stuck at google logo i have tried many things [FIXED]

Edit: fastboot commands worked, then after wiping as pandae suggested i then flashed the latest boot loader, and then flashed recovery from the zip file.
My nexus was giving me problems of not picking up touch, i think it was bad digitizer, because it would go in and out almost randomly.
It was unlocked, and rooted, and i tried a couple factory resets to fix the problem but no luck. Then it would boot loop constantly, until it wouldn't get passed the google screen with the unlocked icon.
I was still running jelly bean, not sure witch build specifically
It can get into fast boot mode, but not recovery.
windows 7 would only recognize it as an android device and not establish adb, I've tried WUG toolkit.
I tried setting up the sdk on unbuntu, I can establish adb on my galaxy nexus, but noit on my 7
adb devices returns nothing when the nexus 7 is plugged in but, lsusb shows it connected as google, inc something
I'm not sure if usb debugging was enabled before it wouldn't boot anymore.
I just want to relock if that is possible, wanted to RMA to ASUS for the touch screen
any help would be great

danqe said:
My nexus was giving me problems of not picking up touch, i think it was bad digitizer, because it would go in and out almost randomly.
It was unlocked, and rooted, and i tried a couple factory resets to fix the problem but no luck. Then it would boot loop constantly, until it wouldn't get passed the google screen with the unlocked icon.
I was still running jelly bean, not sure witch build specifically
It can get into fast boot mode, but not recovery.
windows 7 would only recognize it as an android device and not establish adb, I've tried WUG toolkit.
I tried setting up the sdk on unbuntu, I can establish adb on my galaxy nexus, but noit on my 7
adb devices returns nothing when the nexus 7 is plugged in but, lsusb shows it connected as google, inc something
I'm not sure if usb debugging was enabled before it wouldn't boot anymore.
I just want to relock if that is possible, wanted to RMA to ASUS for the touch screen
any help would be great
Click to expand...
Click to collapse
It's a pain you got through this.
I went through the same. But glad to have my Tablet working after some time figuring out what went wrong or what I have done to have messed it. But I figured that out. Somewhere along the way of my ventures, I have done something that forced my TAB to bootloop forever.
That being said, you can just look back to the things you might have done that caused it. Figure out what you did before that. When was it okay?, Things like that.
There is a thread in here with a one-click recovery that promises a Dead or Alive nexus to be unbricked. Though I never had success with it, go figure if that will solve your issue.
All the best!!

danqe said:
My nexus was giving me problems of not picking up touch, i think it was bad digitizer, because it would go in and out almost randomly.
It was unlocked, and rooted, and i tried a couple factory resets to fix the problem but no luck. Then it would boot loop constantly, until it wouldn't get passed the google screen with the unlocked icon.
I was still running jelly bean, not sure witch build specifically
It can get into fast boot mode, but not recovery.
windows 7 would only recognize it as an android device and not establish adb, I've tried WUG toolkit.
I tried setting up the sdk on unbuntu, I can establish adb on my galaxy nexus, but noit on my 7
adb devices returns nothing when the nexus 7 is plugged in but, lsusb shows it connected as google, inc something
I'm not sure if usb debugging was enabled before it wouldn't boot anymore.
I just want to relock if that is possible, wanted to RMA to ASUS for the touch screen
any help would be great
Click to expand...
Click to collapse
If you're at the bootloader, use "fastboot devices" to see if your tablet is recognized. (ADB is for when you're booted into Android.)
If you can get to the bootloader and your N7 is unlocked and recognized, there's a lot of hope. Run these:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that, you'll need to reflash your favorite custom recovery and ROM.

Pandae said:
If you're at the bootloader, use "fastboot devices" to see if your tablet is recognized. (ADB is for when you're booted into Android.)
If you can get to the bootloader and your N7 is unlocked and recognized, there's a lot of hope. Run these:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that, you'll need to reflash your favorite custom recovery and ROM.
Click to expand...
Click to collapse
Hi Pandae,
Thanks for the reply so good news is fastboot commands work, but now I'm having trouble flashing recoveries and roms.
Flashed twrp 2.6.3.1, and rebooted, but I was still stuck at the google logo when I tried to get into recovery
Tried going to stock
the bootloader flashed to flo-04.02
then tried system and it failed( remote: Unknown chunk type
gonna try some other versions, this just might work.

Fixed
I flashed recovery from the newest stock from the zip and after 30-45 min of the google logo the animation played.
Thanks for the help.

That was a really long time to wait, but still, whew! :good: Gotta love our Nexus devices. As long as you can get to an unlocked bootloader, there are great odds of fixing things at home.
Where did you get the stock ROM? Once you wipe the five partitions I mentioned with fastboot, you can download the stock ROM, then run the "flash-all.bat" file within, without having to worry about individual image files within. The bach file flashes the stock recovery as well as the ROM.
https://developers.google.com/android/nexus/images#razor

[Q] can't unlock bootloader

The bootloader is currently lock. everything is stock, i never root it.
whenever i try "fastboot oem unlock" and select yes on the nexus, it frooze on this "unlock bootloader ?" screen. and on the terminal it say "erasing userdata". the first time i tried i let it like that for a good hour before force shutting off, and i tri again, froze every time.
I can acces to my stock recovery but i have an error "e failed to mount /cache (invalid argument)",
meanwhile, i can't boot
any idea to fix this ?

doss2007 said:
The bootloader is currently lock. everything is stock, i never root it.
whenever i try "fastboot oem unlock" and select yes on the nexus, it frooze on this "unlock bootloader ?" screen. and on the terminal it say "erasing userdata". the first time i tried i let it like that for a good hour before force shutting off, and i tri again, froze every time.
I can acces to my stock recovery but i have an error "e failed to mount /cache (invalid argument)",
meanwhile, i can't boot
any idea to fix this ?
Click to expand...
Click to collapse
I've seen posts like this here and in other forums gleaned from fairly extensive searching. Nobody has an answer. I think it's a hardware problem, to be honest. The N7 2013 is plagued with them, it seems.
Can you still boot into Android? You could try to root via towelroot. From there, you could flash TWRP, or maybe unlock the bootloader with that app from the play store.
I would send it back to Google, if possible.

Aerowinder said:
I would send it back to Google, if possible.
Click to expand...
Click to collapse
unfortunately i can't boot so i will try sending it back

You can download the latest Google nexus image for your model tablet onto your pc.
Boot tablet into fastboot mode.
On the pc run the bat file to install the binaries, and after a few minutes the tablet will have latest factory bootloader, lte modem firmware, recovery, kitkat, and the tablet will have undergone a factory data reset.

HowardZ said:
You can download the latest Google nexus image for your model tablet onto your pc.
Boot tablet into fastboot mode.
On the pc run the bat file to install the binaries, and after a few minutes the tablet will have latest factory bootloader, lte modem firmware, recovery, kitkat, and the tablet will have undergone a factory data reset.
Click to expand...
Click to collapse
The OP states that he was unable to unlock the bootloader. I was unaware that you could "fastboot" flash any kind of image without an unlocked bootloader! ; )

Bootloop after Installing Nethunter 2.0 (Nexus 7 2013 Wifi)

Hello everybody,
i hope the xdadevs can help me with my problem.
Since two Days i try to recover my Nexus 7 form a bootloop.
A week ago i flashed Kali Nethunter 2.0 via TWRP on my Device (Nexus 7 2003 Wifi) - Everything worked fine till yesterday.
My device run out of energy so i loaded it and startet it shortly after that.
Then i regognized the bootloop. I tried to restart the device but it had no effect.
After that i tried to boot into the Recovery Mode with TWRP to restore my working backup. But it got stucked on the loading screen of TWRP too.
Now i tried to recover some images and fix the problem with some manuals which seemed promising. - no success
After a while i did something incredible stupid and locked my bootloader again (i wanted to try to lock and unlock it since some tools couldnt flash the stock rom).
The situation right now:
I cant boot up normaly: Stuck while "Google" is displayed
I cant boot in Recovery Mode (TWRP): Stuck on the blue TWRP Logo
If i try to use the Skipsoft Toolkit or something else it fails - or do i miss something
Recover the Stock rom by using the "flash-all.bat" fails because of this (pastebin. c0m/ie0dBv1D). I used the stock rom of Android 4.4.4(razor-ktu84p) because every other stockrom says this (pastebin. c0m/Dz31k8qu).
I wonder why the stock rom needs to get the bootloader unlocked... ive red so much about it that it just works out of the box..... am i doing something wrong ?
If i try to unlock again, the selection screen on the tablet shows up. I choose yes and hit the Power button. At the console the output <bootloader> erasing userdata" shows up and "freezes?!"... nothing happens afterwards.
Thats about it and this is where i am stuck. I would really appreciate if someone could help me ! I would even reward or spend some money on help.
I try to fix it meanwhile and update this post if something new happens.
I had to alternate the links because im a new member, im sorry for that !
Thanks in advanced and sorry for the spelling

did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?

diehard2013 said:
did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?
Click to expand...
Click to collapse
Yeah i tried it but it couldnt fix my problems. Returning to Stock Rom will always tell me that i need the bootloader unlocked... and i cant unlock it.
My PC and Linux Notebook where recognizing before it was bricked. Now it only gets detected in fastboot because it wont start anymore.

5X just turns off before booting

Hi guys,
this morning i was charging my 5X via USB in my car while listening to spotify via bluetooth (like every morning).
But suddenly my phone turned off.
Now i can't turn it on again.
When i press and hold the power button it shows me the "device can't be checked for corruption" since my bootloader is unlocked.
Then i see the Google logo for some time and then the phone turn off again.
I'm able to get into bootloader mode and already flashed the latest factory image.
The phone still doesn't boot.
I'm not able to get into recovery mode. The same happens:
t shows me the "device can't be checked for corruption" since my bootloader is unlocked.
Then i see the Google logo for some time and then the phone turn off again.
I had my phone rooted and xposed installed on Oreo 8.1 for 1-2 month and didn't had any issues.
Do you have any ideas
Is there a way so get a look at log files right now
Thanks for your help!
edit:
after flashing 8.1.0 (OPM3.171019.016, Mar 2018) i have a new behaviour.
The phone still doesn't boot but as mentioned above.
But when i want to go to recovery it shows me the "broken android".
At some point the phone turns off and then i don't get back to recovery like described above
Also flashing TWRP didn't change anything :crying:

Have you tried the 4-core boot (BLOD fix)?

Flashing the modified boot images doesn't change anything.
With the modified TWRP i was able to get into recovery.
But i had to type in my passcode since my device in encrypted.
Decryption didn't work i guess because it says forced encryption has been disabled?
It said
failed to mount /cache (invalid argument)
Updating partition details
and then "Password failed, please try again"
after confirming the passcode again
failed to mount /cache (invalid argument)
done...
And the phone turn off.
With the TWRP 3.1.1.0 from offical TWRP page i wasn't able to get into recovery.
What does that mean?

It booted successfully yesterday but then again suddenly turned off.
Did some additional research and for me it now looks like i'm having the bad soldered point issue. :crying:

leAndroid91 said:
It booted successfully yesterday but then again suddenly turned off.
Did some additional research and for me it now looks like i'm having the bad soldered point issue. :crying:
Click to expand...
Click to collapse
Mine just starting doing this a couple days ago, I contacted LG and they say they will replace the mainboard for free. I bought my 5X at launch so get in touch with LG support and see if they'll repair yours (I'm in the USA FYI, and I haven't actually sent them my phone yet).

Thanks for the info i will get in touch with them but i'm from germany and bought mine here on google store.
Unfortunately we can't do class actions against big corporates yet.
But let's see what happens i'm currently waiting for my 5X to cool down - fingers crossed

You can still get in touch with LG directly. These devices have a 2 year warranty (under EU law).