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

Root [GUIDE] FroYo 2.2.1 for Root Users! (Updated 3/3/2011 at 3:40 pm EST - NOW EASIER THAN EVER!)

I seem to have caused my phone to be in an infinite loop of crashes. After a short while, the phone keeps saying that android.process.media and android.process.acore have stopped responding, and need to be closed. Whether or not I close them, the phone eventually crashes, and reboots back to the ANDROID screen. Any ideas? :(

Jump in the IRC room for some help, noone will be able to help very easily without context of what point in the process the force closes are occurring.
 
Upvote 0
I'm preparing to run this guide, and getting the files set up on my notebook which runs WinXP SP3.

Step 9 of the guide says:

9. Install the LG Android Drivers (located in froyo_root_tools.zip\LG Android Drivers)

The file that I found in that location is named:

"LGAndroidDriver_WHQL_ML_Ver_1.0_All_Win7.exe"

Does this indicate the file is ONLY for Windows 7, or that it is for "All" Windows versions INCLUDING Windows 7?

I should point out that the Ally has never had any problem connecting to this notebook, and it is what I use to access the files on the Ally's SD card (unless I need to access its EXT partition), "side load" non-Market Android Apps, and also use the Ally sometimes to connect with EasyTether on this notebook. So I am not certain any additional USB drivers would be needed anyway. But I would like to know the answer before I go any further.
 
Upvote 0
I'm preparing to run this guide, and getting the files set up on my notebook which runs WinXP SP3.

Step 9 of the guide says:

9. Install the LG Android Drivers (located in froyo_root_tools.zip\LG Android Drivers)

The file that I found in that location is named:

"LGAndroidDriver_WHQL_ML_Ver_1.0_All_Win7.exe"

Does this indicate the file is ONLY for Windows 7, or that it is for "All" Windows versions INCLUDING Windows 7?

I should point out that the Ally has never had any problem connecting to this notebook, and it is what I use to access the files on the Ally's SD card (unless I need to access its EXT partition), "side load" non-Market Android Apps, and also use the Ally sometimes to connect with EasyTether on this notebook. So I am not certain any additional USB drivers would be needed anyway. But I would like to know the answer before I go any further.

its not the same driver. you need the one in the google sdk. the other driver is for pc/modem connection if im not mistaken.
 
Upvote 0
Thanks for the reply, but I was still confused over which driver to use, because the guide specifically says to get it in the location above, and there is only the one file there. So I went to the LG website and looked up the Android Drivers. Right under the one that I mentioned above it says

"Ally Android USB Drivers for WinXP, Vista, and Win7"

So I have to think this driver I mentioned above is the correct one. I'll install it and proceed with the operation.
 
Upvote 0
Ok, so i keep getting stuck at 20... instead of "ADB Bootloader Device" it says "ADB Interface" and if i expand that, it says "Android Sooner Single ADB Interface". And, when i try applying the next steps (Updating driver) it doesn't even show the "android_winusb.inf" file in the navigation window... pleaaase respond.. i really need help.. :(
 
Upvote 0
The quickest way to get help with this guide is to visit the AllyIRC chat room and ask for help. I think there is a link to it in the guide post at the top of this thread. It can get a bit hectic in there sometimes, but patience and courtesy will get someone to help you eventually. Dots, Trident, Drellisdee, and Savoxis are some of the most helpful I have met but many others will help too.
 
Upvote 0
Ok, so i keep getting stuck at 20... instead of "ADB Bootloader Device" it says "ADB Interface" and if i expand that, it says "Android Sooner Single ADB Interface". And, when i try applying the next steps (Updating driver) it doesn't even show the "android_winusb.inf" file in the navigation window... pleaaase respond.. i really need help.. :(

did you download the driver pack from the repositories? if you did it should be there..
 
Upvote 0
16. When prompted for the version, type "VS740ZV6_01" and then press enter.

17. It should now load the familiar LG Manual Updater screen with a log window below and start reading information from your phone. It will proceed to flash your device.

When I entered step 16 as above and pressed enter, it then asked:

Version (SW Version) (Ex:V10G_04)

The guide, as you can see above, does not mention this step. So what should be entered here? Do I put in "VS740" or "VS740ZV6" or just "ZV6" or what? :thinking:
 
Upvote 0
When I entered step 16 as above and pressed enter, it then asked:



The guide, as you can see above, does not mention this step. So what should be entered here? Do I put in "VS740" or "VS740ZV6" or just "ZV6" or what? :thinking:


Im pretty sure its VS740 then VS740ZV6_01.cab then VS740ZV6_01 Its all in the guide im sure. Id double check im on my phone so i cant.

Edit *this would be after selecting option "j"
 
Upvote 0
Says Problem with communication between cell phone and PC I've installed the drivers from the Froyo root package and to no avail. If someone could point me in the right direction it would be greatly appreciated...

Also here is the log, I don't know if it will help with my question though
I am getting similar error when i try to update to 2.2. Any help would be appreciated. Thanks
 
Upvote 0
I am getting similar error when i try to update to 2.2. Any help would be appreciated. Thanks

One thing I can suggest is that you make sure the USB cable you are using is connected directly between the phone and a USB port on the PC. I had been using the desktop docking cradle LG sells for the Ally, connected through a USB hub, and it kept disconnecting from my PC while in the process of backing up my SD card to my PC (before I started the guide). I had to stop using the cradle and the hub and plug directly into each end as above. If this had happened while trying to run the guide, especially during the "do not disconnect the cable" part of the LG Mobile Updater, very bad things could have happened.

I was able to work through this guide last night, but not without a lot of help from Ally IRC members providing corrections and missing information. It took me about 4 hours because of all the side-tracking I had to do to make things work, and verifying that some of the strange things I was seeing on the computer screen were "normal" (like that the LG Mobile Updater screen is full of question marks and a lot of garbled text while it is working - it looks like a complete train wreck while running, but it worked). So I suggest if you get stuck, go to the Ally IRC. It is the quickest way to get answers when you are left hanging in the middle of this operation.

One other piece of info which might apply for you. After I installed the adb drivers, my WinXP Home SP3 notebook I used for the process insisted on rebooting to make adb work. I left the phone connected. But it screwed up the ability for the command line adb access to work. D2A helped me reset that after the notebook rebooted. I had to unplug the USB cable from the phone and issue an adb kill-server command. That restarted adb when I plugged the phone back in, and it worked after that.

One more grief-saver. Now that Froyo is being pushed OTA, step 27 forcing the manual update to Froyo is no longer needed (the tricky one with the timing of pressing the Home key). Just do one more CHECKIN dial sequence (after you have VZC) and the system update notification for Froyo will appear, so you can open the notifications window and tell it to download the update (I think it was 53.2 MB). Thanks to Dots for pointing that out to me! :)

I hope this info helps.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones