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.
Hi guys,
I've got a HTC Desire (Telstra) which I've used with a number of ROMs, most recently LeeDrOiD V3.0.8.2 GB Data++.
I was using the Bravo Oxygen HBOOT, note NOT the r2 version. I followed some guide around here on how to cut down the ROM at the time to fit on the smaller /system.
So anyway, this has all been working happily for a number of months. Yesterday I decided to upgrade to LeeDrOiD HD V3.3.3 Port R5 DATA++.
I downloaded the ROM to the SD card, did a full wipe + dalvik. Told it to install the ROM from the zip and that was all happy.
Reboot and the phone doesn't boot - just sits on the AlphaRev boot screen. I know you need to wait, I left it for a good half hour, but nothing.
I repeated the wiping + installing process two or three times without any luck.
Trying to work out what went wrong I came to the realization that I was using the non-v2 version of the Oxygen HBOOT so the thing was probably failing because of the different partition sizes.
I created a goldcard and flashed Oxygen r2 via a PB99IMG file which was successful.
Installed the ROM again (with wiping) but it's still doing the same thing - just sits on the Joker logo.
Anyone got any suggestions on how to proceed?
friendly bump
So I got the desire S for more then a year now and decided to flash it with 4.0.4.
Build date 24 june. From here.
Now the first week I didn't seem the have any problems but now it randomly reboots. Mostly it keeps rebooting till I plug it in the powersupply then it keeps working and I can take it out again. But after a while... during a call or just when it's in my pocket it reboots again. What can be the problem here? Anyone who got a anser for that?
More information please
ROM name? How did you root / unlock your DS? What other apps have you recently added that may have helped to cause this?
We aren't mind-readers - our balls are made of flesh and blood, not crystal :angel:
Yeah sorry.
http://forum.xda-developers.com/showthread.php?t=1429215
CyanogenMod 9 Alpha for HTC Desire S
That mod I installed. I only installed whatsapp and google maps.
Other then that didnt do anything else.
To unlock the phone I used the following software.
SuperOneClick 2.2
adb-fastboot-win
ClockworkMod Recovery
There were problems like this a while back with CM9, but they haven't happened for a while.
There were, also, some issues with using CMW but none with using 4EXT Touch.
So, my suggestion would be:
Install 4EXT Recovery Control and Touch Recovery (https://play.google.com/store/apps/details?id=ext.recovery.control)
Install the ROM again using a clean install - superwipe all partitions as 4ext (format, not to be confused with the name of the recovery tool)
I assume that if you are on hboot 2.00.0002 you know about http://forum.xda-developers.com/showthread.php?t=1525100
Hello guys, I've been having unusual problems with my recently purchased 2nd HTC Sensation 4g (it was supposedly brand new). I already have one HTC Sensation 4g running on Revolution HD for almost a year and regularly update it. Anyways, onto my issue with my new HTC Sensation...After I attempted to put on a new 3.33 firmware and the RevolutionHD 6.7.2 ROM, I was unable to boot it (stuck at the HTC quietly brilliant screen). I then tried to put on the latest T-Mobile RUU and again, it got stuck at the boot screen. I then superwiped again and repeatedly try out a bunch of the complete big ROMs (OrDroid 9.0, Elegancia Pegasus, etc) without any success. I was about to give up and figured my phone is bricked, but then decided to try out the more simple CM9 ROMs (Extreme Sensation Power-2) and was shocked it was able to boot and fully function! I then tried out similar ROMs and currently running Infinity's TouchCream 2.1.
I would appreciate if anyone have experienced similar issues and could give me some advice on how I could address it. I will have to do more experimenting to find out what's being going on. I have a feeling it could be a much more complicated problem than just simply mismatched/outdated ROM or Firmware. The reason why is because my 1st HTC Sensation (the control) was tested using the exact same configs without one single hiccup.
Reflash the newest firmware and then ARHD
I assume you are s-off with the latest 4EXT. If not, do that first.
I would download the latest 3.33 universal package: http://d-h.st/bCV, along with the latest ARHD 6.7.2: http://goo.gl/QDuTC
Run the firmware update through HBOOT (place PG58IMG.zip on root of the SD card, VOL DOWN + POWER, accept update), and then reboot into recovery.
4EXT should warn you that it is in safe mode due to a change in your HBOOT/partitions (if not, reboot recovery again, and if still not, you were already on 3.33 with revolutionary HBOOT ), so do a format of all partitions except SD card.
From there, reboot recovery again, and do a full wipe again to be safe, and install ARHD. Leave it for 5m to boot, should work.
Thanks for the advices guys. Unfortunately, none of the methods changed any of the results of my 2nd Sensation. It would still not boot the bigger ARHD or Elengancia ROMs (what appears to be Sense ROMs). However, it boots on CM9 ROMs (like TouchCream or Extreme Sensation). I have an identical phone that's a little older, which I've used as the "control" in my experiment. I've been using pretty much the exact same files and steps that you've mentioned, but my 2nd Sensation wouldn't go past the boot screen, even after 30m of waiting (meanwhile, my 1st Sensation has already finished its first boot within 5m). This happens every single time...frustrating! Please note that my 1st Sensation is also going through the exact same steps, just so I can eliminate obvious software or user errors. Anyways, I'm pretty happy at least I'm able to run TouchCream2.1 on this phone and enjoy pretty much all the functions that the HTC Sensation has to offer after I install the suitable apps & widgets. Thanks again!
Hello guys, sorry for my english, I am writing to put my problem that is plaguing me for days.
I have a htc desire hd was previously a 2.3.5 with sense 3.0, I tried to do this firmware directly from the root with a guide xda but without success. Once this is done I prepare to do the downgrade. After a few tries I managed to do the downgrade and have the ClockworkMod "ace hack kit". The problem is that when I go to install the custom rom (in my case the blackout incredible 4.0) proceeds smoothly with the installation hangs at boot time and the initial htc screen. The only way to return the phone function is to install the rom PD98IMG by the bootloader.
Obviously installing this rom I have to redo the procedure of s-off, kernel etc from hack_ace.
How can I solve this problem?
Thanks in advance
ps: I just noticed that I have the htc screen after the proceedings dell'hack_ace. Once you go to install the kernel and radio phone hangs (but manages to get safely into recovery, bootloader etc.)
up