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.
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
I would love your guy's opinions on this issue. I was planning to do a fresh install of Cyanogenmod due to wifi issues when I ran into some trouble. I just updated my Clockworkmod recovery from 3.0.0.8 to 5.0.2.0 this morning, and it has been bringing up errors along the lines of:
Code:
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/log
E: Error in /cache/recovery/log
(Read-only file system)
I read up on these errors, and it seems that attempting to flash ROMs and whatnot with these errors often lead to bricked devices. So far, my device still works fine (minus the WiFi, obviously), and I've successfully flashed the recovery several times, performed a nandroid backup, and reflashed my kernel without error, as far as I can tell. However, given the nature of these errors, I am much too nervous to try reflashing Cyanogenmod. So far I have attempted downgrading CWM, checking my emmc and checked the cache partition for the files CWM supposedly can't open. last_log is present, but log is not. From the results of the emmc test, I think it's working fine, but I'd like you guys to verify that for me. Below is about as detailed a log as I can give of what has happened today. Any assistance in fixing this problem and making sure it is safe to reflash Cyanogenmod would be extermely appereciated.
Phone Info
HTC Droid Incredible (ADR6300)
Cyanogenmod 7.1.0 RC1
Android 2.3.4
Clockworkmod Recovery 3.0.0.8
Incredikernel 2.6.38.8 (8/15/11)
HBOOT 0.92.0000
Radio 2.15.00.07.28
S-OFF
Code:
Events leading up to this:
Flashed CWM 5.0.2.0 through ROM Manager-flash failed
Rebooted into recovery-still running 3.0.0.8
Rebooted phone
Tried again through ROM Manager with "erase recovery" option checked
Rebooted into recovery-still running 3.0.0.8
Rebooted phone
Flashed CWM 5.0.2.0 through Terminal Emulator
Rebooted into recovery-flash was successful
Rebooted phone
Discovered WiFi error issue
Rebooted into CWM 5.0.2.0
Performed a nandroid backup, which appeared to be successful
Errors appeared at some point, can't remember when.
"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"
Rebooted phone
Rebooted into CWM 5.0.2.0
Wiped Dalvik cache and reflashed incredikernel, thinking it would fix the WiFi issue
Flash seemed successful, same errors popped up again, can't remember exactly when
Rebooted phone
Researched errors, came to notice that navigating menus and backing out now caused:
"E: Error in /cache/recovery/log
(Read-only file system)
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log"
Further navigation would always produce:
"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"
Code:
Steps taken to fix the problem (so far)
Tried flashing CWM 3.0.0.8 through ROM Mangager
Rebooted into recovery-still running 5.0.2.0
Tried flashing CWM 3.0.0.8 through adb
Rebooted into recovery-flash was successful
Errors still persisted
Found a thread suggesting the problem may be with a faulty emmc
Ran "cat /proc/kmsg | grep mmc0" through adb to test the emmc
Results of test
Checked to see if log and last_log files exist
Found last_log, not log
Images of the problem
Results of the emmc test
Errors in CWM 5.0.2.0
Errors in CWM 3.0.0.8
last_log is present in /cache/recovery
Have you wiped the cache partition from recovery and then flash cwm recovery from hboot as a PB31IMG.zip?
How exactly do I go about doing that? I know how to wipe the cache, but do I just rename the CWM zip to PB31IMG.zip and flash it?
Rixanu said:
How exactly do I go about doing that? I know how to wipe the cache, but do I just rename the CWM zip to PB31IMG.zip and flash it?
Click to expand...
Click to collapse
Um not sure what file you have but here is one for you http://dinc.does-it.net/PB31IMG.zip, just place it on the root of your sdcard and boot into hboot. It will find the file after a couple secs and prompt to press vol up to install. This is version 5.0.1.0
Also you may want to run fix permisions from the advanced menu in recovery.
You are quite the lifesaver, it worked like a charm! One more question, though. I would like to upgrade CWM to 5.0.2.0 if possible. Would it be safe to flash it through terminal emulator/adb, or should I just update through hboot from now on? Thanks so much for your help!
Rixanu said:
You are quite the lifesaver, it worked like a charm! One more question, though. I would like to upgrade CWM to 5.0.2.0 if possible. Would it be safe to flash it through terminal emulator/adb, or should I just update through hboot from now on? Thanks so much for your help!
Click to expand...
Click to collapse
No problem. Hboot is the best way to do it. I dont have a 5.0.2.0 file at the moment but if you need one i can get it for you.
Edit: you could also update it thru rom manager and if for some reason it messes something up just flash the one from earlier post again.
That's alright, I found one a few minutes ago, just in case. This also seems to have fixed my wifi issue, so this is about the best case scenario I can picture. Thanks again!
Your welcome.
I guess all is not as it seems. The problem in CWM started popping up again just a few minutes ago. On top of that, when I rebooted, I got caught in a bootloop. I managed to boot up fine after a battery pull, but this is really starting to scare me. Does anyone have any advice?
PS. I'm posting here because I feel this doesn't need a whole new topic. If that would be better, just let me know.
Rixanu said:
I guess all is not as it seems. The problem in CWM started popping up again just a few minutes ago. On top of that, when I rebooted, I got caught in a bootloop. I managed to boot up fine after a battery pull, but this is really starting to scare me. Does anyone have any advice?
PS. I'm posting here because I feel this doesn't need a whole new topic. If that would be better, just let me know.
Click to expand...
Click to collapse
I would revert back to CWM 3.0.0.8 thru rom manager for awile and see if the problem still persists. However once you do make sure to make a new nandroid as i dont believe cwm 5 backups are compatible with version 3.
Rom manager didn't work (again), so I flashed through hboot and it worked fine. Errors are gone, and no more bootloops since last night. I'm gonna wipe and reflash Cyanogen later today because my wifi is all buggy again and I feel as if a clean install may hopefully kill any latent symptoms. Feel free to let me know it that's a bad idea, haha. Thanks again.
Hi Everyone,
I did a boo boo. I flashed my One X without a supported CID with the Android Revolution 14.2 ROM. Is there a way to correct this and revert back to my previous ICS? Help please.
There's a Q&A section especially for Questions and Answers, please use that in future.
That being said you wouldn't have been able to update the hboot so just reflash an ICS rom
ClydeB1 said:
There's a Q&A section especially for Questions and Answers, please use that in future.
That being said you wouldn't have been able to update the hboot so just reflash an ICS rom
Click to expand...
Click to collapse
I'm having problems moving an ICS ROM to the phone to flash it. Whenever I connect the phone to my notebook, the MTP USB device driver is unable to install. because of that Windows could not recognize the phone. I also tried to mount the sdcard in CWM. It is giving me a 'unable to open ums lunfile..." error message.
Is there any other way to flash the phone? I tried "fastboot flash zip rom.zip". It showed OKAY for the copy, however, a second line remark "writing 'zip' ... FAILED (remote not allowed)" appeared. The process then was aborted.
I also tried formatting the sdcard and then tried to mount the sdcard. Same 'unable to open ums lunfile...' error constantly appears. Just afraid that my phone is now a brick. Can anyone help? Thanks in advance.
kevintan12 said:
I'm having problems moving an ICS ROM to the phone to flash it. Whenever I connect the phone to my notebook, the MTP USB device driver is unable to install. because of that Windows could not recognize the phone. I also tried to mount the sdcard in CWM. It is giving me a 'unable to open ums lunfile..." error message.
Click to expand...
Click to collapse
Install a version of CWM that isn't ancient, I.e., 5.8.4.0.
I suspect that I hard brick my phone now.
Following some advice to "fastboot flash recovery recovery.zip", not the phone is unable to even get into recovery mode. when I select recovery, it just comes back to the bootloader screen. I tried to flash CWM again and the message I got was "error: cannot load cwd....img"
Funny thing though, when i select HBOOT, some messages appears and disappears saying "Failed to open sdcard, dalvik, cache, etc. etc." I believe that is why windows is unable to recognize the USB drive and is unable to install the drivers.
Have I hard brick my phone?
kevintan12 said:
I suspect that I hard brick my phone now.
Following some advice to "fastboot flash recovery recovery.zip", not the phone is unable to even get into recovery mode. when I select recovery, it just comes back to the bootloader screen. I tried to flash CWM again and the message I got was "error: cannot load cwd....img"
Funny thing though, when i select HBOOT, some messages appears and disappears saying "Failed to open sdcard, dalvik, cache, etc. etc." I believe that is why windows is unable to recognize the USB drive and is unable to install the drivers.
Have I hard brick my phone?
Click to expand...
Click to collapse
No, everything is recoverable, if your phone won't turn on at all, then you're bricked for real.
Just flash the one from here:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
then put in the same folder as fastboot and use command:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Thanks everyone for the advice. Really appreciate it. I finally managed to use TeamWin Projects and it allowed me to mount the USB. Managed to then transfer an ICS ROM for flashing.
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
Team,
I've consider myself a fairly intermediate android root user. I've been doing this for many years, and have never had an issue that I was able to get out of (with the help of the xda community, of course). I've personally never had to post a question on here because I'm always able to find someone who has a similar issue to me. Today though, I am stumped...
I've been happily running Slimkat: http://forum.xda-developers.com/showthread.php?t=2590649 for the past few weeks.
This morning, I decided to try the ElementaX kernel (http://forum.xda-developers.com/showthread.php?t=2249774). After flashing the Kernel, my phone refused to boot up. Usually, I would just reboot into recovery and re-flash the ROM I've running (which includes the ROM's kernel). Every single time I've flashed an incompatible kernel in the past, this method has worked.
After choosing to flash the ROM, it got stuck while installing. The installation just sat there for at least 20 minutes.
Next step - I decided to wipe data/factory reset and then re-flash the rom. Data was able to be wiped, but then it got stuck on formatting cache....
So I hard reset, and decide to restore my nandroid backup - As soon as I boot up CWM Recovery, I get this message
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
When I tried to restore the backup, it just timed out again...
I reflashed CMW REcovery via fastboot, and even tried TWRP Recovery. Nothing seems to work.
If I try and restore my nondroid backup now, I get an MD5 mismatch.
I'm unable to mount /system, /cache and I'm getting nothing when I try and mount USB storage.
I've soft-bricked devices before (we are all careless sometimes), but I was always able to find a solution somewhere. I think I got myself into a situation that's a bit above my paygrade.
Any help would be greatly appreciated.
Thanks.
Are you sure you reflashed the correct recovery? Try this one just for kicks http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img If it still dosent work, i would try an ruu.
cmlusco,
Thanks for the quick reply. I flashed the recovery - Unable to mount System or Cache and PC is not detecting any devices when activating ADB sideload through TWRP.
To be honest, I never of an RUU before. I can research the topic. If you know of any threads that could help me along the process, I would definitely check them out.
thanks again.
The RUU method worked! Thank you very much for suggesting that.
Here's what I did.
1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/showthread.php?t=2428276)
2. Rename to "ruu.zip" (Optional)
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
Thanks again,
OMG OMG OMG... you saved me
Pharaohnee said:
The RUU method worked! Thank you very much for suggesting that.
Here's what I did.
1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/showthread.php?t=2428276)
2. Rename to "ruu.zip" (Optional)
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
Thanks again,
Click to expand...
Click to collapse
Some of the RUU's i found the download was funky but here's the one that finally worked
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
I was stuck in this situation... something with my cache got messed up when I tried to let ROM Manager update my CWMR... never again.
Glad you got it worked out, could you put solved in thread title it help others, thanks