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
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 !
My phone is a samsung galaxy S3 clone, GT-9300 running ICS 4.0.4
No idea which manufactor it is, I got it from a marked in Thailand, and the phone is marked with Samsung and look exactly like the original. A bit different layout behind the battery cover though.
I did follow the guide from this thread:
http://forum.xda-developers.com/showthread.php?t=1610121&nocache=1
I also did use the auosign program to sign the update.zip file and got a new update_signed.zip file
But when I try to apply the update_signed.zip file from recovery mode I get this message:
-- Install /sdcard ...
E:signature verification failed
Signature verification failed
Installation aborted.
Any idea why this happens?
I have attached mu update file here if anyone cares to take a look at it.
View attachment update_signed.zip
solved..
I found the solution by flashing the modified recovery that was mentioned in this thread.
Also I found that my phone is identical to the one pictured in that thread by OP.
http://forum.xda-developers.com/showthread.php?t=1921178
I ended up flashing the whole rom, recovery and applied the camera 1013 archive as well, and now my phone is almost ok.
My problem was that I lost my camera after a dubious update. Now the main camera is working, and the gps that never worked before is also working (although weak signal), only problem now is the front camera is not working.
As I understand, my situation is fairly specific, and so I need to address a few points:
This is my first time rooting a phone- I've made several mistakes but managed, at this point, to avoid bricking my phone
I'm using a Nexus 5, and flashing the pwnphone system (Android Open Pwn Project)
I've followed all the standard steps (except one... see below) for unlocking, rooting, and using TWRP as my recovery
I've also successfully flashed AOPP once, although I made an error I couldn't fix during setup and needed to reinstall
To my stupidity, I forgot to make a Nandroid backup on both attempts
I've just used TWRP to wipe my phone's Dalvik/ART Cache, system, data, and cache, assuming I could reflash the same zip I used before
MD5 check is disabled
Zip validation is disabled
Okay, so let's get down to the heart of the issue now. My phone is sitting here, plugged into my computer, I have a command prompt running, and adb is working properly. I try to flash THE SAME ZIP file I used, just before, to start from a clean slate AOPP install, and now I'm recieving an Error: 7.
I looked up the fixes for this, and ran into a problem: I'm already using the most recent version of TWRP- and I just made an alternate AOPP.zip where I removed the asserts from /META-INF/com/google/android/update-script. I was hoping this would solve my problem, but it didn't.
Now, instead of getting an Error: 7, I'm getting an "invalid zip format" notice with very little other information.
Installing zip file '/sdcard/aoppfix.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Invalid zip file format!
Error installing zip file '/sdcard/aoppfix.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
I have no idea what to do at this point. In my earlier error, I failed to make a Nandroid backup file- and much to my dismay- I can't even find one someone has uploaded elsewhere which I could use to at least have a functioning phone to to boot into.
Can someone please help figure out what my next course of action is?
Hi and welcome to XDA Assist !
I`ve searching and I couldn`t find that rom on the Nexus 5 development forums so it`s hard to figure out what`s the problem
Your attempts to modify that script are courageous but I`m afraid that is more than a script issue
Try to flash a different rom with xda support and you`ll get more info and help , good luck !