Please delete - Desire General

I been flashing a few roms today, then all of a sudden when i plug the phone into usb my laptop is asking to install Qualcomm CDMA drivers...
Now i did a look at the USB bricked threads, and i FM Radio doesnt work (but i cant say it worked before as i never used it) and usb obviously doesnt work.
IF it is a brick, how do i fix? the threads i read before were some what confusing.
Oh im also running the 2.2 Sense ROM. Slightly edited by me which could have crapped things up.
Any help would be appreciated.

I recently USB bricked my Desire, took me days to get it sorted despite following the guides to the letter. Can you access your SD card?
I ended up solving my problem by using a Vista laptop, which recognised my phone and allowed me to run the 'fastboot oem enableqxdm 0' command in SDK. Don't know why I couldn't get it fixed by using the various other OS.
http://forum.xda-developers.com/showthread.php?t=717361
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/

Just want to check, has this problem made me loose my root? because the guides say to root the phone....
EDIT
i do have root, just installed ES file manager and i can go into the system folder etc... well im guessin that means im rooted?
EDIT
im a moron, you can delete this thread if you want mods.

Related

Cant root Desire

Ok Guys heres what I,e got
Firmware ver 2.1-updat 1
Baseband ver 32.36.00.28U_4.06.00.02_2
Kernal ver 2.6.29-b7e82785
Build Num 1.19.707.7 CL171460 release keys
Software num 1.19.707.7
Browser ver Webkit3.1
Ok. now I,ve spent probably about 24 hours during the past three days trying to root the thing. made a gold card after about 10 attempts, have tried and tried to root the thing, have tried 3 or 4 different methods, most fail becase either I loose USB connection to the fone when navigating to Bootloader. From there on in she all over rover. Actually I,m not sure I have the right ROM to add to the fone, but I,d really like to get to the point where it asks for the rom. I,ve aged about 10 years since embarking on this venture, and still the thing is as bought. The phone isnt branded, bought it thru ebay from Hong Knog I think, has asian english which aint no fun. Have loaded Morelocal2 on but it still aint nice.
Can someone who has rooted one of these with similar ver software email me whith there secrets please before I go totally insane or really root the thing against a brick wall.
Cheers Guys.
Try the tutorial in my sig (second link). You should have no problems rooting with that.
It provides you with the required downloads for rooting. Just download and flash your ROM of choice in place if the 'rootedupdate.zip' file.
Please state any errors you recieve while attempting root.
-------------------------------------
Sent via the XDA Tapatalk App
Rooting Desire
I,ve tried your link, now my wife has been helping me, she cant get it to install either, I,ve even got to the stage of watching in Device manager what happens when it goes into Bootloader/recovery mode. the link between the HTC and the computer breaks,SOOOOOOO as I,ve stated before I have a very good understanding on HOW to root the thing, its just that for some reason I cant keep the phone connected thru the USB . I think this is the only prob I have. Something else that also happens is I get a Customer ID failed message half way thru step 1
What ever system I try to use to root this thig thats where I end up.
Wifie is going to try one more time, this time we are going to try the fone with a default startup to look at the disc not the HTC Syn.
Please keep trying to help guys
Rooting Desire
OK Heres the wifie update,
Screen says,
Pushing update file to device
error: device not found
error: device not found
Now wipe and apply rootupdate.zip from the recovery image menu.
Error: device not found
[email protected]:/mnt/cdrom/root$
So there we go guys, thats it in a nut shell
Try using the TinyCore method, I had all sorts of issues in Windows but this worked first time...see this post...
http://forum.xda-developers.com/showpost.php?p=6710081&postcount=2
obviously download the right Live CD for your bootloader
Also if you are trying to root in windows, make sure you have HTC Sync installed.
Desire root
Yep, I,m using the tiny core app followed the instructions in the link as advised. Still loses connection at bootlader/recovery
When you get back to Bootloader, how long do you wait before trying to run? As I normally leave it 5 or so seconds and then it's fine...if you do it too quick it'll say no device found
Which TinyCore CD did you download? I'm assuming you have HBOOT 0.80 on your device before you started?
Rooting a desire
An answer to your question, I,m using the tcl_r4_desire_hb80 file. when you ask how long are you waiting , I reckon it taks me more than 5 seconds to type in sudo ./step2.sh
I could try it again and wait longer.
Desire a rooted phone
Nope sorry guys, I,ve tried god dam everything, still wont connect afetr step 1 with tcl_r4_desire_hb80.
Somehow I need to be able to force a usb connection.
hey I tried this on Vista and XP, thought XP might be better. is there a stand alone app to force USB drivers when tcl_r4_desire_hb80 boots into termial screen
If you have done step 1, is it possible after failed attempts at getting into the recovery, you have usb bricked it?
Try switching it on normally and see if you have normal usb connectivity, and the sd card mounts and works fine?
socktug said:
If you have done step 1, is it possible after failed attempts at getting into the recovery, you have usb bricked it?
Try switching it on normally and see if you have normal usb connectivity, and the sd card mounts and works fine?
Click to expand...
Click to collapse
I too was thinking that there is a possibility of his device being bricked, especially when receiving errors indicating that the device cannot be found in recovery.
Rooting desire
OK, wondered that myself,
connected phone to PC, sync straight away with fone
reconnected it to pc in disk drive mode and connected, checked in My Computer and the disc drive was there with all my files.
Suppose that means everything there is ok to
OK if it isn't usb bricked then it's got to be a driver issue. My suggestion would be to follow the tutorial in the dev section and use tiny core linux.
Rooting desire
OK guys,,, so heres where I,m at, so far all info gained from you lovely people has been to no avail.
What I,m getting is this
In device manager I am watching what happens when the Desire goes from fastboot to bootloader. In bootloader I get "Android 1.0 with the yellow tiangle indicating it aint set up with drivers. In fastboot I get "My HTC" under Android USB Devices. now in either Bootloader or fastboot I,m only getting one or the other, and as I said, the triangle under "Android 1.0"
Now Ive gone to Android 1.0 and tried to add a driver, seemingly thers not a driver in the world that will work with Android 1.0. All driver in my Sdk dont work. The driver installer asks for a driver but wont except anything trown at it.
First, via your phone, go to Menu > Settings > Applications > Development and ensure the USB Debugging option is selected.
Try a different USB port.
I actually think you need to create a Gold Card even though you have stock rom 1.19.707.7
Try the Gold Card.
-------------------------------------
Sent via the XDA Tapatalk App
I have the exact same issue on win.7 64bit.
Try ignoring the no android 1.0 issue, continue to put your phone into recovery with the volume down and power buttons. Wait about 10 seconds after you see the black screen with red triangle, and then click on recovery windows.bat. Works for me everytime.
Windows takes it's time to see and install devices so it may be that you are trying things too quickly after connecting the usb lead.

Lost SD and USB support

Hello,
I have tried attempted to root and flash a new ROM on my phone and now I seem to have lost SD and USB support. it does not recognize any of the SD cards i put it (doesn't realize theres an SD card inside) and does not recognize any USB plugged in.
I have HBOOT .80 and i THINK i got the root correct (lotsa problems along the way so i'm not sure), but i was able to flash a ROM (NexTSENSE) so i think it worked. now, i saw a thread about fixing USB support but that required SD support. and reading that made me feel like i was royally screwed. in any case, any suggestions? I think USB support is still kinda there since I can get it to recognize it in the boot menu. but when i try to do it in recovery and use the flash rom .bat, it says device not found.
it would seem that the main concern right now is that i can't get it to see my SD cards. any of them, even after reformats and whatnot.
i can't connect to HTC Sync or anything of the of the sort. usually when i charge the phone, you get the charging notification but i don't even get that now. sounds like a driver problem but i can't see what is wrong. my computer doesn't even recognize the phone as a device every now and then
Hope i provided sufficient information. New to android scene so don't be too hard on me please =O but yea, any suggestions are welcome. thanks in advance
edit: usb support... ever so slightly back. aka, it charges now. probably was drivers on my lappy getting funny after moving between bootloader and recovery and all that fun stuff
You have the usb brick issue. Check out the thread on that. Also once you are up and running again, root using unrevoked or the fake flash method. All information is available in the dev forum.
ok, i've done some reading and this is what i've found so far. my phone is stuck in USB debug hence no USB support and somewhere along the way, SD support was disabled. from what i see, the fix is to
first:
reload the step1 of root to get back to 1.15 and basic root access.
second:
from there, i can re-enable SD support using the command:
fastboot oem enableqxdm 0
third:
apply USB-Brick fix found in post 1 of thread
and then i should be able to reload ROMs as usual. is this correct?
and where exactly do i put in the command to re-enable SD support? this is what has be confused right now. along with the commands for the USB fix
i am using the tinycore method so i just have the step1.sh. and then in the same console, can i enter that command? should i do it after a reboot? or load back into bootloader to do it. (bootloader or fastloader)
OOOOK. sorry about the continuous posts. putting new info up so it isn't exactly a bump right?
in any case, i used the androidSDK tools and ran the fastboot from there and i think i re-enabled my SD correctly. i was then able to run the USB-brick fix found on modaco forums. all done and done. nowww, since i just went through half the root process (step1.sh with tinycore), do i need to finish it? or since i had already rooted before, is it all done now?
I'm not 100% sure about that as I haven't had to fix the usb brick for ages now!
Download and install titanium backup from the market. If it works fine, then you are rooted. If not, root woth unrEVOked or fakeflash.
All the older root methods that require usb during the root process leave you open to the usb brick again.
Hi fatpandas..
Is your phone ok now? Actually my phone also have a problem like yours last week..until now,i can't fix it..if now your phone ok,can u share with me..thnks in advance..
@csyrix
sorry to hear about your situation. after just being there, i can tell how horrible it is. good news is, if you really have the same problem, then it is definitely fixable.
now, i don't know what method you used to flash yours the first time but from what i've seen, they're mostly the same. what you wanna do first is do that step1 thing where you have a temporary ROM installed. (1.15?) same process as usual.
then you'll need to run 'fastboot oem enableqxdm 0' with phone plugged in while in FASTBOOT (back button + power button thing)
in case you don't know where to put that in, you wanna run that in your command prompt (computer) while operating in the tools folder of the android SDK. (thank god for my limited computer knowledge cuz all the instructions i found just say, "run this command" and like hell if most know how/where)
in any case, the end result will be you having completed step1 and having re-enabled SD support. then turn off phone.
then get the fix from this thread
move that to your SD card (micro SD adapter) and turn back on your phone into bootloader. go to the recovery menu and hold volume up + power to bring up menu and hit the apply: update.zip.
then all should be well. i then moved on to step2 to make sure i had rooted properly. may not be necessary but i remember reading that rooting a rooted device isn't a problem so i just felt the need to do it to be safe.
that should be it. the link provided actually has all the instructions anyways (i hope mine are a bit more clear), but if not, that link should be able to fill in the holes. g'luck sir

[Q] USB failure? A real puzzle for you people

A remarkable problem to be solved. I run oxygen 1.04, s-off, n1 table. No SD partition, just all fat32. Then I decided to do a stupid thing wich was to change launcher by uninnstalling via titanium backup, and then install launcher pro via market. When reboot the device couldnt read the sdcard, wich i solved by using fastboot command "fastboot oem enableqxdm 0" and then "fastboot reboot-bootloader." I then got access to sdcard via recovery (amonra2.0). I Managed to do a restore of previous backup.. But then i got the problem of the device not being recognized in windows (7, 64). It worked via bootloader strange enough.. Thought it was a problem thanks to my mess ups, and decided to unroot and restore factory settings, wich i did by flashing PB99IMG through sdcard.. Are back on scratch, but no usb functionality.. Unrecogniced by windows still.. Are charging though. At some point it asked for Quallcom CMDA (I have AMOLED if that has anything to do with it) usb drivers something, installed Windows Mobile Device Center, no luck... Is this a hardware malfunction? USB brick? Ive searched everything without luck.. Would really appreciate help here, if not im sending it in on garantuee basis.
That's an usb-brick. You can find everything about it here: http://forum.xda-developers.com/showthread.php?t=691639.
Good luck.
Well. I need to be rootet to use this guide, but I aint.. Got hboot 093.001.. Searching for ways to downgrade via fastboot, or some other way since the phone is not detected via regular USB. Anybody got som tricks up their sleave?
If not this works.. Will the folks repairing this phone be able to see it has been tinkered with? I mean since its unrooted?

Do I have a bricked usb card?...HELP!!!!!

Hi all...bare with me here, I posted this earlier, but in the wrong forum section so I am going to start over here.....thanks for your patience....
Hi everyone...I have a problem..I tried to use the Firerat zips to increase my internal storage, and during the flash of the zip file the phone hung and I had to pull the battery out.....since then the usb wont mount.
I am using a Tmobile mytouch slide 3g.
I tried using the sdk and running the fastboot commands etc to get the sd card to mount...no go.
I have tried the fastboot oem enableqxdm 0 command and no go....
Note:..My sd card works fine in a card reader on my computer, I can drag and drop anything to it etc. etc.
Finally i downloaded the stock rom, and i was able to put it on the card, and rename it ESPRIMG.zip and installed it through recovery...My phone was rooted and S-off running ginger, but now back to stock...S-on, and hating the phone now...lol.....
I have been all over the web and I am so confused...everywhere you search there is something different, I just dont know what to do, Windows doesnt recognize the phone when plugged in so I cant load custom rom etc back on....AARGH!!!..I am so frustrated, and have a migraine messing with this damn thing.....lol...
Someone here suggested the MISC is bad and that a binary flash_img would fix it, but honestly, I have no idea what any of that means...all that means to me is confusion, and I have that already.....lol
Can someone please suggest what I may try doing?I am pretty savvy with computers but some of the adb/shell stuff is very confusing to me, I dont like cmd prompts...so maybe a detailed explanation?..
Thank you so much for taking your time to read my problem, I really appreciate it very much.....Dirtylarry
"Kharma...It's a good thing"
ok man im gonna try to understand the problem... you say your usb mount doesnt work but the sdcard works with the adapter, then you went back to stock and un-rooted and the pc doesnt recognize your phone? right?
So it looks to me (just an idea) that the problem is your cable or the port on your pc... just beacuse your sdcard IS working in your phone as well since you used the ESPRIMG.zip(wich was really unnecessary) and you flashed it using the sdcard obviously.
Now you need to find a way to root it again just like you did the first time... dont mess with the drivers since you havent changed them in your pc (i guess) and try this guide....
http://richard.gluga.com/2010/08/complete-guide-to-rooting-and-hacking.html
Now all i can say is ALWAYS DO A NANDROID BACKUP BEFORE MESSING WITH YOUR PHONE. And check the cable/ports... thats the only problem i can think of...
well the fact that I have 3 computers that all used to recoginize the phone just fine is what's weird....none of them do, nor does my usb connection on my car stereo...the computers all say "USb not recognized" etc. etc. and the car stereo says USB N/A .......So i'm just at a loss as to what is going on here....Any ideas????? Thanks much ....Dirtylarry
Try installing PDA Net. It installs USB Drivers and resets the registry. One day it would work, then the next day it didn't work, reinstalling PDA Net worked every time.
Thanks Wave_Sailor, I tried the pda net install but it wont work....Everytime I try it says that it can't handshake to the phone, and then gives me an error code 103, I have tried many many times....also, in the device manager for computer it shows a yellow Exclamation mark everytime I plug the phone in listed at "Other Devices", and says Qualcomm CDMA Technologies MSM....So I googled, and found another thread saying Install Windows mobile 6 center, so I did, and nothing changed.......ARGH....DIrtylarry
Do part III, but while the phone is unplugged, download and install HTC Sync, and then plug the phone back in.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Ok...I did EXACTLY what you have suggested, and in the driver information box this is what I got after the install....
USB Composite device installed successfully
USB Mass Storage Device Failed
Mytouch slide tmobil installed successful
Still a no go on the Mass storage device......hmmm.....so weird of a problem to have....I would have thought that clearing everything on the phone and going back to stock would have done the trick......any more ideas?...Thanks so much for your help.....Dirty
Have you checked in device manager on your computer to see if the mass storage device has a yellow triangle? I just went through the same thing but in reverse. My pc would see the sd card while in my phone but not through the reader. I still haven't gotten it straightened out either, just learned to live with it.
dirtylarry10 said:
Ok...I did EXACTLY what you have suggested, and in the driver information box this is what I got after the install....
USB Composite device installed successfully
USB Mass Storage Device Failed
Mytouch slide tmobil installed successful
Still a no go on the Mass storage device......hmmm.....so weird of a problem to have....I would have thought that clearing everything on the phone and going back to stock would have done the trick......any more ideas?...Thanks so much for your help.....Dirty
Click to expand...
Click to collapse
Make sure you don't have any drivers disabled. Ran into that problem with a different phone. I had one driver disabled so it wouldn't install some of the other drivers.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Ok...just checked,...no drivers disabled in device manager...has to be something wrong with phone...its a/most like the driver is missing from within the phone or something...isn't there some way to get this back to where I could root it and install a custom rom again without the USB to phone connectivity and use my card reader to get some sort of files back onto phone that way?
ok....well I re-did the whole flash process over, and I am now rooted again once more.....I dont know how or why or what...but I am now going strong again.....lol thanks for the help everyone,

Trouble flashing radio..."error: device not found"

Hi all,
I'm using the guide on how to flash a ROM onto my DHD and I'm at the stage of flashing a new radio.
In command prompt when I start with "adb reboot bootloader" it says *daemon started successfully*, however then says "error: device not found".
Not sure what I'm doing wrong, and I can't post it in the guide thread as I have less than 10 posts!
Many thanks for any info
Have you tried to boot to bootloader from the device itself instead of command prompt. And then flashing the radio from command prompt. Has everything else went ok since that stage, sure you've got every bit right and installed?
I will try doing it that way now. I saw that and thought it would work, but didn't want to risk it.
Root, Radio S-off and ENG S-off all worked fine beforehand.
edit: tried that, bootloader rebooted, so I did "fastboot flash radio radio.img" and now getting - unknown partition 'radio.img',...error: cannot determine image filename for 'radio.img'
LawAce said:
I will try doing it that way now. I saw that and thought it would work, but didn't want to risk it.
Root, Radio S-off and ENG S-off all worked fine beforehand.
edit: tried that, bootloader rebooted, so I did "fastboot flash radio radio.img" and now getting - unknown partition 'radio.img',...error: cannot determine image filename for 'radio.img'
Click to expand...
Click to collapse
Ok, good to know you've got root, s-off and eng s-off so you should be out of harms way trying different things. Have you just tried to download the actual radio file again, could be a bad download? And do you have the radio.img file in the same actual folder as the fastboot file?
I remember while I was flashing a radio for the first time the android sdk had installed fastboot in a different folder (there is tools and platform-tools folders, or similar, can't recall the exact name as they are on my laptop and I'm on a different computer just now) than adb etc. and had to manually move it to the same folder. Check the things above and report back
I will try downloading the radio again, and yes I have moved it into the correct folder. It's weird that it's saying device not found, could it be something to do with drivers?
it might be your using a different usb port to the one that was working originally. Pretty sure that caught me out before.
Well it sounds a bit strange but it could somehow be fixed on a specific usb port, although haven't ever heard about such a problem It surely could be a driver issue, just to make sure you have all the necessary adb drivers and htc sync? And didn't have any problems installing hboot (just checking and checking )? Sometimes these are a bit of spirit world issues and a simple reboot (of the computer perhaps in this case) could solve the issue
Just as a quick update, I got it all to work in the end. Now running Revolution 3.2, very pleased!
Thanks for all your help, didn't get to the bottom of it I just kept trying and it randomly worked, didn't do anything differently!
Vispe85 said:
Well it sounds a bit strange but it could somehow be fixed on a specific usb port, although haven't ever heard about such a problem It surely could be a driver issue, just to make sure you have all the necessary adb drivers and htc sync? And didn't have any problems installing hboot (just checking and checking )? Sometimes these are a bit of spirit world issues and a simple reboot (of the computer perhaps in this case) could solve the issue
Click to expand...
Click to collapse
Its true, adb had trouble working through a hub, you should plug you DHD into a usb port that connects direct to the mainboard
Sent from my Desire HD using Tapatalk
I'm having the exact same issue, but you guys are right, plugging into a USB directly connected to the mother board is the trick.

Categories

Resources