View Full Version : Rev 108 "unknown provider"
kalhua
08-10-2006, 04:18 AM
I am trying to figure out the proper settings for use with my newly purchased white nexus. I have searched the forums but have been unable to determine what is working best.
Should I use a script or Mr Ultimate?
What settings do I need to know for script?
What is the best voltage?
What is the ohm reading I am looking for?
If I am getting frequenrt resets while glitching how do I spread them out?
How long should I let a script run?
Is there anything else I need to know?
Thanks in advance for any info you may provide!
Crazy1_79
08-10-2006, 04:44 AM
is the card provider unknown because it was programmed before? If it is fresh from the stream then it should be provider unknown, however I have seen that happen when resetting it with a loader in N2edit with newd13 instead of newdrs. go to the top of this forum, I have a sticky with a modified script I tweaked just for the higher revs. all the variables you ask about are mentioned I believe. 12 volt power supply is what I use, dips 2 and 5 down, 700 ohms at the pot.
kalhua
08-10-2006, 04:49 AM
Thanks
kalhua
08-10-2006, 04:58 AM
Let the 102 Glitching continue....
AVR delay = 1B
Glitch Delay = 3803
VCC = 02
RX Data :
-
RX Data : Increasing AVR delay to 1C
-
RX Data : -
RX Data : -
RX Data : -
RX Data : -
RX Data : Increasing AVR delay to 1D
-
RX Data : -
RX Data : -
RX Data : -
RX Data : -
RX Data : Increasing AVR delay to 1E
-
RX Data : -
RX Data : -
RX Data : -
RX Data : -
RX Data : Increasing AVR delay to 1F
-
RX Data : -
RX Data : -
Trapofmind
08-10-2006, 08:29 AM
If it is fresh from the stream then it should be provider unknown, however I have seen that happen when resetting it with a loader in N2edit with newd13 instead of newdrs.
Your scripts are to be used with Newd13 right?
Crazy1_79
08-10-2006, 08:31 AM
yes
Crazy1_79
08-10-2006, 08:32 AM
Let the 102 Glitching continue....
AVR delay = 1B
Glitch Delay = 3803
VCC = 02
RX Data :
-
RX Data : Increasing AVR delay to 1C
-
RX Data : -
RX Data : -
RX Data : -
RX Data : -
RX Data : Increasing AVR delay to 1D
-
RX Data : -
RX Data : -
RX Data : -
RX Data : -
RX Data : Increasing AVR delay to 1E
-
RX Data : -
RX Data : -
RX Data : -
RX Data : -
RX Data : Increasing AVR delay to 1F
-
RX Data : -
RX Data : -
Stop the script. what rev is that? that is not good return for at all. something isn't right.
kalhua
08-10-2006, 02:14 PM
REV 108 Good Atr, says unknown provider, card history unknown
kalhua
08-11-2006, 03:49 AM
Any more suggestions?
Trapofmind
08-11-2006, 04:26 AM
This seems to be a common problem right now: Cards with good ATR but unable to be read, saying provider unknown and only receiving resets from glitching.
I have researched it at great length and have found no fix. It seems like one of those things we have to wait for the uberGeeks to figure out.
kalhua
08-12-2006, 05:06 PM
Well nothing seems to work. Dont know if it is card or white nexus. I still get either fast resets or nothing. I have tried 170-2200 ohms. Is there any settings in winexplorer that need to be verified further?
Thanks
gooding
08-13-2006, 12:26 AM
Might try Rebelserf Fooker Unlooper ror rev 107 or higher Its for soft looped cams . Worth a shot . uses Newd 14 comes with NewdRs with file . Give that a shot --hehe--:)
udntcme
08-13-2006, 12:38 AM
I'll tell you what will work for sure...But you may not have the loader needed..Script...rebel stuborn-fix....Mik3 modded with a 25-OHM pot....here is the period......more period's.......eh...hehehe...all the best...I had two unknown provider's don't remember the rev's but as long as it's spoofed or orig subbed (not rev 9) It took about 60 sec's for the first and 29 sec's for the second....I have not seen any post's with this type of quick open that were useing something else ...could be wrong but this mik3 modded with 25 ohm pot is "the witch's tit's"...hehehe . wish I had a rev 108 to be sure...anybody try this with the above setup.....?
gooding
08-15-2006, 10:39 PM
Guys the unknown provider is on purpose. Data space pointer is set to BF BF. After you read your eeprom you can easly fix this by just manually changing $30C0 to A7 for D*shnet. On B*v verify where you dataspace begins and change $30C0 to match.
D*sh data space starts at $A700 and ends at $BFFF so dataspace pointer at $30C0 is A7 BF. So if you Glitch a rev 106 to rev 108 Unkown Most likely will happen This is how you fix it --hehe--If you can read the cam you can fix it ! :)
kalhua
08-16-2006, 02:26 PM
I would love to try your fix however the card is locked and nothing seems to work to unlock it.
vBulletin® v3.8.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.