Database Users

Have to admit I need some help with rooting

Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.

This means you are on the leaked version now and there is nothing that can be done as of right now.

K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?

ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.

sounds like you got a bad pb001.img file.

ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?

nevermind addressed my issue

As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5

ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.

af man...seriously!

out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"

HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA

ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!

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

OFFICIAL: update.zip is finally here! :D

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

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

Xoom 3G/4G ICS Manual upgrade instructions

here you go. You can upgrade your stock Honeycomb on your 3G/4G Xoom, to ICS. do it yourself and not wait for the OTA update:
http://www.droid-life.com/2012/06/04/download-motorola-xoom-4g-android-4-0-4-imm76l-update/
I'm doing it now. worked like a champ!
Good luck!

Another way to update without USB cable
just updated mine...what i did was this:
1. I downloaded the patch to my internal storage and renamed it update.zip
2. adb reboot bootloader
3. fastboot flash recovery rogue-recovery.img (file name found on xda forums )
4. fastboot reboot
5. At the M logo i started pressing the down vol key to select recovery mode then pressed power. After this press power than up will get you into recovery mode. IMPORTANT...DO NOT LET IT BOOT INTO ANDROID OR ELSE CUSTOM RECOVERY WILL BE OVERWROTE AND YOU WILL HAVE TO START OVER AT STEP 2!!
6. When rogue recovery was shown i installed the update.zip from my internal storage.
I am now using the new ICS 4.0.4 update No need for that USB cable idea.

scoobaspeaz said:
just updated mine...what i did was this:
1. I downloaded the patch to my internal storage and renamed it update.zip
2. adb reboot bootloader
3. fastboot flash recovery rogue-recovery.img (file name found on xda forums )
4. fastboot reboot
5. At the M logo i started pressing the down vol key to select recovery mode then pressed power. After this press power than up will get you into recovery mode. IMPORTANT...DO NOT LET IT BOOT INTO ANDROID OR ELSE CUSTOM RECOVERY WILL BE OVERWROTE AND YOU WILL HAVE TO START OVER AT STEP 2!!
6. When rogue recovery was shown i installed the update.zip from my internal storage.
I am now using the new ICS 4.0.4 update No need for that USB cable idea.
Click to expand...
Click to collapse
you meant this? http://forum.xda-developers.com/showthread.php?t=1235170

Yes that is the recovery image i used. Thank you for posting the link. Since my post count is low i was unable to post links.

scoobaspeaz said:
Yes that is the recovery image i used. Thank you for posting the link. Since my post count is low i was unable to post links.
Click to expand...
Click to collapse
confirm his method works but make sure you have to unlock the device before u flash custom recovery

Error upgrading Verizon Xoom to 4.0.4
Hi have tried to update my Xoom to ICS manually. I get the following error
Finding Update package...
Opening Update package...
Verifying update package...
Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2.6/HLK75H/237703:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:4.0.4/IMM76L/345519:user/release-keys"
E:Error in /tmp/sideload/package.zip
(status 7)
Installation aborted
Any thoughts
thanks
---------- Post added at 04:11 AM ---------- Previous post was at 03:59 AM ----------
I have been trying to update my Xoom manually but I think my Honeycomb version which is 3.2.1 build Number HTK75D is not correct? I have tried mashing the update button (nowt happened)
any thoughts ?
thanks

You have to be at least patched to HLK75H before applying this update

This will not work for the 3g only the 4g.

Can anyone post an MD5 checksum on the update zip file?
---------- Post added at 03:50 PM ---------- Previous post was at 03:40 PM ----------
I get a strange error. I'm on rooted stock 3.2.6 build HLK75H. I downloaded the zip file. Saved it to /sdcard/ as update.zip. Rebooted into Rogue Recovery, selected zip file from internal storage, selected update.zip and then I get this error:
...
Verifying current system...
assert failed: apply_patch_check("EMMC: /dev/block/platform/sdhci-tegra.3/by-name/boot: 8388608: 8fe0df6c1ee72cc7a302cca6d501f3736f9e2351: 8388608: 1026267ea3f01b247ea2f1ce59934e307d9e093b")
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Any thoughts? My guess is that my download isn't completing properly which is why I'd love an MD5SUM for the file....

From what I've seen and been told, you must be unrooted and stock to use this update!

shadow101202 said:
I have been trying to update my Xoom manually but I think my Honeycomb version which is 3.2.1 build Number HTK75D is not correct? I have tried mashing the update button (nowt happened)
any thoughts ?
thanks
Click to expand...
Click to collapse
You will need a different file that we don't have a link for yet. You have a 3G CDMA Xoom and the file you downloaded was for the 4G Xoom. If you are willing to be patient and wait, you could assist by providing the link for the 3G OTA file when you get the system update notification on your tablet. If you are interested in helping out, PM me and I'll give you instructions on how to do it so you can be ready when you get the update notification.

rob62551 said:
From what I've seen and been told, you must be unrooted and stock to use this update!
Click to expand...
Click to collapse
Well, I'm on stock - but I am rooted. Where can I find the process by which I can unroot?

http://forum.xda-developers.com/showthread.php?t=1680975
This should get you started.
I personally remain rooted. This update does not address use of the USB capabilities I need.
I enjoy using my 500gb drive!
Hope this helps you!

Easier Route....
SBF to HLK75H
Apply ICS update via OTG USB.
Done.
Worked great, and I didnt have to do all that fastboot bootloader dancing in the rain ****.

oldmacnut said:
Easier Route....
SBF to HLK75H
Apply ICS update via OTG USB.
Done.
Worked great, and I didnt have to do all that fastboot bootloader dancing in the rain ****.
Click to expand...
Click to collapse
And where, prey tell, did you find a SBF for HLK75H? The only one I know of is for 3.2.2/HLK75D.

No cable? This worked for me, down in the comment sections
http://www.droid-life.com/2012/06/04/download-motorola-xoom-4g-android-4-0-4-imm76l-update/
Step 1. goto settings, manage applications, select all and find Google Services Framework.
Step 2. Clear all data and force stop.
Step 3. Check for updates .
You may have to do this 3 or more times in a row, but it seems to work.
I just got ICS by doing this today!!!
Good luck and have fun
Got it from here: http://forums.androidcentral.com/motorola-xoom/178386-how-force-ics-update-vzw.html
On the 4th time it worked for me.

DarienA said:
No cable? This worked for me, down in the comment sections
http://www.droid-life.com/2012/06/04/download-motorola-xoom-4g-android-4-0-4-imm76l-update/
Step 1. goto settings, manage applications, select all and find Google Services Framework.
Step 2. Clear all data and force stop.
Step 3. Check for updates .
You may have to do this 3 or more times in a row, but it seems to work.
I just got ICS by doing this today!!!
Good luck and have fun
Got it from here: http://forums.androidcentral.com/motorola-xoom/178386-how-force-ics-update-vzw.html
On the 4th time it worked for me.
Click to expand...
Click to collapse
That method will break push notifications in apps like Twitter, Android Lost, Foursquare, IMDB, etc. If you do that method an an app stops notifying you of things, the only way to fix it is to clear that app's data and set it up again.

oldblue910 said:
That method will break push notifications in apps like Twitter, Android Lost, Foursquare, IMDB, etc. If you do that method an an app stops notifying you of things, the only way to fix it is to clear that app's data and set it up again.
Click to expand...
Click to collapse
thanks for that info. I don't really use my tablet for my in terms of push notification (since most of the same apps are installed on my phone), but I'll keep that in mind.
Update ran smooth and quickly, no I need to decide if I'm going to go back to the standard launcher or keep using Go Launcher...

DarienA said:
thanks for that info. I don't really use my tablet for my in terms of push notification (since most of the same apps are installed on my phone), but I'll keep that in mind.
Update ran smooth and quickly, no I need to decide if I'm going to go back to the standard launcher or keep using Go Launcher...
Click to expand...
Click to collapse
In the 3g doesn't work...
Enviado desde mi Galaxy Nexus usando Tapatalk 2

It probably means they haven't released the 3G HTK75D -> IMM76L update file yet. Shouldn't be more than another few days. When it comes, if you could post the link, I'd greatly appreciate it. If you don't know how to get the link, PM me for instructions.
I maintain a repository of stock Google firmware for the Nexus S, Galaxy Nexus, and Xoom at randomphantasmagoria.com and will need that link so I can add that file to the repository.
Sent from my Xoom using Tapatalk 2