DaVinci Junior cartridge reset (Page 31 of 58)

So those running the password attempt algorithm, can you try just one bit shifts within a byte... ie
HEX: 01 02 04 08 10 20 40 80

So I got some NTAG213 blanks and used LOGIC to capture the expected passwords for my blanks, then programmed the blank tags with appropriate data, set the password in page 43.  I can then read back the data providing the appropriate password that was sniffed (no read if no password supplied), but the printer still shows 'unrecognized'.  I think both the password and the PACK need to be known.   Anyone have success writing BLANK NTAG213 ???   

@greatone76

I have been on here since page 22, must have missed that in my original reading.  Thanks for pointing it out.

@crcasey

If you go with a higher quality the overall print will be slower.  Also, in settings under advanced there is a speed setting you can slow it there too.  Not sure how much slower you need, but you can start there.  I don't think there would be anything on the tag that would give speed/feed rate I would think that would come from the slicer.

Hi all,

I've bough my da vinci junior about a month ago and I've been trying to read every post on this forum. It seems that there is some great work done and I hope to contribute a bit.
I can program a bit and know a bit of electronics and arduino. I've got a PN532 board hooked up to my arduino and I'm trying to read out my NFC data. I know it is protected and I would like to bute force the password but it will all depend upon the security set on the nfc.
Upon inspecting the ntag213 data sheet, I've read that the can prevent brute force hacking by activating a counter in the nfc chip. (page 18 of the manual)
This counter is located at byte 0 on page 42 (ACCESS byte - see table 10)

This is where I need some help. Can the people who already have there password, read out their nfc tags and report the value of the access byte. If this is 00h, it means that brute force is possible to get the password out (may take a long time).

So who can check the setting of this byte?

Thanks from Belgium

manual: http://www.nxp.com/documents/data_sheet … 15_216.pdf

Hi JustBen

that correct regarding the brute force. It will take far more time then reading out the i³C data and analysing it. But this is more easy and probably more for the masses. You don't need to open up your printer and you don't void warranty.
It the brute force works, maybe somebody can write an app for it and everybody can do it at home. If more people provide their data, we maybe can find a pattern or the algorithm they use.

The data dumps I found did all contain 80h for the ACCESS byte, withc means passwordprotection on, no count for brute force.
I also noticed that most of the dumps only show 42 of the 44 pages. They forgot to update the arduiono sketch to read 44 pages instead of the standard 42.

SO I guess I would give it a go and see what happens. Hopefully I don't ruin my tag.

Ben,

If you are not seeing all 45 pages in your dumps. That can be corrected by making sure the Arduino code you are using is dumping all 45 pages. By making sure the following line is correct.

for (uint8_t i = 0; i < 45; i++) 

I have been looking for days on a way to get the Pack information. I did see where the old libraries did allow for that, but not the new ones.

Hi, 

i bought the key and was able to reset the tag two times. However now it isn't working any more. I had changed every possible value to the ones from the sample tag in the manual and had also tried every possible combination with the colors/lenghts,  but the printer always told me unknown spool when i try to open the spool statistics or try to print. 

It couldn't be the printer,  as i have a second tag (the one from the clear one,  not hacked),  which at least shows the statistics and with wich i was able to start a final print,  as there had been 1 meter left.

I had attached the tag readout from the no longer working one. Could someone with a working tag please check this and tell me,  if maybe there is a mistake in it?

Use the card info posted here.  Make sure to change Page 08 to actually match the instructable at 5A505000

Page 14: Should match the instructable as well at 30333338.

We have now seen this 2 or 3 times were after a few resets it gives spool error.  The last time the issue was everything was good except page 14 was the old data.  I'm kinda guessing that this number has something to do with the color and it needs to match perfectly with something I'm guessing in page 8.  It also could be tracking the tag based on this number, but last time once this was changed the card worked again. 

Try changing the 2 pages above and report back. 

If that doesn't work we might want to try taking someone else dump and copying pages 8 to 14.  It might be using one of those pages to track the card usage. 

I'm also wondering if there is a simple if the same card is used in a certain number of times in row and counts up to a certain footage it errors out. 

Anyone who has been through a few reset please update up with any of your observations. 

IF you been through multiple resets have you used other card between uses ect.

IN your screenshot, you're missing a page 2C. this should contain the password ack bytes and some other things. Also page 2B should contain your password. Or is that never shown? I still need to break my password.