Database Users

HTC Magic - Help required, stuck on splash screen.

Hi guys, here is the situation:
A friend of mine brought his HTC Magic for me to look at last night. The phone starts but sticks on the 'HTC Magic' screen (I think this is called the splash screen?).
It boots into safe mode when I hold Home and Power, however it says this on the bottom of the safe mode screen: E:Can't open /cache/recovery/command
I tried a factory reset from this screen but that didn't help.
However, on the safe mode screen there is an option to apply update from SD Card, which brings me to my questions:
1) Firstly, I'm not a complete beginner when it comes to dealing with this kind of stuff, I have successfully rooted my MyTouch 3G and installed CaNNoNs complete eclair, so I was wondering, with regards to this phone, can I just get a copy of the original ROM and flash it using the update from SD?
2) Also is there anyway to know if the phone is already rooted, besides the fact that the standard recovery screen came up? (which would mean it isn't, right?)
3) If the flash from SD card would work, where do I get the ROM from? There is the word 'TIM' and a weird 3 squiggly line symbol when you first turn on the phone. I think this means its originally from an Italian provider. If so where would I get that ROM.
Thanks in advance for your help. This community has been a great source of information and experience in my life. I thank you all.
Oh yeah I forgot to tell you guys, I CAN get into fastboot, just don't know what to do after that.

Procedure
1.Turn your phone off. Turn it on by holding Back and Power, or Vol. down and Power. Either way, boot into the bootloader.
You should see the three Androids on skateboards, and the menu title should say "Fastboot".
2.Connect your device to the computer. The display on your phone should now say "Fastboot USB".
3.Open up the shell/terminal on your computer, and type
fastboot devices [enter]Your device should be listed with it's serial number, and should say "fastboot".
4.Change directory to where you have saved your recovery image. I.e. type "cd /path/to/recovery.img in windows prompt, press enter.
5.You may issue a "dir" command (Windows) or "ls" (Unix/Linux) to make sure you are at the right directory, or just skip this step.
6.Type
fastboot flash recovery recovery.img
Check your phone's display, as recovery is being sent and flashed to your device.
Check your command prompt/shell to make sure the process is over.

Hey, sorry for the late reply, plenty happing at home now. You said flash with the recovery image that I have saved. Do you mean the original recovery image...or....do you mean I can put on a custom one such as Amon Ra or Cyanogen?

sike89 said:
3.Open up the shell/terminal on your computer, and type
fastboot devices [enter]Your device should be listed with it's serial number, and should say "fastboot".
Click to expand...
Click to collapse
^^This doesnt happen^^
Any ideas?

Download FastbootCommanderV.1.5

[Q] Unbrick Samsung Vibrant after root and framework-res.apk replaced

UPDATE 2* FIXED!!!
I was following a tutorial on applying a LauncherPro theme and did the following command in terminal as super user:
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
I was expecting it to prompt me for the overwrite, but it did it without prompting and then started giving me not responding errors. Then I held down the power on the phone to reboot it and now it won't get by the initial "Vibrant" screen. I backed up my rom with Clockwork and also copied the framework-res.apk to framework-res-bak.apk before doing the final command.
Is there any hope for me?
UPDATE:
After plugging in my phone to my computer with ODIN running, I get the "Downloading... Do not turn off Target!!!" screen. Is there any way I can use this to salvage my brick?
*UPDATE2:
I wish I could give more specific details, but I'm not entirely sure what I did. I was following instructions on using ODIN (holding volume down and power) while also plugging my phone in via USB (have the drivers installed) and pulling and replacing the battery when all of the sudden, the Clockwork boot loader (is that right? the screen with the green text that lets you choose a command with the volume keys) pulled up. I then followed the instructions for loading the rom from anomalous3 (forum [dot] xda-developers [dot] com/showthread.php?t=743506) and got my deodexed rom reinstalled. Then the phone booted up ok.
UNBRICKED!

stupid reason to take back evo to get an epic?

cause the newest evo's arent rootable? lol i just got my evo yesterday and ive searched everywhere that the newest hboot 2.02 and 3.30 cant get rooted? the evo is pretty good but im all customizations. i read that the epic is super easy to root.

It can be rooted you just have to work harder at it. Dont take it back you'll regret it.

Clearly you haven't done any searching in the Android Development section.
But that's OK. Go ahead and get an Epic. Enjoy your screwed-up GPS and all that, and make sure to change your password on here to something you won't remember, so we never have to see you again.

mainguy21 said:
cause the newest evo's arent rootable? lol i just got my evo yesterday and ive searched everywhere that the newest hboot 2.02 and 3.30 cant get rooted? the evo is pretty good but im all customizations. i read that the epic is super easy to root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=829045
there you go. Just follow the directions and make sure you use the correct file locations.

real problem
What he really meant to say is . I am 16 and have Attention deficit hyperactivity disorder and cant bother myself to use the search button above me nor can i follow simple written instructions on rooting phone . If it dont have one click root i wont do it ........ i have both phones and the devs on evo are much better

thats funny i just typed in the search bar root evo hboot 2.02 and the first thread was the guide on how to do it.
@op if you are going to lie about searching the forum do it somewhere else. we know when a search isnt performed.

mainguy21 said:
and ive searched everywhere
Click to expand...
Click to collapse
Sure you have, buddy... sure you have.

ohhhhhhhhhhhhhh

You have been misinformed due to stupid people making stupid and false posts such as this one:
http://forum.xda-developers.com/showpost.php?p=9578042&postcount=8

Kingmac38 said:
What he really meant to say is . I am 16 and have Attention deficit hyperactivity disorder and cant bother myself to use the search button above me nor can i follow simple written instructions on rooting phone . If it dont have one click root i wont do it ........ i have both phones and the devs on evo are much better
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I am 20 and have ADHD and search is my best friend plus I've followed many rooting guides successfully so op has no excuse

Second that my girls epic is a pain in the ass and she kinda of.wish she got my phonr instead
Sent from my PC36100 using XDA App

thanks for help even though i searched everywhere.
but since i cant root my phone im stuck in the middle of it with a red triangle can i atleast go back to my phone? like unroot or something even though i didnt get all the way to root? please thanks

Follow these revised instructions from illogos pg 121 of hboot 2.02 root guide and everything should work. I've already rooted two hboot 2.02 hw 004 and in process of doing another one now. Everything works just fine if you understand and follow the instructions. Anyways, this was a lot simpler than the old school toast part 1 and 2 root methods so acquire some knowledge so you can someday help others and not be such a newbie.

thats what i followed and im still stuck at steps 10-11..my phone says in bootloader its "s-off" but i cant get that file to read after rebooting. ive tried over and over from the start and nada i even downloaded the file like 5 times.

mainguy21 said:
thats what i followed and im still stuck at steps 10-11..my phone says in bootloader its "s-off" but i cant get that file to read after rebooting. ive tried over and over from the start and nada i even downloaded the file like 5 times.
Click to expand...
Click to collapse
Which instructions though? Please follow these ones by illogos-
illogos said:
1. Make sure that you downloaded and installed HTC Sync from HTC website.
2. Unzip hboot202-s_off-V8.zip to a folder in your C: drive. I used C:\hroot
3. This hroot folder should have a folder inside it called root. If you have a folder called hboot202-s_off-V8 then you need to move all the files from that subfolder to c:\hroot.
4. In Vista/7 slick on the start button and type in cmd. You will see in the program list the command prompt. Right click and open as Administrator.
5. In the command prompt type cd c:\hroot
6. On phone goto-> Setting>Applications>Debugging make sure usb debugging is on.
7. Connect the usb cable to your computer and phone. The phone should change it's screen to ask you what type of connection mode you want. Make sure that it is on charge only. Do not mount.
8. Type into the command prompt: adb push root/unrevoked-forever.zip /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
9. Type into the command prompt: adb push root/mtd-eng.img /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
10. Type into the command prompt: adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
11. Type into the command prompt: adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
12. Type into the command prompt: adb push root/flash_image /data/local/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
13. Type into the command prompt: adb push root/rageagainstthecage /data/local/tmp After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
14. Type into the command prompt:adb shell You should see a $, this means that you are "in" the phone.
15. Type into the command prompt:chmod 0755 /data/local/tmp/rageagainstthecage You should see this echoed on your screen. This is normal. You should still have $ on your cmd line.
16. Type into the command prompt: chmod 0755 /data/local/flash_image You should see this echoed on your screen. This is normal. You should still have a $ on your cmd line.
17. Type into the command prompt:./data/local/tmp/rageagainstthecage A message will pop up on the screen. It will take a few seconds, and your will be kicked "out" of the phone. The $ should now be gone.
18. Type into the command prompt: adb shell You should have a # on your command line instead of a $. # means you have temporary root in your phone. If you do not have #, then start over.
19. Type into the command prompt that has #: ./data/local/flash_image misc /sdcard/mtd-eng.img
20. Type into the command prompt that has #: sync
21. Type into the command prompt that has #: reboot bootloader
22. Your phone will be rebooting now. Eventually your phone will be at the bootloader menu. On your phone use volume up/down to highlight bootloader and press the power button once. It will start loading the PC36img.zip file.
23.After it loads, it will ask if you want to flash. Press Volume UP to say yes. It will now flash, which can take some time. You may see some red fail messages. This is normal.
24.When it is done flashing it will ask you if you want to reboot. Press Volume Down to say now to reboot.
25. Use volume up/down to highlight recovery. Press the power button once. This will try to boot into recovery mode but fail and load a screen with a red triangle. This is normal because you have not installed recovery yet.
26. Go back to your computer screen and your command prompt. You should not have a #
27. Type into the command prompt: adb push recovery /
28. Type into the command prompt: adb shell busybox --install /sbin
29. Type into the command prompt: adb shell nohup /sbin/recovery &
30. After a pause you should see a new screen on your phone. It should be green text with your recovery options.
31. Highlight backup/restore. Press the power button. Highlight backup nand and press the power button. Press the power button again to confirm the action. Your phone is now doing a nandroid backup. This will backup your wimax keys amongst other things.
32. It will take a little time to do the backup. After it is done press the power button once to return to the recovery menu.
33. Highlight enable USB-MS and press the power button.
34. On your computer, you should see a new drive in my computer or a pop up asking you for an action. Click on Explore, or open the drive in my computer, to access your phone like you would a thumb drive.
35. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip
36. On your phone, press the power button to disable USB-MS mode. You should be back at the recovery menu.
37. Highlight the option to flash image from zip. Press the power button.
38. Highlight unrevoked-forever.zip and press the power button. Press the power button again to confirm if told to do so.
39. When it completes flashing the image, select reboot from the menu.
40. When it reboots a few things could happen. If you think your phone is frozen, you are okay because that is a normal occurrence on this step.
----->Your phone gets "stuck" on a white screen with the word HTC on it for more than a minute. You need to take the back case off your phone and pull your battery out. Put the battery back in and put the back case on again. Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->You phone started up and fully booted. You need to completely power off.Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->The phone returns to the boot loader.
41. No matter which of the 3 scenarios occurred to you in the last step, you are now in the boot loader. Obviously the 3rd scenario is the best, but all are OKAY.
42. The phone should find PC36img.zip. It then loads this file and asks if you want to flash. Use volume up for yes. When it asks to reboot press volume up for yes.
43. When it is done booting, return to your computer screen and type adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip into the command prompt.
44. Type into the command prompt: adb reboot recovery
45. Highlight backup/restore in recovery and then press power. Highlight backup nand and press power. Press power again to confirm. Wait for the backup to complete.
46. Press power to return to recovery menu. Highlight reboot phone and press power.
47. Your phone is now rooted, S-OFF, and booted into stock 3.30.651.2.
-------------------------------------------------------------------------
After Root:
1. Run through setup and get to the actual phone screens.
2. Try to turn on 4G/wifi/etc and see if it all works. It may not and this does not mean disaster.
For me, I had to flash Stock RUU root 3.30.651.3 to get 4G to work. Here is what I did next:
1. Download stock RUU root 3.30.651.3(I opted for Odexed version) from http://forum.xda-developers.com/showthread.php?t=836728
2. Reboot phone into recovery by completely powering off. Hold down volume down and press power. When you get into the boot loader it will try to find PC36img.zip and fail (we renamed that file remember?) and that is normal. Use volume up/down to highlight recovery and press the power button.
3. In recovery highlight USB-MS and press power to enable.
4. Your phone should be mounted as a drive in your computer again like before. Copy the whole zip file that you downloaded for RUU 3.30.651.3 rooted odexed to your phone. Wait for it to finish the transfer.
5. On your phone press power to turn off USB-MS mode.
6. On the recovery menu highlight wipe and press power.
7. Highlight the first wipe option which is something like wipe cache/factory reset. Press power. Press power again to confirm if needed.
8. Hightlight the second wipe option which is wipe cache. Press power and then press power again if needed.
9. Highlight the third wipe option which is wipe dalvik-cache. Press power and then press power again if needed.
10. Return recovery menu.
11. Hightlight flash image from zip and press power.
12. Highlight the file that you just transfered over that is for RUU 3.30.651.3 and press power. Press power again to confirm if asked. It will start flashing the image to your phone, but you will not see progress bars. It will take a few minutes.
13. When it is complete select the option to reboot the phone.
14. The phone should fully boot up into the stock rooted 3.30.651.3 rom.
15. Now try to turn 4G/wifi/etc on and make sure it works. It did for me.
16. Assuming that everything is working fine, fully power off, boot into recovery, and do another backup. This newest backup is your holy grail backup. It is stock rooted S-OFF and 4G working backup.
Note: these last 15 steps can be used to flash any custom rom too. Just make sure that you get your "holy grail" backup first before you experiment.
Click to expand...
Click to collapse

my wife got an evo on black friday from radio shack and i rooted it with unrevoked in like 5 minutes.

I have adhd... I wonder if 4g transmissions cause an increase in autistic spectrum disorders!?!?
Sent from my PC36100 using XDA App

animal7296 said:
It can be rooted you just have to work harder at it. Dont take it back you'll regret it.
Click to expand...
Click to collapse
he wouldn't regret getting the epic, it's a cool ass phone. if you want a crisper lcd and a keyboard get the epic.

fixxxer2008 said:
If you want a cheap-ass plasticky POS, get the epic.
Click to expand...
Click to collapse
Fixed that for you.

tejasrichard said:
Fixed that for you.
Click to expand...
Click to collapse
Thank you. It seems all these Samsung phones feel like garbage. Way too flimsy. Now I have a friend with an LG Optimus S which I just rooted for her, and I have to say the build quality is very nice.

Install rom via adb (center button broken)

My hero buttons are failing so now my home button does not work and my click ball button does not work. I want to install CM7 but I can't do it since I cannot select wipe/install from recovery since my click ball does not work. Is there an easy way to wipe and install using adb? Thanks for the help

Look up fastboot install..or wait for someone to point you in a more specific direction haha. I don't have time to look for something exact right now
Sent from my Hero using Tapatalk

I'd use adb to flash Amon_RA's recovery since it lets you use the volume keys and receive call button to substitute for the trackball.

MongooseHelix said:
I'd use adb to flash Amon_RA's recovery since it lets you use the volume keys and receive call button to substitute for the trackball.
Click to expand...
Click to collapse
Worked great until i had a bad flash. Now I cannot select recovery from the bootloader since my home button does not work.
Anyone know how to get into recovery if the home button does not work?

Using adb:
Code:
Adb reboot recovery
Sent from my HERO200 using XDA App

adb reboot recovery
Locked & Loaded

Thanks
10char

keep getting device not found. I am plugged in, switched to fastboot. Device manager has ADB interface --> HTC Bootloader.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb.exe shell
error: device not found
Any thoughts?

Got it. Nevermind.

[Q] cLK Fastboot Ignores that Recovery is Installed

Hi guys,
First, I'd like to point out this is my very first post here! And nice noob video, very entertaining
Anyway, before I get yelled at...
I've looked everywhere on this website for a solution, and nothing has worked, and I know there are many people with the same problem. This isn't a Noob question (though I'm not a tech savvy,) but rather a deep mystery that's frustrating.
Have you ever had a time where you do exactly what you've been told, yet you don't get the results expected? Well this is precisely the same thing.
I'm using a T-Mobile HTC HD2 and I'm trying to install a custom Android NAND ROM on it, with cLK as the bootloader.
Whenever I try running CWM through cLK (held the home button as phone rebooted), it goes and stays on fastboot as if CWM was never installed (which I'm sure I did.)
Actually, it doesn't ignore the installed CWM completely, because if I boot with the home button held, as opposed to not, I notice some extra lines in the bootloader..
I'm gonna copy down exactly what is on my HD2's screen right now (even though I could be wasting my time. But just in case .) My phone is connected to my computer via USB at the moment.
I bolded the lines that caught my eye, though I don't know what to do about them:
cedesmith's LK (CLK) v1.4.0.1
[180] 4.0.1
[180] boot reason 6
[180] android reboot reason 0
[180] load address 11800000
[190] flash init
[190] nandid: 0x5551b3ad maker=0xad device=0xb3 page_size=2048
[200] spare_size=64 block_size=131072 num_blocks=8192
[200] nandcfg: aad40000 6744e (initial)
[200] nandcfg: ea5400c0 6744e (used)
[200] ptn 0 name='misc' start=00000219 len=00000008 end=00000221
[200] ptn 1 name='recovery' start=00000221 len=00000028 end=00000249
[200] ptn 2 name='boot' start=00000249 len=00000028 end=00000271
[200] ptn 3 name='system' start=00000271 len=000004b0 end=00000721
[200] ptn 4 name='cache' start=00000721 len=00000028 end=00000749
[200] ptn 5 name='userdata' start=00000749 len=000017f8 end=00001f41
[210] flash_read misc partition
[210] flash_read: misc 800 800
[700] flash_read_image: failed (511 errors)
[700] ERROR: Cannot read recovery_header
[700] flash_read: boot 0 800
[2330] flash_read_image: failed (2560 errors)
[2330] ERROR: Cannot read boot image header
[2330] ERROR: Could not do normal boot. Reverting to fastboot mode.
[2340] USB init ept @ 0x28023000
[2380] fastboot_init()
[2380] udc_start()
[2380] -- suspend --
[2500] -- reset --
[2500] -- portchange --
[2670] -- reset --
[2670] -- portchange --
[3020] fastboot: processing commands
Click to expand...
Click to collapse
I'm REALLY sure I did the install-Android-into-HD2 process correctly. But I'll tell you guys everything I did:
1. I downloaded HD2 Toolkit (4.1), which a lot of people had success installing their ROMs with.
2. I then installed HD2 Toolkit using its setup program on my computer.
3. Then, opened the HD2 Toolkit on my computer.
4. Afterwards, I clicked the Wipe (Task29) button located on the lower right of the Toolkit.
5. I connected HD2 device to my computer through its USB cable.
6. I immediately hold the Volume Down button on the device as it automatically boots up (because that's what happens when I connect it while it's shut down.)
7. Multicolored screen (red, green, blue, then white) shows up on my HD2's screen.
8. On it, it says that I have HSPL 2.08 installed (yes, unmistakably HSPL, not SPL.)
9. I turned my focus back to the computer, and continued with the Wipe process.
10. The HD2 showed a progress bar and I waited until it reached 100%, and rebooted by itself. I help the Volume Down button once again in preparation for the next step.
11. Once I was finished with the "Wipe (Task29)" process, I select the "cLK repartition" button at the top of the Toolkit window, which was the next step.
*This button both installs and repartitions cLK, I don't know what that means but that's what it said on the Toolkit's thread.
12. I then chose "150 MB" inside the selection box labeled "Choose System Partition Size (cLK)."
13. Directly below the same box, I check the 5MB below a label "Cache Size."
14. I then click Install to finally begin the cLK installation&repartition process.
15. With the multicolored screen already shown up on my HD2, I began the 2nd process.
16. Just like the "Wipe (Task29)" process, no confusion occured. The similar-looking progress bar as earlier reached 100%, and the device reboots once again. This time, I DIDN'T hold the Volume Down button but held the Back button, as it's cLK's fastboot's turn to do its job (which means no multicolored screen this time, just white text on a completely black background.)
17. I take a glance at my device. The USB cable is still connected.
18. Turning my focus back to the computer (Toolbox once again, to be exact,) I click on the "cLK Install Recovery," confidently predicting that nothing will go wrong, because I followed all the steps, so far, without any confusion.
19. A command window pops up (on my computer,) and tells me to press a key to begin the CWM Recovery installation process.
20. I press the spacebar button.
21. The installation process begins.
22. In under 5 seconds, the process is finished, and the command window tells me to press any key once again to reboot my phone.
23. I press the spacebar button once again, and the command window closes on its own, and the phone reboots.
24. At the same time, I start holding the home button on my device (the tutorial mentioned that doing that while it's rebooting will launch CWM Recovery)
25. To my surprise, the set of lines above (in the quote) with the errors happen. CWM Recovery was never launched.
This is all the details I can think off that I can give you. The device handles a Custom ROM with MAGLDR 1.13 just fine, so I don't think anything's broken on my device.
Can anyone solve my little problem I got going on? Thanks a bunch

maybe an issue with the toolkit
personally i just just fastboot to install CWM

It's not a toolkit problem
I attempted to reinstall cLK once again (after Task29) using a couple more tutorials that I found in this website. I noticed these tutorials were all very similar, they all basically told me to install the same things the same way as I did the first time, but I still end up in the same fastboot rut.

then its something you are doing wrong
download the fastboot adb drivers
restart the phone in fastboot mode
flash using the fastboot flash recovery command

Richy99 said:
then its something you are doing wrong
download the fastboot adb drivers
restart the phone in fastboot mode
flash using the fastboot flash recovery command
Click to expand...
Click to collapse
The fastboot adb drivers?
I saw a google-usb_driver folder or zip in the tutorials, and I installed them through the "android_winusb.inf" file within them, if that's what you mean?

yes that zip, boot the phone into fastboot mode and then use the command promt to use the fastboot commands

I remember trying that once when I was going through other tutorials. Anytime I typed a command in for it (after Shift+Right clicking in the folder where the recovery img file is and click "open command prompt here") it'd say something like "there is no external fastboot connection" or something like that.
I don't know the exact words, but maybe that relates to the first current problem I'm having.
Two tutorials suggested that cmd method, and both times the same "there is no external connection" message would show up on the cmd. Again, I paid a lot of attention to those tutorials, and there were two of them. Nothing was too complicated to understand, so I'm absolutely sure I haven't messed up in following the steps, at least.
I also saw somewhere it might be a radio problem, so I downloaded two radios and experimented with them both. For each of them, nothing was fixed. (I tried 2.07.50.27_2 then 2.09.50.29_2) So the same fastboot problem persists.
EDIT: Is there a command on cmd to make fastboot go to recovery without pressing the home button?

the home button is for CWM and back arrow boots it into fastboot mode, afaik the phone cannot be put into fastboot mode without this method
it sounds like the drivers are not correctly installed if it is failing to find the phone if you are getting a conenction error
your radio has to be 2.08 and above for android to work properly from what i have read

I am also facing the same issue. Phone is HD2 and was working earlier with MAGLDR but it got corrupted and could not load android so decided to switch to cLK.
when try to load into CWM by holding the home button it loads with one error. As mentioned in the first post the first error but not the second one. Then it just reboots itself again but never goes into the recovery.
I used fastboot to flash the recovery and got the success message on the PC screen and also the phone gets rebooted everytime i try to reflash the recovery.
But when i type the command
fastboot devices
nothing is displayed.
It seems like the device is not connected then how come the recovery is flashed from the fastboot menu.
I checked in the computer management- devices and I see the Android phone without the "!" mark signifying that the fastboot drivers are installed properly.
Please help.
Got it resolved. Used HD2 toolkit to flash the cLK recovery.