This is an off shoot of my original CWM recovery thread. I'm not going to re-write what I added to my original post, I'm just going to start off from where I was at.
I have made great progress with our own CWM (to a point) since my 11/02 update. I have managed to get our memory blocks mapped out so recovery knows where to look for everything. This will make it possible to retrieve all the different files we need for a true backup. Doing this has been a real pain as LG managed to leave some very useful commands out of ROM and I've had to learn some work arounds.
I figured out how to decompile "recovery.img" to get to the guts. Also, I have found the mis-directed recovery points in "recovery.fstab" that cause our current CWM not to work 100% and attempted to correct them.
I have also figured out how to recompile the "img" with the correct changes.
At this point things go horribly wrong. I don't know if I mucked up my recompile, address changes or both but I am now the proud owner of a brick.
It boots and goes straight to recovery but you can't get out of it. No way, no how! Even the trick I used to force a new recovery install when the old 3.0 recovery went sour doesn't work.
Guess I'll be going back to BB in the AM to try to get an exchange on the 28th day of my 30 day grace period.
If anyone else wants to try figure out where I went wrong, I will gladly share what little I know.
I have made great progress with our own CWM (to a point) since my 11/02 update. I have managed to get our memory blocks mapped out so recovery knows where to look for everything. This will make it possible to retrieve all the different files we need for a true backup. Doing this has been a real pain as LG managed to leave some very useful commands out of ROM and I've had to learn some work arounds.
I figured out how to decompile "recovery.img" to get to the guts. Also, I have found the mis-directed recovery points in "recovery.fstab" that cause our current CWM not to work 100% and attempted to correct them.
I have also figured out how to recompile the "img" with the correct changes.
At this point things go horribly wrong. I don't know if I mucked up my recompile, address changes or both but I am now the proud owner of a brick.
It boots and goes straight to recovery but you can't get out of it. No way, no how! Even the trick I used to force a new recovery install when the old 3.0 recovery went sour doesn't work.
Guess I'll be going back to BB in the AM to try to get an exchange on the 28th day of my 30 day grace period.
If anyone else wants to try figure out where I went wrong, I will gladly share what little I know.