[=v=] DOMINATE YOUR LG-OPTIMUS-L9-P769 - \m/ (>_<) \m/

xxx

i can not help those who see no need for help. good luck with life. thread closed.

xxx

as much as @omgbossis21 doesn't like getting excited: this device can be unlocked over usb.

because i can't get gcc to compile, due to a configuration problem there is a lack of documentation for, i decided to do a quick bit of research into i2c.

http://en.wikipedia.org/wiki/I²C
http://www.robot-electronics.co.uk/htm/usb_i2c_tech.htm
http://svn.peeklinux.com/trunk/peek-build/m23/csw-system/drv_app/i2c/i2c_hw_functions.h

those tools that @LaDY Vengeance linked to may be using the same method (see, i told you they might help some one in the future ).

i opened a hex editor and created a binary file to send instructions over usb, and haven't gotten it to work so far, but, i've never written to a usb socket/tty before, either...

i think the slave register's (OMAP_I2C_SA_REG) address offset is 0x0b or 0xac, depending on which struct is being used (neither of which make since, if they are 16-pin registers, the address of the 2nd register should be 0x10, which i HAVE seen in code, but, i2c.h suggests differently). the internal address SHOULD be 0x00 0x00, since it's an instruction, and not a reference to a data payload in memory, and the byte length SHOULD be 0x02, and the data payload, or, "command", itself, is 0xaa 0xdc. i don't know what the BASE memory offset would be, if any, and, i don't know if there is a protocol setup required, or, if it is accepted raw data as instructions/payload. perhaps a more experienced systems programmer might know how to put all that together to create a hack.

the unlock hack may end up being some thing like:

and the contents of hack should be in instruction format, which should look some thing like this:

but i2c.h defined the I2C_FUNC_SMBUS_WRITE_WORD_DATA command to be 0x00400000, so, it COULD be like this:

okay, i'm in over my head with this stuff... i'm going to get back to the "easy" way, of trying to compile a damned u-boot... if i can get gcc to resolve my damned path...

omgbossis21 said:

So this rom your compiling from source (without x and u partition source) is gonna unlock the bootloader on second install? By installing a ported Loki image? By a modified x and/or u partition with the LG signature that you cracked (nope). Because you found a Backdoor in to omaps secure storage(doubt it)? BC you found a way to set the unlock flag or efuse and will only share it via your rom? Lets not hype people up, if you actually do it just release it. If you come across important info and wanna share please do.

Click to expand...

Click to collapse

1: no trolling
2: read the thread
3: if you know some thing i don't know, please share, as every one else is doing

now, in case you missed it, or, didn't catch what my intentions were, i found the place in the code where the bootloader gets unlocked. i don't know how to write it into a c-binary that can access the kernel on a rooted phone, nor a java apk, AND, we NEED a newer STOCK rom any way, so, i'm just going to compile a new stock rom, with the bootloader hack in it. as far as "signing" it, i assume since it's LGs source code, it will have the tools in it to sign each image, or, it will be bootable because the build process has tools for signing it. it should end up like the v20b that @cyanogen prepared for LG. this should be the pretty much same as the previous "b" rom, just, updated for the 769s, and with the bootloader hack in it. if you don't think this can be done, then tell me why. don't just "troll", try "helping" instead.