Develop Bugs

need help on cant open /cache/recovery/command

hi good day..
i was trying to update my rom to opendesire 3.1.1.. so i connected my usb cable and flashed it. but while wiping i had an error. it said cant open /cache/recovery/command. i just ignored it and then while i was trying to flash, my connection from my pc to the phone just got disconnected. so i restarted my phone and tried to flash again. but when i tried to run the recovery-windows.bat file, it just wont start.. i hope you could help me asap! thanks

another thing.. when i plug my phone to the pc it automatically lights up and it gets stuck on the htc logo..
help please.. thanks

ryanpaul said:
hi good day..
i was trying to update my rom to opendesire 3.1.1.. so i connected my usb cable and flashed it. but while wiping i had an error. it said cant open /cache/recovery/command. i just ignored it and then while i was trying to flash, my connection from my pc to the phone just got disconnected. so i restarted my phone and tried to flash again. but when i tried to run the recovery-windows.bat file, it just wont start.. i hope you could help me asap! thanks
Click to expand...
Click to collapse
hi, dont worry about that, I had it too now that you are trying to flash a ROM onto the phone, I am guessing that you are rooted.. to load a ROM you need a ClockworkMod. if you can still get onto your phone (call people and actually use the phone), get ROM Manager, you should see Install clockworkmod, or something like that, just let it download it and instll (don't interrupt!) and try going into recovery (vol down +power button, recover, then you should be able to use your track ball to navigate and install from SD, that worked for me )
pm me if you need further help

uhmmm.. i cant use the phone its stuck on the htc logo.. did i brick it? i tried to go to my cmd prompt ant tried to type in adb devices. it looked like this.
List Of adb Devices
it just blank i cant see my phone.. is it bricked?

UPDATE!!
1.i tried to root the device again but at step 2 i got stuck because the device wasnt found.
2. i thought it was usb bricked so i went to a page here in xda developers "[DEV] USB-BRICK FIX - Restore USB function on your bricked Desire". while i was getting my cid. it suddenly booted (i didnt do anything but set it into fastboot and typed 'fastboot oem boot') and it ran the stock 2.1 rom. so i tried rebooting into recovery but to no avail.. it still cant detect the device when i run the recovery-windows.bat
any ideas?

Unable to boot my htc desire help please!

Hello my name is Mike is there anybody who can help my to make my phone working again?! I dont even know where to start and how to explain what is going on! Honestly i ****ed up! Today everything working fine as ussualy on my HTC desire with 2.2 froyo which I instaled long time ago.. I decided to format phone thruu (volume down + power button) what I done was those actions ,,wipe data/factory reset'' then possibly formated system data cache i mean everything.. so now there is nothing on my SD card ... and I just realised I am stuck here as I dont know how to put system to my phone again as I am unable to boot to home screen which I am more familiar with..
After pressing power button now I can see following
BRAVO PVT1 SHIP S-ON
HBOOT-0.00.0000
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.09.0020
mar 29 2010,21:34:33
i can choose to bootloader,reboot,rebootbotloader,power down then i can got thru bootloader to recovery and there i can moving down up as I like I can mount sd card to pc whatever i want I just dont know what to do anyway.
Anybody who can help please I will appreciater any help.Thank you

Download this RUU:
http://shipped-roms.com/download.php?category=android&model=Bravo&file=RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Boot to fastboot holding the back button while you power on your phone. Connect phone to computer an run the RUU update.
If your device is branded you will have to use a RUU matching your operator.

Hello my tel is branded to Vodafone .. ANd one more think I am bit a retarded so I would aprriciate some more detailed guide how to instal u ment run that RUU from windows ? btw thank you
UPDATE I trayed your rom and its says Error 170 usb failure.. is it becouse of not Vodafone rom?

ERROR [170]: USB CONNECTION ERROR that what is says even after vodafone one RUU

No, it's an error on the USB Connection...

well its says FASTBOOT. As soon as I connected USB from pc its says FASTBOOT USB so usb might work.

Guys anybody? I am stuck without phone well my fault ;o) i know..

Tried turning off any antivirus/firewall?
Do you have htc sync installed? If not, try installing it.
Sent from my HTC Desire using Tapatalk

Hello Mikep I installed htc sync disabled firewall and anti virus.. HTC sync after i connected phone wont find phone it says no device connected, bu when i pugged that cable to phone and pc windows says HTS device driver installer corectly ...

Have you tried now running the RUU with antivirus/firewall off?
Basically, disconnect phone, boot into fastboot (power & back key), plug phone into PC. It should now show FASTBOOT USB or similar.
Then try the RUU.
Sent from my HTC Desire using Tapatalk

acctually something is going on it kight working i will update u after all of taht proces finish.

Please don't rush to unplug your phone tho!!
Sent from my HTC Desire using Tapatalk

u are perfect it is everything ok now here !!! Really thank you Mikep99!

No problem
A joint effort between all the previous posters I think
Enjoy!
Sent from my HTC Desire using Tapatalk

[Q] Did I brick my desire?

Hi.
I was recently experiencing some problems with my desire and I believe that I might have rushed into bricking it.
I woke up the day of the bricking. I had just installed the newest version of GingerVillain (version 2.4). My phone had run out of power the day before so I started recharging it. After it had charged for a couple of hours I went to the market to update some apps. During the update my phone suddently rebooted. I thought that it was nothing and went back to the market and continued updating. A few minutes later it rebooted agian. It kept on rebooting with less and less time in between after each attempt until it chose to reboot at the splash screen continuesly.
This is when I thought of starting the phone in recovery and do a NAND restore. As I tried to enter the recovery mode the phone froze at a black screen. I pulled out the battery and retried a couple of times without success.
I read a little on the internet about ADB and tried doing some stuff but I kept on getting errors when running commands in the tools directory. At this point I was getting desperate because I needed the phone to work as I was expecting an important call. I tried flashing a new RUU (through the installer on my PC) while the phone was in fastboot (but without using any ADB and CMD stuff). After this installation almost had finished I got an error saying that the version of the rom wasn't the right one for my phone and the phone shut off.
Since then I haven't been able to boot it into bootloader or even boot it at all. Whenever I hold down power + volume down nothing happends and if I try only pressing the power button the phone vibrates and other than that nothing else happends. Not even the screen turns on.
I since then set up ADB and got it working. I then tried to see if the phone was still able to fastboot through the following commands:
Code:
adb devices
and
Code:
fastboot devices
but found that this was not the case.
Whenever the battery is in the phone though, the bottom of the phone starts to get warm, a little like it's actually using the battery to perform some actions or something. I was also able to recharge it through my computer.
I really need a phone and as it seems I have got my hands on a spare one, but only for a limited time. I'm really thinking of handing it in to the HTC Concept Store so they can send it to the repair department and hopefully get it back as fast as possible.

Its seems.. S-LCD Brick
try This
http://forum.xda-developers.com/showthread.php?t=748498
or
http://forum.xda-developers.com/showthread.php?t=831734

Ohh dude! I BELIEVE YOU MIGHT JUST HAVE SAVED MY LIFE! TY! TY! TY! TY!
My stationary just killed itself because of the hot weather and a little bit too much work. If I was going to hand in my phone and they couldn't repair it since I had "destroyed" it, I would be forced to buy a new one, and with that I wouldn't be able to afford new components for my stationary.
I will get right on with trying this method as soon as I get home and then I will give feedback asap. It will probably be the most fun "digging in the dark" I will ever do if it turns out to work.
I was almost sure I had killed my beautiful phone, and with it only being a couple of months old that would have been a pain in the ass.
Once again TY so much!!

I have been at this for almost 4 hours now and still no result. I believe the guides could have been more noob friendly. I've been to hell and back reading all the kinds of guides out there to get it all to work and now I'm tired and believe I won't be able to fix this, or atleast doesn't have the capacity to keep on trying.
I pretty much believe that I had this SLCD-brick, but trying out different RUU's is killing me inside and stealing my time. I'd rather just hand in the phone and recieve it as it was from the beginning again to start all over.
Trying to repair a smartphone with a blackscreen is is not something I have the capacity to do. Besides I have my recently deseased stationary computer to take care of as well.
I do have a goldcard, pushed the PB99IMG.zip file to my /sdcard/ through adb and tried starting up fastboot and do as described here.
But somehow I did not find any changes to the problem and the guide itself was wierdly written although the only guide I could find on this problem.
But now I'm giving up. I seriously just hope they will repair my device at no cost.
Regards,
Me

Man.. what happen when you connect your mobile to PC.. is it showing android device and under that bootloader interface.. dont lose hope... lets try some steps...
connect your mobile to PC and see in your device manager.. can you see android.. if yes than your driver are installed...
than remove the phone from pc.. take out the battery.. and put back battery.. and start by volume down and power.. and than after 10 sec just press power button again.. and connect to pc again... and cehck device manager.. and you should see the same if not.. than install your adb driver.
Point is.. install ADB driver.. when you are on hboot screen.. as well fastboot screen..
Than your RUU will detect your phone.

Well I tried all the steps for this. I can see the phone when booting it with the following combos:
Code:
1: Volume down + Power
2: Power
1: Volume down + Power
2: Volume down
3: Power
When using the first method I should as far as I can understand myself enter fastboot and the other one is recovery. Even when running the fastboot devices / adb devices commands in ADB it tells me what state my devices in, that is either fastboot or recovery. So that's for certain.
I tried running the following RUU when I had connected my device with fastboot:
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
The RUU found my device and I ended up with a 140 Error. I read in some guide that this error could be to blame of different windows drivers so I tried grabbing the rom.zip from the RUU (from Temp folder) and renamed it to PB99IMG.zip and put it on the phone. As I couldn't get access to my SD card since I can't see what's on my screen in fastboot and recovery mode I used:
Code:
adb push PB99IMG.zip /sdcard/
with the PB99IMG.zip placed in my tools folder for the transfer. It completed and now the PB99IMG.zip should be placed on the root of my sdcard.
As a notice I live in Denmark and the above RUU should as far as I can understand be the one I need and should as well be SLCD compatible.
When I try to trace the steps in the "not able to see your screen guide" placed here I get none of the desired outcomes:
http://forum.xda-developers.com/showthread.php?t=880268
I find the guide a little but confusing though. When to use the right commands to trace through a black screen fastboot/recovery and stuff isn't really "noob"-friendly.
When I tried using the following command I didn't get the desired result either:
Code:
fastboot oem gencheckpt
Which should return a HTC_<number> that could tell me whether my phone is branded or not, but instead resulted in an error. As far as I can remember I did make my sdcard a goldcard when I rooted my phone, without knowing whether I would need it, so this number should be irrelevant. So I kept on going at this point.
I have basicly tried everything that I can find guides for and have traced all the steps in detail as far as I understand the guides anyhow. I feel like at a dead end. I am having doubtsg whether the PB99IMG.zip is run when I boot my phone.
Having a clean slate (but still the PB99IMG.zip on the sdcard I have now tried the following:
Code:
Volume down + Power
Windows reported a connected Android 1.0 device and the Android Bootloader Interface.
Power once more (should now be in fastboot)
fastboot devices
confirmed the above, but using ADB devices only return a result if the phone is in recovery mode
So far so good..
I'll give this one more day which will be when I return home at 17:00 today. Then I'll head to tech support at my HTC Store.

Good.. i think you should try this RUU
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
As error 140 is for wrong bootloader.. so try this RUU.. n try to run RUU from PC rather than putting PB99IMG into sd..

jhonybravo4u said:
Good.. i think you should try this RUU
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
As error 140 is for wrong bootloader.. so try this RUU.. n try to run RUU from PC rather than putting PB99IMG into sd..
Click to expand...
Click to collapse
Okay. I'll try this and should I run it while in recovery like I did with the other one?
Does it matter if my SD card is out of the phone?
EDIT 1:
I tried with the sdcard out of the phone and with the RUU installed through windows. I now see a HTC Logo on the screen.. and an installing bar below the logo.. Seems like you were my divine interception mate.. ty a lot. I will write once the installation is done.. whether or not it succeeds.
EDIT 2:
My phone is now working. Booted with HTC Sense and a pin code request. Currently setting it up.
I guess I should now be able to re-root it again and get back to the state I was in before I SLCD-bricked it.. or what?
And in what way do I easiest remove that PM99IMG.zip file from the sdcard..? I booted my phone without the sdcard in it to avoid it running the PM99IMG.zip file..
One little question more.. I don't have any phone signal.. could this be to blame for the radio? I can connect to wifi though.. or can I simply run that other RUU I used earlier with the bootloader error to get back my signal?
So happy right now..
EDIT 3:
Nvm. I tried shutting down the phone, put in the sdcard, boot it up again. I found that the ADB push command on that PM99IMG.zip file didn't work. The file wasn't there.. and I suddently got back my signal. Only question is, can I now re-root it again and get back to my previous state without any problems?

Yes Ofcourse you can re root it.. with Unrevoked rooting wont be a big problem... and as soon as you root... just take a nandroid backup from it and be safe..
Enjoy the victory you earned... .. ;-)

[Q][SOLVED] Rooted Desire NOT CHARGING and NOT CONNECTING TO PC

For solution see this
Hi guys...I've got Problem...
This is What it is and what I've Tried so far...
I've posted this Problem at may places but didn't got results..
That's why I am ceating a new Thread..Also there is no Q & A Thread for this..which have good info
Here is What i tried.. and still the NOT CHARGING/LATE CHARGING and HEAVY BATTERY DRAIN PROBLEM..
1. Firstly I had runnymede from seb15 AiOv2.2 installed..Working Perfectly..
(See my signature for my phone's every single detail)
2. I used 4ext recovery..(before cwm).. I go to the recovery.. took backup..done perfectly..
Than rebooted.."STUCKED ON BOOTSCREEN"
"I pulled out the battery ..
Restarted with power+volume down button..
4ext recovery started after long delay..
msg:
"Error mounting your sdcard
Please check your sdcard's fat32 partition for errors"
"Error mounting your sdcard
Please check your sdcard's fat32 partition for errors"
2times...
at the table it is showing as
sacard fat32(fs) null(size) B(Free)....
I removed sd card..
repartitioned by gpartedlive..
my sdcard is 8gb sandisk..partition are 1gb ext4...remaining fat32(Both Primary)
Reinserted sd card..
again rebooted in recovery..
again same message"
This was the starting of the problem..
Now Waht i did is
1.connected to PC and in cmd typed this
adb devices
fastboot flash recovery recoveryCWM.img
fastboot reboot-bootloader
fastboot erase cache
fastboot oem enableqxdm 0
and sussefully done..
2. In fastboot
again first step and added
fastboot eraseconfig
rebooted..
3. got SD card mounted
4. Flashed CynogenMod7.1.0(Worked perfectly..even the battery was charging good...everything Normal)
5. I rewiped everything and flashed runnymede AiOv2.2 again..
Here the problem started of Battery Drain and Not Charging.
6. The Battery was NOT charging firstly...Than started charging 5mins after plugged in..
7. Charging is 1% per 15mins..(Which was almost10% per 15mins)
8. Battery Drain almost 10% in just 15mins..
Now to solve this I searched xda and googled.. foind something and did following..
reflsahed the hboot.
By first downgrading and than upgrading to cm7r2..
3.In fastboot Reflashed recovery CWM 2.5.0.7 than upgraded to 4.xxxx(ext4 and 3 supportable)
Again installed runnymede AiOv2.2 again..SAME RESULTS..
Tried Revolution v2.0 ... SAME RESULTS(the Battery thing..explained above)
Now what you guys suggest me to do NOW... to get my desire in NORMAL CONDITIONS
Huge Thanks for "ckpv5" for the guidence for solving "ERROR IN MOUNTING SDCARD"
and lot more people on xda which i searched threads..
I again NEED HELP!!!
One more thing ...
The time I was re flashing the hboot.... I pulled out the battery..the phone was connected with USB... Kit was still on...by the power from USB only...means the power was not going through battery but directly....
Can this be the cause of late charging problem....and the battery drain...
it happened with your phone???? That you forgot to pull out the USB simultaneously pulled the battery out....
By the way I've tried changing kennels... No luck stool the same problem
Thanks for your kind help

tried a different battery? only logical explanation...
have you tried charging the phone while switched off? what happens then?
also if this is a software issue did you make sure to do a full wipe before you flashed a new ROM? (from mounts 7 storage)

bortak said:
tried a different battery? only logical explanation...
have you tried charging the phone while switched off? what happens then?
also if this is a software issue did you make sure to do a full wipe before you flashed a new ROM? (from mounts 7 storage)
Click to expand...
Click to collapse
I've tried it charging in switch off mode..but.. same result..
Try changing the ROM.. same Result... as u can see above I've tried almost everything....

dont expect any1 to help of you write post the way you just did.
well what happens seems to me like:
-you had USB brick (batt drain, charging issues, no USB connectivity)
-you fixed it with 'fastboot oem enable qxdm 0' and 'fastboot oem eraseconfig'
-you flashed a (corrupted?) rom file again, and got USB bricked once again.
so just do fastboot cmds once again and you should be good.
however if i didnt understand you correctly, blame yourself for it, cause i dont feel like reading the 1st post ever again.
over and out.

dzumagos said:
over and out.
Click to expand...
Click to collapse
What this means is "call me back and don't call me" LOL

Does Bluetooth work (ie. stay on)? If not then it's a USB brick. And I'm with dzumardgos, I almost didn't bother spending some of my hard earned time on you.
Note also that loss of access and repair of the SD card issue is something completely different to charging and PC connectivity issues (USB brick).

Will see you soon with the solution.
Sent from my HTC Desire using XDA App

What are the possibilities that a ROM can be corrupted..Please mention..
By the way I was using this ROM(the v2.2) from i think 10 days..
Is it possible that a ROM which is corrupted would do this after that much time period..

Wildfire - blank screen will not go into boot menu??

A friend has asked me to look at his Wildfire, he said it was updating the Market and then blank screened. Since then it will not turn on, vibrates, then nothing.
I suspected screen (replaced a few wildfire ones now) but no sign of life from touch buttons, volume key, etc - so suspect it is bricked.
Tried to flash it with RUU but the phone will not go into the boot menu via volume down & power on. I've tried numerous times and it went into boot menu once, but you could not select anything, no keys working.
Hooked up to laptop and laptop could see it, but when you try to run the RUU you get Error 170, probably becaused it's not actualy in USB Boot mode.
Has anyone seen this? Any other tricks to get it into boot menu? Anything I can run from laptop or SD card to force it into a recovery or boot menu?
This is a stock ROM phone, not modified at all.
Any help much appreciated

Am sorry but this the Wildfire S forums not Wildfire , write above on find your device buzz and go to that phone , it is the Wildfire forum , those guys might answer ...

Oops, sorry, my mistake!!