hiddenramblings / tagmo Goto Github PK
View Code? Open in Web Editor NEWLicense: GNU General Public License v3.0
License: GNU General Public License v3.0
So I load my data and everything, then when I write tag auto, and place my nfc tag, I hear one noise and then nothing... and literally nothing happens no matter how long I wait, Please help!!
I have an LG Escape 3. It is a Cricket(Carrier) phone. When I download the tagmo onto my phone, it says that it is not NFC supported. What is strange is that my phone is NFC supported, and I even searched up on the internet to find out if it is. I also can't find any NFC settings inside the phone settings. Is there a glitch, a defect, or my phone actually doesn't have NFC?
When ever you tap "WRITE TAG (AUTO)" after selecting your Amiibo bin the App Crashes this Bug is on "2.3.4 Pre-Release" and "2.3.3" but the App works just fine with "2.3.2" my Android Version is 6.0.1 Stock Please Fix this Bug :(
As title, when I click WRITE or READ tag app crashes.
crashes every time i tap edit ssb Data
Galaxy S5, Android 5.0
When I click scan tag the app quits responding and crashes.
I have tried this version and also azsde's forked version and I have the same issue.
The error I am getting is here: http://pastebin.com/VL4LEzqL
Nfc turned on
Tagmo 2.3.4 installed
I can upload both keys and tag
Error message saying NFC not supported on right side beneath 3 white dots.
I have a suggestion that may be helpful if one obtains their NFC BINs from a source that's not their own amiibo ๐
The idea is to put Amiibo in a QR code one can scan and thus eliminate the need of waiting for those sites todo their 10esc countdown :3
I can scan and load just fine, but if I try to scan an amiibo and view hex or edit ssb data, the app crashes. I haven't tried to write tags yet. Android 6.0.1, Samsung Galaxy S5 (G900V).
I have a Sony Z3 compact purchased from Japan. None of the version reads ntag215.
Is this a hardware issue or software one?
Not sure if pre-releases are eligible for issue posting, and this is part issue / part feedback, anyway. Apologies in advance if this is not the right place.
Phone: Galaxy S4 mini with stock UI
Tagmo version 2.4.0
I previously installed 2.3.1 and non other until 2.4.0. I used to test the tags I wrote by scanning the tag and see if the name came up correctly on 2.3.1. On 2.4.0 this function doesn't work for me, just a heads up.
Galaxy S4 (tested with 2.3.2, 2.3.4beta and @azsde branch)
here is the log:
03-10 15:37:55.266: I/Timeline(17256): Timeline: Activity_launch_request id:com.hiddenramblings.tagmo time:1641079
03-10 15:37:55.366: E/PathParser(17256): error in parsing "c0 1.1.9 2 2 2"
03-10 15:37:55.366: D/AndroidRuntime(17256): Shutting down VM
03-10 15:37:55.376: E/AndroidRuntime(17256): FATAL EXCEPTION: main
03-10 15:37:55.376: E/AndroidRuntime(17256): Process: com.hiddenramblings.tagmo, PID: 17256
03-10 15:37:55.376: E/AndroidRuntime(17256): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.hiddenramblings.tagmo/com.hiddenramblings.tagmo.NfcActivity_}: android.view.InflateException: Binary XML file line #31: Error inflating class ImageView
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2702)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2767)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.app.ActivityThread.access$900(ActivityThread.java:177)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1449)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.os.Handler.dispatchMessage(Handler.java:102)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.os.Looper.loop(Looper.java:145)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.app.ActivityThread.main(ActivityThread.java:5951)
03-10 15:37:55.376: E/AndroidRuntime(17256): at java.lang.reflect.Method.invoke(Native Method)
03-10 15:37:55.376: E/AndroidRuntime(17256): at java.lang.reflect.Method.invoke(Method.java:372)
03-10 15:37:55.376: E/AndroidRuntime(17256): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1400)
03-10 15:37:55.376: E/AndroidRuntime(17256): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1195)
03-10 15:37:55.376: E/AndroidRuntime(17256): Caused by: android.view.InflateException: Binary XML file line #31: Error inflating class ImageView
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:770)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.view.LayoutInflater.rInflate(LayoutInflater.java:813)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.view.LayoutInflater.inflate(LayoutInflater.java:511)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.view.LayoutInflater.inflate(LayoutInflater.java:415)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.view.LayoutInflater.inflate(LayoutInflater.java:366)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.support.v7.app.AppCompatDelegateImplV7.setContentView(AppCompatDelegateImplV7.java:256)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.support.v7.app.AppCompatActivity.setContentView(AppCompatActivity.java:109)
03-10 15:37:55.376: E/AndroidRuntime(17256): at com.hiddenramblings.tagmo.NfcActivity_.setContentView(NfcActivity_.java:51)
03-10 15:37:55.376: E/AndroidRuntime(17256): at com.hiddenramblings.tagmo.NfcActivity_.onCreate(NfcActivity_.java:42)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.app.Activity.performCreate(Activity.java:6289)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2655)
03-10 15:37:55.376: E/AndroidRuntime(17256): ... 10 more
03-10 15:37:55.376: E/AndroidRuntime(17256): Caused by: android.content.res.Resources$NotFoundException: File res/drawable-anydpi-v21/nfc_circle.xml from drawable resource ID #0x7f020047
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.content.res.Resources.loadDrawableForCookie(Resources.java:3735)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.content.res.Resources.loadDrawable(Resources.java:3603)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.content.res.TypedArray.getDrawable(TypedArray.java:762)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.widget.ImageView.<init>(ImageView.java:151)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.widget.ImageView.<init>(ImageView.java:140)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.support.v7.widget.AppCompatImageView.<init>(AppCompatImageView.java:58)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.support.v7.widget.AppCompatImageView.<init>(AppCompatImageView.java:54)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.support.v7.app.AppCompatViewInflater.createView(AppCompatViewInflater.java:95)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.support.v7.app.AppCompatDelegateImplV7.createView(AppCompatDelegateImplV7.java:938)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.support.v7.app.AppCompatDelegateImplV7.onCreateView(AppCompatDelegateImplV7.java:992)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.support.v4.view.LayoutInflaterCompatHC$FactoryWrapperHC.onCreateView(LayoutInflaterCompatHC.java:44)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:732)
03-10 15:37:55.376: E/AndroidRuntime(17256): ... 21 more
03-10 15:37:55.376: E/AndroidRuntime(17256): Caused by: java.lang.NumberFormatException: Invalid float: "1.1.9"
03-10 15:37:55.376: E/AndroidRuntime(17256): at java.lang.StringToReal.invalidReal(StringToReal.java:63)
03-10 15:37:55.376: E/AndroidRuntime(17256): at java.lang.StringToReal.initialParse(StringToReal.java:160)
03-10 15:37:55.376: E/AndroidRuntime(17256): at java.lang.StringToReal.parseFloat(StringToReal.java:323)
03-10 15:37:55.376: E/AndroidRuntime(17256): at java.lang.Float.parseFloat(Float.java:306)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.util.PathParser.getFloats(PathParser.java:178)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.util.PathParser.createNodesFromPathData(PathParser.java:59)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.graphics.drawable.VectorDrawable$VFullPath.updateStateFromTypedArray(VectorDrawable.java:1439)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.graphics.drawable.VectorDrawable$VFullPath.inflate(VectorDrawable.java:1421)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.graphics.drawable.VectorDrawable.inflateInternal(VectorDrawable.java:542)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.graphics.drawable.VectorDrawable.inflate(VectorDrawable.java:458)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.graphics.drawable.Drawable.createFromXmlInner(Drawable.java:1150)
03-10 15:37:55.376: E/AndroidRuntime(17256): at android.graphics.drawable.Drawable.createFromXml(D
03-10 15:37:58.829: I/Process(17256): Sending signal. PID: 17256 SIG: 9
Galaxy Note 3, Android 5.
Like the title says, I tested every release of this git and it always crashes when I try to write. Even 2.32, which seem to work for some people, crashes. Can anyone help?
Im trying to make an ocarino of time link tag and every .bin file I load into tagmo says TagId: Mario (UNKN) than the numbers. Will this be a problem or when I write this .bin file to the tag itll be the correct one?
On an Axon 7 with NFC enabled. I can get up to the point where I write the tag but when I do it, it just says "done" before I do anything.
When I tap "Write Tag", it says "Done" at the bottom of the screen before I scan my NFC tag. When I do scan it, it just sends me back to the main screen, leaving the NFC tag empty. I have tried the beta, the current version and the 2 versions before that.
Ive tried every build of Tagmo and still havent been able to get past the error message it says done before the scan starts and gives an error message when it tries to write
I have a Samsung Galaxy Victory which has a 800x480 screen. The menu button does not show up and cannot load keys.
Trying on my nephews Samsung mega. Keys load. Bin loads. When I hit write auto it says to lay the phone on the tag. And that's as far as I get. Thought it was just his phone. Tried on my sisters note 3. And exact same issue. I've tried 2.3.2 and 2.3.3. Any ideas?
I have a wiiu, TP HD and anot amiibo, I read another thread that lined towards nfc cards and I really just want to modify this one slightly, I've heard there's a specific version of tagmo for wolf link edits, could anyone link me to that or something?
Been trying to get this working for a couple hours.
PS. Amiibo has been to the shadow cave already.
Any news regarding this? I am unable to find a retailer of NTAG215 in my country :(
Hello! I have a HTC One Remix with NFC running android 4.4.2 and when I load TagMo with NFC enabled/on and fully functional. As soon as any version of TagMo gets installed, NFC now cycles on and off and I cannot use it nor turn it off unless I do a factory reset. Then NFC returns to normal. I have installed now every version of TagMo on the site. Cycles between "scanning tag" and "NFC Not Enabled!" back and forth. Any thoughts?
Just tried this app (4 versions of it) and can not get it to write to a tag. As soon as I hit the "Write to tag (auto)" button it says "Done" before I even place a tag up to it. I tried placing a tag on it anyway and testing it in Zelda and got nothing. I'm using a Nexus 6 on Android 7.
Is there any way to update stats of an already programmed NFC chip or real amiibo? If not is this a planned future addition? Thanks.
TagMo 2.3.3 just crashes on my phone (Nexus 5X, Android 7.1.1) when I try to write a tag or view hex. However, the patched APK described in this post worked great. I don't have any further insight, but figured it was worth reporting here.
I have a Samsung Galaxy 5
Android version 6.0.1
It will not write to the g215 i bought.
Running Android 6.0.1 and the latest full release, every time I hit the Edit SSB Info button, it crashes. Anyone know why? (Or if it's known and being fixed, I didn't see it among the issues, but I may just be blind)
Was running TagMo 2.3.2 fine on older Android OS (I think it was version 6.1). Then upgraded phone to Android 7.0. TagMo stopped working. Tried a bunch of other versions of TagMo (up to 2.4.1) but they all just can't read/write. None of the versions crash, it just seems TagMo cannot "see" the NFC tags now. OS NFC setting is (still) enabled.
I download the app but the install button cannot be pressed. I'm running 5.5.1 on a Note 4.
Hi
I try to write an amiibo but the app crash, i have a Samsung Galaxy note 3. The version 2.3.2 worked with other amiibo (Super Mario SSB) but i try now and dont work nothing, when i load or scan tag all time load the Super Mario amiibo or app crash. I install 2.3.4 but i dont have the keys, Please i need help and i dont have the new keys for 2.3.4.
Could the app be ported to WP/UWP?, the alternatives for tagmo on a windows device aren't very versatile, that way it could possibly be compiled for use on a desktop pc or a windows 10 mobile.
It seems that something changed with the most recent builds (2.3.4 and 2.3.3) that isn't including the native libs in the apk. When I try to write a tag I end up with the following stacktrace:
E/AndroidRuntime( 2082): FATAL EXCEPTION: main
E/AndroidRuntime( 2082): Process: com.hiddenramblings.tagmo, PID: 2082
E/AndroidRuntime( 2082): java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.hiddenramblings.tagmo-1/base.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]] couldn't find "libamiitool.so"
E/AndroidRuntime( 2082): at java.lang.Runtime.loadLibrary(Runtime.java:366)
E/AndroidRuntime( 2082): at java.lang.System.loadLibrary(System.java:988)
E/AndroidRuntime( 2082): at com.hiddenramblings.tagmo.AmiiTool.<clinit>(AmiiTool.java:8)
E/AndroidRuntime( 2082): at com.hiddenramblings.tagmo.TagUtil.decrypt(TagUtil.java:93)
E/AndroidRuntime( 2082): at com.hiddenramblings.tagmo.EditorSSB.afterViews(EditorSSB.java:82)
E/AndroidRuntime( 2082): at com.hiddenramblings.tagmo.EditorSSB_.onViewChanged(EditorSSB_.java:96)
E/AndroidRuntime( 2082): at org.androidannotations.api.view.OnViewChangedNotifier.notifyViewChanged(OnViewChangedNotifier.java:41)
E/AndroidRuntime( 2082): at com.hiddenramblings.tagmo.EditorSSB_.setContentView(EditorSSB_.java:52)
E/AndroidRuntime( 2082): at com.hiddenramblings.tagmo.EditorSSB_.onCreate(EditorSSB_.java:42)
E/AndroidRuntime( 2082): at android.app.Activity.performCreate(Activity.java:5990)
E/AndroidRuntime( 2082): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1106)
E/AndroidRuntime( 2082): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2278)
E/AndroidRuntime( 2082): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2387)
E/AndroidRuntime( 2082): at android.app.ActivityThread.access$800(ActivityThread.java:151)
E/AndroidRuntime( 2082): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
E/AndroidRuntime( 2082): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 2082): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 2082): at android.app.ActivityThread.main(ActivityThread.java:5254)
E/AndroidRuntime( 2082): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 2082): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 2082): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
E/AndroidRuntime( 2082): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Looking at these APKs in the AS analyzer shows that the native libs are missing:
Compare this with version 2.3.2 which does not crash when writing a tag:
I am getting an error saying tag was lost, any idea on what I am doing wrong?
I am trying to run TagMo on a Samsung Galaxy S III running Android 4.3, and although it starts I can not access a menu as the menu button (I suppose 3 vertical dots in the upper right corner) are not shown at all.
Is there a remedy for this?
After trying to write a bin file onto a tag the app crashes. Another app displays that there weren't any bytes written.
I got a few NTAG215s and their site shows I should be able to overwrite the tags multiple times. But after writing an amiibo to one, it becomes write locked. I can't format the tags even with other apps, they all say it is now write protected.
I'd like to request investigation into the support of Datel's rewritable NFC PowerTags. This would circumvent the need for single-use tags, and support from this app would also circumvent Datel's proprietary PowerSaves USB NFC writer and software. A single tag is bundled with new packages of the PowerSaves writer, or separately in 3 and 10 packs here:
http://www.ebay.com/itm/252829545695
http://www.ebay.com/itm/252828341082
The tags seem to arrive blank, all FF bytes. I attempted to write SSB Mario to one, and data is written to the tag, but it is not valid in-game. Notably bytes 01D5-01DB remain FF after the tag has been written to.
I have a Samsung Galaxy S3 neo with android 4.4.2. I tried all the Tagmo versions there are. But non of them work. The latest version won't open the amiibo bin files correctly. Instead of giving the name of the file at TagId , with every file I try it'll say TagId : 2F7868746D6C312F/3C214443545950 ...As a result , whenever I click WRITE TAG (AUTO) it won't transfer the file to the ntag215. It will say done before you hold the tag against your phone. Any way I can fix this?
Just got my NTAG215 tag in the mail today and i was really exited to write some amiibos to it but so far i havent been able to write using any version of TagMo (from 2.3.0-2.3.4) or any amiibo file. When i attempt to use write(auto) on the newer versions of TagMo the app just crashed and when i use the older versions like people have advised i get a javascript error "Error while writing main data".
Any help would greatly appreciated thank you.
I don't know if this needs a root, or what, but I cannot install any TagMo release on my LG G5.
So I don't know exactly how this works since I don't own the twilight princess HD game but I bought a Wolf Link Amiibo. Apparently, when you use it with the Wii U version of tp you can level him up and he gets hearts and when the new Zelda comes out you can use him in it with his hearts. I don't own a Wii U so it would be nice if he app could edit the Amiibo so at hearts and such. Anyways thanks for the hard work I look forward to using this app.
As the title implies, I'm having issues.
I have "NFC enabled," "Unfixed key OK," "Locked key OK" and a common tag loaded, ready to be written onto brand new ntag215 cards. I'm using a LG G3.
However, when I press "Write Tag (Auto)" and press my card to the phone, I get the error "Unfortunately, Tagmo has stopped" error. I've made sure the app is up to date. Other things that crash the app are "View Hex," and "Edit SSB Data." Although I don't know what it does, I've also tried "Write Tag (Raw)," where I get the message "Source UID does not match the target!" "Scan Tag" and "Save Tag" both work fine. "Restore Tag" crashes.
Also, when I "Scan Tag" the blank cards, it says "Mario SSB" is loaded, however when I scan with amiiqo, it does not say this. Idk what's going on. Is there perhaps something wrong with my keys? When I tap the blank card to my phone without any apps, it confirms it is a blank card.
My phone is currently running android 6. I checked for an update manually but there is none for my phone yet.
Any solutions?
I scanned my Link amiibo, but when I click "WRITE TAG (AUTO)" or "WRITE TAG (RAW)" keeps giving me an error message
when trying to write a Amiibo to NTAG215 it gives the following error:
Error while writing main data (Stage 1)
Java.io.IOException: Transceive failed
running android 7.0 kernel 3.10.61-10958180 at a samsung s6 (model SM-G920F)
Tagmo version 2.3.4 (altered for Samsung)
Using S7Edge android v6.0.1 tried 2.3.3 and 2.3.4 apks.
Anyone else similar or know a fix?
I have a Samsung Galaxy Note 3 with Android 5 and my apk crash when I try to scan or write.
What version of the app do I need? or what do I have to do to make it work? Do I need to have the phone rooted?
I need help ! D:
Tried installing different versions of TagMo and had no luck.
I have an ASUS TF103CE with NFC and even though the NFC feature works and is able to read Amiibos, whenever I press the "scan" button on this app, it force closes. Could it be a problem with tablets, or am I doing something wrong?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.