DaVinci Junior cartridge reset (Page 39 of 58)

I know it has been posted a few places, but not on this main thread, so I just formally wanted to make a post.  We are finding that if you have firmware version 2.2.7 on your printer that if you try to rollback firmware in the same as we found out work with firmware 2.2.6, that it will not work with the newer firmware version 2.2.7.  kr15_uk has a proposed idea in other thread on here if anyone with 2.2.7 wants to try it.  Otherwise let us know if anyone out there finds a way to rollback firmware when you have firmware version 2.2.7.

Just to clarify, I'm not taking any sides what so ever. Just want to comment on this.

@Bozotclown1970 - it's your document, work etc and your decision entirely, totally agree, all do respect.
But @greatone76 just offered you to post this document on Instructable so it's much easier to find for anyone of interest which isn't part of this forum, not to make money of your work (I guess). Personally I don't see any issues there if your name is mentioned all over the place in the Instructable. Just makes it easier for newbies to find. But once again, it's your work and your decision, I do respect that.

Also just want to comment about @greatone76 "side business" - I know it may seem to be unfair to the community that he's/she's making money out of it. But in defence to @greatone76 he's/she's active member of this forum and all XYZ hacking community all over the net and helps to solve issues people are having with XYZ printers.
He's/she's not saying "don't waste your time with logic analysers just buy this brilliant code and all your problems will go away".
He's/she's just offering to do job for you and charge fair amount for that.

For example - me, I was considering to buy logic analyser and try to hack NFC myself. But then I weighted both options.
To hack it myself I'd have to spend £5-10 on all the stuff, wait for it to arrive and then spend at least an hour of my time to get that pesky code.
And on the other hand by buying (what I did) that code which cost me roughly the same I've got the code pretty much within an hour or so and I was ready to print in no time.
It's like when you're heading home after long day, feel hungry and see McDonalds... You know that home cooked food is healthier, cheaper and better in general but yeah - McD's is there for you!

I know, I'd learn something new by playing with logic analyser and I could generate passwords for all my NFC tags. But yeah... I need just one tag at the end of the day, more than one would be probably better but 1x works well for me hence all temp adjustments I do through the gcode editing etc.
(Btw, now I've ordered logic analyser and I'll finally do it myself to learn and not to be dependant on @greatone76 or who ever will come up with another hacking procedure. But at the time that was the easiest way.)

Just to clarify, this is just a personal opinion, no plan intended to take any sides or what so ever, @Bozotclown1970 I do totally respect your decision and also thanks for the effort you've put into producing this document.

I'm intrigued as to how XYZ have implemented the lock down on "hacked" rfid tags in the firmware.

I wonder if they just store the tag no and remaining length in flash for the last one or for all tags ever used?
If it's just the last one then all we need do it have 2 tags and change then over.
How much flash is available to them anyway as I doubt if they put lots of spare in the printer in the first place.
Just need someone who has upgraded in error to test... no I'm not volunteering

I suspect that it is still possible to use the "hacked" tags as long as the printer hasn't seen it with a lower length remaining value before hand (or have they put logic in the check to see if it is > 100m>?).  So again, we could modify a tag first then present it to the printer and see it if accepts 300m (or whatever length is used) .  But the tag is still a one use tag for that printer.
We could all band together and have a tag swop-shop..

The same happened to me. Funny part is that even if you deny (be clicking "X") XYZWare proceeds with upgrade. At this moment I just disconnected the USB cable and went back to an early version of XYZWare.

Regards,
Marcin

I hadn't because I've already paid the 6GBP for the password via the Ebay listing which has been working fine until the 2.2.7 firmware upgrade.  As I have a hacked NFC tag here already I was hoping to do some testing for greatone76 to help me to carry on using the hacked chip and help them with future Ebay sales.

@Bozotclown1970 - Correct me if I'm wrong but logic analyser isn't the answer to the firmware 2.2.6+
You can simply do passcode decoding to unlock NFC editing options?! Or I'm missing something?!
(Still waiting for my analyser to arrive, btw do you mind PM'ing your document?!)

I had 2.2.6 installed on my one for couple of weeks and after you do at least one change to the NFC (temp, length etc) it puts that NFC chip into his "blacklist" and no meter what you do you can't revive it.

On a slightly off topic note, I have purchased a Hobby Components logic analyser and have to use the sigrok software (Pulseview or sigrok-cli).

I have wired it up as per Bozotclown1970's documentation (GnD, SDA & SCL) , but I'm not getting anything like the data that I'd expect.
I have the password for my card and see many 0x1B bytes , but none are followed by the password I expect.
It is probably user error.

Has anyone any experience with this analyser?

Different in the 2nd AND 4rd  byte!!
04 4F 57 94 vs
04 20 57 FB

As well as page 14.

30 31 32 33 vs
30 34 39 35

link not working!

Regarding the nagging upgrade and potential to initiate it by accident, I assume people would know about this, but I thought I'd post anyway in case - you can easily add a rule to the Windows firewall to prevent individual applications from accessing the internet.  Once the nag screen started coming up every few minutes, I just blocked XYZ Ware from accessing the internet and that did it - if it can't access the internet, it can't check for new versions and/or firmware.  The program doesn't use "the cloud" to slice, so it continues to work just fine "offline". 

Here's a page detailing how to add a new rule:  http://www.howtogeek.com/227093/how-to- … s-firewall

Hopes this helps someone avoid inadvertently upgrading their firmware and breaking the NFC hack.

You have 3B 3D 55 missing one number if you have it this is will be password

Where you able to set the card anywhere above 300M?
I've tried without luck, i believe that the firmware block anything above 300M or the checksum return negative results.