Database Info

HTC Desire USB/BT/FM Issue - who is involved

Hi there,
as you may know, some owners of a desire have an issue with their USB/BT/FM functions. For example only fastboot works but no adb / mass storage ...
So, i thought opening this thread to collect your issues, please post the following informations:
Bootloader Infos
Rooted or not
Which rom
Have you used mass storage switch in recovery
Do you use a2sd or a2sd+?
If there are enough answers i will send the collected infos to paul from modaco, who tries to adress the issue.

no usb-bt-fm
bootloader 0.75
original rom 1.15.405.4

when does it happen for you

Also posted om Modaco
Bootloader 0.75
Stock ROM 1.15.405.4 Rooted + App2sd + dalvic
Yes, I used Mass storage in recovery
Issue startet when I transfered the MCR custom fra PC to phone via recovery

I loaded a rom amended with root permissions, not happy I restored everything to its original state with the 1.15.405.4 but now no longer works usb-bt - FM ... and access to most recovery so I can not load the rom recovery .. . Help

From what i know the guys looking into this have problems to dress the trigger of the brick, so all infos on how and when ar great

Bare in mind that the rooting process was at your own risk: no-one (HTC or Paul) will take responsibility if features are no longer working.
Personally, everyone works fine on mine including adb/mass storage. I don't actually see why it'd break.
OP, what OS are you using? I had to add some udev lines into Ubuntu as otherwise adb would work but Mass Storage would fail (on my netbook, even adb wouldn't function without adding the android rules).

I know it's our risc, but hey without some investigation no progress, right?
Btw. Paul is looking into this but no ETA for now

I had exactly the same issue as you lot, only difference was that my new rom flash was interrupted by me knocking the phone and the battery falling out!
I was on evil's 1.0 and decided to change to his 1.1. In the middle of the phone formatting during the flash, I knocked the phone and the battery dislodged causing it to lose power. I had the sd card formatted and was already using a2sd. Turning it back on and restarting the root process from step 1 on Tiny Core Linux got me back with a semi working phone. I had no BT, no SD card, and didn't check the FM radio. It also started to lose signal and would require a reboot to get it back.
I tried unrooting it using paul's method and it was still the same. I just took it back to the shop and acted stupid. They gave me a brand new boxed one, no questions asked I'm scared to try flashing again now though lol.

0.75
Modaco R2 with A2SD+
Yes i have used USB-MS (still works)
no usb connectivity from within android.... but adb works

Bootloader 0.75, tried a few different ROMs (primarily eViL's, tried some MoDaCo), and I've definitely mounted the SD from within recovery. Every single ROM swap I've done was accompanied with a full wipe and SD partition afterwards.
So far I guess I've just been lucky. USB still works, though it can take a long damn time to get recognized in Windows if I'm syncing through the Desire; if I take the SD card out and pop it in a reader, it pops up instantly.
So: .75, lots of ROMs, definitely mounted SD from recovery, always full wipe and format. No issues. Supremely lucky, apparently. :/

Hboot 0.80 o2 Germany ModacoCustomRom r3.
Today after reflashing MCR3! Before all was very well the only thing was that iwasnt able to mount my sdcard without a witget!

Bootloader 0.75
MoDaCo r3 Rom with app2sd+
I used Mass storage in recovery
Issue startet after I flash the jit patch,it can't use recovery again

Can you all confirm that you had a boot loop at some point during your flashing?
The conversations on Modaco now have me convinced that this is triggered when you go through a boot loop of three cycles.

Loccy said:
Can you all confirm that you had a boot loop at some point during your flashing?
The conversations on Modaco now have me convinced that this is triggered when you go through a boot loop of three cycles.
Click to expand...
Click to collapse
yes,I think it's,but have a solution now?

miyu-hitori said:
yes,I think it's,but have a solution now?
Click to expand...
Click to collapse
No, not for those who've been bitten, but I think the rule for those of us still flashing is:
1) Flash rom (or update.zip for kernel, make changes to system, etc) in recovery
2) reboot
3) immediately do adb logcat on your PC and watch first boot like a hawk
4) if logcat reveals that your device is bootlooping, PULL THE BATTERY IMMEDIATELY. Reboot into recovery (which should count as a "successful" boot, and reset the counter) and flash a known good ROM, restore your backup, whatever.
Fixing those phones that are dead is unfortunately a task for a greater mind than mine.

Clueless what to do next?

Hi
I'm completely clueless as to what to do next here. I've rooted my Xoom which worked and was fully functional, etc.
Now I wanted to try the Tiamat ROM. I installed Clockword Mod Recovery from the ROM Manager yesterday. It reads version 4.0.0.4. Now I downloaded the ROM and tried to install via clock word but nothing happens. What's worse now is that my Wifi says "error" and can't be turned on.
At this point if someone can point me in the right direction to getting the ROM installed, I would greatly appreciate it. If not, I'll also go for stock 3.1 rooted if that's possible at this point.
Please help me out
Thanks

This exact same thing happened to me. Made me really nervous and I wound up rolling back to stock and rerooting - all unnecessarily. All you need to do is put the Tiamat recovery back on, wipe your data (yes, everything on your internal storage, so make a backup), and install Tiamat 1.1 from an SD card. I detailed my experience with instructions for another person on how to fix it in this thread:
http://forum.xda-developers.com/showthread.php?t=1152121
Any questions just ask.

mikeserv said:
This exact same thing happened to me. Made me really nervous and I wound up rolling back to stock and rerooting - all unnecessarily. All you need to do is put the Tiamat recovery back on, wipe your data (yes, everything on your internal storage, so make a backup), and install Tiamat 1.1 from an SD card. I detailed my experience with instructions for another person on how to fix it in this thread:
http://forum.xda-developers.com/showthread.php?t=1152121
Any questions just ask.
Click to expand...
Click to collapse
I've been trying to warn people about that incompatible recovery from Rom Manager for several weeks. I wish we could have a sticky post about it. So many people fall into that trap and get all messed up. I know cause it happened to me.

SOLVED Desire S stuck on splash screen

Got S-OFF yesterday and used gribger break to root the phone and all was well.
Didn't install a custom rom ,but now this morning the phone won't reboot past splash screen and keeps rebooting at splash screen. Is it bricked?

Take the battery off, start the phone with vol - preseed and do a factory reset.

When I go into CWM and try the reset it goes through the motions but upon reboot its still the same problem

Don't go into CWM just do a normal factory reset, if it doesn't work i guess you could put a ROM on the SD and install....anyway your phone is not bricked.
Lol before i got S-off... so with s-on i modified a theme, and i got the phone into a boot-loop, the factory reset solved my problem

Thanks , when do factory reset it seems to tale me to CWM recovery by default? any way round this? .
Also your help is much appreciated

Don't know.... i'm almost as new to this as you are...
Put a stock RUU on your sd card and install it... or a custom one.

before it goes to CWM it seems to flash up an error msg .As far as i can make out it says PG88DIAG.zip no image

Morning, The fact that you can still get into CWM is good,
Is your phone recognised, when you plug in usb?
I suspect that you'll need to run an official Ruu (rom upgrade utility) which you run from the pc.
But first try the following
1) download wipe utility http://bitly.com/kpb0A2?r=bb
2) download custom rom http://bitly.com/jnV3em?r=bb
3) copy both files onto sd card, put card in phone
4) boot phone to CWM
5) use the "flash zip files from sd" option to flash both zips in order above, wipe and then rom
6) then reboot
Good luck
EDIT: don't understand the error message that you're getting haven't heard of that.......
does CWM appear to work though, and the wipe you tried from there worked? Our returned cheerfully and came to with the correct messages?

No When I plug it in to the PC HTC Sync isn't picking it up , going to try your other suggestion Ben

Yeah cwm does appear to work it has the status bar and all
Just d/l the rom now then will try that

Just starting to install the rom now .
Does this take some time ? as install bar does not seem to be moving?

ben_pyett and .sh4d0w. you are both stars and I thank you very much. Got that custom rom installed Ben and everything seems ok.Just need to set the phone up the way I like it again lol.
.sh4d0w. thank you for setting my mind at ease 2 months into a 24 month contract and waking up to what i thought was a bricked phone scared the living S*** out of me .
Panic over .
Hopefully I will be able to pass this info on to anyone that needs it in the future

No problem.. glad i could help.
I'm also on a 24 month contract (22 left ), but i just couldn't resist to s-off my phone and try a new rom

Same here even though I was more than happy with it .

Ben one more quick question then i'll leave you be. Do I need to keep the rom zip on the memory card after i have installed it ?

det66 said:
ben_pyett and .sh4d0w. you are both stars and I thank you very much. Got that custom rom installed Ben and everything seems ok.Just need to set the phone up the way I like it again lol.
.sh4d0w. thank you for setting my mind at ease 2 months into a 24 month contract and waking up to what i thought was a bricked phone scared the living S*** out of me .
Panic over .
Hopefully I will be able to pass this info on to anyone that needs it in the future
Click to expand...
Click to collapse
Very glad to be able help to a positive outcome and Very happy that you got it all sorted.
If you intend to stay on that ROM, (I like it) then I'd recommend that you also apply the following (which should all applied via flash from zip option from SD card)
UNITY V2=[SENSE 2.1][OC/UV][CIFS/TUN][SLQB][V(R)][2WCR] V2
later version of kernel that comes with the base rom (kernel updated since rom released)
4EXTRecovery v2.0.2 RC2
which is a re-worked version of CWM (improved, easier to use with more options ) - would recommend this as it currently has great support and is updated very regularly.
There is also the option to install the Engineering (ENG) HBOOT, which is an improved bootloader that gives you more options which are useful in advanced recovery situations. Although I don't know the implications of using it with AlphaRex but believe that there's a thread specifically about this which I'd suggest that you read.http://forum.xda-developers.com/showthread.php?t=1161158
[A] you don't need to leave the ZIPs on the SD card but they do no harm there, I find that it's useful to leave them there, I always leave the ROM that I'm running on on my card - in case I experience any problems.

There is also the option the flash new radio, but this is very much user, location and network specific so only do so if you're having problems.
You may need to re-calibrate you battery having moved to new the ROM see instructions on SAGA thread, see how battery usage is first.
The only bug that I know of in LBC ROM is the ADVANCED POWER MENU (which you get by long hold on power button)->RESTART-> HOT RESTART hangs the device requiring battery removal - so don't use it!

Thanks for the tip .do you know if this is overclocked by default and if so to what speed ?

det66 said:
Thanks for the tip .do you know if this is overclocked by default and if so to what speed ?
Click to expand...
Click to collapse
it has the ability to be Overclocked, but isn't out of the box, and in my opinion unless you're a gamer, probably it isn't needed, it will just burn more battery
do not install setCPU as this disables the O/C daemon
sleep: min 245MHz / max 368MHz / conservative
wake: min 245MHz / max 1017MHz / ondemand
- > everything can be changed with a text editor in /etc/virtuous_oc
If you intend to stay on this ROM then I suggest that you read the whole thread, so as not to ask questions that have been answered already
ROMS also due an update any time soon.

Read and understood and onceagain many thanks .Gonna read the thread calmly this morning

Q&A on wifi "error" - already solved

I'd like to get the feedback from XDA masters on this issue I had.
Here's the steps that led to the problem.
Flashed ROM(Dr No V2), Decide i didn't like it after a day, the wifi was orking.
Entered 4ext recovery did a full wipe.
Used restore to flash my previous fully functioning ROM (EnergyROM-RCMIX)
Rebooted.
After reboot received the message in settings>...>Wifi "error"
I went through a bunch of steps, lots of reboots.
Try restore of an earlier backup - no fix
Reflashed from Zip the original RCMIX ROM, and fastboot flashed boot.img - no fix
Went into recovery and factory reset only. - no fix
Restored the last working ROM (RCMIX) and just fastboot reflashed boot.img
Still not fixed
More reading tried rename of the wpa_supplicant file. nope
One more fastboot flash of boot.img --
Then... turned on "Airplane Mode" for a few minutes. After turning it off Wi-fi "error" was gone and was able to turn it on.
The error changed to "unable to scan for networks"
Rebooted
Went back in and renamed wpa_supplicant.conf 1 more time.
reboot
When I enable wifi this time it scanned and connected.
I left some steps out, but they were just repeats of the ones I listed.
My question after all that is what went wrong?
Lots of threads about the problem but solutions seem to vary.
Is there something in there that I did incorrectly?
Aren't the drivers for the hardware located in the boot.img (as it contains kernel)?
Is there a better way to do this?
trying to get better at this; Insights, advice, comments appreciated.
I do need to get familiar with logcat.

Clean flash a stock-ish ROM like Android Revolution HD. Is the problem still there?

bananagranola said:
Clean flash a stock-ish ROM like Android Revolution HD. Is the problem still there?
Click to expand...
Click to collapse
Wifi seems to be stable now. Running the restored RCmix. Rebooted a couple times and no issues. I'm interested in gaining some insight into the source and solution of the problem. My next step was to run a stock RUU I have, but your suggesting something close to stock might have worked?
Why didn't a re-flash of the previously functioning ROM (RCmix, zip on sdcard & fastboot boot.img) fix the issue? I did full wipes each and every time. Even full wipes before doing Restores from recovery. Restore should be a straight forward process from recovery, right?
The problem started right after a restore, and I'm not sure what step it was that fixed it. The last thing was renaming the wpa_supplicant.conf file. I left out the part where my restored ROM got stuck in the boot animation. There was something going on with the boot loader. Re-flashing boot.img fixed it.
But the wifi...? Any thoughts.
I'm a little hesitant to flash another ROM for fear of losing wifi again. I use it a lot.

Cremnomaniac said:
I'm looking for some intelligent feedback. Any thoughts on my OP?
Click to expand...
Click to collapse
I already answered you...and also, why are you renaming wpa_supplicant.conf? Are you making any other changes?

bananagranola said:
I already answered you...and also, why are you renaming wpa_supplicant.conf? Are you making any other changes?
Click to expand...
Click to collapse
Thanks, but your first comment offered a possible solution, and solutions are important, but as indicated in the title it had been solved. There aren't any comments on the questions I specifically asked. At the least, I was hoping that someone with greater experience could provide insight into the possible causes of loss of wifi (steps, incompatibility of ROM, freak thing, etc.) so I can avoid it in the future.
The renaming of wpa_supplicant.conf came from threads in the XDA forums where similar wifi problems had been encountered. It was a solution with zero risk.
Here: http://forum.xda-developers.com/showthread.php?t=1965812&page=3
Here: http://forum.xda-developers.com/showthread.php?t=1662805
Here: http://forum.xda-developers.com/showthread.php?t=1988190&highlight=wifi+error
Here: http://forum.xda-developers.com/showthread.php?t=703105
If I made any other changes I would mention it. I can see that you may be the only one monitoring this forum, which is unfortunate. You exhibit a lot of patience, but unlike some of the questions posted, I do the research and read directions carefully. The reason I ask questions is to learn, not to have my hand held. And someone posting "ddpo" is a waist of bandwidth. If no one has any comments to my questions, we'll leave it at that.

Because stock is most stable, flashing a stock-ish ROM will reveal whether the problem is a hardware one or a software one. If the problem still exists on stock, your hardware is probably messed up. If the problem doesn't exist on stock, something is up with your ROM. That is why flashing stock is still relevant: for the first step in diagnosis. Other than that, you can look into getting S-Off and flashing an updated radio, but that's up to you.
And I already reported the "ddpo."

[Q] Phone Randomly Reboots Itself?!

So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!

Infused4life said:
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Click to expand...
Click to collapse
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide

joel.maxuel said:
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!

Infused4life said:
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Click to expand...
Click to collapse
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).

5529
joel.maxuel said:
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
Click to expand...
Click to collapse
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help

Infused4life said:
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Click to expand...
Click to collapse
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.

joel.maxuel said:
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
Click to expand...
Click to collapse
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!

Infused4life said:
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Click to expand...
Click to collapse
I am not sure if you are still facing the same issue but if you are facing reboots, then considering doing a fresh install after cleaning your internal storage as well since the remnants of the apps from previous installs have caused me problems. Ever since I started doing a fresh install (Factory reset, wiping the cache, wiping the dalvik cache and even the cache partition along with the wiping of the internal storage), there have been no reboot issues.