My Gw has recently been semi bricked because I was foolish enough to flash a sense 2.1/3.0 over CM7 without flashing, I know, shame on me and don't worry the replacements on the way but this is really aggravating that no matter what online guides say to fix this I just can't seem to do, I DID successfully flash the PC10IMG.zip through hboot and everything went well but that didn't fix the bootloop. I have wiped EVERYTHING and it still loops and still displays the same error "E:Can't Open /cache/recovery/log" proceeded by "E:Can't Open /cache/recovery/last_log". I have tryed using ADB but have yet to even successfully set it up (I've hopped on the ubuntu 10.04 boat). I do have a windows if someone NEEDS me to use ADB to fix this. Any help appreciated.
Sent from my HTC Vision using XDA Premium App
Sorry for the typos, I meant to say "G2" and in the beginningi meant to say "wiping". Would edit but on the XDA app
Sent from my HTC Vision using XDA Premium App
What pcimg did you use? And what's the phone state now?
S-on? S-off hboot? Radio?
I get this error now.
I did the tutorial from RMK40. http://www.virtuousrom.com/
E; nevermind ... I saw at the end of the post that this is needed to happen.. >_>
Related
Earlier today my phone froze. I left it alone for a few minutes to see if it would sort itself out. That didnt happen so I pulled the battery out and rebooted. After having passed the htc boot screen I got stuck on they cyanogenmod boot screen. It constantly kept rebooting but it couldnt get passed the cyanogenmod boot screen. I tried flashing a recovery image with cwm but that didnt work as I got an error that said
"Error while erasing boot image!" followed by
E:Cant mount /cache/recovery/command
E:cant mount /cache/recovery/ log
E:cant open /cache/ recovery/log
E:cant mount /cache/recovery/ last_log
E:cant open /cache/recovery/ last_log
Tried wiping data and cache and installing the newest version of cm7 through a zip and now I cant get passed the htc boot screen.
I was running the cyanogen 7 RC4 mod and did a perm root using the gfree method.
Another one? This is happening so much lately. It's frightening. :[
As far as I know, no one has found a solution or the cause. I have to assume it has something to do with CM.
Every story I've heard, people were running CM7. And they've all been G2s.
I'm personally just going to have to get a replacement through my insurance for $130. Or if I can find a good deal on a Nexus One on ebay, I'd love to do that.
Yea people been having this issue lately. I guess am not even going to flash any other rom right now, untill somebody finds out what's wrong. Really scary stuff. Another thing I saw with the people getting issue is the use gfree method. Well not saying that can be the caused. I hope someone finds a way to fix this.
Sent from my HTC Desire Z/G2 Using XDA Premium App
Getting a bit scared that this error is popping up all over out of seemingly nowhere! I'm gonna be extra careful for the moment.
Sent from my HTC Vision using XDA Premium App
Its because you did something wrong..I have a US G2 and never had this issue nor has it started
Sent from my Vision using XDA Premium App
pokemontrainer4life said:
Another one? This is happening so much lately. It's frightening. :[
As far as I know, no one has found a solution or the cause. I have to assume it has something to do with CM.
Every story I've heard, people were running CM7. And they've all been G2s.
I'm personally just going to have to get a replacement through my insurance for $130. Or if I can find a good deal on a Nexus One on ebay, I'd love to do that.
Click to expand...
Click to collapse
You haven't seen any DZs affected by this issue?
Spastic909 said:
Its because you did something wrong..I have a US G2 and never had this issue nor has it started
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
Did what wrong? It could be but I doubt it since it was running smoothly up until it froze on me.
theSpam said:
You haven't seen any DZs affected by this issue?
Click to expand...
Click to collapse
I haven't read about this happening to any DZs, no.
Spastic909 said:
Its because you did something wrong..I have a US G2 and never had this issue nor has it started
Click to expand...
Click to collapse
Same as Don said. Phone was perfect until it randomly froze.
theSpam said:
You haven't seen any DZs affected by this issue?
Click to expand...
Click to collapse
This happened to my DZ though
If you have Fastboot on your computer and ENG HBOOT, try this in your Terminal/command line:
fastboot flash recovery /path/to/recovery.img
Click to expand...
Click to collapse
Unfortunately I don't have the ENG Hboot. I hope someone figures out a solution soon. I hate my old sidekick -____-
Revert back to full stock and then reroot using gfree.
I thought about trying that before tried doing that by holding the down volume button and then the power button and selecting factory reset but when I select that option nothing happens. Is there some other way to revert?
DON_58 said:
I thought about trying that before tried doing that by holding the down volume button and then the power button and selecting factory reset but when I select that option nothing happens. Is there some other way to revert?
Click to expand...
Click to collapse
Well if you can go to clockwork than the only way is ADB...
Sent from my HTC Desire Z/G2 Using XDA Premium App
do you mean if I CANT access clockwork the only other way is ADB? Because I can access it im just not sure how go about revert to stock.
Well if you can actually open cwm you should be able to mount the sd card and put the stock image on your sd card, then flash it using the hboot.
Sent from my G2 running Cyanogenmod 7.
DON_58 said:
do you mean if I CANT access clockwork the only other way is ADB? Because I can access it im just not sure how go about revert to stock.
Click to expand...
Click to collapse
Sorry I mean to say if you can't. Yea if you can't go in Clockwork then the only thing that would help is Adb(need Eng-hboot). Other than that I don't know my friend
Sent from my HTC Desire Z/G2 Using XDA Premium App
I tried flashing to a stock rom that I got from here
http://forum.xda-developers.com/showthread.php?t=788489
However, I get an error when opening the zip
E: Can't open /sdcard/PC10IMG....
(bad)
Installation aborted
Click to expand...
Click to collapse
When I try and install the new cm7 though, it installs successfully but when rebooted hangs at the htc screen
DON_58 said:
I tried flashing to a stock rom that I got from here
http://forum.xda-developers.com/showthread.php?t=788489
However, I get an error when opening the zip
When I try and install the new cm7 though, it installs successfully but when rebooted hangs at the htc screen
Click to expand...
Click to collapse
PC10IMG files are flashed through the bootloader (white screen with green skateboarding Androids on the bottom), not through recovery. If you have the PC10IMG.zip file on the root of your SD card, simply enter the bootloader (Volume Down + Power) and it should detect the file and ask if you want to flash the ROM.
In recovery, have you tried formatting the system partition as well as data and cache prior to flashing a custom ROM? Also, do you know what version of CWM you were running? Have you checked out the guide on recovering semi-bricks in the dev section? Since you have ADB working, it has some instructions on flashing recovery and such through ADB (so you flash the latest version for example and try again).
DON_58 said:
Earlier today my phone froze. I left it alone for a few minutes to see if it would sort itself out. That didnt happen so I pulled the battery out and rebooted. After having passed the htc boot screen I got stuck on they cyanogenmod boot screen. It constantly kept rebooting but it couldnt get passed the cyanogenmod boot screen. I tried flashing a recovery image with cwm but that didnt work as I got an error that said
"Error while erasing boot image!" followed by
E:Cant mount /cache/recovery/command
E:cant mount /cache/recovery/ log
E:cant open /cache/ recovery/log
E:cant mount /cache/recovery/ last_log
E:cant open /cache/recovery/ last_log
Tried wiping data and cache and installing the newest version of cm7 through a zip and now I cant get passed the htc boot screen.
I was running the cyanogen 7 RC4 mod and did a perm root using the gfree method.
Click to expand...
Click to collapse
I was disscussing the fact that i had the wrong hboot. i was using the one designed for the G2 and I have a DZ. So I decided to change to the correct one, I'm comfortable with ADB so I did not for see any problems. So I flashed the correct hboot 0.84.2000, and everything looked good, rebooted in to bootloader, all good and then finally in to recovery.
Oh crap, some problem as everyone else. You know what they say if "if it ain't broke don't try to fix it". So with that in mind I thought it best to flash back to the G2 hboot. Now I didn't know ADB worked whilst you were in recovery, but it does. I followed the insrtuctions re flashed the G2 hboot and everything works as it did before.
I perm rooted my G2 last night and I have been trying to install the nexdroid ROM for several hours. I followed all the directions and I booted to recovery, wiped all my memory, and when I clicked on the zip file to install, it said something along the lines of:
Cannot find update
Installation aborted.
So later I tried to install the cyanogenmod ROM and the same exac thing happened. I checked with terminal emulator to see that I am still rooted and I still have S-OFF. Any help would be appreciated because the nexdroid ROM looks amazing.
Sent from my T-Mobile G2 using XDA App
having the same exact problem right now, been searching all over and havent found any answers.. someone please help?
(status 7) error in CWm
bbaaccoonn said:
I perm rooted my G2 last night and I have been trying to install the nexdroid ROM for several hours. I followed all the directions and I booted to recovery, wiped all my memory, and when I clicked on the zip file to install, it said something along the lines of:
Cannot find update
Installation aborted.
So later I tried to install the cyanogenmod ROM and the same exac thing happened. I checked with terminal emulator to see that I am still rooted and I still have S-OFF. Any help would be appreciated because the nexdroid ROM looks amazing.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
magnum_touchpro said:
having the same exact problem right now, been searching all over and havent found any answers.. someone please help?
(status 7) error in CWm
Click to expand...
Click to collapse
Are the files on the root of your SD card? If you can find and select the file and it aborts the install it could be a bad file download. I'm not really sure as I've never had that happen.
Either way, If you post this in the Q & A forum you are 100% more likely to get some useful help.
bbaaccoonn said:
I perm rooted my G2 last night and I have been trying to install the nexdroid ROM for several hours. I followed all the directions and I booted to recovery, wiped all my memory, and when I clicked on the zip file to install, it said something along the lines of:
Cannot find update
Installation aborted.
So later I tried to install the cyanogenmod ROM and the same exac thing happened. I checked with terminal emulator to see that I am still rooted and I still have S-OFF. Any help would be appreciated because the nexdroid ROM looks amazing.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
What recovery are you using?
Sent from my HTC Vision using XDA App
ultma75 said:
What recovery are you using?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
* edit* I guess didn't need the help after all
Sent from my HTC Vision using XDA App
i just rooted my galaxy nexus (CDMA/LTE) from verizon and i used uot kitchen to make a custom rom and whenever i go to flash it using cwm it gets to recovery mode and the android shows up lying on its back with a red exclamation point and no text, then eventually reboots...what can i do to fix this problem?
prkchop said:
i just rooted my galaxy nexus (CDMA/LTE) from verizon and i used uot kitchen to make a custom rom and whenever i go to flash it using cwm it gets to recovery mode and the android shows up lying on its back with a red exclamation point and no text, then eventually reboots...what can i do to fix this problem?
Click to expand...
Click to collapse
That is the factory recovery screen on the Nexus. I have found that installing ROM Manager from the market and then using that to flash clockworkmod will fix the issue.
no i understand that but the clockwork recovery wont work, i have it installted and i got to it once but every other time it fails
use root explorer and Rename /system/boot-from-recovery.p to boot-from-recovery.p.bak. that's overwriting CWM. Its a feature that will cause some phones to revert to factory recovery rather than CWM. I think its more relative on your root method as some phones do not seem to need that fix. Others have needed to change their read/write access with root explorer to get it to stick. Otherwise just flash each time before you wish to flash through ROM Manager and then you can still receive and install any OTA updates since permanent clockwork blocks OTA's
Some people have to install CWM via Rom Manager everytime until they do the above ^
I deleted said file and I am now trying to restore to full stock. When I try to get into recovery I get the android on his back with the red exclamation point.. Can someone pull boot-from-recovery.p and post it for me??
how to fix error on Recovery of CWM
hello all XDA-Developers Members, good day! I have a Lenovo Ideapad A1 and last night is I tried to upgrade my Gingerbread 2.3.4 to Cyanogenmod 7 but it didn't work. It appear a Lenovo word on it after i upgrade it .... And when i bring it back to Recovery mode, it appears like this:
E:can't mount /cache/recover/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
Error mounting /cache!
Whenever I bring it back to Gingerbread, it just always appear a word Lenovo ... I am hoping sir/ ma'am that you could help me with this please!!!
Please sir/ ma'am ...
Wrong device
Sent from my Galaxy Nexus using Tapatalk 2
Gingerbread!>? Woah New Android version for us xD
Wrond forum dude
Zepius said:
Wrong device
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Seraz007 said:
Gingerbread!>? Woah New Android version for us xD
Wrond forum dude
Click to expand...
Click to collapse
Yeah he's spamming other forums too. Nice way to get a ban
Sent from my Galaxy Nexus
Pirateghost said:
Yeah he's spamming other forums too. Nice way to get a ban
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Never mind, have to get up early as **** for work, he's seriously wasting our time.
a manta wrote this.
HI everyone, I need some help. My micro USB port went on my phone and VW sent me a replacement. I used the tacoroot temp root methond and the Revolutionary to gain s- off and flashed the newest radio etc. All seemed fine. Fastboot screen say S- off and shows newest radio, I thought great! time to root. Nope..here is what I get:
first of all I have to use adb shell to boot the phone into Revolutionary/CWM recovery. It will not let me do it by holding the power and vol down button.
second when I go into recovery and pick a rom to flash I get this error: E:Can't open /sdcard/xxxx_ rom.zip.
makes no sense to me. Any Ideas?
You didn't receive any errors when using revolutionary? When you boot up your ROM go into settings and look under the power option and make sure fast boot is disabled.
I would go through the whole process again. It sounds like something went wrong in rooting.
Sent from my vivow using xda premium
Thanks for the help Revolutionary is fine
zax10 said:
You didn't receive any errors when using revolutionary? When you boot up your ROM go into settings and look under the power option and make sure fast boot is disabled.
I would go through the whole process again. It sounds like something went wrong in rooting.
Sent from my vivow using xda premium
Click to expand...
Click to collapse
I got some help and of course it was something simple. Bad SD card! Thank you for the help though. Moderator can delete this thread. Thanks again!
Time to update your sig don't ya think
Linch89 said:
Time to update your sig don't ya think
Click to expand...
Click to collapse
Hmm?
I'm so fresh you can suck my nits...
He's talking about OP sig its outdated lol
Sent from my Goonified Paranoid Jelly Droid Incredible 2
Tried to root and flash a new rom. I believe the root worked however phone keeps rebooting into clockworkMod Recovery. Prior to rooting it i tried to downgrade my operating system but that didn't work. unlocked the htc bootloader and i was even able to flash clockworkMod Reocvery v6.0.1.1 touch on the phone. Still everytime that i install the rom which is cm7.1.0.1 it always reboots into CMR v5.0.2.0. I may have flashed recovery reboot onto the phone which may or may not explain what happened. i don't know. I just know that my phone is messed up and I want to fix it. Any help would be appreciated. I can bring up HBOOT and CMR 6 in addition to v5 but thats all i can bring up. Please HELP
You're just S on still. To get S off there are a couple forums around here.
Sent from my ADR6350 using xda app-developers app
FordNate said:
You're just S on still. To get S off there are a couple forums around here.
Sent from my ADR6350 using xda app-developers app[/QUOTE
I've been trying to get S-Off but the problem my computer keeps telling me that it cannot complete those commands. I was trying to do s-off from this think in the forums http://forum.xda-developers.com/showthread.php?t=1751796
Click to expand...
Click to collapse