EDIT: SOLVED!!!! it was a usb brick. see last post for details.
hi all,
I have a problem with my desire.
Bluetooth won't turn on. If I try to enable BT, it says grey'ed out for like 10 secs and the goes back to unchecked.
I got this device used so I don't have many background information. All I can tell is I tried different ROMs and wiped all I could, but still no luck. I actually highly suspect this might be an hardware issues, but I'd really like to try everything before shipping back to assistance.
Here are my current specs:
htc desire amoled
bravo pvt1 ship s-on
hboot 0.80.0000
radio 5.11.05.27
rom cyanogenmod 7.1.0
kernel 2.6.37.6-cyanogenmod-geb50077
Recovery: Clockworkmod
ANY hint highly appreciated.
Got exactly the same problem.
BT worked while running the former stable CM release. I first noticed this issue when flashing latest CM. You tried other ROMs which didnt work?
Did you try other Radios as well?
I am not an expert, but I think it could be a problem of the radio. I never totally understood what the radio does, so could anybody help with this guess? I never changed Radio as there was no need for (never touch a running system).
lexo, did you try rolling back to 7.0.3 to see if BT would work again?
I was also thinking about radio, exp b\c it seems to not be a ROM-specific issue, as I have tried several: LeeDroid, InsertCoin, MIUI, as well as a stock rom.
I believe the point with radio is not necessarily about having the latest, but finding the one that works well with one's rom. Also, there is RIL, but that I don't know what it does.
No, didnt try that yet.
I use BT in my car to listen to music only so I didnt notice the issue at first. Now i am thinking about buying Galaxy Nexus, so I am not too exited about that point. But as I am willing to pass my Desire to my lil sister I would love to have it fixed.
Whats "RIL"? Think I never heard about it.
Don't know if this is relevant but had a similar problem with Bluetooth, wifi and Mobile data yesterday. None of them had connectivity!
The remedy that worked for me was to wipe the cache and dalvik, reflash CM7.1 via recovery (but remember to also flash the Google apps package) and soft reset.
No data is lost this way.
Hope that helps!
Sent from my HTC Desire using XDA App
This may not be relevant but when I couldn't enable Bluetooth on my done when I have a USB brick.....
Try the USB brick fix it may work
Sent from my HTC Desire using XDA App
update:
so far I did:
- wiped everything including dalvik and reflashed cm7 - no luck
- removed files in etc/bluetooth [read somewhere] - nuthing
- applyied a .zip update that is supposed to fix a possible USB brick - no change.
@LEXO: I think you might try the first two things I did, in your case they might work.
So now I flashed a RUU Rom and reverted to stock s-on bootloader, hboot, radio (ril, too, I believe, though I dunno how to tell ril version) and recovery.
The only thing I'm not completely sure about is the USB brick fix, but otherwise it's ready to ship to assistance.
@Reaper, can you point me to the USB fix you referred to?
guys!!! Thanks everyone, expecially reaper.
My BT is working again!!! turn out it was a USB brick, which I was able to solve fairly easy.
I had tried a usb brick fix that involved flashing a .zip, which I did. However still no BT changed so I assumed phone was not bricked after all.
Also, I always assumed usb brick would involve major cd and usb connect malfunctions, and that was not my case at all.
However it must have been that fix that didn't work, because I then followed the guide on this forum http://forum.xda-developers.com/showthread.php?t=691639: got my CID via fastboot, modified the files accordingly, put them on sd card, got temp root with visionary, issued the necessary commands with "free root system tool" terminal, rebooted, and voilà! BT is finally green.
I can't believe I made it!
Related
Hey all, long time lurker, first time poster....unfortunately....
So after sitting on MIUI for a good while, and having a blast with it, I decided to try out some other ROMs. I was interested in seeing Cyanogen 6, and so I went about attempting to get the latest stable, non RC ROM onto my EVO. I read into it seeing that I needed to downgrade my hboot, and found the image without a problem (running the .76 right now, had the 9something one before...)
Well, I downgraded my hboot without an issue, flashed the Cyanogen, and got into a splashloop. I figured out it was becaue I hadn't wiped my cache or data before flashing the rom, so I went into the Clockwork Recovery and wiped those, flashed once more, and it booted into Cyanogen perfectly!
Well, almost. I don't have 3G now.
For some reason, I am unable to connect to 3G no matter what I try. My nandroid's broke due to the hboot downgrading, rewiping the cache/data and reflashing cyanogen did nothing, and now for some reason, when I attempt to go back to MIUI, it still will not allow me to connect to 3G. I can send and receive texts, and make and receive calls, but alas, no data connection.
Should I get a fresh RUU and stock hboot, upgrade and restart from scratch? I just want to get back to MIUI at this point with a working, data enabled phone.....
If that's the case, that I do need to start over, where can I find a new hboot for the EVO that isn't .76? I'm pretty saavy when it comes to this stuff, but for some reason right now I just can't figure it out....
HTC EVO running MIUI v0.11 stable
.76 hboot w/ Clockwork recovery
Broken nand backup
whatdo?
Thanks in advance for the help
Sorry for the double post, but I resolved my issue.
I am unsure of what exactly went wrong, but I figured it was somewhere between downgrading my hboot, and flashing the CM 6 stable ROM that my 3G data got scrambled....
So! Using ROM Manager, I made a backup of my working (non 3G) MIUI image, and flashed the Odyxed version of the RUU found here (http://forum.xda-developers.com/showthread.php?t=836728). After flashing in Recovery, it booted into SenseUI, and worked like a charm!
My 3G hath returned, and issues have been solved. It's nice when you're able to fix things on your own, though I couldn't have done it without the help of that handy dandy search button, and the RUU keyword
Oh, yeah, and I guess xxbabiboi228xx as well.....maybe....^_~
Hi,
please excuse this possibly dumb questions, but ..
In short: I've flashed 20 Roms in the past 3 weeks i think (trying to solve GPS-Issues). I've never had any Problems with the Phone signal and wifi itself, regardless wich ROm/Radio/RIL.
Now suddenly my Phone Signal sometimes goes within seconds from 5 Bars to zero and back. Often when i restart my DHD the full reception is back for 2 or 3 minutes.
This happens on every rom and radio. Now i used the RUU 1.32 to make everything like original - but still the Problem remains.
Is it (technically) possible that upgrading my radio with the PDIMG98.zip method damaged my phone antenna or the software? I think it started when i started to flash radios that way. or could it be a certain Rom/Radio/RIL combination that did the damage? Or a damage because of wiping efs-data?
Could there be a tiny software-issue remaining somewhere in the radio-software that can't be corrected via using the RUU? How original is the DHD after using the RUU?
Thank you very much,
Nasobem
hmm it's quite hard to say. it can be a software or a hardware related problem.
try to reflash to a rom/radio/ril combination which worked for you. if that doesn't work, flash a RUU. after flashing a ruu, your DHD will be completely stock, but it will not remove Radio S-OFF and Super CID, just use jkoljo's tool to set it back to stock.
if it's still not working, its probably related to a faulty hardware, but i'm sure that it's not related to flashing.
Thank you
based on you suggenstion i'v got a plan now: first i'll wipe efs-data again, just to be sure, then RUU again and S-On. If it doesn't work, i'll send it to HTC wich i had in mind anyway, my GPS could not be fixed with software
Hello, I'm new here to this and to the flashing stuff and rest.
I wanted to do some change to my buzz so I just flashed my 2.2.1 to 2.3.7 (CyanogenMod-7.1.0.1).
Everything was fine, flashed Gapps also.
The only thing is my wi-fi isn't working.
It can't even connect. It's like refreshing by 3 secs and doing that in a circle.
/// What I Did:
- Reflashed CyanogenMod twice.
- Reflashed my radio (the newest version anyway).
/// Specs:
- Android 2.3.7
- CyanogenMod-7.1.0.1
- Radio 3.35.20.10
- HBOOt 6.01.1002
- S-OFF
Did everything today and WiFi was working in the morning perfectly (on 2.2.1)
Just let me know if you want to know something more. Thanks guys.
Heard that Regulatory domain may cause that problem. Tips?
There is a cm mod 7.2 and that must fix it i think
Sent from my HTC Wildfire using xda app-developers app
wilek619 said:
Hello, I'm new here to this and to the flashing stuff and rest.
I wanted to do some change to my buzz so I just flashed my 2.2.1 to 2.3.7 (CyanogenMod-7.1.0.1).
Everything was fine, flashed Gapps also.
The only thing is my wi-fi isn't working.
It can't even connect. It's like refreshing by 3 secs and doing that in a circle.
Click to expand...
Click to collapse
first of all: you asked if regulatory domain could have to do with your problem. If you have access to your WiFi's settings you could check that by simply changing the channels (the procedure for that might be totally different in different routers). From my experience I doubt it anyway but I might be wrong here.
Another possibility to check if your phone's WiFi works or not would be to log into a different network - no idea if you could do that.
The reason I'm suggesting this first is, we could of course suggest things you might try with your phone - but - if your WiFi is the problem this might take some days and wasting lots of posts without any result or help
Did you do wipe all? I think if you installed CyanogenMod 7.2 it would be ok then. Give a try
Some tests that you can do:
- Flash an older radio, to see if the radio didn't got corrupted somehow. Reboot the phone and then flash the newer again;
- Flash the stable CM7.2;
Did you have issues with the stock ROM and the wifi?
Sent from my badass HTC Wildfire.
Hi,
I have just started having problems with my HD Desire which is running Mikes Revolution HD 7.0.4 ROM. It seems that everytime I get out of range of my wireless connection, the phone will shutdown in a very short time and then is impossible to restart. It will get to the splash screen and then shutdown again. I can however restart the phone in recovery and the battery will show that it has a good charge. The phone will also shutdown at various times even when my wireless network is available, but not as quickly or as frequently. I know that it isn't the ROM as I tried a different ROM (after a complete wipe) and the problem persisted. I was wondering if these problems might be down to the battery finally giving up and not being able to provuide enough current to keep the phone on and that searching for a network is putting too much strain on the battery. I don't know if this is a common problem, but any advice will be very welcome. I am using the recommended radio for the ROM and the phone has been working properly and well for nearly a year since it was hacked. Phone does work fine when it is plugged in.
Many thanks
Ian
Did you do a Super Wipe ..?
you can find it here http://goo.gl/hWSCt
What is your radio version is it 12.65.60.29_26.14.04.28_M radio ..?
you can download it from here http://goo.gl/vdP8g
I think it is flashing issue.. and I recommend Android Revolution HD 6.3.3 for you because it is very stable ROM :good:
Before flashing a radio, exhaust all other options (that is if you don't have any experience flashing them). It isn't something to take lightly.
Sent from a dream.
I don't think it is a ROM problem as I did use Superwipe and I had the exact same problem with two entirely different ROMs. Android Revolution 7.0.4 and IceColdSandwich 8.1.1. I have been running 7.0.4 since it was first released by Mike. Also the phone acts normally when plugged in (sorry forgot to mention that in first post).
My Radio is: 12.65.60.29U_26.14.04.28_M
Go back to your stock ROM and see if the issues persist. If it still does, then it might be a hardware issue...if not, find a custom ROM that does not do it..
gizmo001i said:
I don't think it is a ROM problem as I did use Superwipe and I had the exact same problem with two entirely different ROMs. Android Revolution 7.0.4 and IceColdSandwich 8.1.1. I have been running 7.0.4 since it was first released by Mike. Also the phone acts normally when plugged in (sorry forgot to mention that in first post).
My Radio is: 12.65.60.29U_26.14.04.28_M
Click to expand...
Click to collapse
Dont use the superwipe script. Do a manual wipe. Wipe everything.
Take out the sd card, use a different one or backup your sd card, wipe it, DO NOT PUT THE FILES BACK IN, just a new rom to try to see if problem persists.
If it does, possibly it's a hardware issue.
Try all the different combinations, could be either a bad file in the sd card or a bad sd card and so on or what was mentioned before.
Sent from a dream.
Hi XDA people,
This is my first post in XDA and its a problem i am facing. Whenever i switch to GSM/WCDMA Mode and start using the 3G internet, the phone restarts with 5 - 7 vibrating alerts. I did searched this forum before posting and got similar posting for HTC Buzz
BIG ISSUE: 3G problem..!!
http://forum.xda-developers.com/showthread.php?t=1823816
Went through that and found out that by updating the radio this problem can be fixed, so went ahead to find the udpated radio and hboot and updated them using RUU, got a tutorial for the same in XDA forums
So updated Radio from 7.53.39.03M to 7.54.39.28M
Hboot : 1.08.0000
But the problem is still there, as soon as i switch it to 3G mode, i can see the H symol comes up for the GPRS and the network changes to R (Roaming- no clues why this happens but i am fine with this as long it works.) and within minutes it restarts making 5-7 vibrating alerts before rebooting.
can someone help me with this, is there a way to fix this for HTC Wildfire S (Marvel)
Kernel : [email protected] #2
Android version : 2.3.5
Htc Sense : 2.1
Software Number : HenseMod 7
tonan791 said:
Hi XDA people,
This is my first post in XDA and its a problem i am facing. Whenever i switch to GSM/WCDMA Mode and start using the 3G internet, the phone restarts with 5 - 7 vibrating alerts. I did searched this forum before posting and got similar posting for HTC Buzz
BIG ISSUE: 3G problem..!!
http://forum.xda-developers.com/showthread.php?t=1823816
Went through that and found out that by updating the radio this problem can be fixed, so went ahead to find the udpated radio and hboot and updated them using RUU, got a tutorial for the same in XDA forums
So updated Radio from 7.53.39.03M to 7.54.39.28M
Hboot : 1.08.0000
But the problem is still there, as soon as i switch it to 3G mode, i can see the H symol comes up for the GPRS and the network changes to R (Roaming- no clues why this happens but i am fine with this as long it works.) and within minutes it restarts making 5-7 vibrating alerts before rebooting.
can someone help me with this, is there a way to fix this for HTC Wildfire S (Marvel)
Kernel : [email protected] #2
Android version : 2.3.5
Htc Sense : 2.1
Software Number : HenseMod 7
Click to expand...
Click to collapse
it happened to me, the only solution I found was flash the backup of my original Rom Sense PREROOT, turn on 3G and check that it worked.
Then without turning off the 3G flash another rom clean (a bit like the problem of the gps).
is a bit long but I was going crazy, my Willy sometimes restarted.
it may be useful with my HTC Buzz it worked ... but you're rooted?
quack75 said:
it happened to me, the only solution I found was flash the backup of my original Rom Sense PREROOT, turn on 3G and check that it worked.
Then without turning off the 3G flash another rom clean (a bit like the problem of the gps).
is a bit long but I was going crazy, my Willy sometimes restarted.
it may be useful with my HTC Buzz it worked ... but you're rooted?
Click to expand...
Click to collapse
Yes i am rooted, also i dont have any stock backup
I read in the forums that in HTC buzz if you update to an older radio then wipe cache then update to a higher radio version it fixes it, but i need to find out if that would work for MARVEL, and what would be versions that i should switch to.
thanks for the help
tonan791 said:
Yes i am rooted, also i dont have any stock backup
I read in the forums that in HTC buzz if you update to an older radio then wipe cache then update to a higher radio version it fixes it, but i need to find out if that would work for MARVEL, and what would be versions that i should switch to.
thanks for the help
Click to expand...
Click to collapse
tonan791 said:
Hi Eventcom, i went through the forum and found that you too had this same problem of bootloop after switching to 3g. I see that you have Buzz, just wanted to know will this simiar fix (update older radio, wipe cache, update to newer radio) can be applied on HTC wildfire Marvel as well.
I have posted my question after a lot of search, got similar threads for BUZZ but none for MARVEL, can you please help.
http://forum.xda-developers.com/showthread.php?p=31998311
Click to expand...
Click to collapse
Well, I don't know anything about the Marvel. Both phones are quite different besides their names and enclosure.
Anyway I don't think that your phones radio will be touched when flashing a ROM or restoring a nandroid backup or that you could wipe, clear or format your radio partition - so in theory it could work with the Marvel, too.
A short explanation about the whole thing: The Buzz has well known issues with the radio (no GPS or BT, WiFi probs) - even directly after rooting and flashing the first custom ROM. There's also a chance that something might go wrong or get messed up when flashing different ROMs, installing tweaks etc. and the problem is that the radio resides on a separate partition which can't be wiped or formatted. All this sounds pretty logical to me but I'm not a developer so I might be totally wrong
The solution seems to be to flash a different radio (older/newer doesn't matter) to "overwrite" the current one - and sometimes reflash the current ROM again.
The problem I had has been hard to spot and even harder to solve. Luckily I found out that switching on 3G initiated the reboots (after quite a while and by accident, really). I made a lot of tests and could put it down to that (WiFi, 2G had no probs - phone rebooted only when switching to 3G or switching on data when 3G has been activated/chosen).
Furthermore I found the "solution" by accident, too: I reflashed the current radio without any success. Then I also tried an older radio - no success. So, as a final attempt, I started to download a RUU to reset the phone to factory condition.
The download server has been awful slow - it took ages to download the file - so I (almost randomly) decided to flash the previous radio again.
I couldn't believe it: that did the trick. (Luckily) I rebooted again, switched on data and 3G and noticed that the phone didn't reboot anymore.
So if you're able to flash a different radio - just give it a try. For the Buzz you need to be S-OFF to flash a radio - no idea about your phones.
I'd be glad if that would work for the Marvel, too :fingers-crossed:
I found this tread
http://forum.xda-developers.com/showthread.php?t=1485345
if you do not solve in any other way you could give it a try
I do not know the Marvel, but the Buzz htc are not all the same, the same solution to different results :silly:
eventcom said:
Well, I don't know anything about the Marvel. Both phones are quite different besides their names and enclosure.
Anyway I don't think that your phones radio will be touched when flashing a ROM or restoring a nandroid backup or that you could wipe, clear or format your radio partition - so in theory it could work with the Marvel, too.
A short explanation about the whole thing: The Buzz has well known issues with the radio (no GPS or BT, WiFi probs) - even directly after rooting and flashing the first custom ROM. There's also a chance that something might go wrong or get messed up when flashing different ROMs, installing tweaks etc. and the problem is that the radio resides on a separate partition which can't be wiped or formatted. All this sounds pretty logical to me but I'm not a developer so I might be totally wrong
The solution seems to be to flash a different radio (older/newer doesn't matter) to "overwrite" the current one - and sometimes reflash the current ROM again.
The problem I had has been hard to spot and even harder to solve. Luckily I found out that switching on 3G initiated the reboots (after quite a while and by accident, really). I made a lot of tests and could put it down to that (WiFi, 2G had no probs - phone rebooted only when switching to 3G or switching on data when 3G has been activated/chosen).
Furthermore I found the "solution" by accident, too: I reflashed the current radio without any success. Then I also tried an older radio - no success. So, as a final attempt, I started to download a RUU to reset the phone to factory condition.
The download server has been awful slow - it took ages to download the file - so I (almost randomly) decided to flash the previous radio again.
I couldn't believe it: that did the trick. (Luckily) I rebooted again, switched on data and 3G and noticed that the phone didn't reboot anymore.
So if you're able to flash a different radio - just give it a try. For the Buzz you need to be S-OFF to flash a radio - no idea about your phones.
I'd be glad if that would work for the Marvel, too :fingers-crossed:
Click to expand...
Click to collapse
Thankyou Eventcom, i will try the method, i am searcing for the Radio to downgrade and upgrade too, i did find a link here in xda will search for that again and see if that resolves my problem, thankyou for the details, appreiciate it