[GUIDE] FroYo 2.2.1 for Root Users! (Updated 3/3/2011 at 3:40 pm EST - NOW EASIER THAN EVER!)
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if you point the
* finger at me for messing up your device, I will laugh at you.
*/
Quote:
Originally Posted by getitnowmarketing
We are not able to flash radio on ally currently with ra or with clock work ( I built the newest 3.0+ clockwork recovery to try). Fastboot doesnt do it either (errors). If it comes back success its a placebo from recovery and doesnt actually flash it. Anyone that had a phone SHIPPED with software newer than VS740ZV06 will need to downgrade. Its on upc label if still there under bin version what you have shipped. Downgrade is to be done via LGMU to ZV06 to get and keep root with fastboot enabled bootloader after taking the ota and ones in the future. Do not do the LGMU Updater method to froyo as you will lose the bootloader.
Work around for this is being looked into with no success yet.
Only ZV06 shipped or downgraded to ZV06 will have fastboot bootloader as bootloader is NOT changed via ota.
Do not discuss any LGMU expoits either as they are already being closed on other devices and can be expected to be closed in the future.
Added : If you are unsure shipped version downgrade to be sure.
Full instructions to root ota with ZV06's bootloader will be posted soon.
Here's those instructions:
-At this time, this guide is only possible by using either Windows XP or Windows 7 (32bit or 64bit) operating systems.
-Download all files indicated in red, and double check that all folders and files are in place.
-Make sure to read the entire guide before starting Step 1!
3. Connect your USB cable to your Ally and enable USB Debugging (Settings>Applications>Enable USB Debugging)
4. Run C:\Froyo\LGVS740\KP500-Utils-En.exe in compatibility mode for Windows XP SP2 and as an Administrator. (Only if you are not running Windows XP)
5. Choose option J
6. When prompted for phone model number, type "VS740" and then press enter
7. When prompted for the cab file, type "VS740ZV6_01.cab" and then press enter (you do not need to specify the location of the cab file)
8. When prompted for the version, type "VS740ZV6_01" and then press enter.
9. 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.
If your firewall warns you about trying to access the internet, allow it.
Your phone will now load a screen that displays the LG and Verizon Wireless logos and says: DOWNLOADING! DO NOT UNPLUG!
At this point, it is now flashing the update to your phone. This normally takes around 20 minutes to complete. Once complete, your phone will automatically reboot.
10. RUN C:\Froyo\ADB.bat
DEVICE MANAGER WILL OPEN AUTOMATICALLY
11. Expand "ADB Bootloader Device" (Might be listed as "Android!" Under Other Devices)
12. Right click and choose "Update Driver or Install Driver"
13. Select "I will choose driver to install"
14. Navigate to where the Android USB drivers are (eg: C:\android-sdk-windows\google-usb_driver) (If file or directory doesn't exist see Step 2).
15. Choose "android_winusb.inf" and accept that this is an unsigned driver it should notify you that the driver was successfully updated.
-It also may state that it can't find suitable driver, if it does simply state you will look yourself and choose "Single ADB Boote Loader" or the like.
16. We handle the rest!
Congratulations! You have now successfully updated to Froyo 2.2.1 with a custom recovery and root access! Aren't you proud of yourself?
For everyone that still has fastboot (this is pretty much anyone running a 2.1 custom rom as well as a few others) savoxis has made a fully automated magical wonder flasher! There are both a windows and linux version:
Open a Terminal and navigate to the extracted dir (eg cd /home/penguins/Downloads/Froyo/)
Type sudo sh froyo.sh
These tools where made with simplicity in mind, make sure with the tux variant that you run the script as root, you do this by using sudo before the command (in ubuntu) on other distros you can just su before running
On some distros you may need to set permissions for the script (tux only) do this (as root) by typing chmod +X ./froyo.sh (assuming you are in a terminal in the same directory) Most of you shouldnt need to do this.
Credits:
- Original method and revisions by Trident.
- Automation and revisions by savoxis.
- Much time and work went into making this possible. Please support your developers!
Device(s): Nexus 4, Nexus 7 (Retired: Galaxy Nexus, DX2, DInc 2, DInc, LG Ally)
Carrier: T-Mobile
Thanks: 6,249
Thanked 2,404 Times in 1,446 Posts
I'm working on it now
Thank you, thank you, thank you.
That is all.
EDIT: Seems you have to rename the update.zip file.
I know it's not in the instructions but i got into recovery and was going to apply update.zip, but it said no such directory found, meaning it doesn't recognize the OTA name as update.zip
Last edited by jmar; January 22nd, 2011 at 03:00 AM.
Reason: cos i think it may help
Can I follow these instructions if I am currently running Velocity .4? My baseband version reads VS740MV7.5210.1013 and right now clockwork recovery is flashed. Thanks. If all goes well I will be donating.
Trident, there are a few issues:
#15 should be cd C:\android-sdk-windows\platform-tools (credit: AfterAffekt)
After #15: Open SDK and go to Available Packages>Google Inc>Google USB Driver Package
Before #17: Windows 7 users: Upon entering fastboot and letting Windows choose your USB driver you must click on the update and choose SKIP WINDOWS UPDATE
Vista/XP users: Open the containing folder that has the new google drivers (e.g. google-usb-driver) and find android_winusb.inf
#23 you need to move the contents of \platform tools into the \tools folder (just so AdbWinApi.dll is in the directory)
after #28 you should have a disclaimer to not let your phone boot. immediately pull the battery or hold the button combination right away
That's about it only 4 hours to complete too!
Last edited by lomar24; January 22nd, 2011 at 05:41 AM.
The Following User Says Thank You to lomar24 For This Useful Post:
If I've already applied the Froyo update via LGMU can I go back and do this? I don't want to brick another phone 'cause I don't think they will send me another one.
When I tried to install superuser, it said it couldn't verify. So I toggled verification, then it installed correctly. For those of you who have problems with it.
The Following 5 Users Say Thank You to lightningdude For This Useful Post:
Still kinda new to all this, I am currently running the Punisher ROM on my Ally, if I follow the instructions above, what ROM will actually be installed on my Ally?
EDIT: Seems you have to rename the update.zip file.
I know it's not in the instructions but i got into recovery and was going to apply update.zip, but it said no such directory found, meaning it doesn't recognize the OTA name as update.zip
Hmm.. it shouldn't need to be renamed. Anyone else have this issue?
Quote:
Originally Posted by iceman1110
Can I follow these instructions if I am currently running Velocity .4? My baseband version reads VS740MV7.5210.1013 and right now clockwork recovery is flashed. Thanks. If all goes well I will be donating.
Yes, you can. You can follow these instructions over any ROM.
Quote:
Originally Posted by yohobojo
Is it worth it to get froyo rite now or should i w8 for roms to com out?
Might as well go ahead and prepare.. you MUST follow these instructions in order to use FroYo ROMs.
Quote:
Originally Posted by socobandit
To clarify....up until youre at zvc vdersion, it's the same as the old way to flash v06 and recovery right?
Yes, you are correct.
Quote:
Originally Posted by shane_is_the_man
Still kinda new to all this, I am currently running the Punisher ROM on my Ally, if I follow the instructions above, what ROM will actually be installed on my Ally?
The stock ROM FroYo ROM will be installed to your device. Then you will go through the process of rooting your device.
Last edited by Trident; January 22nd, 2011 at 08:06 AM.
Still kinda new to all this, I am currently running the Punisher ROM on my Ally, if I follow the instructions above, what ROM will actually be installed on my Ally?
Trident, there are a few issues:
#15 should be cd C:\android-sdk-windows\platform-tools (credit: AfterAffekt)
After #15: Open SDK and go to Available Packages>Google Inc>Google USB Driver Package
Before #17: Windows 7 users: Upon entering fastboot and letting Windows choose your USB driver you must click on the update and choose SKIP WINDOWS UPDATE
Vista/XP users: Open the containing folder that has the new google drivers (e.g. google-usb-driver) and find android_winusb.inf
#23 you need to move the contents of \platform tools into the \tools folder (just so AdbWinApi.dll is in the directory)
after #28 you should have a disclaimer to not let your phone boot. immediately pull the battery or hold the button combination right away
Same question; but if i have 2.2.1 with custom rec and su, do i have the same end result? Or Should i restore stock nand and perform this proceedure.
Well fastboot is broken for you. So if your recovery image every becomes corrupt and you loose root for whatever reason, you're SOL. You should be fine for now though.
So all this is to have 2.2 rooted with fastboot enabled? Is fast boot that important cuz ive never had to use it that i know of...
Or will devs be using fastboot for 2.2 custom roms or something?
Last edited by tron101; January 22nd, 2011 at 09:45 AM.
Device(s): Sony Ericsson Xperia Play
Rooted, unlocked Bootloader
Running CM9 with Calls & Data
(ICS 4.0.x)
Carrier: Not Provided
Thanks: 66
Thanked 109 Times in 71 Posts
Well, we were told to wait, so it will be only at the mercy of the ROM Gods that we get a solution. I currently have Froyo running with Amon Ra Recovery and am rooted with the correct SU in place, but no bootloader. Now what can I do to resolve that in order to use future ROMs? I, too, don't want to run the risk of killing my phone again. Death@All110 spent hours restoring it to life.
I think the question that really needs answered is: can we flash a stock Nandroid at this stage and go back and do it right?
__________________
~ Android... because anything less would probably be an iPhone.
Last edited by netizenmt; January 22nd, 2011 at 10:05 AM.
Do I go straight from 2.1-update 1, running velocity .4, vs640vz8, vs740mv7.5210.1013 to this 2.2.1? or is there something I have to update in order to follow these steps. I have rom manager and clockwork, unsure if I have fastboot. I lack the knowledge about fastboot and how to use it. Thanks in advance for any information.
Last edited by Cjohn8792; January 22nd, 2011 at 11:02 AM.
so, if I'm correct, on my wife's rooted ally, i can skip right to step 28? No factory reset is done, right? she got mad when i did something and she had to reset all her ringtones, email, etc.
Well fastboot is broken for you. So if your recovery image every becomes corrupt and you loose root for whatever reason, you're SOL. You should be fine for now though.
Would it be better then to restore and have fastboot for the future? Will it be necessary for any ROMS that may come along?
I have the same issue with the inf opening as a window of script in Firefox, whats the best way to save it? sorry about the stupid question
Right click the link and "Save file as..." or the equivalent.
The file may save as a .txt file. You have to enable Windows to show file extensions in order to take out the .txt extension and leave it with .inf
To enable Windows 7 & Vista to show file extensions, do this: In the folder where the android_winusb.inf.txt file is saved, click on Organize and then click "Folder and search options", go to the "View" tab, and uncheck "Hide extentions for known file types" and click Apply and OK. You will notice the file is now named android_winusb.inf.txt - simply right click -> Rename and remove the .txt from the name and click OK on the warning popup.
Last edited by d0nd0n; January 22nd, 2011 at 11:04 AM.
The Following User Says Thank You to d0nd0n For This Useful Post:
Device(s): Sony Ericsson Xperia Play
Rooted, unlocked Bootloader
Running CM9 with Calls & Data
(ICS 4.0.x)
Carrier: Not Provided
Thanks: 66
Thanked 109 Times in 71 Posts
Quote:
Originally Posted by socobandit
so, if I'm correct, on my wife's rooted ally, i can skip right to step 28? No factory reset is done, right? she got mad when i did something and she had to reset all her ringtones, email, etc.
so this will only work for those of us who did NOT update with LGMU to 2.2.1 already, correct? I tried it and LGMU for this method stated an error and wouldn't flash back to stock....
Update:
It says specifically: Updating is not possible any longer due to a fatal error while the LG Mobile Phone Software Update.
Last edited by phillk6751; January 22nd, 2011 at 11:40 AM.
If I've already applied the Froyo update via LGMU can I go back and do this? I don't want to brick another phone 'cause I don't think they will send me another one.
Yes, this works. I was abe to do this but if I had to do it over again,I would not have applied the LGMU first. Thanks to the devs for developing this solution. Donation to follow...
Device(s): Samsung DROID Charge TW3@K3D 2.2 ; Samsung Fascinate; LG Ally running on bacon
Carrier: Not Provided
Thanks: 53
Thanked 42 Times in 31 Posts
Quote:
Originally Posted by bnitty
will this mess up my SD card at all? i have tons of pics on there i don't want deleted.
I would highly recommend you back up your SD card to your computer if you have important stuff. You never know when the SD can fail or phone get stolen or dropped in water.
so i'm all official with 2.2.1 and a working SU but amonra wont stick. i got clockwork to stay but i can only use amonra once...after a reboot from recovery it reverts to stock. confirm clockword sticks cos i rebooted 7 times to make sure. clockwork, for now
so this will only work for those of us who did NOT update with LGMU to 2.2.1 already, correct? I tried it and LGMU for this method stated an error and wouldn't flash back to stock....
Update:
It says specifically: Updating is not possible any longer due to a fatal error while the LG Mobile Phone Software Update.
This is simply not true. I used LGMU to 2.2.1, and flashed back to ZV6, then flashed a nandroid (when I had ZVC), then wiped data, cache, Dalvik-Cache, flashed velocity .4
I'm going to do this, but want to clarify something. If i'm not a fan of the way Froyo runs on my Ally, is it still possible to flash a backup copy of my Eclair setup? I've heard the bootloader is changed with the Froyo update and going backwards may not be possible. I want to make sure I can go back because i'm helping someone with something.
Device(s): Samsung DROID Charge TW3@K3D 2.2 ; Samsung Fascinate; LG Ally running on bacon
Carrier: Not Provided
Thanks: 53
Thanked 42 Times in 31 Posts
Quote:
Originally Posted by flyinjoe13
I'm going to do this, but want to clarify something. If i'm not a fan of the way Froyo runs on my Ally, is it still possible to flash a backup copy of my Eclair setup? I've heard the bootloader is changed with the Froyo update and going backwards may not be possible. I want to make sure I can go back because i'm helping someone with something.
Afaik once you go froyo you can't go back.
The Following User Says Thank You to Goonie21 For This Useful Post:
Device(s): Nexus 4, Nexus 7 (Retired: Galaxy Nexus, DX2, DInc 2, DInc, LG Ally)
Carrier: T-Mobile
Thanks: 6,249
Thanked 2,404 Times in 1,446 Posts
Quote:
Originally Posted by xtcvapor
This is simply not true. I used LGMU to 2.2.1, and flashed back to ZV6, then flashed a nandroid (when I had ZVC), then wiped data, cache, Dalvik-Cache, flashed velocity .4
Yes you can do all this. But in order to get 2.2.1 with root and recovery you have to start at v6 and follow all the steps. you will not be able to flash a froyo rom without doing this method.