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!

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

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.

[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