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

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.

Related

[q] help flashing freinds g1

I said I would flash cyanogenmod on a friends G1 because he was fed up with 1.6. I've flashed many custom ROM's on several different devices before but I've made a mess of things with this G1 and I can hardly hand back an unusable phone so I would really appreciate your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work because I would need to use DangerSPL as the /system partition is too small on the dream/g1. To be honest at this point I can't be bothered with to do that and this guy will be happy with anything above 1.6 to be honest so I thought I would try and flash CM4 because that's based on Eclair I believe (and so it not require I use DangerSPL or any other method to repartition the NAND). However, I tried it twice and still no luck.
At this point I'm somewhat panicking as I cannot seem to make the phone boot and it isn't even mine! Is anyone able to help?
Anyone? Please?
Look, at this stage I will forget custom roms etc. If anyone can tell me the easiest way to get this phone booting android again i would be very grateful.
Even if you could just tell me exactly how to restore it to stock 1.6 from here?
I have flashed roms on phones before - never had a problem but this is driving me crazy - please help!
wollac11 said:
Hi I said I would flash cyanogenmod on a friends G1 coz he was pissed off with 1.6 but im having trouble and I can hardly hand back an unusable phone so i really need your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work coz i would need to use DangerSPL coz the /system partition is too small on the dream/g1. Tbh i'm tired so I cba to do that and this guy is not that technical so he will be happy with anything above 1.6 so I thought I do CM4 coz thats 2.0 or 2.1 i seem to remember (and it not require I use DangerSPL) - tried it twice and still not luck.
HOW THE HELL CAN A GET THIS STUPID THING TO WORK AGAIN!??
MAJOR PANIC AS THIS IS NOT MY PHONE - PLEASE HELP!!!
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=803482. I hope it helps.
It's been way too long since I rooted mine to be of any real help but I shall try nonetheless.
Firstly, there is a guide in the G1 forum to unroot and get back to stock firmware: Here (but note that I've never done this).
I must stress though (admittedly from memory) that if you have flashed an SPL or radio image at all, be VERY careful about the order in which you revert back to stock (or go to get a custom ROM depending on which way you decide to go). The G1 is very picky, and flashing things (mostly SPL and radio IIRC) in the wrong order will brick the device. That said, if you follow the instructions you find to the letter you should be OK. But yeah, read twice, flash once.
There is a lot of information in the stickies in the G1 forum. It could take a while to wade through but it should all be there. Failing that, post in the Q&A or General G1 subforums and I'm sure a current user will help you out.
I apologise if I've just posted a bunch of stuff you already know/have read - like I said, I've not used the phone in a while - just trying to offer what I can.
Thanks
No worries now guys i've done it! It was quite complicated but its all sorted now. If anyone is trying this and has the same (or similar) issue then pm me and I will tell you how I sorted it.
Otherwise thanks guys and you can conciser this thread:
---------------------closed--------------------------

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

Clockwork Mod Not Flashing ROMS

Hello, please let me know what I'm doing wrong, I've looked exhaustively for a solution to my problem on my own but I can't seem to find one:
1.) Rooted my G2x
2.) Installed Clockwork ROM Manager
3.) Copied two separate Gingerbread ROMs, Cyanogen 7, and Modaco into Root Folder (no sd card, just phone storage)
4.) Tried flashing both Roms multiple times with Rom Manager by both rebooting into recovery and installing from .zip (this option won't display either of the ROMs, just the log file folder.) I have tried installing .zip from SD in ROM Manager, and the phone just reboots as if nothing has happened.
*I believe ROM Manager does have difficulty mounting the phone storage, as it takes a full twenty count before attempting to flash the ROM.
**I don't know if this helps, but I have not received the OTA Gingerbread update from T-Mobile (even when my phone was unrooted), and when I prompt for the OTA update, I receive a "connection error" message. The LG Updater Tool indicates that my phone is "up to date" when it clearly, is Froyo 2.2.2.
Any help would be greatly appreciated with this issue guys, I usually scour forums for answers to my questions or fumble my way through it myself, but this has really sucked out lots of hours from my life.
No external sd card
You have to have a external to flash roms if im not mistaken
when you install recovery there are 2 choices external storage and internal storage if you dont have an sdcard reinstall clockwork using the internal option. that should do the trick for you.
eagle1967 said:
when you install recovery there are 2 choices external storage and internal storage if you dont have an sdcard reinstall clockwork using the internal option. that should do the trick for you.
Click to expand...
Click to collapse
I am going to try with an external SD card. Also, I am unsure of how to flash it to use internal storage, I checked the settings through ROM manager and couldn't find out how to do it. Is this something I access during Recovery mode? Thanks for the suggestions so far guys, I'll definitely post with results.
pathmarkpolice said:
Hello, please let me know what I'm doing wrong, I've looked exhaustively for a solution to my problem on my own but I can't seem to find one:
1.) Rooted my G2x
2.) Installed Clockwork ROM Manager
3.) Copied two separate Gingerbread ROMs, Cyanogen 7, and Modaco into Root Folder (no sd card, just phone storage)
4.) Tried flashing both Roms multiple times with Rom Manager by both rebooting into recovery and installing from .zip (this option won't display either of the ROMs, just the log file folder.) I have tried installing .zip from SD in ROM Manager, and the phone just reboots as if nothing has happened.
*I believe ROM Manager does have difficulty mounting the phone storage, as it takes a full twenty count before attempting to flash the ROM.
**I don't know if this helps, but I have not received the OTA Gingerbread update from T-Mobile (even when my phone was unrooted), and when I prompt for the OTA update, I receive a "connection error" message. The LG Updater Tool indicates that my phone is "up to date" when it clearly, is Froyo 2.2.2.
Any help would be greatly appreciated with this issue guys, I usually scour forums for answers to my questions or fumble my way through it myself, but this has really sucked out lots of hours from my life.
Click to expand...
Click to collapse
I can't quite tell if you used rom manager to flash CWM, but if you did then make sure to use nvflash. I don't know if it could cause things not to work, but it's the only way to guarantee you can always get into recovery. As people have said above, try to use external, although I hadn't read anything about problems with using internal to flash roms, at least if nvflash has been used.
I'll assume you've already heard of wiping/factory reset and all that since you joined a few years back, but make sure to do it when going to a new rom. As for the update issues, I would say just restore stock froyo, maybe from the nandroid tgagunman created if something is wrong with yours, factory reset it just to be careful, unroot using superoneclick, flash stock recovery using tgagunman's one click recovery flasher, and make sure usb drivers are up to date.
If you really can't get the new baseband and roms working after all that... tell t-mobile you can't get the update and ask for a new one haha.
Thanks Guys...
Danish, Eagle, Water, thanks a lot to all of you guys. I was able to flash a new ROM using an External SD card, I'm still having problems finding a ROM that is stable and is compatible with all of the apps I want to use (I'm currently having difficulty installing Tooyoou on the Bionix ROM I downloaded, which is otherwise AWESOME). I mean, it's not that big of a deal, but I'd like to get my extra $2.50 a month from the program.
Oh and NV Flash...
NV Flash helped me when I messed up my G2x's ability to boot into recovery with a Cyanogenmod 7 ROM build. Here's a link to a guide that helped immensely for anyone who finds themselves in this thread with a similar issue:
http://forum.xda-developers.com/showthread.php?t=1056847

[Q] Never have a successful flash via CWM-Recovery

Hey friends,
I tried to upgrade and flash my tf to the newest ARHD or Revolver ics roms yesterday, coming from Prime 2.1. Therefore I wanted to use my rogue cwm recovery and made sure to wipe the tablet before i started to flash.
At first I thought, the light edition of the full wipe script from ARHD would do, but neither of both roms mentioned came beyond the first screen (nvidia tegra etc.) after installation.
Then I tried the wipe function of cwm, but that simply did what the script did I believe (leaving the internal storage untouched), which didn't succeed, too.
Finally I wiped my tablet with the "real" full wipe script and tried installing again, and again without any success.
So I used a nvflashable version of the stock ics i found in this forum (I have a B50), which eventually resulted in a working ics installation. I gave each of the other roms up to 10 minutes for the first screen before I stpped the try, and stock ics skipped this screen after 2 seconds after its successful installation.
I remembered, that I already had this behaviour when I was trying to flash a custom rom first, right after I rooted it, but with a different recovery back then (must have been roach's).
So I wanted to ask you if you have any ideas why this happens. I mean, I don't believe that it's all because of bad flashs. Both roms were stored in different locations, one on the sd, one on the internal memory. It's very inconvenient that I always have to wipe all partitions including the internal storage when I want to change my rom and there are only the roms available to me which have a nvflash version.
Thank you in advance, I hope I didn't write too much.

Htc one S. Time of the month.

Hi need a bit of help with this one if possible.
start the top..
went to flash leedroids rom..flashed boot image but forgot to pull rom over.
so had various issues getting over in the end had to mess around with recoverys and totally wipe my sd for it to be recognized.
so i solved all this then..now the issue is..of everything i push over..only one rom boots up and installs fine..and that is a cm9 test without sd mounting..so it solves nothing.
any ideas of how to get a rom on there where i can mount the sd..download a rom and put it on..
ill be honest..htc+internal sd card=not happy
ive pushed leedroids..virtuous..utbs rom but nothing.
i tried aokp but it didnt even push.
with these also some get corrupted by a protocol failure..
many questions. currently has cm9 on..but no mounting..so great
Did you already try a factory reset after flashing the stock recovery (e.g. from MoDaCo)?
-
Hi rootrider, yeah i followed a post i found..
basically i used the one click toolkit to flash the stock recovery..then cleared storage and all data etc.then installed clockwork back..it doesnt like the working roms though
cm9 is the only one i can boot up..at least it sees the sd card again in clockwork though
Had your problem as well... I don't remember exactly what I did to get out among many other things (sh..).
Had some trouble as well flashing stock recovery with the one click tool kit. It didn't work as expected. So I did it with adb. Just keep on trying, there is a way out.
-
My next course of action is, to flash the stock recovery, clear everything,reinstall clockwork then install aokp..if its something with the type of rom.maybe that will work..i can mount..get a rom on the sd and resume business as usual..
debatebale whether itll work lol
If this doesn't help get Thor's hammer and flash your appropriate RUU (again).
Easiest method would be to run an RUU and start over again. I see your vodafone UK so try this one
http://dl.dropbox.com/u/69014495/RU..._2_10.23.31501S.10L_release_258386_signed.exe
It also includes the new radio too !
Just relock bootloader before running it, After its finished unlock and fastboot flash cwm..
easy peasy !!
--
thanks people, im running leedroids rom now, seemed my issue was is after pushing the file over i just tried to install immediatley..after a couple of reboots just for the hell of it,untouchables rom started installing...phew..
sadly all my sd contents have gone..very dissapointed with the sd card business!
still least its working again!
thankfully azzle didnt need to go back to ruu
Aye, captain. Glad to read this.

Categories

Resources