OFFICIAL: update.zip is finally here! :D - Droid Incredible General

Ladies and gentlemen, if you are getting impatient on waiting to get your scoop of FroYo...this is NOT the RUU, so it will not wipe any memory off your phone...PLEASE READ EVERYTHING CAREFULLY BEFORE YOU BEGIN!
Quick Note: While one of the great things about the update.zip is that you are not required to clear your memory...i have found from personal experience that your phone will run much smoother by doing a factory reset(much like it would by wiping your hard drive on the computer). This has nothing to do with the update.zip....people who recieved the OTA from Verizon have also reported lots of bugs with updating.
First off, ensure that you have the Stock 2.1 ROM with first OTA, it WILL NOT work otherwise.
software/Build version will read as the following: 1.22.605.2...if it is 1.22.605.0, the update wont work...please go here to update it http://forum.xda-developers.com/showthread.php?p=7933281#post7933281
Directions:
-Drop the update.zip provided at the bottom of the page on to the Root of your SD card.(Just to clarify the "root" of your sd card means you just drag and drop the file to your SD card. DO NOT put it in any folders!)
- Turn your phone off.
- Press and hold the Volume Down and Power at the same time to boot into HBOOT.
-
When the white HBOOT screen appears, use the volume button to move down to “RECOVERY.”
- Press the Power button to select “RECOVERY.”
- When the triangle and exclamation appears, hold the Volume Up and Power button at the same time.
- Using the volume button, scroll down to “apply sdcard:update.zip” and select it.
-Your phone should update now, but it will take some time
enjoy your FroYo everyone ...and a very special thanks to teslatech at Android Central for pulling the .zip from his phone
Update.zip here....http://www.4shared.com/file/aI_WeWN7/update.html
Or here...http://www.megaupload.com/?d=6MC4BIEG
All issues should be resolved at this point...PLEASE REPORT IF YOU HAVE ANY OTHER ISSUES!
EDIT:>>>>>>>>Youur Baseband should read as followed to perform this update....1.00.03.04.06...if it doesnt please follow this link to downgrade your phone to stock Android 2.1 http://androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html <<<<<<<<<<<<<<
Follow this link for rooting directions AFTER you install the update.zip ...http://www.droid-life.com/2010/09/07/unrevoked-3-2-drops-1-click-root-for-2-2-on-droid-incredible/

Better link:
http://android.clients.google.com/p...on_WWE_3.21.605.1_1.22.605.2_release_sign.zip

Berzerker7 said:
Better link:
http://android.clients.google.com/p...on_WWE_3.21.605.1_1.22.605.2_release_sign.zip
Click to expand...
Click to collapse
thankyou, i wasnt sure how to make a link for it...but either way...i want everyone to thank him, lol...i was just complaining to someone else right before him about not putting the update up. So he is our savior

The assumption is that you download, rename as update.zip, place in your sdcard root and then go to recovery?

krelvinaz said:
The assumption is that you download, rename as update.zip, place in your sdcard root and then go to recovery?
Click to expand...
Click to collapse
Im not completely sure yet...we are trying to figure that out over at android central...dont worry, i will have everything sorted out shortly

Yes, that's all that's required, rename to update.zip, apply this.
Make sure you're software version is 1.22.605.2 before you apply this update. If you installed the OTA from a couple months ago, you should be fine.

If anyone still doubted the RUU was not the same as the OTA, it is. I've compared all the files which aren't patch files and they are identical matches.

rmk40 said:
If anyone still doubted the RUU was not the same as the OTA, it is. I've compared all the files which aren't patch files and they are identical matches.
Click to expand...
Click to collapse
I never said it wasnt, did i?...some of us dont want to use the RUU, cuz it wipes the memory off the phone...the update.zip doesnt..and we have been scrambling for days to get it

Copied to update.zip on the sdcard, went to recovery.... just sits there with black device and red triangle !
Been about 5 mins, nothing further, no indication it saw anything.

schwartzman93 said:
I never said it wasnt, did i?...some of us dont want to use the RUU, cuz it wipes the memory off the phone...the update.zip doesnt..and we have been scrambling for days to get it
Click to expand...
Click to collapse
If it sounded like I was downing getting the update.zip, sorry about that. That was not my intention. Thanks for getting it to us.
I was just pointing out for the folks who still thought it was different that I've done an MD5 comparison and they're identical.

krelvinaz said:
Copied to update.zip on the sdcard, went to recovery.... just sits there with black device and red triangle !
Been about 5 mins, nothing further, no indication it saw anything.
Click to expand...
Click to collapse
Press volume up + power button, which brings up the recovery menu. Then apply update.zip.

krelvinaz said:
Copied to update.zip on the sdcard, went to recovery.... just sits there with black device and red triangle !
Been about 5 mins, nothing further, no indication it saw anything.
Click to expand...
Click to collapse
yea, same here...we are trying to figure it out over at android central...sorry i posted this thread up...i just got so gitty...we will have it figured out asap though

rmk40 said:
Press volume up + power button, which brings up the recovery menu. Then apply update.zip.
Click to expand...
Click to collapse
thanks. but the update failed.
E: Can't open /cache/recovery/command
-- Install from sdcard...
verifying update package...
installing update...
Verifying current system...
asser failed: very long string
E: Error in /sdcard/update.zip
(Status 7)
Installation Aborted

krelvinaz said:
thanks. but the update failed.
E: Can't open /cache/recovery/command
-- Install from sdcard...
verifying update package...
installing update...
Verifying current system...
asser failed: very long string
E: Error in /sdcard/update.zip
(Status 7)
Installation Aborted
Click to expand...
Click to collapse
we are trying our best...im sorry for prematurely posting this up...as you can see i changed the title in hopes that someone can help

I'm total noobe and probably should hold my tongue but what of you rename to the proper pb...img.z
ip? I forget the numbers for the incredible.
Sent from my ADR6300 using XDA App

krelvinaz said:
thanks. but the update failed.
E: Can't open /cache/recovery/command
-- Install from sdcard...
verifying update package...
installing update...
Verifying current system...
asser failed: very long string
E: Error in /sdcard/update.zip
(Status 7)
Installation Aborted
Click to expand...
Click to collapse
The assert error indicates there is something on the phone configuration it doesn't like. It is not because the download file failed. that succeeded and matched the correct checksum's. Confirmed this with Unrevoked on IRC.
Just in case someone else gets this.
looks like I will use the RUU update instead. Will do it from work since I only have Win7 here.

marcmarshall said:
I'm total noobe and probably should hold my tongue but what of you rename to the proper pb...img.z
ip? I forget the numbers for the incredible.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i have successfully got it working under update.zip...i will post up a new thread shortly
....but can someone tell me how to delete this one?

Intriguing
Alright so after playing round a bit I've had some interesting luck.
After downloading the file I renamed it to update.zip, placed it within the root of my sd card and proceeded to turn the phone off.
After entering Hboot ( Volume Down + Power ) I launched recovery.
At the recovery screen the phone with a red triangle, I did Volume up + Power to bring up the recovery options and chose Apply update : sd card
It took a few minutes to load, asked me to select reboot from menu. Loaded the 2.2 splash and I now have froyo.
My question is, Couldn't this be done from clockwork as well as there is an SD update from there as well?

Hack.Me said:
Alright so after playing round a bit I've had some interesting luck.
After downloading the file I renamed it to update.zip, placed it within the root of my sd card and proceeded to turn the phone off.
After entering Hboot ( Volume Down + Power ) I launched recovery.
At the recovery screen the phone with a red triangle, I did Volume up + Power to bring up the recovery options and chose Apply update : sd card
It took a few minutes to load, asked me to select reboot from menu. Loaded the 2.2 splash and I now have froyo.
My question is, Couldn't this be done from clockwork as well as there is an SD update from there as well?
Click to expand...
Click to collapse
Unfortunately...im the wrong person to ask, lol...im not good when it comes to rooting

Reason I ask is because it could potentially save a lot of time and effort on the peoples part of having to return to stock etc.... assuming they are running the correct version and baseband pre update. But then again, the update could perhaps check to ensure the stock recovery is in place before hand. Had I not just have updated I would try it myself.
Perhaps we could find a guinea pig to try updating via clockwork...

Related

Manually install the OTA update (2.1-update1) (stock/non-rooted)

Dont see this posted before...Mods please merge with any existing thread as you see fit.
If youre like me and want to install the update RIGHT NOW, then there are instructions at:
http://androidnetwork.org/forum/viewtopic.php?f=62&t=209
Download this file:
[link removed. please follow the original link above]
Then save on to your sd card, not in any folders, and rename it update.zip (windows users just rename it update, the .zip will come by itself)
1) Turn off your phone.
2) Turn on by holding down Power and the Trackball
3)Select Bootloader (Selection instructions on the top of screen)
4)Select recovery
5)An Android-Bot will come standing next to an open box
6)Press down Power and Volume Up
7)Select apply update.zip
8) Enjoy!
Click to expand...
Click to collapse
+
Only thing differnet was that on step 5, I got the android robot standing next to an "Exclamation mark in a triangle" (caution) icon. Simply pressed Power and Volume Up and got the option to install the update. click on update.zip. The phone will restart once and you will see the android outside a box, dont press anything.
Installed fine.]
Heres a thread in the Dev section:
http://forum.xda-developers.com/showthread.php?t=627533
Test results:
-Found that the total internal (app) memory is still 196MB and RAM is still 212MB, makes sense as the kernel is still .29, Have to wait for the next update I guess.
-No problems with any existing apps. (I did an Astro backup earlier anyway). Phone works fine too. (ATT EDGE)
-Multi touch works fine in the Maps app
-Looks like the Launcher2 FC bug is fixed, I could not reproduce the bug. (does not mean I'm leaving Home++ though )
Code:
Firmware version: 2.1-update1
Baseband version: 32.24.00.22U_4.03.00.21_2
Kernel Version: 2.6.29.01117-g4bc62c2
Build Number: ERE27
Thank You! Worked perfectly!
Worked great, thanks a lot! Does anyone know where to find the full changelog of this update? I can't seem to find one for the life of me. :s Thanks.
I didn't find one either.
Signature Verification Failed
I have a rooted Nexus One but no custom ROM installed on it. I pushed the Cyanogen Browser to gain Multi-Touch before the update came out. I downloaded the correct file and changed the name to update.zip on the top level of my SD card. I go into the booloader, then go to recovery, i get the android standing next to the exclamation mark and hit the buttom combination required. I select the update through SD card option and it starts then gives me a "signature verification failed" message. Any clue as to what I could do to apply the update?
ChrisM0678 said:
I have a rooted Nexus One but no custom ROM installed on it. I pushed the Cyanogen Browser to gain Multi-Touch before the update came out. I downloaded the correct file and changed the name to update.zip on the top level of my SD card. I go into the booloader, then go to recovery, i get the android standing next to the exclamation mark and hit the buttom combination required. I select the update through SD card option and it starts then gives me a "signature verification failed" message. Any clue as to what I could do to apply the update?
Click to expand...
Click to collapse
There are many threads in the dev section dealing with rooted phones.
http://forum.xda-developers.com/forumdisplay.php?f=559
I've updated this topic title to indicate its for stock ROMS only.
I get the same error with a brand new phone.
britoso said:
There are many threads in the dev section dealing with rooted phones.
http://forum.xda-developers.com/forumdisplay.php?f=559
I've updated this topic title to indicate its for stock ROMS only.
Click to expand...
Click to collapse
You seemed to indicate that his phone was rooted because he got that error. I have the same exact error and my phone is hours old with no root. Any suggestions?
Thanks
I have the same error, I can't seem to get the update installed.
alphonz said:
I have the same error, I can't seem to get the update installed.
Click to expand...
Click to collapse
Did you get the file from http://androidnetwork.org/forum/viewtopic.php?f=62&t=209 ?
Thats the one that I used.

Froyo 2.2 Verification failed

Im having the worst time in the world trying to get this froyo for my evo. I have it in the root of the sd card, "O:" and removed known file extensions just to make sure its update.zip and not update.zip.zip.
everything is what it should be according to every post ive looked at. Yet no matter what I do, i still get signature verification failed, installation aborted.
Any ideas?!
I could the same thing last night. But what I had to do was to update to 1.47 then go in and update it another time name the file update and that is it. And it should work.
Sent from my PC36100 using XDA App
This is how it's done.
Follow the step by step directions I copied from androidpolice below. When you get to step 8, you will most likely see the red triangle with exclamation point. Don't worry. Just hold the up volume button and press the power key. This will activate the menu where you will see "apply update.zip". Proceed with step 8. It takes care of the rest.
We’ve provided some simple instructions for installing the update:
1. Download the update file and rename it to update.zip.
Note #1: DO NOT UNZIP THIS FILE
Note #2: Make sure you didn’t rename this to update.zip.zip by accident, if your Windows is configured to not show file extensions.
2. Place in the root of your SD card (connect via USB and mount as a drive, transfer via bluetooth, download directly on the phone – pick your poison).
3. Reboot into recovery mode (hold the Volume Up button while your phone is booting).
4. You will be presented with the boot loader. The Volume Up/Down buttons navigate the menu, and the Power button selects.
Note: you may see the red exclamation (!) point at this stage. Try mashing the up/down/power buttons and wait for 10-15 seconds. The recovery should eventually come up.
5. Select Bootloader.
6. Scroll down to Recovery and select it.
7. The phone will reboot again, this time into recovery.
8. Select “apply update.zip” or “install from .zip” (depending on your recovery image).
9. The installation process will take 15-20 minutes and a few reboots.
10. Enjoy!
i can get to that point just fine, its the install that fails due to signature verification failure, i have followed all the steps to prevent any mishaps, but still cannot get past it.
I think I had the same issue with the file after I renamed it update.zip (it was hidden and already there). I renamed it but did not help.
I would recommend deleting it from the card and downloading a fresh copy of the update. Copy it to the SD card and try again.
This is the source I used and it worked.
herehttp://www.megaupload.com/?d=LCONCXF1
xcodesterox said:
i can get to that point just fine, its the install that fails due to signature verification failure, i have followed all the steps to prevent any mishaps, but still cannot get past it.
Click to expand...
Click to collapse
You are probably going to need to download a different file, as a lot of the mirrors here are corrupted. If your file size is 70 something, that is corrupt. The correct file size is 80 something (sorry, I'm on my phone).
Look for a different mirror to download from.
Did everything and nothing, not even the (!) thing, everytime I scroll down to recovery it just takes me back to the main menu (bootloader) and nothing seems to work, am I doing something wrong?
yeah ive only downloaded the 84mb ones, i even had the original from HTC with no results. my evo refuses to evolve lol
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
fsuwade said:
I could the same thing last night. But what I had to do was to update to 1.47 then go in and update it another time name the file update and that is it. And it should work.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Im Hoping thats what the case is, I'm installing 1.47 now, if this doesnt work then im at a loss
well, no luck. i guess i have to wait till the 3rd
I had to remove all the excess files from my sd card root for it to finally work correctly. I think the only thing i had left on my sd card root were folders and the froyo renamed to update.zip
If you are rooted why not boot into recovery and install update from zip. Note that this option will un-root your phone in the process. There are also post on the forum with the stock Rom for non rooted phones, if you are not rooted. You can try using that file rather than the one you got. This may get u on 2.2 b4 u know it.
http://WWW.rootznculture.com
Kornsaq said:
I had to remove all the excess files from my sd card root for it to finally work correctly. I think the only thing i had left on my sd card root were folders and the froyo renamed to update.zip
Click to expand...
Click to collapse
I have many folders and I cleaned up the excess files, still though, no result.
thanks for the tip though, i got really excited to try that,.
jahnile said:
If you are rooted why not boot into recovery and install update from zip. Note that this option will un-root your phone in the process. There are also post on the forum with the stock Rom for non rooted phones, if you are not rooted. You can try using that file rather than the one you got. This may get u on 2.2 b4 u know it.
http://WWW.rootznculture.com
Click to expand...
Click to collapse
Im rooted, i tried being rooted, and unrooted. Ive been going at it since it released when i was at the movies.
thanks for the tip
Same problem
Hey xcodesterox.
I had the exact same issue and even download the linked file from ckombo.
I was finally able to get it to work.
What was happening for me was, I would download the file and my Mac is set to unzip a downloaded file from Safari, I would then just zip it myself after this. This was not working so I switched to Firefox, where I do not have it set to autoextract, and therefore I did not have to re-zip. THAT time it worked.
I hope you had the same issue.
Ok so you said right now you are in rooted. You should try removing all zip files that are current on the root of your SD card. U can back it up to your pc. Then use the file/ method found in this post. http://forum.xda-developers.com/showthread.php?t=740319
http://WWW.rootznculture.com
1:42am day two and im finally enjoying my fozen yogurt.
if anyone cares, i had to use the rooted version of this update, so its still a mystery as to why it wouldnt install. thanks for everything
I had some problems workign so i did this
1.did factory reset(backup date)
2.did the ruu 1.47 update
3.copy zip file to sd (drag and drop in windows, just dont drop into esisting file and dont unzip)
4.name the file update windows will add the .zip checkby right clicking on the file going to preferances then details tab (in win7 anyway)
5.power down phone
6.reboor by holding vol down and power wait for it to read you card
7.might get a cant open cache error, didnt prevent my update
8. using vol keys nav down to recovery, hit power button to select
9.vol down to highlight the update.zip file and powr to select
i was running 1.17 firmware so i had to update from that to 1.32 then 32-47 so check your version and update accourding, is it worth it? my bat life does seem a lil better flash is smother than the flash update i ran in 2.1, and browsign does seem smother, also landscape mode works in both left and right!
Where did you found this rooted version? I have the same problem...

[Q] Rogers logo, HTC Magic is displayed and never proceeds - as requested

Originally Posted by Vicntc
My Data:
Sapphire PVT 32A SHIP S.ON H
Hboot 1.76.0010 (SAPP500000)
CPLD - 12
Radio 6.35.10.18
I am currently stuck at the 2nd boot logo (after Rogers logo, HTC Magic is displayed and never proceeds). I had just finished a successful flash from 1.5 via RUU_Sapphire_Rogers_WWE_3.05.631.7_R_release_signe d_nodriver.
Then, as soon as I setup my WiFi, I was prompted to install yet another update. Dopey me, I said yes. It seemed to go okay for a while then, after one of the reboots, it stopped at a screen that showed a box with an arrow coming out of it and a progress bar below it. After going about 3/4ths of the way over, it stopped. I let it sit for 20min or so then tried to restart. Triangle with exclamation mark screen.
I can however boot into either Recover or fastboot.
I tried to run the RUU again but it times out waiting for the USB to response.
When i boot into Android System Recovery utility, I immediately see "E: Can't open /cache/recovery/command"
Selecting wipe data/factory reset gives no errors but doesn't get me any farther
Selecting apply sdcard:update.zip results in...
Finding update package...
Opening update package...
Verifying update package...
E:no signature (10 Files)
E: verification failed
Installation Aborted.
I'm pretty sure I'm not bricked yet but I am also pretty sure I don't know where to go from here to avoid bricking the phone completely.
Could someone please point me to the thread to resolve these issues and get back to a working state? I have a valid Paypal account and will gladly send beer money once success is acheived.
Thanks in advance.
You should make your own thread. Make a new thread and I'll help you there. Are you trying to stay stock or are you willing to root?
__________________
LG Optimus T, Titanium
T-Mobile
Recovery: Thunderg v1.2
ROM: LOL v1.2
Click me to root your myTouch 1.2/Fender (3.5mm jack) the old school way.
Click me to root your myTouch (regardless of version) the new school way.
----
Yes, i am okay with rooting (I was going to do that later anyway). Your assistance is appreciated.
Well you still didn't answer my question. Are you trying to stay stock or are you willing to root?
Right at the bottom... "Yes, i am okay with rooting "
Alright so what we'll do is grab the file that the RUU is flashing for you from the RUU, put it on your phone, and manually reflash it. Then you now know not to do the update and can just root it. Give me a few minutes please.
As a side note, I missed you saying you wanted to root at the bottom, I apologize.
Sent from my LG-P500 using Tapatalk
No worries, I'm all ears and gratitude.
It was either RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver or
RUU_Sapphire_Rogers_WWE_3.05.631.7_R_release_signed_NoDriver
I am 99% positive it was 3.05.631.7_R because I only have 2 and the first one kept giving me a signature error after downloading to the device.
Alright, if it was the 3.05.631.7 RUU, then slap this file onto your SD card, turn the phone off, boot holding (volume down+power) and follow the on-screen directions. When it's done you should be back to 1.5 and be able to boot into the phone. Then you can follow mumilover's guide to root and install a custom recovery from here. This won't get you a custom ROM, but after installing the recovery, you can find a ROM and flash it from there.
DonJuan692006 said:
Alright, if it was the 3.05.631.7 RUU, then slap this file onto your SD card, turn the phone off, boot holding (volume down+power) and follow the on-screen directions. When it's done you should be back to 1.5 and be able to boot into the phone.
Click to expand...
Click to collapse
Do I need to rename it?
or just copy it from my PC to the SD card as rogers-Rom1.zip?
Copy file from PC to SD card [Done]
Put SD in Phone [Done]
boot holding (volume down+power)
Follow on-screen directions
Then you can follow mumilover's guide to root and install a custom recovery from here. This won't get you a custom ROM, but after installing the recovery, you can find a ROM and flash it from there.
Click to expand...
Click to collapse
Once I am back to 1.5, can I re-run the RUU that I got from Rogers to get their 2.1 (and not accept the subsequent OTA that started this whole thing)?
While I was sitting here, I downloaded the Rootools.rar from the thread you suggested. My AV when bonkers saying it's a trojan. IS that expected because it is going to root the phone (and i can ignore the AV)?
or should I try another mirror and get rid of this first effort?
Copied file to SD
Boot with Vol Down + Power
Phone goes into HBoot
Release keys
A bunch of stuff happens but whips by so quickly I can't read it.
Back to HBoot
Restart Phone
Still stuck at "htc MAGIC" screen
Crap sorry. You need to rename the file to SAPPIMG.ZIP
Sent from my LG-P500 using Tapatalk
The exploit was probably what got flagged by your AV. Nothing to worry about, its just that the exploit started getting used in the market by some dude for malicious purposes so now all the AV providers are flagging it.
Sent from my LG-P500 using Tapatalk
DonJuan692006 said:
Crap sorry. You need to rename the file to SAPPIMG.ZIP
Click to expand...
Click to collapse
Is it normal that if I try to look at the contents of the sappimg.zip file that it says the "file is invalid"?
I've downloaded it twice now and both files do the same.
Vicntc said:
Is it normal that if I try to look at the contents of the sappimg.zip file that it says the "file is invalid"?
I've downloaded it twice now and both files do the same.
Click to expand...
Click to collapse
SD Checking...
Loading...[SAPPDIAG.zip]
No image!
Loading...[SAPPDIA2.nbh]
No image or wrong...
little blue bar up the right hand side of the screen
flashed something about SAPPIMG and is now displaying a menu of options
1. Splash1
2. Recovery
3. Boot
4. System
5. Userdata
Do you want to start update?
<ACTION> Yes
<POWER> No
<ACTION> Yes = Correct?
Yes.
Sent from my LG-P500 using Tapatalk
and Voila!
Absolutely awesome. Send me the link and how much jolt Cola (or whatever) you would like plus email for paypal payment etc...
Absolutely, frickin' awesome! it's ALIVE!! (again).
Thank you.
Cool. Just use the second link to get root and your on your way. Let me know if you run into any problems. Check the sig for the other question.
Sent from my LG-P500 using Tapatalk
Confirmation number: 9BD80494762560535

[Q] Cant get 3.1

24 hours with the tab...
I am new to the tab and i am not going to root yet. I want to use it as ASUS intends it to be, for right now.
Anyways, it came 3.0.1, and i when i ask it to update it tells me no new updates are available. Battery is fully charged, wifi signal is great.
Anything else i can do?
PS- I am saving a review until i get the update, but typing this message was at best frustrating.
Cheers!
Im trying to figure this out as well. Im planning on calling Asus today and ask for help I'll share how to do it as soon ask figure it out
Sent from my SGH-T959 using XDA App
Agnog said:
Anyways, it came 3.0.1, and i when i ask it to update it tells me no new updates are available. Battery is fully charged, wifi signal is great.
Anything else i can do?
Click to expand...
Click to collapse
Download the update manually from the Asus website, save it in your TF's internal memory, then try going to the update page and it should detect the file and allow you to install it. If it doesn't come up straightaway try rebooting your TF and try the update page again.
jonitfcfan said:
Download the update manually from the Asus website, save it in your TF's internal memory, then try going to the update page and it should detect the file and allow you to install it. If it doesn't come up straightaway try rebooting your TF and try the update page again.
Click to expand...
Click to collapse
Something isn't right because your tablet should update automatically once it gets a connection.
I think you an install the update manually.
1)Download the firmware from Asus, unzip it and put the contents for the ASUS/Updates/ folder on the root directory of the external SD card. Rename it to EP101_SDUPDATE.zip
2) Boot into recovery - hold volume down, press power button. Your TF will turn on and say it's going to blow up in 5 secs. Press volume up within 5 secs. Don't delay because you could wipe your data if you press volume up too late.
3) get some popcorn and watch the magic happen. Afterwards, it will reboot, you'll see a progress bar to indicate that it is flashing. Then it should boot into sweet honeycomb.
4) Delete or rename the EP101_SDUPDATE.zip for something else, or else it will flash every time you go to stock recovery.
Edit: I think the firmware has to match your current build, i.E., US, TW, WW. Check your build info to be sure.
gee one said:
I think you an install the update manually.
1)Download the firmware from Asus, unzip it and put the contents for the ASUS/Updates/ folder on the root directory of the external SD card. Rename it to EP101_SDUPDATE.zip
2) Boot into recovery - hold volume down, press power button. Your TF will turn on and say it's going to blow up in 5 secs. Press volume up within 5 secs. Don't delay because you could wipe your data if you press volume up too late.
3) get some popcorn and watch the magic happen. Afterwards, it will reboot, you'll see a progress bar to indicate that it is flashing. Then it should boot into sweet honeycomb.
4) Delete or rename the EP101_SDUPDATE.zip for something else, or else it will flash every time you go to stock recovery.
Edit: I think the firmware has to match your current build, i.E., US, TW, WW. Check your build info to be sure.
Click to expand...
Click to collapse
I am following your instructions and all I am getting is the Android with the exclamation mark symbol when I reboot from recovery.
Agnog said:
I am following your instructions and all I am getting is the Android with the exclamation mark symbol when I reboot from recovery.
Click to expand...
Click to collapse
Nevermind, I got it. I was being dumb.
3.1 goodness.
Agnog said:
Nevermind, I got it. I was being dumb.
3.1 goodness.
Click to expand...
Click to collapse
What you do to get it to work im having the same issue with the exclamation mark symbol.........
EDIT
....ok i took a shot and did EXACTLY (read carefully) what was in the directions... i removed all the folders that were part of the udpate ( ASUS\UPDATE) I put the .zip on the root of the sdmicro... this contradicts what the SOP says to do with the manual update but hey it works ...thanks
EDIT EDIT
This should be added to the STICKIY as a way to update!!
gremmie said:
What you do to get it to work im having the same issue with the exclamation mark symbol.........
EDIT
....ok i took a shot and did EXACTLY (read carefully) what was in the directions... i removed all the folders that were part of the udpate ( ASUS\UPDATE) I put the .zip on the root of the sdmicro... this contradicts what the SOP says to do with the manual update but hey it works ...thanks
EDIT EDIT
This should be added to the STICKIY as a way to update!!
Click to expand...
Click to collapse
Agreed. I misunderstood the directions at first - my fault for being a noob. I ended up using the full SD slot on my dock, but the math was the same.
HUGE thanks to gee one.

[GUIDE] T-Mobile G2 2.3.4 official OTA manual update

There still seem to be a few people with problems so I thought I'd try to collect the steps and add a bit more info:
Notes
- So far this is only confirmed to work on full stock 2.2. For the leaked 2.3.3 you'll need to downgrade first; see this thread: http://forum.xda-developers.com/showthread.php?t=1180733&highlight=temp+root+downgrade
- The only confirmed root so far requires s-off BEFORE you follow this guide: http://forum.xda-developers.com/showthread.php?t=1206930
- I have had no reports of anyone doing this with anything other than 100% stock recovery, hboot, etc. Please let me know if you do try and what happens; I'll update this post.
- Following this procedure will not wipe your apps or your data.
Steps
1. Download http://android.clients.google.com/p...MOUS_2.15.531.3-1.22.531.8_release_197463.zip and rename to update.zip. Turn off 'Hide extensions for known file types' and make sure it's not update.zip.zip!
2. To verify your download didn't get corrupted, check its md5sum. It should match 3c7b0c2253f72f86b06d2c85b2c8c294 (you can get a dos tool to do this here: http://etree.org/md5com.html. Run cmd.exe and type md5sum.exe update.zip from a folder that contains both files) If your result doesn't match, download again.
3. Place update.zip on the root of your SD card, not in any folders.
4. Power down your phone.
5. Press and hold both VOLUME DOWN and POWER until you get a menu
6. You may not be able to navigate the menu yet. Wait for 10-15 seconds until it says it's checking some files, then automatically returns to the menu. Now you can use VOLUME UP/DOWN to choose menu options.
7. Choose Recovery from the menu by highlighting with VOLUME UP/DOWN and pressing POWER.
8. Wait until you get a picture of a phone with a red triangle and !
9. Press & hold VOLUME UP, wait one second, then also press POWER. You should get a menu with blue text.
10. You will see "E:Can't open /cache/recovery/command" at the bottom of the screen. This is OK!
11. Again with VOLUME UP/DOWN and POWER, select "Apply sdcard:update.zip"
12. From this point, just wait until it tells you to reboot and choose that menu option. If you get any errors here, consult the troubleshooting below.
13. There are several more automatic reboots and wait screens to go. Be patient!
Troubleshooting
- "E:failed to open /sdcard/update.zip (no such filler or directory)" - your file isn't named update.zip! Reboot your phone and use Astro or another file manager to make sure you've got the name right.
- "E:failed to seek in /sdcard/update.zip (Invalid argument)" - your download probably got corrupted! Check the md5sum again, redownload, and try again!
- "assertfailed: file_getprop("/system/build.prop", "ro.build.fingerprint") == tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys"" - you probably don't have the latest 2.2 that this update is designed to replace. You might be on 2.3.3 or possibly the original pre-wifi-calling 2.2. To fix this, downgrade from 2.3.3 or wait for the OTA to get the newer 2.2.
Has anyone noticed any bugs in the new OTA? Waiting for bug reports before I flash.
Will this work with clockworkmod recovery?
Sent from my T-Mobile G2 using XDA App
leech1980 said:
Will this work with clockworkmod recovery?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Well I would wait until someone makes a rooted version of this, I don't think you want to loose root over an update that is kind of outdated compared to Cyanogenmod.
Thank you for the link I'm updating my wife's phone tonight
Sent from my LG-P999 using Tapatalk
Cimer said:
Well I would wait until someone makes a rooted version of this, I don't think you want to loose root over an update that is kind of outdated compared to Cyanogenmod.
Click to expand...
Click to collapse
I don't mind losing root. I'm running stock 2.2 with s-off and clockworkmod. I just want the update to work.
The instructions above don't work for me. When I attempt an update in clockworkmod I get an error "(Status 7) installation aborted", something like that.
That's because it's not meant for clockworkmod yet. You can follow his instructions, loose root and be updated, or just wait a little until someone makes a rooted version and just flash it via clockworkmod.
Cimer said:
That's because it's not meant for clockworkmod yet. You can follow his instructions, loose root and be updated, or just wait a little until someone makes a rooted version and just flash it via clockworkmod.
Click to expand...
Click to collapse
Following his instructions, I get to clockworkmod recovery after step 7. I then choose update from .zip and get an error message.
attempted this with Indian HTC Desire Z and official htc update from another user with Canadian HTC Desire Z.
Getting the error: "Invalid Operation"
Why do I have an Indian HTC Desire Z ? Amazon told me it was American. I didn't know better.
How did I get the Canadian update ? A friend kept a copy of the file when he was updating his.
Ideas ?
I get the following output:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Copying fotaBoot to /data/system for customize reload...
Verifying current system...
assert failed:apply_patch_check("/system/bin/dnsmasq", "0ca7c8c9c5d267665622497df4c67dec65166adb", "1d717ab5c2bfc75d16bf6a9ec7936158cdc65aef")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Received the following error:
assertfailed: file_getprop("/system/build.prop", "ro.build.fingerprint") == tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys"
and a bunch of other gobbletygook...ending with
E: Error in /sdcard/update.zip
(status 7)
Installation aborted
OP needs to add "Status 7" error to OP.
You cant use clockworkmod recovery to update using the official OTA update.zip.
no - i don't have clockwork or any mods at all.. I think I screwed up the downgrade slightly, anyhow, what happened was shortly after posting this i got an OTA update that updated my system - but it didn't update it to 2.3.4 just to a newer 2.2 evidently. THEN I was able to use the update file and force it so now I have 2.3.4! (albeit still without my apps..)
wireless hot spot
can anyone tell me if wireless hotspot still works with this update?
All i know is some devs need to rip this stuff apart and get to cooking up some CM type features into it and it's my new daily driver
leech1980 said:
Will this work with clockworkmod recovery?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
It looks like you can't use a custom recovery to apply this update. It likely tries to verify the recovery image. You could open the update up and remove the file version verification, and various other things to prevent it from taking away your S-Off and SuperCID. You would then HAVE to apply it with a custom recovery with signature verification off.
A quick look in the firmware.zip portion of the update and you find this in an info file:
modelid: PC1010000
cidnum: T-MOB010
mainver: 2.15.531.3
hbootpreupdate:12
As well as hboot_7230_Vision_GEP_0.82.0008_110413.nb0
I don't know if that info file actually does anything, but I would still start with changing cidnum to 11111111.
The real meat of what is going on is in the Meta-inf folder, that is what handles copy files and performing updates. You can simply remove things you don't want updated. If modified correctly, you could then apply a superuser su.zip before rebooting and keep root with your update.
Unfortunately, I don't know enough to trust my own handywork. Maybe some people more familiar with the innards of Anroid could help out the Vision/G2 community?
The more I look at it, the more it seems like you could just delete the recovery.img (or replace it with clockworkrecovery) from the firmware.zip and delete the assert(apply_patch_check crap from the updater-script in META-INF\com\google\android and apply the modified update.zip with clockworkrecovery (signature verification off).
You could then apply an su.zip before rebooting and you should come back up with custom recovery at least, if not root also.
No one do this just yet. Surely someone from the N1 community can guide us as to how to chop up the update.zip
Installed successfully on my stock 2.2 G2. Thanks! Was getting tired of constantly checking my phone to see if I had gotten the OTA update yet!
Well just ran this on my roomie's stock phone. Fingers crossed.........
As soon as I posted this the phone booted up. So far so good. Thanks, I was beginning to think this phone was never going to get GB.
Drthunderer said:
can anyone tell me if wireless hotspot still works with this update?
Click to expand...
Click to collapse
WiFi hotspot is working fine for me after updating.

Categories

Resources