• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ClockWorkMod

slutyman said:
can someone help me root with the one click root i have teamviewer
Click to expand...

Lol, yes, I tried to connect to you last night and it wouldn't go through. Did you cancel out of it?

Text me at 417-483-9194. Ive found thaf its easier to get a time set up that way.
 
ktb83 said:
I wholeheartedly appreciate and agree with your perspective and reasoning. And here I thought I was irritated by some of these posts!

I think it's safe to say that you otherwise have little personal stake or need in having a custom recovery for this particular phone.

Thank you for sticking it out with this BS. Take your time.

I'm not made of money, but I'm certainly willing to chip in even more to make up the remainder.

Thanks again,
KTB
Click to expand...

drewwalton1921 said:
Thanks, good to know I wasn't the only one! :)
Click to expand...

Ditto... I echo was KTB has stated... Thanks for taking the time to do this for the LG Elite community. I hope others will donate to you for the time and effort that you put forth in making this happen.
 
Is there someway we can find where and how the checksum is ran so we can change it or patch it to not work anymore? Anyway we can create a "virus" to prevent it solely from doing so? Haha xD I really can't wait for this. I am too scared to even try anything so all I can do to help is spit out ideas. Can we figure out a way to change the checksum of our custom recovery to match the one that our phone searches for? Idk what checksum means or w/e so once again; Just spitting out ideas lol. >.<
 
HaTrEd360 said:
Is there someway we can find where and how the checksum is ran so we can change it or patch it to not work anymore? Anyway we can create a "virus" to prevent it solely from doing so? Haha xD I really can't wait for this. I am too scared to even try anything so all I can do to help is spit out ideas. Can we figure out a way to change the checksum of our custom recovery to match the one that our phone searches for? Idk what checksum means or w/e so once again; Just spitting out ideas lol. >.<
Click to expand...


drew is creating borg nano-probes as we speak ....
 
HaTrEd360 said:
Is there someway we can find where and how the checksum is ran so we can change it or patch it to not work anymore? Anyway we can create a "virus" to prevent it solely from doing so? Haha xD I really can't wait for this. I am too scared to even try anything so all I can do to help is spit out ideas. Can we figure out a way to change the checksum of our custom recovery to match the one that our phone searches for? Idk what checksum means or w/e so once again; Just spitting out ideas lol. >.<
Click to expand...

You need to learn what "checksum" means first. You can't just change the checksum of a file, and the checksum is probably in the bootloader somewhere, which will make this process even more difficult.



Curtis1973 said:
drew is creating borg nano-probes as we speak ....
Click to expand...

Haha that image is awesome!
 
HaTrEd360 said:
Wait exactly what is he doing?? And what is that pic showing?? I can't see it on my phone.
Click to expand...

Well, by very definition he is using a recursive algorithm that calls itself on the nth term in order to terminate the base foundation that is troubling us in this programmable construct!

It's a poultry dilemma really...:rolleyes:

Ok in all seriousness it was just a joke picture just for fun I believe.
 
Hasn't it been confirmed already that we can update to the v5 update and it will replace the recovery partition along with all the other changes, and then we can flash the whole v4 tot and not be bricked? I was thinking that maybe they stuck the checksum somewhere in the nv items and updated it during the process. But if that was the case, downgrading by flashing the tot wouldn't work.

Also, what happens when you have everything stock v4 and only try to load the stock v5 recovery (or even the other way around)? If that fails, then it would point to a checksum being somewhere else. But if that succeeds, then it points to something being signed in the recovery partition.
 
well im just a lowly windows computer repair tech lol..my knowledge of linux,etc etc...is highly limited at this time. checksums,you that sort of thing lol. so ill kindly remove myself from this part of the discussion...to watch and learn.
 
HaTrEd360 said:
Wait exactly what is he doing?? And what is that pic showing?? I can't see it on my phone.
Click to expand...

It's a Star Trek reference and the "shopped" photo includes an old version of ClockworkMod running on our phone (I think).


giantpune said:
Hasn't it been confirmed already that we can update to the v5 update and it will replace the recovery partition along with all the other changes, and then we can flash the whole v4 tot and not be bricked?
Click to expand...
Yes.

giantpune said:
I was thinking that maybe they stuck the checksum somewhere in the nv items and updated it during the process. But if that was the case, downgrading by flashing the tot wouldn't work.

Also, what happens when you have everything stock v4 and only try to load the stock v5 recovery (or even the other way around)?
Click to expand...
I haven't tried, but why not give it a shot.

giantpune said:
If that fails, then it would point to a checksum being somewhere else. But if that succeeds, then it points to something being signed in the recovery partition.
Click to expand...


IIRC, the ZV5 update makes changes to the system, radio, boot and recovery partitions and updates the bootloader partition(s) as well. So, it makes sense to me that a checksum feature would be located in a bootloader partition.

In case somebody would like to confirm updated bootloader partitions by comparing them to the ZV4 versions, here are their SHA-1 checksums in ZV5:

mmcblk0p1 5F5DF6D2918295F58CA56C53ED27A199F42D96A3
mmcblk0p2 B9550FBE2925137EDD1B7149EF5C8A46D093BAAC

I did check the strings we identified as possible SHA-1 hashes in the boot and recovery partitions (blocks 240-253) against SHA-1 checksums of portions and the entirety of the boot and recovery partitions. I also checked for those values in partitions 1 and 2. No matches.

I tried changing that possible SHA-1 hash value at the same offset in a CWM build to the value from the ZV5 recovery. I also edited the first 2048 blocks in the CWM build so that it matched the ZV5 recovery. I still had bootloops.

In case someone knows more, what exactly does the fastboot oem unlock command accomplish on our phone?

I know one of us has tried the oem unlock command, and it didn't seem to change anything (it didn't seem to wipe everything as indicated in what I've read from various sources).

"The explanation to this question is really simple. If you want root, you&#8217;d be wanting to flash Custom ROM post-root, and if you want to install a Custom ROM, you&#8217;d need to have your stock bootloader unlocked. In simple terms Unlocking the bootloader allows you to install custom Firmware on your Android phone.

Warning: Unlocking your phone&#8217;s bootloader voids its warranty. It also completely wipes (formats) your Android phone&#8217;s internal memory including applications, contacts, SMS and MMS messages etc."
 
The way it is in the base android code, they do something like input the kernel data, the kernel size, then the ramfs data, then the ramfs size to get that sha1. LG may have modified the way the hash is calculated by rearranging the order that the data is entered, or including something like "my super sekrit key" into the hashed data.

EDIT:
Well, that's a no for that idea. I calculated the sha1 with the algorithm from mkbootimg.c and I get the same values as what were in the header.
 
Yes, the recovery will take time. But you wont believe how unbelievably awesome the recovery he is building for it is (unless you have had the OV or OS and used it). Its loosely based on CWM, but very very loosely.
 
You must log in or register to reply here.
Back
Top Bottom