ARCHIVED: [DEAD ROM] LEGO-ROM-v2

[jason0777]

so sorta new at this and i didnt pay attention and installed lego rom 2 with V9 but so far not seeing any issues! Why is it that lego rom 2 is not supposed to work with V9! Sorry if i missed anything! Thanks

 

[64fairlane]

This was super easy, and explained step by step. Thank you to all who have contributed.

I have a couple simple questions that I tried searching for in the thread, but didn't seem to find the answers.

1) Can I change themes on top of each other (i.e. right now I have the ThunderROM theme installed, if I decide to try another, can I just flash right over the top of the ThunderROM theme)?

2) I see that the kernal section is empty. Is this something that I can do/add later on? If I am able to do it later, will I have to wipe the phone of all apps, data, etc.?

Thanks again! Great thread!

 

[jimismallz]

Yes you can just flash over themes, all you have to do is flashzip in recovery and reboot. When you flash a kernel later you should wipe dalvix and cache which will keep all of you apps and important info.

 

[lichan]

If I run the VC version of Lego ROM after updating to VD will the OTA pop-up continue to nag? Which Xionia kernel is suggested for overclocking? Thanks.

 

[64fairlane]

If I run the VC version of Lego ROM after updating to VD will the OTA pop-up continue to nag? Which Xionia kernel is suggested for overclocking? Thanks.

If you are referring to the Lego ROM currently linked in post #1 of this thread, I did what you are asking about yesterday, and I have not had any OTA pop-ups nagging about any updating.

 

[jason0777]

Can any one point me to a download for LEGO-ROM-v1? i am still running V9 thanks

 

[jstntp]

Can any one point me to a download for LEGO-ROM-v1? i am still running V9 thanks

LEGO-ROM.zip

Here is a copy of LEGO for V9.

 

[generosity]

VD

I've been trying to read through the threads, and it seems like people with VD are using Lego v2 without any problems. At the beginning of this thread, it said specifically that it only worked with the VC baseband. I have VD; can I use this ROM normally, or might it cause problems? If there might be problems, will there be a VD-based version (as with ThundeROM), or would I need to somehow downgrade to VC?

Also, I noticed the "Email has EAS bypass" in the changelog. Is that referring to the exchanged-enforced lockscreen? Being able to bypass that would by itself make this ROM a winner!

Thanks so much!
N

 

[KSmithInNY]

I've been trying to read through the threads, and it seems like people with VD are using Lego v2 without any problems. At the beginning of this thread, it said specifically that it only worked with the VC baseband. I have VD; can I use this ROM normally, or might it cause problems? If there might be problems, will there be a VD-based version (as with ThundeROM), or would I need to somehow downgrade to VC?

Also, I noticed the "Email has EAS bypass" in the changelog. Is that referring to the exchanged-enforced lockscreen? Being able to bypass that would by itself make this ROM a winner!

Thanks so much!
N

You can run it on VD. Will have an update to VD base soon also.

Yes EAS bypass means the forced security policy is ignored. The phone tells the server it is complying (response = true) but the phone is actually ignoring the request. No lock screen

 

[generosity]

You can run it on VD. Will have an update to VD base soon also.

Yes EAS bypass means the forced security policy is ignored. The phone tells the server it is complying (response = true) but the phone is actually ignoring the request. No lock screen

I have Lego v2 working, it is fantastic! One problem though, I can't seem to bypass the Outlook EAS. When I create the account, it still forces me to add it as an account administrator, and afterwards makes me set the screenlock pin. If I back out and don't set the pin, it refuses to sync. Am I missing something?

Thanks
n

 

[KSmithInNY]

I have Lego v2 working, it is fantastic! One problem though, I can't seem to bypass the Outlook EAS. When I create the account, it still forces me to add it as an account administrator, and afterwards makes me set the screenlock pin. If I back out and don't set the pin, it refuses to sync. Am I missing something?

Thanks
n

Nope, just checked and looks like it was missed in V2. Will be done in V3 but for now you can flash ThundeROM 1.8 which the bypass is working.

 

[lichan]

Started getting the VD OTA nag so I updated to VD via the LG tool on VC ThundeROM 1.7 and then upgraded to ThundeROM 1.8 which stopped the OTA nag. TR 1.8 just wasn't my cup of tea so I switched to Lego ROM v2 but I immediately started getting the VD OTA nag again as Lego v2 shows Android 2.2.1, baseband LS670MV9_6040, Build number ZVC and SW version LS670ZVD. I'll try some of the VC fixes and hope for Lego v3. Thanks all who provide us free development and support.

 

[64fairlane]

When the next version of Lego ROM (v. 3?) comes out, will I be required to wipe everything and lose my apps, settings, etc.?

I am new to all this, and from what I understand (correct me if I am wrong), when you change to a different ROM, you must wipe everything (Wipe data/factory, Wipe cache, and wipe Dalvik cache).

Does the same go for upgrading versions of the same ROM?

Thanks!

 

[64fairlane]

Started getting the VD OTA nag so I updated to VD via the LG tool on VC ThundeROM 1.7 and then upgraded to ThundeROM 1.8 which stopped the OTA nag. TR 1.8 just wasn't my cup of tea so I switched to Lego ROM v2 but I immediately started getting the VD OTA nag again as Lego v2 shows Android 2.2.1, baseband LS670MV9_6040, Build number ZVC and SW version LS670ZVD. I'll try some of the VC fixes and hope for Lego v3. Thanks all who provide us free development and support.

I started getting the OTA nag as well on Lego ROM v2 on one of my phones (but strangely on the other phone I don't get the nag). Can you tell me where I can find more info about these "VC fixes" that you referred to in your post.

Thanks!

EDIT:

Try hitting the more info tab then pull the battery trick and see if that works. It did with vc.

Is this a trick that might work? Or was this person referring to something else?

EDIT 2: It seems like what sonicbluemustang suggested worked (at least for now). I could always make the OTA update nag come up if I switched into roam only, then switched back to Sprint network. I did this, and when the nag came up I hit "more info." After the more info screen came up, I pulled the battery. I am now unable to get the OTA update nag to come up. Hopefully this did the trick. If it begins happening again, I will update in this thread.

EDIT 3: It has been a day and a half and there has not been a single OTA update nag!

 

[jt_mcg]

Hi, just checking in on optimus roms for a friend who's new enough to android.

One thing you may want to try in your stagefright enabled build props is set media.stagefright.enable-http=true to false, it's fixed problems with green/pink lines in youtube and other video issues on 2.2 roms for different phones I've worked on.

 

[KSmithInNY]

Hi, just checking in on optimus roms for a friend who's new enough to android.

One thing you may want to try in your stagefright enabled build props is set media.stagefright.enable-http=true to false, it's fixed problems with green/pink lines in youtube and other video issues on 2.2 roms for different phones I've worked on.

It fixes the pink line by disabling http streaming which then breaks npr and shoutcast which essentially means you've broken the only reason you'd even want to enable stagefright.

 

[jt_mcg]

Hmm, Apoligies. I don't own an Optimus, so I obviously wasn't able to test, but NPR worked on my android 2.2 phone with http streaming disabled.

Stagefright's bugs and decoding obviously present themselves and affect different devices differently.

Looks like nice work you've done here, keep it up.

 

[lichan]

I started getting the OTA nag as well on Lego ROM v2 on one of my phones (but strangely on the other phone I don't get the nag). Can you tell me where I can find more info about these "VC fixes" that you referred to in your post.

Thanks!

EDIT:

Is this a trick that might work? Or was this person referring to something else?

EDIT2: It seems like what sonicbluemustang suggested worked (at least for now). I could always make the OTA update nag come up if I switched into roam only, then switched back to Sprint network. I did this, and when the nag came up I hit "more info." After the more info screen came up, I pulled the battery. I am now unable to get the OTA update nag to come up. Hopefully this did the trick. If it begins happening again, I will update in this thread.

Yes the battery pull after "more info" is the quickest/easiest. There is also an edit you can make to your build.prop file and an update file or apk that you can rename to disable it. I haven't searched through the threads for the exact steps of the last two. Strangely, the OTA hasn't popped up since last night but if it does I'll do the "more info" trick while awaiting Lego V3.

 

[itony]

Nope, just checked and looks like it was missed in V2. Will be done in V3 but for now you can flash ThundeROM 1.8 which the bypass is working.

yes v3 please! just wondering if it will be more soonish or will it be a little while? and how's work on the kernals going?

hope all is going well!

 

[generosity]

LED Substitute

Just a thought that might be included in v3: due to the lack of led notification lights on this phone, a lot of people have suggested using the button backlights on the 4 main buttons as notification lights. There are hacked solutions to do this (use a screen-flashing notification app, set the flash duration very small so that the screen does not have enough time to turn on) but it would be awesome to have the option of just using the button backlights for notifications built in.
Thanks
n