Sorry, I can pull it up in an IVR, but I can't get to it in Service Information.. Below is your rpo codes in case that makes you feel any better.. lol.. L76 does show up as an engine in a 2009 Silverado, not 2010 though.. Below is the power ground schematic, that has everything you should need to ge...

The guy on fb is posting some interesting reading material for the E38 on his new forum.. hopefully plugging another forum is ok here?? it's just getting started, I could post the files here, probably in another post if needed??

http://www.opensourcetuning.com

This may or may not help you, you might already have this, but someone is working on making E38 ecu tuning open source.. This is not my work, but I am definitely interested in it.. If you need/want the seed/key algo for E38 it's posted there.. I need it so few I would just grab it from a session log...

I just found this post, AMAZING WORK!!! I understand some of the gist if what your doing, but it's mostly over my head.. I do have an E38 sitting on my bench at work with a bench harness already on it, and I have a couple MDI's, so if it's something simply I can do to help you verify something, let ...

the clone's set boot primary specifies where mtd8(serialnum) starts.. at least that's what I think it's doing.. serialnum is specified to start at 16320 and is only 32k long.. macaddress starts right after.. There is room to make serial num 128k long and keep macaddress in the same location.. below ...

Looking at the file system could I assume the section in front of the mdt8 partition(serialnum) isn't used by anything else? I didn't see any reference to it in the config files.. I have been successful in simply reconfiguring the setbootargsprimary using askenv and saving it, then changing the seri...

ok.. I really have no idea what I'm, doing, but.... the test below is part of the kernel messages of a genuine MDI.. Jan 1 00:00:07 (none) user.notice kernel: cfi_cmdset_0001: Erase suspend on write enabled Jan 1 00:00:07 (none) user.debug kernel: erase region 0: offset=0x0,size=0x20000,blocks=127 J...

I'm going to keep on researching this, looks like it might be different hardware? can you even change the erase block size? lol..
edited to add.. This is from a genuine MDI where it's very easy to change the serial..

Thank you for the explanation, I kind of understand that albeit technically way over my head.. the reason I was wondering about this is that the genuine mdi let's you change the serial simply by renaming the init-testmode file to the init file and booting up in testmode.. this starts a web server an...

Has anyone yet figured out why the serialnum and madaddress partitions error out with the doesn't start on an erase block boundary -- force read-only error? I am wondering if this can be fixed easily and the ability to change the serial number using serial or by the testmode webpage can be recovered...