Develop Bugs

Could use a hand getting back to Stock

HTC One X Quadcore, Virgin Mobile Australia, CID HTC_023, bootloader unlocked, SDK and Sync manager up to date.
I followed root instructions per Ausdroid which summarizes MoDaCo method using "r3-endeavor-insecurebootandroot" except it doesn't tell you when to backup your existing ROM. So no backup of the stock ROM (believe I feel dumb enough about it).
After reading up a bit more, installed Clockworkmod-5.8.4.0 and backed up the working ROM (presumably r3-endeavor-insecurebootandroot).
Since video was not working and caused forced reboots, I flashed the boot img that was in the r3-endeavor-insecurebootandroot.zip file. No luck, so I decided to go to MoDaCo website and try one of the ROMs he has there. The Sense and Vanilla ROMs there resulted in being stuck in the HTC brilliant screen (left it there plugged in overnight since Paul mentions that one should be patient on first boot).
Ok, so tried various other ROMs, no luck. Always erased cache before and after and tried various combinations of wiping data, factory resets, both in phone and in Clockwork etc., no luck. Tried the OneX All in One Kit v1.0 to reflash the Kernel to stock 2.6.39.4 (not even sure that's the one I should be using), no luck. Ok, so I'm guessing it's time to use the RUU. Found a cool method to bypass Filefactory premium and managed to download my RUU: RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed. Presumably the correct one since I used fastboot to give me the 1.29.728.12 as well as the CID info HTC_023.
Following XDA instructions on RUU recovery, I relocked the bootloader, confirmed the version and tried running the RUU.
The RUU tried to run but I get an error
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
Suggestions?
forgot to mention using win 7, and already tried a few windows support fixes for 0x80070002 errors.

bump
Anyone know what this error might mean?
QUOTE=requiem11;30025087]HTC One X Quadcore, Virgin Mobile Australia, CID HTC_023, bootloader unlocked, SDK and Sync manager up to date.
I followed root instructions per Ausdroid which summarizes MoDaCo method using "r3-endeavor-insecurebootandroot" except it doesn't tell you when to backup your existing ROM. So no backup of the stock ROM (believe I feel dumb enough about it).
After reading up a bit more, installed Clockworkmod-5.8.4.0 and backed up the working ROM (presumably r3-endeavor-insecurebootandroot).
Since video was not working and caused forced reboots, I flashed the boot img that was in the r3-endeavor-insecurebootandroot.zip file. No luck, so I decided to go to MoDaCo website and try one of the ROMs he has there. The Sense and Vanilla ROMs there resulted in being stuck in the HTC brilliant screen (left it there plugged in overnight since Paul mentions that one should be patient on first boot).
Ok, so tried various other ROMs, no luck. Always erased cache before and after and tried various combinations of wiping data, factory resets, both in phone and in Clockwork etc., no luck. Tried the OneX All in One Kit v1.0 to reflash the Kernel to stock 2.6.39.4 (not even sure that's the one I should be using), no luck. Ok, so I'm guessing it's time to use the RUU. Found a cool method to bypass Filefactory premium and managed to download my RUU: RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed. Presumably the correct one since I used fastboot to give me the 1.29.728.12 as well as the CID info HTC_023.
Following XDA instructions on RUU recovery, I relocked the bootloader, confirmed the version and tried running the RUU.
The RUU tried to run but I get an error
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
Suggestions?
forgot to mention using win 7, and already tried a few windows support fixes for 0x80070002 errors.[/QUOTE]

have u tried to install the RUU in fastboot mode?

GUARDIANBD said:
have u tried to install the RUU in fastboot mode?
Click to expand...
Click to collapse
Thanks for the reply. It's a good point that is occasionally not mentioned. I've always assumed that the RUU is to be run while in bootloader with fastboot command window open and RUU exe located within the fastboot directory. I used "fastboot devices" to confirm that the pc has recognized the HOX. I also disconnected everything and tried to run the RUU exe file on its own in order to manually flash the exe file contents, but the RUU does not run properly giving me the 0x80070002 windows error message.
three things I have yet to try:
1 install the stock recovery tool (still relying on CMW)
2 run the RUU on another computer (read somewhere that this helped someone's RUU issue when they tried it on an XP)
3 try to download the RUU again
not sure if any of these would help.
By chance, did you mean that the RUU can be somehow executed as a fastboot command? If so I haven't seen anything about it and would appreciate a detailed description of how to do that.
tanks

I think you have to flash stock recovery and lock the bootloader to flash ruu. Don't quote me though. Worth a try.
Sent from my now amazing HTC One X thanks to TeamVenoms ViperX rom

smidgeox said:
I think you have to flash stock recovery and lock the bootloader to flash ruu. Don't quote me though. Worth a try.
Sent from my now amazing HTC One X thanks to TeamVenoms ViperX rom
Click to expand...
Click to collapse
I've tried with the bootloader locked but not with the stock recovery flashed. I'll try it and report back. Any other suggestions are welcome.
thanks for replying.

Partial success
Downloaded the RUU again and this time it worked (who knows why). The RUU gets cracking and then stops telling me that my battery is less than 30% (it shows 100% in my third-party battery monitor).
So I decided to unpack the ROM.zip file from the %temp% directory as instructed in the wiki, but this time, fastboot flash boot boot.img results in a FAILED Remote something or other.
? Do I have to unlock the bootloader in order to manually flash the boot.img and the system.img files from the RUU?
For anyone who might be in the same position here's what worked for me:
Note, these are not step by step instructions!
RUU windows error -> Redownloaded the RUU file and it worked fine
RUU complains about battery less than 30% -> Connect to a different USB port
ROM.zip boot.img can't flash due to FAILED REMOTE error -> unlock boot loader again and then flash boot.img
ROM.zip boot.img flashed OK but System.img fails says file to large -> re-lock boot loader and start the RUU again

requiem11 said:
Downloaded the RUU again and this time it worked (who knows why). The RUU gets cracking and then stops telling me that my battery is less than 30% (it shows 100% in my third-party battery monitor).
So I decided to unpack the ROM.zip file from the %temp% directory as instructed in the wiki, but this time, fastboot flash boot boot.img results in a FAILED Remote something or other.
? Do I have to unlock the bootloader in order to manually flash the boot.img and the system.img files from the RUU?
For anyone who might be in the same position here's what worked for me:
Note, these are not step by step instructions!
RUU windows error -> Redownloaded the RUU file and it worked fine
RUU complains about battery less than 30% -> Connect to a different USB port
ROM.zip boot.img can't flash due to FAILED REMOTE error -> unlock boot loader again and then flash boot.img
ROM.zip boot.img flashed OK but System.img fails says file to large -> re-lock boot loader and start the RUU again
Click to expand...
Click to collapse
I should imagine that the bootloader needs to be unlocked to be able to flash any sort of .img file.
Have you flashed the ruu with stock recovery yet? I suggest you try this if you haven't already, if this fails. Ensure you have the correct matching RUU, then flash stock recovery, lock bootloader and try that.

Someone correct me if I am wrong but each ROM has a matching boot.img that needs to be flashed before flashing the rom.
Look on YouTube cursed4eva has an easy to follow video about going back to stock ROM

nixey55 said:
Someone correct me if I am wrong but each ROM has a matching boot.img that needs to be flashed before flashing the rom.
Look on YouTube cursed4eva has an easy to follow video about going back to stock ROM
Click to expand...
Click to collapse
Indeed, the boot.img contains the kernel & with s-on devices, boot.img's aren't flashed through recovery so it needs to be done on a computer with fastboot (fastboot flash boot boot.img).
---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------
requiem11 said:
Downloaded the RUU again and this time it worked (who knows why). The RUU gets cracking and then stops telling me that my battery is less than 30% (it shows 100% in my third-party battery monitor).
So I decided to unpack the ROM.zip file from the %temp% directory as instructed in the wiki, but this time, fastboot flash boot boot.img results in a FAILED Remote something or other.
? Do I have to unlock the bootloader in order to manually flash the boot.img and the system.img files from the RUU?
For anyone who might be in the same position here's what worked for me:
Note, these are not step by step instructions!
RUU windows error -> Redownloaded the RUU file and it worked fine
RUU complains about battery less than 30% -> Connect to a different USB port
ROM.zip boot.img can't flash due to FAILED REMOTE error -> unlock boot loader again and then flash boot.img
ROM.zip boot.img flashed OK but System.img fails says file to large -> re-lock boot loader and start the RUU again
Click to expand...
Click to collapse
Also, i forgot to mention. MAKE sure you hold the power and down volume key down to enter the bootloader, then enter 'fastboot' to be able to flash the boot.img in fastboot , i thik that might be the reason you're getting the failed error.

smidgeox said:
Indeed, the boot.img contains the kernel & with s-on devices, boot.img's aren't flashed through recovery so it needs to be done on a computer with fastboot (fastboot flash boot boot.img).
---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------
As a point of clarification, the RUU contains the associated boot.img and system.img required to get back to stock. If your RUU fails for some reason, there are instructions in the HTC One X wiki for extracting the RUU file and manually flashing the boot.img and system.img
Also, i forgot to mention. MAKE sure you hold the power and down volume key down to enter the bootloader, then enter 'fastboot' to be able to flash the boot.img in fastboot , i thik that might be the reason you're getting the failed error.
Click to expand...
Click to collapse
Yes, I did enter the bootloader correctly.

nixey55 said:
Someone correct me if I am wrong but each ROM has a matching boot.img that needs to be flashed before flashing the rom.
Click to expand...
Click to collapse
You're right as to the point that each ROM has a matching boot.img, but in which order you flash them doesnt matter at all.

Unlock the bootloader again and flash a custom ROM, it's usually the easiest way out. Don't bother using the boot.img root method as custom ROMs are pre rooted almost 99 percent of the time.
Sent from my Inspire 4G using Tapatalk 2

requiem11 said:
HTC One X Quadcore, Virgin Mobile Australia, CID HTC_023, bootloader unlocked, SDK and Sync manager up to date.
I followed root instructions per Ausdroid which summarizes MoDaCo method using "r3-endeavor-insecurebootandroot" except it doesn't tell you when to backup your existing ROM. So no backup of the stock ROM (believe I feel dumb enough about it).
After reading up a bit more, installed Clockworkmod-5.8.4.0 and backed up the working ROM (presumably r3-endeavor-insecurebootandroot).
Since video was not working and caused forced reboots, I flashed the boot img that was in the r3-endeavor-insecurebootandroot.zip file. No luck, so I decided to go to MoDaCo website and try one of the ROMs he has there. The Sense and Vanilla ROMs there resulted in being stuck in the HTC brilliant screen (left it there plugged in overnight since Paul mentions that one should be patient on first boot).
Ok, so tried various other ROMs, no luck. Always erased cache before and after and tried various combinations of wiping data, factory resets, both in phone and in Clockwork etc., no luck. Tried the OneX All in One Kit v1.0 to reflash the Kernel to stock 2.6.39.4 (not even sure that's the one I should be using), no luck. Ok, so I'm guessing it's time to use the RUU. Found a cool method to bypass Filefactory premium and managed to download my RUU: RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350_signed. Presumably the correct one since I used fastboot to give me the 1.29.728.12 as well as the CID info HTC_023.
Following XDA instructions on RUU recovery, I relocked the bootloader, confirmed the version and tried running the RUU.
The RUU tried to run but I get an error
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
Suggestions?
forgot to mention using win 7, and already tried a few windows support fixes for 0x80070002 errors.
Click to expand...
Click to collapse
Can you upload the file RUU_ENDEAVOR_U_ICS_40_hTC_Asia_SEA_WWE_1.29.728.12_Radio_1.1204.105.14_release_261350 I can't download it form filefactory !

Not sure where I'd upload it for you to get it, but I followed some instructions that I found here and it worked using Safari
http://o-ogy.blogspot.com.au/2012/02/how-to-use-filefactory-premium-cookie.html
There are a lot of steps, but follow them carefully and it should work.

How do I Update Rooted HTC ONE X ?

Hi guys,
I have a rooted one X and want to install he latest update. I tried to relock my bootloader by starting fastboot and then type:
" fastboot oem relock"
Now my phone should be relocked and it does show relocked in pink in the bootloader, but under that stands security warning I don't kno if thats normal or important or something. I rebooted my phone and downloaded the update but when i try to install it i still get into the bootloader.
What am I doing wrong and how do I unlock my bootloader again after the update?
Sascha

You unlock by flashing the unlock_code.bin file again like you first did.
To apply an ota update you also need to reflash the stock recovery
Sent from my HTC One X using xda app-developers app

Okay I unlocked my bootloader flashed my recovery.img and relocked my bootloader again. But still it reboots into the bootloader. Could it be my backup of the recovery.img is already wrong?? and if so where can i get the right one

My phone:
1.29.401.11
HTC__102
I Relocked the bootloader and got back to stock recovery.. But while updating i have an error.. Phone with red square on him..
Idk what i'm doing wrong. i have status relocked.. Maybe something wrong with stock recovery?

I tried the recovery image attached to this post first time it deleted al my data second time the update succeeded

Still can't update.. tried some other recoveries, but still get error while updating..

try to flash the stock boot.img first.

ckpv5 said:
try to flash the stock boot.img first.
Click to expand...
Click to collapse
can you give me the link pls?

http://forum.xda-developers.com/showthread.php?t=1692404

lirox said:
Still can't update.. tried some other recoveries, but still get error while updating..
Click to expand...
Click to collapse
same here

ckpv5 said:
http://forum.xda-developers.com/showthread.php?t=1692404
Click to expand...
Click to collapse
It returns me to bootloader))

You can try to following download stock recovery and download the RUU of your phone ( the same version as your latest official update ) then go to fastboot
Type
Fastboot flash recovery "your stock recovery " .img
Hit enter
Fastboot flash OEM lock
This might give an error but when you type it again it wil work
Now put your phone in fastboot again and then start your RUU from your pc if it gives an error just search for another One it will take about 10 min but after your phone will work fine
Hope it helps
Sent from my HTC One X using xda app-developers app

[Q] Cant get out of Bootloader anymore. Bootloader relocked - Security warning

Hello,
I have now completely made my PrimoU useless.
For weeks I try to get the CM10 from Lloir working but it never got over the booting screen. So I tried several things, but never came further. Flashing back to my first rom always worked. I tried to unlock bootloader again (thought, maybe it isn't) but it was unlocked. Therefore I tried to lock it to maybe start from scratch.
That was a big mistake, because since then, I am stuck on bootloader. On the top in pink is written "Relocked" "Security warning". No recovery, no starting to the software. I gave it up.
Can anyone help me? I only have a Mac. Is there ANY possibility to just set the whole phone back to Factory form? So no bootloader unlocking, no custom rom, no recovery? I am really thinking about changing it back to this and maybe sell it afterwards. I used HTC Desire for two years with several custom roms and everything. Always could work with it. This device is unfortunately not the same.
But at first I hope anyone can help me to get this back booting with Mac?
Thanks to you all in advance

Moved to Q&A. Please ask all questions there.

Try this ./fastboot-mac flash unlock Unlock_code.bin
You have unlocked it again
You should have it in your email...
Then download the latest boot.img and zip file from cm10 and transfer the Rom zip to your sdcard....
Check development section for cwm recovery 6...download and rename it to recovery.img
Flash it by
./fastboot-mac flash recovery recovery.img
Flash boot.img by renaming it and
./fastboot flash boot boot.img
Go to recovery and flash the cm10 zip file....
Sent from my HTC One V

shubhamchamaria said:
Try this ./fastboot-mac flash unlock Unlock_code.bin
You have unlocked it again
Click to expand...
Click to collapse
Thank you for your help! But the problem begins here. I get the message
Erkan-Ertans-MacBook:fastboot Erkan$ ./fastboot flash unlocktoken Unlock_code.bin
error: cannot load 'Unlock_code.bin'

tekillo said:
Thank you for your help! But the problem begins here. I get the message
Erkan-Ertans-MacBook:fastboot Erkan$ ./fastboot flash unlocktoken Unlock_code.bin
error: cannot load 'Unlock_code.bin'
Click to expand...
Click to collapse
Do you have the Unlock_code.bin?

soham_sss said:
Do you have the Unlock_code.bin?
Click to expand...
Click to collapse
Yes I do. I went through the whole procedure..

tekillo said:
Yes I do. I went through the whole procedure..
Click to expand...
Click to collapse
U need to put in the path of the unlock code....try this ...type the command and instead of Unlock_code.bin just drag that file onto the terminal screen....them it should work
Sent from my HTC One V

shubhamchamaria said:
U need to put in the path of the unlock code....try this ...type the command and instead of Unlock_code.bin just drag that file onto the terminal screen....them it should work
Sent from my HTC One V
Click to expand...
Click to collapse
Thank you all, I used this way:
I installed Virtualbox to use a xp system to unlock bootloader again.
After that I still wasn''t able to install CM10. Whatever I do, it always sticks at the bootscreen.
I then tried the new Modaco Vanilla Rom, and it worked without ANY problems. Now I use this for start... It seems as Jelly Bean is not possible for me...

relocked security warning
I have instaled now MAximus 4.0
i tried to instal JB Maximus 4.1
i have cidnum: HTC__032
after "relocked" i have "security warning"
i watch "Video tutorial: (thanks Flow-Wolf)"
i see that he have HBOOT 0.43
i have 1.12 is there a problem?
i tried fastboot clear cache, charging over 30% but i can't install PJ46IMG, i tried adb reboot oem-78 and i get error no device found, i have the latest Fastboot Kit V4.1, CWM 5840...
nothing i'm stucked
But i can unlock and now i came back to Maximus 4.0
What cand i do. Help!!

you got the wrong forum dude
Sent from my One V using xda premium

Your problem with CM10
The problem was probably you didn't flash the kernel because if you did then you would have to flash a stock kernel to return to your original rom. Just some advice for future reference

[Q] Can not install RUU

Hello guys.
I'm following this thread to install JB on my HOX.
Currently my phones cid is HTC__102
I almost crashed my phone yesterday as I was stuck in the boot loop, had to use adb to push ICS and install ICS back.
Now I noticed my HBOOT is 0.43, the thread says to download one of the file. I have no idea which one
Tried all 3 all 3 crashed, I'm not sure what happens.
These to run untill I get to this place (see attachment 0.png).
ruu_endeavor_u_ics_40_htc_europe_1.29.401.11_radio_1.1204.105.14_release_260491_signed_c9d22.exe and RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe exit with an error of "UNKNOWN ERROR" (see attachment 1.png)
and
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7_Radio_1.1204.104.14_release_259281_signed.exe crashes and doesn't do anything.
One thing though, the phone is Unlocked, not sure if that matters and I'm using windows 8, but I run all the software in compatibility mode.
Thank you and sorry for my bad spelling.

You need to relock bootloader.
Sent from my HTC One X using xda app-developers app

XxVcVxX said:
You need to relock bootloader.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
And you need to install the Stock Recovery, for 1.29 ROM, link is provided in this thread http://forum.xda-developers.com/showthread.php?t=1594819

you cant downgrade ruu

Now I'm stuck in a loop between power up and hboot.
The phone says "Re-Locked" and won't load the ROM.
Oh the thread I was speaking of is : /showthread.php?t=1562603
Could someone explain me the steps I should make.
for example download this, update this, install this then this, rom and voila.
I'm totally lost here.

tomascus said:
you cant downgrade ruu
Click to expand...
Click to collapse
Now I see, you have 2.17 already, so you have to flash 2.17 minimal.
Btw. strange that you still have hboot 0.43 and a 2.17 base?
You cannot flash the 1.29, so you have to flash:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed
So, you have relocked
Edit: You could try to RUN the RUU when device is in Fastboot without going back to stock recovery, cause it's in the RUU, but if that doesn't work... follow next steps.
Btw. Goto fastboot while unplugged and plugin usb cable after entered fastboot, you should see usb appear.
1. Next you need Stock Recovery:
for stock recovery you could run the above RUU, after you donwloaded it, but not install it.
After you run the RUU, it unpacks to the following directory:
C:\Users\[username]\AppData\Local\Temp\{some guid}\{some other guid}\
Get the rom.zip form that directory and in there you can find the Stock Recovery
You can flash recovery through Fastboot using the following command:
fastboot flash recovery [name of the retrieved recovery].img (you need to place it in the fastboot folder.
2. If you have Stock Recovery, Go into Fastboot mode and flash the RUU (2.17).
Something resources:
RUU collection: http://forum.xda-developers.com/showthread.php?t=1543604
Goto Stock Guide: http://forum.xda-developers.com/showthread.php?t=1859714

Bootloop on Desire HD

Hi Peeps. Appreciate any help here.
Recently got 02 faulty Desire HD from someone. No idea what he did. One of it has a bootloop, while the other is just stuck on the HTC logo. I will just concentrate my problem on the device with the bootloop as it seems to have a higher chance of recovering.
Was able to boot to HBoot and shows me this screen. I will type it out as I have no access to camera for now.
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0030
MICROP-0438
RADIO-26.17.14.11_M
EMMC-BOOT
FEB 20 2012, 16:03:18
Tried to flash stock rom, cannot. Go to recovery, goes back to bootloop. Factory Reset, goes back to bootloop. Is there anyone to revive this phone?

Can u flash stock roms that's in one file .exe (RUU i think)? Boot into Hboot, plug usb cable and run the rom installer

That's what I did. It could not complete the update.
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_R_Radio_12.65.60.29_26.14.04.28_M_release_233505_signed
This is the rom that I used...

You are s-on. You have to flash the boot.img using fastboot after installing the rom.
Sent from my Inspire 4G using xda premium

Have you fastboot flashed a recovery?

Firstly. is there anything to make it S-OFF? Couldn't find a method that works. Most of it I found requires to boot into Android which is impossible for my case.
Also tried to put PD98IMG.zip in SD card to flash it, but give CID incorrect error.

ramdesai said:
You are s-on. You have to flash the boot.img using fastboot after installing the rom.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
bananagranola said:
Have you fastboot flashed a recovery?
Click to expand...
Click to collapse
Tried to flash recovery but status failed...

yagami34 said:
Tried to flash recovery but status failed...
Click to expand...
Click to collapse
Knowing what the error was would be helpful. Of you want S-Off you need to relock and do it manually.

bananagranola said:
Knowing what the error was would be helpful. Of you want S-Off you need to relock and do it manually.
Click to expand...
Click to collapse
actually what really matters to me is that I can get it working to stock rom. Rooting can be done later... but I cant even get it flashed to stock rom!!

yagami34 said:
actually what really matters to me is that I can get it working to stock rom. Rooting can be done later... but I cant even get it flashed to stock rom!!
Click to expand...
Click to collapse
Did it give an error when you tried?

bananagranola said:
Did it give an error when you tried?
Click to expand...
Click to collapse
I will try my best to explain cause I have no idea what's happening...
1. used fastboot using CMD to flash CWM to recovery. Error: signature verify fail.
2. Tried RUU.exe to flash. Simply says the update could not be completed.
Is there any thing I could do with Hboot or Fastboot that could revive the phone? I think I tried almost all methods... unless there is other ways that I have not tried...

yagami34 said:
I will try my best to explain cause I have no idea what's happening...
1. used fastboot using CMD to flash CWM to recovery. Error: signature verify fail.
2. Tried RUU.exe to flash. Simply says the update could not be completed.
Is there any thing I could do with Hboot or Fastboot that could revive the phone? I think I tried almost all methods... unless there is other ways that I have not tried...
Click to expand...
Click to collapse
Are you unlocked? Exactly what command did you use to flash? Are you drivers properly installed (HTC Sync with phone unplugged)? Did you flash from the folder containing your recovery.img?

bananagranola said:
Are you unlocked? Exactly what command did you use to flash? Are you drivers properly installed (HTC Sync with phone unplugged)? Did you flash from the folder containing your recovery.img?
Click to expand...
Click to collapse
1. I'm on s-on. Does it matters?
2. Bootloader should be unlocked after flashing the unlock.bin from htcdev.com. I saw the *** UNLOCK *** when I go into HBOOT.
3. Command I used was *fastboot flash recovery recover.img*. The recover.img is actually the CWM recovery.
4. HTC Sync is installed.
4. Yes i did. It gave me FAILED status. Error: Signature verify error.
I will try to snapshot whatever process I did to make my explanation clearer later part of the day.

Make sure the file name is correct of the recovery.img file
Fastboot flash recovery recovery.img
Sent from my HTC Desire HD using xda app-developers app

yagami34 said:
1. I'm on s-on. Does it matters?
2. Bootloader should be unlocked after flashing the unlock.bin from htcdev.com. I saw the *** UNLOCK *** when I go into HBOOT.
3. Command I used was *fastboot flash recovery recover.img*. The recover.img is actually the CWM recovery.
4. HTC Sync is installed.
4. Yes i did. It gave me FAILED status. Error: Signature verify error.
I will try to snapshot whatever process I did to make my explanation clearer later part of the day.
Click to expand...
Click to collapse
Signature check is failing or the .img file is flaw (try downloading again) or your bootloader is not unlocked in its whole. That happens from time to time. Try using this recovery image (touch CWM):
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.1.5-ace.img