01-19-2013, 08:37 AM (This post was last modified: 01-19-2013, 08:39 AM by kasar.)
this is how my descriptor looks, I didnt had to modify anything because I did before like doing what TW said to the whole chip dump at the descriptor part
I already modded the ME region access bits, I just let the GBE unmodded since TW said there was no GBE region at all on my machine.
the problem is that I cant edit the ME firmware itself, not the flash access (read/write) to the ME ^^
now I want to mod my ME image to support overclocking, and be able to rebuild the image and reintegrate it back at the ROM image by paste the hex part ^^
Posts: 397
Threads: 1
Joined: Nov 2011
Reputation:
23
01-19-2013, 08:46 AM (This post was last modified: 01-19-2013, 08:50 AM by jkbuha.)
Yes - but can you do the following:
1. Dump ME from fptw
2. Open ME using FITC
3. Change CPU type from CPU menu as per method described on rog forum (I don't have access to proper Internet/laptop ATM) as this will enable overclocking/undervolt
4. Save modded ME
5. Flash ME using fptw
I had described how to I think around page 58...
Posts: 523
Threads: 0
Joined: Aug 2011
Reputation:
23
01-19-2013, 10:36 AM (This post was last modified: 01-19-2013, 10:39 AM by kasar.)
yeah, that was exactly was I was trying ^^
however, I got stuck at the step 4 (Save modded ME), because FITC cant save my current ME, ,I keep getting errors.
that is why I was waiting input from TW, he seemed able to reasembly my ME version changes.
I remember I also flashed the modded ME from TW long time ago via fptw, but it caused a big brick, I suspect fptw messed up some regions and made the system unbotable. (glad I had a whole chip backup ^^)
thats why I want to try to reintegrate manually the ME firmware into the chip image at this time.
but first, I have to be able to mod and save the ME with FITC ^^
Posts: 19
Threads: 1
Joined: Dec 2012
Reputation:
6
well, each ME firmware have its own information and adjustments over each chipset I think, so it would be need to be a laptop with the same chipset and hardware.
however, those laptop firmwares can be used to analize it and take them as examples to mod the firmware from the laptop to be modded.
this is what is basically explained at this topic:
Hey, guys. Sorry for my lack of inactivity :| Have been polishing my OSX experience regarding touchpad and battery, thanks to @Rehamman over at tonymac.
@kasar regarding your dump .. I have attempted to mod some values but it doesn't save for me either, I have no idea how I managed to export it back then, when we first tried the cross-flashing or ME v8. To be absolutely hoest with you I didn't do anything special back then but just followed how ME was configured for that Alienware x-something machine, or was it Dell anyway ..? You know what I'm referring to, the thread called "Let's unlock bladi-bla". I will try to reiterate the steps I did then to see if it will end up exporting properly and not moaning on some errors.
@jkbuha I have finally tried your VBIOS 2158 that you had posted a while ago, needless to say it didn't work very well for my machine. I lost brightness control and like @ashp (in Acer thread) mentioned the display seemed noticeably dimmer than usual. Man, I just absolutely hate Dell for doing this to their customers..
You can read more about how crappy Dell's SCT is by reading from here and on the following page.
Posts: 523
Threads: 0
Joined: Aug 2011
Reputation:
23
01-21-2013, 09:42 AM (This post was last modified: 01-21-2013, 10:25 AM by kasar.)
(01-21-2013, 06:43 AM)TimeWalker Wrote: Hey, guys. Sorry for my lack of inactivity :| Have been polishing my OSX experience regarding touchpad and battery, thanks to @Rehamman over at tonymac.
@kasar regarding your dump .. I have attempted to mod some values but it doesn't save for me either, I have no idea how I managed to export it back then, when we first tried the cross-flashing or ME v8. To be absolutely hoest with you I didn't do anything special back then but just followed how ME was configured for that Alienware x-something machine, or was it Dell anyway ..? You know what I'm referring to, the thread called "Let's unlock bladi-bla". I will try to reiterate the steps I did then to see if it will end up exporting properly and not moaning on some errors.
np mate
mmm, do you remember what firmware you modded? the one you extracted from my whole chip image? or the one I got via fptw64 ?
curius notes:
fptw64 version 7.1 does not detect my chip and cant dumpt it, but the 8.1 version does!
FITC 8.1 cant open my ME image, give error, but the version 7.1 can open and read all the parameters perfectly ^^ (however it fail while saving it)
another posibility would be to create a completly new ME image from 0, but checking exactly all the parameters from mine, by reading it, do you think that will work?
edit, I attached the ME image extracted by FPTW64, I think that was the one you sucesfully modded.
I found another tool with the intel tools package, but not sure what it does
Available options:
/v0 - Verbose level 0 (default mode, smallest amount of information).
/v1 - Verbose level 1 (debug). Includes raw HECI messaging.
Available commands:
gl - Get Lock
rr - Read ICC Register
wr - Write ICC Register
gr - Get ICC Record
gcc - Get ICC Clocks Capabilities
gcdr - Get Clock Range Definition Record
sl - Set Lock
sce - Set Clock Enables
gp - Get ICC Profile
sp - Set ICC Profile
rrd - Read all dynamic ICC Registers
wuob - Write UOB Record
smr - Read Single ICC Register via SMBUS
smw - Write Single ICC Register via SMBUS
To get help on specific command, use "cctWin.exe command ?"
mmm, this seems also to have the ability to write registers, but I dont know what to change exactly, what do you think guys?
some more parameters I got
Available selectors:
intel - Intel Record
oem - OEM Record
perm - Permanent UOB Record
temp - Temporary UOB Record
preuob - Platform Boot Time Record Pre UOB
postuob - Platform Boot Time Record Post UOB
current - Current Record
01-21-2013, 10:56 AM (This post was last modified: 01-21-2013, 06:06 PM by kasar.)
oh, I forgot to attach the tool ^^
here is it, it also have a PDF file with some ussage help and stuff, it also talk about more hardware required and a required DLL to take be able to use the SMbus feature (however the app worked fine to output those results without aditional HW or DLL in my case, however it obiusly ask for the dll file and extra hardware & test machine while trying the smbus commands)
Posts: 523
Threads: 0
Joined: Aug 2011
Reputation:
23