Related
At my college dorm, we use a certain type of lock in which we put our keys up to the lock, and it unlocks. I figured it used NFC, but I wasn't sure. Then I found this article.
androidauthority/forgot-your-olympic-hotel-room-key-use-your-s3-103325/ (NOTE: As a new user, XDA won't let me post outside URL's. Type in .com after droidauthority for the link to work)
I've got no clue what kind of hardware is in those locks, but I can say that it looks EXACTLY THE SAME as the locks used in my school. For me, that essentially confirmed they use NFC. I don't know who makes those locks, but my school uses the same looking handles and lock mechanism. When the card is held up to the lock, the lock flashes green. If I had to guess, the card acts as an NFC tag. When held up to the door, it will activate my card as any other NFC tag, verify it's me, and then let me in.
Using NFC on my phone, I was wondering if it was possible to do the same! From a logical standpoint (not a dev's standpoint), I would need to somehow steal the info off my card, have it stored in my phone as a usable format for the lock, and then I should be able to just hold the phone up to the lock to have it open!
You guys think this is possible? How would I go about doing it?
sorry that i don't have the answer, but i had this same idea! also wondering if it's possible.
Can.I.Haz.Jelly.Bean? said:
At my college dorm, we use a certain type of lock in which we put our keys up to the lock, and it unlocks. I figured it used NFC, but I wasn't sure. Then I found this article.
androidauthority/forgot-your-olympic-hotel-room-key-use-your-s3-103325/ (NOTE: As a new user, XDA won't let me post outside URL's. Type in .com after droidauthority for the link to work)
I've got no clue what kind of hardware is in those locks, but I can say that it looks EXACTLY THE SAME as the locks used in my school. For me, that essentially confirmed they use NFC. I don't know who makes those locks, but my school uses the same looking handles and lock mechanism. When the card is held up to the lock, the lock flashes green. If I had to guess, the card acts as an NFC tag. When held up to the door, it will activate my card as any other NFC tag, verify it's me, and then let me in.
Using NFC on my phone, I was wondering if it was possible to do the same! From a logical standpoint (not a dev's standpoint), I would need to somehow steal the info off my card, have it stored in my phone as a usable format for the lock, and then I should be able to just hold the phone up to the lock to have it open!
You guys think this is possible? How would I go about doing it?
Click to expand...
Click to collapse
I dont think these use the same frequency. Here in my office we use the HID Prox cards, but its not the same, the easiest way to know if you could do this is get the NFC tag reader software on your phone and try to read the card/key if it will see it I would think you might have a chance, if it doesnt see the card to read it, its not the same and you will not be able to do this.
wiz4769 said:
I dont think these use the same frequency. Here in my office we use the HID Prox cards, but its not the same, the easiest way to know if you could do this is get the NFC tag reader software on your phone and try to read the card/key if it will see it I would think you might have a chance, if it doesnt see the card to read it, its not the same and you will not be able to do this.
Click to expand...
Click to collapse
Lol first thing I tried when reading this thread, but no go, we use the HID Prox cards to. Tried almost every NFC app in the market.
sent from my iPhone killer
from what i've read...
doing what you're suggesting would pose a major security threat to all electronic door locks around the world. you're essentially duplicating your electronic key, which is not unlike duplicating an old school lock/tumbler key. unlike a traditional key however, this is an electronic key which means if you're able to duplicate it, you're also able to send/share it with friends around the world. in other words, we can set up a database of all the dorms / offices locks around the world and we can all have free access. doesn't sound like a pretty picture.
in reality, what our phones are capable of doing is READING the NFC tags. so if anything instead of thinking of your phone as the key, your phone can do the exact same thing as the lock, which is read the info off of the NFC tags. i know we have the ability to WRITE info onto NFC tags as well... but as others have posted there are issues of frequencies and i believe encryption which I HOPE makes this not possible for my security sake.
I'm sure if its physically possible(frequency wise) someone will make it happen. Its just like droid sheep, air crack, wifikill and the likes. Doesn't make it right but throw the technology out there and someone will make use of it.
sent from my iPhone killer using tapatalk 2
I was able to do this with bluetooth and my Samsung Note 3 on Windows7. Got windows 10 and *poof*, it's gone as a bluetooth service. Now I'm scratching my head trying to figure out if that was a function of the BT dongle software, Dell security tools, Windows 7, or what!? A little off topic (not-NFC), but I have the same functional objective.
Hello,
Captivate Glide i927 replaced cracked screen
I replaced the cracked screen assembly and installed a new ribbon. The lower lights (home, search, back button etc) work and also the keyboard lights. The ATT chime sound works too but the display does not light up when powered on.
Connected the phone after replacing ribbon/ screen to the comp for Kies to back up and it is saying the phone is locked. It is the lock code that you set to keep others from accessing. Since the display does not light, the correct code can not be placed in. Can someone please place a picture of the unlock screen mode here? The display touch pad works so if the position of the numbers can be acquired, this may help me to get the phone files accessed and reset hoping to get the display working.
The phone is not rooted and upgraded to the ICS as of October 2012.
Up $86 for the ribbon and new screen and the repair shops want $100 plus the cost of possible parts needed. Would like to try my best so this route can be avoided.
Cheers,
Robert
By now the phone SIM is locked out. I believe there is a way to reboot the phone through a computer?
mer80cedes said:
By now the phone SIM is locked out. I believe there is a way to reboot the phone through a computer?
Click to expand...
Click to collapse
The only way I can think of is rebooting via adb. If you're not rooted (the "reboot" command in shell requires root, i don't know if "adb reboot" wants it), or haven't even turned on USB Debugging at all, then you're doomed.
However, since Odin-ing is not that hard (only requires several key pressing), you could try Odin in a custom recovery (or not, if you already have one), back your system up to external SD in tar or other formats, and then extract the data you want from the backed-up packages (I've done this with tar packages). If you ever need the screenshot of a particular version of recovery, ask again in this thread and I think we'll be more active (and easier) to help.
Sent from Samsung Captivate Glide @ CM10.1.2
AndyYan said:
The only way I can think of is rebooting via adb. If you're not rooted (the "reboot" command in shell requires root, i don't know if "adb reboot" wants it), or haven't even turned on USB Debugging at all, then you're doomed.
However, since Odin-ing is not that hard (only requires several key pressing), you could try Odin in a custom recovery (or not, if you already have one), back your system up to external SD in tar or other formats, and then extract the data you want from the backed-up packages (I've done this with tar packages). If you ever need the screenshot of a particular version of recovery, ask again in this thread and I think we'll be more active (and easier) to help.
Sent from Samsung Captivate Glide @ CM10.1.2
Click to expand...
Click to collapse
Thank you AndYan.
This Captivate has only been upgraded to the Sandwich version. Non-rooted nor modified in any other way. The only reason to remove the files is due to it having solar cell module prototype designs and concepts on it (Reason why it can not be shipped out for professional repairs). Since most of the information was wrote on paper, it's best to just wipe the phone out completely to get it back to working condition for use again.
This is quite interesting learning about programming and such since I have never done this before. Just like building cars, took many many years to do and this programming is just another cool thing to learn about
It takes a special knowledge and experience to understand the programming of Odin and phones which I do not comprehend, I will be destroying the motherboard with a hammer and tossing it out. It is way too much to understand how to set coding and such. Best off investing in another phone and moving on.
The parts that will be saved if anyone can use will be the ribbon strip and also brand new display screen.
Paid $86 for the display and will sell for $75 free shipping with insurance.
Ribbon strip will be $20 free shipping with insurance. If both are wanted $95 free shipping.
Since I do love the Captivate so much another will be purchased.
mer80cedes said:
It takes a special knowledge and experience to understand the programming of Odin and phones which I do not comprehend, I will be destroying the motherboard with a hammer and tossing it out. It is way too much to understand how to set coding and such. Best off investing in another phone and moving on.
The parts that will be saved if anyone can use will be the ribbon strip and also brand new display screen.
Paid $86 for the display and will sell for $75 free shipping with insurance.
Ribbon strip will be $20 free shipping with insurance. If both are wanted $95 free shipping.
Since I do love the Captivate so much another will be purchased.
Click to expand...
Click to collapse
You mean you smashed your Glide?! God, I just had mine 5 days ago. Anyway, hope my tip still helps when you're in any smaller trouble next time.
AndyYan said:
You mean you smashed your Glide?! God, I just had mine 5 days ago. Anyway, hope my tip still helps when you're in any smaller trouble next time.
Click to expand...
Click to collapse
No way lol! Only the mother board will be smashed to save the data on it from being used again. All of the other parts will be saved since another Captivate will be getting purchased.
mer80cedes said:
No way lol! Only the mother board will be smashed to save the data on it from being used again. All of the other parts will be saved since another Captivate will be getting purchased.
Click to expand...
Click to collapse
That's still sad to see. Why not just solder off the storage chip, somehow destroy it, and find a similar model chip to replace it?
EDIT: I guess the Samsung-proprietary partition table and some data on special partitions like EFS are not reconstructible on a blank new chip. Then you did the easiest choice possible.
Sent from Google Nexus 4 @ CM10.2
Is it cool for someone to take a photo of their Captivate i927 when it is at the display for the personal unlock code (PIN). It will make a good reference point enough to possibly use my touch screen to unlock my cell to reboot. Just have to get the location of the numbers and also the OK button.
After many hours research (great learning experience), the phone was done on master reset without needing to see the screen. At least now it can be sent out to get repaired without the personal information being potentially taken by another.
Done
mer80cedes said:
After many hours research (great learning experience), the phone was done on master reset without needing to see the screen. At least now it can be sent out to get repaired without the personal information being potentially taken by another.
Done
Click to expand...
Click to collapse
Woohoo, so no need to smash anything? You did an awesome deed to keep a nice phone alive
I recently obtained a Samsung Rugby Smart, my father upgraded to a new phone and I received his old Rugby, the Rugby is less than a year old and still covered under warranty. This is the first Smartphone I've owned, though I have experience with the Google Nexus 7 so I'm not completely out of the loop on how the devices works.
About a week or a little more after I got the phone and got it set up and rooted the auto-rotate function stopped working, the phone is permanently stuck in landscape regardless of whether or not auto-rotate is toggled. I've read through several threads, removed battery while the phone is on, performed a factory reset three times now, etc, and while I have downloaded an app that allows me to change the rotation I do not consider that to be a fix to the problem. I've been in contact with the manufacturer and the next time I call them I will be approved to send the phone in to be repaired or replaced. I would, however, prefer not to do that and am hoping that someone here might have different suggestions.
That said, if i do need to send it in to be replaced, I obviously need to remove root before I do that. I've been looking at the Kingo Root Android app so far this morning, but it doesn't seem to support my Rugby, what are the suggestions for the safest method of removing root from the phone? I've been reading around the forums but would like a second opinion.
RainbowMagicMarker said:
I recently obtained a Samsung Rugby Smart, my father upgraded to a new phone and I received his old Rugby, the Rugby is less than a year old and still covered under warranty. This is the first Smartphone I've owned, though I have experience with the Google Nexus 7 so I'm not completely out of the loop on how the devices works.
About a week or a little more after I got the phone and got it set up and rooted the auto-rotate function stopped working, the phone is permanently stuck in landscape regardless of whether or not auto-rotate is toggled. I've read through several threads, removed battery while the phone is on, performed a factory reset three times now, etc, and while I have downloaded an app that allows me to change the rotation I do not consider that to be a fix to the problem. I've been in contact with the manufacturer and the next time I call them I will be approved to send the phone in to be repaired or replaced. I would, however, prefer not to do that and am hoping that someone here might have different suggestions.
That said, if i do need to send it in to be replaced, I obviously need to remove root before I do that. I've been looking at the Kingo Root Android app so far this morning, but it doesn't seem to support my Rugby, what are the suggestions for the safest method of removing root from the phone? I've been reading around the forums but would like a second opinion.
Click to expand...
Click to collapse
Temp-unroot would help in this situation, I think..
MayB4ck said:
Temp-unroot would help in this situation, I think..
Click to expand...
Click to collapse
That is not something I am familiar with, how does it work?
So the issue can be referred to :http://forum.xda-developers.com/pixel-c/help/corrupted-hard-drive-dead-pixel-c-t3290331
https://productforums.google.com/forum/#!topic/nexus/xoaMSAa8yC8
I bought the Pixel C few days ago. I'm in China , I haven't got it yet. It's till in transit. I have read some people have this issue. It really worries me because I don't get to RAM it since I'm in China. If anything like this happens then I will have a bricked device.
My question is if I unlock the bootloader as soon as I get it. If this issue occurs, am I able to sideload the factory image to unbrick it?
Also , I would like to know if the latest batch(the ones you can get with the developer discount) have the wifi issue or are they of the same batch as the previous ones?
randy6644 said:
So the issue can be referred to :http://forum.xda-developers.com/pixel-c/help/corrupted-hard-drive-dead-pixel-c-t3290331
https://productforums.google.com/forum/#!topic/nexus/xoaMSAa8yC8
I bought the Pixel C few days ago. I'm in China , I haven't got it yet. It's till in transit. I have read some people have this issue. It really worries me because I don't get to RAM it since I'm in China. If anything like this happens then I will have a bricked device.
My question is if I unlock the bootloader as soon as I get it. If this issue occurs, am I able to sideload the factory image to unbrick it?
Also , I would like to know if the latest batch(the ones you can get with the developer discount) have the wifi issue or are they of the same batch as the previous ones?
Click to expand...
Click to collapse
For every Nexus device I purchase, it's standard practice to unlock it before completely setting everything up. So right after opening it, I'll do a quick setup and use a couple apps to check for things like dead pixels or lightbleed. Then, if everything checks out, I'll unlock the bootloader and flash the latest factory image to make sure I'm getting a fresh start from scratch. I've never seen a reason NOT to unlock the bootloader first. It helps get you out of trouble if something were to go awry on the software side. I've never encountered an issue that flashing a factory image couldn't fix.
While I can't attest to anything regarding the original batches, I can tell you the device I received with the dev discount has been perfect. No issues so far after using it for 2 weeks. I believe it was manufactured in January 2016 if the serial number naming scheme is the same as other Nexus devices.
If you have a dead HDD, nothing can fix it other than replacing it. I'm not sure if that's a software or hardware error, if it's software, reformatting the drive may help, if it's hardware, you're obviously screwed.
charesa39 said:
For every Nexus device I purchase, it's standard practice to unlock it before completely setting everything up. So right after opening it, I'll do a quick setup and use a couple apps to check for things like dead pixels or lightbleed. Then, if everything checks out, I'll unlock the bootloader and flash the latest factory image to make sure I'm getting a fresh start from scratch. I've never seen a reason NOT to unlock the bootloader first. It helps get you out of trouble if something were to go awry on the software side. I've never encountered an issue that flashing a factory image couldn't fix.
While I can't attest to anything regarding the original batches, I can tell you the device I received with the dev discount has been perfect. No issues so far after using it for 2 weeks. I believe it was manufactured in January 2016 if the serial number naming scheme is the same as other Nexus devices.
Click to expand...
Click to collapse
I've bought lots of nexii devices ,say, Gnex, nexus 7 , nexus 6 and 6P. I used to do a lot of flashing just like you do, the first thing I did was unlocked the BL and flashed a new ROM, kernel and maybe did some tweaking. But I haven't messed with my 6P cause I don't wanna unlock the BL for security reason. With an unlocked bootloader, just think about it, if you lose your phone, anyone can do whatever they want. with it That's not cool at all. So I'd rather keep it the way it is.
Glad to know that you don't have any issue with your device. I hope it's the same in my case. Thanks for the information.
brando56894 said:
If you have a dead HDD, nothing can fix it other than replacing it. I'm not sure if that's a software or hardware error, if it's software, reformatting the drive may help, if it's hardware, you're obviously screwed.
Click to expand...
Click to collapse
I think the problem mentioned should be a software issue. As in those two threads , they are not able to boot up the device simply by factory resetting it. And they failed to flash the factory image to the bricked device since it's locked.
randy6644 said:
I've bought lots of nexii devices ,say, Gnex, nexus 7 , nexus 6 and 6P. I used to do a lot of flashing just like you do, the first thing I did was unlocked the BL and flashed a new ROM, kernel and maybe did some tweaking. But I haven't messed with my 6P cause I don't wanna unlock the BL for security reason. With an unlocked bootloader, just think about it, if you lose your phone, anyone can do whatever they want. with it That's not cool at all. So I'd rather keep it the way it is.
Glad to know that you don't have any issue with your device. I hope it's the same in my case. Thanks for the information.
Click to expand...
Click to collapse
While this is definitely true, your average cellphone thief is about as tech savvy as a wet piece of leather hahaha I've had this concern myself but then realized that maybe 2% of Android owners know how to get to the recovery, hell most reps at cell phone stores don't even know how to do it, even the ones that are "techs"!. When I had my S4 rooted and stupidly let it slip that the phone was rooted, next time I came in the rep looked over the phone and called out a tech who looked at the phone for 30 seconds then said "do you know how to get to the recovery on this???". A simple pin/password/pattern lock will thwart about 90% of phone thieves out there from getting access to your data, they're most likely just going to wipe it anyway. They couldn't care less about your data, they can't sell or use that as easily as they can the device itself.
Sent from my Pixel C using Tapatalk
brando56894 said:
While this is definitely true, your average cellphone thief is about as tech savvy as a wet piece of leather hahaha I've had this concern myself but then realized that maybe 2% of Android owners know how to get to the recovery, hell most reps at cell phone stores don't even know how to do it, even the ones that are "techs"!. When I had my S4 rooted and stupidly let it slip that the phone was rooted, next time I came in the rep looked over the phone and called out a tech who looked at the phone for 30 seconds then said "do you know how to get to the recovery on this???". A simple pin/password/pattern lock will thwart about 90% of phone thieves out there from getting access to your data, they're most likely just going to wipe it anyway. They couldn't care less about your data, they can't sell or use that as easily as they can the device itself.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Well, usually thieves might just wipe everything. But still, there are risks. There are certain ways to go around the locked screen if you got a unlcoked BL and rooted phone. I've got all my photos( No nude pics ) stored on Google, and also all my contacts, whom wouldn't be happy to share their information with a thief, and some notes, payment apps as well as some important emails. There's too much going on and I don't wanna take risks. Also, if my phone got stolen, I'll have make sure the SOB got a brick ,nothing more. Sure they can tear it apart and sell some parts of it, but they don't get a phone.
I still flash roms and stuff on my oneplux which i got few days ago since my nexus 6 went dead, I do that because it's not my main phone and I don't have a lot of personal information stored there unlike on my 6P. For a tablet, maybe I would do that since I'll put it home usually .
randy6644 said:
Well, usually thieves might just wipe everything. But still, there are risks. There are certain ways to go around the locked screen if you got a unlcoked BL and rooted phone. I've got all my photos( No nude pics ) stored on Google, and also all my contacts, whom wouldn't be happy to share their information with a thief, and some notes, payment apps as well as some important emails. There's too much going on and I don't wanna take risks. Also, if my phone got stolen, I'll have make sure the SOB got a brick ,nothing more. Sure they can tear it apart and sell some parts of it, but they don't get a phone.
I still flash roms and stuff on my oneplux which i got few days ago since my nexus 6 went dead, I do that because it's not my main phone and I don't have a lot of personal information stored there unlike on my 6P. For a tablet, maybe I would do that since I'll put it home usually .
Click to expand...
Click to collapse
In that case, Android Device Manager comes into play and allows you to beef up your security.
Sent from my Pixel C using Tapatalk
Yesterday i received some ntag215 nfc tags. I immediately tried to read and write them but my htc showed no sign of recongnition. That same day and many days before i have used nfc to pay at the supermarket. This works perfectly. I found that it gives some kind of reaction when placing the tag on the front speaker. It knows its there but it cant seem to fully connect/read/write the tag. The transmitter just seems too weak. Is this a normal HTC 10 flaw? I still have 3 weeks of warranty so i might wanna get it replaced. Too bad i just applied a sick dBrand skin. If anyone has had this issue and mannaged to fix it in some way please let me know. The tags worked on other android devices. I tested it with a Sony Z3 compact.
NFC
bamidrol said:
Yesterday i received some ntag215 nfc tags. I immediately tried to read and write them but my htc showed no sign of recongnition. That same day and many days before i have used nfc to pay at the supermarket. This works perfectly. I found that it gives some kind of reaction when placing the tag on the front speaker. It knows its there but it cant seem to fully connect/read/write the tag. The transmitter just seems too weak. Is this a normal HTC 10 flaw? I still have 3 weeks of warranty so i might wanna get it replaced. Too bad i just applied a sick dBrand skin. If anyone has had this issue and mannaged to fix it in some way please let me know. The tags worked on other android devices. I tested it with a Sony Z3 compact.
Click to expand...
Click to collapse
I just check HTC 10NFC location is around rear camera.
I knew that already. The problem is that it doesn't seem to be able to read the taggs. Not on the back and not on the front. There must be more people having this issue.
It's a known problem with the HTC 10.
The NFC signal is not strong enough.
If you search for it here on XDA, there are some others threads. No solution for it yet.
I sent mine to HTC already. They said they repaired it, but it's still not working for me.
Sent from my HTC 10 using XDA Labs
NFC Tags do not work, if you ask HTC Customer support they will tell you that the phones NFC only works for Android Beam and other Active devices (which does work flawless) Scanning NFC Tags or Cards does simply not work.
Yeah that's what I thought as well. Pretty bad that HTC even choose this chip. Even worse that HTC support Netherlands didn't even bother to tell me it just won't work. They offered a repair. But because I unlocked my device and run Leedroid it would cost me a fair amount. I refused. They honestly have a system that flags your device when you root it. That's insane
If you RUU that should wipe Root. Leaving you with an unlocked bootloader only.
The disclaimer that warranty is lost on unlock is mostly only show.
Don't know how it works with HTC.
The problem is that apparently HTC has a database of modified devices. Even when you reset the device they can see you modified it at some point. The guy told me the exact day and time I unlocked my phone. He even saw the exact time I first installed twrp recovery.
Woot? I totally understand unlocking, as this is done via Webpage from HTC.
But how the hell do they know when you installed a different recovery?
You can always revert back to exact stock settings / RUU / relock bootloader, but once you unlock through HTC Dev, they know your device was modified since you've entered your phone info into their database. Besides, anyone who unlocks the BL through HTC Dev knows what they're doing. Otherwise, they wouldn't be running adb commands, pulling tokens, and unlocking through their dev site. So yes, they know once you unlock that your device was modified. Even if you unlocked the bootloader, and then didn't do any modifications, I think the bigger question at this point would be... why the hell did you even bother doing that? (rhetorical/sarcastic question lol)
Which is why Sunshine can be SO FREAKING USEFUL AND BEAUTIFUL. I did S-OFF / BL LOCKED on my wife's (Verizon) phone since I got it for her months after release (unlike my phone, which was BL UNLOCKED, then S-OFF afterwards. i pre-ordered my device, US Unlocked variant, and unlocked it right out of the box through HTC Dev). I then proceeded to hardcore hard brick the phone months later when I stupidly wrongly flashed a lower partial firmware package after a bad update to Nougat firmware, instead of RUU'ing. The modified aboot that was already loaded was ultimately the phone's demise. But since HTC didn't have any record of modification to the device and it was totally hard bricked, it was warrantied without any problems. To them, it was just a phone that stopped working, no charge, no lights, no nothing. BTW, yes I did feel guilty about this..
Now if I did that with my US Unlocked HTC 10 with an unlocked bootloader logged in their database, it wouldn't have surprised me, nor would I have felt wronged, if they refused full warranty after such a problem.
WOW, THAT WAS WAY OFF TOPIC! But hopefully a lesson to someone..
As for the OP, back on topic!!:
I totally feel your pain. I bought a bunch of tags a month ago to write all the amiibos with special function in Breath of the Wild, just to find the damn phone not being able to write. Sometimes it would keep spasmodically beeping like it knew the tag was there, but never successfully write the tag. My only solution was to use a different phone, in my case my FreedomPop HTC M9. It shocked me that the HTC 10 had such a crap NFC chip and yet the M9 was fine. Oh well, I have all the exclusive Amiibo sets now, and the twilight bow, goddess sword, sword of the six sages, and fierce deity sword all hanging in my house in Hateno village. Plus a fully upgraded Fierce Deity armor set and Sky armor set, which shouldn't even be available yet! Oh my Lord... the amount of time I wasted farming those star fragments...
Good luck with the tags though OP! If possible, try installing TagMo on another Android device if you have any. It also worked on my wife's old Galaxy S5 and a Galaxy Note 2014 edition tablet...
Exactly the same scenario here bro. Wanted to make amiibos but found out the metal case of the 10 is just too distorting. I'll stick to using my old Z3 for now. Can you send me a zip with all amiibo data you used for the Tags? I made 20 already but especially the zelda ones seem to be the wrong amiibos. Getting shield from the one that should give me bows.
bamidrol said:
Exactly the same scenario here bro. Wanted to make amiibos but found out the metal case of the 10 is just too distorting. I'll stick to using my old Z3 for now. Can you send me a zip with all amiibo data you used for the Tags? I made 20 already but especially the zelda ones seem to be the wrong amiibos. Getting shield from the one that should give me bows.
Click to expand...
Click to collapse
pm'ed. sorry it took so long