ROM10 ATR string invalid

[ismarhadzia]

I have other cards that work fine. There is nothing wrong with my hardware setup.

This perticular card gives this message when trying to do reset...

Opening of COM1 was successful
Reset failed
Error reseting card, ATR string invalid
Closing of COM1 was successful

Anybody have any idea...?

[ki55tory]

The card is looped ... not to be confused with locked ... it is looped.

[ismarhadzia]

Is there anything out here that can unloop the card?

[FishPants]

I have other cards that work fine. There is nothing wrong with my hardware setup.

This perticular card gives this message when trying to do reset...

Opening of COM1 was successful
Reset failed
Error reseting card, ATR string invalid
Closing of COM1 was successful

Anybody have any idea...?

I got that on a ROM10 when using my Nexus programmer without dip switch 1 set to ON.. Could program a ROM3 but for whatever reason I had to set that switch for the 10.. Also try Nagra 3.0

[ismarhadzia]

I am using Regular ISO with 3.68MHz and I have mikobuIII Unlooper.
Will I be able to fix the problem with any of them.?

[ismarhadzia]

This is what I did to fix a looped Rom2. Hell, why not give it a try?

Good luck.



(c&p from other thread)
OK, I fixed it as follows:

1) Ran ATRressurection in Xtal 3.68 mode and got a weird response a few times.

2) Ran a bunch of bugbusters on it in Nagra 1

3) Ran ATRresurrection again, this time in 1.8 mode (hell I was desparate!). This actually gave me an ATR response (albeit a short one), which I let run for a while because the numbers kept changing very slightly.

3) Tried to read from card in Nag1 and got the Rom version, and "backdoor appears to be open", but errored out reading it, so more bugbusters...same result.

4) Backt to ATRresurrect, this time on 3.68..got a full ATR!

5) Ran bugbusters, sliding card in and out a few more times...bingo! Popped and reads/writes normally. Immediately wrote the original backup image of this card, and it is like it was never looped :)


1. Where Do I find ATRressurection? I am a little lost.
2. This is ROM10 I am having problem with not ROM2 I cant run Bugbuster for ROM10.

[ismarhadzia]

I found ATResureccionbeta and I ran it for long period on both frequencies but I was getting same message in ATR string window "No ATR No Card ! Test ATR Testcard" but ofcourse the card was in and the ISO programmer is fuctioning fine with other cards.

[ki55tory]

Spookk: Because it was not designed for ROM10 and you could prossibly ruin the ROM beyond repair.

[Fro66er]

Your card is most likely not looped dude........

Here's what to do. Look at your ISO programmer. and you should notice two blank spots on the circuit board right around the crystal - mine says 47pF.

When you changed to a 3.68Mhz, your crystal is a parallel resonance. This means you need the two caps that are missing on your programmer. Put in 22pF capacitors in the two spots. Then you'll be able to do ROM10/11 & just read yellows.

I thought my Yellow and 2 ROM10's were looped, untill I realized the crystal I used needed them caps. All cards were prefect - cha-ching!!!!

RadioCrap should have these caps. If you can't find 22Pf, try something between 17 and 33Pf should do the trick.

Happy programming dude.

[Fro66er]

Yellow card, read just like ROM10's, etc. Of course we can't write to them, but just doing ATR reset in NE4.0 should reveal:

Opening of COM1 was successful
ATR String: 3F FF 95 00 FF 91 81 71 A0 47 00 44 4E 41 53 50
31 30 31 20 52 65 76 30 30 37 3D
ROM Revision: 101
EEPROM Revision: Rev007
Closing of COM1 was successful

If you can read ROM3's, but get invalid ATR's with ROM10's, check your hardware, mainly the crystal and capacitors like I explained in my post below. My thinking is the newer cards are much more finicky and require exact clock frequency.

Some say ROM101 are getting closer to getting hacked or might be almost hacked. Lets hope so!