First off my Google Wallet works....EVENTUALLY. It takes many many tries for it to finally read and/or acknowledge my phone when I try to use it. This happens when completely stock and locked or rooted with several different ROMs. The secure element isn't bricked or it wouldn't work at all. It used to work perfectly then all of a sudden stopped working. I've tried uninstalling it, wiping the phone, factory resets, all the normal stuff like that. I don't know if this just localized to google wallet or if all NFC functions are like this. I don't have any way to test the NFC any other way.
Has anyone heard of anything like this? Or know of anything else I could try to fix it? I am pretty much spent out of ideas on what to do.
Like I said I get the same thing if the phone is completely stock and locked but here's my phone stats.
EVO 4g LTE
HBoot 1.19 S-Off
CM10 Deck's 12/4 Build
Stock Kernel that came with Deck's CM10
Baseband 1.12.11.0809
If you'd like any info on the phone, I'd be happy to post it for you.
You put a new case on your phone recently?
Sent from my LTEVO running MeanRom
Install OTA root keeper, temporarily unroot the phone using that then try again.
Sent from my Evo with CM10
Recently Flashed to CM10 and can't get wallet to work
onlybob said:
Install OTA root keeper, temporarily unroot the phone using that then try again.
Sent from my Evo with CM10
Click to expand...
Click to collapse
I recently flashed CM10 on my EVO (12/7 nightly) and I'm having trouble getting Wallet to work. From all I read, I should be able to install or sideload the .apk but that hasn't seemed to work. I'm wondering if I've missed something in my research. Now I'm getting the "Not Supported: Unfortunately, google wallet is not yet supported for your device or mobile network." When I try to launch Wallet.
Any Ideas? Maybe point me to the right thread. I could very well just not be getting the search results i'm looking for of course.
Always appreciative of the help.
http://forum.xda-developers.com/showthread.php?t=1881914
Sent from my Evo 4G LTE ( ͡° ͜ʖ ͡°)
Related
So I have gotten a 3d 2 weeks ago as a replacement through asurion for my broken evo 4g and like most people on xda it is only natural to root it and slap on a rom the second you get your hands on it. I checked the hboot and to my hearts content it was 1.4, and easy as cake to root since I was coming from evo 4g. The dilemma is that I have tried several roms and everyone I have loaded would give me random reboots and eventually it would just keep rebooting as soon it loads to the home screen. Realizing maybe if I just loaded it back to stock it would help. The random reboots have cut down but I still get it and it's really frustrating. I have checked the battery and it is not loose, and at this point I don't know what to do. I realize that if I go to the sprint store I have to be able to show them the problem. I am also worried that they will update my hboot to 1.5 and claim that I didn't update system software and just send me on my way. Anyone experiencing the same symptoms as mine? Should I just bring it in to sprint to see if I can get a new one?
Thank you
Sent from my PG86100 using Tapatalk
They will update it I suggest you use a format all zip and flash a haus stock rooted ROM or run a ruu hour that works the got me that way updated my phone cause it was over heating
Sent from my PG86100 using Tapatalk
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Yeah I loaded the RUU on it and turned S-off back on. Just sucks because when it doesn't random reboot or bootloop it works great.
Sad Panda said:
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Click to expand...
Click to collapse
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Is your battery loose?
I thought I had this problem at first too but I just popped a business card behind the battery and Viola no random reboots
Sent from my PG86100 using xda premium
bakarus said:
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Click to expand...
Click to collapse
Not a problem at all, that is what the community is all about. Free exchange of information, open source advancement of the platform and technology. Everyone gives a little, and takes a little.
I know there is a dialer code that works to give you that information without the need to install any application, or the need for root access, but after lots of research I was unable to find which one would give that info. However, there is a very useful app that you might want to have anyway. It is called "elixir 2", available on the market for free. Once installed, information > click"processor" > more information > processor: (mine says: ....rev. 2 (v71))
Let us know what yours says [for curiosity sake] please
Quick note, if you replaced the phone through asurion and try to replace it doesn't sprint, don't they refer you back to asurion?
Sent from my PG86100 using xda premium
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
kpsingh said:
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I requested then not to and they still did the update
Sent from my PG86100 using Tapatalk
So just an update, I finally decided to bring it in store today with it rooted and s-off. I was just so sick and tired of it randomly rebooting I just walked into the Sprint store. Technician brought it in, updated the hboot 1.5 =*(. I checked bootloader, and of course I see the locked in capital letters, but I am still s-off. Does that mean I can still load TWRP and root it? Or do I have to follow the HTC method to root it? Thanks for all the help guys!
If it still says s-off, i believe you are good! but that sounds odd, because otherwise we should all be able to update are hboot after rooting? If anyone knows about this...but anyway...
It was not the hboot upgrade but the firmware upgrade that you needed. You did not have to take it to sprint to do that, they have the firmware update without hboot flooting around the dev threads. 2.3.4 and above roms require the new firmware or you'll get the problems you had. No that you have the firmware a lot of the more cutting edge roms still get reboots with most advanced kernels, you have to watch your rom kernel combo, or stick with the stock kernel.
As for flashing, if you really are s-off still, then you can flash anything you want just like on the ol 4g Let us know. Lucky bastard, have fun
[edit] Found this a few threads down:
"I did what you did, had 1.40 and flashed the wrong update, got 1.50 LOCKED with S-off. You can still flash ROMs and Kernels with no issues. I just had to reload TWRP recovery. Then I flashed the 1.40 Bootloader and all was well.
You can grab 1.40 and flash from here: http://forum.xda-developers.com/show...eng+bootloader
***To others reading this...do not flash this, unless you are S-OFF with 1.50 hboot***
You do not need to UNLOCK using the htcdev method. Just flash the 1.40 hboot and you will be fine."
So reinstall twrp, flash 1.40, and have 1.40 s-off and flash the good way
Yep just flashed old hboot 1.3 and merrily rooted, so far so good running cleanrom 2.9 and taking sad panda's advice trying to figure out if it's app related. I am suspecting that it is groove ip running in the background. So far just installed cleanrom and added tapatalk and SwiftKey
Sent from my PG86100 using Tapatalk
Hey everyone,
Im running CM10, wallet has been working fine. Went to test it the other day and Im getting the "not available yet for your device or network" message. Ive not changed anything, the app was working since it updated last. Im afraid to flash another rom until I can clear wallet, since it was linked to this rom. I tried the build.prop edit to get it saying htc_jewel on the 3 proper fields to no avail. Ive also uninstalled the latest wallet update, I am instantly prompted to update upon opening.
Any suggestions?
Thanks!
You should still be able to use it, I'm on decks 9/15 with no wallet issues
I've never had to clear wallet myself, i think google fixed that mistake long ago. fear not mortal! flash that rom!
om4 said:
You should still be able to use it, I'm on decks 9/15 with no wallet issues
Click to expand...
Click to collapse
Thats what I dont get, Im on 9-6 and it was working fine one day, then I get the error.
Should I flash up to 9-15?
Spyderekz said:
I've never had to clear wallet myself, i think google fixed that mistake long ago. fear not mortal! flash that rom!
Click to expand...
Click to collapse
This is my second evo lte, as I didnt clear wallet on my first flash and bricked the secure element.
I'm on my third phone now, for different reasons... but as i said, never ever cleared google wallet settings. never had a problem. even this and last week i been flashing 2x a day not being able to decide between CMX or Viper4G.. I think google fixed that problem. just leave wallet alone and flash a different rom. if it makes you feel batter do a dirty flash with out wiping
Spyderekz said:
I'm on my third phone now, for different reasons... but as i said, never ever cleared google wallet settings. never had a problem. even this and last week i been flashing 2x a day not being able to decide between CMX or Viper4G.. I think google fixed that problem. just leave wallet alone and flash a different rom. if it makes you feel batter do a dirty flash with out wiping
Click to expand...
Click to collapse
This^^^^^
Forget about clearing wallet.
Sent from my EVO using xda app-developers app
Against my better judgement, I flashed over cm10 without clearing wallet. Reinstalled on new rom and everything is working like a charm. Thanks for the push in the right direction guys
If I'm flashing a rom to update my current I don't reset, if I'm switching to a different rom I reset. I'm a bit paranoid like that, at this point I'm going to say it's not a problem
I've never reset/cleared Gwallet and i got my phone on pre-order. . I don't know how many times i flashed new roms but it's a lot. I really think resetting/clearing gwallet was causing the problems. This is complete speculation however
Hate to make my first post an issue post, but I have searched all over XDA for the answer and couldnt find anything particular to my issue. I flashed CM10 to my phone and noticed my Bluetooth would turn on but would not pick up any devices in device search. I tried multiple speakers and headsets and nothing would work. I did a hard wipe and installed MeanBean thinking that it was a ROM related issue. Tried it again on MeanBean and same issue. I tried fixing permissions and Bluetooth Fix app and still nothing. Can anyone help?
(I am on the latest radio/firmware and v.06 MeanBean)
Same exact issue !
cauger24 said:
Hate to make my first post an issue post, but I have searched all over XDA for the answer and couldnt find anything particular to my issue. I flashed CM10 to my phone and noticed my Bluetooth would turn on but would not pick up any devices in device search. I tried multiple speakers and headsets and nothing would work. I did a hard wipe and installed MeanBean thinking that it was a ROM related issue. Tried it again on MeanBean and same issue. I tried fixing permissions and Bluetooth Fix app and still nothing. Can anyone help?
(I am on the latest radio/firmware and v.06 MeanBean)
Click to expand...
Click to collapse
My evo lte has been doing this for as long as i can remember also. I've been through dozens of roms and full wipes and still no bluetooth at all, not even recognizable.
Try deleting everything that is paired or was paired and then reboot. You may have Bluetooth defects if that still doesnt work. I have used on many sense roms, cm10, 10.1 varients with no problems. Hope that helps.
Sent from my EVO using xda app-developers app
Im having the same issue
I have updated my radios and noticed that i lost my Bluetooth connectivity. I was originally running meanrom ics until JB came around. Then updated my radios and moved to JB MeanBean. I did an Ruu and got it back to stock. No dice, stock rom Bluetooth still cannot find or be found. I tried my laptop ipad macbook car audio everything and nothing works. I ve never had any issues with my phone and it seems after Jelly Bean Bluetooth is non existent.
Currently I am running
Twrp 2.3.1
Arc Reactor Kernel
MeanBean3.09
Is there a way to see if the actual Bluetooth is borked or if its working properly, "if its sending a signal"?
Is it possible that something happened when upgrading that the BlueTooth became corrupted? or can it just plain old stop working, died?
At that point if it's Borked on several roms
Then it's time to take it into sprint. That's a manufacturer defect / issue and they should swap it out. Assuming you bought legit from them
Sent from my EVO using Tapatalk 2
Yes I bought it legit when it came out. I also have the insurance plan with Sprint. The only thing I'm worried about is the new hboot and unlocking/rooting the new phone .
But I guess if it means a new phone then I guess its best... To get a fresh new evo
Sent from my EVO using xda app-developers app
First off,
Thanks for taking the time to view this post and offer any help.
Second, sorry if it's in the wrong place (Never really sure of the right place these days)
Finally, the problem:
This morning my phone had no signal at all for a good few hours till restart. I got signal back then shortly afterwards it drops again not to come back on till a restart. I have done a clean flash of the ROM and it is still persisting. Oh and I forgot to say that now my radio is asking for superuser access constantly which makes the phone unusable, this doesn't restore the signal though. I have also tried flashing Evervolv with the same result.
Any ideas?
EDIT: Now the phone won't get any signal at all, even after a reboot and full wipe, it's like the rom can't access the radio receiver (No idea if i decribed that right)
EDIT: I have a feeling this may relate to my problem. Could anyone confirm or correct me?
http://forum.xda-developers.com/show....php?t=1497246
Seems like that link you provided is down right now. Have you tried flashing the stock ICS ruu? Not sure whether your CDMA or gsm.
Just checked the link there and its working now. I'm not sure what I did but after reflashing disarmed toaster (for like the 10th time) it seems to have done the trick. No problems with signal anymore.
I would still like to know what caused it for future reference though. And I'm gsm
Sent from my Evo 3D GSM using xda app-developers app
Joe.Tolchard said:
Just checked the link there and its working now. I'm not sure what I did but after reflashing disarmed toaster (for like the 10th time) it seems to have done the trick. No problems with signal anymore.
I would still like to know what caused it for future reference though. And I'm gsm
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
Maybe not, the problem is back again, going to get a stock rom and test that
I had my phone rooted and unlocked with freegee. I have had many roms on the phone and nfc worked great. I flashed a couple of the 4.4.1 and 4.4.2 roms and never had a problem with nfc working. Google wallet did not work and isis would refuse to install. Even with the xposed trick. So I went back to my trusty nocturnal rom and everything worked great. Then I seen that isis updated and now says it supports kit kat. So I flashed psx 4.4.2 12/31 and the att nfc fix. At that point I was unable to turn on nfc. I flashed back to nocturnal from a back up and same thing, nfc would not turn on. I did a wipe and a reflash and same thing. Even did a lgnpst using and same thing. So I went and got a new phone under warrenty. rooted unlocked and reflashed psx and same thing happened. I attached a logcat in the hopes someone can help me out.
Hmm, not sure if this is any help, but I am running PSX 12/2 build and I can confirm that NFC is working. Never tried Isis though.
Its so strange, and I figure out how this happened twice. I could just return this phone but I don't think it's a hardware issue and flashing back to stock should have fixed any software issues
Sent from my LG-E970 using xda app-developers app