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

[Q] Nexus 7 2013 32GB stuck on google screen

Hi I'm new here, I have a nexus 7 2013 which wont go past the google screen, it just sits there doing nothing. I can still get into recovery mode and do a factory reset using wipe data/factory reset but it comes up with a bunch of errors such as:
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
etc.
I have no idea what to do. I've only had the Nexus since October 2013. It has been running the stock Kitkat 4.4.2 with no root or any bootloader mods
I dont know if this has anything to do with it but last night my sister turned the Nexus on but just as it finished booting (it got to the lock screen) she turned it off straight away before things like the notification bar and background had loaded up. We only turned it on about an hour ago and that was when the Nexus got stuck on the Google logo screen. Also the Nexus was plugged into the stock charger that came with it while this was happening.
What do I do from here?
Is the device bricked?
Or is it as simply flashing a ROM?
Many Thanks
Saajan

saajan_b123 said:
Hi I'm new here, I have a nexus 7 2013 which wont go past the google screen, it just sits there doing nothing. I can still get into recovery mode and do a factory reset using wipe data/factory reset but it comes up with a bunch of errors such as:
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
etc.
I have no idea what to do. I've only had the Nexus since October 2013. It has been running the stock Kitkat 4.4.2 with no root or any bootloader mods
I dont know if this has anything to do with it but last night my sister turned the Nexus on but just as it finished booting (it got to the lock screen) she turned it off straight away before things like the notification bar and background had loaded up. We only turned it on about an hour ago and that was when the Nexus got stuck on the Google logo screen. Also the Nexus was plugged into the stock charger that came with it while this was happening.
What do I do from here?
Is the device bricked?
Or is it as simply flashing a ROM?
Many Thanks
Saajan
Click to expand...
Click to collapse
I would suggest that you put it into fastboot mode (aka get to the bootloader), and fastboot flash the factory image. However, you do have to unlock the bootloader first.
Follow Post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051

charesa39 said:
I would suggest that you put it into fastboot mode (aka get to the bootloader), and fastboot flash the factory image. However, you do have to unlock the bootloader first.
Follow Post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051
Click to expand...
Click to collapse
Thank you, it worked great. I didnt know you could flash the image using fast boot

saajan_b123 said:
Thank you, it worked great. I didnt know you could flash the image using fast boot
Click to expand...
Click to collapse
Awesome. Glad it worked out for you. As far as I know, fastboot is the only way to flash the factory image. Well, I suppose toolkits can flash it as well, but I, personally, am not a huge fan of them. Plus, it's the same process in fastboot as well, just automated. They're convenient for someone that already knows what they're doing, but for "nooks," they can often do more harm than good.
Sent from my Nexus 5 using xda app-developers app

hello guys,
I have the same problem with my nexus 7 2013 (wifi), and i am trying real hard to fix it, but i cannot.
When i try to unlock the boodloader in ADB, the screen freezes, and it will not respond anymore to commands. I have to reset the tablet manually, and boot into recovery mysefl, where the bootloader state is locked..
Running stock android, no root, bootloader locked, no usb debugging!
I think the problem is that the usb debuging is off, and i cannot write on the tablet in adb trough a usb connection.
Can someone help me?
Thank you in advance!

:sasquatch: said:
hello guys,
I have the same problem with my nexus 7 2013 (wifi), and i am trying real hard to fix it, but i cannot.
When i try to unlock the boodloader in ADB, the screen freezes, and it will not respond anymore to commands. I have to reset the tablet manually, and boot into recovery mysefl, where the bootloader state is locked..
Running stock android, no root, bootloader locked, no usb debugging!
I think the problem is that the usb debuging is off, and i cannot write on the tablet in adb trough a usb connection.
Can someone help me?
Thank you in advance!
Click to expand...
Click to collapse
You should be unlocking the bootloader with fastboot, not adb. Once unlocked, flash the factory image with fastboot.

I tried with fastboot, and it works perfect until i select (yes) option from the tablet. After selecting (yea) the tablet freezes and the bootloader remains locked! I have to hard reset the tablet to acces recovery mode again...
Any ideeas?

In fastboot mode, when i try fastboot oem unlock and select yes in tablet. tablet freezes and the bootloader remains locked!
Can someone help me out

It can be an hardware issue, someone say to massage the back of the tablet ( on the X) maybe it work, should be a flat off position.
Btw look at this thread where hundreds of peoples have the same issue... Nexus 7 stuck on Google screen

[q] bootloop, no usb debugging

Hi, had a NEXUS 7 2013 for just over a month, and a few days ago it randomly got stuck in a bootloop and doesnt go past the Google logo, it doesnt go into recovery and im not sure what steps to take from here to get it back to life?
Any help would be appreciated thanks

Hi!
Try to restore stock firmware with NRT.
Choose "Current status": Soft-Bricked/Bootloop.

pavel2084 said:
Hi!
Try to restore stock firmware with NRT
Choose "Current status": Soft-Bricked/Bootloop.
Click to expand...
Click to collapse
I did what you said and it seemed to be working until the flashing process started, it failed twice because the bootloader is locked and now its remained on erasing cache for quite some time now

M0NJH said:
I did what you said and it seemed to be working until the flashing process started, it failed twice because the bootloader is locked and now its remained on erasing cache for quite some time now
Click to expand...
Click to collapse
Hi!
OK, I think the status of bootloader doesn't matter.
Try to boot your tablet to fastboot mode (bootloader mode) and flash stock google image.
Use "flash-all.bat", this batch file will flash all needed *.img files via fastboot (i hope you have it).

Softbrick'd. No idea what to do.

I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?

I had same problem. Follow the steps. Unlock it again and reboot to the system.
There enable developer option, enable debugging, enable unlock bootloader option.
Rebooted to fastboot mode
Install stock recovery
Adb sideload 3.2 full firmware.
After that reboot your phone to fastboot mode.
Unlock bootloader.
This should do it.
Sent from my ONEPLUS A3003 using Tapatalk

It's like you didn't even read what I wrote...
I said it doesn't boot to system, OnePlus logo appears for a split second and phone turns off.
Bootloader is locked and I cannot flash anything.
ADB Sideload won't read files. Gives the 'cannot read' error.

You know that you can load to bootloader by pressing volume up and power button right?
Sent from my ONEPLUS A3003 using Tapatalk

Monskiller said:
I've got quite a problem.
A few weeks ago, I unlocked the bootloader on my phone and flashed SuperSu to root it.
Today I decided to lock it back for personal reasons, wiping everything.
After it wiped, the phone kinda softbricked. When it turns on the OnePlus logo flashes for a second and turns off.
Won't let me unlock bootloader again, got stock recovery. Tried to use sideload, but ADB can't read the file. My guess it's too large.
What can I do?
Click to expand...
Click to collapse
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!

ajaysoranam said:
You should be fine so long as you didn't deactivate the"OEM UNLOCK " option from the developer setting....
do the following
1. press and hold the volume up an power buttons simultaneously to enter the boot loader menu.
2.select start option from the bootloader menu sorry that menu is the boot loader.
3. now connect to pc and use the "fastboot devices" command to see if your pc recognizes you op3 as an android device.
4.type "fastboot oem unlock"
5. flash the custom recovery thru fastboot
5. enter custom recovery and flash your desired rom.
hope this works for you!
Click to expand...
Click to collapse
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?

I relocked the bootloader. Which wiped to factory reset.
That wipe deactivated the ability to unlock bootloader until reactivated from the system, which I cannot get to because the phone turns off/bootlops before loading it.

This happened quite a few times on this forum, there is really no reason to relock the bootloader on the op3, it is covered through warranty, but u will have to contact oneplus and they should walk u through and send u files to unbrick it if u r lucky

ovidiu1982 said:
And if by mistake I have deactivate the "OEM UNLOCK " what can I do?
Click to expand...
Click to collapse
then you better get in touch with the op customer service. they will, from what i know, fix it thru a remote connection sitting.

I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.

karthikrr said:
I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid making the same mistake.
As far as your problem is concerned, I would look for unbricking guides. I know I saw at least one guide that lets you recreate the entire partition table manually and make it just like new for the OP2 (and has the company's blessings to do so). So it should apply here as well. Sorry, do not remember where I saw this, but must have been either on xda or the oneplus forums.
Click to expand...
Click to collapse
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.

Bro don't worry now.
I am gonna guide you out of this.
First install an adb package like this.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Now get a toolkit like this.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Try to connect to fastboot and check for your device in the toolkit.
If failed then kill process adb in your task manager.
Now once connected.
Check OEM status and bootloader status.
Unlock if required.
Now.
Push twrp to your phone .
Then boot into it through the toolkit.
Now load a full ROM.
http://forum.xda-developers.com/oneplus-3/development/rom-op3lite-debloated-tweaked-fast-t3404996
Just copy paste it using your file manager on PC.
Them flash first make it boot and then root.
Hope this helped.

Monskiller said:
I have stock recovery. I did boot TWRP first and let it change system by mistake, but reflashed stock later. That's what might have caused the bootloop once I relocked.
So I guess if you decide to relock in the future, don't flash TWRP, cause it bootloops, even if stock is reflashed.
Click to expand...
Click to collapse
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out

karthikrr said:
Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out
Click to expand...
Click to collapse
Don't test it. I've already done it by mistake.
It replaced recovery with TWRP by allowing the modification of system and even after reflashing stock it'll bootloop on relocking recovery.
So I found something useful then.

Hey, i think i found a solution for you. I don't know if i can post here xda thread links, so search "EDL Mode xda" on Google and the first link it is. Hope i helped

Nexus 5X Bricked Google logo loop - HELP

Nexus 5x h790 - Android 6.0.1
Some day he restarted and frozen in Google Logo. I just access the Bootloader Mode, recovery and Download mode don't run.
The problem is I can't into in Android settings, so I can't enter in developer options, OEM unlock is not allowed and USB debugging to. Because this I can't unlock my bootloader in Fastboot mode. I try use NRT but for solving my problem I need unlock my bootloader and my OEM is not activated.
Yesterday I read some topic that talking about let the device restart several times, for my surprise this worked and enter in the initiation process of Android, but is not everytime that works and is too longer to wait this miracle happens.
Please help me with this problem I don't know what I do now.
Sorry for my English I am from Brazil

Most likely you have a hardware problem.
You can try sideloading the FULL OTA using adb sideload and recovery, but you said you can't get into recovery. I am not sure if you can't get into recovery, ever, or just can't get in most of the time, but sometimes you can. If latter, try adb sideload of FULL OTA.
Bootloader is useless if you can't unlock it.
The last option is to use LGUP and the TOT file, but I think you mentioned not being able to get into download mode.
Keep in mind if you flash the TOT file, it doesn't come with a vendor partition, so it is likely you'll get some error during startup. What I would do is immediately go to developer options and enable OEM unlocking, then go to bootloader and unlock, then flash a full factory image that includes the vendor you need.
That's pretty much your options.