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?
Related
Well, I started out with CM7 RC4, and everything was dandy.
But then I decided to try out Virtuous. I did a Titanium Backup, then did a nandroid backup and wiped through ROM Manager. Virtuous was horribly laggy, however, so I decided to switch back to CM.
Upon restoring my nandroid, my G2 froze at the 'data' section, and I was forced to pull the battery. After reboot, it couldn't get past the white HTC screen. When I booted back into CWM, I immediately got the following:
"ClockworkMod Recovery v3.0.0.5
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"
It reloads those errors every time I go back to the main menu of CWM, as well.
Every ROM I try and flash still gets stuck at the splash screen.
I've wiped everything there is to wipe, and any time I try and restore any of my nandroids, I get:
"Erasing boot before restore...
Error while erasing boot image!"
I've been looking for a solution for the past 4 hours and I can't seem to fix it. I don't even know what ROM is actually loaded on my phone.
Please, if anyone can help, it would be greatly appreciated! I just want to be able to actually use my phone.
pokemontrainer4life said:
Well, I started out with CM7 RC4, and everything was dandy.
But then I decided to try out Virtuous. I did a Titanium Backup, then did a nandroid backup and wiped through ROM Manager. Virtuous was horribly laggy, however, so I decided to switch back to CM.
Upon restoring my nandroid, my G2 froze at the 'data' section, and I was forced to pull the battery. After reboot, it couldn't get past the white HTC screen. When I booted back into CWM, I immediately got the following:
"ClockworkMod Recovery v3.0.0.5
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"
It reloads those errors every time I go back to the main menu of CWM, as well.
Every ROM I try and flash still gets stuck at the splash screen.
I've wiped everything there is to wipe, and any time I try and restore any of my nandroids, I get:
"Erasing boot before restore...
Error while erasing boot image!"
I've been looking for a solution for the past 4 hours and I can't seem to fix it. I don't even know what ROM is actually loaded on my phone.
Please, if anyone can help, it would be greatly appreciated! I just want to be able to actually use my phone.
Click to expand...
Click to collapse
From the looks of it. It seems that you messed up your recovery , all you have to do is go back into fastboot and then reflash/reinstall the recovery.img and everything should be working fine afterwards
derykisonder said:
From the looks of it. It seems that you messed up your recovery , all you have to do is go back into fastboot and then reflash/reinstall the recovery.img and everything should be working fine afterwards
Click to expand...
Click to collapse
I've read a few places that you need the engineering hboot. Is that true?
And how can I tell if I have it already?
Well it appears I don't have the engineering hboot. When I flashed the recovery via fastboot it came back saying "FAILED (remote: not allowed)".
Is there a way I can install the hboot without using Terminal on the phone?
Wow same for my i dont have Eng hboot i thought i put it in my phone but somehow its gone know D: looking for solution :/
OK, I had this same problem and was able to fix it. I d on't know how many of you this will help but here is what I did. I was able to boot into CWM and choose advanced restore where I manually restored the system and data files. I then reboot my device and I was able to get it to fully boot. So far I have seen no real issues with the phone and it's better than a brick; it will at least get you running again so you can try something different if need be.
pokemontrainer4life said:
Well it appears I don't have the engineering hboot. When I flashed the recovery via fastboot it came back saying "FAILED (remote: not allowed)".
Is there a way I can install the hboot without using Terminal on the phone?
Click to expand...
Click to collapse
Ever heard of adb?
Sent from my T-Mobile G2 using XDA Premium App
flash & restore
I had a workaroudn for something similar - basically phone wouldnt boot past splash screen after losing power. I was able to make a CWM backup, and the only way i could find to get all my things back was to do a fresh os flash and work with some nandroid abckup files to try to extract the data out manually - there is one called Nandroid Manager, but it ahsnt always worked for me, but a great concept. worth a try, if not there appears to be other products on the market now which may help
So I reflashed DU after trying out CM 10.1 for a couple weeks and suddenly my phone freezes. After rebooting, my phone doesn't get past the Galaxy S2 logo so I decided to start up recovery and in recovery mode I notice several errors appear.
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
In recovery I wasn't able to reflash the rom or even restore my backup! I then decide to restore to EL29 using Odin OC root but now it's stuck at Set Partition. I've retried Odin in different usb ports and with different cables and nothing changes. Does anyone have any Ideas as to what has happened and a fix for this?
ghostrill said:
So I reflashed DU after trying out CM 10.1 for a couple weeks and suddenly my phone freezes. After rebooting, my phone doesn't get past the Galaxy S2 logo so I decided to start up recovery and in recovery mode I notice several errors appear.
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
In recovery I wasn't able to reflash the rom or even restore my backup! I then decide to restore to EL29 using Odin OC root but now it's stuck at Set Partition. I've retried Odin in different usb ports and with different cables and nothing changes. Does anyone have any Ideas as to what has happened and a fix for this?
Click to expand...
Click to collapse
I understand you are in a jam, but there is really no need to start a new thread for this if you post the same question on the noob friendly q&a. I have put a suggestion for you in there. I hope it helps. And if it doesn't, please let me know in the q&a and we'll try something else. Kennyglass123 my good friend, feel free to delete this if you'd like
Sent from my SPH-D710BST using xda premium
Hi,
I’ve been a lurker here on XDA and thanks to the great posts here have been happy with my DInc for much longer than expected :good:. I was hoping to post on the Incredikernal page as I think I am running Incredikernal (unless it got replaced when I flashed a new PB31IMG) but do not have enough posts yet. I Hope you can help with my current problem.
Current state:
After my DInc got stuck on the white HTC Incredible screen and trying to restore a nandroid backup failed (see History below), I flashed the stock Froyo PB31IMG from pvillecomp (outside link deleted) and flash in HBOOT directions on that site. The DInc booted up into Froyo 2.2.
I then tried to flash the stock Gingerbread image from that site, but the DInc got stuck in a loop (Droid screen, HTC screen, Droid screen…)
I then flashed back stock Froyo.
I then tried to install ClockWorkMod 5.0.2.0 via HBOOT, with file renamed to PB31IMG (per the instructions on androidforums
incredible-all-things-root/420788-how-regain-root-s-off-htc-unlocked-bootloader.html )
When I get into CWM, I get the following "errors":
ClockworkMod Recovery v5.0.2.0
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 install Superuser per step 6 of that thread, I get the error E:Can’t mount /sdcard/
I thought maybe I needed to run the 5 Vibs of Death fix (SD Card fix (fastboot oem enable qxdm 0) and USB but given that my PC can read the SD card while it is in the DInc (Disk Drive under Connection Type with USB Cable plugged in) my thought is that this isn’t the problem.
Then I thought maybe I need to root the DInc using Unrevoked3 since it is on Froyo 2.2.
Then I thought maybe I need to work on the partitions, using Parted.
Now I am wondering if I should just leave well enough alone (at least my DInc is working again ), but thought I would ask here first. If I can't regain root, at least I would like to get Stock Gingerbread to work.
Any guidance is much appreciated!
Thanks,
Al
History:
I rooted my device years ago, but don’t remember if I used Unrevoked3. My DInc has s-off, and the Convert2Ext4_no_data_limit_normal_dalvik mod.
I had been running incredikernal and Tiny’s CM10.1 Inc builds happily for a long time, but after one of the updates the DInc started acting unstable, and so tried CM7.2, then wanted to try Jelly Bean and so tried Evervolv 4.3, but felt it was missing basic features (voicemail notification, etc), so went back to CM7.2.
While playing music via Bluetooth (phone plugged in to a 5v 1200ma charger if that matters), the phone suddenly died – when powering on it got stuck at the White HTC Incredible screen.
When powering on while pressing the Volume Down button I get:
INCREDIBLEC XD SHIP S-off
HBOOT-0.92.0000
MICROP-0417
Touch Panel-atmelc03_16ac
Radio-2.15.00.07.28
July 23, 2010 18:06:51
When I go to recovery I got the ClockworkMod Recovery v5.0.2.0 Blue menu.
After this menu I got the following errors:
ClockworkMod Recovery v5.0.2.0
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 go to mounts and storage I get:
Mount sdcard - Error mounting /sdcard!
Mount emmc – Error mounting /sdcard!
Update:
I've regained root using Unrevoked3. Still got "can't mount" errors in CWM.
Then tried to fix the SD card mounting problem using the "fastboot oem enableqxdm 0" command. Still getting "can't mount" errors in CWM,
but a different set of errors than before:
ClockworkMod Recovery v2.5.1.2
E:Can't mount /dev/block/mmcblk0p2 (File exists)
E:Can't mount /cache:recovery/command
E:Can't mount /dev/block/mmcblk0p2 (File exists)
E:Can't mount /cache:recovery/log
E:Can't mount /dev/block/mmcblk0p2 (File exists)
Still working on it...
bump
Some phones don't like 1click rooting. Have you tried the command prompt method?
http://forum.xda-developers.com/showthread.php?t=1600904
gyro_platter, thanks for the suggestion. Since my original post I have been able to re-gain root using unrevoked3. It took a few tries, but after removing CWM recovery I was successful.
Al
so you were able to install whatever gingerbread ROM you wanted? or does the problem still persist.
Hi Trozzul, thanks for the inquiry.
The problem still persists. Frankly, I have been trying to solve the "can't mount" problems first. No luck on that front yet either. I have created a new, hopefully clearer, post that reflects the current state of my various problems. Please see
DInc Gingerbread Upgrade problem and Froyo CWM Errors - Can't Mount SDcard and Cache
BelmontAl said:
After my DInc got stuck on the white HTC Incredible screen and trying to restore a nandroid backup failed (see History below), I flashed the stock Froyo PB31IMG from pvillecomp (outside link deleted) and flash in HBOOT directions on that site. The DInc booted up into Froyo 2.2.
I then tried to flash the stock Gingerbread image from that site, but the DInc got stuck in a loop (Droid screen, HTC screen, Droid screen…)
I then flashed back stock Froyo.
I then tried to install ClockWorkMod 5.0.2.0 via HBOOT, with file renamed to PB31IMG (per the instructions on androidforums
incredible-all-things-root/420788-how-regain-root-s-off-htc-unlocked-bootloader.html )
When I get into CWM, I get the following "errors":
ClockworkMod Recovery v5.0.2.0
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
Click to expand...
Click to collapse
I saw those exact symptoms on a phone a friend gave me to fix. My conclusion was hardware failure of the emmc (as I posted in response to another post of yours). I was able to get root on it by pushing the su binary and superuser.apk to their correct locations via adb and fixing their permissions, but froyo was the only rom that would flash. It was in service here until a few days ago when it got dropped into water. When I got around to it, I was gonna give this hack a go:
http://forum.xda-developers.com/showthread.php?t=2175346&page=3
It's a way to completely install the ROM on an sdcard and not use the emmc at all. But since the water incident I think that inc is toast.
musical_chairs,
Thanks for the input. I suspect that my emmc might be bad also. The link you provided looks promising, but it looks like the zip file that Tiny created only works with AOSP ROMs. The only ROM I can get to boot is the standard HTC Froyo ROM, which is Sense. I will study that possibility further.
Thanks again,
Al
BelmontAl said:
musical_chairs,
Thanks for the input. I suspect that my emmc might be bad also. The link you provided looks promising, but it looks like the zip file that Tiny created only works with AOSP ROMs. The only ROM I can get to boot is the standard HTC Froyo ROM, which is Sense. I will study that possibility further.
Thanks again,
Al
Click to expand...
Click to collapse
yeah i saw that too i think it only works with AOSP, i think the problem might be your recovery, i saw that you used two different versions, 5.0.x.x and 2.5.x.x, have you tried the latest, 6.0.X.X? not sure if our ol dinc is update able to 6.0.x.x, i would try another custom recovery too, i know my inc has some flashing issues on CWM
To limit confusion, please use the newer thread. Closed.
http://forum.xda-developers.com/showthread.php?t=2571761
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
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.