Anybody having issues with Chase Quick Deposit on GPE Roms, it seems that the pictures turn Green after been snapped.
Having same issue, anyone found a fix?
Bank of America is also giving me problems. Keeps telling me that the image isn't clear enough when it's actually pretty clear.
Sent from my HTC One_M8 using Tapatalk
On S-off, rooted, ATT HTC One M8 and having same green screen on gpe roms or on conversion. App works fine on sense based roms. :crying:
Did anyone find a solution?
Thanks
Alaris said:
Bank of America is also giving me problems. Keeps telling me that the image isn't clear enough when it's actually pretty clear.
Click to expand...
Click to collapse
Reviving a few month old thread here, but I'm having similar issues with Bank of America -- when I snap the photo of the check, it never turns into a static image. Like, even after pushing the camera button and the app asks me to confirm, I still see the moving camera window rather than the static photo that I just supposedly took. Even if i sit perfectly still and confirm the images it never goes through.
Anyone found a fix for this? GPE ROM, using Google Camera.
I have tried multiple ROMs (GPE, CM11) on my Tmobile HTC-M8 and am facing the same issue with the Chase mobile app. The check picture turns green. With Sense ROM there are no issues. I'm wondering if this is happening to folks who converted from Sense to GPE or is it evening happening to people who have a GPE edition phone.
Converted from Sense to GPE
I purchased the unlocked HTC One M8 direct from HTC and converted it to the GPE.
I'm getting the green image when I try to make a deposit with the Chase app too.
The next thing I think I'll try is switching it back to S-ON. I'm a little concerned changing it to S-ON with the GPE RUU will cause more serious issues...
I was getting the green image with CyanogenMod and S-ON too, so I'm not confident making it S-ON will fix it.
Any success stories appreciated.
I have the same issue with Chase and Citibank the picture is fuzzy and does not work. My Moto G works fine for both though. Does anyone have a fix or suggestions?
Back to S-ON
nertner said:
I purchased the unlocked HTC One M8 direct from HTC and converted it to the GPE.
I'm getting the green image when I try to make a deposit with the Chase app too.
The next thing I think I'll try is switching it back to S-ON. I'm a little concerned changing it to S-ON with the GPE RUU will cause more serious issues...
I was getting the green image with CyanogenMod and S-ON too, so I'm not confident making it S-ON will fix it.
Any success stories appreciated.
Click to expand...
Click to collapse
I'm back to S-ON. Didn't brick the phone, but still getting the green image.
Same issue here. AT&T HTC One converted to GPE.
I don't think where you bought the phone should matter its the same hardware
spinninbsod said:
I don't think where you bought the phone should matter its the same hardware
Click to expand...
Click to collapse
This is a software problem. Could definitely be firmware / software related.
For the record I had this issue with Bank of America's check deposit, but they pushed out a fix and the changelog specifically said it was a fix for the M8.
Same issue (blank green photos on HTC One M8 with Chase app)
Not to be confused with a totally different issue, inability to resolve a picture well enough for BofA to use.
Anybody find relief here? I enabled developen mode and tuned background process limits, but I didn't see much to tune, and found no resolution.
Related
So today my Desire Z started to lose connection whenever the screen was locked for more than a few minutes. I would set it down and when I got back the lock screen would say "limited service". To get it back I would either have to restart my phone or enter than exit airplane mode. I have looked into the settings and I have mobile data always on.
Is there anyone else experiencing this?
Update: In small print under where it says "limited service" on the lock screen at also says "emergency calls only" as if my carrier is doing this and not my phone. It also seems to be more random than I thought because sometimes it happens when my screen is on and it doesn't always happen when my screen it locked for a few minutes.
I recently installed a data counter. Could that be conflicting with anything?
Any tips or advice is welcome.
What area are you in? I was experiencing something similar over this past weekend, but heard from up top that they were doing HSPA maintenance / work, they might be in your area now.
J.Coffey said:
Update: In small print under where it says "limited service" on the lock screen at also says "emergency calls only" as if my carrier is doing this and not my phone. It also seems to be more random than I thought because sometimes it happens when my screen is on and it doesn't always happen when my screen it locked for a few minutes.
I recently installed a data counter. Could that be conflicting with anything?
Any tips or advice is welcome.
Click to expand...
Click to collapse
Could it be your SIM card? Maybe clean the contacts and make sure it is in there good.
It does sound like something to do with the SIM card to me, e.g. dirty contacts on the SIM card, the SIM card sitting too loose in the holder, etc.
So I was at work when this started happening, then I went home and everything was fine, now I'm back at work and it's happening again. So I guess my signal isn't strong enough to maintain it while I'm here, I find this strange because I am getting the same speed as anywhere else while having the same amount of bars (3 or 4).
J.Coffey said:
So I was at work when this started happening, then I went home and everything was fine, now I'm back at work and it's happening again. So I guess my signal isn't strong enough to maintain it while I'm here, I find this strange because I am getting the same speed as anywhere else while having the same amount of bars (3 or 4).
Click to expand...
Click to collapse
I just got my bell desire Z, unlocked it and am having the same exact problem with Telus in Victoria, B.C.
I called Telus and they said there is no maintinence going on in the area. I have also S-OFF'd, rooted and installed cyanogen as well as other roms, with the same problem.
Any Ideas OP? did you solve your issue? I have reverted to stock, (still same problems) and am thinking of returning mine.
I will clean my SIM card and report back.
Edit: Yeah, no SIM card cleaning in the world could fix it. I think I am going to have to return it.
Have you both unlocked using codes?... and rooted and s-off using the old method?
.... wasn't there an issue with unlock codes. Revert back to stock then try the Gfree method for s-off and subsidy lock off I reckon.
Sent from my HTC Vision using XDA App
ddotpatel said:
Have you both unlocked using codes?... and rooted and s-off using the old method?
.... wasn't there an issue with unlock codes. Revert back to stock then try the Gfree method for s-off and subsidy lock off I reckon.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I had unlocked with a code, and then rooted and S-offed using the old method.
I can restore my stock nandroid, but I dont think there is a bell RUU that I can use. I will try again.
dash4g said:
I had unlocked with a code, and then rooted and S-offed using the old method.
I can restore my stock nandroid, but I dont think there is a bell RUU that I can use. I will try again.
Click to expand...
Click to collapse
Good call by ddotpatel there. As he said, there was a major issue with unlock codes, at least on the G2 side of things (I'm not clear if this affect the DZ). Don't use the old method to S-OFF, use gfree which will SIM unlock you too. It has even managed to repair some bricked G2's which got corrupted through unlock codes.
steviewevie said:
Good call by ddotpatel there. As he said, there was a major issue with unlock codes, at least on the G2 side of things (I'm not clear if this affect the DZ). Don't use the old method to S-OFF, use gfree which will SIM unlock you too. It has even managed to repair some bricked G2's which got corrupted through unlock codes.
Click to expand...
Click to collapse
OK, I applied the Tmobile RUU, and restored my Telus APN settings and got data back. After 5 minutes of sitting, I notice the same issues happening. I will try again in the morning with gfree, but not expecting much.
Thank you for the quick response and suggestion!
dash4g said:
OK, I applied the Tmobile RUU, and restored my Telus APN settings and got data back. After 5 minutes of sitting, I notice the same issues happening. I will try again in the morning with gfree, but not expecting much.
Click to expand...
Click to collapse
Don't worry, all gfree does is patch your radio configuration partition. Even if this went badly wrong and the partition was damaged/wipe (which won't happen), you could still boot your phone to repair it, it's just that the calling/data won't work without the radio config.
The guys on #G2ROOT have had success in getting a lot of G2's working again, after they started to have serious problems following unlocking codes.
same thing happened with me on the original telus desire. Change your sim card. Apparently they arent meant to last more than two years.
I had issues with my DZ on Telus after I used the gfree method to S-off. Since I was already unlocked and didn't seem to have any issues with my call quality until I S-offd..I assume it affected it somehow..but all's I did was replace my SIM and all was well again. I went from horrible call quality and data sending issues to a now perfect phone. For the $10 a new SIM is worth I'd suggest that.
Sent from my HTC Vision using XDA App
Rickroller said:
I had issues with my DZ on Telus after I used the gfree method to S-off. Since I was already unlocked and didn't seem to have any issues with my call quality until I S-offd..I assume it affected it somehow..but all's I did was replace my SIM and all was well again. I went from horrible call quality and data sending issues to a now perfect phone. For the $10 a new SIM is worth I'd suggest that.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thanks for the input guys, but I just got real s-off with gfree and even bought a new SIM. Same issues.
I think I will bring it back on Monday, and swap for a new one.
Thanks for the help!
I am having the same issue on a DZ i just got from bell. I have full bars, then next thing I know i'm getting 'limited service' no idea why this happens? Guess i'll have to take it back to bell.
whistlerGreg said:
I am having the same issue on a DZ i just got from bell. I have full bars, then next thing I know i'm getting 'limited service' no idea why this happens? Guess i'll have to take it back to bell.
Click to expand...
Click to collapse
Have you rooted or modified it in any way? This is the EXACT same issue, but it would be nice to see if it is happening to stock phones as well.
I have been getting this issue too. I unlocked the phone via an online unlocking service then rooted and soff using gfree. The interesting thing is I would get this issue with my motorola milestone which was also carrier unlocked and rooted. I have a new sim and that hasn't resolved the issue. It only happens very rarely. I am running cyanogen rc1. The fact I was getting this issue on my milestone indicates its a network issue.
JPHCCFC said:
I have been getting this issue too. I unlocked the phone via an online unlocking service then rooted and soff using gfree. The interesting thing is I would get this issue with my motorola milestone which was also carrier unlocked and rooted. I have a new sim and that hasn't resolved the issue. It only happens very rarely. I am running cyanogen rc1. The fact I was getting this issue on my milestone indicates its a network issue.
Click to expand...
Click to collapse
Diff handsets + diff sim cards,... Gota be a network/reception problem no?
has anyone tried the data throttle thing to see if it makes a difference to you guys?
JPHCCFC said:
...The fact I was getting this issue on my milestone indicates its a network issue.
Click to expand...
Click to collapse
Funny that you should mention this, because now that I am at school, I am getting 1 bar, where in my old HTC Desire I would get no service.
At home, I would normally get very good reception with my old Desire, and now it fluctuates from 4 bars to no reception in a matter of minutes with the Z.
So it must be a network issue, but all the *****ing and complaining in the world wont get me anywhere with Telus I'm sure, as I am only 4 months into a 3 year contract. I am sure they will reverb something back like "not our phone, not our problem" Bah-humbug. I will get a replacement, but I also may just switch to Bell if they are going to be like that.
really screwed up. tried unrooting back to gb2.33 from revolutionary. tried using jcases tutorial by installing froyo ruu but after that adb would not recognize device. i loaded newer ruu back on along with cwm and superuser. i even tried radio. at this point i can run the phone but cannot connect with verizon wireless. i have internet connection through wifi but no phone at all just a triangle where it should be. any idea how to get verizon back on? any help is much appreciated. newbjimmy.
All you have to do is put the gb ruu on your SD rename to PG32IMG.zip and flash through hboot you'll be back to where you need to be
Sent from my Incredible 2 3D using xda premium
did not help. its like theres no sim at all.
hmmmm man I'm not sure then maybe someone with some more dinc knowledge can chime in I'm used to my inspire only had my dinc about a week
Sent from my Incredible 2 3D using xda premium
This happened with my neighbor's inc2. We tried everything under the sun and couldn't fix it. VZW tech support spent an hour with him trying to fix it. They ended up sending a replacement. If you were following jcase's tutorial on rootzwiki and did the all the steps the good news is s-on is back so they shouldn't know that you rooted (I can't say for 100% but so far he hasn't been charged for the replacement).
I am assuming your lockscreen says preferred provider or something of that nature. If you factory reset it will ask you for a country code and then the lockscreen will say digital roaming (which vzw will most likely ask you to do, I will warn you that after that he lost the ability to receive/send calls and texts). If you*228 option 1 you will also notice that it doesn't say programming at the top and it will say it was successful on the recording but the phone will not reboot and manually rebooting does nothing as I don't think it actually programs the PRL. Anyways I just wanted to give you an idea of what you are in-store for.
If someone out there is much smarter than me (which I am positive of that) and has more knowledge of how PRL programming works, they might be able to fix your issue but most likely you will need to do a handset exchange with vzw.
problem is fixed
thank you all for the suggestions. it took several ruu tries before it actually worked and for the life of me i don't know what corrected the problem because i did the same fix several times without success. oh well all is ok. i'm rooted,cwm backedup, with several other roms on the back burner.
I wish I knew what did it because it caused me quite a bit of frustration. Out of curiosity which RUU were you using?
Am I the first person to report this on an M8?
My stock software version is 1.54.707.7 (Asia Phone) & stock radio is 1.16.2133156.UA10G.
In my own opinion (& I have no proof to back it up), I guess the clicking/popping noise from the speaker happens after upgrading to 1.54.401.10_firmware which has the radio 1.16.2133156.UA15G.
The noise comes & goes. It's hard to replicate it. It is quite obvious in poor reception areas & I get drop calls too.
My wife's m8 is still running stock radio & she says she doesn't have this issue. So I've just pulled her radio.img & flashed it on my phone.
I will give it a few days to see if it's the radio or not.
The next step is probably warranty it.
I had this issue so badly on the m7, so when I first bought the m8 I tested it thoroughly to make sure it doesn't happen to me. & now it does
Any advice is greatly appreciated.
Thanks.
Same problem here. After last OTA I hear popping during calls. Bad job HTC.
HTC One M8 & Tapatalk
Do you have Bluetooth enabled while this is happening?
Sent from my HTC One_M8 using XDA Free mobile app
AmberBoy said:
Same problem here. After last OTA I hear popping during calls. Bad job HTC.
HTC One M8 & Tapatalk
Click to expand...
Click to collapse
Does the OTA have radio update?
Did you note down your stock baseband? & fastboot getvar all after the update to see if there's any difference?
Could you try to roll back to your stock radio see if the problem goes away.
I tested 1 phone call this morning & all is well with the stock radio from my wife's m8.
Keeping my finger crossed.
wpghtc said:
Do you have Bluetooth enabled while this is happening?
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
No bluetooth here.
But Yes, your thought is correct. Some people have this problem while using some kind of bluetooth devices.
For my case, it *seems* like the firmware update did it.
Believe it or not, before I flashed 1.54.401.10_firmware, I was thinking "would it cause the clicking/popping noise" & it's sneaking up on me slowly.
I've rolled back to stock radio & 1 phone call this morning showed no issue. Good sign, but this thing comes & goes...it's not a fix yet...
I'll give it a few days & update you guys.
Thank you.
Any advice & input is appreciated !
Issue with volte on my M9. I saw the warnings and take responsibility for my actions.
When trying simultaneous voice and data I get the "data not available while on this call" popup. I verified Adv calling is turned on and my Verizon shows it activated also.
Since I'm not sure how to deal with Verizon on S-Off, custom recovery, custom rom I thought I'd start with the clever and helpful contributors on xda.
Any tips for preparing to deal with Verizon from those of you having gone through something similar?
************************ Edit
Viper 3.5 vzw FW 2.6.605 Don't have my hopes up but will try RUU to stock set up tonight
sidjohn said:
informationalIssue with volte on my M9. I saw the warnings and take responsibility for my actions.
When trying simultaneous voice and data I get the "data not available while on this call" popup. I verified Adv calling is turned on and my Verizon shows it activated also.
Since I'm not sure how to deal with Verizon on S-Off, custom recovery, custom rom I thought I'd start with the clever and helpful contributors on xda.
Any tips for preparing to deal with Verizon from those of you having gone through something similar?
************************ Edit
Viper 3.5 vzw FW 2.6.605 Don't have my hopes up but will try RUU to stock set up tonight
Click to expand...
Click to collapse
There have been both temporary and permanent hosings of volte. Ruu will cut to the chase and tell you right away if its ROM/app based.
I had one that had to be returned because of this. We can chat more after you ruu.
dottat said:
There have been both temporary and permanent hosings of volte. Ruu will cut to the chase and tell you right away if its ROM/app based.
I had one that had to be returned because of this. We can chat more after you ruu.
Click to expand...
Click to collapse
Thanks @dottat - Used your vzwM9_1.33_0PJAIMG.zip to ruu with htc_fastboot. Still not able to do voice and data simultaneously.
Just went back into recovery to wipe data/factory reset and noticed messages regarding missing bitmap oem_unlock_bg. Is that relevant? Saw somewhere that that is a toggle in developer options but cant find it
sidjohn said:
Thanks @dottat - Used your vzwM9_1.33_0PJAIMG.zip to ruu with htc_fastboot. Still not able to do voice and data simultaneously.
Just went back into recovery to wipe data/factory reset and noticed messages regarding missing bitmap oem_unlock_bg. Is that relevant? Saw somewhere that that is a toggle in developer options but cant find it
Click to expand...
Click to collapse
That message is normal.
If the issue stuck after ruu and you are in solid 4g service area you may need to get it swapped. Under settings-call is the video calling section greyed out permanently too?
Sent from my HTC6535LVW using Tapatalk
dottat said:
That message is normal.
If the issue stuck after ruu and you are in solid 4g service area you may need to get it swapped. Under settings-call is the video calling section greyed out permanently too?
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
South side of Minneapolis so I believe we have solid 4G and wife's iPhone 6 is capable of simultaneous data/voice.
Video calling is selected and grayed out.
Haven't tried toggling from My Verizon account yet.
sidjohn said:
South side of Minneapolis so I believe we have solid 4G and wife's iPhone 6 is capable of simultaneous data/voice.
Video calling is selected and grayed out.
Haven't tried toggling from My Verizon account yet.
Click to expand...
Click to collapse
Yours is exactly like mine was. I toggled from the account a few times. Had vzw support engineers look at multiple times and we finally gave up.
Any info you can offer up on flash history you might have? Did you browse the root directory of the phone and open some of the files etc?
Sent from my HTC6535LVW using Tapatalk
dottat said:
Yours is exactly like mine was. I toggled from the account a few times. Had vzw support engineers look at multiple times and we finally gave up.
Any info you can offer up on flash history you might have? Did you browse the root directory of the phone and open some of the files etc?
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Not sure when this issue started for me but I didn't think to even check it until seeing some posts from others recently.
S-Off by Java Card in mid-May and bounced around between some of the more stable and popular roms on these forums staying with those that indicate support for verizon
No Red Text aboot, and updated firmware to 2.6. No unusual failures or hangups at either or while flashing any roms.
Other than deleting some files in DCIM, Downloads, and Pictures from my Win7 PC, I have not gone exploring in the root directory and haven't knowingly changed anything there.
sidjohn said:
Not sure when this issue started for me but I didn't think to even check it until seeing some posts from others recently.
S-Off by Java Card in mid-May and bounced around between some of the more stable and popular roms on these forums staying with those that indicate support for verizon
No Red Text aboot, and updated firmware to 2.6. No unusual failures or hangups at either or while flashing any roms.
Other than deleting some files in DCIM, Downloads, and Pictures from my Win7 PC, I have not gone exploring in the root directory and haven't knowingly changed anything there.
Click to expand...
Click to collapse
It possibly is just simply random. Sucks. Did you do a factory reset in stock recovery just to be sure?
Sent from my HTC6535LVW using Tapatalk
dottat said:
It possibly is just simply random. Sucks. Did you do a factory reset in stock recovery just to be sure?
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Besides factory reset, if not already done, talk to Verizon Tech Suppport
and confirm that it is active. I had this same problem after activating the service,
and Tier 2 Support found that only one of the two lines was actually setup for HD Calling.
michaelbsheldon said:
Besides factory reset, if not already done, talk to Verizon Tech Suppport
and confirm that it is active. I had this same problem after activating the service,
and Tier 2 Support found that only one of the two lines was actually setup for HD Calling.
Click to expand...
Click to collapse
Thanks guys for helping - Never run out of thanks for the day before!
I think I will return cid to VZW__001, ruu again to confirm, factory reset from stock recovery, and toggle the adv calling setting from my verizon.
Do I have to remove all evidence of S-Off before contacting Verizon? Best to stop in a store to talk them into a new phone? Or go online for support?
sidjohn said:
Thanks guys for helping - Never run out of thanks for the day before!
I think I will return cid to VZW__001, ruu again to confirm, factory reset from stock recovery, and toggle the adv calling setting from my verizon.
Do I have to remove all evidence of S-Off before contacting Verizon? Best to stop in a store to talk them into a new phone? Or go online for support?
Click to expand...
Click to collapse
I'd recommend going back to S-on before going in to ask about this. If it does get fixed one way or another, just let me know and we can meet up again to get you back to S-Off.
bschram said:
I'd recommend going back to S-on before going in to ask about this. If it does get fixed one way or another, just let me know and we can meet up again to get you back to S-Off.
Click to expand...
Click to collapse
S-on regardless of whether I contact them online or in store?
sidjohn said:
S-on regardless of whether I contact them online or in store?
Click to expand...
Click to collapse
In the store probably. Online you shouldn't need to worry about it
I will update for those interested when resolved...thanks for your help
So I've seen things here and there about what (possibly) causes loss of Volte, but it's been scattered. Browsing or opening things on the root directory, was about the only thing that stands out... What are other ideas about what may cause the problem... Just out of curiosity
lordcheeto03 said:
So I've seen things here and there about what (possibly) causes loss of Volte, but it's been scattered. Browsing or opening things on the root directory, was about the only thing that stands out... What are other ideas about what may cause the problem... Just out of curiosity
Click to expand...
Click to collapse
That was only my theory but sidjohn said he didn't do anything like that. So who knows. Could have been a poor factory configuration too. My replacement has always been fine.
Sent from my HTC6535LVW using Tapatalk
dottat said:
That was only my theory but sidjohn said he didn't do anything like that. So who knows. Could have been a poor factory configuration too. My replacement has always been fine.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I am not shy to explore but cautious about opening or changing anything I'm not fairly sure about. Doesn't rule out a bonehead move on my part but I've been comfortable rooting about since the T-Bolt days.
Still in protracted discussions with big red.
Appreciate the support from the xda community and will update as things progress.
sidjohn said:
I will update for those interested when resolved...thanks for your help
Click to expand...
Click to collapse
Expecting replacement - refurbished "Like New" - M9 July 31st. Will update once It's operational.
sidjohn said:
Expecting replacement - refurbished "Like New" - M9 July 31st. Will update once It's operational.
Click to expand...
Click to collapse
Glad to hear they are replacing it for you!
bschram said:
Glad to hear they are replacing it for you!
Click to expand...
Click to collapse
Not painless but I understand VZW's process I guess. Involved 2 online chats (3 if I count one disconnected after a couple of minutes), email support efforts, and several days of texts and phone calls with tech support engineers before they determined my phone was not accessing a particular APN which allows for Advanced Calling.
Got the impression from Tech that this is uncommon but coincidentally also just yesterday received a survey from verizon pertaining to my experience with my m9. One section asked whether I experienced any of a litany of issues reported by others - short battery life, bad camera, overheating, etc...and the inability to open a web browsing session while on a phone call - my exact problem. So maybe not so uncommon?
Received replacement today, looks and feels clean and "Like New" - Charged it but haven't fired up yet.
Just finished returning my original M9 to Stock, Locked, and S-On per @dottat 's easy to follow directions - thank you.
Now to get the replacement set up and think about S-Off again --- just a little nervous about that!
*****Edit to add link*****
Useful information. (Return to locked/S-on in Post #3)
http://forum.xda-developers.com/verizon-one-m9/general/official-ruu-1-33-605-15-t3137397
I have a weird situation. I bought a M9 (used). It activated fine and data and texting works perfect, but outgoing calls aren't working at all. The dialer just hangs. The Sprint Corporate store couldn't figure out the problem either. I've reprovisioned, updated the PRL, and did a factory reset multiple times.
What's going on?
BTW I know you all help out of kindness, but I'll reward anyone who successfully figures this out for w/ $20.00 via PayPal if they willingly accept it.
Is this phone s-off, unlocked, rooted? What happens when someone calls you? Under Settings - Call, what does it say for Preferred Network?
cmlusco said:
Is this phone s-off, unlocked, rooted? What happens when someone calls you? Under Settings - Call, what does it say for Preferred Network?
Click to expand...
Click to collapse
The phone isn't s-off or rooted (the bootloader is also still locked). I'm not sure how to check whether it's unlocked. Inbound calls seem to work fine.
simonstiph said:
The phone isn't s-off or rooted (the bootloader is also still locked). I'm not sure how to check whether it's unlocked. Inbound calls seem to work fine.
Click to expand...
Click to collapse
Boot into recovery or fastboot (not sure), and you will see the bootloader status. Relocked means that it was unlocked before. You can also see s off status here.
Skickat från min HTC One M9 via Tapatalk
Roobwz said:
Boot into recovery or fastboot (not sure), and you will see the bootloader status. Relocked means that it was unlocked before. You can also see s off status here.
Skickat från min HTC One M9 via Tapatalk
Click to expand...
Click to collapse
The top of the bootloader says ***LOCKED***
One odd thing to note is that everything (including outgoing calls) work when Wi-Fi calling is active.
Have you tried using a third party dialer app such as ExDialer from the market? If that works for outgoing calls, then at least you can rule out a hardware issue.You need to try to flash an RUU. The problem is, im sure the phone is already updated past the point of available ruu's. What software/build number is the phone on? You are probably going to have to find someone with a java card or xtc2 clip and get the phone s-off and unlocked. From there you can flash an older ruu (downgrade) and hopefully that fixes your issue. Other than that, with security on there isnt really anything you can do you havent already tried.
cmlusco said:
Have you tried using a third party dialer app such as ExDialer from the market? If that works for outgoing calls, then at least you can rule out a hardware issue.You need to try to flash an RUU. The problem is, im sure the phone is already updated past the point of available ruu's. What software/build number is the phone on? You are probably going to have to find someone with a java card or xtc2 clip and get the phone s-off and unlocked. From there you can flash an older ruu (downgrade) and hopefully that fixes your issue. Other than that, with security on there isnt really anything you can do you havent already tried.
Click to expand...
Click to collapse
That's a good idea, but I just tried ExDialer and it hangs on the exact same spot where it says "DIALING..." then says the call was lost. I'm at the most recently available RUU, but Marshmallow is on it's way for us any minute now. I'll investigate getting S-OFF.
You would think the verizon corporate store wouId have access to all the ruus, and would have tried reflashing it. I got s-off with a xtc2 clip. I met a guy from the java card thread who had one and lived fairley close. He did it for a small donation, it takes only minutes.
Do you use google voice integration?
I wish I stole my HTC M9.
shivadow said:
Do you use google voice integration?
I wish I stole my HTC M9.
Click to expand...
Click to collapse
I did have it active on the account, but I turned it off and had Sprint remove the [soc] tag from the line.
simonstiph said:
I did have it active on the account, but I turned it off and had Sprint remove the [soc] tag from the line.
Click to expand...
Click to collapse
Your phone is defective, Tell HTC (uh-oh protection) or Sprint to give you another phone.
clsA said:
Your phone is defective, Tell HTC (uh-oh protection) or Sprint to give you another phone.
Click to expand...
Click to collapse
I think you're right -- but I still wished I knew what the &%$# is actually the culprit. Even though I bought the phone second hand, HTC is to be willing to honor the warranty. At least my luck isn't that horrible.