Hi all,
I've been following this guide for rooting my nexus 7: http://forums.androidcentral.com/ne...deo-unlock-root-clockwork-nexus-7-tablet.html
I was able to unlock my bootloader just fine, and I flashed ClockworkMod. But when ClockworkMod loaded up, I got the following errors at the bottom of the screen:
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/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
This was before even trying to push the supersu.zip file, so I didn't try that. I was a bit freaked out since I know basically nothing about flashing android devices other than the basics I've gathered from these guides. Not sure why, but I chose to do a factory reset from within ClockworkMod thinking this would get me safely back to normal, which then gave me errors because it shouldn't mount properly (lol). Then I just had it reboot from within ClockworkMod. My nexus booted up, then shut down, then booted up again and came up fresh. Phew. I have no idea what happened there.
Questions:
1. Is flashing the ClockworkMod permanent, or now that I've rebooted is the original recovery image back in place?
2. What is causing this on a brand new device, and what can be done to fix it so that I can root my device?
3. If I'm ever in ClockworkMod and I get errors, can I just power off the device and turn it back on normally and things will be fine? Or would doing that cause problems?
I want to get a feel for how these sorts of things work before I do any more, because I want to better understand what's happening.
Much thanks for helping me with some basics.
EDIT:
Partially answered my one of my own questions... I tried to do the 4.2.1 OTA update and then ClockworkMod stuff came up and prompted me if it was OK to install an "untrusted package". I didn't know what I was doing, or if having ClockworkMod installed and trying to do an OTA update was a problem that could mess things up, so I aborted the installation and rebooted. Given that I was having those mounting errors earlier, would it have been a bad idea to go forward with the OTA update?
I've been following this guide for rooting my nexus 7: http://forums.androidcentral.com/ne...deo-unlock-root-clockwork-nexus-7-tablet.html
I was able to unlock my bootloader just fine, and I flashed ClockworkMod. But when ClockworkMod loaded up, I got the following errors at the bottom of the screen:
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/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
This was before even trying to push the supersu.zip file, so I didn't try that. I was a bit freaked out since I know basically nothing about flashing android devices other than the basics I've gathered from these guides. Not sure why, but I chose to do a factory reset from within ClockworkMod thinking this would get me safely back to normal, which then gave me errors because it shouldn't mount properly (lol). Then I just had it reboot from within ClockworkMod. My nexus booted up, then shut down, then booted up again and came up fresh. Phew. I have no idea what happened there.
Questions:
1. Is flashing the ClockworkMod permanent, or now that I've rebooted is the original recovery image back in place?
2. What is causing this on a brand new device, and what can be done to fix it so that I can root my device?
3. If I'm ever in ClockworkMod and I get errors, can I just power off the device and turn it back on normally and things will be fine? Or would doing that cause problems?
I want to get a feel for how these sorts of things work before I do any more, because I want to better understand what's happening.
Much thanks for helping me with some basics.
EDIT:
Partially answered my one of my own questions... I tried to do the 4.2.1 OTA update and then ClockworkMod stuff came up and prompted me if it was OK to install an "untrusted package". I didn't know what I was doing, or if having ClockworkMod installed and trying to do an OTA update was a problem that could mess things up, so I aborted the installation and rebooted. Given that I was having those mounting errors earlier, would it have been a bad idea to go forward with the OTA update?
Last edited: