Database Develop

[Q] Google Wallet Weirdness

Just flashed ViperOne 3.1.0 and since then my Google Wallet Tap to Pay hasn't worked. In the Settings - About it says "Unavailable (NfcPaymentSetupFailure: 1)" I've hard reset and reflashed, but I have not reflashed a different ROM, and since nobody else in the ROM thread seems to be having (or have noticed) this issue, I was looking for some sort of guidance.

Fatmouse said:
Just flashed ViperOne 3.1.0 and since then my Google Wallet Tap to Pay hasn't worked. In the Settings - About it says "Unavailable (NfcPaymentSetupFailure: 1)" I've hard reset and reflashed, but I have not reflashed a different ROM, and since nobody else in the ROM thread seems to be having (or have noticed) this issue, I was looking for some sort of guidance.
Click to expand...
Click to collapse
I tried to roll back the update by installing a previous version, then updating.I have the same problem though, I sent an email regarding that to google. I should find out if there is a fix from them in a few days. Im assuming it will be fixed in the next update. Bummer for sure, Cool rom though!

GravyD said:
I tried to roll back the update by installing a previous version, then updating.I have the same problem though, I sent an email regarding that to google. I should find out if there is a fix from them in a few days. Im assuming it will be fixed in the next update. Bummer for sure, Cool rom though!
Click to expand...
Click to collapse
I'm pretty sure the newest firmware is required for it to work. I had it working before flashing to the ViperONE Rom and since then the tap to pay has failed to setup, yet, others in the ViperONE forum say that it works fine for them, but they are on the newest firmware as well.
I'm looking for a link and am going to flash it to see, I'll report back here and the Fiper forum when I'm done with my findings.
EDIT: Nope, firmware didn't matter. My NFC chip si working, I've tested that. But I even unlinked my phone, uninstalled Wallet and re-installed and I get the same error.
EDIT 2 GOT IT WORKING: For anyone else having this issue I seem to have fixed it.
For whatever reason my build.prop wasn't quite right. There is suppose to be a ro.product.model and a ro.product.brand but mine was a little wonky and showed 2 ro.product.brands, under one of them is suppose to be htc but the other said "htcro.product.model=HTCONE" I edited this one using Root tool box to be ro.product.model and changed it's value to HTCONE. rebooted and google wallet doesn't show the error anymore. going to the google wallet website also reflects the fix. Instead of showing a device as "unknown" it shows it as "HTCONE" Now time to go test it.

Can't thank you enough. Fix worked for me

No sound then baseband on GT-I9305 - tried everything

My Galaxy S3 GT-I9305 LTE was running Liquid Smooth 2.37. I bought the phone second hand, it arrived loaded with a stock ROM for Australia's Optus network.
I promptly rooted and flashed the phone to Liquid Smooth and the phone ran fine for months on the 2 Degrees Network in New Zealand.
Recently, (not sure how) I lost notification and phone ring sounds, I first tried restoring my cwm backup on an external sd card - it failed.
Then, after numerous reinstalls, trying various LS and other roms, I lost baseband and have no cell signal - but after flashing to a stock 4.3 rom I have sound back.
In the phone's 'about' section the baseband field is empty.
I've read tons of help posts but nothing works, maybe I need a more methodical approach, but every entry point seems to have a roadblock.
Here's a few of the things I've tried with results in brackets,
Firstly, I thought I'd re-flash back to the phone's original stock ROM using Kies, but the weird thing is Kies doesn't restore, it upgrades to the latest 4.3 ROM, which fails to restore baseband.
I wanted to send the phone back to the 4.1.2 it came with or was it an earlier ROM? I can't remember as I didn't note it down.
Anyway, I must have tried reflashing a dozen stock roms I've found online using Odin. Some of them partially work, I get sound back, (it seems only the 4.3 ones work, with the german I9305XXUEMKC I9305VD2EMK2 reliably loading - it even gives me a NZ english install option) but none restore the baseband.
And all the ones I've found for Optus, which should work, including earlier Android stocks, are rejected. I get the 'unsupported device' or status 7 error in Odin.
I've tried 'fixing permissions' in cwm then reinstalling but I get the same 'status 7' error.
So I decided to install I9305XXUEMKC, install cwm, root the phone and try installing different baseband kernals and/or custom roms to fix the (probably corrupt) efs.
But I'm going round in circles trying to root the phone. Using CWM, supersu shows as successfully installed, but when I boot into the OS, root checker shows my phone is not rooted. Knox seems to obstruct every attempt I make to disable it as well. I keep getting these 'knox stopped etc...from working messages'.
I'm at my wits end. I can't revert back to an older rom, I can't root and modify any existing 4.3 roms.
I want to try everything before I have to ship the phone off to a repairer who may charge me hundreds of dollars to fix the phone.

Odd problems with APN not sticking on Lollipop...

Little background:
I was running Alliance and it was great, decided to be stupid and really wanted MIUI.
So...I stupidly thought I could make MIUI work (I know, I know, I'm retarded). Installed MIUI and of course soft brick, no biggie.
Then Odin'd back to stock (downgraded to NCE). Everything was fine.
Rooted w/ TowelRoot. Installed Busybox and Flashfire and then installed Twi5ted Lollipop.
APN settings wouldn't stick so I thought it might be something wrong with the ROM so then I installed TMS5 (wiped, etc) and everything worked.
Decided I wanted to back to Alliance and wiped, Flashfired Alliance and APN settings won't stick again.
Keeps saying SIM card not inserted, then it will grab a bar or two, then nothing. Try to change APN settings, they won't save, try to reset APN settings back to default, rebooted, etc etc etc.
TLDR:
1. Alliance
2. MIUI (softbrick)
3. Stock NCE via Odin
4. Root, flashfire, busybox etc
5. Twi5ted (APN no worky)
6. TMS5 (APN worky)
7. Alliance (APN no worky)
Thanks for any help!

lollipop-related
Bump.
So, I've read a ton of threads in the past week related to this issue. I have a gs2 on at&t and a gs3 on sprint, and I recently decided to jump away from good old kitkat for lollipop, so naturally I tried cm12 first. Great, both galaxy's love it. But I've tried everything under the sun to get APN's to stick. Ive only found one thing that worked, and its really only a temporary solution, because if you reboot, they ALWAYS get deleted and permissions to write get screwy again.
So, on both phones, I had to wipe everything and flash cm11. Then I dirty flashed cm12, which I didn't even think would work, but for some odd reason it did, and while still in the recovery console (before first boot!) I flashed one of those APN patch scripts to flash the APN's instead of trying to copy the XML later (it always gets deleted on next boot) nor use the actually APN utility in lollipop... And as long as you DONT connect to WiFi on initial setup when you boot, youll notice the flashed APN's show up in the list. DONT EDIT THEM... lol
They won't connect for a couple minutes usually, but after a couple minutes both phones connected... Idk if this will work on your gs5, but it worked for my 2 and my 3 which are both on different providers.
OK, I know that was long-winded and not that useful, but I tried literally everything to address this problem, with no luck. Apparently its super common across a ton of devices that upgrade to lollipop, whether a stock or custom ROM.
I tried setting permissions manually to EVERY ditectory or file that stores anything from the modem. In the data directory, in efs, in system... On every XML and db file. Nothing seems to allow them to be written correctly through the system. And everywhere I found anything on the Google dev forums, Google denied the possibility that its actually a system level problem, and their fault.
Good luck, and please let me know if you find any actual way to solve the APN issue, not like my tricky little workaround that SUCKS if your phone ever dies. lol

[Q] Odin flashed successfully...but GS5 won't boot?

So I was running a 4.4.x ROM and it was working great...then my company bought me a wifi-only tablet and that's pretty much useless for me without some tethering, and for whatever reason FoxFi didn't work with my ROM. I searched Google for days, tried mods and all sorts of Xposed stuff, but nothing worked. So I gave up and figured I'd try a new ROM. No reason not to switch to Lollipop, while I was at it - especially because the ROMs currently supported are all 5.0. So I flash a stock 5.0 firmware and tried a ROM - tethering didn't work. Tried another. Same deal. So fine - if i'm going to have no tethering capabilities, I'd rather have it with my old ROM and Nandroid backup.
Using Odin, I flashed the stock firmware that I've been flashing for a year now. It has worked every time in the past. But this time, Odin worked, and passed, and everything looked great - but when I booted up the phone, it starts to boot up, gives me the unlocked lock picture screen, then starts to load the Samsung image, stops mid-way through, and ... NOTHING. Screen goes blank and it hangs forever. I re-flashed with Odin a dozen times...nothing. Wiped data, wiped cache...nothing. I'm out of ideas and apparently Google hasn't seen this before, as far as I can find.
The image is where it stops loading the Samsung logo and then it just goes black.
Please. Help.

isellmidgets said:
So I was running a 4.4.x ROM and it was working great...then my company bought me a wifi-only tablet and that's pretty much useless for me without some tethering, and for whatever reason FoxFi didn't work with my ROM. I searched Google for days, tried mods and all sorts of Xposed stuff, but nothing worked. So I gave up and figured I'd try a new ROM. No reason not to switch to Lollipop, while I was at it - especially because the ROMs currently supported are all 5.0. So I flash a stock 5.0 firmware and tried a ROM - tethering didn't work. Tried another. Same deal. So fine - if i'm going to have no tethering capabilities, I'd rather have it with my old ROM and Nandroid backup.
Using Odin, I flashed the stock firmware that I've been flashing for a year now. It has worked every time in the past. But this time, Odin worked, and passed, and everything looked great - but when I booted up the phone, it starts to boot up, gives me the unlocked lock picture screen, then starts to load the Samsung image, stops mid-way through, and ... NOTHING. Screen goes blank and it hangs forever. I re-flashed with Odin a dozen times...nothing. Wiped data, wiped cache...nothing. I'm out of ideas and apparently Google hasn't seen this before, as far as I can find.
The image is where it stops loading the Samsung logo and then it just goes black.
Please. Help.
Click to expand...
Click to collapse
I'm not saying you file that you are using is messed up but I've been using the NCE downgrade file in this thread
http://forum.xda-developers.com/showthread.php?t=3076803. It's in the OP, step 5 in the notes section. Worth a shot.

[Q] Android Process FCs and General Device Instability After Flashing MMB29V

Hello all. Generally I've been able to troubleshoot all my Android issues on my own. Most of the time someone has had the same problem (amirite?!). However, I'm stumped and could use a little help from the community.
I've been going along on Marshmallow with FK as my kernel. Generally, waiting a bit to take an update til SuperSU was confirmed all working correctly and that there wasn't any surprises. I had been putting off the MMB29V update for a bit just because everything was running fine and I had no real reason to upgrade. Well, one day I started getting a few FCs and things seemed a bit off performance wise so I decided that I'd go and move on to the next release.
Now, since I've had my N6 I really haven't had the need to run a custom ROM which is completely unlike my old habits on the S3. I decided that it's been a while since I've checked out AOSP so I flashed MMB29V using the batch file with no issues and then DU and their recommended GApps. Here's the first hint of an issue. When I loaded up the OS for the first time I got acore and phone FC's constantly. I instantly thought that I didn't wipe something or that I had a bad zip. I re-downloaded everything and checked MD5s. Everything looked good and after the flash I was able to get through the setup wizard without any issues. As I was sitting there checking out the tweaks and options available I started getting FCs again. It seemed related to Google apps. I did the whole process a second time and still had the same issues. Basically it seemed like at some random point in time the FCs would come and then shortly after the device would be highly unstable. I'd get random reboots, etc. Looking at the stack traces the errors seemed like odd NPEs and native errors.
I decided that AOSP wasn't going to cut it right now if I was going to have a relatively unstable phone and went to flash completely back to stock. Much to my surprise I still got the same errors! Apps like Feedly would never even be able to open. They would just FC on launch. The device hot reboots. The phone process seems to crash during most calls. I triple checked my MD5 on the download from Google. Made sure I wasn't doing something super stupid. I even tried doing the factory flash, booting to the welcome screen, then powering down, going to stock recovery, and factory resetting before continuing. All the same errors.
I've flashed back to complete stock a few times before without any issues. I've been able to flash system.img without any issues. Now it seems like the phone is completely unstable no matter what I do. I get the "Your device is corrupt. It can't be trusted and may not work properly." (red) message when doing a cold boot.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?
I've burned through two backup cards of Google 2-Step backup codes! I'd really like to figure this one out!

mikejr83 said:
.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?!
Click to expand...
Click to collapse
You could read the OP of the following thread and flash a debloated and prerooted ROM.
http://forum.xda-developers.com/showthread.php?t=3059493

I guess I'll try that. I'm still scratching my head why a flash from the factory image is still suffering from FC's and general instability. It also concerns me that I get the corrupted message at boot. It would be one thing if I flashed factory, then put a recovery, kernel, and rooted, but I haven't done that.
Hopefully I'll get a chance to try that this evening. Thanks for the link to that image. It's pretty much what I run when I take an update.

N, n, ne, necromancy!
I brought this thread back to life because I've never been able to solve the instability issues since my last post back in March.
Having some free time lately I decided to nuke my device and start again. I first grabbed the latest stock image and flashed stock. Then I downloaded the latest TWRP and Dirty Unicorns and decided that I'd give it a whirl again. I had FC issues right after the first go at it. I decided to try another GAPPs and do it again. I was able to get through setup. It took a few hours but the FCs started again.
I decided that I would try factory resetting the device and then starting a setup. I remembered that on my previous devices that I sometimes would have to do an immediate factory reset after flashing.
Well that did crap. FCs are random. The device is stuck booting now after a hot reboot.
How can I debug this? What do I need to grab from a logcat? Is there a way to run something like memtest to see if there is a bad section of RAM and something against storage to see if there is a bad sector?
This is frustrating as hell!