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

Root LG Ally 2.1 Update is being RELEASED

I think we need to separate the Compiler info and the 2.1 update info into two separate threads. My $0.02.

Anyway, as soon as the update hits my wife's ally, I'll try to use UniAnd to reroot it and see what happens.

Still no update to either of my two devices as of 12:30pm EST 9/20/10
 
Ota can be rooted fyi. I just flashed recovery on it via fastboot. Didnt try androot which I suspect still works. There is another root attack too. The original method we initially used is more than likely closed.

Thanks. Also, there seems to be no clear consensus around the board... will having a custom recovery image block the OTA? If so, can we simply execute /system/etc/install-recovery.sh to restore it and get the update or is it something more complicated that is altered?

Cheers.
 
Thanks. Also, there seems to be no clear consensus around the board... will having a custom recovery image block the OTA? If so, can we simply execute /system/etc/install-recovery.sh to restore it and get the update or is it something more complicated that is altered?

Cheers.

it shouldnt.
 
Thanks. Also, there seems to be no clear consensus around the board... will having a custom recovery image block the OTA? If so, can we simply execute /system/etc/install-recovery.sh to restore it and get the update or is it something more complicated that is altered?

Cheers.

It does. Unless someone gets LG rsa key and builds that key into a recovery. If you have a custom recovery flash the VZB rom I posted. If your stock wait on ota.
 
It does. Unless someone gets LG rsa key and builds that key into a recovery. If you have a custom recovery flash the VZB rom I posted. If your stock wait on ota.

Is running install-recovery.sh not good enough?
 
Is running install-recovery.sh not good enough?

No. That isnt reliable and the ota patches files so you have to be 100% stock. If done that way and it fails to boot there will be no way to recover. If you want I have posted stock recovery and stock v8. Ultimately its your device and your risk.
 
No. That isnt reliable and the ota patches files so you have to be 100% stock. If done that way and it fails to boot there will be no way to recover. If you want I have posted stock recovery and stock v8. Ultimately its your device and your risk.

Okay, I just flashed to the rooted VZB you uploaded. Working well.
 
I could not get an OTA update from V6 to V8 with a custom recovery installed. I had flash the stock recovery and then install V6. When I finally came up it OTA'd V8.
 
I could not get an OTA update from V6 to V8 with a custom recovery installed. I had flash the stock recovery and then install V6. When I finally came up it OTA'd V8.

Using ClockworkMod Recovery, I could get the OTA but I couldn't install it... on reboot it went to CWM and failed on... something. Sorry I can't remember more. But, in any case, yes, flashing stock recovery works (it's around here on the forum somewhere...)
 
Just an experience report. I did install drellisdee's update on my phone, which was running rooted stock ROM but with custom recovery. Results:

1. BE AWARE that drellisdee's ROM removes a lot of the built-in apps. It's pretty clearly stated in the original post, but I ignored it, and found myself without ThinkFree... which was a real pain. It turns out, as I realized later, that thinkfree is present on a directory created on the SD card by the update; you can just copy it back into the /system/app directory, and you're fine. But it was a real shocker at first.

2. I'm normally pretty skeptical of stuff like this, but I'll add my report to the list of people saying the phone feel quicker. Whether that has to do with the new update, or is a side effect of have cleared the cache and just put in stuff I use more... I can't say.

3. Unfortunately, I just checked battery stats, and I do still have this 50% "time without a signal" issue. So while changes were definitely made to the radio, it did NOT correct the 50% bug.

4. Again, the software version number still says V8, despite the fact that the update definitely installed. That's too bad. Just feels messy to me, and I'll probably poke around for ways to fix that.

I did *not* wipe data before or after install as the instructions said to; but I did wipe cache before and after, and Dalvik cache before. So far, no issues... I decided it was worth the risk because, frankly, it's a tad ludicrous to ask people to wipe out data and reinstall their apps every time a new phone software update comes out.
 
Back
Top Bottom