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

Root [UPDATED 8/8/12]Breath of fresh air....an update

tdm said:
Going through the init.rc from the leak....

Manager: "Hey, let's obfuscate our security crap."
Dev1: "Good idea, let's rename the binary to something innocuous."
Dev1: "Here's the new init code, all commented like we're supposed to do."
Dev2: "Looks great, commit it!"
:rolleyes:

#/* LGE_CHANGE_S [chanhun.sung@lge.com] 2012.03.17, [Security] SW Secureboot and Unlock Secureboot
# [START][20111216, inhwan.we@lge.com]
exec /sbin/wallpaper -ap
wait /sbin/wallpaper
# [END] [20111216, inhwan.we@lge.com]
#/* LGE_CHANGE_S [chanhun.sung@lge.com] 2012.03.17 */
Click to expand...

Yeah, that got brought up in the original thread from XDA as well. Here's the question thou. Would removing the binary break the kernel? I never bothered trying myself, but I doubt they would make it that simple.
 
Also, on that note, being as you got the ICS system files to boot and work with your kernel, does that mean that it'd be worth the time for someone else to tinker and get a functional ROM of that out, or would it not be worth the effort? I have Monday's off this month, with not a lot to do.
 
Neph81 said:
Also, on that note, being as you got the ICS system files to boot and work with your kernel, does that mean that it'd be worth the time for someone else to tinker and get a functional ROM of that out, or would it not be worth the effort? I have Monday's off this month, with not a lot to do.
Click to expand...
I'm sure tdm will answer that himself, but he was saying last night if he got it booting, he was thinking of trying to get it fully working and release it. ;)
 
Neph81 said:
Yeah, that got brought up in the original thread from XDA as well. Here's the question thou. Would removing the binary break the kernel? I never bothered trying myself, but I doubt they would make it that simple.
Click to expand...

Just shoot those dudes an e-mail :)
 
Neph81 said:
Yeah, that got brought up in the original thread from XDA as well. Here's the question thou. Would removing the binary break the kernel? I never bothered trying myself, but I doubt they would make it that simple.
Click to expand...

I haven't used their kernel. My kernel runs the ics leak fine. I booted with it enabled because I didn't see it until later, so I don't know if it could be removed. My guess would be yes.
 
Neph81 said:
Also, on that note, being as you got the ICS system files to boot and work with your kernel, does that mean that it'd be worth the time for someone else to tinker and get a functional ROM of that out, or would it not be worth the effort? I have Monday's off this month, with not a lot to do.
Click to expand...

Yeah that would be a fun little project for someone. Should work.
 
Cameras work with the ics leak libs.

Haven't gotten the ril/radio working though. These things in the radio log worry me:

I/PHONE ( 650): LGFeature VZWBASE

Obviously that is proprietary.

I/PHONE ( 650): Network Mode set to 8

In cm9, the network mode only seems to go to 7. So this may be a special proprietary network mode...?

D/RILJ ( 650): my featureset: VZWBASE MPDN: 1 NAI_SUPPORT: 1 poweroffdelayneed true

More proprietary stuff.

D/RIL_UiccManager( 650): Creating UiccManager

Not sure what this is, need to check, but I don't see anything offhand. Proprietary also?
 
Okay here's the latest scoop:

I got cameras working and PG got lights working. I'll make a build with these changes tonight or in the morning, and push it out as test3 (and update github).

I was unable to get the ril/radio working by just examining the radio log, so it looks like tomorrow I'm gonna need to break out strace.

If and when I can get the radio working, I think that should leave just a couple odds and ends until we're fully functional. For example, GPS will need to be tested. Can't think of much else off the top of my head, but I'm tired and frustrated lol.
 
Hey TDM, are you using the V7_05 leak or the V7_15 leaked /system for what you're currently trying to decypher? I ask because there may be updated stuff in the V7_15 which may have changed in the radio since the first leak.
 
Neph81 said:
Hey TDM, are you using the V7_05 leak or the V7_15 leaked /system for what you're currently trying to decypher? I ask because there may be updated stuff in the V7_15 which may have changed in the radio since the first leak.
Click to expand...

build.prop says:


ro.build.description=i_vzw-user 4.0.4 IMM76D 47e5065f release-keys
ro.build.fingerprint=Verizon/i_vzw/i_vzw:4.0.4/IMM76D/VS920ZV7.47e5065f:user/release-keys
ro.lge.swversion=VS920ZV7
ro.build.version.incremental=VS920ZV7.47e5065f
ro.build.date=Tue Jun 19 17:11:50 KST 2012
 
Looks like you are using the V7_15 then. V7_05 would look like this.

VS920ZV7.47d6aee9:user with Mar 25 18:17:37 KST 2012 as a build date.
 
tdm said:
Okay here's the latest scoop:

I got cameras working and PG got lights working. I'll make a build with these changes tonight or in the morning, and push it out as test3 (and update github).

I was unable to get the ril/radio working by just examining the radio log, so it looks like tomorrow I'm gonna need to break out strace.

If and when I can get the radio working, I think that should leave just a couple odds and ends until we're fully functional. For example, GPS will need to be tested. Can't think of much else off the top of my head, but I'm tired and frustrated lol.
Click to expand...
def push the camera fixes ;)

I think we're missing a init or script or something for the radios, I been trying every network type from 0 to 12 and it just kicks from cdma to gsm lol. Tho gsm seems to be working.
 
Claude485 said:
Well whoever it was who was the cause of this shit, THANKS ALOT FOR RUINING IT FOR EVERYONE!
09dh.jpg
09ht.jpg
09ax.jpg
09jh.jpg
09bh.jpg
zamz2.jpg
Click to expand...
WTF???? lol
 
PlayfulGod said:
def push the camera fixes ;)

I think we're missing a init or script or something for the radios, I been trying every network type from 0 to 12 and it just kicks from cdma to gsm lol. Tho gsm seems to be working.
Click to expand...

You answer may be in init.qcom.rc of the V7_15 kernel

service ril-daemon1 /system/bin/rild -c 1
class late_start
socket rild1 stream 660 root radio
socket rild-debug1 stream 660 radio system
user root
disabled
group radio cache inet misc audio sdcard_rw qcom_oncrpc diag

There is also a group of extra stuff in there about initializing dhcp and other bits and pieces of qualcom specific parts.
 
Neph81 said:
You answer may be in init.qcom.rc of the V7_15 kernel

service ril-daemon1 /system/bin/rild -c 1
class late_start
socket rild1 stream 660 root radio
socket rild-debug1 stream 660 radio system
user root
disabled
group radio cache inet misc audio sdcard_rw qcom_oncrpc diag

There is also a group of extra stuff in there about initializing dhcp and other bits and pieces of qualcom specific parts.
Click to expand...

I've got that in mine, it's really close to the leak scripts. No luck. I'll push what I have soon and all the devs can try debugging it.
 
tdm said:
I've got that in mine, it's really close to the leak scripts. No luck. I'll push what I have soon and all the devs can try debugging it.
Click to expand...
Sounds good. That will give me a better idea of what you guys are currently working with and I may be able to trace something.
 
You devs are saints for working on this. I know everyone on this forum has to be excited for the progress you've made. I see donations in your future.
 
Headsup to the devs:

The device and vendor repos will change name today. This is because the official product name is supposed to be i_vzw (ro.build.product=i_vzw), and the camera libs require it to be set correctly or they won't function.

Yes, I tried adding a build prop override but that just got me two conflicting ro.build.product lines. No good.

Fortunately, it's really easy to change the repo name on your build box. Just rename the two directories from VS920 to i_vzw, then use "git remote set-url ..." to change the remote name.
 
tdm said:
Headsup to the devs:

The device and vendor repos will change name today. This is because the official product name is supposed to be i_vzw (ro.build.product=i_vzw), and the camera libs require it to be set correctly or they won't function.

Yes, I tried adding a build prop override but that just got me two conflicting ro.build.product lines. No good.

Fortunately, it's really easy to change the repo name on your build box. Just rename the two directories from VS920 to i_vzw, then use "git remote set-url ..." to change the remote name.
Click to expand...
actually if you think about renaming the directories is more involved than that. Big thing is if we ever want to get CM behind it we may have to rename it again.

I do see what you're saying tho
 
You must log in or register to reply here.
Back
Top Bottom