Did I Loop Card ?????????? Help

[Dr Zapola]

Went to change keys. Opened with pass word. Read ......cleaned ........loaded 102 Rev 103..........opened updated Gopherx ...........applied cod3sp4c3 blocked....write to card..........something didnt look right so I tried to read and......ATR: 3F FF 95 00 FF 91 81 71 FF 47 00 44 4E 41 53 50 31 30 32 20 52 65 76 31 30 42 15
CAM Type: ROM102 Rev10B
Provider: Unknown................tried password and........ATR: 3F FF 95 00 FF 91 81 71 FF 47 00 44 4E 41 53 50 31 30 32 20 52 65 76 31 30 42 15
CAM Type: ROM102 Rev10B
Provider: Unknown


Help its the only 102 I have.

[puzzlepad]

N2Edit 2.78 is the way to go; try it. Using Codesoace Backdoor Utility to lock card, update keys, and lock card in the future. Good advice to buy another rom102 card or fta receiver w/ a working N2 cardless autoroll fix.

[Dr Zapola]

I think I put my pointer on the wrong file and looped the card.

[stormy777]

you did'nt loop it
you have unknown provider
look @ 1st sticky in 102 section @ rookie
i have fixed 5 with that info

[bobsmith161]

its not looped see if you used glitch enabled code

[Dr Zapola]

@ 1st sticky in 102 section @ rookie ??????????????????????

glitch enabled code ?????????????????

THANX

[traylehr]

don't glitch just yet ! try reopenning the normal way for a while than when all else fails do what you have to to open it but as stormy777 said read all the avail. info. to get it back,

[Ohms]

stormy777 , why don't you post the solution here instead of trying to direct this guy to another site? Others could benefit from it here too ya know.

Dr. Zapola,
Your card has got it's codespace messed up. This is probably due to not cleaning the image before you added the blocker code. I know you said you cleaned, but the proper order is WITH the EEPROM loaded into your utility of choice, clean the codespace, then apply the blocker to the image, then write it to the card.

You said "Opened with pass word. Read ......cleaned ........loaded 102 Rev 103..........opened updated Gopherx ...........applied cod3sp4c3 blocked....write to card."

so you read the image into your utility. then you cleaned it. Then you loaded a different image you are calling "102 Rev 103". You didn't say you cleaned the codespace of that one. Reading the card and cleaning, and then overwriting the code by opening another image is a waste of time. Is that clear enough? I hope so.

Anyway..... When you patched your blocker code without cleaning what was in the utility, you probably had parts of the old code, plus the new blocker code. Unknown Provider is what happens when the codespace is not right. It's security protection built into the card.

Before you glitch, try some other things.

First, download nagramaster 3.8.1 or newer and try to do a forced write of your rev103 bin back to card. This seems to work better with an unlocker than it does with an ISO. Then try to read the card. If it reads, then program as normal. If not, then you will probably have to try to glitch into the card. This is risky. You run the risk of looping it. If the blocker code you wrote last to the card contained anti-glitch code, then YOU WILL loop it by glitching.

Try forced write with nagramaster and post back results. We can go from there.

Anyone that wants to correct or add to what I have said here, feel free. I am no expert. I'm still learning myself.

[stormy777]

1) Open Winexplorer 5.0-run Script Called No Rsp Mod _6
If You Don't Get A Good Response Check Configure/program
Perimeters And Make Sure Rec Timeout Is Set To 3000-byte
Delay Is 100 And Reset Delay Is 100
The Above Is Done With Unlocker Flashed With Nd13

Everything Below Is Done With A 3.68 Iso Programmer

2) Open Nagraedit 5.2_run D2c File Called Fixn2editbackdoor

3) Open N2edit_beta 7 And Write A Clean Virgin Rom 102 Rev 103
Bin To Your Card

Now You Have Your Provider Back And Can Program With Your
Favorite 3m And Blocker

Use @ Your Own Risk _this Has Only Been Tested By Me On Dish
With 100% Success

[stormy777]

ohm- thanks -your right
i have been around this site for a while
i was just stormy before -lost password
can't remember which e mail i had back then
so i had to re register as stormy777
just to let you all know

[fubr]

Thanks for posting this for this guy,
Ohms is mean, but he is right! :)

I hope zapola gets his shit fixed, does not sound as bad as he may think it is.

[Dr Zapola]

Thanx Stormy. I found this same resolve at 10x site. Ran it all night to no avail. But did not use settings you recomend so I will reset and try agian. Did you use any other timing settings on the atmel flashing. I used 60 5 1.



Also OHMS. Reflecting on what I did I believe I used ( mis pointed in the file) the wrong file that is used to reset the card back to 102 rev 103 befor the clean then updated Gopherx with blocker is loaded. So the card never got reset back to 102 rev 103 befor loading updated progg.

[stormy777]

doc
only thing i did'nt mention was i always
have my unlocker pot set @ 1.5 to 1.6
i have had 100% success
most of the ones i fixed were bad writes
using nagraedit 5.2
let us know if you get it going
and how you did it exactly
there are many unk provider cards
out there

[Ohms]

Thanks a lot Stormy. I do remember that name around here. I guess the 777 just means you are lucky. ;) Thanks for posting this as lots of people are getting themselves into this pickle. I fixed one last week for a guy but had to glitch it.

Questions. When you say 1.5 to 1.6, I assume you mean 1500 ohms right? What do you have the meter switch set on? x1000? what kind of unlocker are you using? Ohms vary from unlocker to unlocker.

[Ohms]

Doc,
That thing you are talking about that resets the card back to 103 is probably a EEPROM image file. If so, then your step of reading from your card is not needed. Tell me ..... Is it a patch? How do you load this file?

[stormy777]

ohms
my meter set on 20k
it reads 1.60
i use same pot settings on
a mikn2 yellow
and a lil red modded unlooper
both work well
also i just flashed the little red unlooper
with the newdrs flash
and it reads/write great with n2edit 2.58
i tryed writing a auto roll with newd13
and nagramaster and no go cause of
line 9a40 but had no problem writing
in n2edit 2.58 with newdrs flash
have a good day

[Dr Zapola]

Doc,
That thing you are talking about that resets the card back to 103 is probably a EEPROM image file. If so, then your step of reading from your card is not needed. Tell me ..... Is it a patch? How do you load this file?



Just write to card with N2. The file I use from what I understand is to bring the card back to Rev 103 from 10B because your not suposed to load Gopherx (with blocker) on 10B cuz it will not work. I loaded the wrong file then I opened the updated Gopherx and applied blocker then put it on the card. I noticed something wierd happened so I went to read and bam NO PROV..........

[stormy777]

i have a rom102 rev 103 virgin image
i always unlock card -write the virgin image to card
then i write a bin with blocker
then i make sure card will not read (locked)
seems to be the best way to do it
doc- with all these patches out its not hard
to mess something up
good luck

[Ohms]

Dr Zapola
I think you are a little confused about how N2Edit works. I could be wrong and you really do have a handle on it, but just in case, let me try to explain it anyway.

I'm going to post a "how to prevent going Unknown Provider" in a new thread. You should go and read it. I hope it helps a lot of these people that are getting into this situation.

[Dr Zapola]

i have a rom102 rev 103 virgin image
i always unlock card -write the virgin image to card
then i write a bin with blocker
then i make sure card will not read (locked)
seems to be the best way to do it
doc- with all these patches out its not hard
to mess something up
good luck


Just the way I do it storm. Like I said I think when I went to put on a virgin image I put my mouse couser on the file above my virgin image by mistake then loaded it, then loaded the new bin with blocker. It seam to take the load but went fubar just after,

[Ohms]

The file I use from what I understand is to bring the card back to Rev 103 from 10B because your not suposed to load Gopherx (with blocker) on 10B cuz it will not work.

This is a very true statement. If you PATCH the blocker over the top of ANY unclean image, you will probably get an unknown provider for your efforts. However this it talking about codespace, not what is on your card when you write a image to it.

Your file is just overwriting the card image that is on the card with a virgin image. That's all.

[Dr Zapola]

So your saying my GhoperX was unclean. OR my card was not at REV103 when I loaded GopherX

[Ohms]

I'm not 100% sure. If your GopherX is a PATCH, then the image you had in N2Edit was not cleaned to rev103 when you wrote the patch.

If your GopherX is a Image, then there is something wrong with the codespace of that image.

[Dr Zapola]

GhoperX is a public file for us dummies who cant make their own tiers with DT tier works. Some come with blocker some you patch a blocker to them befor write to card

[Ohms]

Ahhh I see. So Gopherx is either the dataspace with a cleaned to rev103 codespace, or it's also availabe as an AIO, all in one, that already has the blocker in it.

very interesting... I have never used it.

[Dr Zapola]

Ya. Check out BIG ALS Dishrom 102

[Ohms]

Ok doc... so did you fix that card yet? Or is it still Unknown Provider?

[Dr Zapola]

still Unknown Provider

[lobogobo]

I did the same thing as DR ZAPOLA. Followed you advice and got back into my card in 10 seconds. Thanks a bunch guys. I was so happy, dam near kissed the wife. I ran nagramaster 4.0 with FixN2EditBackdoorROM102.d2c and bingo.

[Ohms]

There you go Dr. Zapola. Give that a try.

[blazer]

No Rsp Mod _6 where can I find this file? what area fo down loads section?

[Dr Zapola]

Dont have FixN2EditBackdoorROM102.d2c. PM me a copy.

[Ohms]

Someone uploaded the NO RSP MOD-6 file to the file section. It's in the moderation queue at the moment, but should be available soon.

filename = "102-NO RSP MOD-6.zip"

[Dr Zapola]

I just used Provider unkown fix found at Junky and bam I was back in in seconds.

[billko]

I got unknown provider by using N2 Edit Ver 1 Beta 9 on a card with Cable Hater's cloaking blocker, which I learned too late is a non no (need to use ver 2.5 or higher).

Ohms, I followed your advice from early in this thread and tried a forced write with Nagramaster, did not help. I don't have an unlocker, anything else I can try that does not require an unlocker? If I need an unlocker, any recommendations as to which one to buy?

Dr Z, could you be more specific about the "Provider unkown fix found at Junky"? What's Junky and what's the full name of the fix?

Thanks,
b

[Ohms]

Bummer dude. Here is what I have found.
Sometimes, changing computers can give diff results.
NM 3.8.1 does a forced write better with my white nexus than my ISO.
Some ISO's will show UP when the same card in another ISO shows Dish
Don't glitch the card unless you know what is on it. If it's anti-glitch code, it WILL loop.

Which unlocker is a matter of opinion. I like the white nexus that mili sells. Be sure to do the no-loop mod to any unlocker you buy.

Try another computer and force a write with Nagramaster 3.8.1 or later.
Mess with your com port settings in windows. Set it to 115200 baud.
mess with the read byte delay. Start at 25 and add 10 each time till you get to 100.

Good luck

[seaboard18]

Bummer dude. Here is what I have found.
Sometimes, changing computers can give diff results.
NM 3.8.1 does a forced write better with my white nexus than my ISO.
Some ISO's will show UP when the same card in another ISO shows Dish
Don't glitch the card unless you know what is on it. If it's anti-glitch code, it WILL loop.

Which unlocker is a matter of opinion. I like the white nexus that mili sells. Be sure to do the no-loop mod to any unlocker you buy.

Try another computer and force a write with Nagramaster 3.8.1 or later.
Mess with your com port settings in windows. Set it to 115200 baud.
mess with the read byte delay. Start at 25 and add 10 each time till you get to 100.

Good luck

Hi Ohm's,

I thought all newer computers com ports were set to 115200 baud. I checked mine tonight and it was set to 9600! Its a good possibility that allot of testers don't know this and the ones using cemu are getting desub's and freezing issues due to the data transfer being to slow. A large number of peeps are using P4 computers and having issues. Your post was great and turned out to be a multi use post.

[smilingjack]

a lot of programs, like my dial-up requires 9600
it depend of the BIOS section

[seaboard18]

That is correct Jack but 115200 baud will work better for cemu and will not cause any problem for anything else, including dialup. You may even get lucky and get a faster connection. In this case more is better.

To check this in windows XP, go to Control Panel, System, Hardware, Device Manager, Ports... Click on Communications port and change the setting. Apply and you are done.:D

[billko]

Thanks Ohms. I set com port to 115200 baud, did not help. How do you adjust the read bite delay? Could not figure out how to do this. Will try another PC but don't have one available at the moment.

[smilingjack]

I did not charge the computer, just the INTERNET

[Ohms]

Thanks Ohms. I set com port to 115200 baud, did not help. How do you adjust the read bite delay? Could not figure out how to do this. Will try another PC but don't have one available at the moment.


In nagraMASTER 4.1, it's in the bottom right hand corner of the main screen labeled "user delay setting" right under the com port selector.

[Ohms]

To check this in windows XP, go to Control Panel, System, Hardware, Device Manager,


Or right-click on "my computer" and pick manage. There you will find many useful things like device manager and services and drive manager and logs and and and..

anyway, just check it out.

[billko]

In nagraedit 4.1, it's in the bottom right hand corner of the main screen labeled "user delay setting" right under the com port selector.

Thought we were talking about nagramaster?

[Ohms]

OOPS!!!! You are correct. I ment Nagramaster!!!!

thanks. I'll correct it above.