Database Develop

[Q] Need help from the pros! Rogers HTC Dream rooting and modding!

Long time reader, first time poster (intimidated in the past)! Hi guys!
So here you go guys, another one who ventured into modding his phone. Seems like following the steps wasn't really going to seal it for me so I'll explain what I did and you tell me what I did wrong.
- Installed Eclipse and Android SDK and fastboot tool on my comp.
- Followed Charrion's guide to one-click rooting my device also using haykuro's root kit
*Followed his steps BUT I actually made a nandroid backup and saved it on my computer.
- Installed the latest cyanogen ROM (from their wiki) on the root of the sdcard and renamed it update.zip
After that, I followed haykuro's guide down to the first commands (after putting the radio and recovery.img on the sdcard from haykuro's give me root)
Used fastboot to input the following comands:
Code:
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
Then when I try to reboot into recovery mode, I get stuck on the Rogers screen. I can still access the fastboot and when the device is plugged in through usb it shows fastboot usb on the top left but I just can't access the recovery menu.
Can someone help me? Just getting used to this forum, sorry for not following any procedures. I did read the forum rules and searched the forums. If a thread already exist, I just didn't search well enough.
Thank you
UPDATE:
I use the command prompt to communicate with my Dream in fastboot usb mode and I get the following errors:
C:\Users\Steven>fastboot erase boot
erasing 'boot'... OKAY
C:\Users\Steven>fastboot erase recovery
erasing 'recovery'... OKAY
C:\Users\Steven>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
I may have a bricked phone! Keeping faith in the hopes that one of you comes and saves me!

New development!
My problem was of course a noob problem! Charrion's post on another thread helped making it clear. My .img were in the same folder as fastboot but I had to specify the entire path for it to work!
Anyways got into the recovery menu and now flashed the latest cyanogen rom to my device but now it's still stuck on the Rogers screen!
Any idea?
To help, here's the info on the fastboot screen:
Dream PVT 32B ENG S-Off
HBOOT-1.33.2005 (DREA21000)
CPLD-4
RADIO-2.22.19.261
There!
Thank you in advance!

with a soft-brick do you RUU or do a PH398DIAG.zip to recover

Its not clear to me if I need recovery my soft-bricked HTC Raider by doing a PH39DIAG.zip or running the right RUU???
With the RUU I get the following error:
"RUU, Security fail! Update fail!"
With the PH39DIAG.zip I don`t know where to get one.
Heeeeeeeeeeeeeeeeeeeeeelp!

If the RUU isn't working you probably need to flash the appropriate kernel. Were you using the all-in-one-toolkit? Try flashing back to the stock kernel, and run the RUU.

>>>If the RUU isn't working you probably need to flash the appropriate kernel.
I bought the phone soft-bricked to hboot. RUU is giving me the error I posted. I don`t know what ROM is on it so I don`t think I need to flash a kern.
Here are the things I have tried so far.
My HTC Raid (I am in Canada so don't know if this is a Bell or Rogers or who knows, I bought it white screened) is stuck in white screen with HTC logo. I took
the following steps:
Downloaded RUU_Holiday_Rogers_WWE_1.65.631.1_Radio_1.11.1020.03_30.77.551061.02L_release_219561_signed.exe
from
http://hotfile.com/dl/145619873/245....77.551061.02L_release_219561_signed.exe.html
--Ran RUU and the program noted I have image version 1.65.566.3 on my Radier
--Selected Update and tried to update to 1.65.631.1
--The Raider came up in the HTC/black backgroup and then gave the following ERROR[155] UNKNOWN ERROR.
--After exiting RUU and disconnecting the cable the phone shows along with the general hboot information on the phone "RUU, Security fail! Update fail!"
--Restarted phone with volumn down and power and it came up in hboot and showed the following error:
SD Checking
Loading...[PH39DIAG.zip]
No Image!
Loading...[PH39DIAG.nbh]
No image or wrong image!
Loading...[PH39IMG.zip]
No image!
Loading...[PH39IMG.nbh]
No image!
Loading...[PH39IMG.tar]
No image!
Loading...[PH39IMG.aes]
No image!
--I tried re-locking the bootload with "fastboot oem lock" and I get a "..." after the command and nothing else happens. Waited for 10 minutes.
--Also "adb devices" shows no devices.
--Installed HTCSync, started HTCSync, pluged in hbooted HTC Raider, Drivers Software Installation diolog box shows "My HTC" driver installed, still nothing when
I run "adb devices"
--Ran "fastboot oem lock" and get the following.
(bootloader) Lock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.026s
--When I run Hasoon2000s HTC Vivid AIO Kit v1.2 Relock Bootloader I get the following.
INFOLock successfully
FAILED (status read failed (Too many links))
finished. total time: 0.022s
--With Hasoon2000s HTC Vivid AIO Kit v2.0 I get.
INFOLock successfully
FAILED (status read failed (Unknown error))
finished. total time: 0.023s
--reboot into hboot and status still "*** UNLOCKED ***"

hmmm, I haven't messed with this sort of thing of the Vivid so much, but I have on the flyer, and I've gotten the soft brick white HTC screen too, and typically what it means is the Hboot version doesn't support the firmware on there. I got no link but perhaps the developers have the Hboot version your looking for with the firmware you got.
Can you get into fastboot? If you can its just a matter of flashing the Hboot with ADB and then running the RUU

yes I can get into fastboot.
The hboot version i have is the same as my other Raider that is on rogers. On the working Raider I have 1.65.631.1 software number, 2.3.4 android version, 3.0 Sense, 2.6.35.13-gc1166ee kernel version, 1.11.1020.03_03.77.551061.02L bb, 1.65.631.1 CL175411 release-keys build number.
So the hboot is the same on both of them, they are both unlocked, and the working one has HOLIDAY PUT SHIP S-ON RL
don`t know if that helps or not.

The Reason You Are Getting That Error is because your bootloader is still unlocked, go into hboot go into fastboot and plug in via usb and it should say "Fastboot USB" in red then run the ruu.... once completed do a battery pull, go back into hboot unlock bootloader again, then install a custom recovery (i recommend WildChild's) then if you plan on using a custom rom... use a kernel supported or use the rom's kernel in the zip "Boot.img" flash that kernel put the rom on your sd card or go into wildchilds recovery go to enable usb-ms and enable internel sd card and put the rom in there disable usb-ms go to wipe clear the two caches then go into the main menu flash zip menu internel or externel sd card select the rom and install and you are good to go ! anymore help pm me i can help greatly
---------- Post added at 03:36 AM ---------- Previous post was at 03:24 AM ----------
Hmm sounds like you do not have the right htc drivers installed download the all in one tool kit and run the first few steps ! Download your ph39img.zip here http://goo.im/private/iomonster/htcvivid/roms/ics-ota/PH39IMG.zip

>>>The Reason You Are Getting That Error is because your bootloader is still unlocked
no it is *** UNLOCKED ***
>>>go into hboot go into fastboot and plug in via usb and it should say "Fastboot USB" in red
Yes
>>>then run the ruu....
times out with an error, here is my RUU
RUU_Holiday_Rogers_WWE_1.65.631.1_Radio_1.11.1020.03_30.77.551061.02L_release_219561_signed.exe
>>>Download your ph39img.zip here
what do I do with it. I put it on the sdcard and did a bootload and it gives the following errors.
SD Checking
Loading...[PH39DIAG.zip]
No Image!
Loading...[PH39DIAG.nbh]
No image or wrong image!
Loading...[PH39IMG.zip]
No image!
Loading...[PH39IMG.nbh]
No image!
Loading...[PH39IMG.tar]
No image!
Loading...[PH39IMG.aes]
No image!

Flash a proper recovery, then flash an gingerbread Vivid custom ROM and immediately flash the appropriate boot.img to go with it.
If it boots, you know you're on GB. Relock the bootloader in fastboot and run either the Telus or Bell ruu for GB. Try both before coming back.

>>>Flash a proper recovery,
I have flashed a number of proper recovery images.
From Vivid all in one kit v2.1 http://forum.xda-developers.com/showthread.php?t=1498003 I have tried to flash
recovery-cwm-vivid-5.5.0.4B2.img
wcxrecovery.img
and recovery.img from a back up by cwm on my other working Raider
"fastboot devices" gets me "HT1ALVJ03540" and when I go to fastboot on the hboot menu I get "FASTBOOT USB" in red.
I have used "fastboot flash recovery filename.img"
After all these flashes when I boot into hboot and select RECOVERY and press the power key it show a white screen with a green htc and then with in 1 sec goes back into hboot.
Prehaps is is of interest than when I run the RUU RUU_Holiday_Rogers_WWE_1.65.631.1_Radio_1.11.1020.03_30.77.551061.02L_release_219561_signed.exe it tells me I have image version 1.65.666.3 installed and wants to put 1.65.631.1 -- you can see that from the image name and the getvar all output below
Also I have extracted the rom.zip following http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu/ from this RUU and renamed it PH39DIAG.zip and when it loads it hboot gives an "Wrong zipped image!" after "Checking..[PH39IMG.zip]"
Here is my fastboot getvar all info
INFOversion: 0.5
INFOversion-bootloader: 1.83.0014
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: 0360
INFOversion-main: 1.65.666.3
INFOserialno: HT1ALVJ03540
INFOimei: 358730040049371
INFOproduct: holiday
INFOplatform: HBOOT-8260
INFOmodelid: PH3915000
INFOcidnum: BM___001
INFObattery-status: good
INFObattery-voltage: 4075mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: ccb23700
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.514s
The image that is on this bricked Raider appears to be a bell ICS ROM.
OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip
http://forum.xda-developers.com/showthread.php?t=1672800
When I run RUU I get a "ERROR 155 UNKNOWN ERROR" in the RUU program and if I unplug the phone it shows RUU Security fail! Update fail!
>>>then flash an gingerbread Vivid custom ROM and immediately flash the appropriate boot.img to go with it.
I cant get a recovery to take so I am guessing I need to fix that before going on to a custom ROM?

I had a similar problem with bell ics bootloop. I flashed kozmicks r2 from fastboot, and used darkraider 1.5.4.zip from recovery. Device was s-on at the time.

@RagnarDanneskjold you have links to those two files

Kernel http://forum.xda-developers.com/showthread.php?t=1572015
Dark Raider http://forum.xda-developers.com/showthread.php?t=1586613
bobmutch2 said:
@RagnarDanneskjold you have links to those two files
Click to expand...
Click to collapse

@Maqical
Thanks.
If you are still having trouble you can PM me.

The kernel didn`t take.
>>>flash the kernel from fastboot
Here is what I get when I flash the kernel
"fastboot devices"
gets me "HT1ALVJ03540"
"fastboot flash boot Kernels/KozmiKKernel-RC2.zip"
gets me
sending 'boot' (5480KB)... OKAY [1.332s]
writing 'boot' ... FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.652s

Not exactly sure so dont depend on me for this.. but when i flash my kernels i have a "boot.img" and you put it in with the files for fastboot and i open a command window and type "fastboot flash boot boot.img, you're flashing a zip
bobmutch2 said:
The kernel didn`t take.
>>>flash the kernel from fastboot
Here is what I get when I flash the kernel
"fastboot devices"
gets me "HT1ALVJ03540"
"fastboot flash boot Kernels/KozmiKKernel-RC2.zip"
gets me
sending 'boot' (5480KB)... OKAY [1.332s]
writing 'boot' ... FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.652s
Click to expand...
Click to collapse

Refer to this link:
http://forum.xda-developers.com/showthread.php?t=1416836
Find the boot.img file for kozmicks kernel. You can download it or extract it from
darkraider.zip.
Place the boot.img file in you fastboot folder on your computer.
Run the following commands in fastboot
fastboot flash boot boot.img
fastboot reboot
Now you must flash a custom recovery. CWM, or WCX will work.
You can use all-in-one-toolkit to do this.
From recovery install darkraider from .zip.
Folllow instructions, use defaults.

@RagnarDanneskjold
In darkraider_v1.5.5.zip there is 5 kernels faux, holics, kozmikb7, kozmikrc2, and stock, they all have boot.img but kozmik b7 and rc2?
Which one would I use?

I am not sure if have read all I have posted. I cant write stuff to this device. kernels dont take, recovery images dont take, the PM39IMG.zip doesn`t take. There is some issues here more than just finding the right files to flash.

I used 1.5.4 because s-on compatibility has been dropped in newer versions, (so I understand?), so I would use that version. Take the boot.img from kozmiksrc2. Make sure you select it when installing darkraider.

A Kernel of your choice.. but for now just until you get the phone working i would use stock
bobmutch2 said:
@RagnarDanneskjold
In darkraider_v1.5.5.zip there is 5 kernels faux, holics, kozmikb7, kozmikrc2, and stock, they all have boot.img but kozmik b7 and rc2?
Which one would I use?
Click to expand...
Click to collapse

[Q] Problem Installing a Custom Recovery

I'm trying to install TWRP recovery via CMD but I'm having problems. As of now, I've done the following:
Downloaded TWRP 2.5.0.0
Placed the file in the same folder used to unlock the phone that also contains fastboot
With the phone connected, i run the following command
Code:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
In the prompt window, I received the following results "< waiting for device >" but i don't see anything progress thereafter on the phone or prompt window
I tried to reboot into recovery and now receive a red exclamation point within a triangle that's over a phone. See attached photo.
Thereafter, I have to force restart
Does anyone have any advice?

UPDATE
I was finally able to write the recovery on the phone. However, now when I try to boot into recovery, it fails to load recovery and boots as a normal restart.

UPDATE
I tried to reflash TWRP again. Following the reflash, I also deleted the cache using the following command
Code:
fastboot erase cache
I then reboot the bootloader using
Code:
fastboot reboot-bootloader
This time around, after making an attempt to boot into recovery, I would get the message "Entering Recovery...". However, after a few seconds, the phone would turn off.
Thereafter, I tried to flash the OEM recovery using the steps above and I'm still have the same problem. Is my recovery partition corrupt?

I read that it helps to erase the recovery partition prior to flashing over an existing recovery. I tired the command
Code:
fastboot erase recovery
But I receive the following results
Code:
c:\Android>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.001s
If erasing the recovery partition is good practice, how do I go about doing it?

I'm having the same problem.
I can successfully flash the TWRP 2.5.0.0 recovery ROM, but when I try to load into the recovery to flash a custom ROM, I see a flash of purple text on white background, then the screen goes black and boots normally.
Any help would be appreciated.

Ok... I had some issues when installing recovery so this is what I did...
Be advised that next steps are highly risky and that it might have worked for me but I take no responsibility if you break your device
After following almost all the instructions, I read that someone flashed the recovery to the boot partition. So I did that.
fastboot flash boot recovery.img
Now, after this, the device went to a constant bootloop and suddenly the recovery appeared.
Also, I erased the cache from fastboot with next command:
fastboot erase cache
I'm planning to post the procedure I've followed but I don't have much time lately.
Will try to do it as soon as possible.
Best regards.
---------- Post added at 12:22 AM ---------- Previous post was at 12:21 AM ----------
brianhill1980 said:
I'm having the same problem.
I can successfully flash the TWRP 2.5.0.0 recovery ROM, but when I try to load into the recovery to flash a custom ROM, I see a flash of purple text on white background, then the screen goes black and boots normally.
Any help would be appreciated.
Click to expand...
Click to collapse
For you mate, go into fastboot run:
fastboot erase cache
Then try again.

:No-Frost: said:
For you mate, go into fastboot run:
fastboot erase cache
Then try again.
Click to expand...
Click to collapse
You sir are my hero. Thank you!
I rebooted and went into Fastboot. Ran "fastboot erase cache". Then re-flashed the recovery image. Then ran the command "fastboot erase cache" again. Then restarted the bootloader, then went into the recovery and it worked.

brianhill1980 said:
You sir are my hero. Thank you!
I rebooted and went into Fastboot. Ran "fastboot erase cache". Then re-flashed the recovery image. Then ran the command "fastboot erase cache" again. Then restarted the bootloader, then went into the recovery and it worked.
Click to expand...
Click to collapse
Glad to help mate and glad to know you can go into recovery now

pwr2wh8 said:
UPDATE
I tried to reflash TWRP again. Following the reflash, I also deleted the cache using the following command
Code:
fastboot erase cache
I then reboot the bootloader using
Code:
fastboot reboot-bootloader
This time around, after making an attempt to boot into recovery, I would get the message "Entering Recovery...". However, after a few seconds, the phone would turn off.
Thereafter, I tried to flash the OEM recovery using the steps above and I'm still have the same problem. Is my recovery partition corrupt?
Click to expand...
Click to collapse
Do you have the Sprint version? I have Sprint and I was running into the same issue. After searching everywhere for this issue, I came across this post: http://forum.xda-developers.com/showpost.php?p=40828046&postcount=240
Here's the link to the file you need: http://techerrata.com/browse/twrp2/m7wls
I flashed this recovery img and it finally worked after all the other ones failed in the same way you described.
Hope it works for you!

[Q] Can't boot into recovery HTC one

Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
EDIT & ANSWER;
Sprint phone needed Sprint TWRP image

Have you tried
fastboot erase cache

BenPope said:
Have you tried
fastboot erase cache
Click to expand...
Click to collapse
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"

ryryzz said:
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"
Click to expand...
Click to collapse
Gave that all a shot all over again. Still can't boot into recovery

Is fast boot off?

Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
BenPope said:
Is fast boot off?
Click to expand...
Click to collapse
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium

hardstuffmuc said:
Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Same deal. On it's way to booting into recovery it goes blank, resets and reboots into system

C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adt\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7422 KB)...
OKAY [ 1.139s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.778s
C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adt\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
There's the last log - and then on it's way to recovery there's a red disclaimer and a pink text saying "Entering Recovery"...then after 20 seconds it resets

Did you try various recovery (versions) ? May be , you just have corrupted recovery image.

tash2013 said:
Did you try various recovery (versions) ? May be , you just have corrupted recovery image.
Click to expand...
Click to collapse
at this point I've tried stock, twrp and cwm. All with the same results

Jman12000 said:
at this point I've tried stock, twrp and cwm. All with the same results
Click to expand...
Click to collapse
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.

tash2013 said:
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.
Click to expand...
Click to collapse
Is that something I can do with the revone binary? To be honest, I have no idea how to turn security back on. I can relock it and that may be about it.
I stumbled upon another thread, shares a common theme as my issue, but with a different twist. Using a superboot.img as a rooting method instead of flashing it via recovery. It somewhere says that the boot.img needs to be flashed as well, however I can't find a decent boot.img to flash. The superboot tool seems like unproven territory right now.
Here's the other thread, I've leafed through it and found no determinable answer for my particular issue.
http://forum.xda-developers.com/showthread.php?p=39852757#post39852757

Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.

Jman12000 said:
Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
Click to expand...
Click to collapse
try to install recovery again
you can download recovery from here
http://www.clockworkmod.com/rommanager

tash2013 said:
Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.
Click to expand...
Click to collapse
Code:
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot oem writesecureflag 3
...
(bootloader) writesecureflag: partitions siganture pass
OKAY [ 1.665s]
finished. total time: 1.666s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.046s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
error: device not found
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?

I've just skimmed through the posts and didn't see this mentioned
If you are still able to boot into the system, download either GooManager (for TWRP) or RomManager (for CWM) and use either of those apps to install recovery. Once done, you can use the app to boot into recovery instead of the fancy ADB commands or button presses.

Jman12000 said:
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?
Click to expand...
Click to collapse
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process

tash2013 said:
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process
Click to expand...
Click to collapse
So both that method through ADB shell and GooManager require root. Every rooting method requires recovery, so I don't have perm root yet.

You quoted me, but answered not to me.
Read a post #26 from my link above

Possible Solution
Hello I have the same problem and the solution was:
1. Settings - Energy- Fastboot uncheked
2. Flash Recovery usin one all-in-one-kit
3. Erase Cache 3 times
4. Unplug to PC, and load into system normal
5. Turn off phone - via stock menu NOT FORCE TO OFF pressing the off button
6. Wait 2 minutes, and boot into HBOOT - Power + Volume(-) pressing
7. Choose recovery
Ready.. May these work for you! Let me know

[Q] TWRP Tries to load but fails

Hi, I have an htc one m7 verizon. I am currently running nusense 7.8. I wanted to update to v8.0. Anyway I go to recovery from the menu and the screen goes black like it is going to the team win logo but it goes back to the white screen that says entering recovery. It stays on that screen until I power plus volume down. I am confused because twrp loaded fine. I have tried cwm as well. no recovery software will load. The phone boots to nusense 7.8 fine. Anyone know what would cause recovery software not to load?

Try flashing the latest version of TWRP through Fastboot to see if the issue resolves. Make sure you use TWRP for the Verizon M7.

MarkBell said:
Try flashing the latest version of TWRP through Fastboot to see if the issue resolves. Make sure you use TWRP for the Verizon M7.
Click to expand...
Click to collapse
I agree re-flash TWRP for Verizon
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp-2.8.0.1-m7wlv.img
fastboot erase cache
fastboot reboot-bootloader

Thanks for throwing up the link clsA. I was about to do that a minute ago when my phone died. Lol.

I will give twrp 2.8.0.1 a try. I have tried several versions but not that one.

fastboot flash recovery openrecovery-twrp-2.8.0.1-m7wlv.img
fastboot erase cache
fastboot reboot-bootloader[/QUOTE]
I tried the above and I am still getting stuck with the white screen green htc logo and entering recovery at the top. I am happy with nusense 7.8 except for youtube not working. I do have some backups that are useless when twrp will not load. Maybe it is time to ruu this phone.

I installed the ruu VZW.M7.5.28.605.2.PN0731IMG.zip. It installed ok. I am still s off and rooted. I used flashify to flash twrp 2.8.0.1. My phone still will not load a recovery app.......I wonder if this is a hardware issue?

Anybody have any ideas? everything on my phone works accept the ability to load the recovery software. Like I said I was able to install an RUU file with fastboot. I would really like to get twrp working so I can backup and restore again.

I think I found my issue. I am pretty sure my recovery partition is hosed. The command fastboot format recovery fails. I get this message:
Formatting is not supported for filesystem with type 'raw.
Anybody know how to rebuild a corrupted recovery partition?

vaping redhead said:
I think I found my issue. I am pretty sure my recovery partition is hosed. The command fastboot format recovery fails. I get this message:
Formatting is not supported for filesystem with type 'raw.
Anybody know how to rebuild a corrupted recovery partition?
Click to expand...
Click to collapse
recovery partition is a raw partition, the only EXT4 partitions are /system, /cache, and /data
can you copy/paste your command prompt output as you do the fastboot commands that clsA gave you.

nkk71 said:
recovery partition is a raw partition, the only EXT4 partitions are /system, /cache, and /data
can you copy/paste your command prompt output as you do the fastboot commands that clsA gave you.
Click to expand...
Click to collapse
Here you go.
c:\adb>fastboot flash recovery openrecovery-twrp-2.8.0.1-m7wlv.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9596 KB)...
OKAY [ 1.071s]
writing 'recovery'...
OKAY [ 0.862s]
finished. total time: 1.935s
c:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.511s]
finished. total time: 0.512s
c:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.041s
I have tried flashify, and also an ruu version of twrp. still no go.

Have you tried turning s on, relocking bootloader, running RUU, doing factory reset in Stock recovery and then unlocking and installing TWRP? It is worth a shot I assure you. I had problems with TWRP about a month back and this solved it for me.