Hello everybody.
I'm new here as you can see, and pretty new to the world of android.
I've searched but I couldn't find any s specific answers for my questions.
I started off with a stock Desire and rooted it and installed CM7, one of the earlier ones I think.While I was at this I changed it from s-on to s-off.
Things were fine for the first two months untill my phone started to go down hill.
MY camera flash first stopped working, and then my flash light all together.
Then then camera, headphone jack, and lastly the ability to change to headphone mode when something was plugged into the jack.
I've updated to the newest cm7 build and even tried a nighlty build.
Earlier today I wiped everything an installed MildWild ROM.
I'm still experiencing all the same problems. Can anybody help me fix any of the above problems? The most important being the camera
Summary/Phone Stats
Rooted:
S-off
running 2.3.7
2.6.35.14_r3stable Kernal
32.48.00.32u_5.11.05.14 Baseband
Any replies would be appreciated.
Thanks.
Try to go back to stock and if persists, then it's probably a hardware fault.
stankyou said:
Try to go back to stock and if persists, then it's probably a hardware fault.
Click to expand...
Click to collapse
I'll have a go of that tonight and see. Thanks
Related
After installing Radio 2.05.00.06.11 (dinc_ota.zip), my handset speaker audio disappears. Speakerphone and bluetooth work fine, but no luck with the internal speaker.
Heres the kicker:
Once I restore the 1.0 Radio, the internal speaker starts working again.
After lots of searching, this seems to be a very intermittent problem. I've only found two other people experiencing the same issue. Unfortunately I have not found a solution.
Does anybody have any idea as to what my next step should be to try and solve this?
Thanks!
I have the same problem...
heega1 said:
After installing Radio 2.05.00.06.11 (dinc_ota.zip), my handset speaker audio disappears. Speakerphone and bluetooth work fine, but no luck with the internal speaker.
Heres the kicker:
Once I restore the 1.0 Radio, the internal speaker starts working again.
After lots of searching, this seems to be a very intermittent problem. I've only found two other people experiencing the same issue. Unfortunately I have not found a solution.
Does anybody have any idea as to what my next step should be to try and solve this?
Thanks!
Click to expand...
Click to collapse
Try downloading a fresh copy of the update and running it again?
It's working just fine for too many people for it to be a problem with the update itself.
douger1957 said:
Try downloading a fresh copy of the update and running it again?
It's working just fine for too many people for it to be a problem with the update itself.
Click to expand...
Click to collapse
updating the radio twice will brick the phone! same one that is.
zeke1988 said:
updating the radio twice will brick the phone! same one that is.
Click to expand...
Click to collapse
not exactly. but, this radio isnt a image, its a patch. and a double patch is not the same thing... there is no error checking. dont do it!
I've tried re-installing the update 3 times from three sources. At first I thought it was the Froyo update so I went back to my nand backup and that didn't help, but once I downgraded the baseband it magically started working again.
So I tried it again. Re-downloading all the tools and packages. Only for it to happen again right after the Radio update. So I reverted back, cleared everything to factory, did a fresh install, then did the upgrade once more.... Still same problem.
Since it is such an intermittent issue, I'm thinking that maybe the hardware is to blame. The particular handset that I have is a warranty replacement from Verizon (blown speakers on first one). Maybe that has something to do with it.
Anyone have any other theories?
Thanks!
So I'm stumped. It's a pretty straightforward process, and I can't see where I'm going wrong.
Next Step: Warranty Replacement. We'll see if that helps. I'll be sure to record the serial number and other details of the phone before I send it back. Maybe we can find a pattern.
It will be a couple days before the new phone arrives. If you have something I can try, please suggest away!
Thanks!
I am having the exact same problem. I have tried both 2.x radios and both have the same effect. I want to use froyo but the only way to is to use speakerphone or a plugged in headset. I tried to take it in yesterday but the tech at verizonwireless told me to wait it out until 2.2 comes out to see if that fixes my problems. ( went in stock told them I was having the problem on stock radio) final problem being is when official does come out and it kills my headset speaker is it going to be too late to root my phone knowing the replacement I get will already be loaded with the new software.
Chicken and Egg
Unfortunately, unrEVOked has not developed a S-ON patch. This means that you will either have to take stock 2.2 which will be unrootable -or- you will patch forever, have S-OFF, get stock 2.2 and not be able to return the phone if the problem doesn't clear up.
Please keep that in mind when making your decision.
The replacement phone worked...
Not sure what the problem was, but it confirms my method for installing 2.2 wasn't flawed..
Thanks for all your help!
-j
I am trying to get verizon to send me a new one. They are not being very helpful right now. They said the audio issue is a software issue that should be fixed with the new update but might send me a new phone due to number of dropped calls. I have to stop in store tomorrow
Hello,
I tried searching but coudnt find an answer, I have had my EVO for about 3 months now and recently rooted phone+installed myn's warm 2.2 rls3, shortly after doing so my phone would randomly go into roaming, if i try to make an outgoing call it gives me some error that verizon coudnt verify my phone (iam on sprint)
ALso, i have been having constant issues with my sms not going out, it gives me error that my network radio timedout .......
Has anyone ran into this problem after flashing a new rom?
http://forum.xda-developers.com/forumdisplay.php?f=652
raul602 said:
Hello,
I tried searching but coudnt find an answer, I have had my EVO for about 3 months now and recently rooted phone+installed myn's warm 2.2 rls3, shortly after doing so my phone would randomly go into roaming, if i try to make an outgoing call it gives me some error that verizon coudnt verify my phone (iam on sprint)
ALso, i have been having constant issues with my sms not going out, it gives me error that my network radio timedout .......
Has anyone ran into this problem after flashing a new rom?
Click to expand...
Click to collapse
what HW version do you have? most likely it's due to the HW version. My hw v002 doesn't work well with 3.30 builds (RLS 3 is one of them).... but works great with 3.29 builds (RLS 2)
You can find your HW version by Menu > Settings > About Phone > Hardware
jerdog said:
what HW version do you have? most likely it's due to the HW version. My hw v002 doesn't work well with 3.30 builds (RLS 3 is one of them).... but works great with 3.29 builds (RLS 2)
You can find your HW version by Menu > Settings > About Phone > Hardware
Click to expand...
Click to collapse
Hey thanks for the heads up, my hardware version is "0003" could this be the problem? if so how can i update/upgrade it?
Anyone else ever have this problem?
raul602 said:
Hey thanks for the heads up, my hardware version is "0003" could this be the problem? if so how can i update/upgrade it?
Anyone else ever have this problem?
Click to expand...
Click to collapse
First, I'd try doing a nandroid backup, wiping Cache, Dalvik, and data, then reinstalling Warm 2.2.
If you have an old nandroid backup, you can try restoring that, if you use Amon's recovery, it can backup some stuff Clockwork can't.
If those don't work, you probably have a radio problem, which is a bit... harder... to fix. What rooting method did you use? Did it require you to flash new radios?
phajen said:
First, I'd try doing a nandroid backup, wiping Cache, Dalvik, and data, then reinstalling Warm 2.2.
If you have an old nandroid backup, you can try restoring that, if you use Amon's recovery, it can backup some stuff Clockwork can't.
If those don't work, you probably have a radio problem, which is a bit... harder... to fix. What rooting method did you use? Did it require you to flash new radios?
Click to expand...
Click to collapse
I will give it a shot later today to see if hte problem persist. I rooted it by doing the unrevoked method,
raul602 said:
Hey thanks for the heads up, my hardware version is "0003" could this be the problem? if so how can i update/upgrade it?
Anyone else ever have this problem?
Click to expand...
Click to collapse
You can't change the HW version. Late HW 003's (in the last month) have the new camera hardware and all the 004's do. Only the Evo's that shipped with 3.30 have the new hardware.
It could be the problem given you have older hardware. All the 3.30 ROMs I have tried on my HW 002 would have terrible lag and once I went back to a 3.29 ROM things have been peachy. And I start completely from scratch each time I use a new ROM (clear temp, reboot back to recovery, format all, reboot back to recovery, flash rom)
Is this 002 and 3.30 problem for everyone or are there others besides me who don't have any problems.
There is something different enough (IMHO) in the framewor between late-model 003/004 and 002 that any 3.30 ROM gives problems to hw ver 002. I had nothing but issues on any 3.30 ROM but went to Azrael 2.5 (newly built exclusively for early-model 003 and lower utilizing build 3.29) and have had no problems at all.
I even tried stock 3.30 and had issues... but stock 3.29 didn't.
For me the proof is in the pudding....
Sent from my PC36100 using XDA App
I have hardware version 0003. I've been using rls3 since release (which is 3.30) and have yet to have a single issue. Been using HTC 17 kernel for a week or so. My evo is smooth as glass and flies(as it does with all of myns roms). Never had a fc or any error for that matter, so Idunno. One thing I've learned is that all evos are different, and react differently to different software, even if two have the same HW version, they can still act totally different with the same mods. So I don't know how I feel about the 3.30 being strictly for HW 0004. it works perfectly for me...
Sent from my PC36100 using XDA App
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!
Right now my G2 is running Cyanogenmod-7.1.0 RC1. For the last few months any time I try to update past this version of the rom I lose my microphone. It works absolutely fine with 7.1 but when I go to 7.2 it breaks. For example, When I am on a call I can hear the other person but it is silent on my end. Voice recording programs do not work either, all that it records is a low level of static noise.
I have also tried CM9 and audacity beta4 with the exact same results. When I flash my phone back to 7.1 everything is fine.
Is there some way that I can flash just the old microphone drivers onto the new roms? I am competent enough to follow instructions but not enough to start breaking builds apart for the individual pieces so I don't know where to start.
I have always done a full wipe on everything before I flash.
Does anyone have any ideas? Thank you!
Currently I am running:
Radio: 12.52.60.25U_26.08.04.30_M3
Kernal: [email protected] #1
Mod: Cyanogenmod-7.1.0 RC1 vision
Build number: GRJ22
a
Didn't try any of those,
but this rom:
http://forum.xda-developers.com/showthread.php?t=1492461
works great on my HTC Desire Z with absolutely no issues
It does take a bit of customizing.
I've tried that rom as well but have a whole different issue with that one for some reason. I flash it and then start to reboot and once the phone gets to the white htc screen it freezes with a few horizontal lines running across it. I have to pull the battery and then flash back to my older rom. I have no idea what is going wrong there.
Here might be a dumb question...
Would it help to flash a new kernal? Are the appropriate kernals included in the roms already?
haymaker said:
I've tried that rom as well but have a whole different issue with that one for some reason. I flash it and then start to reboot and once the phone gets to the white htc screen it freezes with a few horizontal lines running across it. I have to pull the battery and then flash back to my older rom. I have no idea what is going wrong there.
Here might be a dumb question...
Would it help to flash a new kernal? Are the appropriate kernals included in the roms already?
Click to expand...
Click to collapse
Hi! Do you solve your problem? I have the same thing there. All the CM roms above 7.0.3 not working with microphone. Do you have still the Cyanogenmod-7.1.0 RC1 file rom and can you upload for me?
Thank you!
I have a used (out of warranty) DINC 2 rooted with Cyanogenmod 7.2 installed (Page Plus). The phone has been working fine for about a month. All of the sudden, the phone will not turn on unless I remove the battery first. If I remove the battery and boot the phone, everything is fine until I turn it off and then it won't come back on. If I do a complete shut-down, then it will turn on. I tried wiping the cache - no help. I tried restoring an old backup that was working at the time - no help. Any ideas? What should I try next to debug this?
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
brymaster5000 said:
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
Click to expand...
Click to collapse
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
rh09 said:
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
Click to expand...
Click to collapse
UPDATE: I think I might have figured it out. I borrowed a battery from another phone and it seems to work fine with a different battery. Anyone have recommendations for a good aftermarket battery (not extended) for the DINC2?
UPDATE 2: The "fix" didn't last. The same problem resumed after an hour or so on the other battery. Still open to suggestions.
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
vforaci said:
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
Click to expand...
Click to collapse
I don't have any bootlooping - the phone was working great with CM7.2 until this started happening. Can't figure out what caused it. How well is CM10 running on your DINC2 (like, performance-wise)? (Assuming that's the phone you have.)
Performance is better than Viper and yes I have the Dinc2.
What is the turbo engine? I've never used or heard of it. I did have reboot issues with the early builds of cm10. I just flashed psycho's new 4.2.2 build & it seems to be quicker than evervlov. I need to give a couple days though.