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

Update to HTC EVO 4G failed

All,
I got a notification of update this morning (June 29, 2011) on my HTC EVO 4G (rooted/with netarchy toast mod) but when I tried to apply the update I get:
assert failed: apply_patch_check ("/system/lib/modules/bcm4329.ko". "78fE:unknown command [c535f323ef3a5c8304b32f514c23ea458132b".]
E:unknown command [9"0]
E: Error in /cache/OTA-Supersonic_4.24.651.1-3.70.651.1_release404yzkft23eop520.zip (Status 7)
Installation aborted.
Android system recover is open and the prompts are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Mounts
- Other
- Power off
What do I do next? How do I get this update? Thanks!

guidecca said:
All,
I got a notification of update this morning (June 29, 2011) on my HTC EVO 4G (rooted/with netarchy toast mod) but when I tried to apply the update I get:
assert failed: apply_patch_check ("/system/lib/modules/bcm4329.ko". "78fE:unknown command [c535f323ef3a5c8304b32f514c23ea458132b".]
E:unknown command [9"0]
E: Error in /cache/OTA-Supersonic_4.24.651.1-3.70.651.1_release404yzkft23eop520.zip (Status 7)
Installation aborted.
Android system recover is open and the prompts are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Mounts
- Other
- Power off
What do I do next? How do I get this update? Thanks!
Click to expand...
Click to collapse
Anyone, anyone? Don't everyone rush down. There's room for everyone.

Is your recovery old (ie not Clockworkmod 3)
Have you tried to backup your apps with titanium and just starting all over with a new updated full rom?
Have you edited the filesystem to cause the update to say this? If you edit any of the filesystem, the update fails.
You need to download a new rom and just start all over it seems.
How are we to figure things out if you dont give any background?

Try unrooting and put a stock rom and then do an update. Hope that helps
Sent from my HTC EVO phone, shouldn't we all have one?

If you want to keep root, then you never take the update. Otherwise you will most likely lose root, and will have to wait until a Dev finds an exploit to reroot. If you want to just update the radio(s) then there are flashable updates in the Dev section that you can flash.

I Think I Did/Didn't
mattrb said:
Is your recovery old (ie not Clockworkmod 3)
Have you tried to backup your apps with titanium and just starting all over with a new updated full rom?
Have you edited the filesystem to cause the update to say this? If you edit any of the filesystem, the update fails.
You need to download a new rom and just start all over it seems.
How are we to figure things out if you dont give any background?
Click to expand...
Click to collapse
Not sure what clockworkmod I have. I could backup app with titanium and which "full rom" would you recommend? I have netarchy-toastmod-4.3.4-cfs-havs-less-nosbc-uni installed and in zip format. I rooted the phone and applied the toastmod so I modified the stock HTC EVO 4G file system. The next comment suggests unrooting the phone and starting over. Why so much work for a "smart" phone? Any specifics would be appreciated on how to proceed.

kf2m said:
If you want to keep root, then you never take the update. Otherwise you will most likely lose root, and will have to wait until a Dev finds an exploit to reroot. If you want to just update the radio(s) then there are flashable updates in the Dev section that you can flash.
Click to expand...
Click to collapse
Seems to be a rule never to take an update of the original after modifying any gadget. Maybe my rooted phone is better off/more advanced without the update but I haven't found anyone that has said it yet. Since the update failed I think I have root but I will check it. My wife's unrooted phone took the update easily.

guidecca said:
Seems to be a rule never to take an update of the original after modifying any gadget. Maybe my rooted phone is better off/more advanced without the update but I haven't found anyone that has said it yet. Since the update failed I think I have root but I will check it.
Click to expand...
Click to collapse
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.

If you would like to keep the stock rom but update to the newest release you can download Rom Manager from the market and flash the newest stock rom. Quite easy and only takes a few clicks. Next time you see an update from sprint, just wait until Rom Manager gets a rooted rom of that release and go nuts. If you don't feel like dealing with Rom Manager you can manually flash the roms you find in this forum. Hope this helps.

This has worked rather well for me for the past few updates, including the most recent one:
forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/90582-guide-updating-rooted-gingerbread-without-flashing-new-rom-wiping-your-phone.html
Also, the error you see is likely due to you changing the Broadcom file in that location to enable Wifi-N speeds on your EVO. Is that something you remember doing? When installing updates, it needs the original unchanged version of "\system" files to be there to verify against, including this one.
I just went through the process, and got the same error before I remembered to change bcm4329.ko back to the original. Also, don't forget to unfreeze any bloatware if it is frozen, or it won't proceed past the verification process (as it changes "\system" files. Additionally, clearing the Davlik cache is always a good idea when updating.

I forgot to mention- If I remember correctly, the instructions are elaborated on in post #44 of that page.

tgruendler said:
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.
Click to expand...
Click to collapse
You say a rooted version was ready to be flashed within hours.
This is what I read on Android Forums:
There is no exploit yet to allow unrevoked to root the new hboot(2.16). They will find it but how long is unknown.
You can apply the update by flashing the rooted rom and the updated radios found here: [ROM][STOCK] 4.24.651.1 - Odexed & De-Odexed - xda-developers and here: [ Radios ][ 6-3 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
The only thing that would not happen by flashing those it that your hboot would not be upgraded which you don't want anyway so that you can retain root.
If Haux has an exploit would it work on netachy toastmod rooted EVO 4G?

guidecca said:
You say a rooted version was ready to be flashed within hours.
This is what I read on Android Forums:
There is no exploit yet to allow unrevoked to root the new hboot(2.16). They will find it but how long is unknown.
You can apply the update by flashing the rooted rom and the updated radios found here: [ROM][STOCK] 4.24.651.1 - Odexed & De-Odexed - xda-developers and here: [ Radios ][ 6-3 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
The only thing that would not happen by flashing those it that your hboot would not be upgraded which you don't want anyway so that you can retain root.
If Haux has an exploit would it work on netachy toastmod rooted EVO 4G?
Click to expand...
Click to collapse
To be technical because I am a jerk, Hehe, you don't root the hboot. You unlock it via making it s off. You root the Rom by applying super user privileges from within. Hboot s off means you can easily flash different recovety images, radios, and any ruu considering you have supported radios. Tomatoes tomahtoes.
Sent from my PC36100 using XDA Premium App

Thanks
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.
I just thought that maybe there was an exploit for gingerbread 2.3 (OTA) that someone had found within hours of Google's release. I wanted to definitely make sure there was or wasn't a way to update my phone. Thanks for your clarification on hboot, etc. Mattlock over on Android Forums has a good guide for rooting and he is good at step-by-step 'how to do it' and some explanation why for us newbies. My rooted phone works fine but my wife's stock phone with the update seems to get a lot of network failures. She has a lot apps and a stock SD card - she refuses to let me root her phone - superstitious kind.

[Q] July Build A500 Fails to Update After Backing Up Stock Rom

I read a couple of threads before trying my first backup (Solved - 3.1 Update & OTA Full Package) Seemed simple enough. My tab is a July build with Acer_A500_4.010.07_Com_Gen2 purchased in the US. I checked the OTA full package thread and that ROM wasn't available, so I thought I'd back up the stock ROM and see if it was useful to anyone.
I Downloaded and installed:
Iconiaroot 1.3
Root Checker
Acer Recovery
File Manager HD
Did the backup according to the thread.
Rebooted. At that time I decided address the update the system was prompting me was available. I tried to unroot as was advised in some posts and got the message: "Something went wrong you are still rooted.
Tried to root again and the program hung on "Extracting"
Shut down, removed the SD card and restarted.
Checked with root checker and it said I was not rooted.
Tried update several times and it failed about 1/4 through the process each time, so I just reset the tab.
The update still fails.
Do I have a problem or is this just typical of the update service?
Thanks

JohnnyDingo said:
I read a couple of threads before trying my first backup (Solved - 3.1 Update & OTA Full Package) Seemed simple enough. My tab is a July build with Acer_A500_4.010.07_Com_Gen2 purchased in the US. I checked the OTA full package thread and that ROM wasn't available, so I thought I'd back up the stock ROM and see if it was useful to anyone.
I Downloaded and installed:
Iconiaroot 1.3
Root Checker
Acer Recovery
File Manager HD
Did the backup according to the thread.
Rebooted. At that time I decided address the update the system was prompting me was available. I tried to unroot as was advised in some posts and got the message: "Something went wrong you are still rooted.
Tried to root again and the program hung on "Extracting"
Shut down, removed the SD card and restarted.
Checked with root checker and it said I was not rooted.
Tried update several times and it failed about 1/4 through the process each time, so I just reset the tab.
The update still fails.
Do I have a problem or is this just typical of the update service?
Thanks
Click to expand...
Click to collapse
Did you install the recovery clockwork? If so then install the stock recovery back on the tablet use acer recovery for that.

mjd1975 said:
Did you install the recovery clockwork? If so then install the stock recovery back on the tablet use acer recovery for that.
Click to expand...
Click to collapse
Thanks a lot. That worked perfectly. I don't know how I failed to pick that up, I read so many threads my head was about to explode.
Any ideas on threads you might have read that explain where the recovery files are stored, how to identify stock, what they actually contain and the recovery process in general?
Thanks again.

[Q] Update to 3.2 failed

Dear all,
I got a update notification today. I was so happy to see that.
I spent 20 mins on downloading this firm, but after the unzipping procedure,
it exit Andriod OS and reboot to a DOS-like system.
I saw a bee on the screen, there was a ProcessBar under this bee.
When the process went to around 20%, the process was failed and a "!" was shown up.
I installed Acer Recovery Installer on my tablet and I have Recovery on it as well.
Is it the reason why I cannot update my OS?
Help!!!!!

Easier way to get official OTA updates from acer is to be full stock :
- stock rom
- stock recovery / bootloader
Remember that updating to stock 3.2 will makes you lose root

franva said:
Dear all,
I got a update notification today. I was so happy to see that.
I spent 20 mins on downloading this firm, but after the unzipping procedure,
it exit Andriod OS and reboot to a DOS-like system.
I saw a bee on the screen, there was a ProcessBar under this bee.
When the process went to around 20%, the process was failed and a "!" was shown up.
I installed Acer Recovery Installer on my tablet and I have Recovery on it as well.
Is it the reason why I cannot update my OS?
Help!!!!!
Click to expand...
Click to collapse
Must remove root and all mods and reflash stock recovery. Maybe not all, but that should work.

shaun298 said:
Must remove root and all mods and reflash stock recovery. Maybe not all, but that should work.
Click to expand...
Click to collapse
Are there instructions on how to do this?

Update 3.2 failed
Hello, I have the same problem, I can install the stock with CWM? if so, where can I download? the ROM?
(sorry for my bad english)
My device is Acer Iconia Tab A501

I am having quite a bit of problem updating my A500. After the update downloaded the first time, it gave me an error saying update is invalid. After that it is constantly trying to download. As soon as 357 MB is downloaded, instead of asking me whether to install now or later, it just goes ahead and tries to re-download all over again. As you know it takes some 20 mins to get the whole 357MB over wifi, so I went ahead and unchecked the automatic update checkbox in system update. Does anyone know where the downloaded file ends up? I could just try to run it from that location.
My system was rooted, but once I got the last ROM update (3.1), the tablet was unrooted and none of the rooted apps work anymore. So I don't think I should be having root related issues unlike some of you who are having problems. Any help is appreciated.

Fix for "Invalid Update" problem .....
Samaruf,
I suggest that you have a look at Post #4 in the following thread......
http://forum.xda-developers.com/showthread.php?p=18132338#post18132338
This thread appears to be focused on a different problem. The resolution to your problem is at the above thread. Good luck....

Lenovo Thinkpad stuck and about to give up

Hi guys
My dad's tablet is messed up after an update from Lenovo. Tablet wasn't rooted nor anything. It is stuck on the "Lenovo" boot screen. I tried wiping the cash, factory reset, no luck.
Then I tried to download the OTA files from Lenovo site and update from the SD cards with no luck either.( downloaded all the files from A400 to A310_02_0024_0065. Each time I try to use an update, I get a message with the version of the previous update...
Each time I try to use an update (for example A310_02/0024_0065), I get the following message:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0024_0060_US:user/release-keys" || "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0024_0065_US:user/release-keys"
E:error in /tmp/sideload/package.zip
(status 7)
installation aborted
Click to expand...
Click to collapse
For example A310_02/0024_0075), I get the following message:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0024_0066_US:user/release-keys" || "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0024_0075_US:user/release-keys"
E:error in /tmp/sideload/package.zip
(status 7)
installation aborted
Click to expand...
Click to collapse
And so on and so forth...
The lenovo site doesn't have any version earlier than the A310_02_024_065...
Anyone has an idea about what 's going on?
The tablet is 1838-CTO.

Anyone?

paricitoi said:
Anyone?
Click to expand...
Click to collapse
Hmm the only thing I can think of is are you using the correct versions of the updates? There are different ones for us, row, we, and so forth. Secondly do you recall what update were you on when you tried to update? Because these are incremental updates you can't revert back to previous updates or skip any if you were on 65 then you have to flash 75 if you were on 75 you have to flash 86 if on 86 you have to flash 89 and so forth. I had hard time updating because I was trying to skip straight to ICS from 75 which isn't possible. You said you never rooted so that means you don't have custom recovery which should make you good to go. Make sure you are flashing the updates in the right order should work then.

hatlesssandman said:
Hmm the only thing I can think of is are you using the correct versions of the updates? There are different ones for us, row, we, and so forth. Secondly do you recall what update were you on when you tried to update? Because these are incremental updates you can't revert back to previous updates or skip any if you were on 65 then you have to flash 75 if you were on 75 you have to flash 86 if on 86 you have to flash 89 and so forth. I had hard time updating because I was trying to skip straight to ICS from 75 which isn't possible. You said you never rooted so that means you don't have custom recovery which should make you good to go. Make sure you are flashing the updates in the right order should work then.
Click to expand...
Click to collapse
The Tablet is a US one. I also suspected the order of the updates but as I said, the oldest update available on Lenovo site is the A310_02_0024_0060_US yet when I try to use it, it complains about a previous version.
Do you know where I can get updates previous to A310_02_0024_0060_US?

Hello, I just fixed my tablet when having the same error as you.
Flash this format.zip:
http://ubuntuone.com/4zKT1jqeqhR8qdGh2y4TaM
What it does is self explanatory.
Reboot when done and then see if it works. If it does not. Flash one of these roms mad for the tablet found here (after using the format.zip):
http://forum.xda-developers.com/showthread.php?t=1846044

You kind of resurrected this thread lol. The issue they would have with that is they weren't rooted, so they wouldn't have CWM.

da_reeseboy said:
You kind of resurrected this thread lol. The issue they would have with that is they weren't rooted, so they wouldn't have CWM.
Click to expand...
Click to collapse
I just wanted to help :angel:
I see many many mega tones of threads online that have the same bricking problem and they all remain unsolved. most of them had rooted devices too.

Destreza said:
I just wanted to help :angel:
I see many many mega tones of threads online that have the same bricking problem and they all remain unsolved. most of them had rooted devices too.
Click to expand...
Click to collapse
All good

I'm one of the bunch of guy that have this tablet bricked, and with the bootloader locked by Lenovo.
The only thing we can do for the moment is:
Keep the pressure on the lenovo forum to unlock the bootloader.
Open formally support tickets about bricked Thinkpad Tablets to Lenovo
I'm also documenting all the stuff I'm finding on the XDA Wiki for this tablet.
http://forum.xda-developers.com/wiki/Lenovo_ThinkPad
Regards
Martin

Thank you soooooooooooooo much
Destreza said:
Hello, I just fixed my tablet when having the same error as you.
Flash this format.zip:
http://ubuntuone.com/4zKT1jqeqhR8qdGh2y4TaM
What it does is self explanatory.
Reboot when done and then see if it works. If it does not. Flash one of these roms mad for the tablet found here (after using the format.zip):
http://forum.xda-developers.com/showthread.php?t=1846044
Click to expand...
Click to collapse
my think pad tablet was rooted with clockwork and cygen ROM and was stuck at lenovo screen for 4 months. i only had to use the format file and it worked.:laugh::highfive: THANKS SO MUCH!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Hi.
It seems that I have a brick like this on the Thinkpad Tablet 1. It just show the Lenovo static logo.
The only good things is that I have CWM V6.0.1.2 installed and seems to works fine.
Any tip on which file can I flash to try to recover this tablet?
Regards

Hi
Can it be possible to repost the format file or include a working link.
Thanks !