Develop Bugs

[Q] HTC One V Recovery doesn't work, Phone Stuck

Hi Y'all, sometime lurker, first time poster.
I got an HTC One V (CDMA, Virgin Mobile) today and given the relative ease of rooting my old Droid Inc I thought it would be a breeze to do this phone as well, but I did not do enough research and messed it up. Here is what I did as best as I can recall:
I unlocked the bootloader without a problem using Fastboot.
Then I flashed CWM recovery through hasoon2000's all in one tool, but it didn't work. I believe I did not flash the correct CWM (CDMA). I tried reflashing stock recovery, and then CDMA CWM recovery, but I couldn't get past the white HTC with the red warning message.
Because I couldn't get recovery to work, I thought maybe I should flash the kernel. I was using hasoon2000's all in one tool, but I did not realize that it would try to boot into recovery in the middle of flashing the kernel (yeah, I'm a noob and an idiot).
So now it won't load into the standard ROM anymore, it just gets stuck on the HTC White screen with the Red Warning. I can get it to load the bootloader, and I tried flashing the kernel from the all in one tool through fastboot, but it didn't work.
Is there any way I can save my phone or am I out of luck?
Thanks for any help you can provide.

Get the stock boot.img and put it in your fast boot folder and go to cmd prompt and type
C:\fastboot
Fast boot flash boot boot.IMG
Make sure your in fastboot
Sent from my One V using xda app-developers app

Thanks XxlemonxX. I did that a few times and it didn't seem to stick.
But! While I was fastloading I went ahead and did the Superboot step found here:
http://forum.xda-developers.com/showthread.php?t=1598964
And the phone restarted! Huzzah! Now I just have to see if I can get a recovery actually working...

OK, so things got a little strange.
The phone booted up just fine, so I tried flashing CWM recovery again. It worked, and restarted into CWM recovery. The power button didn't seem to work for selecting various options for a while, it would just go to the screen with the cog and the top hat, until I held it down for a few seconds, after which the bottom buttons flashed, and at the bottom it said "back button enabled". Then the power button worked for selecting various options. (I'm not sure if this is how CWM recovery is supposed to work for the One V, as I can't find any definitive answers...). Anyways, ran a backup through recovery, but afterwards the phone wouldn't reboot again.
Since it worked before I ran the Superboot app through windows and bam, starts up again. Did a factory reset just to see if that would clear the rebooting problem, but it didn't. It did change, however. Now it goes to the white HTC screen with the red warning for a second, goes back to black, then goes to a really dark black with just the red warning barely visible for about 7~ seconds, then it powers down. The only way I can get a reboot into the ROM is to redo the Superboot app...
I'm a little nervous at this point. I tried flashing an MIUI rom through the CWM app but there was an error (I didn't write it down, sorry), and I can't find a reliable link to the stock RUU VM PrimoC Rom (jmz's links are down as far as I can tell). I just want a rom that will reboot without freezing, haha. Thanks again for any help.
tl;dr Phone only boots when Superboot app is flashed, try a different rom?

jimmymcsnakes said:
OK, so things got a little strange.
The phone booted up just fine, so I tried flashing CWM recovery again. It worked, and restarted into CWM recovery. The power button didn't seem to work for selecting various options for a while, it would just go to the screen with the cog and the top hat, until I held it down for a few seconds, after which the bottom buttons flashed, and at the bottom it said "back button enabled". Then the power button worked for selecting various options. (I'm not sure if this is how CWM recovery is supposed to work for the One V, as I can't find any definitive answers...). Anyways, ran a backup through recovery, but afterwards the phone wouldn't reboot again.
Since it worked before I ran the Superboot app through windows and bam, starts up again. Did a factory reset just to see if that would clear the rebooting problem, but it didn't. It did change, however. Now it goes to the white HTC screen with the red warning for a second, goes back to black, then goes to a really dark black with just the red warning barely visible for about 7~ seconds, then it powers down. The only way I can get a reboot into the ROM is to redo the Superboot app...
I'm a little nervous at this point. I tried flashing an MIUI rom through the CWM app but there was an error (I didn't write it down, sorry), and I can't find a reliable link to the stock RUU VM PrimoC Rom (jmz's links are down as far as I can tell). I just want a rom that will reboot without freezing, haha. Thanks again for any help.
tl;dr Phone only boots when Superboot app is flashed, try a different rom?
Click to expand...
Click to collapse
That is an old cwm. thats how it operates. Once your booted into the system you can install rom manager from play store and then you can update cwm so you wont have to enable the power button for use. But anyway seems you cant boot into a stable system right now. So If you are willing to follow theses instructions you can get back to factory conditions.
1. get the fastboot package if you dont have it. http://www.mediafire.com/?4dx982z93w8z7wk and put those files in a folder in the C drive.
2. Get the ruu from here its the top one if you are virgin mobile US. http://www.filefactory.com/f/0eafb9c43276c308/ look for RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
3. This is how your going to get the stock recovery and stock kernel. run the ruu but dont do anything with it just yet. After the ruu is opened and is at the welcome screen just click and drag the window down out of the way and open ANY folder and type %temp% in the address bar of that folder and press enter. You will see a bunch of folders with titles like this "{B2B09672-51AB-4EF6-BDDF-50CB9719052B}" This is just an example. While in that temp folder just do a search for rom.zip and when you find it you can copy that file to your desktop and then just click cancel in the ruu welcome screen for now.
4. Open the rom.zip file with 7zip. You must use 7zip. The built in windows zip program wont work. Once its opened with 7zip, extract these two files 'recovery_signed.img' and 'boot_signed.img'. This is your stock recovery and stock kernel. Extract those to the fastboot folder.
5. You must somehow get your device into the bootloader again. I had the same symptoms as you did with the dark screen and dim red text. I just kept playing with the volume down during boot and eventualy got there. DO NOT USE VOLUME UP!!
6. Once your in the bootloader choose fastboot and plug your device in and it should now say fastboot usb at the top of the bootloader screen. Now run theses commands.
7. Commands to run.
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
8. Now while in bootloader fastboot usb still just run the ruu and follow all instructions. Make sure you have atleast 30% battery while performing this. And if all goes well you will be back to square one.

[Q] DHD woes

Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?

MerkyBlud said:
Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?
Click to expand...
Click to collapse
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium

MaratabHashmi said:
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
S-off requires rooting it first, am I right? Not having much luck with that - HTC Quickroot claims its been done but none of the apps such as SuperUser are present when it reboots...

Suggestions anyone? efforts to S-OFF not working so far...:fingers-crossed:

You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?

bananagranola said:
You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?
Click to expand...
Click to collapse
I'm trying running the .exe file from the pc, I'm 99.9% sure its the correct region (3UK stock). It gets as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (tried 3 different cables and there is no issue with faulty cables, or either end being unplugged, ). ADB doesnt see the phone as connected. Fastboot doesnt seem to do much as usually when the phone reboots as part of the process it freezes or goes back into bootloop. I've tried putting ROMs on the sd card and updating from the recovery menu but the phone doesnt see the card as mounted in this mode (when it does boot and run ok for a few minutes it does eventually see the card).

I'm confused. You have a recovery menu? Is your phone's bootloader unlocked?

Sorry, I mean the menu accessed through power on + vol down. No, tried unlocking it through the HTC site but no joy.

That's the bootloader. What procedure are you using for fastboot?

Via ADB commands - havent tried with fastboot methods recently though so I forget which particular guide I was using. I'm sure there are all kinds of noob alarms and flashing lights going off somewhere

You cannot run a RUU from adb. Only fastboot.

Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S

MerkyBlud said:
Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S
Click to expand...
Click to collapse
You need to change to the correct folder on your PC where your fastboot.exe file is, thats why your getting your error.
Why you trying to flash stock recovery? Unless I missed it, From what I can see on your posts your still s-on, so you can't flash anything like that from fastboot anyway.
Sent from my GT-I9505 using xda app-developers app

The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.

bananagranola said:
The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.
Click to expand...
Click to collapse
Yeah, I was initially trying to run the RUU.exe but that method wasn't working as I mentioned, so I tried extracting the rom it created and flashing that via fastboot.(Didn't know that shift/rightclick thing, thanks). As for s-off I haven't found a way of doing that without rooting, hence why I thought I couldn't get anywhere without rooting the phone first.
When I try and unlock the bootloader ( at http://www.htcdev.com/bootloader/ruu-downloads) , it wants to update the HBOOT first, this is how far I get with the process:
"BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
To install the RUU, simply follow these instructions:
On your phone, enable USB debugging. (From the Home screen, MENU > Settings > Applications > Development > Check USB debugging)
Connect your phone to the computer using the USB cable that came with your phone. Wait a moment for your computer to identify your phone, this may take a few minutes. After your computer has found your phone, double click on the RUU to start the process"
I get as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (so exactly the same problem trying to update the HBOOT as trying to run the RUU.exe) so I'm not sure how I'm going to unlock the bootloader if this method isn't working - direct .exe method doesnt work, and the process I need to unlock the bootloader so I can flash via fastboot doesnt work for the same reason.

Have you tried booting into bootloader and choosing fastboot before trying the RUU?

Yep. Same USB connection error despite having 'FASTBOOT USB' showing....

Type "fastboot devices." What does it say? Do you have your drivers from HTC Sync installed?

Hi all, had the phone working ok for a while, it wanted to do a software update which froze at 12%, however after cancelling it the phone seems to be problem free. Dont really get this as surely the incomplete update wouldnt take..? but something must have changed. The phones been ok for over a week now although I havent rebooted it or let the battery run flat...still dont trust it entirely!

[Q] Red Triangle and Exclamation point - won't boot and PC won't recognize

I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you

Look at the following thread, may be this can help
http://forum.xda-developers.com/showthread.php?t=2662787
Dugoutdog said:
I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you
Click to expand...
Click to collapse

Dugoutdog said:
I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you
Click to expand...
Click to collapse
Did you try and update while having a custom recovery and/or Rom installed? Also bootloader is power+volume down. The ota won't effect s off or locked status. Just get to fastboot and boot to RUU mode and run stock RUU. Then take updates to 4.4.2

Just a little more info Gizmoe please
Gizmoe said:
Did you try and update while having a custom recovery and/or Rom installed? Also bootloader is power+volume down. The ota won't effect s off or locked status. Just get to fastboot and boot to RUU mode and run stock RUU. Then take updates to 4.4.2
Click to expand...
Click to collapse
I wrote of my problem in middle of night and blanked on getting to bootloader. I am there now. Fastboot takes me to Fastboot USB. RUU mode isn't an option under fastboot just bootloader, reboot, reboot bootloader, and power down. My PC is not recognizing the phone. I was running stock ROM. I don't recall doing anything special as far as recovery since that would be beyond my learning curve.

Dugoutdog said:
I wrote of my problem in middle of night and blanked on getting to bootloader. I am there now. Fastboot takes me to Fastboot USB. RUU mode isn't an option under fastboot just bootloader, reboot, reboot bootloader, and power down. My PC is not recognizing the phone. I was running stock ROM. I don't recall doing anything special as far as recovery since that would be beyond my learning curve.
Click to expand...
Click to collapse
Can you send fastboot commands like
Code:
Fastboot devices
And see your device listed?

PS: to above
Also just noticed my phone is now saying UNLOCKED which it wasn't before. Just S-Off through roadrunner (and still S-Off). . My contract was up on Friday and called Verizon to get unlock info but they said they didn't supply that info. I needed to go to a third party (figures).

Dugoutdog said:
Also just noticed my phone is now saying UNLOCKED which it wasn't before. Just S-Off through roadrunner (and still S-Off). . My contract was up on Friday and called Verizon to get unlock info but they said they didn't supply that info. I needed to go to a third party (figures).
Click to expand...
Click to collapse
Did you read my other post. Can you confirm if you have fastboot connectivity? RUU mode is a command not a list option.

gizmoe
I can get to the FASTBOOT USB command with bootloader, reboot, reboot bootloader, and power down. My PC made a nolise as if it recognized and connected to the phone but it is not listed.

Dugoutdog said:
I can get to the FASTBOOT USB command with bootloader, reboot, reboot bootloader, and power down. My PC made a nolise as if it recognized and connected to the phone but it is not listed.
Click to expand...
Click to collapse
You have connectivity then. It's not going to list it in " my computer" unless its booted into Rom. Just use this thread
http://forum.xda-developers.com/showthread.php?p=46286588
To flash RUU. Don't do relock or s on just flash the stock RUU.

This is where I'm lost again
If I can't see it in my computer then where do I type the codes? I'm very appreciative of your help but I'm in uncharted waters here.

Dugoutdog said:
If I can't see it in my computer then where do I type the codes? I'm very appreciative of your help but I'm in uncharted waters here.
Click to expand...
Click to collapse
Use cmd prompt. Did you setup adb/fastboot when you used rumrunners? In command prompt with phone plugged in while on boot loader screen type fastboot devices. If you see a serial number returned you are connected. Typing fastboot oem rebootRUU will put the phone into RUU mode where you can flash the decrypted RUU.

my sub-directory
Gizmoe said:
Use cmd prompt. Did you setup adb/fastboot when you used rumrunners? In command prompt with phone plugged in while on boot loader screen type fastboot devices. If you see a serial number returned you are connected. Typing fastboot oem rebootRUU will put the phone into RUU mode where you can flash the decrypted RUU.
Click to expand...
Click to collapse
So far so good. It returned FA37GS912166 fastboot.
Typing as directed it returned
<bootloader> Start Verify: 0
OKAY [0.050s]
finished. total time 0.050s
I have a black screen on my device with a white htc showing. Now I just don't know where to get the stock RUU. I went to nosroms.com but page is gone. Went to htc1guru.com and found this one there.
RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted
File Size: 1.1 GiB - Downloads: 1170
MD5: 2704d492d580887e2741c8a6b7fd620e
Comments: modelid: PN0731000
cidnum: VZW__001
It's downloading but REAL slow. Might be done by the time I hear back from you regarding folder.

Dugoutdog said:
So far so good. It returned FA37GS912166 fastboot.
Typing as directed it returned
<bootloader> Start Verify: 0
OKAY [0.050s]
finished. total time 0.050s
I have a black screen on my device with a white htc showing. Now I just don't know where to get the stock RUU. I went to nosroms.com but page is gone. Went to htc1guru.com and found this one there.
RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted
File Size: 1.1 GiB - Downloads: 1170
MD5: 2704d492d580887e2741c8a6b7fd620e
Comments: modelid: PN0731000
cidnum: VZW__001
It's downloading but REAL slow. Might be done by the time I hear back from you regarding folder.
Click to expand...
Click to collapse
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621

now waiting
Gizmoe said:
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Waiting for download to finish and getting ready for work. It will be close to see if I get it done before I have to leave. If not will finish at 3:00am when I get home and get back to you either way.

almost home
Gizmoe said:
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Ok. Have santods file "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted". I can't remember....do I leave it zipped? If unzipped what file do I use??? recovery_signed.img? If left zipped where must the directory be located? if unzipped where do the files have to be?
I won't forget a big thanks when this is done but thanks for getting me this far. Awaiting your reply.

Dugoutdog said:
Ok. Have santods file "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted". I can't remember....do I leave it zipped? If unzipped what file do I use??? recovery_signed.img? If left zipped where must the directory be located? if unzipped where do the files have to be?
I won't forget a big thanks when this is done but thanks for getting me this far. Awaiting your reply.
Click to expand...
Click to collapse
Just leave it zipped. Rename to RUU. Then put it in same directory you are in while using cmd prompt. Then type fastboot oem rebootRUU. Once phone is on black screen with silver letters type fastboot flash zip RUU.zip it will do some stuff and then fail saying to flush the image. Just repeat the fastboot flash zip RUU.zip again and it will succeed. You then will be complete stock. Then you should have no problems updating to kitkat either.

Command Error
Gizmoe said:
Just leave it zipped. Rename to RUU. Then put it in same directory you are in while using cmd prompt. Then type fastboot oem rebootRUU. Once phone is on black screen with silver letters type fastboot flash zip RUU.zip it will do some stuff and then fail saying to flush the image. Just repeat the fastboot flash zip RUU.zip again and it will succeed. You then will be complete stock. Then you should have no problems updating to kitkat either.
Click to expand...
Click to collapse
I'm getting a {ERR} command error.
entered " fastboot oem rebootRUU.zip" also tried fastboot oem rebootRUU", "fastboot oem reboot RUU", and "fastboot oem reboot RUU.zip" in case you forgot the space between reboot and RUU.
It is in the directory where the fastboot.exe is located. It is a zipped folder called RUU.zip.
I called in SL for tonight as I really want to get this done tonight. Too much at stake.

Dugoutdog said:
I'm getting a {ERR} command error.
entered " fastboot oem rebootRUU.zip" also tried fastboot oem rebootRUU", "fastboot oem reboot RUU", and "fastboot oem reboot RUU.zip" in case you forgot the space between reboot and RUU.
It is in the directory where the fastboot.exe is located. It is a zipped folder called RUU.zip.
I called in SL for tonight as I really want to get this done tonight. Too much at stake.
Click to expand...
Click to collapse
First type fastboot devices and make sure its connected. Phone needs to be in fast boot mode. Screen should read fastboot usb in red letters. Then type exactly
Fastboot oem rebootRUU
Then
Fastboot flash zip RUU.zip
RUU.zip needs to be in the same directory cmd is reading.

Something is happening . . . . . "sending zip"

resent as failed like you said.
failed as you stated . . . resent. It also said failed resend immediately. something is gyrating.
OK. at bottom of command prompt it says "Successful OKAY 249.248s" Finished total time 312.192 sec.
My phone has HTC in white small letters and a solid green bar below it.
Before I screw anything from this point, what do I do now? Just press the power button?

[Q] i may have semi bricked my phone please help

hello android geniuses first of sorry about this once my phone is working again i will not mess with it anymore
okay so i was feeling cool and rooted my htc one m7 from verizon then i turned s-off and unlocked bootloader
then i flashed a custom rom it was paranoid android everything worked except i wasnt getting any service on the phone so i was told to flash a verizon htc one rom so i went and flashed viper 6.2 but the phone got stuck in a bootloop so for some reason i thought that doing a factory reset/wipe from the recovery would fix it....it didnt and now i cant reflash the rom either....i tried to sideload but adb wont recognize my device while fastboot recognizes the phone adb wont
what am i to do?

Well im not sure of any other methods to try but i had loads of problems myself pushing files to the SDcard threw twrp and cwm recoveries, so the way I went about it was doing a decrypted RUU to return the phone to stock then once it loaded up in Android I pushed the Rom to the SDcard card then rebooted and started over.
Goto this thread http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
All the way at the bottom you should see some links for RUU's, I used the one labeled "1.10.605.15 Decrypted RUU" You will flash this the same way as you would a firmware update, if you dont know how thats done that post will explain it all. After you flash the RUU reboot and it should be back to the day you got it, but you will still be s-off, at that point just put a custom recovery back on and flash away, however that RUU will downgrade your firmware so you might wanna update your firmware after you get the phone booted up and your rom placed back on the sdcard

fLaWx said:
Well im not sure of any other methods to try but i had loads of problems myself pushing files to the SDcard threw twrp and cwm recoveries, so the way I went about it was doing a decrypted RUU to return the phone to stock then once it loaded up in Android I pushed the Rom to the SDcard card then rebooted and started over.
Goto this thread http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
All the way at the bottom you should see some links for RUU's, I used the one labeled "1.10.605.15 Decrypted RUU" You will flash this the same way as you would a firmware update, if you dont know how thats done that post will explain it all. After you flash the RUU reboot and it should be back to the day you got it, but you will still be s-off, at that point just put a custom recovery back on and flash away, however that RUU will downgrade your firmware so you might wanna update your firmware after you get the phone booted up and your rom placed back on the sdcard
Click to expand...
Click to collapse
What he said. Good post dude.
When you enabled adb sideload, what command did you use? Because you don't push files that way. You type "adb sideload Rom.zip", then it will send the file and after it sends immediately start the install. So you will need to wipe in recovery first to make sure it's clean.
Sent from my Lunar Ecliptic One.

i followed your steps i got to the part where fastboot asks to flush the zip again i typed "fastboot flash zip firmware.zip" and it said waiting for device and that never went away so i rebooted into bootloader and now fastboot wont recognize the device however if i go to device manager it says my htc is plugged but has a little yellow icon...the drivers are up to date this is driving me nuts i just want my phone to work

Ruu
sound like you may need to ruu back to total stock there are instruction on doing it here and I do not want to give you the wrong steps. found this but make sure you have the decrypted ruu
1. Download VZW RUU.zip from the following thread 1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/show....php?t=2428276)
2. Rename to "ruu.zip"
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.
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
I also use cut and paste when doing this as it stops my crappy spelling from getting in the way

The problem now is that fastboot wont recognize the device, when i type "fastboot devices" its blank
i think i screwed up the firmware becouse in fastboot it says in red os-3.11.605.1 (1.10.605.15) in red
before i remember it was green that spot...oh crap i wont be able o buy a new phone in a long time this is terrible....i still have teamwin recovery can i do anything through that?

quadracorn said:
The problem now is that fastboot wont recognize the device, when i type "fastboot devices" its blank
i think i screwed up the firmware becouse in fastboot it says in red os-3.11.605.1 (1.10.605.15) in red
before i remember it was green that spot...oh crap i wont be able o buy a new phone in a long time this is terrible....i still have teamwin recovery can i do anything through that?
Click to expand...
Click to collapse
You could always use a USB-OTG, place a rom on a flash drive and try to install that way. There may be a simpler way, but that's all i can think of for now.

i guess i have to order an otg cable....oh well...ill have to live without a phone a bit longer until cable shows up haha XD w

quadracorn said:
The problem now is that fastboot wont recognize the device, when i type "fastboot devices" its blank
i think i screwed up the firmware becouse in fastboot it says in red os-3.11.605.1 (1.10.605.15) in red
before i remember it was green that spot...oh crap i wont be able o buy a new phone in a long time this is terrible....i still have teamwin recovery can i do anything through that?
Click to expand...
Click to collapse
Does pc see device in computer?if so down load room onto pc place Rom on root of ad card or in download and reboot phone into recovery ahs flash zip..I also had problem where adb would not see devices cause I had miniadb and the full version of adb and it was a conflict,just my two cents

I don't know if this will help, but I had an issue of my devices not being found so I followed this guy's guide: http://zacktutorials.blogspot.com/2013/04/adb-is-not-recognized-as-internal-or.html
and was able to get my device recognized. Also which recovery are you using? I don't know if it's still an issue but when I was on viper I got stuck in a bootloop with TWRP so I switched to Philz.
If you're able to get into fastboot, follow post #4 http://forum.xda-developers.com/showthread.php?t=2677015 and basically start from the beginning.
Make sure you have the latest recovery, the latest firmware (radios and such), and the correct ROM..
good luck

bregga said:
sound like you may need to ruu back to total stock there are instruction on doing it here and I do not want to give you the wrong steps. found this but make sure you have the decrypted ruu
1. Download VZW RUU.zip from the following thread 1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/show....php?t=2428276)
2. Rename to "ruu.zip"
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.
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
I also use cut and paste when doing this as it stops my crappy spelling from getting in the way
Click to expand...
Click to collapse
Hi All,
Do you know is RUU 4.4 has surfaced? please help

Trying to fix an M8

So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.​
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!

TMartin said:
So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.​
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!
Click to expand...
Click to collapse
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.

xunholyx said:
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.
Click to expand...
Click to collapse
I can get into TWRP but it won't mount the data partition. Are you saying I should try flashing another ROM the normal way through TWRP or try the sideload option? I tried to fastboot flash stock recovery. It says it worked but then continues to boot to TWRP.
I can get into bootloader. I'm pretty sure it's a 4.16.401.x ROM but I'll have to double check when I get home. I've tried to flash stock everything but it you know how it restarts through the process? When it restarts, it seems to want to restart to OS.
I'm about 99% sure the OS is there because it boots into Android but only gets me to the "Decrypt storage" screen.