I had a rooted EVO, but I had to unroot because I was spending too much time messing around with the phone and not enough time studying for the bar exam...
Anyways, now I am running a stock 1.47 w/ the radio, etc....everything works perfectly (4g, etc, etc). However, when I boot into bootloader and go to the stock EVO recovery, it has this error on the bottom:
E:Can't open /cache/recovery/command
I just want to make sure that when I decide to root again next week, that this won't give me any problems.
Related
As per the title. I was using it just happily on the bus when it froze. After pulling the battery, it just vibrated three times and the red led flashed. I don't recall what I was doing at the time but it was something harmless - reading email I think - I was quite surprised at this otherwise super stable phone freezing.
Until this time I was happily running CM7nightly 35 (approx) with lastest Pershoot kernel, OCd to around 1200MHz.
I can power up in Clockwork mod recovery 3.0.0.5 and have tried restoring various backups I have and tried reflashing CM7RC4. Trying a regular boot just sticks on the white HTC screen.
When in Clockwork mod it complains:
E:Can't open: /cache/recovery/log
E:Can't open: /cache/recovery/log
E:Can't open: /cache/recovery/last_log
E:Can't open: /cache/recovery/last_log
I tried formatting it but it still complains afterwards.
Error formatting /cache!
ARGH!
I would love some suggestions please.
EDIT: Now I see http://forum.xda-developers.com/showthread.php?t=949733 which seems identical. I will follow up there. Please do the same if you have suggestions.
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
My g2 will not boot up. It gets to the HTC screen and freezes. When I boot into recovery I get these error messages. 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
After doing a lot of reading on xda and speaking with a few people on #g2root on irc they determined the emmc is bad. I called HTC repair and got authorized to return the phone. I told them the phone just stopped working. It's 2 months old and still under warranty. They read off a list of things that would make the warranty void. My phone is rooted and has the desire z hboot. Is there anything I can do so HTC can't tell the phone is rooted? Thanks for the help.
ive seen some people that have had their phones changed even if they were rooted because of the bad emmc
Mailed it in today. I'll keep my fingers crossed they don't catch the root.
I'll keep everyone updated.
Got my phone back on August 23rd. Phone is as good as new. Quick and painless turn around.
talk about a hole in one
Hi All,
I rooted my AMOLED Desire (on T-Mobile) back in June when it was a year old, did it through Unrevoked with ClockworkMod, flashed CM7, never looked back.
Got my Wife a SLCD Desire (on Orange) just after Christmas last year and now want to put CM7 on hers too.
Did the back ups, went to do the Unrevoked and it failed first time. Did it a couple of times and it seemed to go through OK. Booted fine, showed the SU app in the App Drawer. All seemed good to now backup the ROM from Recovery and flash CM7 + GAPPS + Radio.
However, when attempting the backup, I got these messages:
E:Can't mount CACHE:recovery/log
E:Can't find MISC:
E:Can't mount CACHE:recovery/command
E:Can't find MISC:
The phone still boots fine, it is not bricked. Recovery works fine, but few options run with out giving these messages. I have re formatted the SD Card, but from searching, drive E: is internal.
I tried running Unrevoked again to flash Amon Ra, but it could not achieve root, asking if the firmware was too new.
The option is to use ClockworkMod to format Data &/or System, but was reluctant to just proceed with this action before consulting you guys!
Anyone able to give advice based on experience rather than guesswork!?
Many thanks in advance!
Steve
SteveBishy said:
Hi All,
I rooted my AMOLED Desire (on T-Mobile) back in June when it was a year old, did it through Unrevoked with ClockworkMod, flashed CM7, never looked back.
Got my Wife a SLCD Desire (on Orange) just after Christmas last year and now want to put CM7 on hers too.
Did the back ups, went to do the Unrevoked and it failed first time. Did it a couple of times and it seemed to go through OK. Booted fine, showed the SU app in the App Drawer. All seemed good to now backup the ROM from Recovery and flash CM7 + GAPPS + Radio.
However, when attempting the backup, I got these messages:
E:Can't mount CACHE:recovery/log
E:Can't find MISC:
E:Can't mount CACHE:recovery/command
E:Can't find MISC:
The phone still boots fine, it is not bricked. Recovery works fine, but few options run with out giving these messages. I have re formatted the SD Card, but from searching, drive E: is internal.
I tried running Unrevoked again to flash Amon Ra, but it could not achieve root, asking if the firmware was too new.
The option is to use ClockworkMod to format Data &/or System, but was reluctant to just proceed with this action before consulting you guys!
Anyone able to give advice based on experience rather than guesswork!?
Many thanks in advance!
Steve
Click to expand...
Click to collapse
I dont know a lot about it, but E: is NOT a drive, a rookie mistake as I originally thought that, it just means Error: so its saying there are 4 errors as above!
Im sure somebody with more knowledge will come along soon to help you out, sorry I couldnt have been more help
Arty.
I used to get something like that too its fine.. if you're really bothered about it then S-OFF and then use android flasher to flash a new recovery.. which could solve the problem for you.
Sorted
Turns out the problem was because of the PVT4 thing, mine is PVT1 and I didn't get this trouble.
This site described my exact problem and gave me answer that I went with:
ht tp:// www .roms-au. com/installation/rooting/pvt4-issues/
The frustrating thing was that I couldn't find a Linux version of Unrevoked 3.21 anywhere, so had to go through Windoze and **** about with the whole HTC Sync and HBOOT driver stuff.
Still, it worked, so worth it in the end.
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