Patched Google Wallet for Galaxy S4
(Version 1.x - Old Version)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Description: This method (nearly identical to my previous thread for the Verizon Galaxy S III) will help you get Google Wallet working on your Verizon Galaxy S4, regardless if you have a TouchWiz-based ROM or AOSP-based and whether it's Odexed or Deodexed. This should also work on AT&T/Sprint/T-Mobile Galaxy S4 as well.
Please Note: In order to use this method you need to be rooted and have a custom recovery (1, 2, or 3).
Video Demos of the Full Process (Courtesy of 17akota and DroidModd3rX)
Click to expand...
Click to collapse
Downloads (Version R96 v16)
TouchWiz Only - Download Link
AOSP Only - Download Link
Click to expand...
Click to collapse
How to Apply Mod
1. Make sure you have no Google Wallet pre-installed, or if you do, reset data on it
2. Once you have reset the data, go to the Wallet app in your Application Manager
3. Select to "Clear Cache", then to "Clear Data"
4. If you see "Uninstall Updates", select that button, but if you see "Disable" button leave it alone
5. Using a root explorer and text editor, change build.prop lines to correspond to this
Code:
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
6. Keep an old version as a backup
7. Copy the TouchWiz or AOSP zip file for the mod to your phone/SD Card
8. Reboot into your recovery and flash the Google Wallet mod
9. Boot back into the OS and open Xposed Installer app (should be installed after flash)
10. Select "Install/Update" and allow root access if it asks
11. Reboot your device
12. Download and install Paul's Xposed Wallet apk
13. Launch Xposed Installer app again and go to the "Modules" tab
14. Enable the module by checking the checkbox for it
15. Reboot your device again
16. Now open Google Wallet and setup everything as needed (PIN/Security/Cards, etc...)
17. After it is all setup and working, change your modified build.prop back to ONE of the below
Verizon Galaxy S4
Code:
ro.product.model=SCH-I545
ro.product.name=jfltevzw
ro.product.device=jfltevzw
AT&T Galaxy S4
Code:
ro.product.model=SGH-I337
ro.product.name=jflteatt
ro.product.device=jflteatt
T-Mobile Galaxy S4
Code:
ro.product.model=SGH-M919
ro.product.name=jfltetmo
ro.product.device=jfltetmo
Sprint Galaxy S4
Code:
ro.product.model=SPH-L720
ro.product.name=jfltespr
ro.product.device=jfltespr
18. Reboot your phone normally one last time and you will be all set
Click to expand...
Click to collapse
When Changing Roms
1. Open Google Wallet
2. Press the Menu key on your device
3. Select "Settings"
4. Select "Reset Google Wallet app"
5. Select "Reset" button
6. Flash your new ROM and/or wipe as needed
7. Follow "How to Apply Mod" directions again from the beginning
Click to expand...
Click to collapse
Updating to New Version Anytime
1. Follow "How to Apply Mod" steps #5 and 6
2. Reboot your device
3. Open the Play Store and update Google Wallet
4. Open Google Wallet and test everything is working
5. If all is good, follow "How to Apply Mod" steps #17
6. Reboot your device again and confirm everything still working
Click to expand...
Click to collapse
Credits
Credit goes to PaulOBrien for providing the patched Google Wallet apk (Original Post)
Credit goes to tonu42 for creating the original thread for the mod (Original Post)
Credit goes to rovo89 for creating the Xposed Mod (Original Post)
Credit goes to joemagistro for creating the deodexed-only version of this mod in the T-Mobile Galaxy S4 section (Original Post)
Everything seems to be working. I will have to head to McDonald's tomorrow and give it a try. Thanks!
Well I got this working from the other thread but looks to be same methods which is fine.
Now poking around... I noticed I have a devices section on the Wallet website and see I can reset it remotely if anything happens (though I wouldn't test that for ROM issues). Nice to know... is this more a secure element self destruct?
Also I notice a section asking to "Verify Identify" which if required... I will. But I am already reading where people have entire Play Store/Checkout locked out over this permanently over this. I just hope I don't get my account screwed one day because Google hates the grocery which I shop at or some lame thing where GPS is off by 500ft and claims I'm not there.... I know farfetched and over the top but just concerned or if anyone had issues with this.
Ok it works for me untill I change my build.prop back. What am I doing wrong
Sent from my galaxy nexus using xda app-developers app
coolsilver said:
Well I got this working from the other thread but looks to be same methods which is fine.
Now poking around... I noticed I have a devices section on the Wallet website and see I can reset it remotely if anything happens (though I wouldn't test that for ROM issues). Nice to know... is this more a secure element self destruct?
Also I notice a section asking to "Verify Identify" which if required... I will. But I am already reading where people have entire Play Store/Checkout locked out over this permanently over this. I just hope I don't get my account screwed one day because Google hates the grocery which I shop at or some lame thing where GPS is off by 500ft and claims I'm not there.... I know farfetched and over the top but just concerned or if anyone had issues with this.
Click to expand...
Click to collapse
I wouldn't worry too much about those, I think the remote reset from the website just wipes the app by itself, the secure element stays working so it can be passed on. Highly unlikely and unnecessary that Google will want to brick a secure element for security purposes.
iTechWNC said:
Ok it works for me untill I change my build.prop back. What am I doing wrong
Sent from my galaxy nexus using xda app-developers app
Click to expand...
Click to collapse
Which method did you use? What happens when you restore the build.prop? I personally have this running back on the stock build.prop using method A, so I know no issues on that one.
Will this work for the at&t phone of the same model sgh-i337? Stock rom rooted.
Sent from my SAMSUNG-SGH-I337 using xda premium
I'm currently stuck in "identity verification hell" and can't use Wallet even on my 100% stock Nexus 7. not happy. I sent them my license and a utility bill already and they still want more (SS card) which seems ridiculous. Amazon Payments was required to collect SSNs not too long ago...but they didn't require a freakin scan of the original document.
ugh.
anyway: Method A works great for me (still on TouchWiz for now sadly).
anyone else notice that when you change the build.prop product name, if you long-press the home button you see three icons along the bottom of the screen instead of "Task manager", "Google", and "Close All"? I believe that's what AT&T/T-Mo users see by default. wasn't enough to get rid of that stupid WiFi notification though
Sent from my SCH-I545
djdef80 said:
Will this work for the at&t phone of the same model sgh-i337? Stock rom rooted.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
The way I designed it I'm pretty sure it should. Give it a try and let us know.
trogdor3222 said:
I'm currently stuck in "identity verification hell" and can't use Wallet even on my 100% stock Nexus 7. not happy. I sent them my license and a utility bill already and they still want more (SS card) which seems ridiculous. Amazon Payments was required to collect SSNs not too long ago...but they didn't require a freakin scan of the original document.
ugh.
anyway: Method A works great for me (still on TouchWiz for now sadly).
anyone else notice that when you change the build.prop product name, if you long-press the home button you see three icons along the bottom of the screen instead of "Task manager", "Google", and "Close All"? I believe that's what AT&T/T-Mo users see by default. wasn't enough to get rid of that stupid WiFi notification though
Sent from my SCH-I545
Click to expand...
Click to collapse
Wow sorry to hear about all that difficulty. Hope you get it resolved with Google promptly! Glad to hear the method worked for you though (as expected).
On an unrelated note take a read at this thread here regarding the icons instead of words and also the Wifi notification fixes: http://forum.xda-developers.com/showthread.php?t=2295622
!!!! Gonna try this today
Sent from my SCH-I545 using Tapatalk 4 Beta
Awesome! Going to switch to odex rom and try later. Hopefully this works!
Sent from my SCH-I545 using Tapatalk 4 Beta
open1your1eyes0 said:
On an unrelated note take a read at this thread here regarding the icons instead of words and also the Wifi notification fixes: http://forum.xda-developers.com/showthread.php?t=2295622
Click to expand...
Click to collapse
brilliant! thanks for sharing
Sent from my SCH-I545
Method A , Step 7. Reboot into your recovery and flash the Google Wallet mod
The file downloads as JFLTEVZW-Wallet-TW-JB-1.6-R96-v16.zip.zip
It's a nested zip file. does it need to be unzipped one level first or is that just the name of it ?
Mine has been at 'setting up this could take 5 minutes' for 10 minutes. I used Method A.
Nice, just finished Method A.
ZIP file was fine as is.
Everything appears to be working. Will confirm after i get to make a purchase at some point. Thanks!!!!
Edit; I had previously used Google Wallet on my Galaxy Nexus so everthing came back, cards, etc. easy peasy.
What happens if we follow all steps properly and get Wallet working, but then flash the 3Minit framework after in order to use the UI tweaks that the 3Minit app offers? Does that mess anything up for Wallet or is that Xposed framework needed permanently?
Parafly said:
Method A , Step 7. Reboot into your recovery and flash the Google Wallet mod
The file downloads as JFLTEVZW-Wallet-TW-JB-1.6-R96-v16.zip.zip
It's a nested zip file. does it need to be unzipped one level first or is that just the name of it ?
Click to expand...
Click to collapse
My mistake, it's not actually a nested file if you look inside, I just forgot to rename it. I'll reupload with proper name to avoid confusion.
EVOme said:
Mine has been at 'setting up this could take 5 minutes' for 10 minutes. I used Method A.
Click to expand...
Click to collapse
This one did take some time for me as well, usually just let it be there for about 5-15 minutes. It checks a lot of stuff in the background at this point.
open1your1eyes0 said:
This one did take some time for me as well, usually just let it be there for about 5-15 minutes. It checks a lot of stuff in the background at this point.
Click to expand...
Click to collapse
Wow!! That took like 23 minutes to configure, but it's working!!!!!!!!! Solid work on this. This was the only thing my S4 was missing.
THANKS!!!!!!!!!!!!!!!!!!!!!!!!!
just4747 said:
What happens if we follow all steps properly and get Wallet working, but then flash the 3Minit framework after in order to use the UI tweaks that the 3Minit app offers? Does that mess anything up for Wallet or is that Xposed framework needed permanently?
Click to expand...
Click to collapse
The Xposed framework is needed to stay there for Google Wallet to patch properly but if I understand that 3Minit mod correctly I think it just added an additional patch to the Xposed framework to enable and doesn't need to replace it? Could be wrong but I think it should be fine.
I already have xposed framework installed. Do I have to UN install it before doing this? I'll lose all my mods.. and have to set it all up again, grr.
Sent from my SCH-I545 using xda premium
ticrandall said:
I already have xposed framework installed. Do I have to UN install it before doing this? I'll lose all my mods.. and have to set it all up again, grr.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
In that case not required. All you have to do is update the new one that this mod flashes, the rest should remain the same however.
Related
DO NOT USE THE ZIP ON 4.1.2 based ROMS. For 4.1.2 roms: Copy wallet R96 into /system/app and set permissions appropriately. Files from the new Sprint leak appear to fix the "reader not detected" problem (since wallet will be officially supported on the sprint variant) and I will upload a new zip shortly. (Unless someone has time to do it sooner)
For 4.1.1 roms:
Thanks to Its Twix for the write up & ogdobber for the technical support and making the zip
A Complete and Utter Idiot's Guide to Getting Google Wallet Working on the Verizon Note II, Running Touchwiz ROMs:
1) Create a Nandroid backup in Recovery.
2) Flash NoteII-lib_nfc-fix-r87.zip from custom recovery and wipe Cache.
2) Run Google Wallet and see if it works. If you haven't setup Google Wallet before, it will most likely crash at "Setting up Google Wallet. This may take 5 minutes." *If you have already setup Google Wallet and get a crash error after switching ROMs, look for the other guide at the bottom*
3) If it crashes, use Root Explorer (I refer to Root Explorer because that's what I use but you can use any file explorer that can change permissions and mount system) to Mount system R/W and remove the Wallet apk from system/app
4) Edit build.prop (in the system folder) to be a Galaxy Nexus (CHANGES MADE BELOW).
ro.product.model=Galaxy Nexus
ro.product.name=yakju
product.device=maguro
5) Save and Exit then long press build.prop and make sure permissions are Owner: R/W Group: R Others: R
6) Reboot
7) Download Google Wallet from the Play Store
8) Set up Google Wallet and register a card. Once it finishes registering the card the app will reset.
9) When it resets and asks which account you would like to use for Wallet, close the app.
10) DELETE (not uninstall) the Wallet apk from data/app
11) Navigate to where you saved the modified Wallet zip and extract the files.
12) When the extraction completes, go to the extracted files location.
13) Copy the com.google.android.apps.walletnfcrel.modaco.1.5-r87-v15.apk file and paste it in /system/app (make sure you have system mounted R/W).
14) Long press on the wallet apk file you copied and set permissions to Owner: R/W Group: R Others: R
15) Reboot
16) Run Wallet and go through the setup. It should work now instead of crashing.
17) Reboot
18) Run Wallet. If it still works after the reboot, change your build.prop back to where it was originally (CHANGES BELOW).
ro.product.model=SCH-I605
ro.product.name=t0ltevzw
product.device= t0ltevzw
19) Make sure the build.prop permissions are still Owner: R/W Group: R Others: R
20) Make another Nandroid backup.
21) Go try it out!
NOTE: Google Wallet is not usable everywhere that Bling/PayPass is! Just because it doesn't work at one place does not mean it won't work at another!
Merchants where it is (most likely) guaranteed to work can be found here: http://www.google.com/wallet/how-it-works/in-store.html. Some other places that are not listed there may still work (e.g. McDonald's). Sadly. some places you will go do not even have their Bling/PayPass system on or working so make sure it's actually working before you come back here saying your transaction didn't work.
Hope this helps. Sorry it's so thorough, I just wanted to help out some of those that might not be so used to this sort of thing.
If you are changing to a new ROM and having issues:
1) Flash the modaco r87 zip in the OP and try to run it.
2) Try to add an account. It will probably crash at Adding Account.
3) Change build.prop to be a Galaxy Nexus and fix permissions (follow step 4 of the first guide).
4) Reboot
5) Run Wallet and it should be working again. If it works, change your build.prop back to what it was originally and fix permissions (follow step 18 of the first guide).
6) Go try it out!
If you get an error about Insufficient secure element permissions, reflash the Modaco apk and reboot.
On Beans build4 there is an issue with adding cards. Keep trying and close the app occasionally when trying and it should add the card successfully.
WarlockLord said:
Picked up my note 2 last night. Got google wallet working, activated, and my cards added. But, when I hold the phone to a paypass reader, the wallet app activates and tells me to check with the cashier to see if the transaction went through (but it didn't).
Thoughts?
Nfc.apk and NfcTest.apk or something else?
Click to expand...
Click to collapse
Word on the street is Verizon disabled it, pending their own app for the same purpose to make more money
Your farther then I got. Ha. Downloaded it and it said not compatible with this device. Hope you can figure it out soon.
Yes, but Verizon only disabled access to it from the market and left out some libs. I'm past that part already, just gotta figure out how to trigger the transaction now.
I will definitely be following this thread. Good work getting this far!
Thanks, I was actually responsible for getting wallet working on the GS3 and then some scumbag make a video and took credit for it. Very upsetting. This time I'll make the video myself and give it to the tech sites lol
Ganster. Did you copy all the libs over or add anything to framework?
Sent from my SCH-I605 using xda app-developers app
Deckoz2302 said:
Ganster. Did you copy all the libs over or add anything to framework?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Nothing to framework.... some libs yes. I could only get one specific version of wallet to load the secure element applet, so I used that and then afterwards I upgraded the wallet version to R87.
Made normal changes to build.prop so it thinks its a GNex. Lots of tinkering and playing though, and even if I can get it fully working, it seems the process to get it working on this device will be more complicated than the S3
Is snote still working for you since you changed the build.prop to nexus or no?
Sent from my SCH-I605 using xda app-developers app
Deckoz2302 said:
Is snote still working for you since you changed the build.prop to nexus or no?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I changed it to Nexus just to add the cards. Once the cards were added, I changed it back.
Because this is a modified wallet, it doesn't do the device check on every run. But, in the background, it transmits the value in build.prop to google to get the OK to add the card, and if what is transmitted is not valid, google doesn't allow you to add cards.
Are you sure it doesnt check on card swipe as well? Did you try to swipe with the build.prop as a nexus? Just curious
Sent from my SCH-I605 using xda app-developers app
Yes I did. I didn't change the build.prop back until after I came back to work.
Same thing I always did with the S3 too. Like I said, I think the Nfc.apk passes the data to wallet for the transaction.
Right now I'm trying to find a stock odexed rom for the I9300 (same chip) with android 4.1.1.
I'll have this working by the end of the day
WarlockLord said:
Yes I did. I didn't change the build.prop back until after I came back to work.
Same thing I always did with the S3 too. Like I said, I think the Nfc.apk passes the data to wallet for the transaction.
Right now I'm trying to find a stock odexed rom for the I9300 (same chip) with android 4.1.1.
I'll have this working by the end of the day
Click to expand...
Click to collapse
Thanks for the work man. I am dying without my google wallet, so used to using it on my Nexus that at the store I pulled out my phone and tried-then i realized that wouldnt work. The cashier had to have thought I was nuts. :silly:
http://forum.xda-developers.com/showthread.php?t=1863346
Odin i9300 stock. Not at pc so I cant extract it
Sent from my SCH-I605 using xda app-developers app
Deckoz2302 said:
http://forum.xda-developers.com/showthread.php?t=1863346
Odin i9300 stock. Not at pc so I cant extract it
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
hotfile sucks
That's not a full rom either... just a differential OTA... maybe I'll get lucky and it will have what I need though
Hopefully this gets going. I was playing with it yesterday for sometime but it didn't work
Tap'n
techgov8 said:
Hopefully this gets going. I was playing with it yesterday for sometime but it didn't work
Tap'n
Click to expand...
Click to collapse
How far were you able to get?
I know..but it may have the original odex and nfc.apk ill keep looking
Sent from my SCH-I605 using xda app-developers app
no nfc files in that zip... dammit
WarlockLord said:
Picked up my note 2 last night. Got google wallet working, activated, and my cards added. But, when I hold the phone to a paypass reader, the wallet app activates and tells me to check with the cashier to see if the transaction went through (but it didn't).
Thoughts?
Nfc.apk and NfcTest.apk or something else?
Click to expand...
Click to collapse
Have you tried 1.5 R79 v5?
That is the only version that consistently worked with my VZW Gnex. Other versions installed and let me add cards, however, when it came time for the transaction they would scan but wouldn't go through.
I had the exact same symptoms when not using this version.
Hi Folks,
I created this mod for the Galaxy S4 I9505, However I think this mod would work on AT&T Samsung Galaxy S 4 as it running the same spec phone.
Could an experienced user test this mod and report back if it works, if not if they can upload the nfcnci.apk I will see if I can get the mod working on AT&T.
Before running the program please ensure you have a backup of nfcnci.apk and nfcnci.odex (if the file exists) depnending upon if your rom is odex or deodex just in case the mod does not work.
Now for the Mod
Lockscreen What this does is allows you to use nfc when the screen is on and in a locked status.
Screen Off Allows the use of NFC when the screen is off.
By default NFC only works when the phone screen is on and unlocked. (Suspect always had problem on this one as previously stated)
any feedback appreciated.
Remember to backup before flashing. for that just it case situation.
Enjoy Optimal
p.s. remember people that leaving the NFC on all the time can leave you phone open to security breaches. so please be careful when using this mod.
I can report that screen off mod works. Going to try lockscreen next. Dont know how i feel about NFC being on when screen is off.
DJsCrIBbLe said:
I can report that screen off mod works. Going to try lockscreen next. Dont know how i feel about NFC being on when screen is off.
Click to expand...
Click to collapse
thanks @DJsCrIBbLe for testing. In terms of screen off version it will be a security risk, However a number of users have requested it. I suppose they will just need to ensure they take all relevant security precautions. and protection of there phone
Because NFC can be breached and could cause all sorts of issues and hacks.
anyway thanks for testing its much appreciated.
Optimal
Lock screen works too
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Excellent thanks for testing the mods. Its much appreciated.
Sent from my GT-I9505 using Tapatalk 4 Beta
Do you have the stock NFC version of this mod?
I bricked my GS4 i337's Google Wallet. Everything on my phone works, but I can't get into the Google Wallet App because it requires NFC and the toggle doesn't work anymore. I want to install a new ROM and/or use the current one WITH Google Wallet, but I can access it. Do you have a "revert to stock" version of the NFC mod for the i337?
Can anyone send me a copy of the two original files for the i337 nfcnci.odex and nfcnci.apk and tell me how I revert back?
Please help.
kevinjmoore said:
I bricked my GS4 i337's Google Wallet. Everything on my phone works, but I can't get into the Google Wallet App because it requires NFC and the toggle doesn't work anymore. I want to install a new ROM and/or use the current one WITH Google Wallet, but I can access it. Do you have a "revert to stock" version of the NFC mod for the i337?
Can anyone send me a copy of the two original files for the i337 nfcnci.odex and nfcnci.apk and tell me how I revert back?
Please help.
Click to expand...
Click to collapse
Sent you a PM
Optimal
So neither of these mods worked for me. I'm stock SGH-I337M odex. I still have my regular nfc functionality but it's not working with screen off or at lock screen.
kevinjmoore said:
I bricked my GS4 i337's Google Wallet. Everything on my phone works, but I can't get into the Google Wallet App because it requires NFC and the toggle doesn't work anymore. I want to install a new ROM and/or use the current one WITH Google Wallet, but I can access it. Do you have a "revert to stock" version of the NFC mod for the i337?
Can anyone send me a copy of the two original files for the i337 nfcnci.odex and nfcnci.apk and tell me how I revert back?
Please help.
Click to expand...
Click to collapse
Hi kevinjmoore.
Please install the attached nfc, as per our discussion.I hope this resolves your issue.
Optimal
OptimalKiller said:
Hi kevinjmoore.
Please install the attached nfc, as per our discussion.I hope this resolves your issue.
Optimal
Click to expand...
Click to collapse
Any possible way you could take the Google Wallet modified files, make the edits, and post these? Would be handy for those with the Google Wallet mod.
Aou said:
Any possible way you could take the Google Wallet modified files, make the edits, and post these? Would be handy for those with the Google Wallet mod.
Click to expand...
Click to collapse
Can you explain more about the mod. I might be able to do something. But I need to know more about it.
Optimal
Sent from my GT-I9505
OptimalKiller said:
Can you explain more about the mod. I might be able to do something. But I need to know more about it.
Optimal
Sent from my GT-I9505
Click to expand...
Click to collapse
The mod involves the following things:
Install Xposed Mod
Install Wallet Xposed module (hides root and phone model from Wallet's built-in search) and enable the module
Edit /system/build.prop to fool Wallet into thinking it's a Galaxy Nexus
Stop the system
Replace /system/app/NfcNci.apk
(Remove /system/app/NfcNci.odex)
Replace /system/app/NfcTest.apk
(Remove /system/app/NfcTest.odex)
Replace /system/etc/nfcee_access.xml
Replace /system/lib/libnfc-nci.so
Replace /system/lib/libnfc_nci_jni.so
Replace /system/lib/hw/nfc_nci.MSM8960.so
Clear dalvik cache
Reboot
Setup Google Wallet as you would normally. Get it completely initialized.
Restore build.prop to normal settings
Reboot
The original post includes two different methods of doing this, and I think both involve flashing a zip file from recovery. I don't like flashing zips like that, so I disassembled it and came up with the procedure above. ^_^
Aou said:
The mod involves the following things:
Install Xposed Mod
Install Wallet Xposed module (hides root and phone model from Wallet's built-in search) and enable the module
Edit /system/build.prop to fool Wallet into thinking it's a Galaxy Nexus
Stop the system
Replace /system/app/NfcNci.apk
(Remove /system/app/NfcNci.odex)
Replace /system/app/NfcTest.apk
(Remove /system/app/NfcTest.odex)
Replace /system/etc/nfcee_access.xml
Replace /system/lib/libnfc-nci.so
Replace /system/lib/libnfc_nci_jni.so
Replace /system/lib/hw/nfc_nci.MSM8960.so
Clear dalvik cache
Reboot
Setup Google Wallet as you would normally. Get it completely initialized.
Restore build.prop to normal settings
Reboot
The original post includes two different methods of doing this, and I think both involve flashing a zip file from recovery. I don't like flashing zips like that, so I disassembled it and came up with the procedure above. ^_^
Click to expand...
Click to collapse
Pretty cool will take a look at this weekend to see how is it is to implement.
Optimal
Sent from my GT-I9505
Deleted.
Too bad. I'm getting constant FCs on I9505 with Google Edition port ROM. I tried the lockscreen mod only.
Aleq said:
Too bad. I'm getting constant FCs on I9505 with Google Edition port ROM. I tried the lockscreen mod only.
Click to expand...
Click to collapse
Pm sent to you.
Optimal
Sent from my GT-I9505
Did Lockscreen only and every time I scan a tag I get "unfortunately, nfc payment has stopped" errors. Tags still function though
Ephekt said:
Did Lockscreen only and every time I scan a tag I get "unfortunately, nfc payment has stopped" errors. Tags still function though
Click to expand...
Click to collapse
Hi ephekt
What rom version are you running?
I have 2 threads on the go at the moment.
Optimal
Sent from my GT-I9505
Mint jelly
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Any chance I/we could get a zip to disable this mod. I'd like to try the mood in xposed framework to see if I still get the NFC payment crash.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
There are a few methods and links That have worked for Google Wallet. I would like to post them methods and information. None of this is my work at all. I do not take Credit for any of it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IMPORTANT INFO AND LINKS - PLEASE READ
Note II - I got Working Google Wallet from here - Refer to Crazy Talk OP ----> Click Here
Click to expand...
Click to collapse
Recommended build.prop Editor - Jrummy Build Prop Editor
Click to expand...
Click to collapse
ALWAYS! ALWAYS! ALWAYS! RESET GOOGLE WALLET BEFORE YOU FLASH A NEW ROM OR YOU COULD LOSE IT FOREVER
Click to expand...
Click to collapse
BEWARE - BEFORE YOU BEGIN - 1st Picture provided by fireishott - 2nd Picture by firstflyer
After seeing people struggle and research, this appears to still block Google Wallet from completely setting up and initializing. The regular SIM cards do not do it, but the ISIS or NFC appears to be doing the damage. I am not sure if it is possible to switch to a non NFC SIM, but you are more than likely OUT OF LUCK with this SIM Card...Remember this does not guarantee success, but if you hit a wall and just can't get any luck it is a last ditch effort and probable cause to your issues
Refer to Troubleshooting Step 4 in post #2 to possibly solve the issue
Click to expand...
Click to collapse
LATEST PATCHED GOOGLE WALLET - TouchWiz 4.3 and AOSP - Tap and Pay GW v2.0 R151-v8 - Thanks loserskater - Thread Found Here!
IMPORTANT - BEFORE YOU GET STARTED REMOVE ANY TRACES OF WALLET ALSO ENSURING YOU RESET WALLET FROM THE DEVICE BEFORE YOU REMOVE IT.
_________________________________
1. Download The Following Zips
TouchWiz 4.3 - TouchWiz 4.3 NFC Lib Fix and Patched Wallet
AOSP - Go Here for Patched Wallet - Thanks loserskater
2. Reboot into Recovery
3. Flash Appropriate Zip for your ROM Base (Always Wipe Cache and Dalvick before flashing any zip)
5. Reboot
4. Open Google Wallet and Set up Tap and Pay until 100% Completion with all Cards added ready to purchase
5. Once Google Wallet says Tap and Pay is Ready For Use You are Good
6. Enjoy Working Wallet
Reference these build.props
Galaxy Nexus
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
Verizon Note II
ro.product.model=SCH-I605
ro.product.name=t0ltevzw
product.device= t0ltevzw
Give Thanks To:
loserskater - for libfix and patched wallet
WarlockLord - Original Wallet Thread
crazy talk
safeplayer22
siraltus
YourCancer01
Dwitherel - For latest patched version of Google Wallet R96v16
gramsey1911 - Verizon NFC Lib Fix
jimmypop13 - For trying on CM 10.1 and reporting what he did to get successful install
tomskag - Testing MoDaCo - Confirmed Success
PaulOBrien - MoDaCo Toolkit and Patched MoDaco Wallet Modules
fireishott - All The feedback with troubleshooting
ihavenewnike - Mentioned Jrummy's build prop editor
silvertag - I wanted to put resetting Wallet Online in the OP already, however, he made mention so I give credit to him
BoostedB18C - Extremely helpful with Troubleshooting in the Thread - Thanks
vt0r - Providing information for AOSP
open1your1eyes0 - Instructions for installing on AOSP
If you were left out its not by intention just PM Me
Troubleshooting
TROUBLESHOOTING
1) Insufficient Secure Element Privileges for system image (release-keys).
If you've been trying to run Google Wallet on your USA variant Note II you've probably ran into some problems. like this one..
"Insufficient secure element privileges for this system image (release-keys)."
why is this happening? check HERE for more detail.
But for the sake of keeping everything together in this thread..
2) Google Wallet controller applet version says "not present"
1. Open Google Wallet
2. Hot Menu Soft Key
3. Find About
It should not say Not Present
If It says "Not Present"
You need to do a nand restore of the ROM you had Google Wallet running on and hit reset Google Wallet. Then You can restore or flash a new ROM and restart the process. If you Do not have a Nand Backup where Google Wallet was working, you may never be able to use Wallet again
3) Device Not Ready. Wallet is unable to proceed until this device is fully initialized. Make sure the device has network access and try rebooting if the problem persists.
I have just gone through the whole set up process trying to use the Galaxy Sprint Note II build.prop and the above error message occurred. I could not even reset Google Wallet on my phone unless I changed my build.prop to the Galaxy Nexus which is the one in this OP. If you are having issues, Only use the Galaxy Nexus build.prop if you are not already doing that
Step 1. Change your build.prop to the settings in Method 1 and 2. (Do not reboot after you finished)
Galaxy Nexus
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
Step 2. Download Titanium Backup
Step 3. Use Titanium Backup to wipe Google Wallet App Data and Cache or the built in Application Manager
Step 4. Reboot to Recovery
Step 5. Wipe Cache / Dalvick Cache 3x
Step 6. Reboot
Step 7. Set Up Google Wallet until 100% completion with card added
Step 8. Revert to original build.prop
Verizon Note II
ro.product.model=SCH-I605
ro.product.name=t0ltevzw
product.device= t0ltevzw
Step 9. Reboot
Should be Good to Go. I just completed the whole process
FIX: DO NOT USE ANY OTHER BUILD.PROP CONFIGS. ONLY USE WHAT IS IN THIS OP.
4) "Device Setup Failed"
Once your stuck at 'Device setup failed' you need to reset your wallet from the web. Then change your build.prop to Nexus. Reboot, retry wallet and it should register correctly, after that you can change back your build.prop.
1. Go to Google Wallet Online
2. Log in with your login info
3. Click Devices on the left hand side
4. Click Disable Wallet App
5. change your build.prop to the Galaxy Nexus
Galaxy Nexus
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
6. Reboot Phone and Try to Set up Wallet Again
7. If all Goes Well meaning Wallet is set up 100% and ready for use, you can return to the Stock build.prop
8. Revert to Stock.prop
Verizon Note II
ro.product.model=SCH-I605
ro.product.name=t0ltevzw
product.device= t0ltevzw
9. Reboot Phone after you change back to stock build.prop
10. Enjoy
5) Wallet Freezes During Reset
Wallet Will freeze 9 times out of 10 if you try to perform the reset with your stock build.prop. If this happens then you need to change your build.prop to the Galaxy Nexus
1. Use jrummy build.prop editor or whatever your used to using to change your build.prop
2. Change the build.prop to the Galaxy Nexus
Galaxy Nexus
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
3. Reboot Phone
4. Reset Google Wallet
5. Once Google Wallet Resets you can flash another ROM or continue whatever Troubleshooting you were doing
6) Tap and Play Is Missing
If You Have Wallet Working Already and upgrade from the Market which you can do without any build.prop modification, Tap and PLay will disappear. Before updating you need to change to the Galaxy Nexus build.prop, reboot the phone then update form the Market and you should have no issues
1. Go into Apllication Manager, Scroll to Google Wallet and Wipe Data and Cache for the App
2. Use jrummy build.prop editor or whatever your used to using to change your build.prop
3. Change the build.prop to the Galaxy Nexus
Galaxy Nexus
ro.product.device=maguro
ro.product.model=Galaxy Nexus
ro.product.name=yakju
4. Reboot Phone
5. Open Wallet and Set up Tap and Play until 100% Complete and you get notification that Tap and Play is ready for use!!
6. Once Step 5 is complete, you can go back to your stock build.prop
AT&T Note II
ro.product.model=SAMSUNG-SGH-I317
ro.product.name=t0lteatt
product.device= t0lteatt
7. Reboot Phone
8. Enjoy Working Wallet
7) NFC Error 11 Fix - "nfcpaymentsetupfailure: 11"
1. Go Here
2. Disable Any devices associated to your Google Account
3. Go into TWRP
4. Nandroid Backup Your current Setup
5. Click Wipe
- Slide to Factory Reset 3x
- Click Advanced Wipe
- Wipe Dalvick Cache, System, Data, Internal Storage, Cache 3x
This will clear any Wallet pieces that could be lingering
4. Install Whatever ROM you like
5. Try to install again
Confirmation Post - "nfcpaymentsetupfailure: 11"
Dude your awesome like for real. I upgraded from 4.1.1 a few weeks ago since I finally got the this version of wallet is no longer supported...and well I kept getting failed blah blah. Tried this and it worked first try.
Deckoz2302 said:
Dude your awesome like for real. I upgraded from 4.1.1 a few weeks ago since I finally got the this version of wallet is no longer supported...and well I kept getting failed blah blah. Tried this and it worked first try.
Click to expand...
Click to collapse
Nice Man, glad it worked especially first try lol.....It took me a while to figure out why only the Galaxy Nexus would wrk for resetting and setting up, tired to use Sprint's but it still didn't work and I dont know why cause it worked for some, but the Galaxy Nexus build.prop has more success overall for everyone
bdorr1105 said:
Nice Man, glad it worked especially first try lol.....It took me a while to figure out why only the Galaxy Nexus would wrk for resetting and setting up, tired to use Sprint's but it still didn't work and I dont know why cause it worked for some, but the Galaxy Nexus build.prop has more success overall for everyone
Click to expand...
Click to collapse
I think it was probably more to do with formatting cache repetitivly to completely wipe old data. However my trusty cvs didnt detect my phone...meh
Deckoz2302 said:
I think it was probably more to do with formatting cache repetitivly to completely wipe old data. However my trusty cvs didnt detect my phone...meh
Click to expand...
Click to collapse
Was that prior to installing this method, or did you not try using the wallet at CVS yet? Thats weird wonder why it didnt pick it up, maybe a fluke
bdorr1105 said:
Was that prior to installing this method, or did you not try using the wallet at CVS yet? Thats weird wonder why it didnt pick it up, maybe a fluke
Click to expand...
Click to collapse
Well before I tried this method I couldn't load my cards. Who knows. Im heading to home depot...ill know if it was a fluke after that lol. Either way cards are loaded. Now I can play with the libs to get it working hopefully
Deckoz2302 said:
Well before I tried this method I couldn't load my cards. Who knows. Im heading to home depot...ill know if it was a fluke after that lol. Either way cards are loaded. Now I can play with the libs to get it working hopefully
Click to expand...
Click to collapse
Yea let me know how that works, and if its the libs pm me them or something and I will add the libs to the OP and throw your name all over that
Thanks for the information, OP! This is the first time I've had google wallet set up ever
Mac of York said:
Thanks for the information, OP! This is the first time I've had google wallet set up ever
Click to expand...
Click to collapse
Appreciate it man enjoy
Sent from my SGH-T889 using xda premium
Thank you for the great instruction. Setup was easy and no issues.
Took it to local mcdonald to try but some how it kept asking me to tap again and again so I eventually used my credit card.
NFC was on too. Any ideas?
Sent from Verizon Note II
saint365 said:
Thank you for the great instruction. Setup was easy and no issues.
Took it to local mcdonald to try but some how it kept asking me to tap again and again so I eventually used my credit card.
NFC was on too. Any ideas?
Sent from Verizon Note II
Click to expand...
Click to collapse
Not sure why it was asking you to keep tapping, try at another McDonald's and see if it gives you the same issue again. Reboot into recovery wipe cache and dalvick just because. Also shut nfc off and back on to. If you get the same problem try reflashing the libs. Anyway let me know if you have any success
Sent from my SGH-T889 using xda premium
saint365 said:
Thank you for the great instruction. Setup was easy and no issues.
Took it to local mcdonald to try but some how it kept asking me to tap again and again so I eventually used my credit card.
NFC was on too. Any ideas?
Sent from Verizon Note II
Click to expand...
Click to collapse
I've noticed if I hold it too close to the reader it will fail. I hold it around an inch above the reader.
Sent from my SCH-I605 using xda app-developers app
You sir are a ****ing life saver! I've been trying to get this to work for over a month since I lost it and this has been the only way it has worked. Awesome. Thanks!
techgov8 said:
You sir are a ****ing life saver! I've been trying to get this to work for over a month since I lost it and this has been the only way it has worked. Awesome. Thanks!
Click to expand...
Click to collapse
Glad to see it worked for you. I love Google Wallet so I know how you feel
Sent from my SGH-T889 using xda premium
Getting device setup failed.
Sent from my Galaxy Nexus using xda app-developers app
Followed the instructions and works flawlessly. Thanks for the work.
Sent from my SCH-I605 using xda premium
thejron said:
Getting device setup failed.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You flashed the correct libs right. Also after you install the xposed apk, you have to open xposed inside the app as well and hit install, ensure the Google Wallet module is enabled then restart the phone and try again. I have a trouble shooting section since this also happened to me
Sent from my SGH-T889 using xda premium
killerapl said:
I've noticed if I hold it too close to the reader it will fail. I hold it around an inch above the reader.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Hmmm..I tried using it on babyrus and it asked me to enter pin and tapped again but failed. I will try your method this week
Sent from Verizon Note II
saint365 said:
Hmmm..I tried using it on babyrus and it asked me to enter pin and tapped again but failed. I will try your method this week
Sent from Verizon Note II
Click to expand...
Click to collapse
Okay, well during set up of wallet it should ask you to set up a pin. You enter it 2x, one to set and one to confirm. I open wallet before I purchase because it asks for my pin. There used to be a flashable zip for screen off. Let me know if this method works for you.
Sent from my SGH-T889 using xda premium
DISCLAIMER: I'M NOT RESPONSIBLE IF YOU DAMAGE YOUR DEVICE OR DELETE YOUR DATA...BE SURE TO BACKUP BEFORE YOU BEGIN AS ALWAYS!
Well...without further wait i present to u the multi window mod for the I717! First & foremost...i would like to give ALL thanks to the multiwindow master himself @xperiacle because without his work none off these mods would even be possible. Second...please keep in mind that i do NOT actually own an I717 so my help may be limited but i must say that u guys have some of the most dedicated users i have ever seen so i'm sure they will be more than willing to be of assistance in case in any issues may arise. This will be provided in 2 versions one for MD1 & another for MD3 so be sure to download the proper package for your firmware...be aware that this mod will most likely remove certain features from cutom roms so if u cant do without them then u may need to wait until your favorite chef cooks up a version which includes multiwndow
YOU MUST BE USING A 4.1.2 DEODEXED TOUCHWIZED BASED ROOTED ROM TO INSTALL THIS MOD!
INSTALL INSTRUCTIONS
1. Install busybox if not already present on your device
2. Download an alternative launcher (i personally use apex)
3. Open your build prop and find the line "qemu.hw.mainkeys=1" and change it to "qemu.hw.mainkeys=0" then save and reboot (this is what adds the onscreen buttons/bottom bar...MUST be done for phablet/tablet mode to work)).
4. Flash the version which matches your firmware (check "settings/about device/build number" & grab the zip that matches the last 3 digits)
5. Install the xposed framework as well as the app settings module (links below) then set "com.sec.android.app.flashbarservice" to 320 dpi then save & reboot (the edit button will not appear in other dpi settings without performing this step)
6. Open the "FLOATING MW CONTROL" and choose your desired setup
7. If u would like to add extra apps to the multiwindow launcher then download the "MULTIWINDOW APPS MANAGER" xposed module from the link below...u MUST reboot after enabling apps then open the bar, press the "edit" button at the bottom and u should see the list of available apps which need to be dragged over to the tray then press done when finished
KNOWN ISSUES
1. Padawan V4 users MUST install the zip IMMEDIATELY after flashing the rom WITHOUT rebooting to prevent sytemui force closes (alternatively if u do not want to reinstall your rom u can try wiping BOTH caches before/after flashing the mod although this may not help)
2. The icon next to the "edit" button located in the bottom bar when in phablet/tablet mode will cause will cause a force close so do not press it (it was implemented as an expanded desktop switch for N7000 but doesnt function on the I717)
As mentioned in step 6...this mod includes an app called "FLOATING MW CONTROL" (created by & used with the permission of @xperiacle) which not only does as the name suggests but even more, although users should be aware that it was not created specifically with the I717 in mind (it was designed to be used with the international N7000 instead) so there may be options which do not function properly. With that said...this app will allow u to switch from phone to tablet ui as well as from side/flashbar multiwindow mode to the bottom/traybar style and also allow u to hide the navbar as well. There is no proper documentation for the app itself although u will find that it is very intuitive and will not only tell u what step to take next to get the desire results but will also inform why u are not allowed to perform certain actions....well i hope u all enjoy your device a lil more now that it has this useful feature which samsung should have included in the first place
View attachment I717MD1MultiWindowModV1.zip
^MD1 V1
https://drive.google.com/file/d/0B7yxeu9x48ILSlBOcmExbXlLME0/edit?usp=sharing
^MD3 V1
http://forum.xda-developers.com/showthread.php?t=1574401
^XPOSED FRAMEWORK THREAD
http://forum.xda-developers.com/showthread.php?t=2437377
^APP SETTINGS MODULE THREAD
http://forum.xda-developers.com/showthread.php?p=42078224
^MULTIWINDOW APPS MANAGER MODULE THREAD
credit/thanks to: ALL testers who helped get this thing going for u guys but i would like to extend special assistance attention to @scariola as well as @_INSPIREed for going above and beyond to work out the glitches as well as help their fellow I717 owners @xperiacle for the systemui, floating mw control app, & multiwindow apps manager module @rovo89 for xposed & @Tungstwenty for the app settings module
attention all devs: consider this my express permission (although i STRONGLY suggest getting separate permission from @xperiacle before using the included app which is entirely his work) to use this mod in building your roms with proper credit of course BUT i only ask that u actually bake it into the rom itself instead of providing an add-on zip (in that case just link your users back here) which may cause confusion and unnecessary/improperly placed posts...thx
screenshots
here u guys go...a few photos showing the different ui modes and multiwindow styles
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great work @THEDEVIOUS1
Much appreciated
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Damn...I limited to 8 thanks.
Thanks. Wonderful job
@THEDEVIOUS1 once again bro thanks for all your work. Been good testing your work, you truly have been an amazing help for this device. And don't worry the thread will run itself. We have a bunch of people who will pitch in when needed, and when in doubt, I think I speak for myself, and @scariola saying I have no problem pitching in like always. I know you have some other devices to attend to . Good luck on them bro :good::good:
_INSPIREed said:
@THEDEVIOUS1 once again bro thanks for all your work. Been good testing your work, you truly have been an amazing help for this device. And don't worry the thread will run itself. We have a bunch of people who will pitch in when needed, and when in doubt, I think I speak for myself, and @scariola saying I have no problem pitching in like always. I know you have some other devices to attend to . Good luck on them bro :good::good:
Click to expand...
Click to collapse
when u get time could u still check the xposed module with the miniapps traybar/bottom multiwindow launcher to see if it will add apps...i recommended the play store app just to be safe and to be honest i'm curious to find the code for my own device as well
Good work on this.
THEDEVIOUS1 said:
when u get time could u still check the xposed module with the miniapps traybar/bottom multiwindow launcher to see if it will add apps...i recommended the play store app just to be safe and to be honest i'm curious to find the code for my own device as well
Click to expand...
Click to collapse
Multi Window Manager wants to patch a file and asks me which device I am running,
What device do I select when it asks me what device I am using? (Of course I717 is not there,)
The xposed module works for me, although there are apps which won't take to multi-window.
pTeronaut said:
Multi Window Manager wants to patch a file and asks me which device I am running,
What device do I select when it asks me what device I am using? (Of course I717 is not there,)
The xposed module works for me, although there are apps which won't take to multi-window.
Click to expand...
Click to collapse
Ya the N7000 patch works for the i717 on the MWM app
hi just a noob question here... which one i should download MD1 or MD3? i'm using stock 4.1.2 i717D (Telus) rooted
I have downloads the md3 file have everything to work in padawan v4 but keep getting system ui has stopped please help
Sent from my SAMSUNG-SGH-I717 using Tapatalk
bongra80 said:
I have downloads the md3 file have everything to work in padawan v4 but keep getting system ui has stopped please help
Click to expand...
Click to collapse
Did you follow Install Step #3?3. Flash the version which matches your firmware (due to force close issues Padawan V4 users MUST install the zip IMMEDIATELY after flashing the rom WITHOUT rebooting)
As noted in the OP this does break the ROM Customizer options in BlackSTAR BLACKJelly v2. Multiwindow works now though.
Also reporting that the Xposed MW Apps Manager works.
.
in FW app, I go through selections. when I get to Navbar which I want to hide, the multiwindow chooser comes up. stock or floating? I have hit floating twice and phone reboots
I am doing something wrong. attempting to follow.
captemo said:
in FW app, I go through selections. when I get to Navbar which I want to hide, the multiwindow chooser comes up. stock or floating? I have hit floating twice and phone reboots
I am doing something wrong. attempting to follow.
Click to expand...
Click to collapse
I think the original op said to pick stock
frome901 said:
I think the original op said to pick stock
Click to expand...
Click to collapse
reboots on both
LiMITZERO said:
hi just a noob question here... which one i should download MD1 or MD3? i'm using stock 4.1.2 i717D (Telus) rooted
Click to expand...
Click to collapse
Look under Settings/about/ and check your build number.
I do believe it will have MD1 on the end of it. So that would be the MD1 v1 you would use.
captemo said:
reboots on both
Click to expand...
Click to collapse
Does it hide the nav bar? Im still trying to line it out myself, so
frome901 said:
Does it hide the nav bar? Im still trying to line it out myself, so
Click to expand...
Click to collapse
I go through the FW settings one at a time. when I get to the hide the navbar, I hit hide. window then pops up stock or floating. instantly reboots. the navbar never appears. even after reboot.
had to charge phone a bit before playing more.
captemo said:
reboots on both
Click to expand...
Click to collapse
It will reboot on both. What is not happening for you? Touchwiz has no navbar since our phone has capacitance buttons so there is nothing to show or hide. Apex launcher does. That is if this app refers to the onscreen buttons as the navigational bar.
My issue is I can't find the bottom bar no matter what mode or DPI I try. I always get the sidebar.
captemo said:
I go through the FW settings one at a time. when I get to the hide the navbar, I hit hide. window then pops up stock or floating. instantly reboots. the navbar never appears. even after reboot.
had to charge phone a bit before playing more.
Click to expand...
Click to collapse
It reboots so that setting sticks. I have noticed that whenever you change any setting in FW app it will automatically reboot to stick changes
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We're back, boys!
This time with with Oreo 8.1.0 atvXperience v3 for S905X2 and specifically A95X Max!
THE FIRST EVER CUSTOM ROM FOR A95X MAX!!
• Android OS version: 8.1.0
• For devices: A95X MAX
• Recovery: AOSP
Those who don't have it, you can buy from this link. Probably the most popular S905X2 TV box with HDD and SSD Support and really fast and stable!
https://www.gearbest.com/tv-box/pp_009379639442.html?wid=1433363&lkid=39289238
Attention:
I don't force you to use the ROM. It's stable and can be used as daily driver except for a few things.
If you don't like something, please ask me on how to remove/add it.
atvXperience and nobody from the team nor the forum moderators are responsible for bricked devices. But we always try to help as much as we can
Click to expand...
Click to collapse
Based on AndroidTV OS. Has all the features of an AndroidTV but since atvXperienceOS provides a different experience, we combine the best of AOSP and ATV.
Credit: SrWladimir
* Nayam Amarshe
* Carmine Rovito
* Taylor Stephen Hadden
* Vadim Mussin
v3A
NOTE
The first boot will take a lot of time! Screen will be glitchy, bootvideo will be laggy and you may not even see anything except for black screen but this is normal and doesn't affect the device in any way. This only happens on the first boot because the encrypted kernel and bootloader try to reject the device but it boots anyway and everything will be OK in the second boot.
v3A
• Based on latest AndroidTV OS, latest Security patches.
• Google Play Works
• All Google Apps Work!
• Recommendations work great! To turn off go to Settings - Home
• Casting Works with Airscreen
• Fully Compatible with A95X Max!
• atvXed up with Multiple USB drivers!
v3B To-Do:
Add USB drivers
Add Navbar and Status Bar
Change Settings shortcut to TVSettings
Change App Drawer Wallpaper
Add some more preinstall apps
DO THE ATVX THING
PLEASE WATCH THE YOUTUBE VIDEO:
https://m.youtube.com/watch?feature=youtu.be&v=hnliXmly7WY
Please consider donating if you like our work
PAYPAL LINK
or
PAYPAL EMAIL
[email protected]
Known Problems:
None my boi
Credits:
Fabio Ciani
Ricky Divjakovski
Superceleron
eric
A95X Max developers
XDA-Developers Members
forumXperience members
My team
atvXperience followers
and the one reading this
Special Thanks to my boi Nitin for making this when I was busy
Rom is *meh*, as it completely throws away the stock android Oreo layout and switches to a straight up TV Box setup like a Roku. Most apk's refuse to work with this setup. The included Youtube app sucks and needs to be REMOVED FROM THE ROM as a system app or at least replaced with YT Vanced. Also, Chrome is simply gone...and you cant find it in the "store" either. The apk can be manually installed with a USB/SD card. Netflix app installed within the store does not work with this rom so its like what are we doing here?... but there is a work around. There is no option to boot straight to recovery either, if there even is one. We need TWRP for this to let us do what we want...Get rid of the Android TV BS and let people install their own launcher and you will profit more than just re-skinning the stock OS with this.
Then don't use it... I use it because of the Android TV layout. He was very up front in the beginning as to what this was and what would and would not work. No 3rd party box is going to work with Netflix or Amazon Apps at this time due to widevine DRM.
If what you have described is what you want, then by all means make your own ROM.
Rumsfield said:
Rom is *meh*, as it completely throws away the stock android Oreo layout and switches to a straight up TV Box setup like a Roku. Most apk's refuse to work with this setup. The included Youtube app sucks and needs to be REMOVED FROM THE ROM as a system app or at least replaced with YT Vanced. Also, Chrome is simply gone...and you cant find it in the "store" either. The apk can be manually installed with a USB/SD card. Netflix app installed within the store does not work with this rom so its like what are we doing here?... but there is a work around. There is no option to boot straight to recovery either, if there even is one. We need TWRP for this to let us do what we want...Get rid of the Android TV BS and let people install their own launcher and you will profit more than just re-skinning the stock OS with this.
Click to expand...
Click to collapse
Parsival1973 said:
Then don't use it... I use it because of the Android TV layout. He was very up front in the beginning as to what this was and what would and would not work. No 3rd party box is going to work with Netflix or Amazon Apps at this time due to widevine DRM.
If what you have described is what you want, then by all means make your own ROM.
Click to expand...
Click to collapse
I'll get right on it.
Rumsfield said:
Rom is *meh*, as it completely throws away the stock android Oreo layout and switches to a straight up TV Box setup like a Roku. Most apk's refuse to work with this setup. The included Youtube app sucks and needs to be REMOVED FROM THE ROM as a system app or at least replaced with YT Vanced. Also, Chrome is simply gone...and you cant find it in the "store" either. The apk can be manually installed with a USB/SD card. Netflix app installed within the store does not work with this rom so its like what are we doing here?... but there is a work around. There is no option to boot straight to recovery either, if there even is one. We need TWRP for this to let us do what we want...Get rid of the Android TV BS and let people install their own launcher and you will profit more than just re-skinning the stock OS with this.
Click to expand...
Click to collapse
Read the title again maybe?
This is an AndroidTV OS and no it's not BS. Maybe it's only you who likes to use a mouse and keyboard on a tv. This is meant for those who don't want the airmouse BS and want a clean look, to have the real AndroidTV Box and not just a phone-UI Android Box and not the *meh* launchers that are meant for phone screens.
All apks work, if it works in the phone rom, it works in ATV. 'Maybe' you're doing something wrong or lack the knowledge of apps installation.
The google play store is meant for AndroidTV, it shows apps which are compatible with your remote, not mouse or keyboard.
Also, Netflix thing, everybody knows you need a Netflix certified box for it, it's even mentioned on their website.
And everybody knows you can use Aptoide Store for other apps that aren't on play store.
If you want your own launcher, go ahead make a ROM but please don't call my work a 'simple reskin' because I am working my ass off for a box that's totally encrypted to the core and has a 'meh' phone UI.
So, please don't think I'm playing copy and paste here, I've worked hard on this and if my work is *meh*, please use another ROM (if it exists).
Thank you for the feedback on v3A
Sent from my Spaceship using Tapatalk
Links Updated!
Please don't forget to watch the tutorial video first.
Thank you for the support.
Sent from my F3116 using Tapatalk
Good... Then you can ***** and complain to yourself rather than crap on someone elses hard work.
Rumsfield said:
I'll get right on it.
Click to expand...
Click to collapse
Parsival1973 said:
Good... Then you can ***** and complain to yourself rather than crap on someone elses hard work.
Click to expand...
Click to collapse
Did I ***** and complain? I simply stated some of this rom's caveats and giving a heads up to people who might prospectively install this not realizing its going to completely change the OS to a dedicated Kodi box.
No browser at all? Youtube that you cant get rid of? If you dont like my opinion you can straight up not listen to it. I doubt you even installed it in the first place or you wouldn't be responding with your sh*t posts.
Rumsfield said:
Did I ***** and complain? I simply stated some of this rom's caveats and giving a heads up to people who might prospectively install this not realizing its going to completely change the OS to a dedicated Kodi box.
No browser at all? Youtube that you cant get rid of? If you dont like my opinion you can straight up not listen to it. I doubt you even installed it in the first place or you wouldn't be responding with your sh*t posts.
Click to expand...
Click to collapse
You can install Puffin Browser from Google Play. It's the best TV Browser out there, 100% remote compatibility.
It's pre-rooted, you can easily uninstall YouTube if you know what root means. AptoideTV Store is there to help.
I thought I included webXperience, It's our own browser. If I didn't, I'll do it in the next release which is going to shut everybody up because as I mentioned, this is the first release and the next will be address all the issues you mentioned and the features that I mentioned.
If you want a phone rom on a tv box, please go elsewhere because this is an AndroidTV thread, please don't argue here, the mods take notice of everything.
Thank you for understanding.
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
You can install Puffin Browser from Google Play. It's the best TV Browser out there, 100% remote compatibility.
It's pre-rooted, you can easily uninstall YouTube if you know what root means. AptoideTV Store is there to help.
I thought I included webXperience, It's our own browser. If I didn't, I'll do it in the next release which is going to shut everybody up because as I mentioned, this is the first release and the next will be address all the issues you mentioned and the features that I mentioned.
If you want a phone rom on a tv box, please go elsewhere because this is an AndroidTV thread, please don't argue here, the mods take notice of everything.
Thank you for understanding.
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
I am familiar with rooting aka administrative privileges over apps/os and have had many phones/tablets/matricom boxes all eventually rooted with either magisk or super su, some I actually paid for. This rom doesnt allow me to uninstall anything, just disable which is not the same. How can I grant root access to any app, such as bloatware removal tools? There is no root management on this thing. (that I am aware of?) and there is no recovery I can see to get into to flash anything besides the temp TWRP method with an sd card + paper clip which has not worked with anything on this rom.
Rumsfield said:
I am familiar with rooting aka administrative privileges over apps/os and have had many phones/tablets/matricom boxes all eventually rooted with either magisk or super su, some I actually paid for. This rom doesnt allow me to uninstall anything, just disable which is not the same. How can I grant root access to any app, such as bloatware removal tools? There is no root management on this thing. (that I am aware of?) and there is no recovery I can see to get into to flash anything besides the temp TWRP method with an sd card + paper clip which has not worked with anything on this rom.
Click to expand...
Click to collapse
Try switching on the root switch from settings and reboot.
Another tip, install SuperSU 2.79 and it will fix your root management issues.
The recovery is stock, just like the original ROM. Use quick reboot app to reboot to recovery.
If it still doesn't work, I'll double check and fix anything if wrong. As I said, this is the first release so expect issues unless you know how to fix things but don't worry, the v2B or v2F (whatever I name it) is going to fix all the issues. Trust me, you'll never feel the need to use Navbar and Statusbar again with the new build.
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
Try switching on the root switch from settings and reboot.
Another tip, install SuperSU 2.79 and it will fix your root management issues.
The recovery is stock, just like the original ROM. Use quick reboot app to reboot to recovery.
If it still doesn't work, I'll double check and fix anything if wrong. As I said, this is the first release so expect issues unless you know how to fix things but don't worry, the v2B or v2F (whatever I name it) is going to fix all the issues. Trust me, you'll never feel the need to use Navbar and Statusbar again with the new build.
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
Switching off/on root switch doesn't do anything even with restarting.
SuperSu 2.79 does not successfully flash in temp TWRP with paperclip method or with stock recovery (see pic).
Since there is no root management, quick reboot and other root required apps install but dont work.
Ad-Away also will not save host files either, and I prefer to use that in combination with chrome over Puffin.
If I pissed you off with my earlier post, I apologize and that was not my intent. I understand this rom is pretty much in beta at this point but its very frustrating when nothing works for me, pretty much at all except for what worked with the stock OS.
FYI I have the v81 board.
Rumsfield said:
Switching off/on root switch doesn't do anything even with restarting.
SuperSu 2.79 does not successfully flash in temp TWRP with paperclip method or with stock recovery (see pic).
Since there is no root management, quick reboot and other root required apps install but dont work.
Ad-Away also will not save host files either, and I prefer to use that in combination with chrome over Puffin.
If I pissed you off with my earlier post, I apologize and that was not my intent. I understand this rom is pretty much in beta at this point but its very frustrating when nothing works for me, pretty much at all except for what worked with the stock OS.
FYI I have the v81 board.
Click to expand...
Click to collapse
You are not supposed to flash super su. Just install it.
See here:
https://forum.atvxperience.com/viewtopic.php?f=16&t=814
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
You are not supposed to flash super su. Just install it.
See here:
https://forum.atvxperience.com/viewtopic.php?f=16&t=814
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
It doesn't matter, it doesn't install either way (flashing vs apk).
All I can think of is to completely re-flash the new link firmware over my version I installed when you made it first available, maybe there is a difference?
Rumsfield said:
It doesn't matter, it doesn't install either way (flashing vs apk).
All I can think of is to completely re-flash the new link firmware over my version I installed when you made it first available, maybe there is a difference?
Click to expand...
Click to collapse
Thanks for letting me know, it's strange it's not working for you. My friend reported it working. I'll fix the su in the new version. Meanwhile, you can flash stock rom because I don't want you to get any issues.
New build will be ready in a week or so and it's going to be great!
Thanks for all the feedback.
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
Thanks for letting me know, it's strange it's not working for you. My friend reported it working. I'll fix the su in the new version. Meanwhile, you can flash stock rom because I don't want you to get any issues.
New build will be ready in a week or so and it's going to be great!
Thanks for all the feedback.
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
Thats fine, so now we know why I was a bit brash in my original post.
It still needs a bit of polish. Thanks for you work.
Rumsfield said:
Thats fine, so now we know why I was a bit brash in my original post.
It still needs a bit of polish. Thanks for you work.
Click to expand...
Click to collapse
If you watch this video, you can see that Nicholas tested that the ROM is rooted. That's why I said, I don't know why it's not working for you.
https://youtu.be/hnliXmly7WY
Maybe you can try switching root switch off, reboot, then on and reboot.
I'll update the su anyway, nobody should be getting any problems but this box is one hell of a fighter. They've encrypted everything! I could only get access to system because kernel, recovery and everything else was encrypted.
Sent from my Spaceship using Tapatalk
N'ayam Amarsh'e said:
If you watch this video, you can see that Nicholas tested that the ROM is rooted. That's why I said, I don't know why it's not working for you.
https://youtu.be/hnliXmly7WY
Maybe you can try switching root switch off, reboot, then on and reboot.
I'll update the su anyway, nobody should be getting any problems but this box is one hell of a fighter. They've encrypted everything! I could only get access to system because kernel, recovery and everything else was encrypted.
Sent from my Spaceship using Tapatalk
Click to expand...
Click to collapse
Re-flashing the newer firmware link over last weeks firmware link allowed SuperSu apk to install successfully. Apparently we are good to go now...
Rumsfield said:
Re-flashing the newer firmware link over last weeks firmware link allowed SuperSu apk to install successfully. Apparently we are good to go now...
Click to expand...
Click to collapse
Sweet!
Do lookout for new version as it will include these features:
1. Replace settings shortcut with TV Settings
2. Include pre-install apps like Web browser, Netflix and other apps.
3. Double tap home button for Recent Apps and use arrow keys to clear the apps.
4. Hold Power button for quick shutdown.
5. Add Init.d tweaks for more performance.
6. Add Back-Panic Button.
7. Hold Back button for assistant.
8. Add Navbar and Status bar functionality (if possible)
9. Add Gamepad drivers
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
Sweet!
Do lookout for new version as it will include these features:
1. Replace settings shortcut with TV Settings
2. Include pre-install apps like Web browser, Netflix and other apps.
3. Double tap home button for Recent Apps and use arrow keys to clear the apps.
4. Hold Power button for quick shutdown.
5. Add Init.d tweaks for more performance.
6. Add Back-Panic Button.
7. Hold Back button for assistant.
8. Add Navbar and Status bar functionality (if possible)
9. Add Gamepad drivers
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
I spoke too soon lol. SuperSu 2.79 installs after a fresh firmware flash but bootloops (waiting 20 minutes and still stuck on logo screen). Re-flashing and installing SuperSu 2.82 does the same thing. Oh well.
Re-flashing the image brings its back but just beware root doesnt work. I give up, good luck to everyone getting root.