• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Help sought with Desire confusion

H

Hubert_Hubert

Newbie
Hi all,

First: my apologies - I've searched the forums for weeks but am still mighty confused.

Where I am: I'm running CM 7.2.0.1, neither the wifi nor the gps work and the phone signal isn't great either and there is still some T-mobile branding left over at boot.

How I got there: When I bought the Desire it was rooted & running Leedroid. I changed it to Cyanogen 7.2.0 and it was fine for a while. Then I notice that wifi had stopped worked and - thinking that this might help somehow - went to 7.2.0.1. This didn't help and gps stopped working (which I now know is commonplace). Thinking I'd go back to basics I tried to install Oxygen (did all the wiping prior to install) but found that it got stuck in a sort of twitchy loop after it booted up and so I gave up on it and went back to CM. Then I think I tried to update the radio via CWM recovery but it ended up getting stuck in the 'seven vibrations and won't boot' thing. Freaked out, I installed a stock T-mobile RUU (they're my carrier):
RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed.exe
To my relief, this worked. I then put it back into cyanogen and that's where I am.

But if I try to install any other ROMs or RUU's or Radios then I just go straight back to the 'seven vibrations and won't boot' thing again and have to repeat the T-Mobile RUU to get my phone back. So I'm running CM 7201 with what seems like poor radio functionality & I'm stuck with the ugly T-Mobile purple circle every time the phone boots to remind me that I can't figure out how to sort any of this out.

I would be very grateful for any advice about how to get out of this situation and a) get better radio-related functionality back and b) if possible ditch the purple t-mobile circle thing.

Here's the info:

- Revolutionary -
Bravo PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031D
TOUCH PANEL-SYNT0101
RADIO-4.06.00.02_2
Aug 10 2010, 17:52:18

I've got adb set up on my pc etc.

Many thanks in advance for any responses.
HH

PS: Just seem to have fixed gps using the link from post #26 here. I'd still be pleased to hear about other suggestions for the other issues tho'!
 
The experts here may have better ideas but have you tried the official HTC Gingerbread RUU from shipped-roms.com http://shipped-roms.com/download.php?model=Bravo&file=HTC_Desire_Android_2.3_Upgrade.zip it includes the latest radio.

You will then need to run Revolutionary to get S-Off & Flash a recovery. The experts are now recommending 4EXT recovery which can be applied via an app from the play store once S-Off.

To get rid of your T-Mobile circle thing (boot image) read this:

http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html

Alernatively you can use a utility like Android Flasher or Fastboot Commander.

Give Oxygen another try once complete. I use it with no boot, wifi or GPS problems.
 
Thank you very much for your response, nicka3200. I've just obeyed the suggestion in your sig and popped in a quick nandroid backup just to be on the safe side.

Am I right in thinking then that the purple circle thing is just a boot image and nothing more? It doesn't indicate anything going on under the hood then?

I'll have a look at the RUU you suggested. For some reason my Firefox always struggles with the Shipped roms site and won't download. I've just tried it with chrome and it's fine though (this has also been one of the things I've scratched my head about regarding sorting this phone). I've already got 4ext installed so can probably just restore it via titanium when (if) I pop the new ruu on. I'm still concerned that it'll just hit the '7 vibration and no boot' problem again though...

(thanks again tho'!)
 
I ran the old backup as per shauny13's suggestion. Voila: back to 7.2.0 CM with working GPS and - so it seems for the minute, anyway - wifi too. Cool!

That damn purple circle & phone buzz is still there at boot though before the skateboarding droid shows up - I'd love to get rid of that. Any ideas?
 
I just tried to run the RUU above (http://shipped-roms.com/download.php?model=Bravo&file=HTC_Desire_Android_2 .3_Upgrade.zip)

It installed OK but when booting all I get it - once again - is the HTC screen and the dreaded 7 vibrations of doom. Nothing else.

Currently reloading the only RUU I have that seems to actually produce a bootable phone: RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed.exe

Any suggestions as to why this keeps happening would be most gratefully received!
 
noticed, your s-off. Have you tried flashing the downgrade image first from alpharev, then running the ruu upgrade?
 
You're suggesting I downgrade my HBOOT by flashing one from alpharev? Why would that be useful, could you say? I'd really like to understand.

(I also see to have just 'accidentally' installed CWM 4.0.1.4 while fannying about. Not sure if this is such a cool thing to have done. Will try to get 4ext back)...
 
now i'm confused. You've got cwm recovery and working? Can you do a full wipe/factory reset from recovery and then flash a new rom?
 
I did the backup thing, that worked fine but - Mr.restless that I am - I thought I'd try to use the RUU linked to above (with the newer radio) to try to lose the remains of the branding & upgrade my radio. That didn't work and I ended up stuck in the 'no boot 7 vibrations' situation again. So I ran the ruu that does work, the t-mobile one again.

Then - and this is not smart - I ran revolutionary thinking Ok perhaps I need root again. It said I didn't but it suggested I might like to install CWM recovery. I thought why not and said yes. It installed 4.0.1.4.

Then I ran evo3 to get an earlier cwm. (Don't quite know why...)

Currently installing 4ext and aiming to re-apply that backup that worked...
 
is the card partitioned? can you full wipe and flash a different rom?

Been through your original post again and it said update radio from recovery? This is done with fastboot not recovery.
 
shauny13 said:
Been through your original post again and it said update radio from recovery? This is done with fastboot not recovery.
Click to expand...

Ah, OK, that's useful, thanks.

As for ROM's I'm fairly happy with cm7. I'd sooner try to flash a generic RUU to get rid of the boot stuff and update the radio and then go back to a clean, radio-upgraded cm7 but it only seems to want to let me flash this one t-mobile RUU rather than a generic one & I don't understand why. I've had the card partitioned before and running with S2E etc.

But it's running CM7.2 again now with gps and wifi which is pretty damn cool after a month without either so thanks for the backup suggestion.
 
Thought I would install a slightly earlier radio - just to be a bit less bleeding edge and all - and opted for 5.10.05.17_2. Installed via fastboot and...

got the damn 7 vibes of doom again.

Bugger.

------------> Re-install t-mob ruu all over again etc...
 
5.17.05.23 isn't exactly bleeding edge - it's about 15 months old IIRC, and I've been using it for more than a year :)

So what ROM did you have installed?
 
Hadron said:
5.17.05.23 isn't exactly bleeding edge - it's about 15 months old IIRC, and I've been using it for more than a year :)

So what ROM did you have installed?
Click to expand...

Ah. Ok.

I had CM7.2 running. But the radio update via fastboot produced the 7 vibes of doom again. :(

Mainly, I wish I understood why this was happening.
 
Crikey!

This one just went on!:ruu_bravo_froyo_htc_wwe_2.29.405.2_radio_32.49.00.32u_5.11.05.27_release_151783_signed.exe

Most unexpected. A quick peek at the info under -revolutionary- now tells me I'm running the 5.11.05.27 radio too. Which is good news I think. I shall now attempt to pop 4ext and then a back up with cm7 on it and see what happens...!
 
Well it's progress - it gives you a working phone with a newer radio.

But it's a real puzzle why flashing other RUUs or radios should cause problems (RUUs flash radios, so the RUU part may be a red herring, but that's at least as odd).
 
You must log in or register to reply here.
Back
Top Bottom