Database Info

Full 8.4.4.11 CWR ZIP

I tried to update my rooted TF using a repacked 8.4.4.11 update.zip file (the one with all the patch files in it), but it kept failing on checking of the existing APK hashes. Not sure why, but I got around it by doing a clean install of 8.4.4.5, manually applying the 8.4.4.11 patch, then taking all of the changed (between 8.4.4.5 and .11) files and packing them up in a zip file with an updater-script file.
You should be able to apply this to any US version TF (rooted or stock as long as you have CWR) and bring everything up-to-date without losing root or any of your other install modules, system APKs, etc.
Make sure you back up first, as this is something I quickly threw together and has not been properly vetted. If you find a problem, let me know and I'll try to get it fixed and updated ASAP.
You can also download this ZIP and just take out any APKs you are interested in (the google video apk seems to be popular for example).
Link: http://blog.ryantadams.com/2011/07/...4-5-to-8-4-4-11-changed-files-rom-update-zip/

good work dude! i know a bunch of guys here need this. Now Im assuming this has SU installed
The only thing is you should label this Thread correctly with a [ROM] tag so others will know

nicknowsky said:
good work dude! i know a bunch of guys here need this. Now Im assuming this has SU installed
The only thing is you should label this Thread correctly with a [ROM] tag so others will know
Click to expand...
Click to collapse
Unless I misread this is just an update script and not a full ROM. So this would only work for people on 3.1 though right? You shouldn't flash this from 8.2.X.X for example?
Edit: Thanks this is a great idea, and I was just ready to try this when I saw Prime 1.6 out. Keep it up, I wonder if something like this would work when the 3.2 update comes out.

ToyTank said:
Unless I misread this is just an update script and not a full ROM. So this would only work for people on 3.1 though right? You shouldn't flash this from 8.2.X.X for example?
Click to expand...
Click to collapse
...Not sure why, but I got around it by doing a clean install of 8.4.4.5, manually applying the 8.4.4.11 patch, then taking all of the changed (between 8.4.4.5 and .11) files and packing them up in a zip file with an updater-script file....
Click to expand...
Click to collapse
Looks like so; zip should be run on-top of 8.4.4.5.

thank you worked for me

This does not have SU in it (or anyhtign else "custom"), but when applied to a ROM that already has SU/busybox/anyhting else in it, those files will be retained.
This is an "update" in the sense that it only contains files changed between 8.4.4.5 and 8.4.4.11, so you will need to be coming from 8.4.4.5 (or perhaps anyhtign 3.1, not sure). It is nto really an "update" though, as all of the patch files (blahblahblah.apk.p) and the patch script have been replaced with full 8.4.4.11 version of the files and the script has been udpated to simply copy these over into the appropriate folders on yoru TF.
I see this being most useful for people who have modified their 8.4.4.5 install such that in will no longer be patachable using a script that pataches the existing files.

I just used this to update from 8.4.4.5_US and it seems to have worked just fine! I kept my superuser app, and nothing was touched. My apps, widgets, and settings are all in the right places. I've now got 8.4.4.11! Thank you very much rtadams89!

Thank you for this!! I've been racking my brain trying to get to a rooted 8.4.4.11 with a good CWM recovery and this did it!
thanks.

Can anyone check to see if their BT is able to turn on....?
After doing this...my BT won't turn on.

rpavich said:
Can anyone check to see if their BT is able to turn on....?
After doing this...my BT won't turn on.
Click to expand...
Click to collapse
My bluetooth works fine, using it right now. Did you tweak anyhting else on your TF?

Well done!
I still have the update notification, but "About" shows x.11.
Screen seems both brighter & to have smoother transitions.
-bZj

Does this also give you the Nvidia boot animation?

Is it possible to get a .zip for the WW version?

down8 said:
Well done!
I still have the update notification, but "About" shows x.11.
Screen seems both brighter & to have smoother transitions.
-bZj
Click to expand...
Click to collapse
Try clearing data for the "dmclient" app.

AllTheWay said:
Does this also give you the Nvidia boot animation?
Click to expand...
Click to collapse
Yes. Anything new or updated is included.

rtadams89 said:
Try clearing data for the "dmclient" app.
Click to expand...
Click to collapse
Thanks!
rtadams89 said:
Yes. Anything new or updated is included.
Click to expand...
Click to collapse
My transformer still has the "Transformer" boot animation I added - wasn't replaced when using this file to update.
-bZj

[email protected] said:
Is it possible to get a .zip for the WW version?
Click to expand...
Click to collapse
+1, also interested on this

down8 said:
Thanks!My transformer still has the "Transformer" boot animation I added - wasn't replaced when using this file to update.
-bZj
Click to expand...
Click to collapse
That is the boot animation I use, and I may have accidentally included this in the zip. If you want the real 8.4.4.11 animation, you can download the "update" 8.4.4.11 zip file that has been posted on xda and inside you will find that boot animation.
[email protected] said:
Is it possible to get a .zip for the WW version?
Click to expand...
Click to collapse
Since I don't have a WW version myself, I don't have a need to do this and quite frankly because I don't have much free time, I don't want to say I'll do something and then not follow through. Further, I'm not sure I can install the WW versions on my US transformer. That said, I will see if I can whip one together. If you get impatient waiting, you can follow the same process I did and make one yourself:
Backup your current ROM/setup
Wipe your device (leaving CWR in place)
Install the stock 8.4.4.5 WW with the ZIP found on XDA
"Update" to 8.4.4.11 using the update zip found on XDA
Backup this new 8.4.4.11 ROM
Restore to your first backup
Take the backup of the 8.4.4.11 ROM you made last, and use your computer to "unyaffs" it
You will now have 8.4.4.11 versions of all the system files; Look at the updater-script file in the 8.4.4.11 update zip and remove any files you just "unyaffs"ed that aren't mentioned in there
Put all of the remaining files (in their folder structure) into a zip file
Copy the updater-script (and it's folder structure) from my download to your zip file
Verify that your final zip looks like the one I posted
You should then have a ZIP file that will bring all the files on your device up to 8.4.4.11 WW without touching any of your other files (like su).

My BT doesn't turn on either.
I went to this as a stepping stone while recovering from a failed root. Went to an older stock than this update. I notice a few slow downs here and there and BT not working, but that's about it.
What I would really love is an image of 8.4.4.11 stock/rooted. I like having it rooted for things like Titanium, but I still like having the stock image. I can't seem to get back to that now.

Link is down, Dropbox says too much traffic. Rapidshare/MUpload?

[Q] trying to update my Pure Root WW 8.4.4.11 via CWM

Very new to this stuff but have experimented in simple tweaking of the tf101
- I tried updating to 3.2 via the file uploaded from this thread" [UPDATE][WW] CWM Rooted Update to STOCK 8.6.5.7 from STOCK 8.4.4.11 WW only "
but I keep getting this error:
assert failed: apply_patch_check("/system/app/SystemUI.apk"
Error in /sdcard etc etc
(Status 7)
- please correct me if im wrong(cause maybe I am), the steps I did was:
access CWM (power, -volume then a quick +volume)
install zip from sd card/ choose zip from sd card . .. yes - Install 8.6.5.7_FOTA_WW_root_rec.zip
then after "Verifying Current System..."
i get
assert failed: apply_patch_check("/system/app/SystemUI.apk"
Error in /sdcard etc etc
(Status 7)
- just so you'd know, i changed the looks of my bar buttons from this thread" [MOD] Stock/Xoom bar buttons for 3.1 rom (8.4.4.5 - 8.4.4.11 - Prime 1.6) "
- but as per the instructions before updating to 3.2, I switched back to the stock buttons which were still included in the thread w/o problems . . did it a second time after my first fail of attempting to update to 3.2
Any ideas on how to fix this, w/o wiping my entire data is very much appreciated..
current build: ww 8.4.4.11-20110711

FOTA check EVERY files it update, so since your MOD changed SystemUI.apk. FOTA will not work for you. You need to be very very close to stock for any FOTA patch to work.

Wiping /data will have no effect. The SystemUI in on your /system partition.
The updated script will check all the sha1 hashes of the system apps that it patches to make sure that it is patching the right one. If these fail, then the patch fails, which means the update fails.
After the patches apply, reboot into recovery from the menu. It will flash the blob!
You can unzip the update, and edit the updater-script in META..com...google...android
You could probably keep the odex file if it isn't modded. There will be two references- one to check the patch and one to apply the patch. Delete them both. Zip it all back together, maybe sign it for good measure, then try flashing again. You might not need to sign, but it wouldn't hurt.
EDIT: Ohh, I'm not sure if CWM will finish the OTA. It will probably patch all the system files and then bomb on the blob because it tries to copy it to the staging partition, which isn't mounted. You might be able to mount it through adb, or you could mod CWM to mount it automatically

it worked! thanks!!
i updated the updater-script , maybe removed too much since im now getting a force close on the systemui.apk and currently dont have any home buttons.. bummer..
but i believe i could just push a 3.2 systemui.apk file from one of the forums here
currently at WW 8.6.5.7
3.2
btw, this is what i removed from the line:
assert(apply_patch_check("/system/app/SystemUI.apk", "b630f0a4f2d1c8e450f6269a997c950d11694ce9", "4cbd4f2cb3f4ba71d803f930b5a9c8f850bdda31"));
set_progress(0.397204);
overdid it, or under did it? i'll keep this as reference for the future

That will be OK. There is another line much further down that actually applies the patch. That is probably why you are getting FC's. The modded file was patched, but since it was modded, the patch probably corrupted it. Pushing a new version would probably work.
Sent from my T-Mobile G2 using XDA App

[q] asus t101 restore from image help

Thought I backed up original ROM, when I opened the file today it was blank (NVFLASH).
I did copy the internal sd and have a copy of that but its not the right file type.
I also have some image files of the ROM, can I use either of these?

How about a little more information.... what file did you open that was blank?
Do you have files that look like 09_APP_raw.img? Did you use a script or just type a bunch of stuff in at the command line?
How did you copy the internal SD card that it is not the right file type?
What are these image files of the ROM?
So many questions...

The way I copied the internal sd was in the file manager, had to click show hidden files to do it.

The blank file was a file that brk asus transformer root toolkit made. Went to do a restore with it the next day and file not found,
The image files I have are ones that another version cwm m ade doing a backup a few times that I got from the market. But that version of cwm doesnt support asus.

OK- it that helps. If you just want the stock firmware, you can get that from the ASUS website. You might have to get the 8.6.5.9 version and then upgrade to 8.6.5.13 via the ota. From there you can root again and/or install CWM if you want.
There are TF specific versions of CWM- solarnz and roach each have a version in the dev section. These might allow you to flash the data partition from your backups to restore any apps that you installed. I think brk's tool uses one of the modded versions of CWM.
As far as the internal sd card, you might have to copy those over with an external SD card/adb/ftp/etc.
If you want to restore one of the CMW images you have, that might be tricky, but you can extract them with the unyaffs tool. Google should find it for you. They might be flashable with one of the modded versions of CWM, but I think the modded versions have a slight difference in the parts that they backup/restore. You can try the "advanced restore" option to restore the data.img, but I'm not sure what would happen.

I looked at asus website for the rom, all I found were firmware and kernels are those the roms? I would prefer doing it that way.

Yup- select the android OS and pick your country specific firmware (aka ROM).
It might be tricky if you are downgrading I.e., you flashed 8.6.5.13 and want to flash the stock 8.6.5.9 firmware. I'm not sure if you can downgrade the "easy" way.
The easy way is to unzip the firmware and place the whole ASUS folder on your external SD card. Turn on the TF and insert the SD card when it is running- a notification should pop up to flash. ASUS has some documentation with pictures in the Manuals section. Look for one of the "Update SOP" files.
Let me know if that works. I've never tried to downgrade that way, so I'm not sure if it will work because you might be on a higher build number. If it doesn't, there is another way if you are rooted or you can use nvflash.

Let me get this right, do I use the firmwaree or the kernel.

Use the firmware.

Thanks, I reread the firmware aka rom. I'm in the us so the us one right! Will let you know if it works, says something about downgrading in there...

If it won't let you downgrade, then you have to do it the "hard" way.... but you have to be rooted.
Download the firmware and unzip it. It should be something like ASUS/Update/some.zip
Unzip the some.zip file and it'll contain a blob. Copy the blob to your external sd card or use adb to push it to your TF.
It would be a good idea to verify the MD5 sum of the blob. The US one that I downloaded for 8.6.5.9 is
MD5(blob)= 57d4c4342277d39e523e26b943891a1f
Use terminal on the TF or adb shell from your PC and type the following:
Code:
su
dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
the last three characters are zero-pee-four. It's important to get this right or you could mess up your TF.
If you copied it somewhere else, then adjust the /Removable/MicroSD/blob part.
It will take a while because it's a big file, but when it's done, type "reboot" or just turn off, then turn on your TF, and it will flash you back to stock. You should see a blue progress bar that moves very slowly. Be patient, it takes a while and should reboot when it's done. You will be unrooted with a stock recovery at this point.
Afterwards, you can verify that you have the downgraded firmware and then check updates to receive the OTA to upgrade to 8.6.5.13. Lastly, clean up and remove the blob file from your sdcard- it's 521MB!

Your awsome man! You took all that time to help me out and I won't forget it gee!

So did the downgrade work, or did you have to flash the blob?

Not gonna try tonight, thats how I lost the backup as I was tired... Will try tomorrow and will let you know what workes.
I have prime on here now so I dont think that would technically be a downgrade?
Yes I am rooted.

So while I have you, will a rooted machine get OTA updates?

Yup, the updates still download, but they usually break root or won't flash because something is not stock, such as kernels.
Of course, you can mod them so they flash and keep root.
Good idea about starting fresh tomorrow.

r u Randal in Ca?

No, sorry.

No worries, just reminded me of the big guy. Will let you know how everything goes. I try to be sure before I comet to a change I can't recover from so will have to sus up everything first.
I want to thank you again for the help, I hope you get compensated for it?

Hardy har har, and I'm still in thi situation!
We will see tomorrow!

Stock TF101 wont OTA

So my sister just bought a Transformer tonight, It has never been rooted or anything.
It will not detect any updates on the "search for update" OTA thing.
I also downloaded the ICS firmware directly from Asus's website, extracted it on a microSD card, and the trasnformer still doesnt show theres any update.
In the manual update guide it says put the extracted ASUS folder on the SD card, however there is no ASUS folder in the update downloaded from their site.
No idea whats going on.
Any help is appreciated.

Did you unzipped the file you download from Asus website? You can't leave it whole, there's another zip inside that zip.

Yep I followed all the instructions

Bawb3 said:
In the manual update guide it says put the extracted ASUS folder on the SD card, however there is no ASUS folder in the update downloaded from their site.
Click to expand...
Click to collapse
Reading that gives me the feeling that you probably didn't do it right. There is no reason it won't work.
Can you post the EXACT steps you took?

I'm having the same issue
There is no ASUS directory in the zip.
Inside the second zip there is a file called blob and a directory called Meta-Inf with a bunch if files in.

Okay, I go to asus's tf101 site, download sectiion > firmware.
Download the US SKU 4.0.3 firmware update which is ~300mb
Extract that zip which yields a file with another ZIP inside of it. There is no ASUS folder.
Like the above poster said, the second zip file looks like a recovery update script that you would flash in CWM with a meta-inf with the signatures, and a blob file.
EDIT[SOLVED]:
Okay I figured it out. I downloaded the 3.2.1 update from asus, which does have the ASUS folder. This one worked and launched the update wizard.
It seems that the update wizard looks for the directory /ASUS/Update/US_epad-user-x.x.x.xx.zip file on the root of the microSd card.
So I put the ICS update which is US_epad-user-9.2.1.11.zip into the ASUS/Update/ Directory in the microSD card that I initially extracted from the 3.2 update. Sure it enough it launched the update wizard and allowed me to select that file for the update.
ASUS Didnt properly upload the ICS update it seems.
I still dont know why the OTA didnt acknowledge an update.

OK, this is just getting dumb now.
OK, this is just getting really really stupid now. ASUS I AM SERIOUSLY STARTING TO HATE YOU.
OK I have done the following across MULTIPLE reboots and really getting ticked off now. This would NOT be an issue if the recovery mode didn't give me a damned green droid with yellow triangle with ! in the middle of it.
I have:
Way 1
-------
1 - Extracted WW_epad-user-9.2.1.11.zip from the original WW_epaduser9_2_1_11UpdateLauncher.zip from ASUS site.
2 - Copied extracted WW_epad-user-9.2.1.11.zip to EP101_SDUPDATE.zip
3 - Put both zips on root of microSD. Failed. Tried with copy on /sdcard/ as well, both with and without leaving the original 2 on the microSD.
Way 2
-------
Extracted the WW zip both to the / of the tablet and to the root of the microSD, trying both with and without leaving the originals on the microSD.
Way 3
-------
Same exact as Way 1 and Way 2 but with removing the .zip extension from both files, and with swapping removal of the extension between the 2 files on both the tablet and the microSD.
Way 4
-------
Tried all permutations of Way 1, 2, and 3 with both 8.6.5.21 and 8.6.6.21.
NONE of these ways worked.
I grabbed NVFLASH with 8.6.5.13 and that flashed just fine, except that the recovery mode is still giving me the triangular ! droid image.
I absolutely positively can not root or otherwise do anything to this tablet.
The tablet is a ASUS 32GB Transformer HD Tablet (Serial #: B50KAS#####) with a 2GB microSD formatted with FAT32. (I've tried formatting NTFS and FAT32) This is not a Prime! This is the original Transformer!
I even found an article for how to create your own and tried that as well!.
(Wow really guys? You can't post outside links?? Really? What the heck is that retardation supposed to prevent? I mean really!)
All I get for that mess is the USB connection is dropped even before NVFLASH can do anything. I have Windows 7 Ultimate, Mac OS X Lion, and several distributions of Linux (ArchLinux, Ubuntu, CentOS, Debian, and OpenSUSE). I've tried on them all!! This has been a great many hours trying to figure this out, searching like crazy through these forums. (Incidently, the 10 posts requirement in order to post in the 'experienced' area is just nuts.)
I even tried both the renaming WW portion of the zip name to US as described in other areas in this forum and it still failed! I'm a programmer by trade, and I have never run up against something as stubborn as this! The recovery mode is what is breaking all of this. I absolutely can not get a stable, working recovery mode on this tablet! Heck, I'd be happy with the stock 8.6.5.21 on here or ICS (the 9.2.1.11) without ever again attempting to root the pup! Can anyone assist in getting the recovery mode back to normal? Is there a way to use NVFLASH to write the original recovery mode back such that I stop getting that dang Droid With Yellow ! Triangle image?

Do you have CWM Recovery installed? If so, it will not do the OTA updates, but you can just go into CWM Recovery and then choose the 9.2.1.11 firmware and when it is done flashing, you will have an unrooted stock ICS (with stock recovery).

CWM
Unable to root. RazorClaw tells me I'm missing the required file (though it doesn't tell me what file that its) and says Too bad!

deryldoucette said:
Unable to root. RazorClaw tells me I'm missing the required file (though it doesn't tell me what file that its) and says Too bad!
Click to expand...
Click to collapse
Razorclaw only works on 8.6.5.19.
Not certain on which version you try to run razorclaw.
use Vipermod on 8.6.5.21 or higher.

was 8.6.5.13 which is what i was able to nvflash back to the tablet. Do you know if there is a more recent nvflash packaged 8.6? Looking to see if I can at least put 8.6.5.21 on here. Currently still running the 8.6.5.13

Mine also wont OTA, i have put the downloads in ASUS/Update and nothing... does not detect updates.

Just bought my tf101 yesterday, same problem. Called support and they told me the update was not pushed to my device yet and a manual update would probably fail.how long ago was ics released?
found it, february 24th... It should be pushed to my device by now, right?
Sent from my SPH-D700 using XDA

G'day guys,
I finally managed to get it to work for me!
TLDR Version - I have the US build version - this may or may not be relevant to these instructions:
* Use "App Backup" to backup all your apps and/or data (optional)
* Factory reset
* Choose "English (US)" from the initial setup wizard and default options for the rest (skip wifi setup)
* Plug the transformer in to your PC via USB
* Create the following folder structure exactly (including case!)
<Internal Storage>\ASUS\Update
* Copy US_epad-user-9.2.1.11.zip that you extracted from US_epaduser9_2_1_11UpdateLauncher.zip to "<Internal Storage>\ASUS\Update"
* Reboot Transformer
* Choose the triangle from the notification area
* TF should update successfully!
Long version:
I followed the instructions in this thread but still wasn't having any luck.
I don't have an external SD card so I was copying the zip from the downloaded file to internal storage\Asus\Update. The triangle was appearing in the bottom right but when I went to do the update it would reboot to the android man with an "!" on his chest. I then tried a factory reset and then recopied the update and tried again. Same "!" dude. I tried another reset but did two things different and it then worked! Instead of choosing "English (UK)" on the initial setup wizard (I'm from Aus) I chose "English (US)" (just a wild guess given its US update required for my TF. The other thing that I did differently was located the update at "ASUS\Update". Note the capitalisation of "ASUS" where previously I was using Asus. I had this idea when I noticed the first time I had both "Asus" and "ASUS" folders there simulataneously. So one or both of those things made it work for me!
If these tips worked for you please post your success (or otherwise even).
Best of luck!

[GUIDE] Updating A700 while rooted! revised: 8/4/12, bonus for USA tab owners

Make sure you are using CWM version 6.0.1.0
I am not responsible for whatever happens to your device because everyone else puts this in their threads too! get over it
Be sure to click that Thanks button if this helped you. this also appears in everyone else's thread's! deal with it
1. download the update file for your region from paugustin's thread here:
http://forum.xda-developers.com/showthread.php?t=1720157
2. unzip it inside any folder.
3. open the file called updater-script which is located at:
/META-INF/com/google/android
4. delete the line and the blank space left afterwards then save changes to the file. the line for the US version looks like this:
assert(getprop("ro.product.name") == "a700_pa_cus1");
5. highlight everything that came out of the download from step 1, zip it, and rename it to update.zip
6. place in the root of an SD card, not internal storage!
Note: a few users have recommended placing the update.zip on internal storage. i tried it again from a SD card and it worked just fine. if you're having issues with this try internal.
7. reboot to recovery mode. if you need this guide you've had to do it in the past, nuff said! :silly:
8. select Apply update.zip
9. after you select Reboot System, you will be given two options:
Yes will keep CWM recovery but you wont be able to use recovery mode at all until you unlock the bootloader again!
No will allow the update to restore stock recovery, and you will need to re-flash CWM.
10. if you chose Yes from step 9, unlock your bootloader and do the root process again. DONE!
if you chose No, unlock your bootloader, flash CWM again, and do the root process again. DONE!
there are already guides on how to do that.
BONUS FOR USA TAB OWNERS!
This is ONLY FOR UPDATING FROM the Acer_A700_AV043.RV00RC00_AV043.RV07RC06_PA_CUS1.zip file from the link in Step 1 at the top of the page.
If you are on any other version, and / or from any other country, DO NOT TRY THIS!
This is the latest update with the power option added in settings & touch sensitivity improvements, with the getprop line already deleted from the script!
A. Download this directly to your tab.
B. Reboot to recovery mode.
C. Install.
D. After selecting Reboot System you will be given two options. Refer to Step 9 above.
E. After making your choice, you will be given the option to prevent the update from deleting root :victory:
F. Unlock your bootloader again.
G. If you chose No. from Step 9, re-flash CWM 6.0.1.0
H. If you chose No. from Step E, root again if you wish.
DONE!!

I've try this, but when I do point 8 (select Apply update.zip), the update is aborded.
I'm on SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip with the root by patched boot.
I want install Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR.zip.
I don't know why update fail.

imtheyoyo said:
I've try this, but when I do point 8 (select Apply update.zip), the update is aborded.
I'm on SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip with the root by patched boot.
I want install Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR.zip.
I don't know why update fail.
Click to expand...
Click to collapse
i think i know why.
i revised step 5, check it out

That's what I had done, zip and rename in update.zip.

imtheyoyo said:
That's what I had done, zip and rename in update.zip.
Click to expand...
Click to collapse
hmm... did you put it on an sd card?
and what error is it giving you?

Sterist said:
hmm... did you put it on an sd card?
and what error is it giving you?
Click to expand...
Click to collapse
Yes, and the message was "Update aborted"

Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
---------- Post added at 10:57 PM ---------- Previous post was at 10:52 PM ----------
CheopsChefren said:
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
Click to expand...
Click to collapse
Thanks for any advice.

CheopsChefren said:
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
Click to expand...
Click to collapse
I'm not sure if a modified update script would run on the stock recovery. you can try it, the worst that would happen is it will decline to run the update. i would recommend you always have CWM recovery regardless of any flashing/updating plans you may or may not have.
and the location for the update.zip does not change regardless of what you use to get the file there lol it doesn't matter if you use a Toyota or Lamborghini to get to work. silly question lol..

Thanks for your answer. The problem is, an unmodified update script wont run either on my unlocked A700.
And, I am scared about using CWM, as I hear stories it will possibly brick your A700, and that is something I am not too keen about.
But, with Root Explorer compared to ES File Explorer you have more possibilities. But I agree, it was abit a silly question.
So now, how to update my unlocked A700 with the OTA delivered by Acer? That's the question.....

CheopsChefren said:
Thanks for your answer. The problem is, an unmodified update script wont run either on my unlocked A700.
And, I am scared about using CWM, as I hear stories it will possibly brick your A700, and that is something I am not too keen about.
But, with Root Explorer compared to ES File Explorer you have more possibilities. But I agree, it was abit a silly question.
So now, how to update my unlocked A700 with the OTA delivered by Acer? That's the question.....
Click to expand...
Click to collapse
by my understanding, the CWM versions to avoid are 5.4.0.0 (something like that) and the touch version(s)
unlocking your bootloader and not installing CWM is like alcohol-free-beer... pointless.

When trying the above mentioned procedure, i first got an error 6, which i solved by editing the updater-script the second time with notepad++, so i could keep the unix-like line-ends.
Then when i tried to run the update.zip from within cwm, i got error status 7.
(On both the downloaded update file from the thread mentioned above, and from the original from Acer received OTA update file)
As far as i know, after googling error status 7 has to do with the update zip not for the system trying to update. But i am sure, as i also tried with the Acer received OTA (after deleting the first line in the updater-script), i used the correct update file.
What could cause this?

Hi. Link for U.S. tab owners (www.sendspace.com) is dead. Can you post again?

eman01 said:
Hi. Link for U.S. tab owners (www.sendspace.com) is dead. Can you post again?
Click to expand...
Click to collapse
LOL stupid mistake on my part
the link wasn't really dead, i just screwed up in how i posting it lol thanks for mentioningit

Got it. Thanks.

OK. I finally tried above method to update rooted U.S. A700.
Started with:
Image Acer_AV043_A700_RV07RC06_PA_CUS1
Build Acer_AV043_A700_1.029.00_PA_CUS1
CWM Recovery 6.0.1.1
I tried both methods above- initially using the update.zip specifically provided for U.S. A700 owners in the 2nd part of 1st post of this thread
IN "BONUS FOR USA TAB OWNERS!".
Tried it on 1st external SD, then internal SD.
Both ways I get RED TRIANGLE with exclamation point and message:
"Can't open /sdcard/update.zip
(bad)"
OR
"Can't open /emmc/update.zip
(bad)"
I am, of course, sure I copied the update.zip directly from Downloads to the root of the external and internal cards;
I also made sure to use "Choose zip from SD card" in CWM to find the Update.zip file right where I put it.
Not ready to quit, I tried again using the original Update zip file and modifying updater.script myself, exactly as described in the 1st part of the 1st post. I also tried this update.zip with modified updater.script on both the external and internal SD, without success.
This time I did get further, receiving:
Finding update package...
Opening update package...
Installing update...
Mount Data success
Verifying current system...
assert failed: apply_patch_check_("EMMC:\dev\block\platform\sdhci-tegra.3/by-name/LNX:4065536:95
Then a bunch of letters/numbers
E:Error in sdcard/update.zip
(Status 7)
Installation aborted.
P.S. I verified I have the assert line deleted in the updater.script before I tried this.
I should mention that I have stock ROM, have and have NOT deleted any system apps
(I have inactivated a few like VirusScan within Android).
Luckily I was able to reboot without any problems after all these attempts, but now I am stuck.
Any ideas?

hmmm that's an error i haven't seen before. try deleting the update and downloading it again, or disabling assert check
I'm not a developer, that's the best i can suggest. you'd have to ask someone with a bit more knowledge
it might have something to do with the root method you used originally

Well, I tried yIur modified update.zip multiple times (downloaded it 3 different times, and tried both internal and external SD). As mentioned, I also tried modifying the updater.script myself (used JOTA text editor; maybe that was an issue with respect to how it saves a file, etc.).
How does one disable assert check, as you describe? A link, perhaps?
Interestingly, today I was able to flash the original1.029 update (1st A700 OTA update) after modifying it's updater.script in exactly the same fashion you describe. It put me back to stock 1.029, which I then updated to stock 1.057 (2nd A700 OTA update). I then re-unlocked bootloader, re-rooted and re-installed CWM recovery 6.0.1.1 easily and successfully as described in the threads in A700 development in this forum. Still holding out on CM ROM, as it seems fairly buggy. Thanks for trying. My way definitely took longer; don't know why your direct method would not work on my tab. Thanks.

disable asset check should be one of about 4 or 5 options to choose from, right next to ''choose from internal'' / external
it actually might not be available on this device it's been a while since I've used CWM
i do these modifications right from my tab with ES file explorer.
glad you were able to get it working

[solved] US A700 rooted OTA update
hi all,
after few days of messing about I finally managed to update a rooted US A700. I will try to guide you through what I did.
After initially booting up the A700 I upgraded it OTA to AV043_A700_RV07RC06_PA_CUS1 and after that rooted it using method #2 in the rooting thread (method #1 didn't work for some reason)
Got OTA notification saying that AV043.RV23RC03_PA_CUS1 was available (performance update, 35.72MB in size) but that wouldn't install giving error Status 7.
Installed CWM 6.1.1, still tthe same results, it wouldn't even install any of the other ROM's that are posted in this forum.
I probably should mention that I saved the original OTA update for installation later.
here is the solution (at least in my case)
Downloaded ROM Acer_A700_AV043.RV00RC00_AV043.RV07RC06_PA_CUS1.zi p from http://forum.xda-developers.com/showthread.php?t=1720157
Extracted boot.img and flashed via fastboot flash boot boot.img
Rebooted into CWM recovery and flashed the earlier saved OTA update no problem (was saved on internal memory but external memory card should work as well)
Then all that needed to be done was to root the A700 again (I used method #2 again)
Hope that helps someone.

eman01 said:
OK. I finally tried above method to update rooted U.S. A700.
assert failed: apply_patch_check_("EMMC:\dev\block\platform\sdhci-tegra.3/by-name/LNX:4065536:95
Then a bunch of letters/numbers
E:Error in sdcard/update.zip
(Status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You are not using the original bootloader so checking failed.
Simply delete this line to fix it (it happened to me last week when I created my homemade OTA update). Don't forget to unlock your bootloader after that !