Develop Bugs

[Q] Rooting gone wrong/ I've made a big mistake

Hi everyone, I'm hoping someone can help me out here because I've screwed up somehow and would like to un-do whatever it is I've done. I'm trying to think straight so I hope what I type out ends up making sense .
1. Right now, my phone works. I'm stuck on a rooted pre-OTA stock rom. I unrooted once, but was not able to flash the OTA update via the stock recovery. I still have a use-able phone so I'm doing better than some people in threads I've read about.
2. I tried to root it with gfree. I don't think it worked, and some errors came up during the process. I used the first method then skipped to 0.2 per the wiki. Using g-free verify tells me everything is alright. supercid, sim lock, etc.
3. I am s-off, but earlier I couldn't get gfree verify to work (my own error I'm certain) and assumed I screwed up. Rom manager and root explorer never gave me prompts for superuser permissions, but I was s-off. I didn't think I rooted correctly and used the rage against the cage method.
4. Right now, I'm apparently s-off and rooted. I can't flash any roms though. I use rom manager to flash the latest recovery, it says it works and then when I reboot to recovery it stays stuck on the HTC splash screen. Battery pull takes me back to the pre-OTA rom. Recovery only recently stopped working though.
Ultimately, I need to get recovery back somehow, and then I'd return my phone back to an unrooted state with the stock 2.2 rom since I can't seem to handle rooting to well. Since I have no clockwork mod recovery, not really sure what to do to get this process rolling. If someone can help me get recovery back, and then help me flash roms again I'd definitely appreciate it. I have noone to blame but myself here.
If it ends up mattering, I do have adb installed and can use that if need be, and like I said my phone still boots up. I don't have a brick but something crazy is going on.

tjmarchand said:
Hi everyone, I'm hoping someone can help me out here because I've screwed up somehow and would like to un-do whatever it is I've done. I'm trying to think straight so I hope what I type out ends up making sense .
1. Right now, my phone works. I'm stuck on a rooted pre-OTA stock rom. I unrooted once, but was not able to flash the OTA update via the stock recovery. I still have a use-able phone so I'm doing better than some people in threads I've read about.
2. I tried to root it with gfree. I don't think it worked, and some errors came up during the process. I used the first method then skipped to 0.2 per the wiki. Using g-free verify tells me everything is alright. supercid, sim lock, etc.
3. I am s-off, but earlier I couldn't get gfree verify to work (my own error I'm certain) and assumed I screwed up. Rom manager and root explorer never gave me prompts for superuser permissions, but I was s-off. I didn't think I rooted correctly and used the rage against the cage method.
4. Right now, I'm apparently s-off and rooted. I can't flash any roms though. I use rom manager to flash the latest recovery, it says it works and then when I reboot to recovery it stays stuck on the HTC splash screen. Battery pull takes me back to the pre-OTA rom. Recovery only recently stopped working though.
Ultimately, I need to get recovery back somehow, and then I'd return my phone back to an unrooted state with the stock 2.2 rom since I can't seem to handle rooting to well. Since I have no clockwork mod recovery, not really sure what to do to get this process rolling. If someone can help me get recovery back, and then help me flash roms again I'd definitely appreciate it. I have noone to blame but myself here.
If it ends up mattering, I do have adb installed and can use that if need be, and like I said my phone still boots up. I don't have a brick but something crazy is going on.
Click to expand...
Click to collapse
Download ClockworkMod Recovery straight from Koushik's page and put it on the root of your SD card. Open up Terminal Emulator on your phone and type in the following:
su
flash_image recovery recovery-clockwork-3.0.2.4-vision.img
reboot recovery
Click to expand...
Click to collapse
Post the results in here.

blackknightavalon said:
Download ClockworkMod Recovery straight from Koushik's page and put it on the root of your SD card. Open up Terminal Emulator on your phone and type in the following:
Post the results in here.
Click to expand...
Click to collapse
Hey thank you so much for a response! I tried this with two sd cards because I didn't have any luck. I tried that exact command and flash_image recovery /sdcard/recovery-clockwork-3.0.2.4-vision.img and each time it returns flash_image: not found
It definately is on my sd card.

tjmarchand said:
Hey thank you so much for a response! I tried this with two sd cards because I didn't have any luck. I tried that exact command and flash_image recovery /sdcard/recovery-clockwork-3.0.2.4-vision.img and each time it returns flash_image: not found
It definately is on my sd card.
Click to expand...
Click to collapse
Do you have the engineering bootloader? If not, you may have to try it with ADB.

blackknightavalon said:
Do you have the engineering bootloader? If not, you may have to try it with ADB.
Click to expand...
Click to collapse
Im fairly certain I had to flash it to root with the rage method, vol + pwr screen says "vision pvt eng s-off hboot 0.76.2000 (pc1010000)"
With adb it gives me the same error, but I used rom manager to flash 2.5.1.3 so I have a recovery again. I have one good nandroid of the rom im stuck on.
My next issue is that I tried to flash the stock rom with root from http://forum.xda-developers.com/showthread.php?t=836042 and something isn't right. I wipe data/cache and then go to install zip from sdcard (manual recovery) and select the rom. What happens after is it tells me the normal messages it gives when flashing and "welcome to vision" but when the flash is done instead of giving me the option of "reboot system now" it goes back to the install zip for sd card menu like the flash never happened (and it will not boot past the htc screen)

tjmarchand said:
Im fairly certain I had to flash it to root with the rage method, vol + pwr screen says "vision pvt eng s-off hboot 0.76.2000 (pc1010000)"
With adb it gives me the same error, but I used rom manager to flash 2.5.1.3 so I have a recovery again. I have one good nandroid of the rom im stuck on.
My next issue is that I tried to flash the stock rom with root from http://forum.xda-developers.com/showthread.php?t=836042 and something isn't right. I wipe data/cache and then go to install zip from sdcard (manual recovery) and select the rom. What happens after is it tells me the normal messages it gives when flashing and "welcome to vision" but when the flash is done instead of giving me the option of "reboot system now" it goes back to the install zip for sd card menu like the flash never happened (and it will not boot past the htc screen)
Click to expand...
Click to collapse
Maybe it's a bad recovery. You said you flashed 2.5.1.3, so ROM Manager should work. Try flashing 3.0.2.4 through there now. If not, I suggest downloading Fastboot.

tjmarchand said:
Hey thank you so much for a response! I tried this with two sd cards because I didn't have any luck. I tried that exact command and flash_image recovery /sdcard/recovery-clockwork-3.0.2.4-vision.img and each time it returns flash_image: not found
It definately is on my sd card.
Click to expand...
Click to collapse
flash_image isn't part of the stock ROM, I made a guide for using it: http://forum.xda-developers.com/showthread.php?t=902493

raitchison said:
flash_image isn't part of the stock ROM, I made a guide for using it: http://forum.xda-developers.com/showthread.php?t=902493
Click to expand...
Click to collapse
Thanks for the guide! I followed it with no issue, I rebooted into recovery; it first hung on the HTC screen, rebooted, vibrated and then booted back into the OS. So anyway, instead of 2.5.1.3, I'm on 3.0.0.5 now.
I went down to 2.5.1.3 and downloaded cm6.1 via rom manager. It told me this : E: can't open '/sdcard/..location (bad) installation aborted. tmp/recovery.log was copied to sdcard
I tried enom's froyo themed rom next, heres what recovery tells me:
Installing update...
Formatting cache
Copying files
Formatting SYSTEM
Copying files...
E Can't symlink /system/bin/su
E Failure at line 19:
symlink /system/xbin/su SYSTEM: bin/su
Installation aborted.
I also tried to download an updated superuser from the market, it says installation unsuccessful package file was not signed correctly.

Use Titanium to update your Superuser.apk
Sent from a Western Union telegram.

blackknightavalon said:
Use Titanium to update your Superuser.apk
Sent from a Western Union telegram.
Click to expand...
Click to collapse
That worked, so thank you. I ended up unrooting and putting s back on so I can retry. Now, I can't flash the OTA update via stock recovery. Any ideas for that one? Thank you so much for all the other help as well.
"E:Can't open /cache/recovery/command" -when I first enter recovery
--Install from sdcard...
Finding update pacakge...
Opening update pacakge...
Verifying update package...
E:failed to verify whole file signature
E: signature verification failed
Installation aborted. -after trying the OTA (named update.zip of course)

tjmarchand said:
That worked, so thank you. I ended up unrooting and putting s back on so I can retry. Now, I can't flash the OTA update via stock recovery. Any ideas for that one? Thank you so much for all the other help as well.
"E:Can't open /cache/recovery/command" -when I first enter recovery
--Install from sdcard...
Finding update pacakge...
Opening update pacakge...
Verifying update package...
E:failed to verify whole file signature
E: signature verification failed
Installation aborted. -after trying the OTA (named update.zip of course)
Click to expand...
Click to collapse
If this is the Gingerbread OTA, you'll need everything as stock. If it's the "OTA" with Superuser thrown in, you'll need CWM Recovery 3+ (2.5* formats the system in yaffs, 3+ formats it in EXT).

This is just the ota update with wifi calling still 2.2, Im unrooted and stock recovery again
Sent from my T-Mobile G2 using XDA Premium App

Help Please. No rom. System is formatted. S-ON. PB31IMG won't install.

Hey guys. So my friend wanted me to install a Jelly Bean rom on his HTC Incredible. I unlocked the bootloader, installed CWM and accidentally formatted the system once I got CWM installed. So now the phone has no ROM and S-ON. I tried installing stock 2.3.4 again from HBOOT by using PB31IMG.zip but that didn't work (SD Card is formatted in FAT32).
Is there any way to get this phone up and running again?
Info in bootloader is as follows:
INCREDIBLEX XD SHIP S-OM
HBOOT-1.07.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16AB
RADIO-2.15.10.12.20

rockethot said:
Hey guys. So my friend wanted me to install a Jelly Bean rom on his HTC Incredible. I unlocked the bootloader, installed CWM and accidentally formatted the system once I got CWM installed. So now the phone has no ROM and S-ON. I tried installing stock 2.3.4 again from HBOOT by using PB31IMG.zip but that didn't work (SD Card is formatted in FAT32).
Is there any way to get this phone up and running again?
Info in bootloader is as follows:
INCREDIBLEX XD SHIP S-OM
HBOOT-1.07.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16AB
RADIO-2.15.10.12.20
Click to expand...
Click to collapse
If your unlocked and have cwm installed, all you need to do is wipe everything in the mounts and storrage menu in recovery except emmc and sdcard. Then just flash the rom of your choosing.
If you really feel or find the need to go back stock download this ruu http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip, place it on the sdcard in no folders and boot to hboot. Hboot should find the file after a few secs, and prompt you to press vol up to update.
If you want s-off you will need to fastboot flash a misc img, downgrade to froyo, and then flash the unrevoked forever patch.

cmlusco said:
If your unlocked and have cwm installed, all you need to do is wipe everything in the mounts and storrage menu in recovery except emmc and sdcard. Then just flash the rom of your choosing.
If you really feel or find the need to go back stock download this ruu http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip, place it on the sdcard in no folders and boot to hboot. Hboot should find the file after a few secs, and prompt you to press vol up to update.
Click to expand...
Click to collapse
Ignore the PM I just sent you haha
When I try to install a rom through cwm I get the following error:
Creating symlinks
symlink: some symlinks failed
E:Error in /sdcard/(Name of rom)
(Status 7)
Installation Aborted

rockethot said:
Ignore the PM I just sent you haha
When I try to install a rom through cwm I get the following error:
Creating symlinks
symlink: some symlinks failed
E:Error in /sdcard/(Name of rom)
(Status 7)
Installation Aborted
Click to expand...
Click to collapse
Try redownloading the rom. I belive status7 is either a corrupt zip, or the updater script of the rom is messed up.

cmlusco said:
Try redownloading the rom. I belive status7 is either a corrupt zip, or the updater script of the rom is messed up.
Click to expand...
Click to collapse
Just flashed CM7 and Gapps for it with no errors. Rebooted from CWM and it won't go past the white HTC Incredible screen. Any ideas?

rockethot said:
Just flashed CM7 and Gapps for it with no errors. Rebooted from CWM and it won't go past the white HTC Incredible screen. Any ideas?
Click to expand...
Click to collapse
Did you wipe everything in the mounts and storrage menu except emmc and sdcard before flashing? If so it may take several minutes to get thru the splash screen and on to the bootanimation.

cmlusco said:
Did you wipe everything in the mounts and storrage menu except emmc and sdcard before flashing?
Click to expand...
Click to collapse
Yeah, just wiped everything again and reflashed and I'm still stuck at the white HTC Incredible Screen.

rockethot said:
Yeah, just wiped everything again and reflashed and I'm still stuck at the white HTC Incredible Screen.
Click to expand...
Click to collapse
Not sure if you saw i added to my post about it possibly taking several minutes to get past the splash and on to the bootanimation. If it takes more than 5 min its not gonna work. If thats not the issue i would wipe everything again, do the ruu i posted and then unlock by fastboot flashing the unlock_token.bin file, fastboot flash cwm and then wipe and flash the rom again.

cmlusco said:
Not sure if you saw i added to my post about it possibly taking several minutes to get past the splash and on to the bootanimation. If it takes more than 5 min its not gonna work. If thats not the issue i would wipe everything again, do the ruu i posted and then unlock by fastboot flashing the unlock_token.bin file, fastboot flash cwm and then wipe and flash the rom again.
Click to expand...
Click to collapse
Tried it again, it's been 7 minutes and still nothing. I also tried flashing Bugless Beast, it would boot to the same HTC Incredible screen, then reboot into recovery around 15 seconds later. I guess I'll give the ruu a try.

So I tried flashing a non AOSP rom and figured I'd give yours a try. It works!

rockethot said:
So I tried flashing a non AOSP rom and figured I'd give yours a try. It works!
Click to expand...
Click to collapse
Strange. You could try flashing aosp again and see if it works now. Either way at least you know the phones not screwed.

[HOWTO] ONE V how to revert back to Stock ROM

I have recent version of One V gotten from Virgin Mobile during the cyber Monday sale. I really wanted to try jellybean so I tried AOKP cdma (http://forum.xda-developers.com/showthread.php?t=1878994)
I used All-In-One Tool Kit by hasoon2000 (http://forum.xda-developers.com/showthread.php?t=1676686) first to unlock and flash recovery. It has a video on how to use it too. vey nice.
Then I flash the AOKP 11/19 nightly rom but something was not right, it was booting OK but every 20~30 seconds, the phone rebooted itself. They say recent One V with the OTA update experiences this symtoms.
------------------------------------------------------------------------
The solution is to go back to stock rom.
Pre requirements which are already available if you downloaded All-In-One Tool
1. HTC drivers are installed
2. Android SDK installed
The way to go back to stock rom is to use RUU (http://forum.xda-developers.com/showthread.php?t=1591059)
For the virgin mobile USA CDMA, you can download
"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"
Make sure you download the correct RUU. Otherwise , you will break your phone !
Execute the RUU executable and go to temp folder by typing %temp% in your explorer window. It will create two temporay folders with long names. Once the wizard screen appears, one of the folders contains another long named folder that contains 'rom.zip' file. Copy the 'rom.zip' file into the directory where 'fastboot.exe' is located. You can close the RUU wizard screen now.
This is the full temp path for me.
C:\Users\%windows7_userid%\AppData\Local\Temp\{8AB121A4-D261-43DF-A709-93BCAAEE61DB}\{50F2F878-636A-496F-A7CB-544C067E0C4B}
Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
Now execute below commands from the CMD window from the directory where the fastboot.exe is located.
Code:
fastboot oem lock
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Then reboot normally to see your Stock rom !
After that, I reflashed the AOKP 11/19 nightly rom, and now it is working like a charm! I love it!.
See my phone with jellybean! Note that AOKP 11/19 is pretty stable, video recording is working good , but with minor graphic glitches time to time. The glitches occurs and disappears right away, so it's not a big deal.

I followed your instructions and was able to revert to the stock rom. The problem now is that ClockWorkMod recovery no longer work and I can't reflashed the AOKP rom. When I try, the phone displays a processing icon and then a red triangle with an exclamation mark. That's when I have to hold down the power bottun to shutdown manually. I can still boot into bootloader though.
I tried going through the steps to install recovery.img again but somewhere/somehow as the cmd are executed I see a line that says failed.
Do you have any idea what's causing the problem?

td8 said:
I followed your instructions and was able to revert to the stock rom. The problem now is that ClockWorkMod recovery no longer work and I can't reflashed the AOKP rom. When I try, the phone displays a processing icon and then a red triangle with an exclamation mark. That's when I have to hold down the power bottun to shutdown manually. I can still boot into bootloader though.
I tried going through the steps to install recovery.img again but somewhere/somehow as the cmd are executed I see a line that says failed.
Do you have any idea what's causing the problem?
Click to expand...
Click to collapse
Hello, Basically processing icon with red triangle shows when you go into recovery mode with the stock rom.
what happens is that we have to lock the phone to install the stock rom to work properly ( This commands locked the phone --> fastboot oem lock )
So you have to perform the unlock and flash the recovery again after reverting to the stock rom . Try the ALL IN ONE Tool kit.

Basically when flashing your recovery to clockworkmod and then installing aokp (for the one v) download a seperate boot.img which is in the topic because the one included in the AOKP zip caused mine to lock up as well. Once you flash boot.img with one of the newest (CM10 bla blabla) it was ok for me.

nurungji said:
So you have to perform the unlock and flash the recovery again after reverting to the stock rom . Try the ALL IN ONE Tool kit.
Click to expand...
Click to collapse
I tried the fastboot oem unlock command and also reflash the recovery using the All In One Tool Kit but was unsuccessful. What am I doing wrong?
I have included attachments of the cmd screen to give you more context to what is happening.

Thanks Tomskii for the advice and will keep it in mind when choosing rom but my current problem is that I am unable to access the CWM recovery to flash any rom.
What happen was I flashed to the CM10 rom but it kept rebooting after few seconds.
Multiple xda post says to revert to an earlier stock rom to fix the RADIO version.
I am now in the current position:
stock rom with RADIO 1.00.00.0521_2(Which I believe is correct)
No access to CWM recovery from Hboot screen
fastboot oem unlock cmd is not executing
All In One not able to flash recovery or boot in recovery
---------- Post added at 10:02 PM ---------- Previous post was at 09:17 PM ----------
Tomskii said:
Basically when flashing your recovery to clockworkmod and then installing aokp (for the one v) download a seperate boot.img which is in the topic because the one included in the AOKP zip caused mine to lock up as well. Once you flash boot.img with one of the newest (CM10 bla blabla) it was ok for me.
Click to expand...
Click to collapse
What do you mean by "which is in the topic"? Could you provide a link?

td8 said:
I tried the fastboot oem unlock command and also reflash the recovery using the All In One Tool Kit but was unsuccessful. What am I doing wrong?
I have included attachments of the cmd screen to give you more context to what is happening.
Click to expand...
Click to collapse
It looks like the phone is not unlocked.
Enable the USB debugging under the developer option setting then perform the tasks by running "One V 1.2.exe"
then follow step 1 through 5 to unlock your stock rom phone.
then your flash recovery command would not fail.
> fastboot flash recovery Recoveries/CVM.img

td8 said:
Thanks Tomskii for the advice and will keep it in mind when choosing rom but my current problem is that I am unable to access the CWM recovery to flash any rom.
What happen was I flashed to the CM10 rom but it kept rebooting after few seconds.
Multiple xda post says to revert to an earlier stock rom to fix the RADIO version.
I am now in the current position:
stock rom with RADIO 1.00.00.0521_2(Which I believe is correct)
No access to CWM recovery from Hboot screen
fastboot oem unlock cmd is not executing
All In One not able to flash recovery or boot in recovery
---------- Post added at 10:02 PM ---------- Previous post was at 09:17 PM ----------
What do you mean by "which is in the topic"? Could you provide a link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1882990
See: latest boot.img but I just read that isn't the problem. Have you tried reflashing your recovery.img with a newer CWM?

nurungji said:
It looks like the phone is not unlocked.
Enable the USB debugging under the developer option setting then perform the tasks by running "One V 1.2.exe"
then follow step 1 through 5 to unlock your stock rom phone.
then your flash recovery command would not fail.
> fastboot flash recovery Recoveries/CVM.img
Click to expand...
Click to collapse
Ok decided to use TWRP b/c the All-In-One has it for CDMA and now able to access recovery. Yay. Thanks nurungji.
Next I tried to reflash CM10 version 20121108, along with Gapps and the steps I did before the stock rom like clear cache and boot.img from the zip.
But now when I reboot, the phone is stuck on the CyanogenMod load screen. I waited over 10 mins before I shutdown manually. Before the earlier stock rom, I was able to go to the "register google account" screen before the phone rebooted.
I tried to redo the whole process again like some said on other threads but keep getting the same result. I also tried the AOKP 12/05 but got a black screen.
Any advice would be appreciated.
**Update**
Took about the whole day but finally everything is working properly. The boot.img from the Tomskii didn't work. Maybe b/c it was from a PrimoU Aokp page and my phone is PrimoC.
It is currently using supersick kernel from simonsimons34. It solves the wifi problem for the CM10 version 12/20.

td8 said:
Ok decided to use TWRP b/c the All-In-One has it for CDMA and now able to access recovery. Yay. Thanks nurungji.
Next I tried to reflash CM10 version 20121108, along with Gapps and the steps I did before the stock rom like clear cache and boot.img from the zip.
But now when I reboot, the phone is stuck on the CyanogenMod load screen. I waited over 10 mins before I shutdown manually. Before the earlier stock rom, I was able to go to the "register google account" screen before the phone rebooted.
I tried to redo the whole process again like some said on other threads but keep getting the same result. I also tried the AOKP 12/05 but got a black screen.
Any advice would be appreciated.
Click to expand...
Click to collapse
Hey congratulation, you are almost there. I am not sure about CM10 mod because I didn't try CM10 because the video recording didn't work at the time I was looking to try Jellybean. So I decided to use AOKP but anything after 11/19 nightly version shows just black screen ( I tried every night version)
I am currently using 11/19 version now.

[Q] Bricked HTC One need help please

So tonight around 6pm EST I noticed that there was a Cyanogen mod nightly for my wife's Verizon htc one. I also noticed that there was an update function so I decided to give it a try. However, I didn't realize I had yet to make a backup of her current ROM. I thought I had done this when I originally rooted the phone... HUGE MISTAKE NUMBER 1. Once the update was flashed it gave me an error and began boot looping. I tried to find the original version of Cyanogen but could not locate it on the device. Since the HTC One doesn't have an SD card and I Don't have the special OTG USB I couldn't get the storage to mount to add a new ROM. After 2 hours of searching I was finally able to Push a ROM to her device but I kept getting an E: Error executing updater binary... <--- this error I researched only to find that I couldn't flash the rom I was trying to lash in the latest TWRP recovery.
ALL I want to do now is to flash a new recovery to the phone so I can install a ROM and get this paperweight working again.
Can someone please explain to me STEP by STEP what to do here?

volumebmx15 said:
So tonight around 6pm EST I noticed that there was a Cyanogen mod nightly for my wife's Verizon htc one. I also noticed that there was an update function so I decided to give it a try. However, I didn't realize I had yet to make a backup of her current ROM. I thought I had done this when I originally rooted the phone... HUGE MISTAKE NUMBER 1. Once the update was flashed it gave me an error and began boot looping. I tried to find the original version of Cyanogen but could not locate it on the device. Since the HTC One doesn't have an SD card and I Don't have the special OTG USB I couldn't get the storage to mount to add a new ROM. After 2 hours of searching I was finally able to Push a ROM to her device but I kept getting an E: Error executing updater binary... <--- this error I researched only to find that I couldn't flash the rom I was trying to lash in the latest TWRP recovery.
ALL I want to do now is to flash a new recovery to the phone so I can install a ROM and get this paperweight working again.
Can someone please explain to me STEP by STEP what to do here?
Click to expand...
Click to collapse
It depends on what you are trying to do. You said you wanted to flash a new recovery, so go ahead and do it.
http://forum.xda-developers.com/showthread.php?t=2416431
If you want to revert back to stock, go ahead and do that too.
http://forum.xda-developers.com/showthread.php?t=2475216
But I say your best bet is to just push a ROM in recovery. Are you S-Off?
Also, what commands are you doing to push a ROM? Is the E: drive where your SDK toolkit located?

Karn101,
What ROM and RECOVERY would you suggest I flash?
I had the TWRP 2.6.3.4 touch recovery installed but for some reason it would not allow me to install the following 2 ROMS
1. Google Edition HTC One VZW [KITKAT]
2. Inverted-EclipticONE-KitKat-v1.2
When I did this I kept getting the E: Error executing updater binary which really had me as a loss.
To answer your question I am S-OFF it says UNLOCKED M7_WLV PVT SHIP S-OFF RH @ the bootloader screen.
HBOOT Version is 1.54.000
Also when I was pushing a ROM I was using some commands I found in a guide here: http://forum.xda-developers.com/showthread.php?t=2354259
I followed some of the steps on here with no luck...
Also I attempted to flash several recoveries from Fast boot with the Fastboot flash recovery recovery.img in the command promt. It shows that the files was sent but the phone just get stuck at the bootloader saying loading recovery at the top in blue font.
Can you walk me through each step on this? I need to get a recovery on there first them push a ROM to the device and install it via the recovery.... I am assuming that would be the easiest method.

If your s-off can't you flash the Ruu in fastboot? Maybe that will help
sent from my JAVA CARD S-OFF FAUX HBOOT BLUE HTC ONE using xda premium app.

Tigerstown said:
If your s-off can't you flash the Ruu in fastboot? Maybe that will help
sent from my JAVA CARD S-OFF FAUX HBOOT BLUE HTC ONE using xda premium app.
Click to expand...
Click to collapse
I suggest this as well.
also
"brick" means phone is dead. you're phone turns on..
not a brick.

what i did once when i couldnt flash RUU was it should work S-On and well Its got to work on S-Off
1-Download TWRP recovery also the System.img and boot.img
2-Rename TWRPRecovery6.3xx.img to Recovery.img
3-Flash recovery in fastboot fastboot flash recovery Recovery.img
4-boot into recovery via fastboot fastboot boot recovery.img
This will boot your device into the custom recovery
5-press Backup
6-swipe to confirm
7-after it's done making a backup
8-navigate back to the home screen
9-press Advanced
10-press Mount
11-check the box next to USB-OTG
This will allow to mount your sdcard into the computer and you can copy the system.img from the RUU
12-open folder TWRP open folder BACKUPS ETC ETC until you get to the folder with the backup you just made
13-delete the system.ext4.win delete the system.ext4.win.md5
14-copy the system.img here abd rename it to
15-system.ext4.win
16-then unmount
17-then navigate back to the home page in the recovery and
18-press Restore
19-then choose that backup and swipe to confirm
20-also recommend fastbooting the boot.img
this is what i did when i couldnt get any rom to flash any roms via recovery nor a i could do a RUU saved my phone.

[Q] ViperOne 5.8 Bootloop HTC One M7

*FIXED*
The problem turned out to be the wrong TWRP version for verizon phones, the correct version is here http://crackflasher.com/openrecovery-twrp-2-7-0-1-m7wlv-img-htc-one-verizon-openrecovery/
Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I flash the rom via TWRP everything seems to work fine and the install claims it is successful however this is clearly not the case as when i try to boot the phone it bootloops getting only as far as the HTC screen (with the red development only text underneath)
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Steps Taken:
I have tried both pushing the Rom.zip and copying the rom.zip to the sdcard on the phone, this has made no difference
I do the factory reset (wipe) before installing
I do the factory reset (wipe) after installing
I have unchecked all the options and made the most basic install I can
I have tried to flash the TWRP version that came on the ROM, this also causes recovery bootloop
I have tried downloading the rom directly to the phone
I have made sure the MD5 codes match
I have tried flashing the boot.img separately via fastboot
My most recent attempts Aroma Log is attached
Any help would be greatly appreciated!!!!!

PblicEnemy said:
Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I flash the rom via TWRP everything seems to work fine and the install claims it is successful however this is clearly not the case as when i try to boot the phone it bootloops getting only as far as the HTC screen (with the red development only text underneath)
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Steps Taken:
I have tried both pushing the Rom.zip and copying the rom.zip to the sdcard on the phone, this has made no difference
I do the factory reset (wipe) before installing
I do the factory reset (wipe) after installing
I have unchecked all the options and made the most basic install I can
I have tried to flash the TWRP version that came on the ROM, this also causes recovery bootloop
I have tried downloading the rom directly to the phone
I have made sure the MD5 codes match
I have tried flashing the boot.img separately via fastboot
My most recent attempts Aroma Log is attached
Any help would be greatly appreciated!!!!!
Click to expand...
Click to collapse
I noticed you said you do the factory reset after you flash Viper? You'll only want to wipe before you flash the rom. I'm guessing that's you're issue if I understood correctly.
Sent from my HTC6500LVW using Tapatalk

brholt6 said:
I noticed you said you do the factory reset after you flash Viper? You'll only want to wipe before you flash the rom. I'm guessing that's you're issue if I understood correctly.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I see now I might not have been as clear as I meant to be. When I said that i wiped before and after I meant that I performed both wipes seprately from each other and a third time together. I only tried the wipe after flash because it was a suggestion from another developer website. It would seem that this is not the solution, as the bootloop happens regardles of wipe before, wipe after, or wipe before and after or even no wipe at all. Thanks for the reply!

Try this. Download this recovery http://www.androidfilehost.com/?fid=23329332407584851.
Use fastboot to flash the recovery.
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot flash recovery nameofrecovery.img
Code:
fastboot reboot-bootloader
Go to recovery.
In recovery go to wipe - advanced - check boot, system, data, and cache. Proceed with the wipe.
Flash your rom
Boot up.

cmlusco said:
Try this
Use fastboot to flash the recovery.
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot flash recovery nameofrecovery.img
Code:
fastboot reboot-bootloader
Go to recovery.
In recovery go to wipe - advanced - check boot, system, data, and cache. Proceed with the wipe.
Flash your rom
Boot up.
Click to expand...
Click to collapse
Everything went very well except 2 things. 1: when issuing the "fastboot erase recovery" command in fastboot it failed and came back as "not allowed". 2: the rom installation failed and came back as , error: 7. I tried to boot to system regardless of the error message but the boot loop continues
The new error log is attached again. Thanks for the reply! (and the TWRP update!)

Seems to be an issue with the rom. The log shows everything going fine until the very last step where it tries to change the permissions of an apk and fails, therfore aborting the whole install.
Code:
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
I would post that in the roms thread.

cmlusco said:
Seems to be an issue with the rom. The log shows everything going fine until the very last step where it tries to change the permissions of an apk and fails, therfore aborting the whole install.
Code:
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
I would post that in the roms thread.
Click to expand...
Click to collapse
I would love to but unfortunately I am not allowed to post there until I have 10 posts and have been cleared by a mod. Do you think it could have anything to do with the temproot i installed (weaksauce) because it works by installing a root every time the phone boots up, or would that be deleted when the wipe is performed?

When you wiped before the rom install it should wipe out everything including weaksauce. The reason it wont boot is because you have no or an incomplete rom. I would just flash another rom in the mean time till you can figure out whats up with viper. Or you could do an ruu if you wanted to be stock.

cmlusco said:
When you wiped before the rom install it should wipe out everything including weaksauce. The reason it wont boot is because you have no or an incomplete rom. I would just flash another rom in the mean time till you can figure out whats up with viper. Or you could do an ruu if you wanted to be stock.
Click to expand...
Click to collapse
I really want viper because of the customization, do you know of any other sources that I could acquire viper from? or would it be possible to install an older version and update it?
*UPDATE* I tried to install Android Revolution HD just now to see if it would work and I end up with the exact same error, seems like a phone problem to me. is there anyway to put my phone completely back to the way i got it out of the box and start over?

Yes you can do an ruu to get back to stock. But you need fastboot to do it. You probably dont have the correct drivers installed on your pc. What version of windows you runing?

cmlusco said:
Yes you can do an ruu to get back to stock. But you need fastboot to do it. You probably dont have the correct drivers installed on your pc. What version of windows you runing?
Click to expand...
Click to collapse
Windows 7 64bit. I use fastboot all the time with this phone so I should be able to use it.

Nevermind, i was thinking this was a different thread. Anyways you will need to change your cid back to vzw__001. Then download the ruu from the second post of santods stock rom thread in development section.
fastboot oem rebootRUU
fastboot flash zip ruufilename.zip
(may fail with flush error, do command again)
fastboot reboot

PblicEnemy said:
I really want viper because of the customization, do you know of any other sources that I could acquire viper from? or would it be possible to install an older version and update it?
*UPDATE* I tried to install Android Revolution HD just now to see if it would work and I end up with the exact same error, seems like a phone problem to me. is there anyway to put my phone completely back to the way i got it out of the box and start over?
Click to expand...
Click to collapse
The big problem with Android Revolution is that it isn't made for the Verizon HTC One. Make sure you you're only flashing roms from the Verizon HTC One thread or you've talked to the Dev. Flashing roms meant for other carriers can really screw you up.
Sent from my HTC6500LVW using Tapatalk

Thanks to both of you, good information and helpful, I'm still hoping I can figure out the set_metadata_recursive error, I have another thread going specifically for it!