New 3.7 byte location

[large1]

dont work 4 me either

[MIKEDATA]

Hi..ok i have tryed all of the above and the best i can do is i only can get the frist 6 bytes of the bk the rest i only get Zero's this was useing ocd and bke 2.1 and 2.2 also try this with and with out feed with and with out card in i just get the same ex-cw 41042.......i will have have to look into this abit more i think....lol.....fookers......lol.....THE FUNS STARTS

regs
MIKEDATA

[ronster]

As it seems some peeps are having problems with this byte address i'll recheck it tomorrow as things may of changed since last july!!
Dont forget when using OCD you must add the 8 at the end.

BYTE 0x008FFE38 8

Sorry cant advise on SDT & BKE as never use them!

[MIKEDATA]

Originally Posted by ronster

As it seems some peeps are having problems with this byte address i'll recheck it tomorrow as things may of changed since last july!!
Dont forget when using OCD you must add the 8 at the end.

BYTE 0x008FFE38 8

Sorry cant advise on SDT & BKE as never use them!

Hi Ronster....well i have tryed them all and with 8 on the end of the new byte addy....it may have worked a few days ago but vm as beem updateing like mad over the last few days.....


regs
MIKEDATA

[ronster]

Ive been at this fooker all day,yes the byte location has changed....again
The IRD AND BK are now at 00928271
Red is your ird and Blue is your BK
eg 00928271: 00 00 00 12 34 56 78 ab cd ef gh 12 34 56 78

New byte address is

BYTE 0x00928271 15

This is using OCD commander, ive not tried it on SDT or BKE but assume its the same without the 15 at the end

This is CW byte only

Ronster

[bidwell]

No good with bke still all zeros for bk grrrrr !!!!!!

[MIKEDATA]

Hi Ronster....just a update here for you..ok on 3.7 netid 41042 with the new bytes from your hard work and by the way thank you....the byte gave me all Zero's and i said fook fook...lol so what i did was to put a new netid by ocd which was 41045 and the box updated to that netid i then want on to retry your bytes in ocd and it gave me 00 00 00 then the ird then the bk so done the batt thing and did a funcard to reset the netid to my netid and fook it would not reset the box so after trying loads of ways i just reset the netid with ocd and then did a mosc card and fook me it work....so my guess now is that once you have gone to 3.7 you cannot use the funcard way anymore and have to set the netid by ocd and of coause this will only work on 2100 and prob pace 4000...so there you have it i now have a sammy 2100 up and runnig from your hard work and by you posting the the byte's so once again thanks Ronster....this sammy will only last untill N3 comes.......lol....

regs
MIKEDATA

[MIKEDATA]

Hi....just in caes anyone out there cannot set there netid by funcard anymore its becasue your netid 1.7 will not work on the new update 3.7 the new netid hex v1.8 By SunRise WILL this as been tested and works 100% on the 3.7 so i would just like to thank SunRise for letting me post it as i know he is so busy these day.....well done...WHAT A GUY!!!

regs
MIKEDATA


Attachment removed -- added to Download Section..

[khan]

hi all
at start of this thread it was mentioned to use OCD FLASH PROGRAMMER.
I have downloaded the soft ware. got it running.

1. i can get to target the flash from 00000000 to 0fffffff.
2. i can view it.

question is for any1 using the proggy.

how do i save the targeted flash.

help please.

on pure 3.7

[paul001]

Originally Posted by ronster

Ive been at this fooker all day,yes the byte location has changed....again
The IRD AND BK are now at 00928271
Red is your ird and Blue is your BK
eg 00928271: 00 00 00 12 34 56 78 ab cd ef gh 12 34 56 78

New byte address is

BYTE 0x00928271 15

This is using OCD commander, ive not tried it on SDT or BKE but assume its the same without the 15 at the end

This is CW byte only

Ronster

Do you have the bytes for pure tried the following:0x00895934

0x00927fa8 0x00902aa4 0x00895934 8. No luck.

Box is Sammy 2100c in pure