Hacking [Tools] AmiiBomb

[missbender]

i got 5 Tags (all not working but the worked the first time) an im using the exact .bins i used the first time ....

the Tags are rewriteable ?

READING works fine for me ...

 

[nitrostemp]

once they are written they are done, make sure you dont have the tag on the writer until it tells you.

 

[Jokkovitch]

Tags ARE NOT rewritable.

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk

 

[DjoeN]

Hi again ...
i got it Working with 0.2 on an Win7x64 at work (i ordered the right cards now as it was stated here- not the ones that came with the NFC r/w)

i wrote 5 cards with different Zelda Amiibos without any problems

Now i wanted to rewrite them with different stuff at home but i cant get it working here.... (tried with one X64 Win7 and one X64 Win10)
I can read the Cards i wrote at work without problems, but i cant rewrite them

I tried 0.2 and 0.3 version, an i reflashed the Ammiibomuino several times to the the ELEGOO uno R3.
The cards can be rewritten several times ???

i get this error:

"C:\AmiiBomb_0.3_Alpha\DUMP\Wolf Link (20 Hearts, Cave of Shadows Beaten, B40).bin" is send to AmiiBombuino.

Error occured: ERROR Data: A MIFARE PICC responded with NAK.

You can't rewrite NTAG cards
- All those NTAG cards or lables for Amiibo are write once

 

[GraFfiX420]

Hi again ...
i got it Working with 0.2 on an Win7x64 at work (i ordered the right cards now as it was stated here- not the ones that came with the NFC r/w)

i wrote 5 cards with different Zelda Amiibos without any problems

Now i wanted to rewrite them with different stuff at home but i cant get it working here.... (tried with one X64 Win7 and one X64 Win10)
I can read the Cards i wrote at work without problems, but i cant rewrite them

I tried 0.2 and 0.3 version, an i reflashed the Ammiibomuino several times to the the ELEGOO uno R3.
The cards can be rewritten several times ???

i get this error:

"C:\AmiiBomb_0.3_Alpha\DUMP\Wolf Link (20 Hearts, Cave of Shadows Beaten, B40).bin" is send to AmiiBombuino.

Error occured: ERROR Data: A MIFARE PICC responded with NAK.

You cannot rewrite standard NTAG215's, once the lock bits are written, which they have to be for the system to read them as an Amiibo, that's it, consider the lock bits to be similar to an efuse, once blown, that's all she wrote, folks.

 

[LoDeus]

I think maybe the process isn't as clear as it should be, have you flashed your arduino with the amiibomb-uino firmware?

Of course I did, I think I'll record the next time I'll try to show you and the OP what is happening if it doesn't work

 

[GraFfiX420]

Of course I did, I think I'll record the next time I'll try to show you and the OP what is happening if it doesn't work

That may help, I can say that I got some fresh NTAG's the other day, and it was the first time I used v0.3. I was able to flash my arduino uno using both xflasher and the internal flasher fine, and I was able to write an amiibo fine. The writing of the amiibo seemed to be quite a bit faster than the write's I experience with my powersaves module, or the arduino using the old manual method. However, this may be a placebo effect.

I'm using VMWare Fusion with a Win10 VM to do all my work, I have not tried to do any of this under Win7.

 

[aut0mat3d]

@missbender If you write a amiibo .bin file to a ntag215 the Lockbit of the Tag has been set to make it work.
Setting the Lockbit means you cannot rewrite the Tag to another Amiibo.
1 Ntag = 1 Amiibo

 

[missbender]

OK are there any Cards that are rewritable ?
Or do they Work if i dont set the Lockbit ?

I found hose on Ebay they should work; right ?

Frequenz: HF 13.56MHz
Standards: ISO 14 443-2 A, ISO 14 443-3 A, NFC-Forum Typ 2
Funktionen: Lesen/ Schreiben, Schreibschutz, Wiederbeschreibbar
Form: Sticker (30mm)
Formatierung: NDEF wird unterstützt
Speicherkapazität: NXP NTAG 215 - 540 Byte (NDEF: 504 Byte)
Chipsatz: NXP NTAG 215
Material: Aufkleber (PET)

BTW has anyone made a custom Icon set to print on the NFCs ?

 

[aut0mat3d]

@missbender
Setting the Lockbit is Part of the Writing Process. Without locking the Tag it wont work.
They can only be written once.

The described Tags should work.

For Graphics/Icons try this as a start: https://gbatemp.net/threads/custom-amiibo-cards-for-botw.464093/

 

[Makk]

Hi, really appreciate your work. Keep on with it.
Is there a possibility to add a batch function. Where you select a Folder and create one NTAG after another. So you would open up your directory with A.bin B.bin C.bin then you start a batch Job. The little Window pops up and tells you to put your NTAG on the Reader to write A.bin. When it is finished succesfully it prompts you to put the next NTAG on the to write B.bin after that the same with C.bin.

That would be great.

 

[VargRSBZ]

Hello All,

i have downloaded Amiibomb 0.3 Alpha. I'm on Windows 7
I have a error message at the launch, and everytime I click on a menu

************** Texte de l'exception **************
System.MissingMethodException: Méthode introuvable : '!!0[] System.Array.Empty()'.
à AmiiBomb.Main_Form.AskBinFolder()
à AmiiBomb.Main_Form.Main_Form_Shown(Object sender, EventArgs e)
à System.Windows.Forms.Form.OnShown(EventArgs e)
à System.Windows.Forms.Form.CallShownEvent()
à System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
à System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
à System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
à System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
à System.Windows.Forms.Control.InvokeMarshaledCallbacks()


************** Assemblys chargés **************
mscorlib
Version de l'assembly : 4.0.0.0
Version Win32 : 4.0.30319.17929 built by: FX45RTMREL
CodeBase : file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
AmiiBomb
Version de l'assembly : 1.0.0.0
Version Win32 : 1.0.0.0
CodeBase : file:///C:/MARC/WIIU/WIIU/AmiiBomb_0.3_Alpha_by_Ac_K/AmiiBomb.exe
----------------------------------------
System.Windows.Forms
Version de l'assembly : 4.0.0.0
Version Win32 : 4.0.30319.17929 built by: FX45RTMREL
CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Version de l'assembly : 4.0.0.0
Version Win32 : 4.0.30319.17929 built by: FX45RTMREL
CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Version de l'assembly : 4.0.0.0
Version Win32 : 4.0.30319.17929 built by: FX45RTMREL
CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms.resources
Version de l'assembly : 4.0.0.0
Version Win32 : 4.0.30319.17929 built by: FX45RTMREL
CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
Accessibility
Version de l'assembly : 4.0.0.0
Version Win32 : 4.0.30319.17929 built by: FX45RTMREL
CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
Newtonsoft.Json
Version de l'assembly : 10.0.0.0
Version Win32 : 1.0.0.0
CodeBase : file:///C:/MARC/WIIU/WIIU/AmiiBomb_0.3_Alpha_by_Ac_K/AmiiBomb.exe
----------------------------------------
System.Core
Version de l'assembly : 4.0.0.0
Version Win32 : 4.0.30319.17929 built by: FX45RTMREL
CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Numerics
Version de l'assembly : 4.0.0.0
Version Win32 : 4.0.30319.17929 built by: FX45RTMREL
CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Runtime.Serialization
Version de l'assembly : 4.0.0.0
Version Win32 : 4.0.30319.17929 built by: FX45RTMREL
CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Data
Version de l'assembly : 4.0.0.0
Version Win32 : 4.0.30319.17929 built by: FX45RTMREL
CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Version de l'assembly : 4.0.0.0
Version Win32 : 4.0.30319.17929 built by: FX45RTMREL
CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
mscorlib.resources
Version de l'assembly : 4.0.0.0
Version Win32 : 4.0.30319.17929 built by: FX45RTMREL
CodeBase : file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------

************** Débogage JIT **************
Pour activer le débogage juste-à-temps (JIT), le fichier de configuration pour cette
application ou cet ordinateur (machine.config) doit avoir la valeur
jitDebugging définie dans la section system.windows.forms.
L'application doit également être compilée avec le débogage
activé.

Par exemple :

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

Lorsque le débogage juste-à-temps est activé, les exceptions non gérées
seront envoyées au débogueur JIT inscrit sur l'ordinateur
plutôt que d'être gérées par cette boîte de dialogue.




Can someone help me ??

Cheers
Marc

 

[VargRSBZ]

Hi EveryOne,

AcK77 gave me the solution to my issue.
I needed to update .NET from 4.5 to 4.6.1 and now all it's ok !!!!

it could be nice to notice all the prerequisites in order to use this nice tool.. Amiibomb

Good Job !!!!

Cheers
Marc

 

[Rizzice]

Just wondering has anyone gotten the plastic card type NTAG215 to work? My sticker ones work just fine, but my order of 100 NTAG215 plastic cards don't register whatsoever. Wondering if this is something that can be fixed in the future or if anyone has experienced similar?

 

[Jokkovitch]

Can you scan them using the NXP app ?
And post the result here.

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk

 

[RubyRoid]

Just wondering has anyone gotten the plastic card type NTAG215 to work? My sticker ones work just fine, but my order of 100 NTAG215 plastic cards don't register whatsoever. Wondering if this is something that can be fixed in the future or if anyone has experienced similar?

You either have tags of different format or the antenna of your reader is too weak to read them. I can't help with the first option but have a nice solution to the second.

Stick a small coin to the middle of your NFC module's antenna this way: http://imgur.com/a/MQvez

Make sure the glue and the coin don't touch any exposed metal contacts on the board.

I used hot glue but you can use anything you like, even a gum.

The coin trick greatly increases the antenna sensitivity.

 

[Rizzice]

You either have tags of different format or the antenna of your reader is too weak to read them. I can't help with the first option but have a nice solution to the second.

Stick a small coin to the middle of your NFC module's antenna this way: http://imgur.com/a/MQvez

Make sure the glue and the coin don't touch any exposed metal contacts on the board.

I used hot glue but you can use anything you like, even a gum.

The coin trick greatly increases the antenna sensitivity.

Thanks for this tip! I'm going to try it out.. just wondering do I have to glue it or can I just put the coin on top? And any coin will work at all?

I'm almost 99% sure it's the antenna, but I just tried with a 1 cent penny on top without adhesive and didn't work.

 

[urherenow]

First off, I have no clue about the specifics of my arduino. It's obviously a clone and goes by the name EDarduino. The arduino suite did not even have drivers that would install for my unit. I had to download drivers for CH340, which properly made it a com (4) port.

The internal flasher errors out no matter which model I choose to flash. Any suggestions or does this model need it's own firmware? The other flashing method didn't spit out any errors, but I'm not sure if it's working at all. I haven't recieved my NTAG stickers yet and there doesn't seem to be anything at all I can do with the included key fob or card, to include telling me what kind of NTAG it is. I thought at least it would detect an NTAG and give me an error that it's not the correct kind. But no indication at all...

I am using the v0.3

 

[aut0mat3d]

You could try to flash it with Xloader.
If your Arduino Clone does not have a proper Bootloader preloaded you need a ISP Programmer to flash the Bootloader via Arduino IDE.
Simply grab another (working) Arduino and use it as ISP: https://www.arduino.cc/en/Tutorial/ArduinoISP
or buy a dedicated ISP Programmer like the AVRisp MKII: http://www.atmel.com/tools/avrispmkii.aspx

 

[GraFfiX420]

First off, I have no clue about the specifics of my arduino. It's obviously a clone and goes by the name EDarduino. The arduino suite did not even have drivers that would install for my unit. I had to download drivers for CH340, which properly made it a com (4) port.

The internal flasher errors out no matter which model I choose to flash. Any suggestions or does this model need it's own firmware? The other flashing method didn't spit out any errors, but I'm not sure if it's working at all. I haven't recieved my NTAG stickers yet and there doesn't seem to be anything at all I can do with the included key fob or card, to include telling me what kind of NTAG it is. I thought at least it would detect an NTAG and give me an error that it's not the correct kind. But no indication at all...

I am using the v0.3

I believe you should be seeing the error. Have you tested the examples from the mfrc522 library to make sure that you're getting proper communication? I'm not sure how this will work with a clone arduino, but why not just buy an official one? If you get the arduino nano and the 522 rfid board I think you can get both for like $10.

--------------------- MERGED ---------------------------

You could try to flash it with Xloader.
If your Arduino Clone does not have a proper Bootloader preloaded you need a ISP Programmer to flash the Bootloader via Arduino IDE.
Simply grab another (working) Arduino and use it as ISP: https://www.arduino.cc/en/Tutorial/ArduinoISP
or buy a dedicated ISP Programmer like the AVRisp MKII: http://www.atmel.com/tools/avrispmkii.aspx

@urherenow, @aut0mat3d seems a lot more familiar with what you're experiencing. I would definitely try the bootloader first, could solve all your problems.