I have just recently got an G4 xda exec, fully unlocked and i have upgraded to TML 8.7.1 and i have also got a 3 sim, but when i put my 3 sim card in the device it says that it is an orange sim
I have tried with my other sim card and that is perfect but it is not a 3g sim so i really want 3g to work
Any Ideas ???
Have you run the Connection Setup? I can't remember if TML871 has built one in his ROM or if it's auto-run. Either way, if you run it again, you should be able to select 3sim instead of orange.
Trying that now, it did have that setting, and i have not tried that one before
EDIT: I have tried to do that, it still says orange and when i go into the connection setup it says error with the database
I have had another look at it and it shows that i am on roming signal, but when i was on wm5 it showed UTMS when i put the sim in, so if it is just my signal or not i do not know
but thanks for the help anyway
ALls I can think is to try a different ROM, and see if it's a problem with Tomal's ROM. It would switch to roaming if it can't find your network and goes through another one (eg Orange). Are you still using the same Radio that you did with WM5? Perhaps you should try another Radio - people seem to like 1.15.
Or... find a .CAB with your network settings and just install by hand. I had some problems with settings provided in various ROMs, so always carry Voda NZ .CAB on my SD. Just in case
i have tried using different settings, so i am now trying a different 6.1 ROM to see if it is a problem with this rom
Thanks for everyone's help
I Have been able to fix the problem, i have used the AllmostOfficial 1.2 Professional rom and I went into the phone options and then network and manually selected 3 off the list in preferred networks and added it onto the list and now it works
Thanks for everyone's help and support as well as the good availability of the site.
I flashed JG5 using Odin (removed sim and sd card) after that i did the modaco r3. Now it does not connect to the mobile network. PLEASE HELP
Did you flash all three files (pda,phone and csc)?
Also, are you talking about mobile network for calls/texts or data only?
Thank you for responding.
Yes i flashed all together.
My Calls / Text is not working...the status bar does not show the connection.
I thought the problem was with the task killer hence that too has been un installed.
I did notice that when i switched sim cards and restarted the network came on but the phone would restart and the network would disappear.
did you install the apn files for your phone .most of the time you find a list at the provider .you can go to apps settings wireless internet mobile networks names and intrance points tip at tapp and tip on new apn .but first find your providers list .if you google apn list ore so you can find it also
wheelboy said:
did you install the apn files for your phone .most of the time you find a list at the provider .you can go to apps settings wireless internet mobile networks names and intrance points tip at tapp and tip on new apn .but first find your providers list .if you google apn list ore so you can find it also
Click to expand...
Click to collapse
Thanks for the reply. Isnt APN used primarily to connect to EDGE / GPRS. Is it required for registering on a mobile network because as of now the phone is not registering on the mobile network.
Need help urgently...hence bumping
Set up your apn again. Trust me
Sent from my GT-I9000 using Tapatalk
APN---Done that it did not help.
Sometimes i get the signal strength bars but when i dial a number it does not connect it just says Dialing.
This is getting very frustrating.
should i try to flash another firmware...if so please point me to a mirror site as the samsung firmware site is down since the past few days.
Yes, you probably should try a different firmware. Try JM2 from my mirror. (see signature, download is fastest if you run wuala. direct http downloads may be slow at times)
Darkstriker said:
Yes, you probably should try a different firmware. Try JM2 from my mirror. (see signature, download is fastest if you run wuala. direct http downloads may be slow at times)
Click to expand...
Click to collapse
Thanks for the reply...Downloading JM2 in progress from your site.
One doubt...are firmwares region specific or anything goes ??
Once i flash i will update this post and i pray that it works
The content of the f/ws is region specific (additional languages and apps that only work in some countries). However, they all work on the your device!
Darkstriker said:
The content of the f/ws is region specific (additional languages and apps that only work in some countries). However, they all work on the your device!
Click to expand...
Click to collapse
Flashed JM2...same problem HELP!!
Should i format my internal if that is what is causing the problem...because i am not able to figure out the exact problem.
I have the same problem. I bought my GS from USA and I try to use it in Europe. I flashed it both European and America firmwares but I couldn't solve the problem.
When I press *#1234#, it shows that "Phone: Unknown" and *#06# responses nothing.
When i insert the sim card of another operator the phone works. My original operators sim works on other mobiles except this galaxy s. Any tips on why or how to check.
I'm having the same problem, any help to fix this would me really great!
It seems that the galaxy s is not connecting on 1800mhz after flashing. It connects on networks using 900 mhz. Any way to check this on the phone
This is weird. I tried using the phone from another location and it worked. I think this has to do something with the cell tower near my home location.
Hi guys,
I was able to re-flash the original firmware and all works again. If you guys want to go that way here is the link http://forum.xda-developers.com/showthread.php?t=734475 I think this is just for the Vibrant but I'm sure you can find the other firmware on the forums.
Hi!
I am investigating an interesting (and potentially "deadly") issue with the Oppo modem, occuring on european netoworks, specifically Orange and Vodafone Romania. Orange has licences in the LTE FDD 800/1800/2600 mhz, Vodafone 800/1800 FDD and 2600 TDD. Where I live I can only get Orange on 1800/2600 and Vodafone on 800/1800 mhz. At first tried installing with a custon recovery both stock and custom firmwares, wich broke LTE on Orange and I was installing roms for 2 days fearing I messed up something. Actually, with stock recovery by installing stock fw, LTE started working again, but there was no way for it to work on AOSP roms. I then bought a Vodafone card and I figured that while LTE on Orange breaks, it works with Vodafone and vice-versa. On custom roms, only Vodafone works, but when I restore a twrp backup, it breaks for both Vodafone and Orange. Logcat does not show anything suspicious and I only get (while on LTE only) "emergency calls only" after the phone tried desperately to register on LTE for dozens of seconds. Since the way I flash roms does seem to have an effect sometimes, I realised it could be a filesystem bug, though I must admit further investigation is needed. I am not unified an I tried unbricking my phone twice (with the default version after unbricking, it works on Vdf, no Orange).
I would need a collaboration with more experienced developpers to further investigate this serious issue.
Strange But . . .
thank you for the heads-up, I've tried several ROMs already including the famous Chinese COS ROMs and have not experienced this issue, however, I have observed in the past that my LTE connection is functioning erratically. I am not sure if this is related but i believe it needs to be checked. I totally lost LTE connection from one of the 2 providers in my country where previously am getting strong signal. Am not suspecting anything of this sort until I came across this report. Hope an expert respond to this to clear this out.
Yes, it happened to me also, although the signal bars are there, the connection gets lost. At first I thought it was a network issue, but it happened once again after that. I realised that swiching data on/off sometimes solves the issue, sometimes not. Sometimes a reboot soles it, sometimes not.
But the fact that I have to flash another ROM to be able to use another netork, well, that's a big issue that almost makes me wanna change my phone. Too bad, because Oppo has geat signal strength where Samsung/ HTC normaly would loose connectivity.
I am waiting for the devs to suggest another thing to look for. I suppose that opening another thread on the stock rom area would be useless since this issue is specific to both stock and custom roms.
Maybe the mods would just post a shortcut there to this post, as this is a serious issue.
you need to enter engineering main page from the dialer enter *#36446337# Go to "Network Set" "RAT Mode"
Select what you need.. Go Back using Back button, go to "Band Mode" and select what you need, Then go to LTE Band Mode and do the same. That solved the issue for me.
that ussd code doesnt do anything on my v9077 however *#*#4664#*#* brings up a testing menu which enables setting radio to lte only this is handy if you are testing in bad reception are as phone will default to hspap if the signal is stronger
Unfortunately, none of the codes work, only *#*#4636#*#*
I suspect a RIL issue, since flashing stock modem instead of CM based, I get to see all networks, but I cannot conect to any of them with the proper tested SIM card.
In order to accomplish that, I must credit Flying_Bear with his thread http://forum.xda-developers.com/showthread.php?t=2496075 but also xpirt http://forum.xda-developers.com/and.../how-to-conver-lollipop-dat-files-to-t2978952
You basically need to exctract the telephony-common.jar and insert files from stock FW in order for it to comply with the stock modem that has been flashed. Only a combination of these 2 parts will make a good working phone.
The problem is that the files in stock ROM are odexed so you have 2 files, telephony-common.jar and telephony-common.odex. I tried deodexing them (thanks to sicopat http://forum.xda-developers.com/galaxy-s2/themes-apps/how-to-manually-deodex-odex-t1208320 )
Code:
java -jar baksmali.jar -x telephony-common.odex -o deodex
but I get
Code:
Error occured while loading boot class path files. Aborting.
org.jf.dexlib.Code.Analysis.ClassPath$ClassNotFoundException: Could not find superclass Landroid/app/Service;
at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.loadSuperclass(ClassPath.java:784)
at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.<init>(ClassPath.java:668)
at org.jf.dexlib.Code.Analysis.ClassPath.loadClassDef(ClassPath.java:280)
at org.jf.dexlib.Code.Analysis.ClassPath.initClassPath(ClassPath.java:163)
at org.jf.dexlib.Code.Analysis.ClassPath.InitializeClassPathFromOdex(ClassPath.java:110)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:98)
at org.jf.baksmali.main.main(main.java:278)
Error while loading class Landroid/accessibilityservice/AccessibilityService; from file ./framework.zip
Error while loading ClassPath class Landroid/accessibilityservice/AccessibilityService;
If you are only *#*#4636#*#* can access. It means you are not in stock rom. (No engineer mode)
Use computer to flash back to stock first. Then try step by step.
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/
Sent from my X9070
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 .