Database Users

Getting your phone ready for the FroYo update.zip!

Okay, so it seems we ran into a few issues with the installation
DO NOT run the FroYo update.zip unless the software information on your phone reads as followed:
Baseband should say 1.00.03.04.06
Software/Build number should say 1.22.605.2...if it is 1.22.605.0 please read the following instructions:
May OTA attached at the bottom of the thread thanks to wryun(note: i havent tested it, so any feedback on the zip would be great.)
-Drop the file on the root of your SD card.
- 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.
- Make sure that the software now says 1.22.605.2[/COLOR]
Now go back to the update.zip on your sd card and delete...now you can proceed with the Froyo update.zip here http://forum.xda-developers.com/showthread.php?t=770091

Dinc with Baseband 2.05.00.06.11
I'm not rooted but had applied the leaked update to my Droid that updated my phone and now have the baseband 2.05.00.06.11. I am not able to apply the froyo update.zip without getting the same error message as many others have. Any assistance would be much appreciated. I hope to get back to stock and then update.

whiteknight333 said:
I'm not rooted but had applied the leaked update to my Droid that updated my phone and now have the baseband 2.05.00.06.11. I am not able to apply the froyo update.zip without getting the same error message as many others have. Any assistance would be much appreciated. I hope to get back to stock and then update.
Click to expand...
Click to collapse
I will provide you with a link to get it back to stock shortly

whiteknight333 said:
I'm not rooted but had applied the leaked update to my Droid that updated my phone and now have the baseband 2.05.00.06.11. I am not able to apply the froyo update.zip without getting the same error message as many others have. Any assistance would be much appreciated. I hope to get back to stock and then update.
Click to expand...
Click to collapse
Here ya go...http://androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html

Thank you schwartzman93. Very much appreciated. I'll let you know how it works.

Is it CONFIRMED that the update will fail if we are running 1.22.605.2 with the 2.15 radio and STOCK recovery?

Do we have to downgrade if we are running on the 2.2 OTA from 8/1?
build 3.16.605.0/ radio 2.05.00.06.11

lamusician said:
Do we have to downgrade if we are running on the 2.2 OTA from 8/1?
build 3.16.605.0/ radio 2.05.00.06.11
Click to expand...
Click to collapse
Yes, you do.

tylerwagler said:
Is it CONFIRMED that the update will fail if we are running 1.22.605.2 with the 2.15 radio and STOCK recovery?
Click to expand...
Click to collapse
that's also with hboot .77
**Trying it right now
***it appeared to have worked, however when I booted it hung toward the end of the droid bootup animation... then after like 3 minutes it finally booted

Thank you so much for all of the help on these threads. I have read extensively but I still have a question concerning the new 2.2 OTA update:
I rooted via unrevoked3, then ran unrevoked forever to set s-off. I then immediately reverted back to pure stock 2.1. I have not upgraded my radio and I never received an OTA of any kind, in May or now.
Baseband:1.00.03.04.06
Build Number: 1.22.605.0 CL161493
My question is this: will I receive the "official" OTA 2.2 from verizon with this build, and will I be able to install it if I receive it, or will I need to upgrade my build to 1.22.605.2 before I can receive and/or install it? Thanks!

THANKS
THANKS schwartzman. the "may OTA" got me to ...605.2 perfectly. I read through a bunch of other posts by you. You did a lot of good work today. THANKS

schwartzman93 said:
Yes, you do.
Click to expand...
Click to collapse
I've downgraded and my baseband is now 1.00.03.04.06 and sw is 1.22.605.2
My hboot is 0.79 though, not 0.77. Is this going to be a problem or can I proceed with the update?
Thanks in advance.

Thanks for posting the link to the downgrade. It took some work but I was able to get my phone back to stock and now...it is booting up with Froyo (crossing fingers).

help!
schwartzman93 said:
I will provide you with a link to get it back to stock shortly
Click to expand...
Click to collapse
I was following the video instruction to downgrade from 1.36.605.0 baseband 2.05.00.06.11. when i booted and it was supposed to error out reading the pb31img it wants to install. is this a problem? bootloader is .77

HELP!!!!
its telling me e: signature verification failed Installation aborted... how do i fix this?? i factory reset and wiped cache still nothing???

Thanks soo much dude. I just registered with this site so I could thank you. I rooted my phone right before the OTA and the update failed so I assumed it was my fault and unrooted back to stock. I wasn't even aware of a May update till now. Thanks a ton!

when i try to install the may ota update.zip i keep getting
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/inc/inc/inc:2.1-update1/ERE27/161494:user/release-keys" || file_getprop("system/build.prop", "ro.build.fingerprint") == "verizon_wwe/inc/inc/inc:2.2/FRF91/231334:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted.
anyone have any idea what im doing wrong or what i should do to fix it so i can install the may ota, and then install the 2.2 ota?
Here is what i have on it right now
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.77.0000
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06
Firmware 2.1-update1
Build 1.22.605.0 CL161493 release-keys

Make sure you arent running Clockwork Recovery...that maybe the problem...thats what seems to be the problem with people getting their phones to Android 2.2

no i did the pb31img.zip to remove it and when i go into it says its the android recovery

same error
optikkore said:
no i did the pb31img.zip to remove it and when i go into it says its the android recovery
Click to expand...
Click to collapse
i am getting that same error when i try it as well

[Q] recovery verification failed

I feel really stupid even having to ask this since I've had a vibrant for the last few months and this should be a no brainer switching over to the fascinate,but appearantly there is something I'm missing.
A few months ago,my friend bought this fascinate and I rooted it for him using rage against the cage,manually typing in commands using a tutorial that I can't find anymore for some reason,it was running dl01 I believe,whatever is stock. he was happy with that for awhile,then tried zinc and a few other roms and then odin'd back to dl01 and used it like that for awhile. fast forward a few months and I bought it from him and i'm trying to reroot. I used super one click and it succeeded and I have root access,I installed rom manager,it downloaded cwm and I told it to reboot to recovery and I get E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
I then tried flashing to DJ05,and I get the same result. any idea why this is happening? I have 2e recovery with both,so it should be working. I have tried deleting the update.zip file and making rom manager redownload it over both 3g and wifi and nothing changes. any ideas?
(edit)
now I feel double stupid. I followed the sticky for how to install CWM and I flashed the file in odin and that fixed it. I wonder why it worked a few months ago without doing that,but this time it wouldn't? oh well,either way it fixed it,mods-can you delete this thread please?

[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.

Update issues with latest OTA update from ASUS - Rooted with CWM

I Have a tf101 with first the ics upgrade. I recently got notice of the ota update. I ran OTA Rootkeeper and then ran the update. It bombed after reboot with the downed robot. After that would only boot into cwm, unless i cold boot. Even then the update is not applied. How do ii fix this without starting from scratch with a new or factory rom? If i have to restore factory, where/how do i do it Assn how do i then get my phone back to its current state?
Thanks all
Sent from rmy SAMSUNG-SGH-I717 using XDA

Go here. http://forum.xda-developers.com/showthread.php?t=1530337

ssl123 said:
Go here. http://forum.xda-developers.com/showthread.php?t=1530337
Click to expand...
Click to collapse
Thanks for the link, but it's not really helping me.
Firstly, it says nothing about the OTA update and how to address installing it on a rooted system.
Second, that thread has 23 pages and there seem to be a LOT of questions about the integrity of the process they have there.
I would figure that MANY people are in my situation and that there would be a more straightforward answer.

Why are you trying to get update with CWM.?

At this point, this thing is so messed up I want to toss it out the window! I have tried so many fixes! Nothing is working like it should. What is the best way to restore it back to factory...even if it means going pre-ICS and going through the upgrades? I just want the hours of time i'm spending on this to end.

Wait. You had root + CWM with stock 9.2.1.11 and you installed OTA update?
What version of CWM do you have?

Try this thread, I did it and it worked no bother, had to go back to Roach2010 CWM 3.2.0.1 first though --- http://forum.xda-developers.com/showthread.php?t=1545965

Get an Assert Failed error: apply_patch_check (long string of numbers)
E:Error in /sdcard/patch-edited.zip
(status 7)
Installation aborted

[Q] Kit-Kat OTA Fail

I was notified today that the OTA was ready to install so I told my N7 to go for it. It was almost completed but then I got some message about the installation failed and it had been aborted. I unfortunately did not take not of exactly what the error said and just rebooted thinking there was probably some error with the download. Well now I get the new boot screen like it wants to boot into Kit-Kat but it is endless. I can boot into CWM but that is it right now. I was thinking I would try and do an adb sideload but I don't know how to get my N7 recognized in adb while in CWM. I also read something on here that I might be missing the currents.apk file. If that is the problem I don't know how to get the file onto my N7 since I cannot boot into anything but CWM. What would you all recommend? Should I just do a factory reset? I am trying to avoid that so as to not lose all my saved games but if that's my only option at this point then so be it.

danipoak said:
I was notified today that the OTA was ready to install so I told my N7 to go for it. It was almost completed but then I got some message about the installation failed and it had been aborted. I unfortunately did not take not of exactly what the error said and just rebooted thinking there was probably some error with the download. Well now I get the new boot screen like it wants to boot into Kit-Kat but it is endless. I can boot into CWM but that is it right now. I was thinking I would try and do an adb sideload but I don't know how to get my N7 recognized in adb while in CWM. I also read something on here that I might be missing the currents.apk file. If that is the problem I don't know how to get the file onto my N7 since I cannot boot into anything but CWM. What would you all recommend? Should I just do a factory reset? I am trying to avoid that so as to not lose all my saved games but if that's my only option at this point then so be it.
Click to expand...
Click to collapse
Retry it to try to get the exact error message. I'm currently running into the (i forgot the name)has unexpected contents
error, you should have a "has unexpected contents" error message too though it might involve different files that are not recognizable by the android kit Kat file update, if you find the error message, please explain it here and hopefully someone can upload the file fix for the error. In my case I always get a new different error after I find a fix for the previous error.
Sent from my Nexus 7 using XDA Premium HD app

GoldenNexus7 said:
Retry it to try to get the exact error message. I'm currently running into the (i forgot the name)has unexpected contents
error, you should have a "has unexpected contents" error message too though it might involve different files that are not recognizable by the android kit Kat file update, if you find the error message, please explain it here and hopefully someone can upload the file fix for the error. In my case I always get a new different error after I find a fix for the previous error.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Well I would try that but I cannot boot into android at all. All I can do is boot into CWM and from there I cannot reinstall Kit-Kat because I do not have it on my /sdcard.