Stuck at Google Screen - Samsung Galaxy Nexus

Hi I'm stuck at Google Screen and not sure what the problem is.
I had the below responses in Clockwork Mod when in that recovery and then switched to TWRP, still to no avail. I read that it may be the partitions, but not sure how to correct. I can connect to the phone and ADB to the bootloader and can flash recoveries, but doesn't seem like I have an SD card anymore. Any/all help would be extremely appreciated. I'm not new to android, but this experience is proving to me that I have no clue what I've been doing.
E: can't mount /cache/recovery/command
E: can't mount /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

cmorebusiness said:
Hi I'm stuck at Google Screen and not sure what the problem is.
I had the below responses in Clockwork Mod when in that recovery and then switched to TWRP, still to no avail. I read that it may be the partitions, but not sure how to correct. I can connect to the phone and ADB to the bootloader and can flash recoveries, but doesn't seem like I have an SD card anymore. Any/all help would be extremely appreciated. I'm not new to android, but this experience is proving to me that I have no clue what I've been doing.
E: can't mount /cache/recovery/command
E: can't mount /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
Click to expand...
Click to collapse
how about you try to re-flash it by using nexus root toolkit? but before that back up every thing (TWRP) then pull the the backup files just in case you have an important files on you phone.

jibralee said:
how about you to re-flash it by using nexus root toolkit? but before that back up every thing (TWRP) then pull the the backup files just in case you have an important files on you phone.
Click to expand...
Click to collapse
I'm on MAC and it seems like toolkit is windows based? I'm pretty sure I wiped out whatever ROM is on the phone. I tried pushing zip folder to the phone and just got "Permission Denied". I know I'm missing something, because I can ADB to reboot, I can flash recoveries, I just cannot access the SD card or get passed the Google splash screen
Code:
~/Desktop/androidsdk/platform-tools/adb push ~/Desktop/androidsdk/platform-tools/image-yakju-jwr66y.zip data/media/0
failed to copy '/Users/SeeBusiness/Desktop/androidsdk/platform-tools/image-yakju-jwr66y.zip' to 'data/media/0': Permission denied

Should be /data/media/0. You don't have the / before data
Sent from my Nexus 5

Related

[Q] E: can't mount cache/recovery/log

Originally posted here:
This happened to me yesterday; my phone told me I had some updates from the market, and it froze mid-updating an app (don't remember which one).
I pulled the battery and the phone went directly into recovery, and it has stayed there ever since.
I tried everything, wiping the cache, the boot, dalvik, EVERYTHING. I even did the factory reset/data wipe, and in the end it tells me the same thing:
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
Is there something that I overlooked? My phone isn't even able to be "seen" by my computer, the only way I can turn it off is by doing a battery pull, and when I put the battery back in, it goes straight into CWMod's recovery.
Click to expand...
Click to collapse
jrizk07 said:
re flash your ROM since you're in recovery. otherwise restore a nandroid backup and that'll get you up and running again.
Click to expand...
Click to collapse
I 've tried flashing trinity 2.6 and it aborted the installation citing a (status 7), I had tried to previously install coredroid multidevice (3.5) and it had aborted it as well, citing a (status 1); I downloaded clockwork 5, as well as 2 other roms; miui.us vivow 1.12.30, which was also aborted with a (status 1) and JmzRunyInc2v1, this one managed to go through "deleting stuff", "Installing stuff", "Symlinking stuff", "Installing bussybox stuff", "Flashing kernel stuff" and then "done" followed by "Install from SD card complete", but when I chose "Go back" it gave me the same message:
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
So, when I rebooted, it went again into CWMod.
Is there anything else I'm missing?
Doing some reading it looks like your recovery image is corrupted. You'll need to re flash your recovery manually.
You can get into the bootloader correct?
Noob's Guide #6: I just HTC Unlocked, what now?
Thank AgalychnisCallidryas
yeah, when I turn on my phone, it goes directly into CWMod, but I can go into Hboot, and select fastboot, recovery, etc., but the problem is my computer isn't able to identify the phone when it gets plugged in.
EDIT: I tried HBoot USB, and it tells me the drivers aren't correctly installed, something about android 1.0.
Do you have any access to a Linux/Mac machine?
A friend of mine has a mac, yeah. However, my brother also has a droid phone (Incredible 1) and may have the needed drives, would that work?
Edit: I was able to get the android dsk and platform tools from an old backup, I'll try to give this a go with it.
cowboyv said:
A friend of mine has a mac, yeah. However, my brother also has a droid phone (Incredible 1) and may have the needed drives, would that work?
Click to expand...
Click to collapse
Use a windows computer, it's pretty simple. You'll probably need to uninstall the current drivers on that computer (Control Panel> Add Remove Programs or Programs under windows 7, Make sure all HTC Drivers are uninstalled)
Then go here
http://forum.xda-developers.com/showthread.php?t=1298990
Install the HTC USB drivers and go from there.
LOL. I just use mac, no drivers required.
Ok, I was able to download the sdk, and reinstalled the htc drivers, everything's groovy, but the computer is still not able to "see" my phone, it's telling me "device not found".
Should I be using the "push" adb command to push in a new recovery image from CWMod?
EDIT: I tried doing the recovery again, this time, it went through checking the MD5 sums, erasing and restoring the boot image, but when it got to the system restoring, it tells me there was an error formatting the system.
So, since adb can't connect to the phone, what are my options?
cowboyv said:
Ok, I was able to download the sdk, and reinstalled the htc drivers, everything's groovy, but the computer is still not able to "see" my phone, it's telling me "device not found".
Should I be using the "push" adb command to push in a new recovery image from CWMod?
EDIT: I tried doing the recovery again, this time, it went through checking the MD5 sums, erasing and restoring the boot image, but when it got to the system restoring, it tells me there was an error formatting the system.
So, since adb can't connect to the phone, what are my options?
Click to expand...
Click to collapse
Read this and take note http://forum.xda-developers.com/showthread.php?p=18016711#post18016711
You need to be in the bootloader and not recovery in order to do what you need to do.
You cannot re flash the recovery from CWMod. Remember the white screen with the android guys skating? That's where you need to be.
Either hold down the volume down button and hold power, or if you have your device detected by adb you can
adb reboot bootloader
This is where you flash the recovery image via fastboot.
http://forum.xda-developers.com/showthread.php?t=1134520
Or you might even want to consider re flashing the stock RUU to unroot and just start over from scratch.
That worked, but...
jrizk07 said:
This is where you flash the recovery image via fastboot. Or you might even want to consider re flashing the stock RUU to unroot and just start over from scratch.
Click to expand...
Click to collapse
Ok, thank you! That did work. I just flashed the vivow, vut after trying to restore to the my latest backup, it still gives me the same error logs: it goes through checking the MD5 sums, erasing and restoring the boot image, but when it gets to the system restoring, it tells me there was an error formatting the system before giving me the same error message.
Code:
Error while formatting /system!
E:Error in /cache/recovery/log (Read-only file system)
E: can't open /cache/recovery/last_log
So I guess I'll have to flash the stock RUU and start from scratch. Just a question, though; to flash the RUU, I just follow the same procedure, go into fastboot, plug into computer, and use adb, correct?
cowboyv said:
Ok, thank you! That did work. I just flashed the vivow, vut after trying to restore to the my latest backup, it still gives me the same error logs: it goes through checking the MD5 sums, erasing and restoring the boot image, but when it gets to the system restoring, it tells me there was an error formatting the system before giving me the same error message.
Code:
Error while formatting /system!
E:Error in /cache/recovery/log (Read-only file system)
E: can't open /cache/recovery/last_log
So I guess I'll have to flash the stock RUU and start from scratch. Just a question, though; to flash the RUU, I just follow the same procedure, go into fastboot, plug into computer, and use adb, correct?
Click to expand...
Click to collapse
Right, Just follow this procedure and start over from scratch completely. Do not restore a backup because it seems to be corrupt.
http://forum.xda-developers.com/showthread.php?t=1298990
Ok, I downloaded the zip file vwhk-12102011-c and have extracted it to my C: root, however, when I try to do the first code
Code:
adb shell rm -r /data/local/tmp/*
ADB tells me "error: device not found".
Now, apologies beforehand, as you may have noticed this is my first android phone and I am a noob, so some of my questions may seem a bit obvious to you.
1. I read that I rename the ruu to PG32IMG.zip, is this true?
2. Should I continue and flash the RUU zip via adb, or should I push the RUU?
3. Should I simply put the zip in a microsd and then restart the phone in bootloader?
EDIT: Nevermind, went ahead and did 1. and 3. and that worked. I still have the root access, but I need to re-install a recovery.
Once again, thanks.

[Q] Stuck in bootloader

Hey how's it going? I'm stuck in the boot loader. I had CM7 installed before and it got stuck in a loop. So, tried wiping cache/data and dalvik. Dalvik couldn't be wiped. Tried installing another rom and that didn't work at all. I'm able to get into recovery mode without a problem, but now I'm getting stuck on the HTC screen.
Error wise, I'm getting the following:
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
I've looked around for some help and couldn't find much help, but it was a recovery issue/ Don't have a backup or anything, and don't mind wiping everything and starting from scratch anyways.
I'm on a mac as of now but can grab a windows computer if needed. Any ideas?
Well, last resort should be to flash the ruu file that will get you back to stock. Honestly, this sounds like a hardware failure though. Try going to recovery, fixing permissions, then go to mounts and storage in recovery and manually mount those things and see what, if any errors you get.
Sent from my Incredible 2 using xda premium
Not a hardware failure at all. You just need to reflash your recovery Just follow the Guide #6 in my guides directory, just the part about reflashing the recovery.
Thanks for the replies and glad to hear it isn't a hardware failure. So as I said I'm on my mac and the phone doesn't come up under devices at all. Do I need the drivers still on the mac?
I was able to load the sd card onto my computer and throw the cam file in the root of the card. Is there a way to flash memory from that through clockwork or does it have to be through command prompt?

[Q] E: Can't mount problem!

I get these message when I boot recovery, try to wipe, try to flash, etc.
These messages prevents me from installing ROMs, .zip files, etc.
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
What I have tried so far:
• Flashing stock using fastboot
• Researching
I hope I get a solution on fixing this problem.
Which recovery and version are you using?
Is the device currently rooted?
Were ANY other modifications made to the device prior to this occurring?
Hey thanks for your reply!
My device is rooted and unlocked.
I'm not really sure about this but I used wugfresh's root toolkit to root but it failed, so then I used cf-autoroot by chainfire.
z3r0c311 said:
Hey thanks for your reply!
My device is rooted and unlocked.
I'm not really sure about this but I used wugfresh's root toolkit to root but it failed, so then I used cf-autoroot by chainfire.
Click to expand...
Click to collapse
Try TWRP recovery from my signature.
Aerowinder said:
Try TWRP recovery from my signature.
Click to expand...
Click to collapse
I have flashed TWRP recovery in your signature using fastboot, when i try to wipe, i still get the same messages.
I have also tried philz and cwm.
I had the same problem on mine a few weeks ago, had to send it into Asus to get the motherboard replaced.
Sent from my Nexus 7 using XDA Free mobile app
jazzyjames said:
I had the same problem on mine a few weeks ago, had to send it into Asus to get the motherboard replaced.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Oh I see... I guess that is the only solution to fix this.
Ill contact Asus so i could get my motherboard replace.
Thanks for helping guys!
z3r0c311 said:
I get these message when I boot recovery, try to wipe, try to flash, etc.
These messages prevents me from installing ROMs, .zip files, etc.
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
What I have tried so far:
• Flashing stock using fastboot
• Researching
I hope I get a solution on fixing this problem.
Click to expand...
Click to collapse
Sorry to say, but I had the same sort of issue with my Huewai Ascend P1 LTE as one of the partitions wouldn't unmount. The device still boots but the wifi is broken. It's pretty much a paper weight now. :crying:
Its one of the few things which puts me off rooting. If I dont need to root, I dont.
Thanks for your reply! I think I need root I'm a type of a guy who can't live without root! Thanks for helping though!

N7100 Stuck at Note II Splash Screen Case

CASE CLOSED
Hi XDA ppl, I'm desperate enough with my SGN2 so I decided to make a thread here.
It all begin with my apps (some of them are BBM, Adobe Air, Livescore) crashed and suddenly disappear.
Tried to reinstall, Play Store said an error code (I forgot) and google it. Turns out I need to root my phone and delete /data/com.bbm and another folders to reinstall BBM and another disappeared apps.
Rooted, open ES File Explorer with root permission, and unfortunately I can't delete those folders but somehow I still can rename it, then reinstall BBM.
A few days later, my phone randomly restart and when I noticed, it takes longer boot time everytime it randomly restart (I have startup manager installed and it reports startup/boot time).
At last, my phone randomly restart, again, while charging. Can't get past Samsung Galaxy Note II splash screen, but I can get it into recovery mode and odin mode (download mode).
Here's the condition:
Stuck at Samsung Galaxy Note II splash screen
ABLE to enter ODIN mode
ABLE to enter recovery mode (PhilZ 6.48.4 with CWM 6.0.5.0)
Detected by ODIN3 v3.09
Code:
PhilZ showing:
E: could not mount /data to setup /data/media path!
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Tried to flash with odin, ended up with NAND Write Start, FAIL! and sometimes at my phone screen (at download mode screen) show error report like "magic string" or something.
PIT Re-partition >> Failed (odin never said "No PIT Partition")
Format /cache >> E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Can't mount /system /cache /preload /data and even /sdcard (internal storage), but it can read my external storage. I can even see my microSD contain using PhilZ' mount USB storage feature.
Essentially, everything that I tried ended up with mounting problem, sdcard problem, can't find specific path, and etc.
And I suspect that I have emmc insane/SDS on my phone.
Any solution for my phone? Any helps appreciated.
Thanks in advance!
3xocid3 said:
Hi XDA ppl, I'm desperate enough with my SGN2 so I decided to make a thread here.
It all begin with my apps (some of them are BBM, Adobe Air, Livescore) crashed and suddenly disappear.
Tried to reinstall, Play Store said an error code (I forgot) and google it. Turns out I need to root my phone and delete /data/com.bbm and another folders to reinstall BBM and another disappeared apps.
Rooted, open ES File Explorer with root permission, and unfortunately I can't delete those folders but somehow I still can rename it, then reinstall BBM.
A few days later, my phone randomly restart and when I noticed, it takes longer boot time everytime it randomly restart (I have startup manager installed and it reports startup/boot time).
At last, my phone randomly restart, again, while charging. Can't get past Samsung Galaxy Note II splash screen, but I can get it into recovery mode and odin mode (download mode).
Here's the condition:
Stuck at Samsung Galaxy Note II splash screen
ABLE to enter ODIN mode
ABLE to enter recovery mode (PhilZ 6.48.4 with CWM 6.0.5.0)
Detected by ODIN3 v3.09
Code:
PhilZ showing:
E: could not mount /data to setup /data/media path!
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Tried to flash with odin, ended up with NAND Write Start, FAIL! and sometimes at my phone screen (at download mode screen) show error report like "magic string" or something.
PIT Re-partition >> Failed (odin never said "No PIT Partition")
Format /cache >> E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Can't mount /system /cache /preload /data and even /sdcard (internal storage), but it can read my external storage. I can even see my microSD contain using PhilZ' mount USB storage feature.
Essentially, everything that I tried ended up with mounting problem, sdcard problem, can't find specific path, and etc.
And I suspect that I have emmc insane/SDS on my phone.
Any solution for my phone? Any helps appreciated.
Thanks in advance!
Click to expand...
Click to collapse
probably you are right with your diagnosis.
try different versions of Odin
yaro666 said:
probably you are right with your diagnosis.
try different versions of Odin
Click to expand...
Click to collapse
I've been trying with different odin, no luck.
Guess gonna repair it on serice center. Thanks dude!

TWRP failing to mount /data + bootloop

Hi all,
After spending all my morning looking at various solutions I've resulted in opening a new thread.
I was trying to install a stock rom this morning however was stuck in a bootloop on the LG logo.
Trying to go back into recovery resulted in a black screen after the TWRP logo.
I was attempting to re-install TWRP to see if that would fix the problem however I only managed to get into Download Mode (is this the same screen as the Bootloader?) and adb/fastboot couldn't find the device.
Magically, TWRP boots up now however in the log it states the following:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount /data
E: Unable to recreate /data/media folder
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
If anyone can point me in the right direction in how to resolve this I would be grateful.
Regards,
Ash
AshleyNG2 said:
Hi all,
After spending all my morning looking at various solutions I've resulted in opening a new thread.
I was trying to install a stock rom this morning however was stuck in a bootloop on the LG logo.
Trying to go back into recovery resulted in a black screen after the TWRP logo.
I was attempting to re-install TWRP to see if that would fix the problem however I only managed to get into Download Mode (is this the same screen as the Bootloader?) and adb/fastboot couldn't find the device.
Magically, TWRP boots up now however in the log it states the following:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount /data
E: Unable to recreate /data/media folder
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
If anyone can point me in the right direction in how to resolve this I would be grateful.
Regards,
Ash
Click to expand...
Click to collapse
Looks like you trying to install stock Rom, Given the account you used a flashable zip. It didnt install all the way. and now your stuck with a messed up unstable device......
If you can get into TWRP, wipe everything at least 2 times.. Then install a Flashable ROM/gapps ect..
If you cant get into TWRP and only into Download mode.. Then you will have to flash stock kdz file...............
you can find all types of guides on that around here............
Eliminater74 said:
Looks like you trying to install stock Rom, Given the account you used a flashable zip. It didnt install all the way. and now your stuck with a messed up unstable device......
Click to expand...
Click to collapse
Thanks for your response, once I got into TWRP I couldn't wipe anything as it couldn't mount any partition nor could I flash anything from the external sd.
When I plugged it in there was no internal memory so I decided to use the TOT restore method to go back to stock which was successful and now I've got my custom stock rom back on.

Categories

Resources