I've just rooted and installed Viper ROM on my ATT HTC m9 and everything works great except I can't receive phone calls. The phone never even rings. I've also flashed ICE and ARHD with no success receiving phone calls. If I restore to a TWRP backup of stock the phone works perfectly so it's obviously something to do with the ROM.
I've checked the other posts on here and none of the fixes have worked, yet. I wanted to try to RUU but whenever I run the RUU application (windows 8.1) the progress bar to initialize the setup completes and the program closes. It never does a flash. I've tried running as admin, disabling services, and running in Win7 compatibility mode to no success.
Do any of you have any ideas on either of these?
mdomino said:
I've just rooted and installed Viper ROM on my ATT HTC m9 and everything works great except I can't receive phone calls. The phone never even rings. I've also flashed ICE and ARHD with no success receiving phone calls. If I restore to a TWRP backup of stock the phone works perfectly so it's obviously something to do with the ROM.
I've checked the other posts on here and none of the fixes have worked, yet. I wanted to try to RUU but whenever I run the RUU application (windows 8.1) the progress bar to initialize the setup completes and the program closes. It never does a flash. I've tried running as admin, disabling services, and running in Win7 compatibility mode to no success.
Do any of you have any ideas on either of these?
Click to expand...
Click to collapse
I had this happen too and it's still kind of a mystery as to what causes it. Did you see this thread? My posts in there are everything I did to fix this, but I can't say exactly what step fixed it. http://forum.xda-developers.com/one-m9/help/unable-to-receive-phone-calls-t3137209
I haven't had the issue in about three weeks now, so whatever it was is apparently fixed. I'm on ICE 3.0.1 with no issue. A definite short-term fix is to do steps 2 or 3 of post #3 in the above link. I suspect it has something to do with either the radio not reading the default.xml file properly or the default.xml file not containing the correct voLte settings.
jollywhitefoot said:
I had this happen too and it's still kind of a mystery as to what causes it. Did you see this thread? My posts in there are everything I did to fix this, but I can't say exactly what step fixed it. http://forum.xda-developers.com/one-m9/help/unable-to-receive-phone-calls-t3137209
I haven't had the issue in about three weeks now, so whatever it was is apparently fixed. I'm on ICE 3.0.1 with no issue. A definite short-term fix is to do steps 2 or 3 of post #3 in the above link. I suspect it has something to do with either the radio not reading the default.xml file properly or the default.xml file not containing the correct voLte settings.
Click to expand...
Click to collapse
Thanks! I followed your steps and got it working. It seems from what you and Venom support said that the problem is with going directly from the ATT RUU (5.0.2) to a custom 5.1 ROM. Once I flashed the developer edition RUU and edited the default.xml I was able to flash ViperROM and have calls working without any further tinkering.
Thanks a ton!
mdomino said:
Thanks! I followed your steps and got it working. It seems from what you and Venom support said that the problem is with going directly from the ATT RUU (5.0.2) to a custom 5.1 ROM. Once I flashed the developer edition RUU and edited the default.xml I was able to flash ViperROM and have calls working without any further tinkering.
Thanks a ton!
Click to expand...
Click to collapse
Thanks for the feedback. That's weird though because I couldn't even receive calls on the developer edition.
I couldn't make calls until editing the default.XML in developer edition. I'm still not sure how it works but I'm happy either way!
Sent from my HTC One M9 using XDA Free mobile app
Related
Hello. I have a problem with sound in my kaiser with Android. I tried 2 systems [Cynanogen mod 6 (Froyo) and Myn's Warm Donut], 4 radios (from 1.71 to 1.65) and 2 kernels. Sound never appeared. Why?
what zimage or nbh you using if you are using a older one it might have problems
Did you mean kernel? the newest from this page:
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
it may be that you have muted the media volume in settings.
No. I don't have any sound. Not only media. When someone calls to me, I cannot hear him too and this person cant hear me too.
Audio issue
I have the same problem. I tried different builds and nothing helps. Any suggestions??
Just a thought, but have you tried flashing a stock rom, then flashing to nand again? Flashing a stock rom clears the entire nand, leaving no possibility of stray bits of data left from custom roms.
I have to say, I get the same thing, but with a slight variation. Sound works for me up until i make at least one call (but could happen before that). Once I make that call, either during the call, or after, the sound is gone. I too had myn's donut, and then frayo, and both times, the exact same problem. I will try to flash the stock rom, and then back to android, but it is a problem that I also share.
This is my first post on xda, so please be nice!
<refresh>.
Mu_aawiyah said:
I have to say, I get the same thing, but with a slight variation. Sound works for me up until i make at least one call (but could happen before that). Once I make that call, either during the call, or after, the sound is gone. I too had myn's donut, and then frayo, and both times, the exact same problem. I will try to flash the stock rom, and then back to android, but it is a problem that I also share.
This is my first post on xda, so please be nice!
Click to expand...
Click to collapse
Yeah, flashed it back to a the most recent stock rom, and then back to andriod.. how works perfectly. Sorry i didnt tell you guys earlier.
I think it was to do with the radio thingy-ma-jig. I flashed it with winmo 6.1 from htc website, and then back again.
Now i'm runnying frayo.
I flashed the newest stock rom from htc site too, then 1.65 radio, but it didn't help :/
Wagierek said:
I flashed the newest stock rom from htc site too, then 1.65 radio, but it didn't help :/
Click to expand...
Click to collapse
That is most likely because you didnt flash it right. take the .nhb from it, plug it into your sd card and flash it from sd. try that.
I'm not stupid. I always flash anything like that-not via CustomRUU-because I have damaged my USB socket and now my Kaiser cannot be recognized by computer.
PS: Today when I booted my Kaiser, next to ANDROID word, I saw "handset status changed to 1". When I rebooted, it didn't show. What's this?
Wagierek said:
I'm not stupid. I always flash anything like that-not via CustomRUU-because I have damaged my USB socket and now my Kaiser cannot be recognized by computer.
PS: Today when I booted my Kaiser, next to ANDROID word, I saw "handset status changed to 1". When I rebooted, it didn't show. What's this?
Click to expand...
Click to collapse
Well, with regards to how I got it fixed (the detailed explanation), i flashed it with a custom winmob rom initially, but surprisingly, the same problem i had with android was happening with the winmob. I could make a call after reboot, but after that call, the sound completely died, and the camera did not work. So i tried to flash with the latest stock rom. I've uploaded the actual roms i used on my public drop box folder here => "i tried posting the link, but because i'm new, it wouldnt allow me...pm me"
I am not a professional on flashing, rather i am a beginner. My tytn 2 is a european T-mobile version. I tried to flash it, it did it half way...then stopped! I tried to do it again, but then it just said "...loading..." and would not go past it. But when i booted to my custom rom, it was still there, but the problems had gone. I guessed that it flashed the radio, and nothing else.
When i then went to android, it worked perfectly.
That was my journey.
I hope that helped... maybe.
Unfortunately, it didn't help.
Any other ideas?
I solved mine by changing radio ROM,but i lost sound and camera in windows,any ROM that fit both android and windows???
What version did you flash?
1.65.14.06
Me too!
I flahsed froyo last night and didn't test after makng calls. I'm having the same issue (lose sound after a phone call). I followed the sticky guide and sim unlocked the radio before flashing (which I think I had already done before). I will try changing radios when I get home to see if this resolves the issue and post my results.
Update: I flashed 1.71.09.01 on my ATT Tilt and this fixed the issue. Now sound and camera work great. Phone runs faster also!
Okay so the other night i went and decided to flash the UK 2.2 firmware specifically 3.4.2.155 then flashed Pay's ROM and it went well. Instantly fell in love with how smooth everything ran without blurr. However.. as everyone warned I lost 3G and Wifi Calling.... and I love those things.
Did the adb push of those 3G fix files for 6.19 T-Mobile that user rob_t put together...http://forum.xda-developers.com/showthread.php?t=897445
However after rebooting i was simply stuck on moto logo... the wretched bootloop... and was forced to go back to US froyo...which after using Pay's rom just seemed unbearably slow...
Any reason that the 3G fix only seemed to bootloop me?
I really want Pay's ROM but I must have 3G
http://forum.xda-developers.com/showthread.php?t=944258
try these fixes dude...
i using pays rom and 3g is normally working.
phanikiranss said:
http://forum.xda-developers.com/showthread.php?t=944258
try these fixes dude...
Click to expand...
Click to collapse
I finally got it working. These files were a big help since I didnt have to mess with adb myself.. (I suck at command script)
I am running jboogies ginger now... and its pretty awesome but no built in tether like Pay's rom....
Ill try it on for a week.
Thanks for pointing me in the right way again
If this thread is still open - can someone please help me. I am on Pays rom and used the zip patch, so I have data working. However, market works intermittently, and I get an error message with roughly half the data downloaded and have to keep pressing 'retry' to get everything loaded. Also, when downloading an app, the first time or even a few times, it downloads the data but doesn't initiate the install. After I click 'download' it goes back to the market screen (as usual), and I have to quickly open the link for the app that I'm downloading so it brings up the app homepage and then it will actually download/install.
Is this normal? I initially didn't wipe after flashing the rom per Pays instructions, and since have wiped and reinstalled the patch to see if that worked...but it hasn't and still doing the above.
Anyone have the same problem? Any fix? Thanks in advance for any help! Oh, and same for browser internet...keep getting error message. And I used the APN settings that is on wife's stock tmous defy.
darule_2011 said:
If this thread is still open - can someone please help me. I am on Pays rom and used the zip patch, so I have data working. However, market works intermittently, and I get an error message with roughly half the data downloaded and have to keep pressing 'retry' to get everything loaded. Also, when downloading an app, the first time or even a few times, it downloads the data but doesn't initiate the install. After I click 'download' it goes back to the market screen (as usual), and I have to quickly open the link for the app that I'm downloading so it brings up the app homepage and then it will actually download/install.
Is this normal? I initially didn't wipe after flashing the rom per Pays instructions, and since have wiped and reinstalled the patch to see if that worked...but it hasn't and still doing the above.
Anyone have the same problem? Any fix? Thanks in advance for any help! Oh, and same for browser internet...keep getting error message. And I used the APN settings that is on wife's stock tmous defy.
Click to expand...
Click to collapse
I would make a new thread I think your problem is much different than mine was and I think people will overlook your question on a resolved thread
ketonkss4 said:
I would make a new thread I think your problem is much different than mine was and I think people will overlook your question on a resolved thread
Click to expand...
Click to collapse
Ended up getting it resolved with that baseband changer on here (v3.1 worked as v3.0 wasn't working).
Thanks for the reply though...I kinda figured my post would be lost at sea given that the thread was in resolved status
Did you ever get it working on Pays or did you end up staying with jboogie?
OK sooo, while making some last-minute checks before posting this thread, I finally found the solution to my problem. It was actually quite obvious if you think about it for a second, but I'll post this anyway just in case someone runs into this problem, as I spent hours figuring this one out.
Just as a reminder of my shame and stupidity, I'll just say that even with years of experience on most PC OS, and as many years troubleshouting on any of those, it didn't occur to me that I should just google the exact error message. Instead, I spent countless hours scouring forums, guides, wikis and whatnot to no avail. Also did countless google searches, just not with the exact error message. So if you're stuck anywhere on any operating system, and have an error message, just remember : GOOGLE THE DAMN ERROR MESSAGE !
So, first and foremost, the solution : go into sms app>settings and search for service center number. Then google your provider's service center number. If they're different, that's probably your problem right here. Write down the one you have just in case, and put in the one you found. Problem solved !
What happened is that while trying to resolve the APN problem and before using the info from another rom, I found some bad informations regarding my operator. I used it, including something that I thought was unrelated to sms. Well it was, and it broke the functionality.
But wait, I still have a question !
Now I'm back on stock 1.82.405.1 with S-OFF and plan to root again tonight or tomorrow following instructions in that thread : http://forum.xda-developers.com/showthread.php?t=1107911.
I plan on backing up everything (including APNs) and do it all over again. Anything I should worry about (like, not doing some specific part because I already have S-OFF) or will it be just fine ?
Here is my unfinished original message, just in case someone searches for a similar problem :
Hi,
So, I always wanted to root my Desire Z to have more control/apps/etc, and finally decided to do it yesterday. Now I have a problem, SMS won't work any more. I tested with the rooted 1.34, CM7.0.3, go sms pro, the stock app, handcent, and any combination of those. Not working.
Everything else went perfectly fine, except the sms. I had issues regarding APNs (no internet, mms), but found the info and all was working nice in cm7. Except sms.
I also tried to go unroot and go back to stock rom, no luck.
Now, I'm not sure at which point this happened between being stock and being on CM7. Here are the steps I followed :
Base situation was : stock rom 1.82.xxx (last OTA update), INFOCID was htc_102
The phone itself is a Desire Z with german keyboard (QWERTZ physical keybord)
So, I Rooted using this guide : http://forum.xda-developers.com/showthread.php?t=1107911.
Everything worked nice, nothing to report. Didn't test sms at that point though.
Backed up with ROM manager.
Then, I installed CM7.0.3 and google apps using their wiki (http://wiki.cyanogenmod.com/wiki/HTC_Vision:_Radio_and_CyanogenMod). Backed up with rom manager.
At that point, internet and mms didn't work because of a lack of APNs, so I found suitable info (restored my 1.34 save, exported apns, re-restored CM7, import apns) and everything was working like a charm.
I noticed that the phone seemed to lose data connexion quite often, but not sure if I was just unlucky or if there was a problem.
Still, everything worked nicely, except sms.
Now, that's a problem obviously, so after reading countless threads vaguely related to my problem, the consensus seemed to be "flash again". Well I did it, it didn't help.
So I thought screw that, I'll return to stock. Which is what I did. I used this guide : http://forum.xda-developers.com/showthread.php?t=835971 .
I used the 1.34 rooted rom, and the factory 1.72 from the RUU found here : http://forum.xda-developers.com/showthread.php?t=971109&highlight=vanilla+rom
I took extra care of the versions number, and didn't have to change the misc.img as in the guide, everything went smooth. Well, except it didn't turn S-ON back when I flashed the factory, so i'm still S-OFF.
I updated up to 1.82.405.1
I figured I could restore S-ON using this : http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#radio_S-ON_and_original_CID
But that doesn't seem to address my sms problem.
So, I am back on stock but with S-OFF, got a part7 and part17 backups (no idea what part17 is for, but it looks like it was created before rooting attempt).
Ideally, I'd like to re-root and go to whatever nice rom is out there, but what I want right now is sms working. Sending gives me a message after a while saying "Couldn't send text message after multiple tries". Can't send to myself or other people. Not sure if I can recieve (but I think I can't). MMS/internet works fine which is why I think it's not APN-related.
Click to expand...
Click to collapse
Hi I pretty much know nothing about custom roms etc but I was forced to go for a custom ROM due to a friend wiping my phone but when I flashed Viper 3.2.1 everything was fine except the wifi button was greyed out, I also tried android revolution and the same problem occured. However it was fine when i tried candy5 but once i flashed google play the wifi stopped working again.
Does anyone know what the problem is and how i should fix it? thanks.
Hope you are on latest 4.4.4 firmware , link for the same should be in OP/FAQ of Viper.
fandam said:
Hi I pretty much know nothing about custom roms etc but I was forced to go for a custom ROM due to a friend wiping my phone but when I flashed Viper 3.2.1 everything was fine except the wifi button was greyed out, I also tried android revolution and the same problem occured. However it was fine when i tried candy5 but once i flashed google play the wifi stopped working again.
Does anyone know what the problem is and how i should fix it? thanks.
Click to expand...
Click to collapse
If you are only unlocked and not s-off you will need to manually flash the corresponding boot.img for each rom each time you flash a new rom. If you can get s-off you won't need to do this anymore.
Firmware needs to be updated. Confirmed on OP's other thread here: http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-bricked-t2989202/page2
Also its not necessary to manually extract and flash boot.img on the M8, even when s-on. Folks giving this advice may be carrying over knowledge from an older HTC device.
I have searched all over and couldn't find any answers, so hopefully this isn't a repeat thread.
I just purchased the HTC desire 816 and upgraded to it. I activated it, and set everything up, Saturday. Sunday after trying to load xposed onto it, it froze on the boot screen.
I managed to restore it from fastboot, and got it updated to lollipop.
Now for the problem, and what I have tried:
The phone will not see bluetooth devices at all.
First I tried simply a factory reset, which allowed it to see my smart watch and start to connect to it. Part way through the setup of my watch, it lost it's connection.
Next I tried a wipe and restore to full stock, this did not allow me to see any bluetooth devices.
Then I tried rooting, cwm, and putting kitkat back on the phone. I still couldn't see bluetooth, and now I am trying to upgrade back to lollipop.
I am at a loss as to what may be the problem, but I need it to work with bluetooth.
I have tested it with both my LG G smartwatch, and a gemline bluetooth speaker.
OK, so a little update here. I did a full stock & root flash last night.
The wifi began working, and Bluetooth was connected to my smartwatch.
This morning, wifi is still working and bluetooth can't see any devices.
On a side note, I am trying to figure out what version of xposed to install on my phone.
tenchu98 said:
OK, so a little update here. I did a full stock & root flash last night.
The wifi began working, and Bluetooth was connected to my smartwatch.
This morning, wifi is still working and bluetooth can't see any devices.
On a side note, I am trying to figure out what version of xposed to install on my phone.
Click to expand...
Click to collapse
If you're on 5.0 lollipop then 21. If you're on CM 12.1 (5.1) then 22. I have this same device and carrier and haven't had any issues like you're describing other than a few Bluetooth dropouts every once in a while. Good luck.
http://forum.xda-developers.com/showthread.php?t=3034811
thoctor said:
If you're on 5.0 lollipop then 21. If you're on CM 12.1 (5.1) then 22. I have this same device and carrier and haven't had any issues like you're describing other than a few Bluetooth dropouts every once in a while. Good luck.
http://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
I went back to full stock, and relocked the bootloader, because HTC said that it was an issue with the bootloader being unlocked. I doubted them, and it turns out I was right to doubt. The issue isn't fixed, and I seem to have narrowed it down to the searching function. My HTC can't see any discoverable items.
I have a gemline speaker, which has NFC to pair Bluetooth built-in, and my phone is unable to see it when I try to use NFC enabled pairing.
I am suspicious that somewhere along the lines the bluetooth files became corrupted in system. I have been trying to find a way to put the original ones back on, but haven't been able to find a way. I really want to get this working, and remove root.
Why do I not want root, because my kids enjoy pokemon go and it won't run on root anymore.
tenchu98 said:
I went back to full stock, and relocked the bootloader, because HTC said that it was an issue with the bootloader being unlocked. I doubted them, and it turns out I was right to doubt. The issue isn't fixed, and I seem to have narrowed it down to the searching function. My HTC can't see any discoverable items.
I have a gemline speaker, which has NFC to pair Bluetooth built-in, and my phone is unable to see it when I try to use NFC enabled pairing.
Click to expand...
Click to collapse
Yeah, that's a load of crap so you were right to question that. My bootloader stays unlocked and I don't have any Bluetooth issues other than the ones noted for running CM custom roms and the headset dropouts. I have 3 different Bluetooth devices linked to my phone and no issues pairing any others either.
I am suspicious that somewhere along the lines the bluetooth files became corrupted in system. I have been trying to find a way to put the original ones back on, but haven't been able to find a way. I really want to get this working, and remove root.
Why do I not want root, because my kids enjoy pokemon go and it won't run on root anymore.
Click to expand...
Click to collapse
You could find and flash back your stock recovery and then find either the stock RUU file or the stock Rom.zip file and flash back to stock. I understand about root. It's getting to the point my next device will probably stay stock but I'm having my fun now.
thoctor said:
Yeah, that's a load of crap so you were right to question that. My bootloader stays unlocked and I don't have any Bluetooth issues other than the ones noted for running CM custom roms and the headset dropouts. I have 3 different Bluetooth devices linked to my phone and no issues pairing any others either.
You could find and flash back your stock recovery and then find either the stock RUU file or the stock Rom.zip file and flash back to stock. I understand about root. It's getting to the point my next device will probably stay stock but I'm having my fun now.
Click to expand...
Click to collapse
I did this once already, I am thinking that my next step will be to manually copy the bluetooth related files from the system image into system using root
then flash unsupersu.zip
So I hav replace every bluetooth related file I can think of, and even deleted some file suggested online, and my phone still doesn't see other devices. When I put my phone on my NFc enabled speaker it acts like it is going to pair, but then says "unable to pair gemline speaker".
I am beginning to become frustrated.