Hi There, I'll try and keep this short, this is regarding my brothers Desire HD:
he's running MIUI 1.7.8 - no problems. Ril 2.2.0018G, Radio 12.54.60.25U_26.09.04.11_M2
We thought we'd try a new ROM, did the usual, wiped data, dalvik cache etc etc. installed Cyanogen 7.0.3 through CWM
He prefers this new ROM. set everything up, then discovered a strange problem, an active call is dropped when the proximity sensor turns the screen off. I looked this problem up (someone else experienced it and did a "fastboot oem eraseconfig" I tried this and it said successful but didnt cure the problem...
I tried to flash the RIL 2.2.0018G in CWM (It said it flashed successful, but when i booted into the ROM, it still had the old RIL installed with the ROM not the new one i just flashed.
One other thing, the Radio that I had was: 12.54.60.25U_26.09.04.11_M2, something strange, the U changed to P after i installed Cyanogen7 ???
I used Nandroid to restore MIUI and the P changed back to a U, the RIL was obviously changed to the one that came with the MIUI ROM and all is now working again.
Q1, Why couldn't i flash a new RIL under Cyanogen (was i doing it wrong - just a normal flash through CWM?)
Q2, Why did the U change to a P in the radio name when i installed Cyanogen?
Q3, Any ideas to the cause of the dropped calls (if not answered in Q1 or Q2)?
I tried, but it still turned into a longer post. sorry.
thanks for your help.
Kevin
I'm not an expert, but I believe RILs can only be flashed in the recovery console. I know I flashed mine there and it worked. No idea why the letter changed
RILs can be safely flashed in CWM, with minimal harm. But do make sure that md5 provided by the dev is matching with yours. If the RIL is restored after rebooting, maybe the RIL is tied with the stock radio. Plus, RIL does not has any effect in AOSP rom.
The radio prefix can change due to rom/radio own setting and region. Read this http://forum.xda-developers.com/showthread.php?t=1068874
Reason of dropped call may caused by dialer that flagged as open application and would kill itself if its clashed with screen off command. Try to reflash/change kernel.
Sent from my HTC Desire HD using XDA App
to use cmd with the phone in fastboot mode you need the "fastboot.exe" file, also you need to make sure the cmd directory points in the correct path. Could be why you didn't actually flash anything.
Related
Hello,
at first sorry for my bad english, I hope u could understand
This is my Desire:
MIUI 1.7.1 - Android 2.3.4
Eng S-Off
Hboot 0.85.2007
Radio 26.08.03.07_M
Baseband 12.35d.60.140fp
Kernel 2.6.35.13-LorDmodUE-V5.0
My problem is, that BT doesn't work for me! I turned it on...after a few seconds the switch returns back into off position.
I tried everything, full wipe, wipe script, etc...
I rooted my DHD out of the box, so I don't know if it worked in the beginning! I never used BT before, but now I got a BT Car Radio...and now I need it of course! I thought the problem is the Radio maybe, so I tried to flash the Revolution Rom with the corresponding Radio...but it still don't work!
Any suggestion for that problem?
No ideas??
Update everything in your DHD. MIUI 1.7.15 already out there, use recommended radio 12.54.60.25_26.9.4.11_M2 and also fresh LordModv6.1cfs/bfs kernel.
Sent from my HTC Desire HD using XDA App
EDIT: latest MIUI 1.7.22 and the radio above is my preferred radio
flashed your preffered radio and lordmod 6.1 cfs...but it still dont work
Wiped everything, also formated the hole sd card
Logcat says :
Bt_enable_impl : timeout vor hci device to come up
Whoa, there's no need to wipe out the whole sd card! Hmmm, I'm feeling guilty right now. Okay, usually changing the mix of kernel does the trick though. Have you tried to revert to stock rom?
Sent from my HTC Desire HD using XDA App
I have the same problem when my battery is over 80%. If I restart my phone after the battery drops below 80% then my bluetooth turns on. I am running Cyanogen 7 nightly with LordModUE 6.3 and radio .09.04.11.
Sent from my Desire HD using XDA App
drpsyko said:
Whoa, there's no need to wipe out the whole sd card! Hmmm, I'm feeling guilty right now. Okay, usually changing the mix of kernel does the trick though. Have you tried to revert to stock rom?
Click to expand...
Click to collapse
No problem mate...I thought that could not actually be the problem...but that was my last hope so I wanted to exclude all possibilities! I have backuped everything before formatting, so do not worry...
I tried the Revolution Rom with corresponding kernel/radio...also without success...i will now try the stock rom...
did you try using another radio?
it could also be hardware related
So I recently installed MIUI, and as soon as I did my Wifi radio stopped working. Every time I try to switch it, it turns back off and says "error."
I figured this was a problem with my radio (26.02.01.15_M2) when I found another irksome problem. When I go to flash PC10IMG.zip the bootloader gets to "Checking PC10IMG.zip) and then quits and refuses to attempt the update.
Any ideas?
I apologize if this question has been asked, but I couldn't find anything similar in the short search I did.
Thanks in advance!
Could be a bad download? Which Radio are you trying to flash?
Download the radio from here http://forum.xda-developers.com/showthread.php?t=970809
Dont know what ROM you are running but Vision_Radio_12.52. 60.25_26.08.04.30 seems to be a good one,download the attached file for wiping the EFS(Important when flashing radios)
The link has further instructions and information,hope that helps
Hey, thanks for your response! I actually tried three different Radios from that thread (the first three), and none of them worked. I ran an efs wipe yesterday because I was having GPS problems, and these problems persisted after that...
FWIW, when I flash other kernels/ROMs, things work fine (CM7, PyroMod, Stock) but on MIUI these problems crop up.
alexonfyre said:
Hey, thanks for your response! I actually tried three different Radios from that thread (the first three), and none of them worked. I ran an efs wipe yesterday because I was having GPS problems, and these problems persisted after that...
FWIW, when I flash other kernels/ROMs, things work fine (CM7, PyroMod, Stock) but on MIUI these problems crop up.
Click to expand...
Click to collapse
Do you mean you can update the radio with other ROMs or do you mean that the wifi problem is only on MIUI?If your problem is only with MIUI cant help as I dont use that ROM but still doesnt explain your problem with flashing a radio as the bootloader is independent of the ROM
I think the wifi radio and the cellular radio are different and when you flash the radio firmware, it only updates the cellular radio firmware. Someone more knowledgable than me will probably correct me. It's probably something screwy with the MIUI roms which is effecting you. If you want to use MIUI then try one of the other MIUI roms that are out there and also notify the developer of the MIUI rom your using about your issue.
I hate the recent radios for G2 latest one from Bell sucks. Signal drops every few seconds, data connection is just OK. Very disappointed. I did the efs wipe and auto ril matcher V6 and all this other bs and I hate it.
Sent from my HTC Vision using xda premium
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!
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 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