Root problem with 'Fastboot oem enableqxdm 0'

[HikerMan]

Hi, I'm having a bit of trouble with my desire here; after backing up my rom using rom manager my phone's sd card became un-mountable - this has happened before to me, and I used this thread to help me out then; Cannot mount SD card in boot recovery [resolved thanks to mariosraptor] - xda-developers
So I had the same problem, so I took the same steps as before to fix it, however I got stuck at the 'fastboot oem enableqxdm 0' part and this was because, I realized, that on the fastboot screen/recovery whatever it is, says 'S-ON'; this is new I believe, and is the reason that I cannot use this method - please help! I now do not know what to do.

Extra info if needed: I am running a Desire on AmonRA, rooted using unrevoked, and just to clarify, my sd card is unreadable because of this problem; this also means that my sim card won't work, and that I can't recover any backups or anything.

Any feedback will be greatly appreciated; as you can tell I'm in a bit of a tough spot and I will be willing to do pretty much anything just to get it back to working order.
Thanks in advance!

 

[SUroot]

S-on / s-off is nothing to do with being rooted (except you need to be rooted to have s-off).

Are you positive you were s-off? You ran the alpharev bootable CD to s-off correct? from here: AlphaRev 1.8

Does your USB still work?

If you cannot boot into rom, you cannot become s-off again

If USB works, may be able to return to stock using an RUU, but I do not know what carrier you are on / whether you were branded or not?

 

[HikerMan]

Hi, thanks for your reply. Yes I have come to the conclusion that I was never S-OFF, which is good news, however my initial problem is still here; when performing the command line 'fastboot oem enableqxdm 0' it says '<waiting for device>' and hangs there. I think this may a driver problem, but not sure... any ideas?

 

[SUroot]

Yes the problem will still be there because you cant 'fastboot oem enableqxdm 0' unless s-off.

If you have a working USB, I recommend returning to stock with the RUU. This is the only decent thing I can think of to get your phone working.

However, you still have not answered my last question, so unable to point you in the right direction.

 

[brokerdan]

I have the same problem "Waiting for device" I found on various forums that it would seem that this is a driver issue. I have yet to find the solution to my phone Cherry Mobile Candy. That said in SDK make sure that you have D/L the generic USB Drivers also make sure that when you plug in your device via USB that (Windows...Assuming) it says that there are no missing Drivers. If not try to find the correct drivers and install via SDK the Generic USB drivers. Maybe that will help maybe not I wish you better luck than me.

 

[Rastaman-FB]

I have the same problem "Waiting for device" I found on various forums that it would seem that this is a driver issue. I have yet to find the solution to my phone Cherry Mobile Candy. That said in SDK make sure that you have D/L the generic USB Drivers also make sure that when you plug in your device via USB that (Windows...Assuming) it says that there are no missing Drivers. If not try to find the correct drivers and install via SDK the Generic USB drivers. Maybe that will help maybe not I wish you better luck than me.

its a fastboot driver issue.

in order to get fastboot working you will first need to install htc sync
then uninstall it leaving just the drivers.
connect the device while booted into android and let it install the drivers.
reboot the device and boot to fastboot

if it doesnt auto install the MyHTC drivers for fastboot then download the drivers from the root tools sticky in my signature
point android 1.0 to the drivers