text: Jump to page: Results 321 to 330 of 457
  22nd July 2016, 07:10 AM
  Posts 3,047	Rep Power 714 Originally Posted by Paul Lin
  <...> 5. try to change CID on the new SD card, yet find anything works.
  You really mean anything works (if so, what works?), or you mean nothing works?
  BTW: welcome to GPS Power, Paul Lin. To avoid clutter, please don't leave any "Thank You" posts but use the button or the LIKE this post ↑ link instead
  23rd July 2016, 09:35 PM
  Posts 1	Rep Power 0 Hi Everybody
  Can somebody summarize the whole process? It seems really confusing
  Reply With Quote 23rd July 2016, 09:55 PM
  Posts 12	Rep Power 0 Originally Posted by adamek
  I did a dump of the used card, you can find it here: [Only registered and activated users can see links. ]
  Please let me know if you find any ineresting changes on the used card. I will check today if I had a 0001 or different value there and let you know.
  Part #10 is corrupted.
  Reply With Quote 25th July 2016, 01:09 PM
  Posts 48	Rep Power 5 Originally Posted by MrSolo
  I described my steps [Only registered and activated users can see links. ] .
  This works for virgin and married cards.
  A fews things to keep in mind.
  The MB-Garmin cards do have a slightly higher capacity than normal cards, so if you want to use the image method you would need the next bigger card (e.g. if your original is 16GB card you need a 32GB card / if original is 32GB you need a 64GB card).
  If you know how to create a valid exfat card and can change the volume label to a 12/13 digit label you might not need bigger cards which seems to be another part of the copy protection.
  I tried to analyse the actual software and found what I believe is a list of valid labels/card names
  As you can see these are longer than the 11 characters you can normally assign to an exfat volume.
  On Linux you can use 'exfatlabel' to rename the volume.
  Looking a bit further there also seems to be different types of card that the unit accepts.
  Unfortunately I have not been able to find out how the systems identifies the different card types.
  Also the version that adamek uploaded seems to be different from my version (C-class/A-class)
  The C-Class version seems to use some kind of embeded Windows CE based OS
  Which is the NTG5E head unit.
  While the new A-Class uses a Linux based OS.
  Which is the NTG5Star1 head unit.
  Unfortunately both are called Audio 20.
  I hope someone here knows how to disassemble the code.
  I have only found a few things in the code (like the list which I believe is the list of valid volume labels) yet that I don not understand (yet).
  Originally Posted by adamek
  Okay, I did some quick analytic on what the differences between used and virgin are.
  .unl/.gma files have been deleted
  dorp.bin has been deleted
  GarminDevice.xml has been created
  So I guess this only gives us little info on the actual process.
  We already knew that the .unl/.gma files are deleted during first use -> from what I found they are stored within an internal database together with the CID / Card Serial
  The GarminDevice.xml contains the contend of the .unl files in the unlock section of the file (there are also a few other things like VIN gets added, ifix date and CID/Serial).
  I noticed that dorp.bin seems to trigger actions in the head unit.
  At least if the file is present you get prompted if you want to use the card with this car.
  Reply With Quote 25th July 2016, 05:43 PM
  gpsmercedes
  Location Piacenza
  What do you think about UK ebayer that sell the "genuine SD" (but without box and brochure ...uhm ... ) with a cheap price (110-140 euros)? Are those fake? Thank you
  Reply With Quote 25th July 2016, 07:25 PM
  Posts 48	Rep Power 5 Well I got " donated" 3 dumps with CID from3 different people who bought the card on ebay, they all three had the same CID, so I would asume they were cloned.
  It's very unlikely that 3 different cards have the same CID.
  Last edited by _Stefan_; 25th July 2016 at 08:59 PM.
  Reply With Quote 25th July 2016, 09:48 PM
  Posts 2	Rep Power 0 it's clear. It was my suspect. But it works fine with same CID? If same CID is married with different car I think that upgrade will be locked when the first do the upgrade, right?
  Reply With Quote 26th July 2016, 11:45 AM
  I contacted someone who won't join the forum...
  Regarding the NOT WORKING Samsung evo plus sd cards he assumes that there are sd cards on the market that are not genuine. He on his own bought three cards and all worked fine. They all came with holograms on the package and verification codes to check on Samsung's website.
  The CID of the sd card is of course no guarantee, but he assumes that those people generating fake cards bother to set the CID to look like a Samsung, so it might be an easy way to spot a fake.
  Now, you can ask if it's likely to get faked cards on amazon?! I have no doubts that this could happen. I have yet made experiences with faked batteries on amazon that were sold as genuine.
  The other possibility is that the cards are not using the same movinand chips, possibly older rebaged stock...
  When changing the CID and seeing mmc0:59b4 (e.g.) NOT the mmc0:0001 --> These cards could be pre-evo plus cards, classe 6. But these cards are also working as the one I contacted has bought three of them and could change the CID...
  He also noticed the following post:
  "Writing new CID: 744a605344432020023cffffffe14fffffffbc0001ffffff8b"
  --> This is not right, there are too many digits, looks like a load of extra f's in there for some reason, which suggests, that somehing has gone wrong.
  I can confirm that. The CID could (for me) only correctly be changed on Android, not on Ubuntu.
  It will only work with proper sd interface though, not with usb readers.
  Now, for me, both can be the reason: interface or Ubuntu...
  As I said, on Android (rooted) it works.
  Reply With Quote 26th July 2016, 02:27 PM
  as for the mmc0:59b4 I could NOT change the CID on neigther rooted android (tried 3 different models) nor Linux, while with the mmc0:0001 it was working on both.
  Seems to be a display/output problem only on the screen specific to Linux. No idea why the 3 x ffffff are displayed, but this is NOT was is being written to the actual card. The correct CID is written to the card.
  I will have a look at the source if I find the time and see if I can figure it out.
  Reply With Quote 26th July 2016, 07:33 PM
  Posts 11	Rep Power 0 Hey
  I'm sorry that I can't help much, but I have a problem myself. The problem is that when I run the command to set the CID, I get the error "Failed to enter vendor mode. Genuine Samsung Evo Plus?". But I have samsung evo plus 64gb sd card, I don't understand where the problem is.