D
ddsdavey
Newbie
Hi guys,my issue is almost identical to to another thread on this forum.
Ok,ive restored about 8 consoles ive had stored using reset glitch,i foolishly decided to change the osig of one of the consoles as i had a few Samsung drives and the consoles osig was liteon and i new this would be an issue with lt2.0.
I glitched the console approx a week ago and since then i have updated it,like a fool i am i patched the original 9199 image i dumped and wrote that back,obviously the console should be on 13955 having updated midweek so coughs up 0022. I have a 13955 image and imported my kv/config and cpu corresponds correctly,Ive tried adjusting the ldv values but i cant seem to source any info on what these should be,it went directly from 9199 to 13955 and its values at 9199 were (from top) 0,7,6,what should they be? should i change my pairing data also?
I would appreciate your input guys.
Ok,ive restored about 8 consoles ive had stored using reset glitch,i foolishly decided to change the osig of one of the consoles as i had a few Samsung drives and the consoles osig was liteon and i new this would be an issue with lt2.0.
I glitched the console approx a week ago and since then i have updated it,like a fool i am i patched the original 9199 image i dumped and wrote that back,obviously the console should be on 13955 having updated midweek so coughs up 0022. I have a 13955 image and imported my kv/config and cpu corresponds correctly,Ive tried adjusting the ldv values but i cant seem to source any info on what these should be,it went directly from 9199 to 13955 and its values at 9199 were (from top) 0,7,6,what should they be? should i change my pairing data also?
I would appreciate your input guys.