Develop Bugs

[help] HTC Desire Can't Enter Recovery Mode and Clockworkmod

Hi guys, i am a newbie here.
Last night i was trying to root my desire using unrevoked. I followed the guide from XDA step by step and everything seemed fine until word "done" appear in unrevoked.
After that, desire supposed to enter recovery mode and clockworkdmod but there was nothing appear in the screen. My desire suddenly shut down.
Can you tell me what am i suppose to do then because i want to put custom rom in my desire and now there's nothing i can do because it can't enter recovery mode (it only able to enter bootloader or Android OS itself).
Thanks

kyosiro said:
Hi guys, i am a newbie here.
Last night i was trying to root my desire using unrevoked. I followed the guide from XDA step by step and everything seemed fine until word "done" appear in unrevoked.
After that, desire supposed to enter recovery mode and clockworkdmod but there was nothing appear in the screen. My desire suddenly shut down.
Can you tell me what am i suppose to do then because i want to put custom rom in my desire and now there's nothing i can do because it can't enter recovery mode (it only able to enter bootloader or Android OS itself).
Thanks
Click to expand...
Click to collapse
when you are in boot loader, use the volume down key and goto recovery and git power button. you should then be taken to clockwork recovery. this is where you can select your rom from SD card and flash

I've tried to do that and now it stuck in HTC Logo. Doest it mean i've to try unrevoked again or simply unroot it?

try rebooting by taking battery off. i'm not an expert but you might have to do it manually using the guide http://forum.xda-developers.com/showthread.php?t=696189
did you install the unrevoked drivers?

Okay i will try. Btw, in case i want to unroot, can you tell me where i can get "RUU_Bravo_hTC_Asia_WWE_1.19.707.7_Radio_32.36.00.2 8U_4.06.00.02_2_release_126179" ? The link from XDA seems down and i can download any.

Me and another member have encountered the same issue, seems there's some bug in HBOOT or something.
Boot into Android, go to Settings > Privacy > Factory data reset. Once you confirm it, it will reboot your phone into Recovery.
BUT, unless you re-format (partition) your SD Card, you won't be able to get back in again (unless you do the Factory data reset again).
This seems to happen randomly. Right now I can get into Recovery just fine. But once the bug occurs, the only way to get it to stop is to format your SD card.

Now i am thinking to unroot it than trying to do the whole rooting step all over again. Can you tell me where i can get the RUU for HTC Desire Asia

kyosiro said:
Now i am thinking to unroot it than trying to do the whole rooting step all over again. Can you tell me where i can get the RUU for HTC Desire Asia
Click to expand...
Click to collapse
Here you go:
http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_126179_signed.exe

Okay, i've done unrooting with HTC Desire RUU Asi and what happen now my SLCD is brick. I am really hopeless right now because guide for "SLCD Brick" doesn't even work in my phone because once again my htc can't enter recovery mode ><
"I am trying to use the guide from sprinker right now. Hopefully it will work"

when you are in hboot the volume down/up button work?

Hi all,
I also have the problem that I can no longer enter the recovery mode on my desire.
Basically, whenever I am in the bootloader menu (either by pressing vol-down+power, return+power, or via ROMManager) and then select "recovery" I get right back to the "fastboot" screen.
I tried uninstalling/installing/upgrading ROMManager and also tried flashing clockwork via the newest version of Unrevoked (downloaded yesterday).
Nothing helps :-(
What I didn't try, yet, is reformatting my SDCard or resetting my device via "Settings > Privacy > Factory data reset". (I don't want to install all my apps >again<; I'm also a bit afraid that I break something an then cannot even reflash using recovery).
Here is some more info about my device:
- Flashed rom: Leedroid 2.1a
- HBOOT 0.83.0001
- RADIO 5.10.05.23
I would be really greatful if anyone had a solution for this problem.
P.s.: in case I HAVE to reset/format: can I somehow make a backup of all my apps&settings?

Hi all, I have the same problem now.
Everything works, after s-off, except I can no longer enter Recovery - any solution?

I didn't find an easy solution. I had to do the following (some steps might be optional but I wanted to be sure):
- Formated SD card (ext3 and fat partition)
- Complete reset via RUU (RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32U_4.08.00.09_release_137222_signed.exe)
- Using unrevoked to reinstall recovery rom
- Reinstalled my custom rom (Leedroid)
Now everything works.
BTW: via TitaniumBackup I could backup all my apps and data quite easily. Didn't expect it to work that well

thanks- what about s-off - is it working now for you?

"s-off" = ?

I Have a similar problem... I can't enter recovery. When i press "recovery mode", I just get a black screen with a phone and a "!" in it.
Have to pull battery to reboot desire.
I have formatted sd.
Quite annoying, cause I need to wipe my battery stats, and I don't know any other way to do it, than going to recovery.

I tried to update ROM to Cyanogenrom which was unsuccessful - just get boot loop.
I also get the same 'red triangle with exclamation mark on phone' icon when trying to go to recovery mode.
So now I have a Desire which boot loops and cant enter recovery mode ...
anyone know how to get out of this one?

This might work for you
WAIT, BEFORE YOU START, CREATE A GOLDCARD. IT IS VERY NECESSARY. THINGS WILL GO WRONG IF YOU DONT.
YOU MUST BE ABLE TO BOOT GO TO THE BOOTLOADER MENU.
Firstly, download this file. http://dl.dropbox.com/u/13240777/Desire Downgrade.ZIP
Extract the files.
Run the win-down.bat file.
Follow on screen instructions.
After the process is completed, Head to the root of your SD card and check if there is a file named P99***IMG (FORGOT THE EXACT NAME BUT IT SHOULD BE SOMETHING LIKE THIS) there should be one.
Secondly, disconnect your phone and turn it off.
After that boot up your phone while pressing the volume down button and the power button.
The bootloader should be checking for files after awhile and once it found the file that is supposed to be in the root of your sd card, press the volume up button (NOT EXACTLY SURE, SHOULD BE THE ONE THAT SAYS YES AND CONTINUE)
It should be writing files to your phone. and replaces everything. E.G: HBOOT, RECOVERY,RADIO and such.
It should be writing files successfully and then it would ask you to reboot. Continue with the reboot and you should be having your Desire back to stock. Perfect.
PLEASE KEEP IN MIND THAT THERE ARE RISKS INVOLVED LIKE FAILURE OF WRITING TO THE HBOOT. PLEASE REMEMBER TO FOLLOW INSTRUCTIONS. MAINLY, DO NOT BLAME ME FOR ANYTHING THAT GOES WRONG.
FINALLY, YOU SHOULD BE READING EVERYTHING UP TO HERE AND THAT YOU MUST HAVE A GOLDCARD (A GOLD SD CARD)
Hope this helps you and please ask if you have further questions. PM me if the questions cannot be answered here. Good Luck
This should bring back your phone to stock. Root your phone again after it is done

i have the same issue. but i got stuck when trying to partition my sd card. Now i can't enter Android itself only the bootloader. But i also lost my clockwork recovery...
it keeps looping the HTC Quitly brilliant bootscreen... Forever!
i am now formatting my sd card with my pc. will i then be able to go into recovery again using a zip file from clockwork i found? using this:
fake-flash
Fake-flash is only possible with root access, you need to be rooted to use it. Basically, its a way to have recovery running on the phone without using a PC (making it safer as you are less likely to brick using no USB cable to push files, instead, you push directly from your phone). You can use "ROM Manager" from the marketplace to do this. Simply place the downloaded test recovery image on the phone and the downloaded rom zip (renamed to update.zip) and flash using ROM Manager.
Preperation
Download the fake-flash update zip from one of the links below
Copy the update.zip to the root of your SD card (the name MUST remain as update.zip)
When you want to launch the recovery image
Turn on your device with 'volume down' pressed and select 'Recovery'
When the exclamation mark appears, press and hold 'volume up' then press 'power'
Select the second option, 'Apply sdcard:update.zip
That's it, ClockworkMod recovery should launch!
Click to expand...
Click to collapse
and then installing a ROM with it?
(sry for bad english)

i'm having the exact same problem. i've tried fake flash and it does nothing for me, so does flashing the clockwork recovery image. the only one i haven't used yet is the downgrade...hope that will help

[Q] System dead, I can't enter even in recovery mode...

Hello Guys...
I've write about my problem in a thread title...
What can I do? : ((
P.S. RMA is impossible...

Can you Enter Hboot? (press volume down+power on)

A bit more details of your problem would be much helpful.

sorry to use this thread for my problem but I thought it's not necessary to open a second one with the same problem.
I can't enter recovery or boot into OS. It freezes at the splash screen. I tryed to flash a new recovery via fastboot but it didn't help. So I'm going to try to install an official ROM and redo the other stuff to get root again.
My problem is ... is unrevoked able to give me root no matter which hboot comes with the official rom? I have to install the one which is on the o2 homepage. HTC Desire: Version 2.14.207.1
I googled a bit and found answers that it doesn't matter which hboot I have after that but I just want to make sure.

Peikko said:
sorry to use this thread for my problem but I thought it's not necessary to open a second one with the same problem.
I can't enter recovery or boot into OS. It freezes at the splash screen. I tryed to flash a new recovery via fastboot but it didn't help. So I'm going to try to install an official ROM and redo the other stuff to get root again.
My problem is ... is unrevoked able to give me root no matter which hboot comes with the official rom? I have to install the one which is on the o2 homepage. HTC Desire: Version 2.14.207.1
I googled a bit and found answers that it doesn't matter which hboot I have after that but I just want to make sure.
Click to expand...
Click to collapse
Quoting from CrimzonEyed above, Can you Enter Hboot? (press volume down+power on)

This might work for BOTH of you
WAIT, BEFORE YOU START, CREATE A GOLDCARD. IT IS VERY NECESSARY. THINGS WILL GO WRONG IF YOU DONT.
EDIT: YOU MUST BE ABLE TO BOOT GO TO THE BOOTLOADER MENU.
Firstly, download this file. http://dl.dropbox.com/u/13240777/Desire Downgrade.ZIP
Extract the files.
Run the win-down.bat file.
Follow on screen instructions.
After the process is completed, Head to the root of your SD card and check if there is a file named P99***IMG (FORGOT THE EXACT NAME BUT IT SHOULD BE SOMETHING LIKE THIS) there should be one.
Secondly, disconnect your phone and turn it off.
After that boot up your phone while pressing the volume down button and the power button.
The bootloader should be checking for files after awhile and once it found the file that is supposed to be in the root of your sd card, press the volume up button (NOT EXACTLY SURE, SHOULD BE THE ONE THAT SAYS YES AND CONTINUE)
It should be writing files to your phone. and replaces everything. E.G: HBOOT, RECOVERY,RADIO and such.
It should be writing files successfully and then it would ask you to reboot. Continue with the reboot and you should be having your Desire back to stock. Perfect.
PLEASE KEEP IN MIND THAT THERE ARE RISKS INVOLVED LIKE FAILURE OF WRITING TO THE HBOOT. PLEASE REMEMBER TO FOLLOW INSTRUCTIONS. MAINLY, DO NOT BLAME ME FOR ANYTHING THAT GOES WRONG.
FINALLY, YOU SHOULD BE READING EVERYTHING UP TO HERE AND THAT YOU MUST HAVE A GOLDCARD (A GOLD SD CARD)
Hope this helps you and please ask if you have further questions. PM me if the questions cannot be answered here. Good Luck

Can get to HBOOT, but dead end from there...

Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!

BigEdgar said:
Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
Click to expand...
Click to collapse
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.

cmlusco said:
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
Click to expand...
Click to collapse
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?

BigEdgar said:
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
Click to expand...
Click to collapse
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.

cmlusco said:
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
Click to expand...
Click to collapse
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?

BigEdgar said:
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
Click to expand...
Click to collapse
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?

BigEdgar said:
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
Click to expand...
Click to collapse
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...

BigEdgar said:
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
Click to expand...
Click to collapse
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Are you able to use adb now? If you can, i have another sugestion i came across in another thread. A guy said he could not access, format, or use his data partition. He claims he fixed it by adb pulling the file system from a working inc, and adb pushing the files to the borked inc, fixing it. If you can get adb to stay connected long enough to push the files it might be worth a try.

cmlusco said:
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Click to expand...
Click to collapse
Thanks again for the suggestions.
I tried that but it's pretty much the same results.
HBOOT--> Factory Reset --> Screen with green arrows --> Red triangle with Exclamation point --> - Power button + Up Volume to get to the System Recovery menu --> Reboot:
Phone hangs on the black/white "htc Incredible" splash screen
One other odd note - if I do this same factory reset process with the USB cable *unplugged*, the instead of hanging on the black/white splash screen, it just goes into an infinite loop (black/white splash screen --> HTC quietly brilliant screen --> droid eye --> back to the black/white splash screen). FWIW this isn't new behavior, I just forgot to mention it earlier. In fact this is what the phone started doing once Verizon pushed the OTA update that screwed up the phone in the first place (there are a number of threads on this over at HTC and VZW forums, but their solutions aren't working for me).
I think this thing is a brick. If anyone has any recommendations for tools that can be used to analyze the partitions on a phone that won't boot, let me know. Otherwise this thing is getting sold for parts : )

Ok, some more progress. Most importantly, I learned that adb has a shell! I obviously didn't RTFM well enough.
Anyways, with the shell I was able to verify that the partitions on the phone are accessible (at least from a Windows machine) and I can, in fact, write files to the device (using "adb push" to push files to /sdcard, for example). That's great as it proves that the storage on the device *is* accessible, but just not from CWM. I followed some instructions that I followed partially before (http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html) in an attempt to see if I could get S-OFF. This tutorial is nice because most of the actions are via adb and fastboot instead of using the UI on the phone, which I couldn't get to. I was able to do most of the work I needed to get S-OFF via adb instead of using CWM or some other recovery tool, which was key, since CWM always tells me that it can't read or write any partitions.
I was actually able to get Froyo installed and boot into it! That's the first time this POS has booted into anything in almost a month!!
Now to my current problem - the last few steps of the tutorial linked above require that I install superuser and unrevoked, and suggest that this be done via CWM. Unfortunately, CWM can't read any of my data partitions, so this doesn't work for me. Not many others seem to have this problem, so googling it doesn't turn up any help.
Is there any way I can use ADB to install superuser and unrevoked forever? I also have access to the UI via Froyo and could conceivably install apks as well.
Here are the instructions from the tutorial that don't work for me, as they rely on CWM:
******************
use the recovery menu on your phone to:
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-install zip from sd card(chose your forever file)
******************
Those last two steps - install zip from sd card - are the ones that completely fail for me. CWM just gives me a bunch of "E:can't mount /sdcard/" errors.
If anyone has any ideas on how to install superuser and unrevoked using ADB, I'm all ears : )
Thanks!

So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app

nschiwy said:
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?

BigEdgar said:
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
Click to expand...
Click to collapse
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.

cmlusco said:
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried this a few times and while Unrevoked is reporting success, I'm still S-ON and BusyBox and ROM Manager report that I'm not rooted. Back in CWM, CWM still reports errors mounting all drives and is basically crippled. In addition to the "can't mount SD card" errors, I'm also seeing "E:cant mount /dev/block/mmcblk0p2" and "E:Can't mount /cache/recovery/command". Weird. Can't tell if the mount errors are causing my inability to root or my inability to root is causing the mount errors.
(I also tried using AmonRa and got the same "can't mount" blah blah issues). Time for a drink : )

There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off

eljean said:
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
Click to expand...
Click to collapse
Eljean - that link's a 404...

I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app

eljean said:
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.

BigEdgar said:
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
Click to expand...
Click to collapse
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243

eljean said:
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
I appreciate the thoughts, but I think we're talking about different issues here. One of your issues seemed to be that you couldn't access the device at all via USB. I don't have that problem. My USB connection has always been fine. My problem is that CWM can't mount the SD card (or any other drives, for that matter). Everything mounts fine in Froyo, so I'm guessing it has to do with the way the drives are mounted in Recovery vs. Froyo.
The thread you referenced stated that the fix for not being able to access the SDcard was the fastboot oem enableqxdm 0 fix. I tried that a few times but it didn't make any difference.
Thanks for the thoughts!

Some assistance is requested

Hello there,
I'm slightly new to the forums, at least posting to them so if I'm in the wrong section or if I'm just not suppose to ask these questions... well... lend some expert advice and help me out!
I'm by no means an expert on rooting and flashing, pretty much every thing i have learned has been on my Optimus V, Nexus 7, and My latest device, HTC One V and i learned it all on these forums!
So my problem is... My HTC One V i have unlocked it and rooted it with a tool kit i found on here called "Hasoon2000's HTC One V All-In-One Kit" and all was well in the world. But now that i have rooted it I've grown bored with the device... after less than 24 hours of running stock rooted. And i've attempted to flash MIUI.us on my device as found on the developers website Now I've flashed many custom roms on my other devices, currently running Paranoid Android Beta 3 on my Nexus and Harmonia 2 (I believe) on my OV. But this phone has become quite the hassle. I'm running TWRP CDMA recovery and i Factory reset, wipe data, cache, dalvic (spelled correctly?) and it boots up to the MIUI boot logo then it goes to the usual Google start screen where you select language and set up your device... but... at that point it fails to do anything then boot loops back out and restarts the phone, and repeats... sometimes it won't even get out of the boot loop and it will just restart the phone... so i have used the RUU and reset the phone multiple times after this has occurred... If anyone could be of assistance or point me towards the correct forum it would be much appreciated!
I'm not totally sure what else could help anyone out there but it says S-OFF and i am unlocked and i have tried multiple roms and none of them have worked yet at all, the AOSP rom actually got to the home screen then restarted... this is getting quite frustrating and slightly irritating so if anyone could lend a helping hand I'd be much appreciative!

If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.

robaho said:
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
Click to expand...
Click to collapse
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV

the last OTA broke the Radio (-> v.0928) firmware
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
mkgarrod said:
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
Click to expand...
Click to collapse

master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Okay so I just wanna make sure i understand all this... I'm basically doing the same thing that the RUU does? What does the RUU do outside of this? and i tried what you said and it never notices it and now when i boot up my phone it has no service and doesn't connect to the network....

master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not

You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
mkgarrod said:
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
Click to expand...
Click to collapse

master_c said:
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
Click to expand...
Click to collapse
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..

You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
mkgarrod said:
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
Click to expand...
Click to collapse

master_c said:
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
Click to expand...
Click to collapse
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.

I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
mkgarrod said:
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
Click to expand...
Click to collapse

master_c said:
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
Click to expand...
Click to collapse
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?

It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
mkgarrod said:
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
Click to expand...
Click to collapse

master_c said:
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
Click to expand...
Click to collapse
Well as soon as i get back to my house I'm going to try this out and try reflashing the MIUI rom which is JB i believe and hope it works! if not... I'll be using that RUU tool again... I think i've been on that more than i have my new phone!

Why did no one report this thread? Obviously I'll see it eventually, but come on guys/gals!
Moved to Q&A.

boot loop for no reason, unmodified phone

Hello,
I am no expert but i usually fix problems, however this one keeps puzzling me for a long time now.
I own a wildfire, not modded, not modified in any way. One day I open a qr code app, it decides to freeze, so i reboot. (i think i had to remove the battery) It takes about 15min to boot, doesn't respond to any input and then reboots and the cycle continues.
I have looked into several solutions for the problem, but all require me to turn S-off. But to do that I need to turn on usb-debug, but to do that I need a bootable image!!!!
At first i wanted to mod, tried revolutionary to turn off S, but doesn't work because i can't turn on usb-debug.
Then i wanted to turn off S the HTC way, where they send me the code needed to unlock it, but it said i had to first update the RUU and guess what:
"To install the RUU, simply follow these instructions: On your phone, enable USB debugging. (..)"
I do not understand what i should choose from the RUU download page, but if it helps i am from Italy. I tried the program and this is the output:
C:\Users\*user*>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
I did all possible options the bootloader gives me: deleted all user data (losing most of my stuff i guess), I tried recovery too but it doesn't like the image. (which i have not touched or modified in any way)
specs:
BUZZ PVT SHIP S-ON
HBOOT - 1 . 01 . 0001
MICROP - 0622
TOUCH PANEL - ATMELC03_16ac
RADIO - 3 . 35 . 20 . 10
Nov 17 2010 , 12:08:53

stormsight said:
Hello,
I am no expert but i usually fix problems, however this one keeps puzzling me for a long time now.
I own a wildfire, not modded, not modified in any way. One day I open a qr code app, it decides to freeze, so i reboot. (i think i had to remove the battery) It takes about 15min to boot, doesn't respond to any input and then reboots and the cycle continues.
I have looked into several solutions for the problem, but all require me to turn S-off. But to do that I need to turn on usb-debug, but to do that I need a bootable image!!!!
At first i wanted to mod, tried revolutionary to turn off S, but doesn't work because i can't turn on usb-debug.
Then i wanted to turn off S the HTC way, where they send me the code needed to unlock it, but it said i had to first update the RUU and guess what:
"To install the RUU, simply follow these instructions: On your phone, enable USB debugging. (..)"
I do not understand what i should choose from the RUU download page, but if it helps i am from Italy. I tried the program and this is the output:
C:\Users\*user*>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
I did all possible options the bootloader gives me: deleted all user data (losing most of my stuff i guess), I tried recovery too but it doesn't like the image. (which i have not touched or modified in any way)
specs:
BUZZ PVT SHIP S-ON
HBOOT - 1 . 01 . 0001
MICROP - 0622
TOUCH PANEL - ATMELC03_16ac
RADIO - 3 . 35 . 20 . 10
Nov 17 2010 , 12:08:53
Click to expand...
Click to collapse
Hmmm. First off, have you tried to factory reset from recovery? If you boot into the recovery and then hold both volume buttons and power a usable menu should appear. Factory reset from there and reboot. See if that helps.
If not we turn our attention to your hboot. The error is because it is not updated enough to have that command. So we have two choices here. You can either upgrade the hboot, unlock your bootloader via htcdev and flash a custom rom. Or you could create a Goldcard, flash a ruu that has the same hboot as the one you have. This should fix your rom and enable the phone to boot again.
In any event you will need to extract the rom.zip from whichever ruu you choose. To do that have a quick google search for a guide but its easy enough. After that rename the rom.zip to PC49img.zip and place it onto your sdcard, boot into hboot and allow it to flash it. The golcard process should be covered in one of my downgrade threads or one of the others from this forum.
Post back here if your having and trouble or need a hand

heavy_metal_man said:
Hmmm. First off, have you tried to factory reset from recovery? If you boot into the recovery and then hold both volume buttons and power a usable menu should appear. Factory reset from there and reboot. See if that helps.
Click to expand...
Click to collapse
Yes, i forgot to mention: i have tried all options in the recovery (red triangle thing) too (clear cache, factory reset) nothing worked, it says: E:Can't open /cache/recovery/command
heavy_metal_man said:
You can upgrade the hboot, unlock your bootloader via htcdev and flash a custom rom.
Click to expand...
Click to collapse
To do this, i would need usb-debug enabled, so I think i cannot, but if there is a way please tell me!
heavy_metal_man said:
Or you could create a Goldcard
Click to expand...
Click to collapse
To do this i will need a micro-sd adapter to put my card into my computer, i will find one and try it out.
I also read that i need the correct RUU for my carrier. I am not understanding very well what i'm doing, also no idea what a RUU is or where to get the appropriate one for my Hboot and carrier, any advice ?

stormsight said:
Yes, i forgot to mention: i have tried all options in the recovery (red triangle thing) too (clear cache, factory reset) nothing worked, it says: E:Can't open /cache/recovery/command
To do this, i would need usb-debug enabled, so I think i cannot, but if there is a way please tell me!
To do this i will need a micro-sd adapter to put my card into my computer, i will find one and try it out.
I also read that i need the correct RUU for my carrier. I am not understanding very well what i'm doing, also no idea what a RUU is or where to get the appropriate one for my Hboot and carrier, any advice ?
Click to expand...
Click to collapse
All usb debugging is for is so that adb can reboot the device to hboot. If you google for how to extract the rom.zip from the ruu and then put it on the sdcard (after renaming it to PC49IMG.zip) and boot to hboot it is the same thing. Just without usb debugging needed.
You will need a micro sdcard adapter pal.

alright, after using the HTC dev method, i unlocked the phone, it still says S-ON but *** UNLOCKED *** on top, the HBOOT is now 1.02.000
after that i obtained the ClockWorkMod recovery img (i used version 5.0.2.0) and did in the terminal:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img

stormsight said:
alright, after using the HTC dev method, i unlocked the phone, it still says S-ON but *** UNLOCKED *** on top, the HBOOT is now 1.02.000
after that i obtained the ClockWorkMod recovery img (i used version 5.0.2.0) and did in the terminal:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
Click to expand...
Click to collapse
good stuff pal.
when you are in clockworkmod recovery the controls are different. use the trackball to scroll and select. power button is now the back button.
I would recommend this custom rom as it is stable and has a stock vibe to it. just follow its install instructions and you should be good to go

Thanks, after many trial and error i ended up asking my hacker friend and managed to install cyanide mod.
However the same problem which i originally had persists ( it is very slow to boot (when it boots) and it doesn't react to any input, at this point it must be a hardware problem. This makes me very sad, i thought i saved it..

stormsight said:
Thanks, after many trial and error i ended up asking my hacker friend and managed to install cyanide mod.
However the same problem which i originally had persists ( it is very slow to boot (when it boots) and it doesn't react to any input, at this point it must be a hardware problem. This makes me very sad, i thought i saved it..
Click to expand...
Click to collapse
That suck man.
Hmmm. Slow boot times are normal on this phone to a certain degree. Usually 20secs to 3 minutes at first boot aftet rom flash.
Once the phone has booted up does the trackball still work? Could just be a damaged digitizer. They are fairly cheap these days. Look here http://m.ebay.co.uk/itm/281644653982 and here http://m.ebay.co.uk/itm/281644653982 fairly straight forward to install, but you could buy a used version of the phone for £30 minimum so its up to you
Edit: although, on reflection 15 boot time and constant reboots are not a good sign. I was hoping it was a software issue. If the trackball is functional you could go into settings, enable usb debugging and then get a logcat. That would at least give us somewhere to work from :-/

the trackball is functional because i can use it in clockwork recovery! but the phone doesn't react to it after boot, it's like it's stuck, i don't think the issue is the touchscreen, it used to work fine, it must be something else.
boot time is about 5-6minutes now, but after that it's like frozen, and after a couple more minutes it reboots. A big improvement, now the bootloop period is at least 70% shorter! xD

stormsight said:
the trackball is functional because i can use it in clockwork recovery! but the phone doesn't react to it after boot, it's like it's stuck, i don't think the issue is the touchscreen, it used to work fine, it must be something else.
boot time is about 5-6minutes now, but after that it's like frozen, and after a couple more minutes it reboots. A big improvement, now the bootloop period is at least 70% shorter! xD
Click to expand...
Click to collapse
Lol! Well at least thats a plus :-/ theres not much else we can do here. We could try to enable usb debugging fron within clockworkmod by editing the build.prop and see if we can get a logcat but if the phones just locking up we might not even get one :-/