I was playing around with the nightly build of CM10.1, and my radio stopped working. I flashed what I thought was the stock ROM back with Odin, but then I started receiving an, "Insert SIM Card" message whenever I tried to enable Mobile Data. So I flashed another one I found online. Still, with no luck (though the error was gone), I tried some radios. A dozen radios later, and I can get 3G data -- but still no calls or texts. I've been updating the PRL non-stop, still no luck (except when I'm roaming.)
I'm guessing the problem has to do with the many many files I have in /system/etc/firmware
Is there anyway I can get my radio back to stock?
Thanks!
you need a full odin flash with repartition. do not do this till you know for sure you have the right files to use. you can screw **** up with odin pretty damn quick. lemme search and ill see if i can find the right stuff for you.
EDIT:
I am downloading the files you will need to flash in odin. I want to see that they are indeed the correct ones for you to use. If you need help i can remote connect to your pc and help you out.
22 mins left on the DL and then ill be back
loggedinasroot said:
I was playing around with the nightly build of CM10.1, and my radio stopped working. I flashed what I thought was the stock ROM back with Odin, but then I started receiving an, "Insert SIM Card" message whenever I tried to enable Mobile Data. So I flashed another one I found online. Still, with no luck (though the error was gone), I tried some radios. A dozen radios later, and I can get 3G data -- but still no calls or texts. I've been updating the PRL non-stop, still no luck (except when I'm roaming.)
I'm guessing the problem has to do with the many many files I have in /system/etc/firmware
Is there anyway I can get my radio back to stock?
Thanks!
Click to expand...
Click to collapse
first rule of posting on any forum, "no question is dumb"
Rule number 2 " always ask if there is something you need fixed or need help with"
dont worry youre not dumb. though i may not be able to help you, the person above me hopefully will.
Quick answer from my own findings, the original stock ROM had a bug that doesn't allow it to see the SIM properly, but if you patch it (settings, update - or something like that), it will fix it (there will likely be a few rounds of updates).
bonduniverse said:
Quick answer from my own findings, the original stock ROM had a bug that doesn't allow it to see the SIM properly, but if you patch it (settings, update - or something like that), it will fix it (there will likely be a few rounds of updates).
Click to expand...
Click to collapse
Thanks!
The ROMs at Sumsung-Updates.com seem to be trustworthy. Are they?
Anyway, I finally got the issued resolved. It wasn't a radio problem that was blocking me, it was a badly linked Google Voice account. Sprint killed it, and now everything's OK (though I signed up again ^_^)
loggedinasroot said:
Thanks!
The ROMs at Sumsung-Updates.com seem to be trustworthy. Are they?
Anyway, I finally got the issued resolved. It wasn't a radio problem that was blocking me, it was a badly linked Google Voice account. Sprint killed it, and now everything's OK (though I signed up again ^_^)
Click to expand...
Click to collapse
I had the same problem with the sim card thing...linked it to my wifi and it downloaded like 15 updates and then finally started working normally...probably incorrect stock rom or seriously old...got the one from samsung-updates and that works flawlessly
I updated to official Lollipop rom on Canadian Note 3 (SM-N900W8) and hit with big WiFi issue. I searched xda and couldn't find the solution. How can I say, Phone don't remember my WiFi after I reboot phone. I have to re-select the WiFi, re-input password and it connects fine. But next reboot, It won't even remember the WiFi i connected to and have to redo all steps again. Anyone with same issue..pleas help.
WiFi issue, what rom?
raju_xda said:
I updated to official Lollipop rom on Canadian Note 3 (SM-N900W8) and hit with big WiFi issue. I searched xda and couldn't find the solution. How can I say, Phone don't remember my WiFi after I reboot phone. I have to re-select the WiFi, re-input password and it connects fine. But next reboot, It won't even remember the WiFi i connected to and have to redo all steps again. Anyone with same issue..pleas help.
Click to expand...
Click to collapse
So I'm actually a little bit curious, what official n900w8 rom are you talking about. I've been looking for one for some time now and nothing. Please link if you can.
With regards to the WiFi. I have heard of this before. People with S5 have reported almost similar issues and solution was a script edit.
There has been ports of the new N900t lollipop rom that after a proper kernel "lean kernel" and a S5 WiFi fix. All this has worked on the n900w8 however video recording and nfc don't work.
I'm really curious as to what your set up is.
I went back to 4.4 because I use nfc so much and video recording is a must.
Thanls so much
VOLTS
Lollipop released for Canadian Note 3 SM-N900W8. Telus, Bell and virgin mobile release 5.0 two days back. See link http://www.sammobile.com/firmwares/database/SM-N900W8/
Have you fixed this?
I have the same problem. I tried editing the build.prop file as suggested on some posts for the 900T but it seems that my phone is not detecting root correctly, so even editing the file reverts when power cycling the phone
raju_xda said:
I updated to official Lollipop rom on Canadian Note 3 (SM-N900W8) and hit with big WiFi issue. I searched xda and couldn't find the solution. How can I say, Phone don't remember my WiFi after I reboot phone. I have to re-select the WiFi, re-input password and it connects fine. But next reboot, It won't even remember the WiFi i connected to and have to redo all steps again. Anyone with same issue..pleas help.
Click to expand...
Click to collapse
Fix Wifi
Edit build.prop ro.securestorage.support and ro.securestorage.knox from true to false. If they are already false change to true and then back to false. Reboot.
You must fix your root issue first, before you can apply this fix...
Good luck
Äx
Thanks. I went back to custom rom with custom kernel on sm-n900w8. I will try once flash official rom. NFC not working in Custom rom.
Custom rom
raju_xda said:
Thanks. I went back to custom rom with custom kernel on sm-n900w8. I will try once flash official rom. NFC not working in Custom rom.
Click to expand...
Click to collapse
I have the rom installed in my N900W8 and at first I was suffering from the WiFi password not saving. However after a few complete wipes both in twrm and in the data wipe service menu.
Now with 5.0 and with lean kernel my passwords save.
So there is a way for it to save and mine works.
AxAtAx said:
Fix Wifi
Edit build.prop ro.securestorage.support and ro.securestorage.knox from true to false. If they are already false change to true and then back to false. Reboot.
You must fix your root issue first, before you can apply this fix...
Good luck
Äx
Click to expand...
Click to collapse
Actually I am using your vision international ROM, works great. I flashed official rom but was too bloated and slow and video recording was not working. Your rom is awesome and fast and already debloted. Only thing not working is NFC which I don't use anyway. Great work..keep it up.
VoltsLee said:
I have the rom installed in my N900W8 and at first I was suffering from the WiFi password not saving. However after a few complete wipes both in twrm and in the data wipe service menu.
Now with 5.0 and with lean kernel my passwords save.
So there is a way for it to save and mine works.
Click to expand...
Click to collapse
If lean kernel custom kernel? If everything works I. E. NFC, video recording.
raju_xda said:
Actually I am using your vision international ROM, works great. I flashed official rom but was too bloated and slow and video recording was not working. Your rom is awesome and fast and already debloted. Only thing not working is NFC which I don't use anyway. Great work..keep it up.
Click to expand...
Click to collapse
Nice, I was going to say, try a different kernel.:good:
Hello to everyone! I have Samsung Ace 2x (GT-S7560M) with Public Mobile, Canada. After the phone become incredibly lagging, I have decided to flash it with custom ROM, which I successfully did following instructions on this forum (http://forum.xda-developers.com/show...7#post50909757). I like my phone back again, the ROM is amazing.
BUT there are two huge issues - it is not connecting to Mobile Network and Bluetooth can not be enabled. (WiFi connects and working fine).
As I mentioned earlier I am with Public Mobile and able to make calls and recieve/send SMS messages with CM11. After every reboot there is message : "SIM card added. Restart your device to access the mobile network." , which can be easily bypassed by pressing right bottom button (not sure about the name, probably "Escape"). The phone indicates TELUS Network.
I read over the posts on this forum and tried to change settings in Prefered Network to GSM/CDMA auto(PRL). Also checked APN to Public Mobile (tried Telus as well) but no success in getting back 4g network.
Any suggestion? Really do not want to go back to official ROM
novice70 said:
Hello to everyone! I have Samsung Ace 2x (GT-S7560M) with Public Mobile, Canada. After the phone become incredibly lagging, I have decided to flash it with custom ROM, which I successfully did following instructions on this forum (http://forum.xda-developers.com/show...7#post50909757). I like my phone back again, the ROM is amazing.
BUT there are two huge issues - it is not connecting to Mobile Network and Bluetooth can not be enabled. (WiFi connects and working fine).
As I mentioned earlier I am with Public Mobile and able to make calls and recieve/send SMS messages with CM11. After every reboot there is message : "SIM card added. Restart your device to access the mobile network." , which can be easily bypassed by pressing right bottom button (not sure about the name, probably "Escape"). The phone indicates TELUS Network.
I read over the posts on this forum and tried to change settings in Prefered Network to GSM/CDMA auto(PRL). Also checked APN to Public Mobile (tried Telus as well) but no success in getting back 4g network.
Any suggestion? Really do not want to go back to official ROM
Click to expand...
Click to collapse
Unfortunately your issue with Bluetooth is super common with this phone and roms. In fact, as far as I'm aware there's not a single kitkat rom that doesn't disable Bluetooth. You might find a solution buried in one of the other threads pertaining to this phone, but I'm almost positive there's not a solution.
Just about every rom I've flashed for this phone gives me the sim card added message when I start it up, ignoring it is the best fix I've come across. Regarding your inability to connect to a network, it seems you've already tried everything I would have suggested. Which cm11 build did you flash, by the way?
If you can't get that sorted out you aren't stuck with going back to stock. There's also another cm11 build for the IIx/ Trend, as well as Omni 4.4.4, PAC 4.4.4, Beanatalk 4.4.3 and ALLEGEDLY SlimKat (I can't find the download link to save my life, but a few people have said someone ported slimrom to this phone).
Sorry I couldnt be of more help bru.
about my ROM
thank you for response, I am currently using CM11-20141114-UNOFFICIAL-kylessopen (240DPI) with gapps - kk -20140629-signed.
Hmm, the first time I flashed that same build I had quite a few issues and they rectified themselves when I flashed a different gapps. I think it was the January 2014 4.4.4 full package (when I've got some free time in an hour or so I'll let you know the exact one), which I found odd considering it was super out of date and yet cured what ailed me. Next time I flashed it the 20140629 package worked fine though, so who knows. You've tried redownloading that gapps package right? Sometimes an ever so slightly corrupted gapps zip can do this kind of stuff. Unfortunately I'm not super familiar with the ins and outs of this phone since its just to tide me over until I can afford to replace my Note 4 in earnest, so my ability to help here is mostly guesswork and drawing parallells. I hope you get this on the ropes dude. If you can't get it sussed out in the end I'd recommend going with Beanstalk. It doesn't have a working theme engine unfortunately and is ever so slightly more buggy (well, less buggy I. Your case I guess), but it's waaaaaaay more feature rich than either of the cm11 builds. If you value stability more than customization than Omnirom is your best bet. ALL of the roms for this phone are kinda glitchy, but I found Omnirom to be the least so.
I've recently moved to Washington, D.C. for a summer internship as of last Friday. Ever since getting into the area, I have not been able to receive phone calls on my AT&T HTC One M9. I was curious to know if anyone else has had this issue? I am able to make phone calls, use the cellular internet (usually I have LTE service), send text messages, and anything else using the phone service, but the only time I know I get an incoming call is when my phone notifies me that I have a new voicemail message. It also doesn't matter if the phone is "awake" or not. I have had people call me when the phone screen is off and on, with the same result. I commute from Arlington, VA every day, and this issue happens regardless of where I am along my commute.
To further complicate things, if I am in phone conversation and someone calls me, Call Waiting shows up with the incoming call. So I am "able" to receive phone calls, but I do not receive them when I am not in a phone conversation.
Has anyone had a similar problem like this? I'm currently running Android Revolution 5.1 since the latest version has an issue for me where the phone restarts if I try to turn on the screen. Even then, that is not the issue because 8.1 has the same calling issue. I've talked with AT&T tech support and did everything they suggested, when I get home from work I plan on getting a new SIM card to see if that fixes things.
My gut tells me there is either something wrong with the SIM, or for some reason my out-of-state phone number (I have a central Ohio area code) has issues with the towers in the area.
I would reccommend that you try performing a manual roam, go to settings>mobile data>Network operators, let it scan for networks, select a network that is NOT your carrier then once it fails to register select your own carrier, this should update the Mobile HLR and hopefully allow you to receive calls again.
Hope this helps
shark0807 said:
I've recently moved to Washington, D.C. for a summer internship as of last Friday. Ever since getting into the area, I have not been able to receive phone calls on my AT&T HTC One M9. I was curious to know if anyone else has had this issue? I am able to make phone calls, use the cellular internet (usually I have LTE service), send text messages, and anything else using the phone service, but the only time I know I get an incoming call is when my phone notifies me that I have a new voicemail message. It also doesn't matter if the phone is "awake" or not. I have had people call me when the phone screen is off and on, with the same result. I commute from Arlington, VA every day, and this issue happens regardless of where I am along my commute.
To further complicate things, if I am in phone conversation and someone calls me, Call Waiting shows up with the incoming call. So I am "able" to receive phone calls, but I do not receive them when I am not in a phone conversation.
Has anyone had a similar problem like this? I'm currently running Android Revolution 5.1 since the latest version has an issue for me where the phone restarts if I try to turn on the screen. Even then, that is not the issue because 8.1 has the same calling issue. I've talked with AT&T tech support and did everything they suggested, when I get home from work I plan on getting a new SIM card to see if that fixes things.
My gut tells me there is either something wrong with the SIM, or for some reason my out-of-state phone number (I have a central Ohio area code) has issues with the towers in the area.
Click to expand...
Click to collapse
I had this issue last week as well. It came on out of the blue and did all the usual AT&T troubleshooting and technical support. As of Monday, though, I think I have the issue fixed. I don't know if AT&T made a network modification that spurred the issue or if I changed something on my phone. Anyway, I'm not sure exactly what step along the way actually fixed my issue, but here's what I did.
1) Go into mobile data settings and see if turning off "Enhanced 4G LTE services" helps
2) I'm not sure if ARHD has this option, but if you can set your phone disable 4g in mobile data settings, turn 4g off and see if you can receive calls...I bet you can (so that's a temporary solution)
3) Alternatively, you can dial *#*#4636#*#* which will bring you into phone settings. Go into phone information, scroll down and on preferred network type, change that from GSM/WCDMA/LTE auto to GSM or GSM Auto (again this is just a temp fix because basically you're disabling LTE which is not desirable)
If any of those work, then check this file:
system\customize\ACC\default.xml
Scroll to the "Phone" app section
Look for a line "<item type="boolean" name="voLteEnabled">false</item>"
Change that to "true"
(If ARHD is compatible with AT&T, then it's probably already set to true)
If it was set to false, reboot and see if that works (to test, you'll have to undo any changes made in steps 1,2 or 3).
I did a lot of stuff before I did any of the above and Insert Coin (the custom ROM I use) already had the voLte setting set to true so the stuff below might actually be what fixed my issue. The next steps are just not as quick to accomplish as I ran the AT&T Ruu a few times and also flashed the developer ROM.
here's everything that i did...
Ran ATT 1.32.502.31 RUU to confirm that I can receive calls on 100% stock.
Flashed stock developer RUU and I could no longer receive calls.
Flashed custom rom (Insert Coin) and I could still not receive calls.
Ran ATT RUU again and calls suddenly worked again.
Re-flashed developer RUU.
Rooted it
installed root explorer (ES Files Explorer)
navigated to system\customize\ACC\default.xml and made the change explained above
rebooted the phone and I was again able to receive calls on the developer edition
Restored Insert Coin from a backup and i was STILL able to receive calls.
After restoring IC, i checked the default.xml file and noticed that not only was voLte set to true, ALL of the voLte options (there are like 5 of them) were set to true. Then I checked the IC zip file and opened the default.xml from what i was flashing and they were all set to true in the zip file. So I think they were all set to true when I began having problems. So I'm really not sure what fixed this for me. But, like I said, that's everything I did and it's working again.
If you go 100% stock by flashing the AT&T RUU (or if you're able to restore to stock using an untouched system image from TWRP) and still can't receive calls, then get on with AT&T support and have them verify your provisioning.
Sorry if this is not very well organized, but I started having this issue like last Friday and worked on it all weekend and Monday and finally got it resolved Monday night...so needless to say...I tried a lot of different things, but what I've written above is what I believe fixed the issue.
I think the problem is that your area supports voLte but maybe the ROM doesn't. Notice when you make a call that your 4G/LTE icon changes to 4G only. Well, the same is supposed to happen when you receive a call, but for some reason, something isn't allowing the phone to switch to 4g only.
jollywhitefoot said:
I had this issue last week as well. It came on out of the blue and did all the usual AT&T troubleshooting and technical support. As of Monday, though, I think I have the issue fixed. I don't know if AT&T made a network modification that spurred the issue or if I changed something on my phone. Anyway, I'm not sure exactly what step along the way actually fixed my issue, but here's what I did.
1) Go into mobile data settings and see if turning off "Enhanced 4G LTE services" helps
2) I'm not sure if ARHD has this option, but if you can set your phone disable 4g in mobile data settings, turn 4g off and see if you can receive calls...I bet you can (so that's a temporary solution)
3) Alternatively, you can dial *#*#4636#*#* which will bring you into phone settings. Go into phone information, scroll down and on preferred network type, change that from GSM/WCDMA/LTE auto to GSM or GSM Auto (again this is just a temp fix because basically you're disabling LTE which is not desirable)
If any of those work, then check this file:
system\customize\ACC\default.xml
Scroll to the "Phone" app section
Look for a line "<item type="boolean" name="voLteEnabled">false</item>"
Change that to "true"
(If ARHD is compatible with AT&T, then it's probably already set to true)
If it was set to false, reboot and see if that works (to test, you'll have to undo any changes made in steps 1,2 or 3).
I did a lot of stuff before I did any of the above and Insert Coin (the custom ROM I use) already had the voLte setting set to true so the stuff below might actually be what fixed my issue. The next steps are just not as quick to accomplish as I ran the AT&T Ruu a few times and also flashed the developer ROM.
here's everything that i did...
Ran ATT 1.32.502.31 RUU to confirm that I can receive calls on 100% stock.
Flashed stock developer RUU and I could no longer receive calls.
Flashed custom rom (Insert Coin) and I could still not receive calls.
Ran ATT RUU again and calls suddenly worked again.
Re-flashed developer RUU.
Rooted it
installed root explorer (ES Files Explorer)
navigated to system\customize\ACC\default.xml and made the change explained above
rebooted the phone and I was again able to receive calls on the developer edition
Restored Insert Coin from a backup and i was STILL able to receive calls.
After restoring IC, i checked the default.xml file and noticed that not only was voLte set to true, ALL of the voLte options (there are like 5 of them) were set to true. Then I checked the IC zip file and opened the default.xml from what i was flashing and they were all set to true in the zip file. So I think they were all set to true when I began having problems. So I'm really not sure what fixed this for me. But, like I said, that's everything I did and it's working again.
If you go 100% stock by flashing the AT&T RUU (or if you're able to restore to stock using an untouched system image from TWRP) and still can't receive calls, then get on with AT&T support and have them verify your provisioning.
Sorry if this is not very well organized, but I started having this issue like last Friday and worked on it all weekend and Monday and finally got it resolved Monday night...so needless to say...I tried a lot of different things, but what I've written above is what I believe fixed the issue.
I think the problem is that your area supports voLte but maybe the ROM doesn't. Notice when you make a call that your 4G/LTE icon changes to 4G only. Well, the same is supposed to happen when you receive a call, but for some reason, something isn't allowing the phone to switch to 4g only.
Click to expand...
Click to collapse
Friend, you win the internet, turning off 4G and turning it back on did the trick. Thank you!
shark0807 said:
Friend, you win the internet, turning off 4G and turning it back on did the trick.
Click to expand...
Click to collapse
Nice. Glad to hear it. Where did you turn 4G off? In mobile data settings?
shark0807 said:
Thank you!
Click to expand...
Click to collapse
There's a button for that
jollywhitefoot said:
Nice. Glad to hear it. Where did you turn 4G off? In mobile data settings?
There's a button for that
Click to expand...
Click to collapse
Yes, once off of 4G I was able to receive calls again. Now That I'm home I'm trying the .xml edit to see what happens.
EDIT: Tried the .xml edit, didn't work, I will flash the RUU tonight and see what happens.
shark0807 said:
Yes, once off of 4G I was able to receive calls again. Now That I'm home I'm trying the .xml edit to see what happens.
EDIT: Tried the .xml edit, didn't work, I will flash the RUU tonight and see what happens.
Click to expand...
Click to collapse
This happened to me with my M7 on T-Mobile after they added VoLTE and I was forced to toggle off LTE whenever I wanted to use the phone and I could never make it work properly again. Fortunately for you, the M9 supports it so it could be something like tower upgrades thus toggling it off then on made it grab on to different towers...possibly. I was running ViperROM then so it was a quick toggle however it would get frustrating to have to go into settings regularly. Hope you are all fixed for good
shark0807 said:
Yes, once off of 4G I was able to receive calls again. Now That I'm home I'm trying the .xml edit to see what happens.
EDIT: Tried the .xml edit, didn't work, I will flash the RUU tonight and see what happens.
Click to expand...
Click to collapse
Was the XML switch set to false? You could try changing all of the volte switches to true. Also maybe a different custom rom...maybe arhd doesn't support volte at all.
It was, and I did as you suggested, still nothing doing. I've now been trying to use the AT&T RUU to restore everything, but I'm running into problems with that as well. I haven't seen anyone discuss it on this forum, but fastboot and htc_fastboot crash while trying to flash the RUU. First I tried with the .exe of the RUU, which doesn't give me much information except that it crashes. If I do it through command prompt (and a RUU in .zip format), the RUU sends a "pre-update", crashes with an error code FAIL90, tries to do it again, then fastboot and htc_fastboot crash on the computer.
From previous HTC phone forums, it seems like this error happens on Windows 8 and 8.1 computers, but I'm not entirely convinced why my OS in this case would be the problem.
Fastboot error on computer:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: fastboot.exe
Application Version: 0.0.0.0
Application Timestamp: 54bfb0a1
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.17736
Fault Module Timestamp: 550f42c2
Exception Code: c0000005
Exception Offset: 0004248d
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: a10f
Additional Information 4: a10ff7d2bb2516fdc753f9c34fc3b069
And for htc_fastboot:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: htc_fastboot.exe
Application Version: 0.0.0.0
Application Timestamp: 546e94d2
Fault Module Name: StackHash_79f3
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: PCH_27_FROM_htc_fastboot+0x00001215
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 79f3
Additional Information 2: 79f3f37ca9651ef9bd47b0bfb55904f8
Additional Information 3: 86de
Additional Information 4: 86de0d14c4489f5d62365f6244178ece
shark0807 said:
It was, and I did as you suggested, still nothing doing. I've now been trying to use the AT&T RUU to restore everything, but I'm running into problems with that as well. I haven't seen anyone discuss it on this forum, but fastboot and htc_fastboot crash while trying to flash the RUU. First I tried with the .exe of the RUU, which doesn't give me much information except that it crashes. If I do it through command prompt (and a RUU in .zip format), the RUU sends a "pre-update", crashes with an error code FAIL90, tries to do it again, then fastboot and htc_fastboot crash on the computer.
From previous HTC phone forums, it seems like this error happens on Windows 8 and 8.1 computers, but I'm not entirely convinced why my OS in this case would be the problem.
Fastboot error on computer:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: fastboot.exe
Application Version: 0.0.0.0
Application Timestamp: 54bfb0a1
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.17736
Fault Module Timestamp: 550f42c2
Exception Code: c0000005
Exception Offset: 0004248d
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: a10f
Additional Information 4: a10ff7d2bb2516fdc753f9c34fc3b069
And for htc_fastboot:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: htc_fastboot.exe
Application Version: 0.0.0.0
Application Timestamp: 546e94d2
Fault Module Name: StackHash_79f3
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: PCH_27_FROM_htc_fastboot+0x00001215
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 79f3
Additional Information 2: 79f3f37ca9651ef9bd47b0bfb55904f8
Additional Information 3: 86de
Additional Information 4: 86de0d14c4489f5d62365f6244178ece
Click to expand...
Click to collapse
I'm on Windows 7, so I don't know about the Win 8/8.1 issues, but I've read a lot of people that have trouble using those operating systems with drivers.
Maybe try insert coin or another custom rom...I know IC supports AT&T, even thought that's the rom i was using when I started having problems.
Unfortunately I have very slow internet so it takes hours to download a ROM to test. I installed ViperROM, which I have been very happy with when I had my M7, and I can confirm that receiving calls works again. But I have the same problem I had with ARHD, that being that when the screen turns off, the phone turns off. So, the solution is "fixed" kind of, I just need to figure out why my phone is doing this standby issue, and fix that.
shark0807 said:
Unfortunately I have very slow internet so it takes hours to download a ROM to test. I installed ViperROM, which I have been very happy with when I had my M7, and I can confirm that receiving calls works again. But I have the same problem I had with ARHD, that being that when the screen turns off, the phone turns off. So, the solution is "fixed" kind of, I just need to figure out why my phone is doing this standby issue, and fix that.
Click to expand...
Click to collapse
That's because the version of Viper you're using is on the 1.40 base and you're on 1.32 firmware. Either upgrade firmware to 1.40 (requires s-off), flash a 1.32 version of Viper (if one is available...i'm sure one is), or you can try only flashing a 1.32 kernel (either the kernel found in the 1.32 viper rom, or you could try flashing Flar2's 0.3 version kernel in the Original Develpment section). I can confirm with insert coin that I'm able to run a 1.40 base rom on 1.32 base firmware by flashing a 1.32 base kernel...I can't guarantee the same will work with Viper, but it probably will. The easiest thing will be to just flash Flar's 0.3 version kernel because it's a small download. If that doesn't work, you probably should just download the entire 1.32 viper rom (or get s-off and flash the 1.40 firmware).
Actually, I forgot there's an option in Viper's aroma to install the old base kernel. Read here: http://venomroms.com/htc-one-m9/ (see the firmware requirements section)
@shark0807 your ADB and fastboot crash because they are not suitable for the M9 and buggy probably. I had such versions at the beginning of the M9 lifecycle. HTC has by now released their own version of fastboot which a.) doesn't crash anymore and b.) is capable of flashing RUU's larger than 2GB.
You can get my "Batch Tool" which includes the ARUWizard (the "RUU") from HTC as well as the updated htc_fastboot.exe and adb.exe (which I believe is just the generic Google adb.exe).
The Batch Tool comes as self-extracting rar archive and extracts to C:\Android - if you don't want to use it anymore, just delete that folder and its gone.
Batch Tool is here: http://forum.xda-developers.com/showpost.php?p=59783535&postcount=4
A procedure to have your stuff working on Windows 8/8.1:
1.) Go into Control Panel and remove everything that is or might be connected to HTC. First and foremost, HTC Sync Manager. Also every type of ADB/Fastboot drivers you see there.
2.) Download HTC Sync Manager from HERE and install it. Then remove it again (Sync Manager likes interfering with RUU flashes by blocking Fastboot and ADB for its own stupid purposes - better not have it run in the background. The drivers it installs will remain on your system anyway).
3.) Download my Batch Tool and use the "htc_fastboot.exe" instead of the generic Google fastboot.exe!
That should get you up and running. My Batch Tool additionally installs vcredist_x86_2008_SP1.exe - which is vital for a RUU to run properly. It is usually also installed by HTC Sync Manager but I have seen plenty of cases where that did not happen, so I included it into my Batch Tool setup.
Furthermore, DotNet in some version is required but usually already on most windows PC's - I haven't seen the necessity to separately install it. Just FYI.
I ended up having this problem, just tried what was said and its working so far hopefully it stays working! never had this problem before I think the volte stuff was disabled from when I tried a different rom, im staying stock rooted at&t now
jollywhitefoot said:
I think the problem is that your area supports voLte but maybe the ROM doesn't. Notice when you make a call that your 4G/LTE icon changes to 4G only. Well, the same is supposed to happen when you receive a call, but for some reason, something isn't allowing the phone to switch to 4g only.
Click to expand...
Click to collapse
I think that's the case , for now what has work for me is using GSM auto prl, drains the battery faster , don't know why .
I have call att, I have them going nuts , they don't know what it is , I also enable all of the values, for volte, in the default.XML file, but didn't work .
I'm going to try changing roms, I'm thinking maximum HD
To point out, I haven't change firmwares , the phone still has the at&t one , I've kept in order to avoid this situations , I'll try another ROM
@ZeRo2o9
Where can I get the at&t ROM rooted ??
People I had the same issue , I've call at&t and told them I can only receive call on GSM mode , while on LTE , the phone wouldn't ring at all .
So the lady explain that LTE voice is not supported on all towers , that is the reason , so she opt me out , while it becomes available. Then unchecking the option under setting and reseting the phone the calls where working again .
Thanks for this forum for the help .
I was using cyanogen 12.1 stable release. everything was working. suddenly I could no longer hear people in calls and they could not hear me. I can make and receive calls, there is just no audio. I also don't hear a ringing noise when I dial. I have TWRP recover.
Things I have tried with cm 12.1:
I tried wiping my phone followed by flashing cm 12.1
I tried toggling speaker
I tried disabling google checkin service
My sim card works in another phone
I restored my stock recover (nandroid recovery?) and did a factory reset.
stock info:
SGH-M919
android 4.4.4
baseband m919uvufnk2
kernel 3.4.0-2437203
build KTU84P.M919UVUFNK2
bootloader = baseband
I'm not sure how to share logcat from cm 12.1 because i cant post urls and i dont se a way to attach a file.
update: wifi calling works
vandamere said:
I was using cyanogen 12.1 stable release. everything was working. suddenly I could no longer hear people in calls and they could not hear me. I can make and receive calls, there is just no audio. I also don't hear a ringing noise when I dial. I have TWRP recover.
Things I have tried with cm 12.1:
I tried wiping my phone followed by flashing cm 12.1
I tried toggling speaker
I tried disabling google checkin service
My sim card works in another phone
I restored my stock recover (nandroid recovery?) and did a factory reset.
stock info:
SGH-M919
android 4.4.4
baseband m919uvufnk2
kernel 3.4.0-2437203
build KTU84P.M919UVUFNK2
bootloader = baseband
I'm not sure how to share logcat from cm 12.1 because i cant post urls and i dont se a way to attach a file.
update: wifi calling works
Click to expand...
Click to collapse
Hmm... sounds like something that started happening on my M919 a few months ago.
Another user with similar (same?) issue posted in general here: http://forum.xda-developers.com/galaxy-s4-tmobile/general/sound-voice-calls-t3392450
My reply was this... haven't tried the fix yet:
dirkdigles said:
This just happened to my M919 a few weeks ago. Voice call audio works via bluetooth ONLY but not via phone speakers or wired headset. Everything else (media, videos, whatsapp calls, messenger calls, etc.) works fine.
I did a lot of research and found almost nothing ... except this:
https://www.youtube.com/watch?v=heJqdryGhrs
http://blog.brokenlcds.com/samsung-galaxy-s4-speaker-problem/
If you look at the 2nd picture, I believe that the solder connections on the Audio IC chip (in-call audio chip) are degraded.. Initially if I put pressure on that area on my phone, the audio would cut in and out. Now it's completely gone.
I've read that if you disassemble the phone and use a heat gun to carefully reflow the solder on that little chip, the connections re-attach and this may fix the issue.
I haven't tried because I can't afford a new phone right now and don't want to risk further damaging this one, so I just have my calls currently forwarding to my GVoice number, which works fine.
Click to expand...
Click to collapse
vandamere said:
I was using cyanogen 12.1 stable release. everything was working. suddenly I could no longer hear people in calls and they could not hear me. I can make and receive calls, there is just no audio. I also don't hear a ringing noise when I dial. I have TWRP recover.
Things I have tried with cm 12.1:
I tried wiping my phone followed by flashing cm 12.1
I tried toggling speaker
I tried disabling google checkin service
My sim card works in another phone
I restored my stock recover (nandroid recovery?) and did a factory reset.
stock info:
SGH-M919
android 4.4.4
baseband m919uvufnk2
kernel 3.4.0-2437203
build KTU84P.M919UVUFNK2
bootloader = baseband
I'm not sure how to share logcat from cm 12.1 because i cant post urls and i dont se a way to attach a file.
update: wifi calling works
Click to expand...
Click to collapse
Hi, a quick question, does it work on other ROMs? E.g., does it work normally on SlimLP, RR, AOKP, etc., to see if it is the phone or CM12.1 problem.
Also, to post a logcat, just paste it into the XDA post, and select the code flag.
Sent from my SGH-M919 using XDA-Developers mobile app
AlaskaLinuxUser said:
Hi, a quick question, does it work on other ROMs? E.g., does it work normally on SlimLP, RR, AOKP, etc., to see if it is the phone or CM12.1 problem.
Also, to post a logcat, just paste it into the XDA post, and select the code flag.
I haven't tried any other roms besides cm12.1. I tried updating my phone using kies to the lateset firmware and that didn't work either. Luckily my phone is still under warranty so I'm getting it replaced today.
When I tried pasting logcat, the forum said it was too long. I don't remember if I tried the log with warning level.
Click to expand...
Click to collapse
vandamere said:
AlaskaLinuxUser said:
Hi, a quick question, does it work on other ROMs? E.g., does it work normally on SlimLP, RR, AOKP, etc., to see if it is the phone or CM12.1 problem.
Also, to post a logcat, just paste it into the XDA post, and select the code flag.
I haven't tried any other roms besides cm12.1. I tried updating my phone using kies to the lateset firmware and that didn't work either. Luckily my phone is still under warranty so I'm getting it replaced today.
When I tried pasting logcat, the forum said it was too long. I don't remember if I tried the log with warning level.
Click to expand...
Click to collapse
Hi!! My girlfriend also has a similar problem, but she is on cm13. I haven't figured out the solution, but it seems that when you call someone, if you press the loudspeaker button twice (i.e. -> loudspeaker -> regular), the problem is solved. However, you need to repeat this for every call. Does this happen with your phone too?
Click to expand...
Click to collapse